| Oracle® Database Release Notes 11g Release 1 (11.1) for Linux Part Number B32001-04 |
|
| View PDF |
| Oracle® Database Release Notes 11g Release 1 (11.1) for Linux Part Number B32001-04 |
|
| View PDF |
Release Notes
11g Release 1 (11.1) for Linux
B32001-04
November 2007
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.
This document contains the following topics:
The latest certification information for Oracle Database 11g Release 1 (11.1) is available on OracleMetaLink at:
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.
Review the following section for information about issues that affect Oracle Database installation, configuration, and upgrade:
Error in Copying Files While Upgrading Oracle Database 10g Release 2 to Oracle Database 11g
The /etc/oratab File Lists Multiple Automatic Storage Management Instances
The ORA-12157 Error Message is Displayed When Using Shared Oracle Home on OCFS2
Installation, Configuration, and Upgrade Issues on Linux x86
Installation, Configuration, and Upgrade Issues on Linux x86-64
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.
If you install Oracle Clusterware on shared Oracle home, the /etc/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 /etc/oratab file.
Workaround: Oracle Universal Installer detects this issue during the prerequisite checks. You can edit the /etc/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 install Oracle RAC in a shared Oracle home on OCFS2, the ORA-12157 error message is displayed for multiple files.
The health check of Oracle database instances and Automatic Storage Management instances by Oracle Clusterware (CRS) does not work correctly if the Oracle database home is installed on a filesystem that does not support memory mapped files, such as OCFS2 on Linux.
Workaround: Oracle Clusterware (CRS) and Oracle Enterprise Manager agent try to access the $ORACLE_HOME/dbs/hc_SID.dat file and the Automatic Storage Management instance tries to access the $ORACLE_HOME/dbs/ab_SID.dat file by using the mmap function. This means that the $ORACLE_HOME/dbs/hc_SID.dat and $ORACLE_HOME/dbs/ab_SID.dat files must be moved to a filesystem that supports the mmap functions on all nodes in the cluster. Complete the following procedure to use a location on the local disk drive to store the file:
Use commands similar to the following on all nodes in the cluster, to copy the files to a local drive:
cp $ORACLE_HOME/dbs/hc_SID.dat /local_dir/hc_SID.dat cp $ORACLE_HOME/dbs/ab_SID.dat /local_dir/ab_SID.dat
Use commands similar to the following to remove the file from the cluster filesystem:
rm $ORACLE_HOME/dbs/hc_SID.dat rm $ORACLE_HOME/dbs/ab_SID.dat
Use commands similar to the following to create a symbolic link to the file in the $ORACLE_HOME/dbs directory:
ln -s /local_dir/hc_SID.dat $ORACLE_HOME/dbs/hc_SID.dat ln -s /local_dir/ab_SID.dat $ORACLE_HOME/dbs/ab_SID.dat
See Also:
Frequently asked question number 49 from thehttp://oss.oracle.com/projects/ocfs2/dist/documentation/ocfs2_faq.html#RAC link for more information about OCFS2This issue is tracked with Oracle bug 4961541.
The following are the Linux x86-specific issues that affect Oracle Database installation, configuration, and upgrade:
Note:
The issues mentioned in this section are observed only on Linux x86.If you are creating a database without using Automatic Storage Management and specify Automatic Storage Management to store backup and recovery data, then Oracle Database Configuration Assistant stops responding.
Workaround: Select Do not enable Automated Backups while creating the database and finish the installation process. After the installation process has finished, run Oracle Database Configuration Assistant and configure Backup and Recovery storage.
This issue is tracked with Oracle bug 6417211.
Oracle Universal Installer intermittently displays Oracle Database Configuration Assistant status as failed even after it finishes the installation process successfully.
This behavior is seen intermittently if you leave Oracle Database installation running for a long time without acknowledging the confirmation dialog shown by Oracle Database Configuration Assistant at the end of the database creation. The configured Oracle database and Oracle Database Control function normally. This error can be safely ignored.
This issues is tracked with Oracle bug 6238219.
The following are the Linux x86-64 specific issues that affect Oracle Database installation, configuration, and upgrade:
Error When Installing Oracle Database 11g on Asianux Server 3
The Oracle Home Directory Structure is Changed for Instant Client
Note:
The issues mentioned in this section are not observed on Linux x86.When installing Oracle Database 11g on Asianux Server 3, the Product-Specific Prerequisite Checks screen reports that the operating system requirement checks fail.
Workaround: Change the contents of /etc/asianux-release from Asianux Server 3 (Quartet) to Asianux release 3 (Quartet).
This issue is tracked with Oracle bug 6457598.
The Product-Specific Prerequisite Checks screen may alter about incorrect value for the rmem_default variable.
Workaround: If you have set the value for the variable according to the installation guide, you can ignore this alert by selecting the check box available against it and continue with the installation process.
This issue is tracked with Oracle bug 6445078.
In the earlier releases, the $ORACLE_HOME/lib directory contained all the libraries. However, when installing Oracle Database Instant Client, the 32-Bit libraries are missing from the installation. To resolve this issue, $ORACLE_HOME/lib32 directory is added to the directory structure to store the 32-Bit libraries.
This issue is tracked with Oracle bug 6338225.
The following sections contain information about issues related to Oracle Database 11g and associated products:
If Oracle Enterprise Manager Database Control is running on Oracle Enterprise Linux 5 or Red Hat Enterprise Linux 5, Metric Collection Error is displayed for the CPU Usage metric. Due to this issue, the CPU usage information for the host is not displayed. Therefore, you cannot set alert threshold on the host CPU usage.
This issue is tracked with Oracle bug 6316367.
SQL*Plus and Oracle Call Interface (OCI) program calls fail with SELinux in the Enforcing mode on Oracle Enterprise Linux 5.0 and Red Hat Enterprise Linux 5.0. Refer to the OracleMetaLink note 454196.1 for more details about the issue.
Workaround: Shift SELinux to Permissive mode on the system.
This issue is tracked with Oracle bugs 6140224 and 6342166.
When you click the Host Administration tab of the Oracle Enterprise Manager Database Control on Oracle Enterprise Linux 5, the following error is displayed:
This feature is only available on hosts running Red Hat Linux and SUSE Linux Operating Systems.
Due to this issue, you cannot administer the host using Oracle Enterprise Manager Database Control on Oracle Enterprise Linux 5.
This issue is tracked with Oracle bug 6316469.
The use of the client static library is not supported.
On Red Hat Enterprise Linux 5 and SUSE Linux Enterprise Server 10, standard C header files may contain symbols, such as __LDBL_REDIR1_DECL, which Pro*C parser fails to recognize.
Workaround: You can use one of the following code in the .pc files so that the header file does not get included during precompilation:
#ifndef ORA_PROC
#include <filename.h>
#endif
or
#ifdef ORA_PROC #define _HEADERFILENAME_H__ #endif
This issue is tracked with Oracle bug 6142780.
When installing Oracle Database 11g, Oracle Universal Installer removes third party library paths from the LD_LIBRARY_PATH variable for security reasons. Due to this, the relinking of the rtsora file fails during installation. The rtsora file can be relinked by updating the LD_LIBRARY_PATH variable with the path where Cobol libraries are available and calling an appropriate make target. You can use the following commands to make the rstora file:
$ cd $ORACLE_HOME/precomp/lib $ make -f ins_precomp.mk rtsora
When uploading patches through Oracle Enterprise Manager Database Control using the Mozilla Firefox 1.5 Web browser on Linux, the Web browser window crashes.
Workaround: Start the Mozilla Firefox 1.5 Web browser client from a non-Linux environment or use an alternate Web browser, such as Internet Explorer.
This issue is tracked with Oracle bug 6008421.
Use the following procedure to create block device partitions:
Use fdisk to create disk partitions on block devices for database files
On each node, create or modify the permissions file in /etc/udev/permissions.d, to change the permissions of the datafiles from default root ownership. On Asianux 2, Oracle Enterprise Linux 4, and Red Hat Enterprise Linux 4, this file should be called 49-oracle.permissions, so that the kernel loads it before the 50-udev.permissions file. On Asianux Server 3, Oracle Enterprise Linux 5, Red Hat Enterprise Linux 5, and SUSE Linux Enterprise Server 10, this file should be called 51-oracle.permissions, so that the kernel loads it after the 50-udev.permissions file.
For each partition, use the following syntax in the xx-oracle.permissions to set access permissions:
devicepartition:oracle_db_install_owner:OSDBA:0660
You can also use raw logical volumes as shared storage media for Oracle Database files. After you have created the required partitions, you must bind the partitions to raw devices on every node. However, you must first determine what raw devices are already bound to other devices. Refer to the "5.6.4 Using Raw Logical Volumes on Linux" section of Chapter 5, "Configuring Oracle Real Application Clusters Storage" in Oracle Clusterware Installation Guide for Linux for the procedure to be followed to use raw logical volumes as shared storage media for Oracle Database files.
The following are the Linux x86-64 specific known issues:
Note:
The issues mentioned in this section are not observed on Linux x86.If you use ZH_TW, ZH_CN, or KO_KR locales, the locale builder screen may display multibyte words as square boxes. This is a known JDK font issue for the east Asian languages.
This issue is tracked with Oracle bug 6446186.
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
When compiling 32-bit demonstrations using the $ORACLE_HOME/rdbms/demo/demo_rdbms32.mk file, the make utility displays the following error message:
demo_rdbms32.mk:302: *** missing separator (did you mean TAB instead of 8 spaces?). Stop.
Workaround: Complete the following procedure to resolve this issue:
Open the demo_rdbms32.mk file in a text editor, such as vi editor.
Replace 8 spaces in the beginning of lines 302 and 305 with a Tab space.
This issue is tracked with Oracle bug 6432737.
This section contains the corrections and additions to the content available in the documentation set available with this release.
The following products are required if you want to use PRO*COBOL. These products are missing in the list available in the Oracle Database Client installation and quick installation guides:
Acucorp ACUCOBOL-GT 6.2
Micro Focus Server Express 4.0 SP2
The following kernel parameters should be added to the lists available in the Configuring Kernel Parameters section in the Oracle Database installation and quick installation guides:
The table listing the recommended values for the kernel parameters in the section should contain the following rows:
| Parameter | Value | File |
|---|---|---|
| tcp_wmem_default | 262144 | /proc/sys/net/ipv4/tcp_wmem_default |
| tcp_wmem_max | 262144 | /proc/sys/net/ipv4/tcp_wmem_max |
| tcp_rmem_default | 262144 | /proc/sys/net/ipv4/tcp_rmem_default |
| tcp_rmem_max | 4194304 | /proc/sys/net/ipv4/tcp_rmem_max |
The table listing the commands to display the values of the kernel parameters in the section should contain the following rows:
| Parameter | Command |
|---|---|
| tcp_wmem_default | # /sbin/sysctl -a | grep tcp_wmem_default |
| tcp_wmem_max | # /sbin/sysctl -a | grep tcp_wmem_max |
| tcp_rmem_default | # /sbin/sysctl -a | grep tcp_rmem_default |
| tcp_rmem_max | # /sbin/sysctl -a | grep tcp_rmem_max |
The list of parameters and their values in the /etc/sysctl.conf file should also contain the following entries:
net.ipv4.tcp_wmem_default = 262144 net.ipv4.tcp_wmem_max = 262144 net.ipv4.tcp_rmem_default = 262144 net.ipv4.tcp_rmem_max = 4194304
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.
Oracle Database Release Notes, 11g Release 1 (11.1) for Linux
B32001-04
Copyright © 2007, 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.
