Oracle® Database

3.3.1 Patch Installation Instructions for a Non-RAC Environment

Follow these steps:

1. 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.1 CPUOct2006 patch to an Oracle Database Release 10.2.0.1.

2. Review Section 4, "Known Issues" before proceeding with this installation.

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

6. On Linux platforms where the kernel release is greater than 2.4, set the LD_ASSUME_KERNEL environment variable as follows:

   export LD_ASSUME_KERNEL=2.4.19
   
   

   Failure to do this may result in the following error when running OPatch:

   java.lang.UnsatisfiedLinkError
   
   

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

   cd 5490846
   opatch apply
   
   

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

3.3.2 Post Installation Instructions for a Non-RAC Environment

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:

   (Due to changes in the installation scripts, it is no longer a requirement to startup the database in MIGRATE mode.)

   cd $ORACLE_HOME/cpu/CPUOct2006
   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 Section 4, "Known Issues".

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 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';
   
   

3.3.3 Patch Installation Instructions for a RAC Environment

Follow these steps:

1. Shut down the instance on one node.

2. Shut down all nodeapps services on the node in step 1:

   srvctl stop nodeapps -n <node-name>
   
   

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 5490846
   opatch apply -local
   
   

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

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. Shut down the instance on the next node.

7. Repeat steps 1-6 on all the nodes in the cluster.

3.3.4 Post Installation Instructions for a RAC Environment

Select one node to execute the post installation steps. Follow the same set of instructions as mentioned in the Section 3.3.2, "Post Installation Instructions for a Non-RAC Environment".

Users can continue to access the database during the post-installation steps.

3.4.1 Patch Deinstallation Instructions for a Non-RAC Environment

Follow these steps:

1. Set your current directory to the directory where the patch is located, for example:

   cd 5490846
   
   

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 rollback argument. For example:

   opatch rollback -id 5490846
   
   

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

3.4.2 Post Deinstallation Instructions for a Non-RAC Environment

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/CPUOct2006
   sqlplus /nolog
   SQL> CONNECT / AS SYSDBA
   SQL> STARTUP
   SQL> @catcpu_rollback.sql
   SQL> QUIT
   
   

3. Inspect the logfile for any errors. If there are any errors, refer to Section 4, "Known Issues".

4. If catcpu_rollback.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';  
   

3.4.3 Patch Deinstallation Instructions for a RAC Environment

Follow these steps:

1. Shut down the instance on one node.

2. Shut down all nodeapps services on the node in step 1:

   srvctl stop nodeapps -n <node-name>
   

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 5490846
   
   

   Run OPatch using the rollback argument. For example:

   opatch rollback -id 5490846
   
   

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

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. Shut down the instance on the next node.

7. Repeat steps 1-6 on all the nodes in the cluster.

3.4.4 Post Deinstallation Instructions for a RAC Environment

Run the post-deinstall instructions from the same node where you ran the Section 3.4.2, "Post Deinstallation Instructions for a Non-RAC Environment".

Users can start and access all other instances as usual while you are executing the steps from the selected instance.

1. Restart all nodeapps services on all nodes, one at a time:

   srvctl start nodeapps -n <node-name>
   
   

2. Restart instances on all nodes.

You do not need to run post installation steps again on other nodes.

4.1.1 Generic Issues

The following are generic issues common to all platforms.

• Issue 1: While applying the patch, you may see the following error. This error can be ignored.

  ** Starting rebuild for libraries and executables
  rdbms/lib:ins_rdbms.mk:client_sharedlib,ioracle
  make -f ins_rdbms.mk client_sharedlib ioracle
  ... /bin/genclntsh
  basename: too few arguments
  Try 'basename --help' for more information.
  cp: missing file arguments
  Try 'cp --help' for more information.
  Created /.../lib/libclntst9.a
  Patch applied succesfully
  
  

• Issue 2: While applying the patch, you may see the following error. This error can be ignored.

  *** Starting rebuild for libraries and executables
  rdbms/lib:ins_rdbms.mk:client_sharedlib,ioracle,utilities
  make -f ins_rdbms.mk client_sharedlib ioracle utilities
  /u02/user6/11510/ap666s06ora/iAS/bin/genclntsh
  cp: cannot stat `/DISCARD/': No such file or directory 
  
  

• Issue 3: While relinking Oracle Internet Directory binaries, you may encounter the following ignorable error:

  mkdir: cannot create directory '<ORACLE_HOME>/bin/oiddcopy': File exists
  make: [inst_servers] Error 1 (ignored)
  
  

• Issue 4: While rolling back the patch, if you encounter the following prompt, enter N to continue.

  Printing stderr to output (from $ORACLE_HOME/.patch_storage/4201702/make_local.stderr)
  mkdir: Failed to make directory "$ORACLE_HOME/bin/oiddcopy"; File exists
  OPatch encounters the following issues during Make:
  There were problems running make commands.  The errors encounted were:
  ERROR: mv oidldapd $ORACLE_HOME/bin/oidldapd
  mkdir $ORACLE_HOME/bin/oiddcopy
  *** Error code 2 (ignored)
  cp $ORACLE_HOME/bin/oidldapd  $ORACLE_HOME/bin/oiddcopy
  mv oidrepld $ORACLE_HOME/bin/oidrepld  
  chmod 4755 $ORACLE_HOME/bin/oidldapd
  chmod 600 $ORACLE_HOME/bin/oiddcopy/oidldapd
  Do you want to STOP?
  Please respond Y|N >
  
  

• Issue 5: When linking client_sharedlib you may encounter the following ignorable warning:

  ld: warning: option -o appears more than once, first setting taken
  
  

• Issue 6: The following ignorable errors may be encountered while running the catcpu.sql and catcpu_rollback.sql scripts (and the sdocpu.sql and sdocpu_rollback.sql scripts, in case you are executing those separately):

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

• Issue 7: While running opatch apply, you may see the following prompt, enter N to continue:

  OPatch encounters the following issues during file back-up:
  The following problems were encountered when trying to backup Java class
   files: /nfs/bld/d4/apps/11510/AB4/apps/cpu1db/9.2.0/rdbms/jlib/CDC.jar 
  [ object: Subscription.class ]
  Do you want to continue?
  Please respond Y|N >
  The problem here is that OPatch could not find jdk in the default
  location.
  Rerun 'opatch apply -jdk <local jdk location>' and provide the location
  of the jdk.  
  
  

• Issue 8: During patch application, if following error is encountered, respond Y:

  Executing the Apply pre-patch script (.../4392423/custom/scripts/pre)...
  The pre patch script returned an error.
  Do you want to STOP?
  Please respond Y|N >
  Y
  Pre-patch script error
  ERROR: OPatch failed because of problems with pre-patch script.
  
  

  Workaround: Run the following commands:

  chmod 755 custom/scripts/pre
  chmod 755 custom/scripts/post
  
  

• Issue 9: If the NLS_LANG environment variable is set to Japanese_Japan.JA16EUC or Japanese_Japan.JA16SJIS, while executing catcpu.sql (and catcpu_rollback.sql), the following errors may occur:

  SP2-0768: Illegal SPOOL commandSP2-0768: Illegal SPOOL command
  Usage: SPOOL { <file> | OFF | OUT }
  where <file> is file_name[.ext] [CRE[ATE]|REP[LACE]|APP[END]]
  
  

  Workaround: Before running the catcpu.sql or catcpu_rollback.sql scripts, run the following SQL statement to change the nls_language setting:

  SQL>ALTER SESSION SET nls_language='American';
  
  

• Issue 10: Patch installation could fail with the following message if Oracle Data Mining was de-installed. To avoid this error, see Note 339186.1.

  $ORACLE_HOME/.patch_storage/4210374/make_local.stderr)
  /usr/bin/ld: cannot find -ldm10
  collect2: ld returned 1 exit status
  make: *** [$ORACLE_HOME/rdbms/lib/oracle] Error 1
  Make failed.
  
  

• Issue 11: If you are applying the patch using a Terminal Services or Remote Desktop Connection and experiencing problems, attempt to apply the patch locally at the console of the machine against which the patch is being applied before filing a Service request with Oracle Global Product Support.

• Issue 12: During the installation of the CPU patch, OPatch throws the following error:

  OPatch encounters the following issues during file patching:
  The following java archives had problems with being patched:
  classes12.zip [ object: JndiAttrs.class ]
  classes111.zip [ object: JndiAttrs.class ]
  
  

  Workaround: Run opatch with -jdk option. For example:

  • Sun Solaris (32 bit and 64 bit)

    > opatch apply -jdk /usr/java1.4
    
    

  • AIX 5L

    > opatch apply -jdk /usr/java141
    
    

  • HP-UX

    > opatch apply -jdk /opt/java1.4
    
    

  • Linux (32bit)

    > opatch apply -jdk /usr/j2sdk1.4.1_02
    
    

  • Tru64

    > opatch apply -jdk /usr/opt/java141
    
    

• Issue 13: This critical patch update may reload a few packages (for example, the utl_file package). This reinstates all of its default grants, regardless of any revocations made by the end-user.

  Workaround: Revoke all grants made by end user for such packages. (ref: OracleMetaLink Note 131752.1.)

• Issue 14: The following warning may be displayed when using the Opatch utility to apply a CPU. You can ignore this warning. Respond Y when you are prompted to proceed.

  WARNING:OUI-67124: 
  Copy Action: Desctination File "<ORACLE_HOME>/lib/libnjssl10.sl" is not 
  writeable. 
  @ 'oracle.rsf.net_rsf, 10.1.0.4.0': Cannot copy file from 'libnjssl10.sl' to 
  '<ORACLE_HOME>/lib/libnjssl10.sl'
  

4.1.2 Platform-specific Issues

This section describes platform-specific issues.

/ora01/oracle/product/920/network/lib/libnmi.a(snmite.o)(.text+0x1427): In function `snmitetn_tempName':
the use of `tmpnam_r' is dangerous, better use `mkstemp'
/ora01/oracle/product/920/network/lib/libnmi.a(nmijs.o)(.text+0x3571): In function `nmijsupper':
 : undefined reference to `__ctype_b'
