Skip Headers

Oracle® Database Patch 30501910 - GI Release Update 19.6.0.0.200114

Oracle® Database
Patch 30501910 - GI Release Update 19.6.0.0.200114
In this document Oracle Database Home refers to Enterprise Edition and Standard Edition.

The GI Release Update 19.6.0.0.200114 includes updates for both the Clusterware home and Database home that can be applied in a rolling fashion.

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

For the latest Update with Security Fixes that should be used on Client-Only installations, please refer to the Critical Patch Update (CPU) Program Patch Availability
Document (PAD) section on the Oracle Database, for the cycle you are interested in.

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

Document 2602428.1 Oracle Database 19c RU/RUR Jan 2020 Known Issues

This document includes the following sections:

Patch Information

Patch Installation and Deinstallation

Known Issues

References

Manual Steps for Apply/Rollback Patch

Bugs Fixed by This Patch

Documentation Accessibility

1.1 Patch Information

The Grid Infrastructure patches are cumulative and include the Database CPU program security content.

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

Table 1-1 Configuration and Database Patch Mapping

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

GI Home in conjunction with 19 19 GI RU/RUR opatchauto GI Home and all the Database
RAC, RACOne, or Single Homes will be patched
Instance home

GI Home in conjunction with
RAC, RACOne, or Single
Instance home
19 19 and prior versions GI RU/RUR opatchauto GI Home and Database Home at
19 version will be patched.
For Database home with version
other than 19, apply the
appropriate Database RU for that
version. For example, apply
12.2.0.1.x RU to Database version
12.2.0.1.0.

GI Home in conjunction with
RAC, RACOne, or Single
Instance home
19 Versions prior to 19 GI RU/RUR opatchauto GI Home alone is patched.
For Database home, apply the
appropriate Database RU for that
version. For example, apply
12.2.0.1.x RU to Database version
12.2.0.1.0.

Oracle Restart Home 19 19 GI RU/RUR opatchauto GI Home and all the Database
Homes will be patched.

Database Single Instance NA 19 DB RU/RUR opatch apply None

home
Configuration GI Version Database Versions Patch OPatch Command(1) Comments

Database Client home NA 19 DB RU/RUR opatch apply None

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

Table 1-2 lists the various patches by patch number getting installed as part of this Bundle patch.

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

Patch Number Description Applicable Homes

30557433 Database Release Update 19.6.0.0.200114 Only DB Home for non-Oracle RAC setup. Both DB Homes and Grid
Home for Oracle RAC setup.

30489227 OCW Release Update 19.6.0.0.200114 Both DB Homes and Grid Home

30489632 ACFS Release Update 19.6.0.0.200114 Footnote2 Only Grid Home

Footnote 2 Only Grid Home

30655595 Tomcat Release Update 19.0.0.0.0Footnote 2 Only Grid Home

Footnote 2

ACFS, DBWLM and TOMCAT subpatches are not applicable to the HP-UX Itanium and Linux on IBM System z platforms.

1.2 Patch Installation and Deinstallation

This section includes the following sections:

Patch Installation Prerequisites

One-off Patch Conflict Detection and Resolution

opatchauto

Patch Installation

Installing patch in Standby-First Mode

Patch Post-Installation Instructions

Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of Patch in the Oracle Home

Patch Deinstallation

Patch Post-Deinstallation Instructions

1.2.1 Patch Installation Prerequisites

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

OPatch Utility Information

Validation of Oracle Inventory

Download and Unzip the Patch

Run OPatch Conflict Check

Run OPatch SystemSpace Check

1.2.1.1 OPatch Utility Information

You must use the OPatch utility version 12.2.0.1.17 or later to apply this patch for all platforms. Oracle recommends that you use the latest released OPatch version for 19c,
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 location on 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 the Oracle RAC database homes and the GI home that are being patched.

To update Opatch, use the following instructions:

1. Download the OPatch utility to a temporary directory.

2. For each Oracle RAC database home and the GI home that are being patched, run the following commands as the home owner to extract the OPatch utility.
 $ unzip <OPATCH-ZIP> -d <ORACLE_HOME>
