|
Patch 36582781 - Database Release Update 19.24.0.0.240716
This document is accurate at the time of release. For any changes and additional information regarding Database Release Update 19.24.0.0.240716, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
- Document 19202407.9 Oracle DB/GI/OJVM Update/Revision R19 Jul 2024 Known Issues
- Document 555.1 Oracle Database 19c Important Recommended One-off Patches
- Document 888.1 Primary Note for Database Proactive Patch Program
- Document 1919.2 19c Database Upgrade - Self Guided Assistance with Best Practices
This document includes the following sections:
- Section 1, "Patch Information"
- Section 2, "Prerequisites"
- Section 3, "Installation"
- Section 4, "Deinstallation"
- Section 5, "Known Issues"
- Section 6, "References"
- Section 7, "Bugs Fixed by This Patch"
- Section 8, "Documentation Accessibility"
1 Patch Information
- Database Release Update 19.24.0.0.240716 patches are cumulative. That is, the content of all previous Database bundles is included in the latest Database bundle patch.
- To install the Database Release Update 19.24.0.0.240716 patch, the Oracle home must have Oracle Database release 19c installed.
- This patch is Oracle RAC Rolling Installable.
- This patch is Database Vault installable. Review My Oracle Support document 1195205.1 Primary Note For Oracle Database Vault for details on how to apply this patch to a Database Vault environment.
- This patch is Data Guard Standby-First Installable. See My Oracle Support document 1265700.1 Oracle Patch Assurance - Data Guard Standby-First Patch Apply for details on how to remove risk and reduce downtime when applying this patch.
- This patch includes the JDK fixes released in the prior cycle and will update the JDK in the Oracle home. For the most recent JDK fixes, a separate patch is available and needs to be installed in addition to this patch. Refer to My Oracle Support document 888.1 Primary Note for Database Proactive Patch Program for the JDK patch number.
- Beginning with 19.21 Oct2023 RU, UTL_URI.ESCAPE function is now compliant with RFC 3896 and will treat "#" as a reserved character. See My Oracle Support Note 2981395.1 for more details.
- Beginning with 19.22 Jan2024 RU, the 19c database is now certified on Oracle Linux 9.x and RHEL9.x.
- Beginning with 19.18 Jan2023 RU, the DBRU contains the CORE DST Time Zone patches. Applying this Release Update (RU) does not change the DST version in any of your databases. The DST patches are only copied into $ORACLE_HOME/oracore/zoneinfo and no DST upgrade is performed. You can decide to upgrade the DST version in your database to a newer DST version independently of applying the RU at any time. Be aware that this incurs downtime.
This DBRU contains the following CORE DST patches:
- 28852325 - DSTV33 UPDATE - TZDATA2018G
- 29997937 - DSTV34 UPDATE - TZDATA2019B
- 31335037 - DSTV35 UPDATE - TZDATA2020A
- 32327201 - DSTV36 UPDATE - TZDATA2020E
- 33613829 - DSTV37 UPDATE - TZDATA2021E
- 34006614 - DSTV38 UPDATE - TZDATA2022A
- 34533061 - DSTV39 UPDATE - TZDATA2022C
- 34698179 - DSTV40 UPDATE - TZDATA2022E
- 35099667 - DSTV41 UPDATE - TZDATA2022G
- 35220732 - DSTV42 UPDATE - TZDATA2023C
- 36260493 - DSTV43 UPDATE - TZDATA2024A
If you plan to adjust the DST version of your databases, Oracle recommends adjusting it to the latest available DST version. Then follow the instructions in the Oracle 19c Oracle Database Upgrade Guide.
For more information on various DST patch releases, refer to My Oracle Support document 412160.1 Primary Note DST FAQ: Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches.
- Any new or changed database initialization parameters that might be included into a quarterly patch bundle would be documented in the Oracle Database Reference manual section on initialization parameters. For Oracle Database 19c, refer to Oracle Database Reference.
- For the latest Update with Security Fixes that should be used on Client-Only installations, refer to the Critical Patch Update (CPU) Program Patch Availability Document (PAD) section on the Oracle Database, for the cycle in which you are interested.
- Applying Database Release Update Database Release Update 19.24.0.0.240716 with Oracle JavaVM 19.x Updates
- For customers who want to install both patches together during a single downtime window, follow one of the Patching Options listed in the My Oracle Support document:
- 1929745.1 - Oracle Recommended Patches - "Oracle JavaVM Component Database PSU and Update" (OJVM PSU and OJVM Update) Patches.
- The Oracle JavaVM 19.x Release Update is available as a separate patch. That separate patch has some additional requirements if it is to be installed in a RAC Rolling fashion, as detailed in My Oracle Support document:
- 2217053.1 - RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU/RU" (OJVM PSU/RU) Patches.
It is highly recommended to take a backup of the Oracle_Home binaries and Central Inventory prior to applying patches. For further information, refer to My Oracle Support document 565017.1 How to Perform ORACLE_HOME Backup?.
This section includes the following section:
You must use the OPatch utility version 12.2.0.1.42 or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 12.2, which is available for download from My Oracle Support patch 6880880 by selecting ARU link for the 12.2.0.1.0 OPatch release. It is recommended that you download the OPatch utility and the patch in a shared location to be able to access them from any node in the cluster for the patch application on each node.
When patching the GI home, a shared locaton on Oracle ACFS only needs to be unmounted on the node where the GI home is being patched.
The new OPatch utility should be updated in all of the Oracle RAC database homes and the GI home that are being patched.
For each Oracle RAC database home and the GI home that are being patched, as the home owner, extract the OPatch utility.
For exact instructions to install OPatch, follow the OPatch readme.
A new feature has been added to OPatch to increase performance by deleting inactive patches. See My Oracle Support document 2942102.1 OPatch 12.2.0.1.37+ Introduces a New Feature to Delete Inactive Patches in the ORACLE_HOME/.patch_storage directory.
For information about OPatch documentation, including any known issues, see My Oracle Support document 293369.1 Primary Note For OPatch.
These instructions are for all Oracle Database installations.
- Section 3.1, "Patch Pre-Installation Instructions"
- Section 3.2, "Patch Installation Instructions"
- Section 3.3, "Patch Post-Installation Instructions"
- Section 3.4, "Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of this patch in the Oracle Home"
3.1 Patch Pre-Installation Instructions
Before you install Database Release Update 19.24.0.0.240716, perform the following actions to check the environment and to detect and resolve any interim patch conflicts.
3.1.1 Environments with Grid Infrastructure
This patch is not to be installed to an environment that has a Grid Infrastructure home. Refer to the following My Oracle Support document 888.1 to determine the appropriate Grid infrastructure patch to be installed.
- Ensure that the $PATH definition has the following executables: make, ar, ld, and nm.
The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin, in which case you can set your PATH definition as follows:
export PATH=$PATH:/usr/ccs/bin
3.1.3 Interim Patch Conflict Detection and Resolution
The fastest and easiest way to determine whether you have interim patches in the Oracle home that conflict with Database Release Update 19.24.0.0.240716, and to get the necessary conflict resolution patches, is to use the Patch Recommendations and Patch Plans features on the Patches & Updates tab in My Oracle Support. These features work in conjunction with the My Oracle Support Configuration Manager. Recorded training sessions on these features can be found in My Oracle Support document 603505.2 My Oracle Support How-to Video Training Series.
However, if you are not using My Oracle Support Patch Plans, the My Oracle Support Conflict Checker tool enables you to upload an OPatch inventory and check the patches that you want to apply to your environment for conflicts.
If no conflicts are found, you can download the patches. If conflicts are found, the tool finds an existing resolution to download. If no resolution is found, it will automatically request a resolution, which you can monitor in the Plans and Patch Requests region of the Patches & Updates tab.
For more information, see Knowledge Document 1091294.1, How to Use My Oracle Support Conflict Checker Tool for Patches Installed with OPatch.
Or, use the following steps to manually discover conflicts and resolutions:
- Determine whether any currently installed interim patches conflict with the patch being installed, 36582781:
- unzip p36582781_<version>_<platform>.zip
- cd 36582781
- opatch prereq CheckConflictAgainstOHWithDetail -ph ./
- The report indicates the patches that conflict and the patches that are a superset.
- Use My Oracle Support document 1321267.1 Database Patch Conflict Resolution to determine, for each conflicting patch, whether a conflict resolution patch is already available, and if you need to request a new conflict resolution patch or if the conflict may be ignored.
- When all the interim patches that you have requested are available at My Oracle Support, proceed with Section 3.2, "Patch Installation Instructions".
3.2 Patch Installation Instructions
Follow these steps:
- If you are using a Data Guard Physical Standby database, you must install this patch on both the primary database and the physical standby database, as described by My Oracle Support document 278641.1 How do you apply a Patchset, PSU or CPU in a Data Guard Physical Standby configuration.
- If this is an Oracle RAC environment, install this patch using the OPatch rolling (no downtime) installation method as this patch is rolling RAC installable. Refer to My Oracle Support document 244241.1 Rolling Patch - OPatch Support for RAC.
- If this is not a RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
- Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
- unzip -d <PATCH_TOP_DIR> p36582781_<version>_<platform>.zip
- cd <PATCH_TOP_DIR> 36582781
- opatch apply
- If there are errors, refer to Section 5, "Known Issues".
3.3 Patch Post-Installation Instructions
On Oracle Database server, after installing the patch, perform the following actions. This is not required on Oracle Database client.
3.3.1 Apply Conflict Resolution Patches
Apply the patch conflict resolution interim patches that were determined to be needed when you performed the steps in Section 3.1.4, "Interim Patch Conflict Detection and Resolution".
3.3.2 Load Modified SQL Files into the Database
The following steps load modified SQL files into the database. For an Oracle RAC environment, perform these steps on only one node.
Datapatch is run to complete the post-install SQL deployment for the patch being installed. For further details about Datapatch, including Known Issues and workarounds to common problems, see My Oracle Support document 1585822.1 Datapatch: Database 12c or later Post Patch SQL Automation and My Oracle Support document 2680521.1 Datapatch User Guide.
- For each separate database running on the same shared Oracle home being patched, run the datapatch utility as described in Table 2.
Table 2 Steps to Run the Datapatch Utility for Non-CDB or Non-PDB Database Versus Multitenant (CDB or PDB) Oracle Database
| Steps | Non-CDB or Non-PDB Database | Steps | Multitenant (CDB/PDB) Oracle Database |
| 1 | sqlplus /nolog | 1 | sqlplus /nolog |
| 2 | SQL> Connect / as sysdba | 2 | SQL> Connect / as sysdba |
| 3 | SQL> startup | 3 | SQL> startup |
| 4 | SQL> quit | 4 | |
| 5 | cd $ORACLE_HOME/OPatch | 5 | SQL> quit |
| 6 | ./datapatch -sanity_checks (optional) | 6 | cd $ORACLE_HOME/OPatch |
| 7 | ./datapatch -verbose | 7 | ./datapatch -sanity_checks (optional) |
| 8 | ./datapatch -verbose |
- Footnote 1 It is recommended the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open ) could be substituted to only open certain PDBs in the single or multitenant database. Doing so will result in the Post Install step only being run on the CDB and opened PDB's. To update a pluggable database at a later date (skipped or newly plugged in), open the database using the alter pluggable database command mentioned previously and rerun the datapatch utility.
- See My Oracle Support document 1935365.1 Multitenant Unplug/Plug Best Practices for more information about the procedure for unplugging/plugging with different patch releases (in both directions).
- Recommended: The datapatch -sanity_checks optional step runs a series of environment and database checks to validate if conditions are optimal for patching. Results are shown on screen with severity and potential actions to take.
- For more information, refer to My Oracle Support document 2680521.1 Datapatch User Guide for additional information and actions. Oracle highly recommends that you perform this step.
- The datapatch utility runs the necessary apply scripts to load the modified SQL files into the database. An entry is added to the dba_registry_sqlpatch view reflecting the patch application. In the dba_registry_sqlpatch view, verify that the status for the APPLY is SUCCESS.
- For any other status, refer to My Oracle Support document 2335899.2 Troubleshooting Assistant: 12c Datapatch Issues for additional information and actions.
- Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/36582781/<unique patch ID> for errors:
- 36582781_apply_<database SID>_<CDB name>_<timestamp>.log
where database SID is the database SID, CDB name is the name of the multitenant container database, and timestamp is of the form YYYYMMMDD_HH_MM_SS.
- Any (pluggable) database that has invalid objects after the execution of datapatch should have catcon.pl run to revalidate those objects. For example:
- export PATH=$PATH:$ORACLE_HOME/bin
- cd $ORACLE_HOME/rdbms/admin
$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin utlrp.sql
3.3.3 Upgrade Oracle Recovery Manager Catalog
If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it. The UPGRADE CATALOG command must be entered twice to confirm the upgrade.
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
RMAN> UPGRADE CATALOG;
RMAN> EXIT;
3.3.4 Bug Fixes That May Change an Existing Optimizer Execution Plan
At the successful conclusion of the patching event, none of the database bug fixes that may change an existing optimizer execution plan are delivered with the bug fix disabled by default. The status of any module bug fixes (which cause an execution plan change) that were in an enabled state prior to starting the patching event are preserved, but no new module bug fixes (which cause an execution plan change) are activated automatically.
Details on this, including the commands to explicitly enable such bug fixes are present in My Oracle Support document 2147007.1 Managing "installed but disabled" bug fixes in Database Release Updates using DBMS_OPTIM_BUNDLE.
3.3.5 Update Permissions for extjob
Database release update patch installation involves relinking of libraries and executables to be updated. This can sometimes result in permissions changing and needing to be updated. Execute the following as root user:
# chown root $ORACLE_HOME/bin/extjob
# chmod 4750 $ORACLE_HOME/bin/extjob
3.4 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of this patch in the Oracle Home
On Oracle Database server, you must execute the steps in Section 3.3.2, "Load Modified SQL Files into the Database" for any new database. There are no actions required for databases that have been upgraded. This is not required on Oracle Database client.
These instructions apply if you need to deinstall the patch.
- Section 4.1, "Patch Deinstallation Instructions for a Non-RAC Environment"
- Section 4.2, "Patch Post-Deinstallation Instructions for a Non-RAC Environment"
- Section 4.3, "Patch Deinstallation Instructions for Oracle RAC Environment"
- Section 4.4, "Patch Post-Deinstallation Instructions for Oracle RAC Environment"
4.1 Patch Deinstallation Instructions for a Non-RAC Environment
Follow these steps:
- Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
- Run the OPatch utility specifying the rollback argument as follows.
- opatch rollback -id 36582781
- If there are errors, refer to Section 5, "Known Issues".
4.2 Patch Post-Deinstallation Instructions for a Non-RAC Environment
On Oracle Database server, after deinstalling the patch, perform the following actions. This is not required on Oracle Database client.
- Rollback SQL changes from the the Database, as explained in Section 4.2.1.
- Upgrade Oracle Recovery Manager Catalog, as explained in Section 4.2.2.
4.2.1 Load Modified SQL Files into the Database
Datapatch is run to complete the post-deinstall SQL deployment for the patch being deinstalled. For further details about Datapatch, including Known Issues and workarounds to common problems, see My Oracle Support document 1585822.1 Datapatch: Database 12c or later Post Patch SQL Automation and My Oracle Support document 2680521.1 Datapatch User Guide.
Follow these steps:
- For each separate database running on the same shared Oracle home being patched, run the datapatch utility as described in Table 3. If this is Oracle RAC, run datapatch on only one instance.
Table 3 Steps to Run the datapatch Utility for Non-CDB or Non-PDB Database Versus Multitenant (CDB or PDB) Database
| Steps | Non-CDB or Non-PDB Database | Steps | Multitenant (CDB/PDB) Oracle Database |
| 1 | sqlplus /nolog | 1 | sqlplus /nolog |
| 2 | SQL> Connect / as sysdba | 2 | SQL> Connect / as sysdba |
| 3 | SQL> startup | 3 | SQL> startup |
| 4 | SQL> quit | 4 | SQL> alter pluggable database all openFoot 1 |
| 5 | cd $ORACLE_HOME/OPatch | 5 | SQL> quit |
| 6 | ./datapatch -sanity_checks (optional) | 6 | cd $ORACLE_HOME/OPatch |
| 7 | ./datapatch -verbose | 7 | ./datapatch -sanity_checks (optional) |
| 8 | ./datapatch -verbose |
- Footnote 1 It is recommended the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open ) could be substituted to only open certain PDBs in the single/multitenant database. Doing so will result in the Post Install step only being run on the CDB and opened PDB's. To update a pluggable database at a later date (skipped or newly plugged in), open the database using the alter pluggable database command mentioned previously and rerun the datapatch utility.
- See My Oracle Support document 1935365.1 Multitenant Unplug/Plug Best Practices for more information about the procedure for unplugging/plugging with different patch releases (in both directions).
- Recommended: The datapatch -sanity_checks optional step runs a series of environment and database checks to validate if conditions are optimal for patching. Results are shown on screen with severity and potential actions to take.
- For more information, refer to the My Oracle Support document 2680521.1 Datapatch User Guide for additional information and actions. Oracle highly recommends that you perform this step.
- The datapatch utility runs the necessary rollback scripts. An entry is added to the dba_registry_sqlpatch view reflecting the patch application. In the dba_registry_sqlpatch view, verify the Status for the ROLLBACK is SUCCESS.
- For any other status, refer to My Oracle Support document 2335899.2 Troubleshooting Assistant: 12c Datapatch Issues for additional information and actions.
- Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/36582781/<unique patch ID> for errors:
- 36582781_rollback_<database SID>_<CDB name>_<timestamp>.log
where database SID is the database SID, CDB name is the name of the multitenant container database, and timestamp is of the form YYYYMMMDD_HH_MM_SS.
- Any (pluggable) database that has invalid objects after the execution of datapatch should have catcon.pl run to revalidate those objects. For example:
- cd $ORACLE_HOME/rdbms/admin
$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin utlrp.sql
4.2.2 Upgrade Oracle Recovery Manager Catalog
If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it. The UPGRADE CATALOG command must be entered twice to confirm the upgrade.
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
RMAN> UPGRADE CATALOG;
RMAN> EXIT;
4.3 Patch Deinstallation Instructions for Oracle RAC Environment
Patch deinstallation instructions for Oracle RAC includes these environments:
Follow these steps for each node in the cluster, one node at a time.
- Shut down the instance on the node.
- Run the OPatch utility specifying the rollback argument as follows.
- opatch rollback -id 36582781
If there are errors, refer to Section 5, "Known Issues".
- Start the instance on the node as follows:
- srvctl start instance
4.4 Patch Post-Deinstallation Instructions for Oracle RAC Environment
On Oracle Database server, follow the instructions listed in Section Section 4.2, "Patch Post-Deinstallation Instructions for a Non-RAC Environment" only on the node for which the steps in Section 3.3.2, "Load Modified SQL Files into the Database" were executed during the patch application. This is not required on Oracle Database client.
All other instances can be started and accessed as usual while you are executing the deinstallation steps.
For information about OPatch issues, see My Oracle Support document 293369.1 Primary Note For OPatch.
For issues documented after the release of this patch, see My Oracle Support document 19202407.9 Oracle DB/GI/OJVM Update/Revision R19 Jul 2024 Known Issues
Other issues are as follows.
The following ignorable errors may be encountered while running the datapatch/catbundle.sql script or its rollback script:
ORA-00942: table or view does not exist
ORA-00955: name is already used by an existing object
ORA-01430: column being added already exists in table
ORA-01432: public synonym to be dropped does not exist
ORA-01434: private synonym to be dropped does not exist
ORA-01435: user does not exist
ORA-01917: user or role 'XDB' does not exist
ORA-01920: user name '<user-name>' conflicts with another user or role name
ORA-01921: role name '<role name>' conflicts with another user or role name
ORA-01927: cannot REVOKE privileges you did not grant
ORA-01952: system privileges not granted to 'WKSYS'
ORA-02289: sequence does not exist
ORA-02303: cannot drop or replace a type with type or table dependents
ORA-02443: Cannot drop constraint - nonexistent constraint
ORA-04043: object <object-name> does not exist
ORA-06512: at line <line number>. If this error follow any of above errors, then can be safely ignored.
ORA-14452: attempt to create, alter or drop an index on temporary table already in use
ORA-29809: cannot drop an operator with dependent objects
ORA-29830: operator does not exist
ORA-29832: cannot drop or replace an indextype with dependent indexes
ORA-29844: duplicate operator name specified
ORA-29931: specified association does not exist
The following documents are references for this patch.
Document 36582781.8 Database Release Update 19.24.0.0.240716
Document 1919.2 19c Database Upgrade - Self Guided Assistance with Best Practices
Document 888.1 Primary Note for Database Proactive Patch Program
Document 1585822.1 Datapatch: Database 12c or later Post Patch SQL Automation
Document 293369.1 Primary Note for OPatch
Document 412160.1 Primary Note DST FAQ: Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File Patches
Document 1321267.1 Database Patch Conflict Resolution
Document 2523220.1 Database 19 Release Updates and Revisions Bugs Fixed Lists
Document 1561792.2 Troubleshooting Assistant: Patching Oracle Database/Client
See My Oracle Support document 2523220.1 Database 19 Release Updates and Revisions Bugs Fixed Lists for the list of bugs fixed in this patch.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id-docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Patch 36582781 - Database Release Update 19.24.0.0.240716
