Mandatory Patching Requirement for Database Versions 11.2.0.3 or Earlier, Usi...

郑全

In this Document
        Purpose
        Scope
        Details
        1. What are the minimum recommended patchset/PSU/BP/RU levels?

        2. What is the timeline for moving to the minimum recommended patchset/PSU/BP mentioned?

        3. What is the change introduced by the patches listed above?

        4. What happens if the mandatory PSU / patchset is not applied?

        5. What about databases that are 10.2 or older, which are not listed in the table?

        6. How can I check the details regarding the dblinks to and from a database?

        7. Will there be any issues with the db links connecting two unpatched databases ? Or databases of older versions?

        8. Will the dblinks involving a patched and an unpatched database, stop working immediately after April 2019?

        9. What should I do, if the dblink connection from an older version database to a latest (or patched) version database fails, after April 2019?

        10. What do we need to do for 11.2.0.4, 12.1.0.2 and 12.2.0.1 database releases?

        11. Support and Questions

        References

Applies to:

Oracle Database - Enterprise Edition -Version 11.1.0.7 to 12.2.0.1 [Release 11.1 to 12.2]
Oracle Database - Standard Edition - Version 11.1.0.7 to 12.2.0.1 [Release 11.1to 12.2]
Information in this document applies to any platform.

Purpose

This support note provides additional info related tomandatory patching/upgrade of all supported releases of Oracle Databases to aminimum patchset/PSU level before April 2019.

Scope

The document is intended for all DBAs.

Details

All supported releases of Oracle Databases need to bepatched to a minimum patchset/PSU level before April 2019 to ensure proper functioning of database links. Thisnote only applies to Database Server installations and the interoperability ofdatabase clients with database servers is not impacted by this patch.

1.What are the minimum recommended patchset/PSU/BP/RU levels?

For all database releases prior to 12.2.0.1, ensure thatall interconnected databases are in the below mentioned patchset/ PSU/BP levelsor above:

Mandatory patch levels
Patch Name	Release Data	Patch Number
12.1.0.2.0 PATCH SET FOR ORACLE DATABASE SERVER	09/01/15	Patch  17694377
11.2.0.4.0 PATCH SET FOR ORACLE DATABASE SERVER	08/27/13	Patch  13390677
DATABASE PATCH SET UPDATE 11.2.0.3.9 (INCLUDES  CPUJAN2014)	01/14/14	Patch  17540582
DATABASE PATCH SET UPDATE 11.1.0.7.20 (INCLUDES  CPUJUL2014)	07/14/14	Patch  18522513
ORACLE 11G 11.2.0.3 PATCH 28 BUG FOR WINDOWS    **Patch 28 is withdrawn. Apply Patch 29 or above.	02/26/14	Patch  17906982 (Win x64) | Patch  17906981 (Win 32-Bit)    ** Patch 29 Patch  18075406 (Win x64) | Patch  18075405 (Win 32-Bit)
ORACLE 11G 11.1.0.7 PATCH 57 BUG FOR WINDOWS	07/15/14	Patch  18944208 (Win x64) | Patch  18944207 (Win 32-Bit)
QUARTERLY DATABASE PATCH FOR EXADATA (JAN 2014 -  11.2.0.3.22)	01/14/14	Patch  17747147

In summary, 12.2.0.1 and higher releases, 11.2.0.4 and12.1.0.2 patchsets have this fix included, while patches are available for11.1.0.7 and 11.2.0.3 releases. If you have any other database serverinstallations (e.g. 10.2.0.5, 11.2.0.2), you should upgrade such databases ifyou would like the older databases to continue using database links with newerversions of databases.

Patching the older versions is mandatory *only*if you want to have a db link connection to a latest release or patcheddatabase.

2.What is the timeline for moving to the minimum recommended patchset/PSU/BPmentioned?

All databases should be at the above mentionedrelease/patchset/ PSU/BP levels (or above) before April 2019.

3. Whatis the change introduced by the patches listed above?

The patches listed above make the older databases capableof supporting increased SCN soft limit (i.e. support transactions with higherSCN rate) though the increased SCN soft limit only becomes effective at a latertime (after April 2019).

4.What happens if the mandatory PSU / patchset is not applied?

If either the source or target database using database links is notpatched/upgraded to the right patchset/PSU level, you may get run-time errorsduring database link operations after April 2019. In order to resolve the errors, you would immediatelyneed to patch/upgrade the databases.

5.What about databases that are 10.2 or older, which are not listed in the table?

Please ensure that you don't have any database link(incoming or outgoing) between earlier versions of databases (e.g. 10.2) andthe database releases/patches mentioned in this document (Under Sec 1.What are the minimum recommended patchset/PSU/BP/RU levels? ) as we don't planto release patches for those unsupported versions of databases. If you continueto have such database links after April 2019, you may get run-time errors during database linkoperations and you would need to disconnect those database links at that time.

6. Howcan I check the details regarding the dblinks to and from a database?

In order to identify database links, please review "Viewing Information About databaseLinks" in Database Administrator's guide.  

Please note that outgoing db links from a database can beidentified via DBA_DB_LINKS view for all database releases.

select * fromdba_db_links;

For 12.1 and later releases, you can also find out aboutincoming database links via DBA_DB_LINK_SOURCES view.

select * fromdba_db_link_sources;

7. Willthere be any issues with the db links connecting two unpatched databases ? Ordatabases of older versions?

The dblink connections involving two unpatched databasesor two older releases are not directly affected by this change. Having saidthat, we do recommend to apply the patches or upgrade the database as per thetable above. The patches listed above are recommended inline with the featuresavailable in the future releases.

8. Willthe dblinks involving a patched and an unpatched database, stop workingimmediately after April 2019?

DB Links won't become unusable immediately after April2019. But might encounter errors (for some cases) at any point of time, afterApril 2019.

9. Whatshould I do, if the dblink connection from an older version database to alatest (or patched) version database fails, after April 2019?

Upgrade the older version database to any patch levelmentioned in the table - Mandatory patch levels.

10. Whatdo we need to do for 11.2.0.4, 12.1.0.2 and 12.2.0.1 database releases?

No action is necessary. All the fixes needed are alreadyincluded in these releases.

11.Support and Questions

If you have any queries please post themin the Database community page: https://community.oracle.com/message/14710245#14710245