$ <ORACLE_HOME>/OPatch/opatch version

The version output of the previous command should be 12.2.0.1.17 or later.

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

1.2.1.2 Validation of Oracle Inventory

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

$ <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 you have the status prior to the patch apply.

If this command fails, contact Oracle Support Services for assistance.

1.2.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, this is called the
<UNZIPPED_PATCH_LOCATION>. This directory must be empty and not be /tmp. Additionally, the directory should have read permission for the ORA_INSTALL group.

$ cd <UNZIPPED_PATCH_LOCATION>

Check that the directory is empty.

$ ls

Unzip the patch as grid home owner except for installations that do not have any grid homes. For installations where this patch will be applied to the Database home only,
the patch needs to be unzipped as the database home owner.

$ unzip p30501910_190000_Linux-x86-64.zip

1.2.1.4 Run OPatch Conflict Check

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

For Grid Infrastructure Home, as home user:

% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/30501910/30557433

% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/30501910/30489227
% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/30501910/30489632
% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/30501910/
% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/30501910/30655595

For Database home, as home user:

% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/30501910/30557433

% $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/30501910/30489227

The report will indicate the interim patches that conflict with the patch 30501910 and the interim patches for which patch 30501910 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.

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.

1.2.1.5 Run OPatch SystemSpace 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:

% cat /tmp/patch_list_gihome.txt

<UNZIPPED_PATCH_LOCATION>/30501910/30557433
<UNZIPPED_PATCH_LOCATION>/30501910/30489227
<UNZIPPED_PATCH_LOCATION>/30501910/30489632
<UNZIPPED_PATCH_LOCATION>/30501910/
<UNZIPPED_PATCH_LOCATION>/30501910/30655595

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

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

 For Database home, as home user:

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

% cat /tmp/patch_list_dbhome.txt
<UNZIPPED_PATCH_LOCATION>/30501910/30557433
<UNZIPPED_PATCH_LOCATION>/30501910/30489227

2. Run opatch command to check if enough free space is available in the Database Home:

% $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.

1.2.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 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 Document 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 12.1 GI home and the 12.1 DB homes.

In case you are applying the patch, run this command:

#GRID_HOME/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/30501910 -analyze

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

#GRID_HOME/OPatch/opatchauto rollback <UNZIPPED_PATCH_LOCATION>/30501910 -analyze

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.

1.2.3 opatchauto

The Opatch utility has automated the patch application for the Oracle Grid Infrastructure (GI) 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 GI 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 GI home or Oracle RAC
database home is in non-shared storage. The utility should not be run in parallel on the cluster nodes.

Depending on command line options specified, one invocation of opatchauto can patch the GI home, Oracle RAC database homes, or both GI 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:

# export PATH=$PATH:<GI_HOME>/OPatch

To patch the GI home and all Oracle RAC database homes of the same version:

# opatchauto apply <UNZIPPED_PATCH_LOCATION>/30501910

To patch only the GI home:

# opatchauto apply <UNZIPPED_PATCH_LOCATION>/30501910 -oh <GI_HOME>

To patch one or more Oracle RAC database homes:

# opatchauto apply <UNZIPPED_PATCH_LOCATION>/30501910 -oh <oracle_home1_path>,<oracle_home2_path>

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

# opatchauto rollback <UNZIPPED_PATCH_LOCATION>/30501910

To roll back the patch from the GI home:

# opatchauto rollback <UNZIPPED_PATCH_LOCATION>/30501910 -oh <path to GI home>

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

# opatchauto rollback <UNZIPPED_PATCH_LOCATION>/30501910 -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.

1.2.4 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 GI together are listed below.

The most common configurations are listed as follows:

Case 1: Oracle RAC, where the GI Home and the Database Homes are not shared and ACFS file system is not configured

Case 2: Oracle RAC, where the GI Home is not shared, Database Home is shared, ACFS may be used

Case 3: Non-Oracle RAC Database homes

For other configurations listed below, see My Oracle Support Document 1591616.1:

GI Home is not shared, the Database Home is not shared, ACFS may be used.

Patching Oracle RAC Database Homes.

Patching GI Home alone.

