The Oracle Universal Installer (OUI) runInstaller script that resides in the Oracle home (ORACLE_HOME/oui/bin/setup.exe) cannot be used to install the Oracle Database 18c releases, Oracle Grid Infrastructure for a cluster, and Oracle Database Client.

Workaround:

Refer to the Installation Guide of the respective product for instructions on how to install the product.

Oracle Database installer does not check if the password specified for ASMSNMP on the Specify Management Options screen is correct or not. If you proceed with the configuration and specify an incorrect password, then Oracle Enterprise Manager Cloud Control cannot discover details and monitor the Oracle ASM instance.

Workaround #1:

Ensure that the correct password (the same password that was specified earlier during the Oracle Grid Infrastructure for a cluster installation) is specified in Specify Management Options screen of Oracle Database installer.

Workaround #2:

On the Oracle Enterprise Manager Cloud Control portal, navigate to the Oracle ASM credentials screen and update the correct password for ASMSNMP. Once the correct password is saved on Oracle Enterprise Manager Cloud Control, the Oracle ASM monitoring starts working.

When installing an Oracle RAC database on an Oracle Member Cluster for Database that is configured to use an Oracle ASM service of an Oracle Domain Services Cluster (DSC) and, if the network selected for ASM or ASM & Private usage is not of the same type as the ASM network of the DSC, then the database instance terminates with the following error:

IOS hit ORA-00600: internal error code, arguments: [kfias_creg!net]

Workaround:

During the installation of the Oracle Member Cluster for Database, choose the network interface for ASM or ASM & Private so that it is on the same network as the Oracle ASM network of the DSC.

When deinstalling Oracle Grid Infrastructure for a standalone server home with an Oracle Management Server configuration, the emConfig.txt file in ORACLE_BASE/admin/emca may not get deleted.

Workaround:

To remove the emConfig.txt file, execute the following command:

rm -rf $ORACLE_BASE/admin/emca/emConfig.txt

During the last ORACLE_HOME deinstallation, to remove ORACLE_BASE, execute the following command after the deinstallation tool exits:

rm -rf $ORACLE_BASE

After downgrading Oracle Clusterware using the Grid Setup Wizard, from release 18c to release 12.1 or 11.2 of Oracle Clusterware, the unused data files of the Oracle Grid Infrastructure Management Repository (GIMR) of the 18c Oracle Grid Infrastructure home could still be present in the disk group.

Workaround:

Before starting the downgrade procedure using the Grid Setup Wizard, delete the GIMR database using the following command:

<Active_GI_HOME>/bin/dbca -silent -deleteDatabase -sourceDB -MGMTDB