Deinstallation of Oracle Real Application Clusters (Oracle RAC) home on shared Network Attached Storage (NAS) fails to delete the directory $ORACLE_HOME/deinstall and returns the following error:

Failed to delete the directory $ORACLE_HOME/deinstall. Either user has no permission to delete or it is in use.

Workaround:

Manually delete the $ORACLE_HOME/deinstall folder as either the Oracle RAC owner or as root.

To install Oracle Database software 19.4 on SUSE Linux Enterprise Server 15, download the Oracle Database software binaries from Oracle Technology Network (OTN), and then apply the 19.4 release updates (RUs) during the the Oracle Database and Oracle Grid Infrastructure installation or upgrade process.

Workaround:

During the Oracle Database and Oracle Grid Infrastructure installation process, run the runInstaller and gridSetup.sh commands with the -applyRU and -applyOneOffs options to install the latest 19.4 RU for SUSE Linux Enterprise Server 15:

 $ 19.3_grid_home/gridSetup.sh -applyRU 19.4GIRU patch 29708769 -applyOneOffs patch 30171454

$ 19.3_grid_home/gridSetup.sh -applyRU 19.4GIRU patch 29708769 -applyOneOffs patch 30171454, patch 28321248

$ 19.3_dbhome/runInstaller -applyRU 19.4GIRU patch 29708769 -applyOneOffs patch 30171454

$ 19.3_dbhome/runInstaller -applyRU 19.4DBRU patch 29834717 -applyOneOffs patch 30083976

1. Enter the following command to stop OSWatcher from Oracle Trace File Analyzer (Oracle TFA):

   $ grid_home/bin/tfactl stop  oswbb to stop

2. Add disown -a to the main loop inside OSWatcher.sh.
3. Set ulimit to a sufficiently low value for the user running OSWatcher. 

libstdc++33 package missing error during Oracle Instant Client installation.

Workaround:

In the Perform Prerequisite Checks screen, select Ignore All and proceed with the installation.

For non-interactive or silent installations, run the following command:

$./runInstaller -ignorePrereq

If you install single instance Oracle Database 19c on SUSE Linux Enterprise Server 15 or SUSE Linux Enterprise Server 12 SP3 with 19.8 or later DBRU, then you may encounter a prerequisite error for the libstdc++33-3.3.3-62.1 package.

Workaround 1:

The libstdc++33-3.3.3-62.1 package is not required on SUSE Linux Enterprise Server 15 or SUSE Linux Enterprise Server 12 SP3.

In the Perform Prerequisite Checks screen, select Ignore All and proceed with the installation.

Workaround 2:

Apply 19c Oracle Clusterware Release Update (OCWRU) that is bundled in the 19c Oracle Grid Infrastructure Release Update (GIRU) along with Oracle Database 19c Release Update (DBRU) 19.8 or later.

libgfortran package missing error during Oracle Database 19.4 installation on SUSE Linux Enterprise Server 15

Workaround:

Ignore the warning and ensure that you install the libgfortran4-7.3.1+r258812-2.15.x86_64 package on the system.

To install Oracle Database 19c on Oracle Linux 8 or Red Hat Enterprise Linux 8, download the 19.3 Oracle Database software binaries from Oracle Technology Network (OTN), and then apply the 19.6 or 19.7 release updates (RUs) during the the Oracle Database and Oracle Grid Infrastructure installation or upgrade process.

Installation Process:

During the Oracle Database and Oracle Grid Infrastructure installation process, run the runInstaller and gridSetup.sh commands with the -applyRU and -applyOneOffs options to install the latest 19.6 RU or 19.7 RU for Oracle Linux 8 and Red Hat Enterprise Linux 8:

$ export CV_ASSUME_DISTID=OL7
$ 19.3_dbhome/runInstaller -applyRU 19.6DBRU patch 30557433 location -applyOneOffs 19.6OJVM patch 30484981 location, 19.6Oneoff patch 30150710 location

$ export CV_ASSUME_DISTID=OL7
$ 19.3_dbhome/runInstaller -applyRU 19.7DBRU patch 30869156 location

$ 19.3_grid_home/gridSetup.sh -applyRU 19.6GIRU patch 30501910 location -applyOneOffs 19.6OJVM patch 30484981 location, 19.6OCWRU patch 30855259 location

$ 19.3_grid_home/gridSetup.sh -applyRU 19.7GIRU patch 30899722 location 