:/ora01/oracle/product/920/network/lib/libnmi.a(snmifork.o)(.text+0x149): In function `snmifon2p_NameToPathname':
: undefined reference to `__ctype_b'
/ora01/oracle/product/920/network/lib/libnmi.a(snmitcl.o)(.text+0xc6): In function `get_ora_ctx_handle':
undefined reference to `__ctype_b'

4.2.1 Generic Issues

The following issue is generic for Release 10.2.0.1.

• Issue 1: 10.2.0.1 Patchset changes permissions of some files in $ORACLE_HOME.

  If you encounter this problem, download and apply patch for 4516865.

4.2.2 Platform-specific Issues

This section describes platform-specific issues for Release 10.2.0.1.

/usr/bin/ld: Warning: size of symbol `std::basic_string<unsigned short,
oracle::occi::utext_char_traits, std::allocator<unsigned short>
>::~basic_string()' changed from 168 in $ORACLE_HOME/lib32/libocci10.a(occiConnectionImpl.o) to 52 in
$ORACLE_HOME/lib32/libocci10.a(occiMetaData.o)

/usr/bin/ld: warning: i386 architecture of input file
`$ORACLE_HOME/lib32/libocci10.a(occiSQLExceptionImpl.o)' is incompatible with
i386:x86-64 output

$ORACLE_HOME/lib32/libocci10.a(occiSQLExceptionImpl.o)(.text+0x194): In
function
`_ZN6oracle4occi16SQLExceptionImplC9EPvi': : undefined reference to
`OCIPGetErrorMessage'