Patchset 10.2.0.5.1

Patch 9952230 – 10.2.0.5.1 Patch Set Update

Fri, 10/22/2010 – 09:29 — Maclean

Released: October 12, 2010

This document is accurate at the time of release. For any changes and additional information regarding PSU 10.2.0.5.1, see these related documents that are available at My Oracle Support (http://support.oracle.com/):

  • Note 854428.1 Patch Set Updates for Oracle Products
  • Note 1230855.1 Oracle Database Patch Set Update 10.2.0.5.1 Known Issues

This document includes the following sections:

1 Patch Information

Patch Set Update (PSU) patches are cumulative. That is, the content of all previous PSUs is included in the latest PSU patch.

PSU 10.2.0.5.1 includes the fixes listed in Section 5, “Bugs Fixed by This Patch”.

To install the PSU 10.2.0.5.1 patch, the Oracle home must have the 10.2.0.5.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 10.2.0.5.0 or any PSU with a lower 5th numeral version than the one being installed.

Table 1 describes installation types and security content. For each installation type, it indicates the most recent PSU patch to include new security fixes that are pertinent to that installation type. If there are no security fixes to be applied to an installation type, then “None” is indicated. If a specific PSU is listed, then apply that or any later PSU patch to be current with security fixes.

Table 1 Installation Types and Security Content 

Installation Type Latest PSU with Security Fixes
Server homes PSU 10.2.0.5.1
Client-Only Installations None
Instant Client Installations None 

(The Instant Client installation is not the same as the client-only Installation. For additional information about Instant Client installations, see Oracle Database Concepts.)

ASM (Automatic Storage Management) homes None
CRS (Cluster Ready Services) homes None

2 Patch Installation and Deinstallation

This section includes the following sections:

2.1 Platforms for PSU 10.2.0.5.1

For a list of platforms that are supported in this Patch Set Update, see My Oracle Support Note 1159443.1 Patch Set Update and Critical Patch Update October 2010 Availability Document.

2.2 OPatch Utility Information

You must use the OPatch 10.2 version 10.2.0.4.8 or later to apply this patch. Oracle recommends that you use the latest released OPatch 10.2, which is available for download from My Oracle Support patch 6880880 by selecting the 10.2.0.0.0 release.

For information about OPatch documentation, including any known issues, see My Oracle Support Note 293369.1 OPatch documentation list.

2.3 Patch Installation

These instructions are for both non-RAC environments and RAC environments.

2.3.1 Patch Pre-Installation Instructions

Before you install PSU 10.2.0.5.1, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.

 

2.3.1.1 Environment Checks
  1. Ensure that the $PATH definition has the following executables: make, ar, ld, and nm.The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin, in which case you can set your PATH definition as follows:
    export PATH=$PATH:/usr/ccs/bin

2.3.1.2 One-off Patch Conflict Detection and Resolution

For an introduction to the PSU one-off patch concepts, see “Patch Set Updates Patch Conflict Resolution” in My Oracle Support Note 854428.1 Patch Set Updates for Oracle Products.

The fastest and easiest way to determine whether you have one-off patches in the Oracle home that conflict with the PSU, and to get the necessary conflict resolution patches, is to use the Patch Recommendations and Patch Plans features on the Patches & Updates tab in My Oracle Support. These features work in conjunction with the My Oracle Support Configuration Manager. Recorded training sessions on these features can be found in Note 603505.1.

However, if you are not using My Oracle Support Patch Plans, follow these steps:

  1. Determine whether any currently installed one-off patches conflict with the PSU patch as follows:
    unzip p9952230_10205_<platform>.zip  opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./9952230
  2. The report will indicate the patches that conflict with PSU 9952230 and the patches for which PSU 9952230 is a superset. Refer to “Patch Set Updates Patch Conflict Resolution” in My Oracle Support Note 854428.1 Patch Set Updates for Oracle Products.Note that Oracle proactively provides PSU 10.2.0.5.1 one-off patches for common conflicts.
  3. Use My Oracle Support Note 1061295.1 Patch Set Updates – One-off Patch Conflict Resolution to determine, for each conflicting patch, whether a conflict resolution patch is already available, and if you need to request a new conflict resolution patch or if the conflict may be ignored
  4. When all the PSU 10.2.0.5.1 one-off patches that you have requested are available at My Oracle Support, proceed with Section 2.3.2, “Patch Installation Instructions”.

2.3.2 Patch Installation Instructions

Follow these steps:

  1. If you are using a Data Guard Physical Standby database, you must install this patch on both the primary database and the physical standby database, as described by My Oracle Support Note 278641.1.
  2. If you are patching an ASM instance, shut down all Oracle Database instances that use this ASM instance. (To see which Oracle Database instances are connected to this ASM instance, query the V$ASM_CLIENT view.)
  3. Do one of the following, depending on whether this is a RAC environment:
    • If this is a RAC environment, choose one of the patch installation methods provided by OPatch (rolling, all node, or minimum downtime), and shutdown instances and listeners as appropriate for the installation method selected.This PSU patch is rolling RAC installable. Refer to My Oracle Support Note 244241.1 Rolling Patch – OPatch Support for RAC.
    • If this is not a RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator’s Guide.
  4. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
    unzip p9952230_10204_<platform>.zip  cd 9952230  opatch apply
  5. If there are errors, refer to Section 3, “Known Issues”.

2.3.3 Post Installation Instructions

Do not perform the operations in this section on ASM instances. However, if you shut down ASM as part of applying the PSU, you must start ASM instances before you can perform any of the actions in this section on any database instances.

After installing the patch, perform the following actions:

  1. Apply conflict resolution patches as explained in Section 2.3.3.1.
  2. Load modified SQL files into the database, as explained in Section 2.3.3.2.

2.3.3.1 Applying Conflict Resolution Patches

Apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section 2.3.1.2, “One-off Patch Conflict Detection and Resolution”.

2.3.3.2 Loading Modified SQL Files into the Database

The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.

  1. For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA and run the catbundle.sql script as follows:
    cd $ORACLE_HOME/rdbms/admin  sqlplus /nolog  SQL> CONNECT / AS SYSDBA  SQL> STARTUP  SQL> @catbundle.sql psu apply

    For information about the catbundle.sql script, see My Oracle Support Note 605795.1 Introduction to Oracle Database catbundle.sql.

  2. Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle for any errors:
    catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.log  catbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log

    where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 3, “Known Issues”.

2.3.4 Post Installation Instructions for Databases Created or Upgraded after Installation of PSU 10.2.0.5.1 in the Oracle Home

These instructions are for a database that is created or upgraded after the installation of PSU 10.2.0.5.1.

You must execute the steps in Section 2.3.3.2, “Loading Modified SQL Files into the Database” for any new database only if it was created by any of the following methods:

  • Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing)
  • Using a script that was created by DBCA that creates a database from a sample database
  • Cloning a database that was created by either of the two preceding methods, and if the steps in Section 2.3.3.2, “Loading Modified SQL Files into the Database” were not executed after PSU 10.2.0.5.1 was applied