$ 19.3_dbhome/runInstaller -applyRU 19.6GIRU patch 30501910 location -applyOneOffs 19.6OJVM patch 30484981 location, 19.6OCWRU patch 30855259 location, 19.6Oneoff patch 30150710 location

$ 19.3_dbhome/runInstaller -applyRU 19.7GIRU patch 30899722 location 

The sudo option for running root configuration scripts does not work during Oracle Database 19c or Oracle Grid Infrastructure 19c installations on Oracle Linux 8 or Red Hat Enterprise Linux 8 systems.

On Oracle Linux 8 or Red Hat Enterprise Linux 8, C++ applications built with g++8 cannot be used with Oracle C++ Call Interface (OCCI).

Workaround:

-D_GLIBCXX_USE_CXX11_ABI=0 -Wno-narrowing

compat-libcap1-1.10 package missing error during single-instance Oracle Database and Oracle Database Client installations on Oracle Linux 8 and Red Hat Enterprise Linux 8.

Workaround:

In the Perform Prerequisite Checks screen, for the compat-libcap1-1.10 missing check, select Ignore All, and click Install to continue with the installation.

Oracle Database Standard Edition 2 allows you to create more than one pluggable database (PDB) in a multitenant container database (CDB). However, when you use the Oracle Database Configuration Assistant (Oracle DBCA) to create a second PDB, you receive the following error:

[FATAL] [DBT-11506] Creation of more than one PDB requires Enterprise Edition license.

Workaround:

Create the additional PDB using the SQL statement CREATE PLUGGABLE DATABASE.

When you use the srvctl relocate database command to initiate the relocation of a database configured with Standard Edition High Availability, and if the destination-configured node does not have an available Oracle Database home, then the relocation fails as expected but with error messages that do not include the reason for the failure.

This issue will be fixed in a future Oracle Database 19c release update.

Workaround:

None.

When you use Oracle Database Configuration Assistant (Oracle DBCA) to create a single-instance database on an Oracle Clusterware node, the database is registered with Oracle Clusterware. However, the command output incorrectly says the following:

Registering database with Oracle Restart

Workaround:

None.

When you relocate Oracle Database configured with Standard Edition High Availability that has active database services, the srvctl status service command on that database displays a blank list of instance that has the services running. However, the services are running on the database instance.

Workaround:

None.

When you use the srvctl relocate database command to initiate the relocation of a database configured with Standard Edition High Availability, and if Oracle Database has a service registered, then the shutdown of the database instance is suspended for a period of time due to the mount lock being held.

The registered database services are not accessible when the database instance is suspended and the Oracle Database instance stops eventually on the current node and starts on the destination node.

Workaround:

  Use a sequence of srvctl stop database commands followed by the srvctl start database -node destination node commands to avoid shutdown suspension.  

When you run the srvctl config service command for an Oracle Database with Standard Edition High Availability configured and its services registered,  a Java NULL pointer exception occurs at the end of the output for the first service.

This issue will be fixed in a future Oracle Database 19c release update.

Workaround:

None.

When you configure Standard Edition High Availability for a single-instance Oracle Database 19c Release Update (RU) 19.7 that does not have any database services registered, you will observe a local restart when the instance is abnormally terminated. However, after a service is added to the database, you do not observe the local restart. Instead, the database fails over immediately when it is abnormally terminated.

This issue will be fixed in a future Oracle Database 19c release update.

Workaround:

None.

If Oracle base of the Oracle Database home is the same as Oracle base of the Oracle Grid Infrastructure home, then if the user adds a new node to the cluster, the Oracle Database home user loses access permissions to some of the subdirectories under Oraclebase of the Oracle Database home.

Workaround:

Use distinct directories as Oracle base for the Oracle Grid Infrastructure and Oracle Database installations.

When you use the srvctl relocate database -help command from a Standard Edition single-instance Oracle Database 19c home, the prompt incorrectly displays usage and help messages with the mention of Oracle Real Application Clusters One Node (Oracle RAC One Node). Starting with Oracle Database 19c Release Update (RU) 19.7, this command applies to Standard Edition High Availability and must contain the corresponding usage and help messages.

This issue will be fixed in a future Oracle Databse 19c release update.

Workaround:

Starting with Oracle Database 19c Release Update (RU) 19.7, you use the srvctl add or modify database commands to configure Standard Edition High Availability by specifying the -node option with a node list of more than one node. However, the usage messages from these commands, such as when running from an Oracle Database Standard Edition 2 database home with the -help option, do not show this usage.

This issue will be fixed in a future Oracle Database 19c release update.

Workaround: