Shulou(Shulou.com)06/01 Report--

Recommended patches and operations for Oracle database version 12.1.0.1 Magi 11.2.0.3 and earlier-by June 2019 (document ID 2335265.1)

In this document,

Purpose

Range

Details

1. What is the recommended patch set / PSU / BP / RU level?

two。 What is the schedule for mentioning the recommended patch set / PSU / BP?

3. What are the changes introduced by the above patch?

4. What happens if the recommended PSU / patch set is not recommended?

5. For 10.2 or older databases, which are not listed in the table?

6. How do I check the details of dblink in the database?

7. Is there a problem connecting two unpatched database links? Or the old version of the database?

8. Will dblink involving patched and unpatched databases stop working immediately after June 2019?

9. What should I do if the dblink connection from the old version of the database to the latest (or patched) version fails after June 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 issu

The reference applies to:

Oracle Database-Enterprise Edition-versions 11.1.0.7 to 12.2.0.1 [versions 11.1 to 12.2]

Oracle Database-Standard Edition-versions 11.1.0.7 to 12.2.0.1 [versions 11.1 to 12.2]

The information in this document applies to any platform.

Purpose

This support note provides additional information related to the recommended patching requirements for Oracle database versions 11.1.0.7, 11.2.0.3 and 12.1.0.1, which will be completed by June 2019.

Range

This document is intended for all DBA.

Details

It is strongly recommended that the Oracle database versions 11.1.0.7, 11.2.0.3 and 12.1.0.1 be patched to the patch set / PSU level mentioned below by June 2019 to address potential future problems with dblink interoperability. If you are running the database version 12.2mai 12.1.0.2 or 11.2.0.4, you do not need to do anything. This description applies if you are still using version 10.2 or earlier and use dblink in a later database version.

The interoperability between the database client and the database server is not affected.

(based on customer feedback, we are currently evaluating the need and feasibility of providing a patch for 10.2.0.5, and this description will be updated later. )

1. What is the recommended patch set / PSU / BP / RU level?

For database versions 11.1.0.7, 11.2.0.3 and 12.1.0.1, ensure that all interconnect databases are at the patch set / PSU / BP level or higher mentioned below:

Recommended patch-level patch name release data Patch No. 12.1.0.2.0 for ORACLE DATABASE SERVER PATCH SET09/01/15 Patch 1769437712.1.0.1.0 for ORACLE DATABASE SERVER PATCH SET09/01/15 upgrade to 12.1.0.2 or later Patch 1769437711.2.0.4.0 for ORACLE DATABASE SERVER Patch set 08swap 27swab 13 Patch 13390677 Database Patch set Update 11.2. 0.3.9 (including CPUJAN2014) 01Accord 14 Patch 14 Patch 17540582 Database Patch set Update 11.1.0.7.20 (including CPUJUL2014) 07Accord 14Accord 14 Patch 18522513

ORACLE 11G 11.2.0.3 PATCH 28 BUG FOR WINDOWS

* * Patch 28 was revoked. Apply patch 29 or later.

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 WINDOWS07/15/14 Patch 18944208 (Win x64) | Patch 18944207 (Win 32-bit) Quarterly Database Patch for EXADATA (January 2014-11.2.0.3.22) 01 14 patch 17747147

In summary, 12.2.0.1 and later, the patch sets 11.2.0.4 and 12.1.0.2 contain this fix, and patches are available for 11.1.0.7 and 11.2.0.3. If you have any other database server installations (such as 10.2.0.5 11.2.0.2), you should be aware of possible dblink problems in the future and consider applying the required patches or upgrading the database, or do not use dblink with a newer version of the database.

two。 What is the schedule for mentioning the recommended patch set / PSU / BP?

All databases are recommended at the above version / patch set / PSU / BP level (or above) by June 2019.

3. What are the changes introduced by the above patch?

These patches increase the current maximum SCN (number of system changes) limit for the database.

At any time, the Oracle database calculates the "no more" limit of the number of SCN the database can use based on the number of seconds that have elapsed since 1988. This is called the current maximum SCN limit for the database. This ensures that the Oracle database is allocated to SCN over time, providing more than 500 years of data processing capacity for any Oracle database.

These recommended patches allow the database to allow a higher current maximum SCN limit. The rate at which this limit is calculated can be called the "SCN rate," and these patches help allow higher SCN rates so that the database supports transaction rates many times higher than in previous versions.

Note that these patches will only increase the maximum limit, but the current SCN will not be affected. Therefore, if there is no significant change in the transaction rate for all databases, the current SCN will still be below the current maximum SCN limit, and database links between new (or patched) and unpatched databases will continue to work. These patches provide security measures to ensure that you have no problems with dblinks and are not affected by any possible rate of transaction changes.

With the application of these patches, this change in the current maximum SCN limit will occur automatically from June 23, 2019.

4. What happens if the recommended PSU / patch set is not recommended?

If this patch is not applied, unpatched databases will have a lower SCN rate or a lower current maximum SCN limit.

Newer or patched databases will have higher SCN rates or higher current maximum SCN limits.

Therefore, this may occur when the patch database is at a higher SCN level (due to a higher SCN rate tolerance) and an unpatched database is at a lower SCN level (due to a lower SCN rate tolerance).

When you open a dblink between these two databases, it must synchronize the SCN level of the two databases, and if the SCN increase required in the synchronized unpatched database exceeds the allowed SCN rate or the current maximum SCN limit, the dblink connection cannot be established.

This situation will not rise immediately after the change, but it may happen at any time after June 23, 2019.

5. For 10.2 or older databases, which are not listed in the table?

You should be aware of possible dblink problems in the future and consider upgrading the database or not using dblink with a newer version of the database. If such database links still exist after June 2019, run-time errors may occur during database link operations (as described above), and you need to break these database links at that time.

(based on customer feedback, we are currently evaluating the need and feasibility of providing a patch for 10.2.0.5, and this description will be updated later. )

6. How do I check the details of dblink in the database?

To identify database links, see "View Information about Database links" in the Database Administrator's Guide.

Note that database links from the database can be identified for all database versions through the DBA_DB_LINKS view.

Select from dba_db_links *

For 12.1 and later, you can also learn about incoming database links through the DBA_DB_LINK_SOURCES view.

Select from dba_db_link_sources *

7. Is there a problem connecting two unpatched database links? Or the old version of the database?

Connections involving two unpatched databases or two older versions of dblink are not affected by this change.

8. Will dblink involving patched and unpatched databases stop working immediately after June 2019?

DB links will not become unavailable immediately after June 2019. However, in the case explained in question 4, an error may occur at any point in time after June 2019.

9. What should I do if the dblink connection from the old version of the database to the latest (or patched) version fails after June 2019?

Patch or upgrade the older version of the database to any patch level mentioned in the table.

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

There is no need to take action. All required patches are included in these versions.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.