APPLIES TO:
Oracle Database - Standard Edition
Oracle Database - Enterprise Edition
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
PURPOSE
The Database patch bundles that were released on October 20, 2020 for Release 19c were:
| Name |
Download Link |
| Database Release Update 19.9.0.0.201020 |
Patch 31771877 |
| Grid Infrastructure Release Update 19.9.0.0.201020 |
Patch 31750108 |
| OJVM Release Update 19.9.0.0.201020 |
Patch 31668882 |
| Database Release Update Revision 19.8.1.0.201020 |
Patch 31666885 |
| Grid Infrastructure Release Update Revision 19.8.1.0.201020 |
Patch 31719890 |
| Database Release Update Revision 19.7.2.0.201020 |
Patch 31667176 |
| Grid Infrastructure Release Update Revision 19.7.2.0.201020 |
Patch 31719845 |
| (there were no OJVM Release Update Revisions for Oct 2020) |
|
| Microsoft Windows 32-Bit & x86-64 Bundle Patch 19.9.0.0.201020 |
Patch 31719903 |
This is the Known Issues note for the patches listed above. These known issues are in addition to the issues listed in the README file for each individual Release Update (RU), Release Update Revision (RUR), or Bundle Patch (BP). These known issues are also in addition to the issues listed for the 19.0.0.0 Base Release in Note 2527930.1, "19.0.0.0 Base Release - Availability and Known Issues ".
SCOPE
This known issues document will be of interest to Database Administrators who are responsible for bundle patching for Oracle Database / Grid Infrastructure / OJVM Release 19c.
DETAILS
My Oracle Support Document ID: 2694903.1
Released: October 20, 2020
This document lists the known issues for Oracle Database / Grid Infrastructure / OJVM Release 19c Oct 2020. These known issues are in addition to the issues listed in the README file for each individual RU, RUR, or BP.
This document includes the following sections:
1 Known Issues
| # |
Applies to |
Issue |
Fix or Workaround |
More Details * |
| 1.1 |
DB RU 19.9.0.0.201020
DB RUR 19.8.1.0.201020
DB RUR 19.7.2.0.201020
|
Opatch utility version 12.2.0.1.19 is sufficient.
The README file for the patch states "you must use the OPatch utility version 12.2.0.1.21 or later to apply this patch." However, the metadata for the patch actually allows for OPatch utility version 12.2.0.1.19 or later to be used.
This Known Issue was first identified in the Jul2020 quarter.
|
While it is Oracle's recommendation that the newest available version of the OPatch utility always be used, this patch will (in this case) install successfully if only "OPatch utility version 12.2.0.1.19 or later" is actually used.
|
|
| 1.2 |
OJVM RU 19.9.0.0.201020 |
'datapatch –verbose' may fail.
In certain situations the Post-install or Post-deinstall actions (datapatch -verbose) may fail for Oracle JavaVM Component 19.8.0.0.201020 Database RU:
Error at line 360: ORA-04068: existing state of packages has been discarded
Error at line 361: ORA-04061: existing state of package body "SYS.DBMS_REGISTRY_SYS" has been discarded
Error at line 363: ORA-04065: not executed, altered or dropped package body
Error at line 365: ORA-06508: PL/SQL: could not find program unit being called:
Error at line 371: ORA-04061: existing state of package body "SYS.DBMS_REGISTRY_SYS" has been discarded
Error at line 373: ORA-04065: not executed, altered or dropped package body
Error at line 375: ORA-06508: PL/SQL: could not find program unit being called
This Known Issue was first identified in the Apr2019 quarter.
|
When this occurs, it is simply a consequence of multiple package state changes that are performed within the "datapatch" process. The error is retriable and therefore the work around is simply to run 'datapatch –verbose' a second time.
A fix for this will be included into a future quarterly Oracle JavaVM Component Database RU.
|
|
| 1.3 |
OJVM RU 19.9.0.0.201020 |
'datapatch –verbose' may fail.
In certain situations the Post-install or Post-deinstall actions (datapatch -verbose) may fail for Oracle JavaVM Component 19.8.0.0.201020 Database RU:
Error at line 162844: script md/admin/sdoloadj.sql
ORA-29548: Java system class reported: release of Java system classes in the database (19.0.0.0.0 1.8) does not match that of the oracle executable (19.0.0.0.201020 1.8)
Error at line 162854: script md/admin/sdoloadj.sql
ORA-29548: Java system class reported: release of Java system classes in the database (19.0.0.0.0 1.8) does not match that of the oracle executable (19.0.0.0.201020 1.8)
Error at line 162864: script md/admin/sdoloadj.sql
ORA-29548: Java system class reported: release of Java system classes in the database (19.0.0.0.0 1.8) does not match that of the oracle executable (19.0.0.0.201020 1.8)
Error at line 162878: script md/admin/sdoloadj.sql
(continues)
This Known Issue was first identified in the Apr2020 quarter.
|
When this occurs, it is simply a collateral symptom from Known Issue 1.2. Since the OJVM RU post-install failed in Known Issue 1.2, this subsequent use of Java in the CDB$ROOT will also fail. The error is retriable and therefore the work around is simply to run 'datapatch –verbose' a second time.
A fix for this will be included into a future quarterly Oracle JavaVM Component Database RU.
|
|
| 1.4 |
All except MS-Win BP |
The following error stack may be logged into the Database alert log while datapatch is running:
ORA-12012: error on auto execute of job "SYS"."ORA$AT_SQ_SQL_SW_6"
ORA-13767: End snapshot ID must be greater than begin snapshot ID.
ORA-06512: at "SYS.DBMS_SPM_INTERNAL", line 4589
ORA-06512: at "SYS.DBMS_SPM_INTERNAL", line 5962
ORA-06512: at "SYS.DBMS_SQLTUNE", line 8636
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.DBMS_SQLTUNE_UTIL2", line 90
ORA-06512: at "SYS.DBMS_SQLTUNE", line 5260
ORA-06512: at "SYS.DBMS_SQLTUNE", line 8556
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_SPM_INTERNAL", line 5708
ORA-06512: at "SYS.DBMS_SPM_INTERNAL", line 4552
ORA-06512: at "SYS.DBMS_SPM", line 2824
ORA-06512: at "SYS.PRVT_ADVISOR", line 3546
ORA-06512: at "SYS.PRVT_ADVISOR", line 932
ORA-06512: at "SYS.DBMS_SQLTUNE_INTERNAL", line 14140
ORA-06512: at "SYS.DBMS_SQLTUNE_INTERNAL", line 14167
ORA-06512: at "SYS.WRI$_ADV_SPM_EVOLVE", line 7
ORA-06512: at "SYS.PRVT_ADVISOR", line 915
ORA-06512: at "SYS.PRVT_ADVISOR", line 3451
ORA-06512: at "SYS.DBMS_ADVISOR", line 276
ORA-06512: at "SYS.DBMS_SPM", line
This Known Issue was first identified in the Jan2020 quarter.
|
This is an ignorable error stack, and occurs when dbms_sqltune APIs are not able to perform properly because there is only one snapshot in the AWR. When sqltune API validates the input [begin_snap_id, end_snap_id] range, if the begin_snap_id = end_snap_id, it considers it as a invalid input. This can occur for a newly created database, when there is just one snapshot created.
|
|
| 1.5 |
All except MS-Win BP |
The following errors may be logged into the Container Database alert log while datapatch is running:
ORA-65221 signalled during: alter pluggable database application APP$CDB$SYSTEM begin install '1.0'...
ORA-65214 signalled during: alter pluggable database application APP$CDB$SYSTEM end install '1.0'...
This Known Issue was first identified in the Apr2020 quarter.
|
These errors are ignorable.
|
|
| 1.6 |
DB RU 19.9.0.0.201020 |
In an Oracle Client Home where the 19.7.0 DB RU (Patch 30869156) is already installed, applying the 19.9.0 DB RU (Patch 31281355) fails:
Verifying environment and performing prerequisite checks...
Skip patch 31281355 from list of patches to apply: This patch is not needed.
After skipping patches with missing components, there are no patches to apply.
OPatch Session completed with warnings.
This Known Issue was first identified in the Jul2020 quarter.
|
A workaround is presented in Note 2701095.1.
|
Note 2701095.1 |
| 1.7 |
DB RU 19.9.0.0.201020
DB RUR 19.8.1.0.201020
|
Since the fix of bug 29817547 is in place for the two listed patch bundles, the lob data from an affected block may not be able to be read. When this occurs, errors seen can be ORA-22924 or ORA-600 [kdliReadPos]. If there is an instance crash, then roll forward (crash recovery or instance recovery) may fail with an error ORA-600 [kcratr_scan_lostwrt]. If there is a standby database, then recovery may fail with either ORA-00752 (if db_lost_write_protect is set) or ORA-00600 [3020]. |
If the database does not open at this point, the workaround is to mark the block as soft corrupt using recover allow 1 corruption.
To prevent the problem, Oracle recommends that you apply interim one-off Patch 32010707 to correct this problem(s) in the RUs / RURs indicated in the second column of this row.
|
Note 32010707.8 |
| 1.8 |
DB RUR 19.7.2.0.201020 |
The assert [krcrgne_badkeepscn] should trigger a global resource dump and the trace accompanying KRCRGNE_BADKEEPSCN says "krcrgne: dump resource ..". However, but there actually is no dump. It is missing because the call to actually perform the global dump is missing from the code.
This Known Issue was first identified in the Oct2020 quarter.
|
To prevent the problem, Oracle recommends that you apply interim one-off Patch 30253705 to correct this problem(s) in the RUs / RURs indicated in the second column of this row.
|
Note 30253705.8 |
* For more details about each problem, refer to the "Description" section of the My Oracle Support (MOS) NOTE indicated. For more details about additional bundles that first include the fix for this issue, refer to the "Fixed" section of the My Oracle Support (MOS) NOTE indicated.
2 Modification History
| Date |
Modification |
| October 20, 2020 |
Released |
| December 01, 2020 |
Corrected out-of date "Applies To" column values.
Added Known Issue 1.7 |
| December 17, 2020 |
Added Known Issue 1.8 |
Copyright © 2006, 2020, Oracle and/or its affiliates.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.
REFERENCES
NOTE:1369107.1 - ACFS Support On OS Platforms (Certification Matrix).
|
