Oracle® Database

3.1.1 n-Apply CPUs and Patch Conflict Checking

N-apply CPUs are cumulative patches. For further information, refer to My Oracle Support Note 438314.1 Critical Patch Update - Introduction to Database n-Apply CPU Patches.

An n-apply CPU patch consists of groups of security fixes, where each group is called a molecule. Each molecule is an independent patch and does not conflict with any of the other molecule patches within the CPU. Prior to the patch installation, the following checks are performed for each molecule patch being installed:

• Conflicts with other patches

• Subset patches (patch to be installed is a subset of an existing patch in the Oracle Home)

• Duplicates (patch to be installed is the same as an existing patch in the Oracle Home)

If a conflict is found, the installation will stop and you will be notified to file a merge request for the conflicting patches. To assist you in determining the best course of action when conflicts are reported, refer to My Oracle Support Note 835682.1, which documents the mapping of molecules to security vulnerabilities.

Select one of the following options:

• Option 1: Resolve patch conflicts and install CPU together

  1. File an SR for the merge request indicating all patches that conflict with the CPU as reported by OPatch.

  2. Install the merge patches when they become available.

  3. Install the CPU patch.

• Option 2: Perform a partial installation of the CPU and resolve the conflicts later

  1. At the conclusion of the aborted installation, OPatch returns the necessary command to install all molecules that do not conflict with patches in the Oracle home. Run this command to perform a partial CPU installation.

  2. File an SR for the merge request indicating all patches that conflict with the CPU as reported by OPatch.

  3. Install the merge patches when they become available.

If a subset or duplicate is found, the patch installation will continue. The subset and duplicate patches will not be installed as they are already installed.

3.2.1 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 CPU 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. Ensure that the $PATH 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 as follows:

   export PATH=$PATH:/usr/ccs/bin
   

5. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:

   unzip p12828112_10204_<platform>.zip
   cd 12828112
   opatch napply -skip_subset -skip_duplicate
   

   Should OPatch return conflicts or subsets, refer to Section 3.1.1, "n-Apply CPUs and Patch Conflict Checking" for additional options.

6. If this is the first CPU installed in this Oracle home, see Issue 2 in Section 4, "Known Issues".

7. If there are errors, refer to Section 4, "Known Issues".

3.2.2 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 CPU, 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. Load modified SQL files into the database, as explained in Section 3.2.2.1.

2. Recompile views in the database, if necessary, as explained in Section 3.2.2.2.

SELECT * FROM registry$history where ID = '6452863';

3.2.3 Post Installation Instructions for Databases Created or Upgraded after Installation of CPUOct2011 in the Oracle Home

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

You must execute the steps in Section 3.2.2.1, "Loading Modified SQL Files into the Database" and Section 3.2.2.2, "Recompiling Views in 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 Section 3.2.2.1, "Loading Modified SQL Files into the Database" and Section 3.2.2.2, "Recompiling Views in the Database" were not executed after CPUOct2011 was applied

Upgraded databases require that you perform the steps in Section 3.2.2.2, "Recompiling Views in the Database" if these steps have not previously been performed; otherwise, no post-installation steps need to be performed.

3.3.1 Patch Deinstallation Instructions for a Non-RAC Environment

Follow these steps:

1. Verify that an $ORACLE_HOME/rdbms/admin/catbundle_CPU_<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 3.2.2.1, "Loading Modified SQL Files into the Database" against the database before deinstalling the CPU.

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 using the specified rollback argument to rollback all molecule patches included in CPUOct2011. If a molecule is not installed in the Oracle Home, the rollback will ignore it. If a molecule is installed as part of a merge patch, it will not be rolled back. If it is desired to rollback merge patches that have been applied to your Oracle Home, the rollback needs to be issued separately.

   opatch nrollback -idFile $ORACLE_HOME/cpu/CPUOct2011/rollback_all.lst
   

   If you have applied CPUOct2011 on top of a previous CPU, you may instead want to rollback only the molecule patches that are new in CPUOct2011. To do so, use the following command:

   opatch nrollback -idFile $ORACLE_HOME/cpu/CPUOct2011/rollback_new.lst
   

   You may also rollback individual molecules or a list of molecules, as needed. Refer to the OPatch documentation on the nrollback command.

4. If the entire CPU has been deinstalled, see Issue 2 in Section 4, "Known Issues".

5. For information on the content of molecules when doing a rollback of CPUOct2011, refer to My Oracle Support Note 1346023.1 "Critical Patch Update October 2011 Database Patch Security Vulnerability Molecule Mapping.

6. If there are errors, refer to Section 4, "Known Issues".

3.3.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_CPU_<database SID>_ROLLBACK.sql
   SQL> -- Execute the next statement only if this is the first 10.2.0.4 CPU applied or this is the first CPU applied since CPUApr2011.
   SQL> @utlrp.sql
   SQL> QUIT
   

   In a RAC environment, the name of the rollback script will have the format catbundle_CPU_<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_CPU_<database SID>_ROLLBACK_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 4, "Known Issues".

3.3.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. Roll back the patch on the node.

   Run the OPatch utility using the specified rollback argument to rollback all molecule patches included in CPUOct2011. If a molecule is not installed in the Oracle Home, the rollback will ignore it. If a molecule is installed as part of a merge patch, it will not be rolled back. If it is desired to rollback merge patches that have been applied to your Oracle Home, the rollback needs to be issued separately.

   opatch nrollback -idFile $ORACLE_HOME/cpu/CPUOct2011/rollback_all.lst -local
   

   If you have applied CPUOct2011 on top of a previous CPU, you may instead want to rollback only the molecule patches that are new in CPUOct2011. To do so, use the following command:

   opatch nrollback -idFile $ORACLE_HOME/cpu/CPUOct2011/rollback_new.lst -local
   

   You may also rollback individual molecules or a list of molecules, as needed. Refer to the OPatch documentation on the nrollback command.

   For information on the content of molecules when doing a rollback of CPUOct2011, refer to My Oracle Support Note 1346023.1 "Critical Patch Update October 2011 Database Patch Security Vulnerability Molecule Mapping.

   If there are errors, refer to Section 4, "Known Issues".

3. If the entire CPU has been deinstalled, see Issue 2 in Section 4, "Known Issues".

4. 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
     

3.3.4 Post Deinstallation Instructions for a RAC Environment

Follow the instructions listed in Section Section 3.3.2, "Post Deinstallation Instructions for a Non-RAC Environment" only on the node for which the steps in Section 3.2.2.1, "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.