签到成功

知道了

CNDBA社区CNDBA社区

Oracle 19.28 RU Readme

2025-07-23 09:14 4306 0 转载 Oracle 19c
作者： dave
Skip Headers
Oracle® Database Patch 37957391 - GI Release Update 19.28.0.0.250715
 
 

Oracle® Database

Patch 37957391 - GI Release Update 19.28.0.0.250715

In this document, Oracle Database home refers to Oracle Database Enterprise Edition and Oracle Database Standard Edition.

The GI Release Update 19.28.0.0.250715 includes updates for both the Oracle Grid Infrastructure home and Oracle Database home that can be applied in a rolling fashion.

This patch is Oracle Data Guard Standby-First Installable. See Installing Patch in Oracle Data Guard Standby-First Mode for more information.

The database subpatch 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.

For the latest Bundle Patch with security fixes that should be used on client-only installations, see the "Oracle Database Client" row for your Database version in the "Oracle Database" section of the most recent Critical Patch Update (CPU) Program Patch Availability Document (PAD).

This document is accurate at the time of release. For any changes and additional information regarding GI Release Update 19.28.0.0.250715, see this related document that is available at My Oracle Support (http://support.oracle.com/):

  • Document 19202507.9 Oracle Database 19c RU/RUR Jul 2025 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 Self-Guided Upgrade with Best Practices

This document includes the following sections:

1.1 Patch Information

  • The Oracle Grid Infrastructure patches are cumulative and include the database CPU program security content.

  • 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.

  • This GIRU contains the following CORE DST patches:

    Patch Numbers 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
    37537949 DSTV44 UPDATE - TZDATA2025A

Table 1-1 lists the various configurations and the patch that should be used to patch that configuration.

Table 1-1 Configuration and Database Patch Mapping

Configuration Grid Version Database Versions Patch OPatch Command(1) Comments

Grid home in conjunction with Oracle RAC, Oracle RAC One Node, or single-instance home

19

19

Grid RU/RUR

opatchauto

Grid home and all Oracle homes are patched.

Grid home in conjunction with Oracle RAC, Oracle RAC One Node, or single-instance home

19

19 and prior versions

Grid RU/RUR

opatchauto

Grid home and Oracle home at version 19 are patched.

For Oracle home with a version other than 19, apply the appropriate database RU for that version. For example, apply 19.x RU to database version 19c.

Grid home in conjunction with Oracle RAC, Oracle RAC One Node, or single-instance home

19http://www.cndba.cn/cndba/dave/article/131694

Versions prior to 19

Grid RU/RUR

opatchauto

Grid home alone is patched.

For Oracle home, apply the appropriate database RU for that version. For example, apply 19.x RU to database version 19c.

Oracle Restart home

19

19

Grid RU/RUR

opatchauto

Grid home and all the Oracle homes are patched.

Database single-instance home

NA

19

Database RU/RUR

opatch apply

None.

Database client home

NA

19

Database RU/RUR

opatch apply

None.

Footnote 1 OPatchAuto does not support patching in Oracle Data Guard environments. See Installing Patch in Oracle Data Guard Standby-First Mode for more information.

Table 1-2 lists the various patches by patch number that are installed as part of this bundle patch.

Table 1-2 Patch Numbers Installed as Part of this Bundle Patch

Patch Number Description Applicable Homes

37960098

Database Release Update 19.28.0.0.250715

Only Oracle home for non-Oracle RAC setup. Both Oracle home and Grid home for Oracle RAC setup.

37962946

OCW Release Update 19.28.0.0.250715

Both Oracle home and Grid home.

37962938

ACFS Release Update 19.28.0.0.250715 Footnote 2

Only Grid home.

38124772

Tomcat Release Update 19.0.0.0.0Footnote 2

Only Grid home.

36758186

DBWLM Release Update 19.0.0.0.0Footnote 2

Only Grid home.

Footnote 2 Oracle Automatic Storage Management Cluster File System (Oracle ACFS), Apache Tomcat (TOMCAT), and Database Workload Management (DBWLM) subpatches are not applicable to the HP-UX Itanium and Linux on IBM System z platforms.

2.1 Patch Installation and Deinstallation

2.1.1 Patch Installation Prerequisites

It is highly recommended to take a backup of the Oracle home binaries, the Grid 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?.

You must satisfy the conditions in the following sections before applying the patch:

2.1.1.1 OPatch Utility Information

You must use the OPatch utility version 12.2.0.1.46 or later to apply this patch. Oracle recommends that you use the latest released OPatch 12.2.0.1.xx version for DB 19.0.0.0.0, which is available for download from My Oracle Support patch 6880880 by selecting "OPatch for DB 19.0.0.0.0" from the Select a Release dropdown. It is recommended that you download the OPatch utility and the patch to a shared location in order to access them from any node in the cluster for the patch application on each node.

When patching the Grid home, a shared location on Oracle ACFS only needs to be unmounted on the node where the Grid home is being patched.

The new OPatch utility should be updated in all of the Oracle RAC database homes and the Grid home that are being patched.

For each Oracle RAC database home and the Oracle Grid Infrastructure home that are being patched, as the respective home owner, extract the OPatch utility.

For exact instructions to install OPatch, follow the readme included with the tool download.

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.http://www.cndba.cn/cndba/dave/article/131694

For information about OPatch documentation, including any known issues, see My Oracle Support document 293369.1 Primary Note For OPatch.

2.1.1.2 Validation of Oracle Inventory

Before beginning patch application, check the consistency of inventory information for Grid home and each Oracle home to be patched. Run this command as the respective Oracle home owner to check the consistency:

Step Command 
1.
 
$ <ORACLE_HOME>/OPatch/opatch lsinventory -detail -oh <ORACLE_HOME>

If this command succeeds, it lists the Oracle components that are installed in the home. Save the output so that you have the status prior to the patch application.

If this command fails, contact Oracle Support for assistance.

2.1.1.3 Download and Unzip the Patch

To apply the patch, it must be accessible from all nodes in the Oracle cluster. Download the patch and unzip it to a shared location called the <UNZIPPED_PATCH_LOCATION>. This directory must be empty and cannot be /tmp. Additionally, the directory should have read permission for the ORA_INSTALL group:

Step Command 
1.
 
$ cd <UNZIPPED_PATCH_LOCATION>

Ensure that the directory is empty:

Step Command 
1.
 
$ ls

Unzip the patch as the Grid home owner except for installations that do not have any Grid homes. For installations where this patch is applied to the Oracle home only, the patch must be unzipped as the Oracle home owner:

Step Command 
1.
 
$ unzip p37957391_190000_<platform>.zip

2.1.1.4 Run OPatch Conflict Check

Determine whether any currently installed one-off patches conflict with this patch 37957391 as follows:

  • As the Grid home user:

    Step Command 
    1.
    		 
    % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/37957391/37960098
    		 
    2.
    		 
    % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/37957391/37962946
    		 
    3.
    		 
    % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/37957391/37962938
    		 
    4.
    		 
    % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/37957391/38124772
    		 
    5.
    		 
    % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/37957391/36758186

    Note:

    For HP-UX Itanium and Linux on IBM System z platforms, the last two checks in the previous example do not need to be done.

  • For Oracle home, as home user:

    Step Command 
    1.
    		 
    % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/37957391/37960098
    		 
    2.
    		 
    % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/37957391/37962946

The report will indicate the interim patches that conflict with the patch 37957391 and the interim patches for which patch 37957391 is a superset.

Note:

When OPatch starts, it validates the patch and ensures that there are no conflicts with the software already installed in the ORACLE_HOME. OPatch categorizes conflicts into the following types:

  • Conflicts with a patch already applied to the ORACLE_HOME.

    In this case, stop the patch installation and contact Oracle Support Services.

  • Conflicts with subset patch already applied to the ORACLE_HOME.http://www.cndba.cn/cndba/dave/article/131694

    In this case, continue with the patch installation because as the new patch contains all the fixes from the existing patch in the ORACLE_HOME. And, in any case, the subset patch will automatically be rolled back prior to the installation of the new patch.

2.1.1.5 Run OPatch System Space Check

Check if enough free space is available on the ORACLE_HOME filesystem for the patches to be applied as given below:

  • For Grid Infrastructure home, as home user:

    1. Create file /tmp/patch_list_gihome.txt with the following content:

      Step Command 
      1.
      		 
      % cat /tmp/patch_list_gihome.txt
      		 
      2.
      		 
      <UNZIPPED_PATCH_LOCATION>/37957391/37960098
<UNZIPPED_PATCH_LOCATION>/37957391/37962946
<UNZIPPED_PATCH_LOCATION>/37957391/37962938
<UNZIPPED_PATCH_LOCATION>/37957391/38124772
<UNZIPPED_PATCH_LOCATION>/37957391/36758186

      Note:

      For HP-UX Itanium and Linux on IBM System z platforms, the last two rows in the previous example should not be added to the patch_list_gihome.txt file.

    2. Run the OPatch command to check if enough free space is available in the Grid Infrastructure home:

      Step Command 
      1.
      		 
      % $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_gihome.txt

  • For Oracle home, as home user:

    1. Create file /tmp/patch_list_dbhome.txt with the following content:

      Step Command 
      1.
      		 
      % cat /tmp/patch_list_dbhome.txt
      		 
      2.
      		 
      <UNZIPPED_PATCH_LOCATION>/37957391/37960098
<UNZIPPED_PATCH_LOCATION>/37957391/37962946

    2. Run OPatch command to check if enough free space is available in the Oracle home:

      Step Command 
      1.
      		 
      % $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_dbhome.txt

The command output reports pass and fail messages as per the system space availability:

  • If OPatch reports Prereq "checkSystemSpace" failed., then cleanup the system space as the required amount of space is not available.

  • If OPatch reports Prereq "checkSystemSpace" passed., then no action is needed. Proceed with patch installation.

2.1.2 One-off Patch Conflict Detection and Resolution

The fastest and easiest way to determine whether you have one-off patches in the Oracle home that conflict with the patch, and to get the necessary conflict resolution patches, is as follows:

  •  If you are using the My Oracle Support Patch Plan, then 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.
  •  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.

Note that Oracle proactively generates interim patches for common conflicts.

See My Oracle Support document 1061295.1 Patch Set Updates - One-off 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.

2.1.3 Patch Installation Checks

The Cluster Verification Utility (CVU) command line interface (CLUVFY) may be used to verify the readiness of the Grid_Home to apply the patch. The CLUVFY command may be issued from the configured Grid_Home or from the downloaded latest version of the CVU standalone release (preferred) from My Oracle Support patch 30839369http://www.cndba.cn/cndba/dave/article/131694

Before applying the patch, the readiness of the Grid_Home can be verified by issuing the cluvfy stage -pre patch command from any one of the cluster nodes. This command reports issues, if any are detected, in the Grid_Home which may affect the patching process.

After applying the patch, the sanity of the patching operation can be verified by issuing the cluvfy stage -post patch command from any of the cluster nodes upon completion of the patch application process.

The CLUVFY command line for patching ensures that the Grid_Home can receive the new patch and also ensures that the patch application process completed successfully leaving the home in the correct state.

2.1.4 OPatchAuto Out-of-Place Patching

Out-of-place patching is a mechanism where patching is done by creating a clone of the Oracle home, applying patches on the cloned home, and switching services to the newly created cloned home. This approach to patching reduces unavailability or downtime of the service by separating the step to create the patched clone home from the step of switching services when they must be restarted.

Out-of-place patching documentation can be found at this link:

Oracle OPatch User's Guide

Note: Users can check OPatchAuto help for syntax and examples to execute out-of-place patching.

2.1.5 OPatchAuto

The OPatch utility has automated the patch application for the Oracle Grid Infrastructure (Grid) home and the Oracle RAC database homes. It operates by querying existing configurations and automating the steps required for patching each Oracle RAC database home of same version and the Grid home.

The utility must be executed by an operating system (OS) user with root privileges, and it must be executed on each node in the cluster if the Grid home or Oracle RAC database home is in non-shared storage. The utility can be run in parallel on the cluster nodes except for the first (any) node.

Depending on command line options specified, one invocation of OPatchAuto can patch the Grid home, Oracle RAC database homes, or both Grid and Oracle RAC database homes of the same Oracle release version as the patch. You can also roll back the patch with the same selectivity.

Task Command
Add the directory containing the OPatchAuto to the $PATH environment variable. For example: 
# export PATH=$PATH:<GI_HOME>/OPatch

# cd <UNZIPPED_PATCH_LOCATION>
When using -oh flag: 
# export PATH=$PATH:<oracle_home_path>/OPatch

# cd <UNZIPPED_PATCH_LOCATION>
To patch the Grid home and all Oracle RAC database homes of the same version: 
# opatchauto apply <UNZIPPED_PATCH_LOCATION>/37957391
To patch only the Grid home: 
# opatchauto apply <UNZIPPED_PATCH_LOCATION>/37957391 -oh <GI_HOME>
To patch one or more Oracle RAC database homes: 
# opatchauto apply <UNZIPPED_PATCH_LOCATION>/37957391 -oh <oracle_home1_path>,<oracle_home2_path>
To roll back the patch from the Grid home and each Oracle RAC database home: 
# opatchauto rollback <UNZIPPED_PATCH_LOCATION>/37957391
To roll back the patch from the Grid home: 
# opatchauto rollback <UNZIPPED_PATCH_LOCATION>/37957391 -oh <path to GI home>
To roll back the patch from the Oracle RAC database home: 
# opatchauto rollback <UNZIPPED_PATCH_LOCATION>/37957391 -oh <oracle_home1_path>,<oracle_home2_path>

For more information about opatchauto, see Oracle® OPatch User's Guide.

For detailed patch installation instructions, see Patch Installation.

2.1.6 Patch Installation

The patch instructions will differ based on the configuration of the Grid infrastructure and the Oracle RAC database homes. Patching instructions for Oracle RAC database homes and Grid together are listed below.

The most common configurations are listed as follows:

For other configurations listed below, see My Oracle Support document 2246888.1 Supplemental Readme - Grid Infrastructure Release Update 12.2.0.1.x / 18c / 19c:

  • Grid home is not shared, the Oracle home is not shared, Oracle ACFS may be used.

  • Patching Oracle RAC database homes.

  • Patching Grid home alone.

  • Patching Grid home together with Oracle RAC One Node and clusterware-managed single-instance databases.http://www.cndba.cn/cndba/dave/article/131694

  • Patching Oracle Restart home.

  • Patching a software only Grid home installation or before the Grid home is configured.

Case 1: Oracle RAC, where the Grid home and the Oracle homes are not shared and Oracle ACFS file system is not configured

As root user, execute the following command on each node of the cluster:

Step Command 
1.
 
# <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/37957391
 
2.
 
# cd <UNZIPPED_PATCH_LOCATION>

Case 2: Oracle RAC, where the Grid home is not shared, Oracle home is shared, and Oracle ACFS may be used

Patching instructions:http://www.cndba.cn/cndba/dave/article/131694

  1. From the Oracle home, make sure to stop the Oracle RAC databases running on all nodes. As the Oracle home owner execute:

    Step Command 
    1.
    		 
    $ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>

  2. On the first node, unmount the Oracle ACFS file systems. See My Oracle Support document 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches? for unmounting Oracle ACFS file systems.

  3. On the first node, apply the patch to the Grid home using the opatchauto command. As root user, execute the following command:

    Step Command 
    1.
    		 
    # <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/37957391 -oh <GI_HOME>
    		 
    2.
    		 
    # cd <UNZIPPED_PATCH_LOCATION>

  4. If the message, "A system reboot is recommended before using ACFS" is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS/ADVM/OKS driver.

  5. On the first node, remount Oracle ACFS file systems. See My Oracle Support document 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches? for mounting Oracle ACFS file systems.

  6. On the first node, apply the patch to the Oracle home using the opatchauto command. Since the Oracle home is shared, this operation will patch the Oracle home across the cluster. Note that a USM only patch cannot be applied to a Oracle home. As root user, execute the following command:

    Step Command 
    1.
    		 
    # <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/37957391 -oh <ORACLE_HOME>
    		 
    2.
    		 
    # cd <UNZIPPED_PATCH_LOCATION>

  7. On the first node only, restart the Oracle instance, which you have previously stopped in Step 1. As the Oracle home owner execute:

    Step Command 
    1.
    		 
    $ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename>

  8. On the second (next) node, unmount the Oracle ACFS file systems. See My Oracle Support document 1494652.1 for unmounting Oracle ACFS file systems.

  9. On the second node, apply the patch to Grid home using the opatchauto command. As root user, execute the following command:

    Step Command 
    1.
    		 
    # <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/37957391 -oh <GI_HOME>
    		 
    2.
    		 
    # cd <UNZIPPED_PATCH_LOCATION>

  10. If the message, "A system reboot is recommended before using ACFS" is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS/ADVM/OKS driver.

  11. On the second node, running the opatchauto command in Step 9 will restart the stack.

  12. On the second node, remount Oracle ACFS file systems. See My Oracle Support document 1494652.1 for mounting Oracle ACFS file systems.

  13. On the second node only, restart the Oracle instance, which you have previously stopped in Step 1. As the Oracle home owner execute:

    Step Command 
    1.
    		 
    $ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename>

  14. Repeat steps 8 through 13 for all remaining nodes of the cluster.

Case 3: Single-instance homes not managed by Oracle Grid Infrastructure

Follow these steps:

  1. 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 3039160.1 How do you apply a Patchset, PSU or CPU in a Data Guard Physical Standby configuration.

  2. Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.http://www.cndba.cn/cndba/dave/article/131694

  3. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:

    Step Command 
    1.
    		 
    cd <UNZIPPED_PATCH_LOCATION>/37957391/37960098
    		 
    2.
    		 
    opatch apply

  4. If there are errors, refer to Known Issues.

2.1.7 Installing Patch in Oracle Data Guard Standby-First Mode

For Data Guard Standby-First patching, see My Oracle Support document 1265700.1. For Standby-First patching for Oracle database RU 12.2 and higher, the following points need to be considered:

  1. The database RU subpatch 37960098 must be applied to the Data Guard standby using OPatch.

  2. Datapatch must not be invoked on the Data Guard standby environment to apply post patch SQL actions for the database RU. If datapatch is run on a standby, it will error while trying to call the SYS.DBMS_QOPATCH interface. For more details about this error, see My Oracle Support document 1599479.1.

  3. Datapatch must be invoked on the primary database after all the databases, that is primary and Data Guard, are patched and patch deployment of the database RU is complete for the setup.

2.1.8 Patch Post Installation Instructions

After installing the patch, perform the following actions:

  1. Apply conflict resolution patches as explained in Section 2.1.8.1 .

  2. If you are not using OPatchAuto, then load modified SQL files into the database, as explained in Section 2.1.8.2 .

  3. Upgrade Oracle Recovery Manager Catalog, as explained in Section 2.1.8.3.

  4. Bug fixes that may change an existing optimizer execution plan, as explained in Section 2.1.8.4 .

2.1.8.1 Applying Conflict Resolution Patches

Apply the patch conflict resolution interim patches that were determined to be needed when you performed the steps in One-off Patch Conflict Detection and Resolution.

2.1.8.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 PSU. 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.

  1. For each separate database running on the same shared Oracle home being patched, run the datapatch utility as described in Table 1-3.

    Table 1-3 Steps to Run the Datapatch Utility for Non-CDB or Non-PDB Database Versus Multitenant (CDB/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

    SQL> alter pluggable database all open; Foot 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 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 will then run the necessary apply scripts to load the modified SQL files into the database. An entry will be added to the dba_registry_sqlpatch view reflecting the patch application. In the dba_registry_sqlpatch view, verify 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.

  2. Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/37960098/<unique patch ID> for errors:

    Step Command 
    1.
    		 
    37960098_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.

  3. Any (pluggable) database that has invalid objects after the execution of datapatch should have catcon.pl run to revalidate those objects. For example:

    Step Command 
    1.
    		 
    export PATH=$PATH:$ORACLE_HOME/bin
    		 
    2.
    		 
    cd $ORACLE_HOME/rdbms/admin
    		 
    3.
    		 
    $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin utlrp.sql

2.1.8.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.

Step Command 
1.
 
$ rman catalog username/password@alias
 
2.
 
RMAN> UPGRADE CATALOG;
 
3.
 
RMAN> UPGRADE CATALOG;
 
4.
 
RMAN> EXIT;

2.1.8.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.

2.1.9 Patch Post Installation Instructions for Databases Created or Upgraded After Installation of Patch in the Oracle Home

You must execute the steps in Load Modified SQL Files into the Database for any new or upgraded database.

2.1.10 Patch Deinstallation

Datapatch is run to complete the post-deinstall SQL deployment for the database subpatch. For further details about Datapatch, including Known Issues and workarounds to common problems, see My Oracle Support document 1585822.1 Database 12c Post Patch SQL Automation.

The patch rollback instructions will differ based on the configuration of the Grid infrastructure and the Oracle RAC database homes. Roll Back instructions for Oracle RAC database homes and Grid are listed below.

The most common configurations are listed as follows:

  • Case 1: Oracle RAC, where the Grid home and Oracle homes are not shared and Oracle ACFS file system is not configured

  • Case 2: Oracle RAC, where the Grid home is not shared, Oracle home is shared and Oracle ACFS may be used

  • Case 3: Single-instance homes not managed by Oracle Grid Infrastructure

For other configurations listed below, see My Oracle Support document 2246888.1:

  • Grid home is not shared, the Oracle home is not shared, Oracle ACFS may be used.

  • Rolling back from Oracle RAC database homes.

  • Rolling back from Grid home alone.

  • Rolling back from Grid home together with Oracle RAC One Node and clusterware-managed single-instance databases.http://www.cndba.cn/cndba/dave/article/131694

  • Rolling back the patch from Oracle Restart home.

  • Rolling back the patch from a software only Grid home installation or before the Grid home is configured.

Roll Back the Oracle RAC Database Homes and Grid Together

  • Case 1: Oracle RAC, where the Grid home and Oracle homes are not shared and Oracle ACFS file system is not configured.

    As root user, execute the following command on each node of the cluster.

    Step Command 
    1.
    		 
    # <GI_HOME>/OPatch/opatchauto rollback <UNZIPPED_PATCH_LOCATION>/37957391

    If the message, "A system reboot is recommended before using ACFS" is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS/ADVM/OKS driver.

  • Case 2: Oracle RAC, where the Grid home is not shared, Oracle home is shared and Oracle ACFS may be used.

    1. From the Oracle Oracle home, make sure to stop the Oracle RAC databases running on all nodes. As the Oracle home owner execute:

      Step Command 
      1.
      		 
      $ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>

    2. On the first node, unmount the Oracle ACFS file systems. See My Oracle Support document 1494652.1 for unmounting Oracle ACFS file systems.

    3. On the first node, roll back the patch from the Grid home using the opatchauto command. As root user, execute the following command:

      Step Command 
      1.
      		 
      # <GI_HOME>/OPatch/opatchauto rollback <UNZIPPED_PATCH_LOCATION>/37957391 -oh <GI_HOME>

    4. If the message, "A system reboot is recommended before using ACFS" is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS/ADVM/OKS driver.

    5. On the first node, remount Oracle ACFS file systems. See My Oracle Support document 1494652.1 for mounting Oracle ACFS file systems.

    6. On the first node, roll back the patch to the Oracle home using the opatchauto command. This operation will rollback the patch to the Oracle home across the cluster given that it is a shared Oracle ACFS home. Note that a USM only patch cannot be applied to a Oracle home. As root user, execute the following command:

      Step Command 
      1.
      		 
      # <GI_HOME>/OPatch/opatchauto rollback <UNZIPPED_PATCH_LOCATION>/37957391

    7. On the first node only, restart the Oracle instance, which you have previously stopped in Step 1. As the Oracle home owner execute:

      Step Command 
      1.
      		 
      $ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename>

    8. On the second (next) node, unmount the Oracle ACFS file systems. See My Oracle Support document 1494652.1 for unmounting Oracle ACFS file systems.

    9. On the second node, roll back the patch to Grid home using the opatchauto command. As root user, execute the following command:

      Step Command 
      1.
      		 
      # <GI_HOME>/OPatch/opatchauto rollback <UNZIPPED_PATCH_LOCATION>/37957391

    10. If the message, "A system reboot is recommended before using ACFS" is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS/ADVM/OKS driver.

    11. On the second node, running the opatchauto command in Step 9 will restart the stack.

    12. On the second node, remount Oracle ACFS file systems. See My Oracle Support document 1494652.1 for mounting Oracle ACFS file systems.

    13. On the second node only, restart the Oracle instance, which you have previously stopped in Step 1. As the Oracle home owner execute:

      Step Command 
      1.
      		 
      $ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename>

    14. Repeat Steps 8 through 13 for all remaining nodes of the cluster.

  • Case 3: Single-instance homes not managed by Oracle Grid Infrastructure

    Follow these steps:

    1. Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.

    2. Run the OPatch utility specifying the rollback argument as follows.

      Step Command 
      1.
      		 
      opatch rollback -id 37960098

    3. If there are errors, refer to Known Issues.

2.1.11 Patch Post Deinstallation Instructions

After deinstalling the patch, perform the following actions.

2.1.11.1 Run the Datapatch Utility

Perform the following steps:

  1. For each separate Oracle running on the Oracle home being patched, run the datapatch utility as described in Table 1-4. If this is Oracle RAC, run datapatch on only one instance.

    Table 1-4 Steps to Run the datapatch Utility for Non-CDB or Non-PDB Database Versus Multitenant (CDB/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

    SQL> alter pluggable database all open;Foot 1

    5

    cd $ORACLE_HOME/OPatch

    5http://www.cndba.cn/cndba/dave/article/131694

    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.

  2. Check the following log files in $ORACLE_HOME/sqlpatch/37960098/ for errors:

    Step Command 
    1.
    		 
    37960098_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.

  3. Any (pluggable) database that has invalid objects after the execution of datapatch should have catcon.pl run to revalidate those objects. For example:
    Step Command 
    1.
    		 
    export PATH=$PATH:$ORACLE_HOME/bin
    		 
    2.
    		 
    cd $ORACLE_HOME/rdbms/admin
    		 
    3.
    		 
    $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin utlrp.sql

2.1.11.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.

Step Command 
1.
 
$ rman catalog username/password@alias
 
2.
 
RMAN> UPGRADE CATALOG;
 
3.
 
RMAN> UPGRADE CATALOG;
 
4.
 
RMAN> EXIT;

3.1 Known Issues

For issues documented after the release of this patch, see My Oracle Support document 19202507.9 Oracle Database 19c RU/RUR Jul 2025 Known Issues.

4.1 References

The following documents are references for this patch:

Document 19202507.9 Oracle Database 19c RU/RUR Jul 2025 Known Issues

Document 1919.2 19c Database Upgrade - Self Guided Assistance with Best Practices

Document 2246888.1 Supplemental Readme - Grid Infrastructure Release Update 12.2.0.1.x / 18c / 19c

Document 1494652.1 How to Mount or Unmount ACFS While Applying GI Patches?

Document 1585822.1 Datapatch: Database 12c or later Post Patch SQL Automation

Document 360870.1 Impact of Java SE Security Vulnerabilities on Oracle Database and Fusion Middleware Products

Document 2523221.1 Grid Infrastructure 19 Release Updates and Revisions Bugs Fixed Lists

Document 340978.1 genclntsh: Could not locate $ORACLE_HOME/network/admin/shrept.lst

Document 468959.1 Enterprise Manager Grid Control 10.1 and 10.2 Known Issues

Oracle® OPatch User's Guide

5.1 Manual Steps for Applying or Rolling Back the Patch

See My Oracle Support document 2246888.1 for cases where opatchauto cannot be used.

6.1 Bugs Fixed by This Patch

See My Oracle Support document 2523221.1 for the list of bugs fixed in this patch.

7.1 Documentation Accessibility

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.

Access to Oracle Support

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.

Oracle Database Patch 37957391 - GI Release Update 19.28.0.0.250715http://www.cndba.cn/cndba/dave/article/131694

Copyright © 2025, 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, software documentation, data (as defined in the Federal Acquisition Regulation), 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 embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. 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®, Java, MySQL, and NetSuite are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Inside 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, Epyc, and the AMD 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.

Copyright © 2025, Oracle and/or its affiliates.
用户评论
* 以下用户言论只代表其个人观点，不代表CNDBA社区的观点或立场
dave

dave

关注

人的一生应该是这样度过的：当他回首往事的时候，他不会因为虚度年华而悔恨，也不会因为碌碌无为而羞耻；这样，在临死的时候，他就能够说：“我的整个生命和全部精力，都已经献给世界上最壮丽的事业....."

  • 2297
    原创
  • 3
    翻译
  • 630
    转载
  • 198
    评论
  • 访问：9255514次
  • 积分：4528
  • 等级：核心会员
  • 排名：第1名
精华文章

    达梦数据库运维实战

    Oracle 18c 必须掌握的新特性：管理与实战

    Oracle数据库问题解决方案和故障排除手册
    最新问题
    查看更多+
    热门文章
      热门用户
      推荐用户
        友情链接： CNDBA社区 | openGauss | openEuler | openAnolis | 广告联系: database@ustc.edu
        Copyright © 2016 All Rights Reserved. Powered by CNDBA · 皖ICP备2022006297号-1·

        QQ交流群

        注册联系QQ