Upgraded databases do not require any post-installation steps.

2.4 Patch Deinstallation

These instructions are for both Non-RAC environments and RAC environments.

2.4.1 Patch Deinstallation Instructions for a Non-RAC Environment

Follow these steps:

  1. Verify that an $ORACLE_HOME/rdbms/admin/catbundle_PSU_<database SID>_ROLLBACK.sql file exists for each database associated with this ORACLE_HOME. If this is not the case, you must execute the steps in Section 2.3.3.2, “Loading Modified SQL Files into the Database” against the database before deinstalling the PSU.
  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. Run the OPatch utility specifying the rollback argument as follows.
    opatch rollback -id 9952230
  4. If there are errors, refer to Section 3, “Known Issues”.

2.4.2 Post Deinstallation Instructions for a Non-RAC Environment

Follow these steps:

  1. Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator’s Guide.)
  2. For each database instance running out of the ORACLE_HOME, connect to the database using SQL*Plus as SYSDBA and run the rollback script as follows:
    cd $ORACLE_HOME/rdbms/admin  sqlplus /nolog  SQL> CONNECT / AS SYSDBA  SQL> STARTUP  SQL> @catbundle_PSU_<database SID>_ROLLBACK.sql  SQL> QUIT

    In a RAC environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.

  3. Check the log file for any errors. The log file is found in $ORACLE_HOME/cfgtoollogs/catbundle and is named catbundle_PSU_<database SID>_ROLLBACK_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 3, “Known Issues”.

