Oracle Critical Patch Update
January 2006
Release Notes for Oracle Database Server Version 10.2.0.1
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.
This patch should be
applied to
the Oracle home for the Database.
Additionally, you might have OHS
10.1.2.0.0 or OHS 10.1.2.1.0 installed in a separate Oracle home. You
might have installed this from the Oracle 10g R2 Companion CD or from a
standalone download.You need to apply the appropriate Oracle
Application Server patch to this OHS Oracle home.
Please refer to the
Pre-installation
notes for Critical Patch Update - January 2006 for
Application Server to determine what patch to apply.
This
document guides your through the Installation, Post Installation
Actions and
optionally, De-Installation steps required for Oracle Critical Patch
Update January 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: 4751931
Patch for Platform
: Sun SPARC
SOLARIS, Linux, HP-UX,AIX , Linux Itanium, Linux x86-64 AMD.
Product Version:
10.2.0.1
Product Patched:
Database, Modplsql
You must have Perl 5.00503 (or
later) installed under the ORACLE_HOME, or
elsewhere within the host environment.
Bugs
Fixed by this patch
4751931:MLR ON TOP OF 10.2.0.1 FOR
CPUJAN2006.
4754888:EFFORT REPRESENTATIVE BUG FOR
10.2.0.1 FOR CPUJAN2006.
OPatch information
Prior to the Install Phase, following
checks are performed
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
10.2.0.1.1. It can be downloaded from
Metalink (Patch
4898608
)
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
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, specifiying the full path to the JDK to be used. For more information see the
Opatch Users Guide release with the Opatch distribution.
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.
Set your current directory to the
directory where the patch is located and then
run opatch by entering the following command:
cd
4751931
opatch apply
If you encounter any errors, please
refer to the
Known Issues section in thePre-installation
notes for Critical Patch Update - January 2006
Post
Installation Instructions
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 –
cd
$ORACLE_HOME/cpu/CPUJan2006
SQL>
sqlplus /nolog
SQL>
connect / as sysdba
SQL>
STARTUP
SQL>
@catcpu.sql
SQL>
QUIT
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
SQL>
sqlplus /nolog
SQL>
connect / as sysdba
SQL>
@utlrp.sql
SQL>
QUIT
You can check for any invalid objects by executing following statement;
sqlplus> 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 4751931
opatch rollback
-id 4751931
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
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_rollback.sql as
follows -
cd
$ORACLE_HOME/cpu/CPUJan2006
SQL>
sqlplus /nolog
SQL>
connect / as sysdba
SQL>
STARTUP
SQL>
@catcpu_rollback.sql
SQL>
QUIT
Inspect the logfile and utlrplog
files 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
SQL>
sqlplus /nolog
SQL>
connect / as sysdba
SQL>
@utlrp.sql
SQL>
QUIT
You can check for any invalid objects by executing following statement;
select OBJECT_NAME from DBA_OBJECTS where status = 'INVALID';