How to Apply CPU JAN 2009

Patch Number for Linux platform.

• You must use the OPatch 10.2 version 10.2.0.4.2 or later. 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.

• Ensure that your Oracle Database installation is the same release for which you are applying this patch. In other words, only apply the Release 10.2.0.4 CPUJan2009 patch to an Oracle Database Release 10.2.0.4

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

• Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator’s Guide

• 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

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

unzip p7592346_10204_<platform>.zip
cd 7592346
opatch napply -skip_subset -skip_duplicate

• If this is the first CPU installed in this Oracle home since CPUApr2008, then run cpu_root.sh as root to complete the installation of molecule 7155248. To run cpu_root.sh, go to the directory where you downloaded the patch (if you are not already in that directory) and enter the following commands.

sh cpu_root.sh

• If you are unable to run cpu_root.sh during the CPU patch installation because of the additional access rights required, it can be run after the CPU patch installation, and the database does not need to be shut down.

ORA-27369: job of type EXECUTABLE failed with exit code: ...

Post Installation:

Loading Modified .sql Files into the Database

1. If there is a database in the Oracle home that you are patching, start all database instances running from this Oracle home.
2. 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 cpu apply
   SQL> QUIT
   

3. Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle any errors:

   catbundle_CPU_<database SID>_APPLY_<TIMESTAMP>.log
   catbundle_CPU_<database sid>_GENERATE_<TIMESTAMP>.log

4. If you want to check whether view recompilation has already been performed for the database, execute the following statement.

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

   If the view recompilation has been performed, this statement returns one or more rows. If the view recompilation has not been performed, this statement returns no rows.

   To recompile the views in the database, follow these steps:

   1. Run the pre-check script (so named because it was initially released in CPUJan2008), which reports the maximum number of views and objects that may be recompiled:

      cd $ORACLE_HOME/cpu/view_recompile
      sqlplus /nolog
      SQL> CONNECT / AS SYSDBA
      SQL> @recompile_precheck_jan2008cpu.sql
      SQL> QUIT

      The purpose of this step is to help you determine whether view recompilation should be done at the same time as the CPU install, or scheduled later.

   2. If the database is not in a RAC environment, perform this step. (If the database is in a RAC environment, go to the next step.)

      Run the view recompilation script. Note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA.

      cd $ORACLE_HOME/cpu/view_recompile
      sqlplus /nolog
      SQL> CONNECT / AS SYSDBA
      SQL> SHUTDOWN IMMEDIATE
      SQL> STARTUP UPGRADE
      SQL> @view_recompile_jan2008cpu.sql
      SQL> SHUTDOWN;
      SQL> STARTUP;
      SQL> QUIT

   3. If the database is in a RAC environment, run the view recompilation script as follows. Note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA.

      cd $ORACLE_HOME/cpu/view_recompile
      sqlplus /nolog
      SQL> CONNECT / AS SYSDBA
      SQL> STARTUP NOMOUNT
      SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
      SQL> SHUTDOWN
      SQL> STARTUP UPGRADE
      SQL> @view_recompile_jan2008cpu.sql
      SQL> SHUTDOWN;
      SQL> STARTUP NOMOUINT;
      
      Set the CLUSTER_DATABASE initialization parameter to TRUE:
      
      SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
      
      Restart the database:
      
      SQL> SHUTDOWN;
      SQL> STARTUP;
      SQL> QUIT

   4. Check the log file for any errors. The log file is in the current directory and is named: vcomp_<sid>_<timestamp>.log
   5. If any invalid objects were reported, run the utlrp.sql script as follows:

      cd $ORACLE_HOME/rdbms/admin
      sqlplus /nolog
      SQL> CONNECT / AS SYSDBA
      SQL> @utlrp.sql

      Then, manually recompile any invalid objects. For example:

      SQL> alter package schemaname.packagename compile;