Patching Oracle Restart Home.

Patching a software only GI Home installation or before the GI Home is configured.

Patching Oracle RAC Database Homes and GI Together

Case 1: Oracle RAC, where the GI Home and the Database Homes are not shared and ACFS file system is not configured.

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

# <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/30501910

Case 2: Oracle RAC, where the GI Home is not shared, Database Home is shared, ACFS may be used.

Patching instructions:

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

$ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>

2. On the 1st node, unmount the ACFS file systems. See My Oracle Support Document 1494652.1 for unmounting ACFS file systems.

3. On the 1st node, apply the patch to the GI Home using the opatchauto command. As root user, execute the following command:

# <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/30501910 -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 1st node, remount ACFS file systems. See My Oracle Support Document 1494652.1 for mounting ACFS file systems.

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

# <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/30501910 -oh <ORACLE_HOME>

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

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

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

9. On the 2nd node, apply the patch to GI Home using the opatchauto command. As root user, execute the following command:

# <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/30501910 -oh <GI_HOME>

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 2nd node, running the opatchauto command in Step 9 will restart the stack.

12. On the 2nd node, remount ACFS file systems. See My Oracle Support Document 1494652.1 for mounting ACFS file systems.

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

$ <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: Non-Oracle RAC Database homes.

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 278641.1.
 2. If this is not an Oracle 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.

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

cd <UNZIPPED_PATCH_LOCATION>/30501910/30557433
opatch apply

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

1.2.5 Installing patch in 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 30557433 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.

1.2.6 Patch Post-Installation Instructions

After installing the patch, perform the following actions:

1. Apply conflict resolution patches as explained in Applying Conflict Resolution Patches.

2. If you are not using opatchauto, then load modified SQL files into the database, as explained in Loading Modified SQL Files into the Database.

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

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

1.2.6.2 Loading Modified SQL Files into the Database

The following steps load modified SQL files into the database. For a 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: Database 12c Post Patch SQL Automation (Doc ID 1585822.1).

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 Standalone DB Versus Single/Multitenant (CDB/PDB) DB

Steps Standalone DB Steps Single/Multitenant (CDB/PDB) DB

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 -verbose 6 % cd $ORACLE_HOME/OPatch

7 % ./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).

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 the following My Oracle Support note for additional information and actions: Document 1609718.1 Datapatch Known Issues.
 2. Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/30557433/<unique patch ID> for errors:

30557433_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 databases that have invalid objects after the execution of datapatch should have utlrp.sql run to revalidate those objects.

For example:
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql

1.2.6.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;

1.2.7 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of Patch in the Oracle Home

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

1.2.8 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: Database 12c Post Patch SQL Automation (Doc ID 1585822.1).

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 GI are listed below.

The most common configurations are listed as follows:

Case 1: Oracle RAC, where the GI Home and Database Homes are not shared and ACFS file system is not configured

Case 2: Oracle RAC, where the GI Home is not shared, Database Home is shared and ACFS may be used

Case 3: Non-Oracle RAC Database homes

For other configurations listed below, see My Oracle Support Document 1591616.1:

GI Home is not shared, the Database Home is not shared, ACFS may be used.

Rolling back from Oracle RAC Database Homes.

Rolling back from GI Home alone.

Rolling back the patch from Oracle Restart Home.

Rolling back the patch from a software only GI Home installation or before the GI Home is configured.

Roll Back the Oracle RAC Database Homes and GI Together

Case 1: Oracle RAC, where the GI Home and Database Homes are not shared and ACFS file system is not configured.

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

# <GI_HOME>/OPatch/opatchauto rollback <UNZIPPED_PATCH_LOCATION>/30501910

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 GI Home is not shared, Database Home is shared and ACFS may be used.

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

$ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>

2. On the 1st node, unmount the ACFS file systems. See My Oracle Support Document 1494652.1 for unmounting ACFS file systems.

3. On the 1st node, roll back the patch from the GI Home using the opatchauto command. As root user, execute the following command:

# <GI_HOME>/OPatch/opatchauto rollback <UNZIPPED_PATCH_LOCATION>/30501910 -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 1st node, remount ACFS file systems. See My Oracle Support Document 1494652.1 for mounting ACFS file systems.

6. On the 1st node, roll back the patch to the Database home using the opatchauto command. This operation will rollback the patch to the Database home
across the cluster given that it is a shared ACFS home. Note that a USM only patch cannot be applied to a Database home. As root user, execute the
following command:
 # <GI_HOME>/OPatch/opatchauto rollback <UNZIPPED_PATCH_LOCATION>/30501910

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

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

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

9. On the 2nd node, roll back the patch to GI Home using the opatchauto command. As root user, execute the following command:

# <GI_HOME>/OPatch/opatchauto rollback <UNZIPPED_PATCH_LOCATION>/30501910

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 2nd node, running the opatchauto command in Step 9 will restart the stack.

12. On the 2nd node, remount ACFS file systems. See My Oracle Support Document 1494652.1 for mounting ACFS file systems.

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

$ <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: Non-Oracle RAC Database homes.

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.

opatch rollback -id 30557433

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

1.2.9 Patch Post-Deinstallation Instructions

After deinstalling the patch, perform the following actions.

Run the datapatch Utility

Upgrade Oracle Recovery Manager Catalog

1.2.9.1 Run the datapatch Utility

Perform the following steps:

1. For each separate database 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 Standalone DB Versus Single/Multitenant (CDB/PDB) DB

Steps Standalone DB Steps Single/Multitenant (CDB/PDB) DB

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 -verbose 6 % cd $ORACLE_HOME/OPatch

7 % ./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).
 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 the following My Oracle Support note for additional information and actions: Document 1609718.1 Datapatch Known Issues.

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

30557433_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 databases that have invalid objects after the execution of datapatch should have utlrp.sql run to revalidate those objects.

For example:
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql

1.2.9.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;

1.3 Known Issues

For issues documented after the release of this patch, see My Oracle Support Document 2602428.1 Oracle Database 19c RU/RUR Jan 2020 Known Issues.

This section includes the following known issues:

Issue 1

For all Opatchauto known issues, see My Oracle Support Master Note for OPatch (Document ID 293369.1). For more information about opatchauto and known
issues while patching, see Oracle® OPatch User's Guide.

Issue 2

Problem: An ORA-04068 error may appear in the Database alert log file when datapatch is run.

During a successful run of the datapatch tool with no errors indicated, an ORA-04068 error may appear in the Database alert log file:

ORA-04068: existing state of packages has been discarded

Workaround: This is a retryable error in datapatch itself. If a patch installation receives it, then datapatch will automatically retry the operation once, before reporting
it as a failure. The fact that datapatch did not report the retry and ran successfully with no errors confirms that the patch was successfully installed, and that another
Oracle background process received the error. The ORA-04068 error should be ignored as long as datapatch runs successfully with no errors indicated (possibly
after an automatic retry).

1.4 References
The following documents are references for this patch.

Document 2602428.1 Oracle Database 19c RU/RUR Jan 2020 Known Issues

Document 2523221.1 Database 19 Release Updates and Revisions Bugs Fixed Lists

Document 2246888.1 Supplemental Readme — Grid Infrastructure Release Update 12.1.0.1.x / 18.x / 19.x

Document 1494652.1 Instructions for Mounting/Unmounting ACFS File Systems

Document 1585822.1 Database 12c Post Patch SQL Automation

Document 360870.1 Impact of Java Security Vulnerabilities on Oracle Products

Document 340978.1 Genclntsh: Could Not Locate $ORACLE_HOME/network/admin/shrept.lst

Document 468959.1 Enterprise Manager Grid Control Known Issues

Oracle® OPatch User's Guide

1.5 Manual Steps for Apply/Rollback Patch

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

1.6 Bugs Fixed by This Patch

See My Oracle Support Document 2523221.1 Database 19 Release Updates and Revisions Bugs Fixed Lists

1.7 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 30501910 - GI Release Update 19.6.0.0.200114

Copyright © 2020, Oracle and/or its affiliates. All rights reserved.

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.

Copyright © 2020, Oracle and/or its affiliates. All rights reserved.