oracle rac 19.3安装补丁19.19

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

• Note 19202304.9 Oracle Database 19c RU/RUR Apr 2023 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
• 2.1 Patch Installation and Deinstallation
• 3.1 Known Issues
• 4.1 References
• 5.1 Manual Steps for Applying or Rolling Back the Patch
• 6.1 Bugs Fixed by This Patch
• 7.1 Documentation Accessibility

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

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

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.

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.

This topic includes the following sections:

• 2.1.1 Patch Installation Prerequisites
• 2.1.2 One-off Patch Conflict Detection and Resolution
• 2.1.3 Patch Installation Checks
• 2.1.4 OPatchAuto Out-of-Place Patching
• 2.1.5 OPatchAuto
• 2.1.6 Patch Installation
• 2.1.7 Installing Patch in Oracle Data Guard Standby-First Mode
• 2.1.8 Patch Post Installation Instructions
• 2.1.9 Patch Post Installation Instructions for Databases Created or Upgraded After Installation of Patch in the Oracle Home
• 2.1.10 Patch Deinstallation
• 2.1.11 Patch Post Deinstallation Instructions

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 Note 565017.1.

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

• 2.1.1.1 OPatch Utility Information
• 2.1.1.2 Validation of Oracle Inventory
• 2.1.1.3 Download and Unzip the Patch
• 2.1.1.4 Run OPatch Conflict Check
• 2.1.1.5 Run OPatch System Space Check

You must use the OPatch utility version 12.2.0.1.36 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 note 6880880 by selecting the ARU link for the 12.2.0.1.0 OPatch release. 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.

For information about OPatch documentation, including any known issues, see My Oracle Support note 293369.1 OPatch documentation list.

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:

<span style="color:#000000"><span style="background-color:#ffffff">$ <ORACLE_HOME>/OPatch/opatch lsinventory -detail -oh <ORACLE_HOME>
</span></span>

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 Services for assistance.

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:

<span style="color:#000000"><span style="background-color:#ffffff">$ cd <UNZIPPED_PATCH_LOCATION>
</span></span>

Ensure that the directory is empty:

<span style="color:#000000"><span style="background-color:#ffffff">$ ls
</span></span>

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:

<span style="color:#000000"><span style="background-color:#ffffff">$ unzip p35037840_190000_<platform>.zip
</span></span>

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

• As the Grid home user:     ###grid用户执行，检查patch的完整性

  <span style="color:#000000"><span style="background-color:#ffffff">% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/35037840/35042068
  
  % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/35037840/35050331
  
  % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/35037840/35050325
  
  % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/35037840/35107512
  
  % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/35037840/33575402
  
  				</span></span>

  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:

  <span style="color:#000000"><span style="background-color:#ffffff">% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/35037840/35042068
  % $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/35037840/35050331
  </span></span>

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

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:

     <span style="color:#000000"><span style="background-color:#ffffff">% cat /tmp/patch_list_gihome.txt
     
     <UNZIPPED_PATCH_LOCATION>/35037840/35042068
     <UNZIPPED_PATCH_LOCATION>/35037840/35050331
     <UNZIPPED_PATCH_LOCATION>/35037840/35050325
     <UNZIPPED_PATCH_LOCATION>/35037840/35107512
     <UNZIPPED_PATCH_LOCATION>/35037840/33575402
     </span></span>

     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:

     <span style="color:#000000"><span style="background-color:#ffffff">% $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_gihome.txt
     </span></span>

• For Oracle home, as home user:
  1. Create file /tmp/patch_list_dbhome.txt with the following content:

     <span style="color:#000000"><span style="background-color:#ffffff">% cat /tmp/patch_list_dbhome.txt
     <UNZIPPED_PATCH_LOCATION>/35037840/35042068
     <UNZIPPED_PATCH_LOCATION>/35037840/35050331
     </span></span>

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

     <span style="color:#000000"><span style="background-color:#ffffff">% $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_dbhome.txt
     </span></span>

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.

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 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 note 603505.1.

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 the My Oracle Support Conflict Checker Tool.

Or, manually determine whether any currently installed one-off patches conflict with the PSU patch as follows:

• In the unzipped directory as described in Download and Unzip the Patch.
• The following commands check for conflicts in both the 19c Grid home and the 19c DB homes.
  • In case you are applying the patch, run this command:   ##冲突检查，使用root用户执行

    <span style="color:#000000"><span style="background-color:#ffffff">#GRID_HOME/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/35037840 -analyze
    </span></span>

  • In case you are rolling back the patch, run this command:

    <span style="color:#000000"><span style="background-color:#ffffff">#GRID_HOME/OPatch/opatchauto rollback <UNZIPPED_PATCH_LOCATION>/35037840 -analyze
    </span></span>

Note that Oracle proactively generates interim patches for common conflicts.

See My Oracle Support note 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.

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 30839369

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.

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:

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

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.

Add the directory containing the OPatchAuto to the $PATH environment variable. For example:##设置环境变量，下面都是用root用户执行

<span style="color:#000000"><span style="background-color:#ffffff"># export PATH=$PATH:<GI_HOME>/OPatch
</span></span>

Or, when using -oh flag:

<span style="color:#000000"><span style="background-color:#ffffff"># export PATH=$PATH:<oracle_home_path>/OPatch
</span></span>

To patch the Grid home and all Oracle RAC database homes of the same version: ###升级GRID和DB，这一步比较慢，我这边4U服务器144核心512内存实测花了20分钟

<span style="color:#000000"><span style="background-color:#ffffff"># opatchauto apply <UNZIPPED_PATCH_LOCATION>/35037840
</span></span>

To patch only the Grid home:   ###只升级GRID

<span style="color:#000000"><span style="background-color:#ffffff"># opatchauto apply <UNZIPPED_PATCH_LOCATION>/35037840 -oh <GI_HOME>
</span></span>

To patch one or more Oracle RAC database homes:  ###只升级DB

<span style="color:#000000"><span style="background-color:#ffffff"># opatchauto apply <UNZIPPED_PATCH_LOCATION>/35037840 -oh <oracle_home1_path>,<oracle_home2_path>
</span></span>

To roll back the patch from the Grid home and each Oracle RAC database home:

<span style="color:#000000"><span style="background-color:#ffffff"># opatchauto rollback <UNZIPPED_PATCH_LOCATION>/35037840 
</span></span>

To roll back the patch from the Grid home:

<span style="color:#000000"><span style="background-color:#ffffff"># opatchauto rollback <UNZIPPED_PATCH_LOCATION>/35037840 -oh <path to GI home>  
</span></span>

To roll back the patch from the Oracle RAC database home:

<span style="color:#000000"><span style="background-color:#ffffff"># opatchauto rollback <UNZIPPED_PATCH_LOCATION>/35037840 -oh <oracle_home1_path>,<oracle_home2_path> 
</span></span>

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

For detailed patch installation instructions, see Patch Installation.

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:

<span style="color:#000000"><span style="background-color:#ffffff"># <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/35037840</span></span>

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

Patching instructions:

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

   <span style="color:#000000"><span style="background-color:#ffffff">$ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>
   </span></span>

2. On the first node, unmount the Oracle ACFS file systems. See My Oracle Support note 1494652.1 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:

   <span style="color:#000000"><span style="background-color:#ffffff"># <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/35037840 -oh <GI_HOME>
   </span></span>

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 note 1494652.1 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:

   <span style="color:#000000"><span style="background-color:#ffffff"># <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/35037840 -oh <ORACLE_HOME>
   </span></span>

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

   <span style="color:#000000"><span style="background-color:#ffffff">$ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename>
   </span></span>

8. On the second (next) node, unmount the Oracle ACFS file systems. See My Oracle Support note 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:

   <span style="color:#000000"><span style="background-color:#ffffff"># <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/35037840 -oh <GI_HOME>
   </span></span>

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 note 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:

    <span style="color:#000000"><span style="background-color:#ffffff">$ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename>
    </span></span>

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 note 278641.1.
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.
3. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
4. ####单实例打补丁，只需要打35042068,用oracle用户执行

   <span style="color:#000000"><span style="background-color:#ffffff">cd <UNZIPPED_PATCH_LOCATION>/35037840/35042068
   opatch apply
   </span></span>

5. If there are errors, refer to Conflict Issues.

Roll Back the Oracle RAC Database Homes and Grid Together

For issues documented after the release of this patch, see My Oracle Support note 19202304.9 Oracle Database 19c RU/RUR Apr 2023 Known Issues.

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.