Oracle Critical Patch Update January 2006
Release Notes for Oracle Database Server Version 9.2.0.7

Release Date: January 17th, 2006

Note:   You are required to read the Advisory and Pre-installation notes for Critical Patch Update - January 2006 before you proceed. 

CONTENTS

Introduction
Requirements
Bugs Fixed by this patch
OPatch information
Patch Installation Instructions 
Patch Deinstallation Instructions


Introduction


Database Server Patch for Oracle Critical Patch Update January 2006 is an opatch 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, please 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.


Requirements


Your system configuration (Oracle Server version and patch level, OS Version) must exactly match those listed below.

Patch for Base Bug:    4751923
Patch for Platforms:   Sun SPARC SOLARIS, Linux, HP-UX, HP Tru64, AIX
Product Version:        9.2.0.7
Product Patched:        RDBMS, NETWORK, CONTEXT, NSLRTL, Modplsql ( 3.0.9.8.5 )


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


Bugs Fixed by this patch

4754842: SECURITY BUG FOR 9.2.0.7 FOR CPUJAN2006
4567971:SECURITY BUGS FIXED IN CPUOCT
4547641:SECURITY BUGS FIXED IN CPUJUL

4049345:EFFORT REPRESENTATIVE BUG - OHS_CPU_1 FOR 9.2
2701372:DTDS AND SOAP (SEC ALERT 65)
4567854:MLR ON TOP OF 9207 FOR CPUOCT2005
4547566:MLR ON TOP OF 9.2.0.7 FOR CPUJUL2005
4751923: MLR ON TOP OF 9.2.0.7  FOR CPUJAN2006.


OPatch information

For further details regarding OPatch, see Metalink article Doc ID: 293369.1 OPatch Documentation
Prior to the Install Phase, 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, please abort the install and contact Oracle Support Services
If a subset is found, please continue the install, as all fixes for the subset patch are included in the patch being installed.  The subset patch(s) will be automatically rolled back prior to the installation of the new patch.
You must use OPatch version 1.0.0.0.54 or later. It can be downloaded from Metalink with Patch#2617419. (The minimum version of OPatch required is 1.0.0.0.54)
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

Patch Installation Instructions


Please review the ‘Known Issues’ section in the Pre-installation notes for Critical Patch Update - January 2006  before proceeding with the patch installation.
(Note Id : 333956.1:Oracle CPUJan2006 Pre-Installation for Oracle Database Server)


To apply this patch, you must shutdown all instances and listeners associated to the ORACLE_HOME being updated.
The following executables must be present in the $PATH: make, ar, ld, and nm.

Before starting the installation check whether "java" and "jar" executables are present in your Oracle Home. In a standard Oracle installation,

"java" is available in "$ORACLE_HOME/jre/<JDK version>/bin" directory and "jar" is available in "$ORACLE_HOME/jdk/bin" directory. By default, "opatch" uses the executables from these

locations.

If you don't have a standard installation (e.g., you may have installed through an Oracle E-Business Suite Rapid Install) and these commands are not present, then invoke

the "opatch apply" command with the -jdk flag, specifying the full path to the JDK  to be used. For more information see the Opatch Users Guide release with the Opatch distribution.


Set your current directory to the directory where the patch is located and then run opatch by entering the following command:

cd 4751923
opatch apply

If you encounter any errors, please refer to the ‘Known Issues’ section in the Pre-installation notes for Critical Patch Update - January 2006

Post Installation Instructions


Instructions for Clustered Database

If you are not using the RAC Installations for Oracle9i Database Release 2, then you can ignore the rest of this section and skip to next.

If applying CPUJan2006 to a cluster database, set the CLUSTER_DATABASE initialization parameter to FALSE before running the steps in Post Installation Instructions and set it back to TRUE after the steps are completed.

       1. Shut down all instances.
       2. Reset the CLUSTER_DATABASE parameter to false on one  instance. If you are using the server parameter file, make a sid-specific entry for this. (Please refer to Real Application Clusters Administration guide for details)
       3. Start the instance on which you have set CLUSTER_DATABASE to false.
       4. Complete the steps in the Post Installation Instructions as given in next "
Instructions for Single Instance Database" section.
       5. Shut down the instance.
       6. Change the value of the CLUSTER_DATABASE parameter to true.
       7. Restart your instances

Instructions for Single Instance Database

Start up all database instances running out of the ORACLE_HOME being patched.

For each database instance running out of the ORACLE_HOME being patched,
connect to the database using Sqlplus as sysdba and run catcpu.sql as follows –

Note: Due to changes in the installation scripts, it is no longer a requirement to startup the database in MIGRATE mode.

cd $ORACLE_HOME/cpu/CPUJan2006

sqlplus /nolog

SQL> connect / as sysdba

SQL> STARTUP

SQL> @catcpu.sql

SQL> QUIT


Inspect the logfile for any errors. If you have encountered any errors, please refer to the ‘Known Issues’ section in the Pre-installation notes for Critical Patch Update - January 2006

If catcpu.sql reports any Invalid Objects, Oracle recommends that you compile the invalid objects using the following;

(Please note that for large numbers of objects, this compilation step can take some time.

If this patch is being applied through the Enterprise Manager console, you will be prompted to run this compilation script. )


cd $ORACLE_HOME/rdbms/admin

sqlplus /nolog

SQL> connect / as sysdba

SQL> @utlrp.sql


You can check for any invalid objects by executing following statement;


SQL> select OBJECT_NAME from DBA_OBJECTS where status = 'INVALID';


Patch Deinstallation Instructions

To de-install the patch, set your current directory to the directory where the patch is located and then run opatch by entering the following command:

cd 4751923
opatch rollback -id 4751923


If you encounter any errors, please refer to the ‘Known Issues’ section in the Pre-installation notes for Critical Patch Update - January 2006

Post Deinstallation Instructions (Note: Follow post deinstallation instructions only if post-install instructions were followed)


Instructions for Clustered Database

If you are not using the RAC Installations for Oracle9i Database Release 2, then you can ignore the rest of this section and skip to next.

If rolling-back CPUJan2006 to a cluster database, set the CLUSTER_DATABASE initialization parameter to FALSE before running the steps in Post Deinstallation Instructions and set it back to TRUE after the steps are completed.

       1. Shut down all instances.
       2. Reset the CLUSTER_DATABASE parameter to false on one  instance. If you are using the server parameter file, make a sid-specific entry for this. (Please refer to Real Application Clusters Administration guide for details)
       3. Start the instance on which you have set CLUSTER_DATABASE to false.
       4. Complete the steps in the Post Deinstallation Instructions as given in next
"Instructions for Single Instance Database" section.
       5. Shut down the instance.
       6. Change the value of the CLUSTER_DATABASE parameter to true.
       7. Restart your instances

Instructions for Single Instance Database

Start up all database instances running out of the ORACLE_HOME being roll backed.

For each database instance running out of the ORACLE_HOME being roll backed,
connect to the database using Sqlplus as sysdba and run catcpu_rollback.sql as follows -

cd $ORACLE_HOME/cpu/CPUJan2006

sqlplus /nolog

SQL> connect / as sysdba

SQL> STARTUP

SQL> @catcpu_rollback.sql

SQL> QUIT


Inspect the logfile for any errors. If you have encountered any errors, please refer to the ‘Known Issues’ section in the Pre-installation notes for Critical Patch Update - January 2006

If catcpu.sql reports any Invalid Objects, Oracle recommends that you compile the invalid objects using the following;

(Please note that for large numbers of objects, this compilation step can take some time.

If this patch is being applied through the Enterprise Manager console, you will be prompted to run this compilation script. )


cd $ORACLE_HOME/rdbms/admin

sqlplus /nolog

SQL> connect / as sysdba

SQL> @utlrp.sql

You can check for any invalid objects by executing following statement;


SQL> select OBJECT_NAME from DBA_OBJECTS where status = 'INVALID';