| Oracle® Database Release Notes 10g Release 2 (10.2) for Solaris Operating System (x86-64) Part Number B15703-04 |
|
| View PDF |
| Oracle® Database Release Notes 10g Release 2 (10.2) for Solaris Operating System (x86-64) Part Number B15703-04 |
|
| View PDF |
Release Notes
10g Release 2 (10.2) for Solaris Operating System (x86-64)
B15703-04
March 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 and may be updated after it is released.
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 10g release 2 (10.2) is available on OracleMetaLink at:
The following products are not supported with Oracle Database 10g release 2 (10.2):
Grid Control Support
Oracle Database 10g release 2 (10.2) can be managed as a target by Grid Control 10.1.0.4. However, Oracle Database 10g release 2 is not supported by Grid Control 10.1.0.4 as a repository.
JDBC 1.2 driver
JDBC 1.2 driver is not supported on Solaris 10
Radius with the CHAP protocol
Verity
Verity filters used for Oracle Text are not supported on Solaris 10.
Refer to the installation guides for the preinstallation requirements.
This section lists the following corrections to the installation guides for Solaris operating System (Solaris x86-64):
The second note under the "Configuring Kernel Parameters" section incorrectly refers to System V TPC. However, the correct reference is System V IPC.
In the "Configuring Kernel Parameters" section of the Database Quick Installation Guide and Preinstallation Tasks chapter of the installation guide for this platform contains the procedure for changing the kernel parameters on Solaris 10. However, if you set the kernel parameters using this procedure, the values are lost when you restart the system. To make the values available after the system restart, use the following procedure to change the kernel parameters:
By default, Oracle instances are run as the oracle user of the dba group. A project with the group.dba name is created to serve as the default project for the oracle user. Run the id command to verify the default project for the oracle user:
# su - oracle $ id -p uid=100(oracle) gid=100(dba) projid=100(group.dba) $ exit
To set the maximum shared memory size to 2 GB, run the projmod command:
# projmod -sK "project.max-shm-memory=(privileged,2G,deny)" group.dba
Alternatively, add the project.max-shm-memory=(privileged, 2147483648,deny) resource control to the last field of the project entries for the Oracle project.
After these steps are complete, the /etc/project file should contain the following:
# cat /etc/project
The following is the output of the command:
system:0:::: user.root:1:::: noproject:2:::: default:3:::: group.staff:10:::: group.dba:100:Oracle default project:::project.max-shmmemory=(privileged,2147483648,deny)
To verify that the resource control is active, run the id and prctl commands:
# su - oracle
$ id -p
uid=100(oracle) gid=100(dba) projid=100(group.dba)
$ prctl -n project.max-shm-memory -i process $$
process: 5754: -bash
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-memory
privileged 2.00GB - deny
Note:
For additional information, refer to the Solaris Tunable Parameters Reference Manual.The table in the "Checking Software Requirements" section of Chapter 2 in instalaltion guides for Solaris Operating System (x86-64) displays Sun One Studio 10 (c and C++ 5.5) and gcc 3.4.2 as a requirement for PL/SQL native compilation, Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK), GNU Compiler Collection (GCC). However, this row should be spilt into the following two rows:
| Item | Requirement |
|---|---|
| PL/SQL native compilation | One of the following:
|
| Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK), GNU Compiler Collection (GCC) | Sun ONE Studio 10 (C and C++ 5.7) |
The "Checking Software Requirements" section of Chpter 2 in Oracle Database Installation Guide for Solaris Operating System (x86-64) does not specify the command to verify the update level of the operating system. You can use the following command to verify the update level of the operating system:
$ cat /etc/release Solaris 9 4/03 s9s_u3wos_
In the output of the command, _u3 refers to update 3 of Solaris 9.
In Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide, Chapter 2, "Preinstallation," in the section "Oracle Clusterware Home Directory," it incorrectly lists the path /u01/app/oracle/product/crs as a possible Oracle Clusterware home (or CRS home) path. This is incorrect. A default Oracle base path is /u01/app/oracle, and the Oracle Clusterware home must never be a subdirectory of the Oracle base directory.
A possible CRS home directory is in a path outside of the Oracle base directory. for example, if the Oracle base directory is u01/app/oracle, then the CRS home can be an option similar to one of the following:
u01/crs/ /u01/crs/oracle/product/10/crs /crs/home
This issue is tracked with Oracle bug 5843155.
Review the following sections for information about issues that affect Oracle Database installation, configuration, and upgrade:
To install Oracle Security Manager, install Oracle Client and then select the Administrator installation type.
Oracle Universal Installer displays an error message that reads 0. This message is displayed after you specify the database home and path in the Specify Home Details screen and click Next. Ignore the error message whenever it is displayed, and continue the installation.
To enable the extjob executable to locate required libraries, the $ORACLE_HOME/lib directory and all of its parent directories must have execute permissions for group and other.
When modifying the name, IP address, or netmask of an existing virtual IP address (VIP) resource, use the srvctl modify nodeapps command and include the existing interfaces for the VIP in the -A argument. For example:
srvctl modify nodeapps -n mynode1 -A 100.200.300.40/255.255.255.0/eth0
This issue is tracked with Oracle bug 4500688.
The following sections contain information about issues related to Oracle Database 10g and associated products:
Importing a User Certificate Into Oracle Wallet Using Oracle Wallet Manager
Node Names do not Reflect in the Specify Cluster Nodes to Add to Installation Dialog Box
When the query has single column in-lists, the materialized view has ranges, and partition change tracking rewrite is used, you might get stale results with Query Rewrite. Turn off the fresh partition containment rewrite to avoid this problem by using the following command:
SQL> alter session set "_query_rewrite_fpc" = false;
The host-based mirroring is not supported with ASM. Note that there is no issue with resilvering for storage based mirroring.
Workaround: Use ASM redundancy.
This issue is tracked with Oracle bug 4466206.
Oracle ODBC driver for Solaris does not work if you use the REAL data type for a column and the application tries to retrieve data as native double or float data type through PL/SQL stored procedure.
Workaround: Instead of the REAL data type, use the NUMBER(s,p) data type while creating a table.
This issue is tracked with Oracle bug 4551566.
Oracle Wallet Manager will fail to recognize the user certificate as valid if you capture the user certificate contents from the Oracle Certificate Authority site and save this as a flat file. This is because when saving as a flat file, all the lines of the user certificate are run together with no line breaks.
Workaround: Edit the user certificate. Insert a new line after -----BEGIN CERTIFICATE----- and a new line before -----END CERTIFICATE-----.
Do not remove the key values for the wait class metrics. Doing so removes them permanently and currently there is no easy way to recover them.
This issue is tracked with Oracle bug 4602952.
If a storage area network (SAN) device is used to provide access to a shared storage and IO Multi-pathing (MPxIO) is enabled, then you must install the following patches on all the nodes of the cluster.
119375-13
119716-10
Without these patches, a node can lose access to the shared storage being accessed through the physical link that gets disconnected or fails.
In Solaris 10 update 1, the boot archive service is introduced. The main purpose of this service is to reduce the boot time and simplify the boot loader. Due to an aggressive shutdown, the boot archive verification service may require manual intervention during boot.
During a patch installation or software upgrade, if you do not shutdown the computer properly, then kernel modules are reported to be out of sync. In such a case, start the computer to the fail-safe menu entry, follow the prompts to re-sync the archive, and then reboot. If you do not want the manual intervention, you can disable the check by running the following commands:
# svcprop -p start/exec boot-archive:true # svcadm refresh boot-archive
However, if the kernel modules are not reported to be out of sync, then you can clear the check by logging into the single user shell and running the following command:
# svcadm clear boot-archive
It is possible to disable the boot archive check on production computer to avoid manual intervention during aggressive reboots. To do so, the patch application and installation of driver or kernel software must be followed by a boot archive update. The kernel software includes the non-Solaris kernel modules.
The boot archive update can be achieved by applying a graceful reboot or an explicit re-sync of the boot archive by running the following command:
bootadm update-archive
Oracle recommends that you remove the node from the cluster before patch installation and software installation or upgrade. When using CRS this can be done by completing the following steps:
Stop the CRS service by using the following command:
$CRS_HOME/bin/crsctl stop crs
Disable the CRS service by using the following command:
$CRS_HOME/bin/crsctl disable crs
Install or upgrade the required patch or software
Reboot or re-sync the boot archive
Enable the CRS service by using the following command:
$CRS_HOME/bin/crsctl enable crs
Start the CRS service by using the following command:
$CRS_HOME/bin/crsctl start crs
Complete the following steps to remove the node from the cluster if you are using using Sun Cluster:
Reboot the node in the maintenance mode
See Also:
Sun Cluster documentation for details on rebooting a node in maintenance modeInstall or upgrade the required patch or software
Reboot the node in the cluster mode
A fix for the boot archive service will be integrated in a future Solaris 10 update. After this fix is in place there will be no need to disable the check or to provide manual intervention during a reboot. The boot archive check can be re-enabled by running the following commands:
# svccfg -s boot-archive setprop start/exec=/lib/svc/method/boot-archive # svcadm refresh boot-archive
When the Solaris fiber channel port driver senses that a link is down, it gives two minutes timeout period before offlining the LUN path associated with the port. The purpose of this delay is to prevent a premature fail over in as a result of a transient link failure. If there are alternate active paths to the LUNs and SCSI reservations are not active, then within this timeout MPxIO automatically reconfigures to use the alternate path.
However, during this timeout period the port failure is not perceived by CRS because the path is not offlined. If the node is evicted during this timeout period, the CRS daemons fail to reboot the node and services will not fail over to other nodes. In this case, the node will reboot only until the link is up again. After the reboot, all services belonging to the node will be up.
To avoid this problem the misscount parameter must be set to a value greater than 120 seconds. As a result, the eviction and reboot process is not affected by the Solaris timeout period. The node is evicted, it reboots and its services fail over to other nodes as expected.
After CRS installation is complete, you can change the misscount parameter by completing the following steps:
On any node run the $CRS_HOME/bin/crsctl set css misscount 130 command.
On all nodes run the $CRS_HOME/bin/crsctl stop crs command.
On all nodes run the $CRS_HOME/bin/crsctl start crs command.
The default value for the misscount parameter is 27. Increasing the value of this parameter increases the time the node takes to fail over. Therefore, the service level of the cluster reduces for a longer period of time. It is up to the user to decide if a longer fail over time is acceptable. Solaris has a mechanism in place to allow applications to be notified immediately of a link down.
In this release, Oracle is not using this mechanism but work is in progress to make use of this mechanism. In a future Oracle release this workaround will no longer be needed.
In the Specify Cluster Nodes to Add to Installation dialog box, an intermittent timing issue is observed. This dialog box prompts you to enter Public Node Names, Private Node Names, and Virtual Node Names for the new nodes to be added. Even after entering the node names, the configuration specified does not reflect in the install area. To avoid this issue, you need to press Tab after the last input to this dialog box.
Do not click the link to the Monitor in Memory Access Mode feature in the database screen. This feature is not available in Enterprise Manager Database Control 10.2.0.2 release. Clicking this link may stop an agent from responding.
This issue is tracked with Oracle bug 4866231.
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, 10g Release 2 (10.2) for Solaris Operating System (x86-64)
B15703-04
Copyright © 2006, 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.
