| Clustered Database Platform 280/3 With Oracle9i Database RAC Release Notes |     |
| Clustered Database Platform 280/3 With Oracle9i Database RAC Release Notes | |
|
Clustered Database Platform 280/3 Release Notes |
This document contains the release notes for the Clustered Database Platform 280/3 system. These issues were known at the time of the production of the documentation.
This section contains the known issues at the time when the Clustered Database Platform 280/3 documents were produced.
If you want to correct the ANSI JOIN feature introduced in the Oracle9i software the software must be patched with Patchset 2271678, followed by Patch Number 2121935. You can obtain the patches from the Oracle Metalink website. The Patch Number is the same the Bug number, 2121935, that it fixes.
Oracle Security Product Management has released new security alerts. To view the alerts, log in to the Metalink site at http://metalink.oracle.com. Use the advanced search option to retrieve the documents by identification number.
The Solaris
Operating Environment Media Kit includes the Oracle9i installation CDs. If you are using the Oracle8i client on an existing workstation, you must upgrade to Oracle9i by using the Oracle software CDs.
In the Clustered Database Platform 280/3 software, the $ORACLE_HOME variable is a symbolic link. The only time you should set $ORACLE_HOME variable to the directory pointed to by the /export/home/oracle link (for example, /export/home/oracle_base/product/9.0.1_32b) is when you apply a patchset using the Oracle Universal Installer. Patches are registered in the Oracle inventory, which is maintained on a product-by-product basis. Otherwise, you must refer to $ORACLE_HOME as /export/home/oracle in the $HOME/.profile, $HOME/.cshrc, or /var/opt/oracle/oratab files.
As indicated in Oracle Security Alert No. 29 (Metalink Document ID 175429.1), there is "a potential security vulnerability in the Oracle PL/SQL package for External Procedures (EXTPROC)." For this reason the Clustered Database Platform 280/3 system comes with the EXTPROC functionality disabled. Specifically, the /export/home/oracle/bin/extproc has been renamed to /export/home/oracle/bin/extproc_SAVED, and its executable bits have been turned off. If you require the use of External Procedures, perform the follow steps as user oracle:
$ cd $ORACLE_HOME/bin $ mv extproc_SAVED extproc $ chmod +x extproc |
You must then follow the workaround procedures described in Security Alert No. 29 to safely set up the EXTPROC functionality.
Typically, when connecting from a remote client to Oracle9i RAC, you set the TWO_TASK environment variable to the RAC service name to which you would like to connect (for example, ORCL). However, as outlined in Oracle Metalink Doc. ID 97926.1, using TWO_TASK when connecting through SQL*Plus causes the TAF feature of the connection to be disabled.
If you need to make a TAF-enabled connection to the RAC database service, do not set TWO_TASK. Instead, specify the service name on the command line using the @ symbol, as in the following example.
$ sqlplus mary@ORCL/mypassword |
Specifying the service name on the command line will ensure that your connection is TAF-enabled.
The following Sun and Oracle software bugs were known to exist at the time the documents were published.
The following bugs are known to exist in the Clustered Database Platform software version 1.0:
The Oracle software is using the oratab file for two, distinct purposes. In the /etc/init.d/dbora file, the name of the instance is used to control start-up and shutdown by using the dbstart and dbshut scripts. However, the OEM agent needs it to be the database name instead.
Workaround: Edit the /var/opt/oracle/oratab file on each node. Substitute orcl where either orcl1 or orcl2 appear in the file. Stop, and restart the Intelligent Agent on each node. Then, delete the nodes in the Intelligent Agent, and perform discovery again in the OEM. You should then see the orcl instance. Under that name, choose Instance, and you should see the Cluster Database Instances folder, as documented in the Oracle9i RAC Administration Guide.
The Top SQL utility reports SQL statistics for the non-clustered databases, but it displays the following message if you try to connect to the clustered database:
The TOP SQL chart is only available for database targets
Workaround: Place the cursor on the instance icon (either orcl1 or orcl2 with in the orcl database hierarchy to view the SQL statistics.
The following bug is known to exist in the Oracle9i software:
If you want to correct the ANSI JOIN feature introduced in the Oracle9i software, the software must be patched with Patchset 2271678, followed by Patch Number 2121935.
Workaround: You can obtain the patches from the Oracle Metalink website. The Patch Number is the same the Bug number, 2121935, that it fixes.
This section contains the known errors in the documentation at the time of the product release.
In the Clustered Database Platform 280/3 system Operations Guide (online on the management server), the "Moving the Oracle Software" page and the "Applying Oracle Patchsets" page contain a typographical error. Both pages have lsnrct as the Listener command name. The correct name is lsnrctl.
In the Clustered Database Platform 280/3 system Operations Guide (online on the management server), the "Changing the Oracle User and Group IDs" page contains the following code line:
exec chown oracle:oinstall `\} \; |
| Clustered Database Platform 280/3 With Oracle9i Database RAC Release Notes | 816-4077-10 | |
Copyright © 2002, Sun Microsystems, Inc. All rights reserved.