Critical Patch Update Release Notes
Release 9.2.0.7
April 18, 2006
These release notes include the following sections:
Section 1, "Introduction"
Section 2, "Requirements"
Section 3, "Bugs Fixed by this Patch"
Section 4, "OPatch Utility Information"
Section 5, "Patch Installation Instructions"
Section 6, "Patch Deinstallation Instructions"
Section 7, "Documentation Accessibility"
Database Server Patch for Oracle Critical Patch Update April 2006 is an OPatch utility installable bundle for components in the data server and client. This patch should be applied to the Oracle home for the Database.
This document guides your through the Installation, Post Installation Actions and optionally, De-Installation steps required for Oracle Critical Patch Update April 2006 Database Server Patch. Failure to carefully read and understand these steps may result in your applying a patch that can cause your Oracle Installation to malfunction, including interruption of service and/or loss of data.
If you do not meet all of the following requirements, log an iTAR, so that an Oracle support analyst may review your situation. The Oracle analyst will help you determine if this patch is suitable for you to apply to your system. We recommend that you avoid applying any temporary patch unless directed by an Oracle Support Analyst who has reviewed your system and determined that it is applicable.
|
Note: You are required to read the Advisory and Pre-installation Note for Critical Patch Update - April 2006 before you proceed. |
Your system configuration must exactly match the following requirements:
Patch for Base Bug: 5049060
Patch for Platforms:
Linux
Linux x86-64
Solaris Operating System (SPARC)
Product Release: 9.2.0.7
Product Patched: Oracle Database
Components patched:
Oracle ConText
NETWORK
SDO
NLSRTL
mod_plsql release 3.0.9.8.5
This section lists bugs fixed by this patch.
5049060 - MLR ON TOP OF 9.2.0.7 FOR CPUAPR2006.
5049062 - SECURITY BUG FOR 9.2.0.7 FOR CPUAPR2006
5021058 - MLR ON TOP OF 9.2.0.7 FOR CPUJAN_MERGE
4754842 - SECURITY BUG FOR 9.2.0.7 FOR CPUJAN2006
4567971 - SECURITY BUGS FIXED IN CPUOCT
4567854 - MLR ON TOP OF 9207 FOR CPUOCT2005
4547641 - SECURITY BUGS FIXED IN CPUJUL
4547566 - MLR ON TOP OF 9.2.0.7 FOR CPUJUL2005
4516151 - SQLSERVER STREAMS GIVES ERROR IF DML HAS NULLS FOR DATE COLUMN
4121749 - ORA-21779 DURATION NOT ACTIVE ERROR - TABLE FUNCTION
4049345 - EFFORT REPRESENTATIVE BUG - OHS_CPU_1 FOR 9.2
2701372 - DTDS AND SOAP (SEC ALERT 65)
You must use the OPatch utility release 1.0.0.0.55 or later. It can be
downloaded from OracleMetaLink with Patch 2617419. The
minimum version of the OPatch utility required is 1.0.0.0.55.
You must have Perl 5.00503 (or later) installed under the ORACLE_HOME, or elsewhere within the host environment. OPatch is no longer included in patches as of 9.2.0.2. Refer to the following link for details on Perl and OPatch: Doc ID 189489.1
Prior to the patch installation, the following checks are performed
Conflicts with other patches
Conflicts with subset patches (existing patch is a subset of the patch being installed)
If a conflict is found, then stop the installation and contact Oracle Support Services.
If a subset is found, then continue the installation. All fixes for the subset patch are included in the patch being installed. The subset patches will be automatically rolled back prior to the installation of the new patch.
If the Oracle inventory is not setup correctly this utility will fail. To check accessibility to the inventory you can use the command
% opatch lsinventory
Follow these steps:
Review the 'Known Issues' section in the Pre-installation Note for Critical Patch Update - April 2006 before proceeding with the patch installation. (OracleMetaLink Note 360465.1).
Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
Ensure that the $PATH has the following executables:
make, ar, ld, and nm.
Check whether the java and jar executables are
present in your Oracle home.
In a standard Oracle installation, java is available in
$ORACLE_BASE/jre/JDK
version/bin directory and jar is
available in "$ORACLE_HOME/jdk/bin directory. By default, the
OPatch utility uses the executables from these locations. However, if they are
located elsewhere, you can use the opatch apply command with the
-jdk flag, and then specify the full path to the JDK to be used.
For more information, refer to OPatch User's Guide,
which is available with the OPatch utility distribution.
If you are using a Non-RAC Database, then follow the below instructions to apply the CPU patch.
To apply the patch, set your current directory to the directory where the patch is located and then run OPatch by entering the following command.
cd 5049060
opatch apply
If there are errors, refer to the "Known Issues" section in the Pre-installation Note for Critical Patch Update - April 2006.
Follow these steps:
Start all database instances running from the Oracle home that you are patching.
For each database instance running of the Oracle home being patched,
connect to the database using SQL*Plus. Connect as SYSDBA and run
the catcpu.sql script as follows:
|
Note: Due to changes in the installation scripts, it
is no longer a requirement to startup the database in
|
cd $ORACLE_HOME/cpu/CPUApr2006
sqlplus /nolog
SQL> CONNECT /AS SYSDBA
SQL> STARTUP
SQL> @catcpu.sql
SQL> QUIT
Check the log file for any errors.
If there are errors, refer to the "Known Issues" section in the Pre-installation Note for Critical Patch Update - April
2006. If catcpu.sql reports any Invalid Objects, run the
following commands:
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT /AS SYSDBA
SQL> STARTUP
SQL> @utlrp.sql
You can check for any invalid objects by executing following statement:
SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS= 'INVALID';
If you are not using the RAC Installations for Oracle9i Database Release 2, then you can skip to next section.
Note that 9.2.0.7 CPUApr2006 patch is not certified for RAC Rolling upgrade. So you can not apply or rollback this patch in the rolling node fashion.
Follow these steps:
Shut down all nodeapps services on all the nodes by repeating the following command on each node:
srvctl stop nodeapps -n <node-name>
Shut down all instances and listeners on all the nodes.
Apply the patch to the Oracle Home on all the nodes as follows:
cd 5049060
opatch apply
If there are errors, refer to the "Known Issues" section in the Pre-installation Note for Critical Patch Update - April 2006.
Select one node to execute the post installation steps. Follow the same set of instructions under "Post-installation Instructions for a Non-RAC Database".
Make sure that no users access the selected instance, and that all other instances are shut down.
Follow these steps:
Restart instances on all nodes.
Restart all nodeapps services on all nodes, one at a time:
srvctl start nodeapps -n <node-name>
You do not need to run post installation steps again on the other nodes.
Follow these steps:
Set your current directory to the directory where the patch is located, for example:
cd 5049060
Run OPatch using the rollback argument. For example:
opatch rollback -id 5049060
If there are errors, refer to the "Known Issues" section in the Pre-installation Note for Critical Patch Update - April 2006.
Follow these steps:
Start all database instances running out of the Oracle home that you are patching.
For each of these database instances, connect to the database using
SQL*Plus as SYSDBA, and then run catcpu_rollback.sql as follows:
cd $ORACLE_HOME/cpu/CPUApr2006
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catcpu_rollback.sql
SQL> QUIT
Check the log file for errors. If there are errors, refer to the refer to the 'Known Issues' section in the Pre-installation Note for Critical Patch Update - April 2006.
If catcpu_rollback.sql reports invalid objects, compile the
invalid objects using the following commands. (Note that for a large number of
objects, this compilation step can take a long time.)
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql
To check for invalid objecs, execute the following statement:
SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID';
Follow these steps:
Shut down all nodeapps services on all the nodes by repeating the following command on each node:
nodeapps -n <node-name>
Shut down all instances and listeners on all the nodes.
Rollback the patch to the Oracle Home, on all the nodes following the steps.
opatch rollback -id 5049060
If there are errors, refer to the "Known Issues" section in the Pre-installation notes for Critical Patch Update - April 2006.
Follow these steps:
Go to the node where you ran the "Post-installation Instructions for RAC Database" instructions.
Follow the instructions described under "Post Deinstallation Instructions for Non-RAC Database".
Make sure that no users can access the selected single instance.
Shut down all other instances.
Restart instances on all nodes.
Restart all nodeapps services on all nodes, one at a time:
srvctl start nodeapps -n <node-name>
You do not need to run post installation steps again on other nodes.
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. 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 additional information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation JAWS, a Windows screen reader, 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, JAWS 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.
Oracle Database Critical Patch Update Release Notes, Release 9.2.0.7
Copyright © 2005, 2006, 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.