4 Issues Affecting the Oracle Solaris Platform for Oracle Database 18c
These topics contain last-minute features and changes for the Oracle Solaris platform for Oracle Database 18c.
- Unsupported Products for the Oracle Solaris Platform
- Linking Applications with Oracle Client Libraries for the Oracle Solaris Platform
- Preinstallation Requirements for the Oracle Solaris Platform
- Installation, Configuration, and Upgrade Issues for the Oracle Solaris Platform
- Open Bugs Affecting the Oracle Solaris Platform
4.1 Unsupported Products for the Oracle Solaris Platform
In addition to the list of unavailable products or features in this release of Oracle Database 18c, the following products and features are not supported:
See Also:
4.1.1 Net Configuration Assistant Support
Net Configuration Assistant (NETCA) is not supported on Oracle Solaris on SPARC (32-Bit) and Oracle Solaris on x86 (32-Bit) client platforms.
Parent topic: Unsupported Products for the Oracle Solaris Platform
4.2 Linking Applications with Oracle Client Libraries for the Oracle Solaris Platform
You must use the dynamic Oracle client libraries to link the client code on Linux. Do not link the static Oracle client libraries.
4.3 Preinstallation Requirements for the Oracle Solaris Platform
Refer to the installation guides for the preinstallation requirements for Oracle Database 18c.
4.4 Installation, Configuration, and Upgrade Issues for the Oracle Solaris Platform
Review the following section for information about issues that affect Oracle Database installation, configuration, and upgrade:
4.4.1 Font Color Issue When Installing Oracle Database
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.
4.4.2 Inconsistent Oracle Home Path During an Oracle Grid Infrastructure Installation
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:
-
Set the Oracle Grid Infrastructure installer using the complete path to the desired Oracle home path:
Complete Oracle home path/gridSetup.sh
-
Proceed with the Oracle Grid Infrastructure installation.
This issue is tracked with Oracle bug 24355490.
4.5 Open Bugs Affecting the Oracle Solaris Platform
These topics contain last-minute features and changes for Oracle Database 18c.
4.5.1 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:
-
Verify if the
COBMODE
andCOBDIR
variables point to the directory where Visual COBOL is installed andLD_LIBRARY_PATH
andPATH
variables contain theCOBDIR
andCOBIDR/lib
directories respectively. -
Relink the
rtsora
command inORACLE_HOME
.cd $ORACLE_HOME/precomp/lib make -f ins_precomp.mk relink EXENAME=rtsora
-
Run the Visual COBOL 2.2 applications.
This issue is tracked with Oracle bug 24438496.
Parent topic: Open Bugs Affecting the Oracle Solaris Platform