|
Oracle®
Database Server Critical Patch Update Release |
|
|
|
Critical Patch Update Release
10g Release 2 (10.2.0.2)
April 30, 2006
This document contains 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.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. Refer to the Pre-installation Note for
Critical Patch Update - April 2006 for Database 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 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.
|
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:
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.
·
Patch for
Base Bug: 5079037
·
Patch for Platforms:
Solaris Operating System (SPARC 64-bit)
·
Product
Release: 10.2.0.2
·
Product
Patched: Oracle Database
·
Components
patched:
o
Oracle
Database
o
mod_plsql
The following bugs are fixed.
5079037 - MLR ON TOP OF 10.2.0.2 FOR CPUAPR2006.
5079038 - EFFORT REPRESENTATIVE BUG ON TOP OF 10.2.0.2 FOR CPUAPR2006
You must use OPatch version 10.2.0.2 or later. OPatch 10.2.0.2 is
shipped with DB 10.2.0.2 patchset.
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
These instructions are for both Non-RAC
environments and RAC environments.
Follow these steps:
1.
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).
2.
Shut down
all instances and listeners associated with the Oracle home that you are
updating. For more information, see Oracle Database
Administrator's Guide.
3.
Ensure that
the $PATH has the
following executables: make, ar, ld, and nm.
4.
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.
5.
Set your
current directory to the directory where the patch is located and then run the
OPatch utility by entering the following command:
cd 5079037
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:
1.
Start all
database instances running from the Oracle home that you are patching.
2.
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:
|
ote: Due to changes in the installation scripts, it is no longer a requirement to startup the database in MIGRATE mode.. |
cd $ORACLE_HOME/cpu/CPUApr2006
sqlplus /nolog
SQL> CONNECT /AS SYSDBA
SQL> STARTUP
SQL> @catcpu.sql
SQL> QUIT
3.
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.
4.
If catcpu.sql reports any Invalid Objects, run the
following commands:
|
Note: For large numbers of objects, this compilation step can take some time. If you are apllying this patch 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> 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';
Follow these steps:
1.
Shut down
all nodeapps services on one node:
srvctl stop nodeapps -n <node-name>
2.
Shut down
the instance on the node in step 1.
3.
Apply patch on
the node in step 1.
Set your current directory to the
directory where the patch is located and then run OPatch by entering the
following command:
cd 5079037
opatch apply -local
If there are errors, refer to the Known
Issues section in the Pre-installation Note for
Critical Patch Update - April 2006.
4.
Start the
instance on the node in step 1.
5.
Start all
nodeapps services on the node in step 1:
srvctl start nodeapps -n <node-name>
6.
Shutdown the
instance on the next node.
7.
Repeat steps
1-6 on all the nodes in the cluster.
Select one node to execute the post
installation steps. Follow the same set of instructions as mentioned in the
"Post Installation Instructions for Non-RAC
Database".
No user should be accessing the selected
instance and all other instances must be shutdown.
1. Restart instances on
all nodes.
2. Restart all nodeapps services on all nodes, one at a
time:
srvctl start nodeapps -n
<node-name>
There is no need
to run post installation steps again on other nodes.
These instructions are for both Non-RAC
environments and RAC environments.
Follow these steps:
1.
Set your
current directory to the directory where the patch is located, for example:
cd 5079037
2.
Shut down
all instances and listeners associated with the Oracle home that you are
updating. For more information, see Oracle Database Administrator'sGuide.
Run the OPatch utility using the rollback argument. For example:
opatch rollback -id 5079037
If there are errors, refer to the
"Known Issues" section in the Pre-installation Note for
Critical Patch Update - April 2006.
Follow these steps:
1.
Start all
database instances running from the Oracle home that you had patched. (For more
information, see Oracle Database Administrator's Guide.)
2.
For each
database instance running out of the ORACLE_HOME that was patched, connect to the database
using SQL*Plus as sysdba and 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
3.
Inspect the logfile
for any errors.
If there are errors, refer to the 'Known
Issues' section in the Pre-installation Note for
Critical Patch Update - April 2006.
4.
If catcpu.sql reports any Invalid Objects, Oracle
recommends that you compile the invalid objects as follows:
|
Note: For large numbers of objects, this compilation step can take some time. If you are applying this patch 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> 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';
Follow these steps:
1.
Shut down
all nodeapps services on one node:
srvctl stop nodeapps -n <node-name>
2.
Shut down the
instance on the node in step 1.
3.
Roll back
the patch on the node in step 1.
Set your current directory to the
directory where the patch is located, for example:
cd 5079037
Run OPatch using the rollback argument.
For example:
opatch rollback -id 5079037
If there are errors, refer to the
"Known Issues" section in the Pre-installation Note for
Critical Patch Update - April 2006.
4.
Start the
instance on the node in step 1.
5.
Start all
nodeapps services on the node in step 1:
srvctl start nodeapps -n <node-name>
6.
Shutdown the
instance on the next node.
7.
Repeat steps
1-6 on all the nodes in the cluster.
Post Deinstall Instructions should be run from the same node where the
"Post Installation Instruction"s were run. Goto the node and follow
the same set of instructions as mentioned in the "Post Deinstallation
Instructions for Non-RAC Database" .
All other instances can be started as usual and accessed by users while the
steps are being executed from the selected instance.
1. Restart instances on all nodes.
2. Restart all nodeapps services on all nodes, one at a
time:
srvctl start nodeapps -n <node-name>
There is no 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. 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 Critical Patch Update
Release Notes, Volume 1, 10g Release 2 (10.2.0.2)
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.
Copyright © 2006, Oracle. All rights reserved.