2.4.3 Patch Deinstallation Instructions for a RAC Environment

Follow these steps for each node in the cluster, one node at a time:

  1. Shut down the instance on the node. (Shut down all RDBMS instances before any ASM instances.)
  2. Run the OPatch utility specifying the rollback argument as follows.
    opatch rollback -id 9952230

    If there are errors, refer to Section 3, “Known Issues”.

  3. Start the instance on the node. Depending on the type of home, enter the following commands or command.
    • For ASM homes:
      srvctl start listener  srvctl start asm  srvctl start instance
    • For RDBMS (non-ASM) homes:
      srvctl start instance

2.4.4 Post Deinstallation Instructions for a RAC Environment

Follow the instructions listed in Section Section 2.4.2, “Post Deinstallation Instructions for a Non-RAC Environment” only on the node for which the steps in Section 2.3.3.2, “Loading Modified SQL Files into the Database” were executed during the patch application.

All other instances can be started and accessed as usual while you are executing the deinstallation steps.

3 Known Issues

For information about OPatch issues, see My Oracle Support Note 293369.1 OPatch documentation list.

For issues documented after the release of this PSU, see My Oracle Support Note 1230855.1 Oracle Database Patch Set Update 10.2.0.5.1 Known Issues.

Other known issues are as follows.

Issue 1
The following ignorable errors may be encountered while running the catbundle.sql script or its rollback script: 

ORA-29809: cannot drop an operator with dependent objects  ORA-29931: specified association does not exist  ORA-29830: operator does not exist  ORA-00942: table or view does not exist  ORA-00955: name is already used by an existing object  ORA-01430: column being added already exists in table  ORA-01432: public synonym to be dropped does not exist  ORA-01434: private synonym to be dropped does not exist  ORA-01435: user does not exist  ORA-01917: user or role 'XDB' does not exist  ORA-01920: user name '<user-name>' conflicts with another user or role name  ORA-01921: role name '<role name>' conflicts with another user or role name  ORA-01952: system privileges not granted to 'WKSYS'  ORA-02303: cannot drop or replace a type with type or table dependents  ORA-02443: Cannot drop constraint - nonexistent constraint  ORA-04043: object <object-name> does not exist  ORA-29832: cannot drop or replace an indextype with dependent indexes  ORA-29844: duplicate operator name specified   ORA-14452: attempt to create, alter or drop an index on temporary table already in use  ORA-06512: at line <line number>. If this error follow any of above errors, then can be safely ignored.  ORA-01927: cannot REVOKE privileges you did not grant

4 References

The following documents are references for this patch.

Note 293369.1 OPatch documentation list

Note 360870.1 Impact of Java Security Vulnerabilities on Oracle Products

Note 468959.1 Enterprise Manager Grid Control Known Issues

Note 9952230.8 DATABASE PSU 10.2.0.5.1 (INCLUDES CPUOCT2010)

5 Bugs Fixed by This Patch

This patch includes the following bug fixes.

5.1 CPU Molecules

CPU molecules in PSU 10.2.0.5.1:

PSU 10.2.0.5.1 contains the following molecules:

9963497 – DB:10.2.0.5-MOLECULE-001-CPUOCT2010

5.2 Bug Fixes

PSU 10.2.0.5.1 contains the following fixes:

High Availability

6402302 – DROP SYNONYM DDL IS NOT CAPTURED/PROPAGATED OR APPLIED

Space Management

7519406 – ‘J000’ TRACE FILE REGARDING GATHER_STATS_JOB INTERMITTENTLY SINCE 10.2.0.4

8544696 – TABLE GROWTH – BLOCKS ARE NOT REUSED

9711859 – ORA-600 [KTSPTRN_FIX-EXTMAP] DURING EXTENT ALLOCATION

Generic

8546356 – ORA-600 [KDSGRP1] AFTER REBUILD COMPOSITE PARTITION INDEX ONLINE IN RAC

8664189 – ORA-00600 [KDISS_UNCOMPRESS: BUFFER LENGTH]

Message File Changes

9713537 – ENHANCE CAUSE/ACTION FIELDS OF THE INTERNAL ERROR ORA-00600

9714832 – ENHANCE CAUSE/ACTION FIELDS OF THE INTERNAL ERROR ORA-07445

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: