Skip Headers
Oracle® Database Release Notes
11g Release 1 (11.1) for Solaris Operating System

Part Number B32067-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

  View PDF

Oracle® Database

Release Notes

11g Release 1 (11.1) for Solaris Operating System

B32067-05

February 2008

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:

http://www.oracle.com/technology/documentation/

For additional information about this release, refer to the readme files located in the $ORACLE_HOME/relnotes directory.

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:

1 Certification Information

The latest certification information for Oracle Database 11g Release 1 (11.1) is available on OracleMetaLink at:

http://metalink.oracle.com

2 Unsupported Products

Internet Protocol version 6 (IPv6) support is not enabled on Solaris Operating System (SPARC 64-Bit).

A list of unavailable features and products is available in Section 2, "Features Not Available or Restricted in This Release", in Oracle Database Readme.

3 Preinstallation Requirements

Refer to the installation guides for the preinstallation requirements.

4 Installation, Configuration, and Upgrade Issues

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

4.1 Latest Upgrade Information

For late-breaking updates and best practices about preupgrade, post-upgrade, compatibility, and interoperability discussions, refer to Note 466181.1 on OracleMetaLink (https://metalink.oracle.com/) that links to "The Upgrade Companion" Web site.

4.2 32-bit Java Refers to the 64-bit libocijdbc11.so Library

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 $ORACLE_HOME/lib32.

This issue is tracked with Oracle bug 5507215.

4.3 Database Instance Fails to Start After Upgrading From Oracle Database 10g Release 1

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:

    1. Open the racgwrap script available under 10.1.0.4 RAC_home in an editor, such as vi editor.

    2. 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.

4.4 Database Upgrade Assistant Fails to Stop Oracle9i Database

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:

  1. 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
    
  2. 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 $CRSHome\bin\olsnodes command.

This issue is tracked with Oracle bug 6499906.

4.5 Error in Copying Files While Upgrading Oracle Database 10g Release 2 to Oracle Database 11g

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.

4.6 Help Button is not Working in Oracle Database Installation

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.

4.7 Oracle Database Configuration Assistant Fails to Start

When installing Oracle Database 11g (11.1.0.6.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:

java.lang.UnsatisfiedLinkError: $ORACLE_HOME/lib/libOsUtils.so

Workaround: To resolve this issue, complete the following procedure before starting Oracle Universal Installer or Oracle Database Configuration Assistant:

  1. Run the following command to set the JAVA64FLAG variable:

    $ export JAVA64FLAG="-d64"
    
  2. Start Oracle Universal Installer or Oracle Database Configuration Assistant.

This issue is tracked with Oracle bug 6628285.

4.8 Oracle Enterprise Manager Configuration Fails During Data Guard Rolling Upgrade

When performing Data Guard rolling upgrade from Oracle Database 10g Release 2 (10.2.0.3) using Oracle Database Upgrade Assistant, Oracle Enterprise Manger displays an error message.

This issue is tracked with Oracle bug 6597505.

4.9 Oracle Enterprise Manger Database Control Fails During Database Upgrade

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.

4.10 Oracle Universal Installer Displays a Warning Message

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.

4.11 The /var/opt/oracle/oratab File Lists Multiple Automatic Storage Management Instances

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 /var/opt/oracle/oratab file.

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.

4.12 The *.err File is Created While Removing Automatic Storage Management with Database

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.

5 Other Known Issues

The following sections contain information about issues related to Oracle Database 11g and associated products:

5.1 Reactivate the OC4JADMIN User for Oracle Ultra Search

The 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>

with:

<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

5.2 Same Location for Symbolic links to Oracle Instant Client Libraries Does not Work

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.

5.3 Oracle Clusterware Node Addition in Vendor Cluster Environment

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 rootaddnode.sh script:
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.

6 Documentation Corrections and Additions

None

7 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. 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 http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

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.

Accessibility of Links to External Web Sites in Documentation

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.

TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398. Outside the United States, call +1.407.458.2479.


Oracle Database Release Notes, 11g Release 1 (11.1) for Solaris Operating System

B32067-05

Copyright © 2008, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States 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, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.