4 Issues Affecting Oracle Solaris for Oracle Database 18c

These topics contain last-minute features and changes for Oracle Solaris for Oracle Database 18c.

• Unsupported Products for Oracle Solaris
  In addition to the list of unavailable products or features in this release of Oracle Database 18c, the following product is not supported for Oracle Solaris:
• Product Support
  These are the supported products or features for Oracle Database 18c:
• Linking Applications with Oracle Client Libraries for Oracle Solaris
  You must use the dynamic Oracle client libraries to link the client code on Oracle Solaris.
• Preinstallation Requirements for Oracle Solaris
  Refer to the installation guides for the preinstallation requirements for Oracle Database 18c.
• Installation, Configuration, and Upgrade Issues for Oracle Solaris
  These topics describe information about issues that affect Oracle Database installation, configuration, and upgrade.
• Open Bugs Affecting Oracle Solaris
  This topic contains last-minute features and changes for Oracle Database 18c.

4.1 Unsupported Products for Oracle Solaris

In addition to the list of unavailable products or features in this release of Oracle Database 18c, the following product is not supported for Oracle Solaris:

• Net Configuration Assistant Support

Refer to the list of unavailable products or features for all platforms in Oracle Database 18c.

See Also:

Features Not Available or Restricted

4.2 Product Support

These are the supported products or features for Oracle Database 18c:

• Oracle Solaris Support on SPARC

  Oracle Database 18c is supported on Oracle Solaris on SPARC (64-bit).

• Database Smart Flash Cache Support

  Database Smart Flash Cache is supported on Oracle Solaris.

• Oracle ACFS and Oracle ADVM Support

  Although Oracle ADVM supports raw disks in Oracle Automatic Storage Management disk groups, Oracle ADVM device special files created through raw 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

4.3 Linking Applications with Oracle Client Libraries for Oracle Solaris

You must use the dynamic Oracle client libraries to link the client code on Oracle Solaris.

 Do not link the static Oracle client libraries.

4.4 Preinstallation Requirements for Oracle Solaris

Refer to the installation guides for the preinstallation requirements for Oracle Database 18c.

4.5 Installation, Configuration, and Upgrade Issues for Oracle Solaris

These topics describe information about issues that affect Oracle Database installation, configuration, and upgrade.

• Bug 21800407
  
• Bug 24355490
  
• Bug 28175678
  

4.5.1 Bug 21800407

When installing Oracle Database for English and Japanese environments, 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'

4.5.2 Bug 24355490

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 incorrectly sets the physical path as the software location.

Workaround:

Perform the following steps:

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

   Complete Oracle home path/gridSetup.sh

2. Proceed with the Oracle Grid Infrastructure installation.

4.5.3 Bug 28175678

When you relink product executables manually in the Oracle Database home or Oracle Grid Infrastructure home by using either the relink, relink all, or relink as_installed commands, these commands fail with the following error:

ld.so.1: getcrshome: fatal: libons.so: open failed: No such file or directory sh: line 4: 17756: Killed 

INFO: 

ld.so.1: skgxpinfo: fatal: libons.so: open failed: No such file or directory

Workaround:

Before you run either the relink, relink all, or relink as_installed commands, set the LD_LIBRARY_PATH to $ORACLE_HOME/lib: $export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib

4.6 Open Bugs Affecting Oracle Solaris

This topic contains last-minute features and changes for Oracle Database 18c.

• Bug 24438496
  

4.6.1 Bug 24438496

If you want to run the Visual COBOL 2.2 applications using the rtsora command, then 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 refer 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.