This document contains information that was not included in the platform-specific or product-specific documentation for this release. This document supplements Oracle Database Readme.

This document may be updated after it is released. You can check for updates to this document and view other Oracle documentation at

http://docs.oracle.com/en/database/database.html

This document contains the following topics:

• Unsupported Products

• Product Support

• Preinstallation Requirements for Release 12.2

• Installation, Configuration, and Upgrade Issues for Release 12.2

• Other Known Issues for Release 12.2

• Documentation Accessibility

In addition to the list of unavailable products or features in section, ”Features Not Available or Restricted in This Release of Oracle Database 12c Release 2 (12.2.0.1)” in Oracle Database Readme, the following products and features are not supported:

For this release, IPv6 networks are not supported for Oracle Real Application Clusters (Oracle RAC) private interconnects on Oracle Solaris platform.

Net Configuration Assistant (NETCA) is not supported on Oracle Solaris on SPARC (32-Bit) and Oracle Solaris on x86 (32-Bit) client platforms.

The list of supported products or features for Oracle Database 12c Release 2 (12.2.0.1) are as follows:

This release is supported on Oracle Solaris on SPARC (64-bit).

Database Smart Flash Cache is supported only on Oracle Solaris and Oracle Linux.

Although Oracle ADVM supports raw disks in Oracle Automatic Storage Management disk groups, Oracle ADVM device special files created through raw(8) are not supported; Oracle ADVM only supports block device special files.

For the latest information about supported platforms and releases, see the Note 1369107.1 on My Oracle Support at

https://support.oracle.com

Oracle Automatic Storage Management Filter Driver (Oracle ASMFD) is supported only on Linux x86-64.

Share-based Instance Caging is supported only on Oracle Solaris and Oracle Linux.

Refer to the installation guides for the preinstallation requirements.

Review the following section for information about issues that affect Oracle Database installation, configuration, and upgrade:

• Font Color Issue When Installing Oracle Database

• Inconsistent Oracle Home Path During an Oracle Grid Infrastructure Installation

When installing Oracle Database for the English and Japanese environment, the background font incorrectly displays yellow color for the Oracle Universal Installer (OUI), Database Configuration Assistant (DBCA), and Database Upgrade Assistant (DBUA) pages.

Workaround:

Prior to installing Oracle Database, run the following command:

export _JAVA_OPTIONS='-Dsun.java2d.xrender=false'

This issue is tracked with Oracle bug 21800407.

When installing or upgrading an Oracle Grid Infrastructure home on Oracle Solaris 10, if the desired software location resides under a soft link, then the Oracle Grid Infrastructure installer may incorrectly set the physical path as the software location.

Workaround:

Perform the following steps:

1. Set the Oracle Grid Infrastructure installer using the complete path to the desired Oracle home path:

   Complete Oracle home path/gridSetup.sh

2. Proceed with the Oracle Grid Infrastructure installation.

This issue is tracked with Oracle bug 24355490.

The following section contains information about issues related to Oracle Database 12c and associated products:

• Running Visual COBOL 2.2 Applications Using rtsora

If you want to run the Visual COBOL 2.2 applications using the rtsora command, then you must relink rtsora in ORACLE_HOME.

Workaround:

Perform the following steps to run the Visual COBOL 2.2 applications:

1. Verify if the COBMODE and COBDIR variables point to the directory where Visual COBOL is installed and LD_LIBRARY_PATH and PATH variables contain the COBDIR and COBIDR/lib directories respectively.

2. Relink the rtsora command in ORACLE_HOME.

   cd $ORACLE_HOME/precomp/lib
   make -f ins_precomp.mk relink EXENAME=rtsora

3. Run the Visual COBOL 2.2 applications.

This issue is tracked with Oracle bug 24438496.

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.