|Oracle® Database Release Notes
11g Release 1 (11.1) for Oracle Solaris
|PDF · Mobi · ePub|
11g Release 1 (11.1) for Oracle Solaris
This document contains important 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. To check for updates to this document and to view other Oracle documentation, refer to the Documentation section on the Oracle Technology Network (OTN) Web site:
For additional information about this release, refer to the readme files located in the
Note:The Database Quick Installation Guides are no longer available in printed format. These documents are available with the media in the same location as the software and on Oracle Technology Network.
This document contains the following topics:
The latest certification information for Oracle Database 11g Release 1 (11.1) is available on My Oracle Support (formerly OracleMetaLink) at:
Starting with Oracle Database 11g release 1 (184.108.40.206), Oracle ODBC driver is supported on Solaris SPARC. Oracle ODBC driver uses
gcc 3.4.5 for compilation instead of the native compilers on Solaris SPARC operating systems.
A list of unavailable features and products is available in Section 2, "Features Not Available or Restricted in This Release", in Oracle Database Readme.
Refer to the installation guides for the preinstallation requirements. However, the following section contains additional preinstallation requirements:
If you plan to use Sun Cluster with Solaris Operating System (SPARC 64-bit), then install ORCLudlm 64-Bit reentrant 220.127.116.11. This requirement supersedes the UDLM version listed in Oracle Clusterware Installation Guide for Solaris Operating System.
This issue is tracked with Oracle bug 8795539.
On trying to install Oracle Database 11g release 1 on Oracle Solaris on SPARC (64-Bit) with update 5 or lower installed, Oracle Universal Installer reports the following error:
The 11g compatible version of operating system update is not present.
To workaround this issue, perform the following steps:
Install Solaris 9 update 6 or higher on Oracle Solaris on SPARC (64-Bit):
% cat /etc/release | grep s9s Solaris 9 9/04 s9s_u6wos_04a SPARC
In the output of the command,
_u6 refers to update 6 of Solaris 9.
Ensure the required version of Solaris package is installed:
% /bin/pkginfo -l SUNWsolnm | grep VERSION VERSION: 9,REV=2004.03.22.13.18
If the revision date is prior to the date provided, order a newer version of the package, and install it on the server.
Install Oracle Database 11g release 1.
Review the following sections for information about issues that affect Oracle Database installation, configuration, and upgrade:
For late-breaking updates and best practices about preupgrade, post-upgrade, compatibility, and interoperability discussions, refer to Note 601807.1 on My Oracle Support (formerly OracleMetaLink)(
https://support.oracle.com/) that links to "Oracle 11g Upgrade Companion" page.
Use the Oracle Fusion Middleware Web Tier Utilities 11g (18.104.22.168.0) media to install Oracle HTTP Server.
To determine the size of the configured swap space, enter the following command:
# /usr/sbin/swap -l
Note:The output of this command shows the total/available swap blocks, where each block is equal to 512 bytes and not 1 KB.
32-bit Java refers to the 64-bit
$ORACLE_HOME/lib/libocijdbc11.so library and displays an exception.
Workaround: Set the
LD_LIBRARY_PATH variable to
This issue is tracked with Oracle bug 5507215.
When you upgrade Oracle Database 10g Release 1 (10.1.0.4) to Oracle Database 11g, the database instance fails to start after the
rootupgrade.sh script is run and an error message is displayed.
Workaround: Complete one of the following options to address this issue:
One each node, complete the following procedure:
racgwrap script available under 10.1.0.4 RAC_home in an editor, such as vi editor.
Add the following lines to the script:
LD_LIBRARY_PATH_64=$ORACLE_HOME/lib:$LD_LIBRARY_PATH_64 export LD_LIBRARY_PATH_64
Attempt the upgrade from Oracle Database 10g Release 1 (10.1.0.5) to Oracle Database 11g.
When upgrading Oracle9i database to Oracle Database 11g, Database Upgrade Assistant fails to stop the Oracle9i database on Oracle Clusterware.
Workaround: Complete the following procedure to resolve this issue:
Run the following commands on each node in Oracle Clusterware:
$CRSHome/bin/crsuser add Oracle_92_user_domain/Oracle_92_username $CRSHome/bin/crs_setperm ora.node_name.gsd -o Oracle_92_user_domain/Oracle_92_username
From any node in the cluster, run the following commands for each node configured in the cluster:
$CRSHome/bin/crs_stop -f ora.node_name.gsd $CRSHome/bin/crs_start ora.node_name.gsd
Note:To find the list of nodes in the cluster, run the
This issue is tracked with Oracle bug 6499906.
When you start upgrading second node from Oracle Database 10g Release 2 to Oracle Database 11g, an error message is displayed while copying files during the upgrade process.
Workaround: Run the upgrade session from the node on which you initially installed Oracle RAC.
This issue is tracked with Oracle bug 6501871.
When installing Oracle Database 11g, if you click Help, then Oracle Universal Installer does not display the help page for the Run Root.sh screen.
This issue is tracked with Oracle bug 6503397.
When installing Oracle Database 11g (22.214.171.124.0) software with create or upgrade database option, Oracle Database Configuration Assistant fails to start and Oracle Universal installer displays the
OUI-25301 error message.
When running Oracle Database Configuration Assistant after the installation, the following error message is displayed:
Workaround: To resolve this issue, complete the following procedure before starting Oracle Universal Installer or Oracle Database Configuration Assistant:
Run the following command to set the
$ export JAVA64FLAG="-d64"
Start Oracle Universal Installer or Oracle Database Configuration Assistant.
This issue is tracked with Oracle bug 6628285.
When performing Data Guard rolling upgrade from Oracle Database 10g Release 2 (10.2.0.3) using Oracle Database Upgrade Assistant, Oracle Enterprise Manager displays an error message.
This issue is tracked with Oracle bug 6597505.
When performing upgrade from Oracle Database 10g Release 1 (10.1.0.4), Oracle Enterprise Manager Database Control fails and displays the following error message:
QUEUE SYSMAN.MGMT_NOTIFY_Q does not exist
Workaround: To resolve this issue, run the following SQL command as
SYSMAN user before performing the upgrade:
SQL> BEGIN SQL> DBMS_AQADM.CREATE_QUEUE_TABLE (queue_table => SQL> 'SYSMAN.MGMT_NOTIFY_QTABLE', queue_payload_type => SQL> 'SYSMAN.MGMT_NOTIFY_NOTIFICATION', multiple_consumers => TRUE); SQL> DBMS_AQADM.CREATE_QUEUE (queue_name => 'SYSMAN.MGMT_NOTIFY_Q', SQL> queue_table => 'SYSMAN.MGMT_NOTIFY_QTABLE'); SQL> DBMS_AQADM.START_QUEUE (queue_name => 'SYSMAN.MGMT_NOTIFY_Q'); SQL> END;
This issue is tracked with Oracle bug 5508403.
Oracle Universal Installer displays the following warning message:
Warning: Cannot convert string "-monotype-arial-regular-r-normal--*-140-*-*-p-*-iso8859-1" to type FontStruct sh: sysdef: not found sh: sysdef: not found
Workaround: This is a benign message and you can ignore it. Click Ok to continue with the installation process.
This issue is tracked with Oracle bug 6145402.
If you install Oracle Clusterware on shared Oracle home, the
/var/opt/oracle/oratab file lists multiple Automatic Storage instances.
When Automatic Storage Management Oracle home is installed in shared file system to create Automatic Storage Management instances from Oracle Universal Installer, multiple Automatic Storage Management instances are listed in the
Workaround: Oracle Universal Installer detects this issue during the prerequisite checks. You can edit the
/var/opt/oracle/oratab file in each node and remove the entries that are not part of that node. The alternative is to install the software, run the
root.sh script on all nodes and create Automatic Storage Management instance by running Database Configuration Assistant.
The issue is tracked with Oracle bug 5942123.
When you remove Automatic Storage Management with database, the *.err log file is created under the under the
$ORACLE_BASE\oraInventory\logs. directory. This file shows that some error was generated when removing Automatic Storage Management with database.
This issue is tracked with Oracle bug 6369645.
The following sections contain information about issues related to Oracle Database 11g and associated products:
OC4JADMIN user is deactivated during the Oracle Database 11g installation process. After the installation is complete, you must modify the
$ORACLE_HOME/oc4j/j2ee/OC4J_SEARCH/config/system-jazn-data.xml file. Replace the following content of the file:
<user deactivated="true"> <name>oc4jadmin</name> <display-name>OC4J Administrator</display-name> <description>OC4J Administrator</description>
<user> <name>oc4jadmin</name> <display-name>OC4J Administrator</display-name> <description>OC4J Administrator</description>
Use the following commands to restart the Oracle Ultra Search middle tier in the Oracle Database:
$ $ORACLE_HOME/bin/searchctl stop $ $ORACLE_HOME/bin/searchctl start
If you keep Oracle Instant Client libraries in different directories and create symbolic links to these libraries in the same directory, then the Oracle Instant Client mode is not turned on.
Workaround: All the Oracle Instant Client libraries must physically reside in the same directory.
This issue is tracked with Oracle bug 6504887.
When adding a node to the Oracle Clusterware in a vendor cluster environment that uses host names with fully qualified domain names, the
rootaddnode.sh utility displays the following error message:
PRKO-2006 : Invalid node name: NODE_NAME
Workaround: For each node that is being added to the Oracle Clusterware, run the following command:
srvctl add nodeapps -n node_name_without_fully_qualified_ domain_name -A node-vip/netmask/Interfaces
Note:To find the node name and virtual IP address/netmask/interface to be used for the newly added nodes, you can refer to values set for the following variables in the
CRS_NEW_NODE_NAME_LIST= CRS_NEW_NODEVIPS= NETMASK= NETIFs=
To find if the vendor clusterware is configured, run the
$ORA_CRS_HOME/bin/lsnodes command. The
lsnodes command displays the list of nodes in this case.
You can refer to
rootaddnode.sh for the value that
ORA_CRS_HOME is set to.
This issue is tracked with Oracle bug 6617499.
This section lists the following corrections to the Solaris installation guides:
The " Patch Requirements" section in chapter 2 of Oracle Database Installation Guide for Solaris Operating System, lists the following incorrect values for Pro*C/C++, Pro*FORTRAN, Oracle Call Interface, Oracle C++ Call Interface, and Oracle XML Developer's Kit (XDK). The following values are invalid:
Patches for Solaris 9 :
112760-05, C 5.5: Patch for S1S8CC C compiler
Patches For Solaris 10:
117837-05: C++ compiler optimizer patch
117846-08: C++ compiler Optimization patch
Section 2.3.3, "Compiler Requirements" in Chapter 2 of Oracle Database Installation Guide for Solaris Operating System, Oracle Database Client Installation Guide for Solaris Operating System, and the respective Quick Installation Guides incorrectly mention the compiler name as Sun One Studio 11.
Chapter 2 of Oracle Clusterware Installation Guide for Solaris Operating System also incorrectly mentions Sun One Studio 11.
The correct compiler name is Sun Studio 11.
Appendix H, "Database Limits" of Oracle Database Administrator's Reference for Linux and UNIX guide states the incorrect value for control files as 20000 database blocks. The correct value is 25000 control file blocks with a block size of 4096 bytes.
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Oracle customers have access to electronic support through My Oracle Support. For information, visit
http://www.oracle.com/support/contact.html or visit
http://www.oracle.com/accessibility/support.html if you are hearing impaired.
Oracle Database Release Notes, 11g Release 1 (11.1) for Oracle Solaris
Copyright © 2008, 2011, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.