Skip Headers
 
 

Oracle® Database

Critical Patch Update Note

Release 10.2.0.3 for UNIX

 

Released: July 17, 2007
Document Updated: August 1, 2007


Important:

Beginning with CPUJul2007, the 10.2.0.3 CPU patch has new, improved packaging. Review the information in Section 3.2, "OPatch Utility Information" before you install this patch.

This document includes the following sections:


Note:

This document is accurate at the time of release. You can access the latest information about this critical patch update in OracleMetaLink Note 432874.1 Oracle Critical Patch Update July 2007 Known Issues for Oracle Database. The note is available at

https://www.metalink.oracle.com/


1 Getting Started

You should administer one Oracle product, one Oracle home at a time, for its particular Critical Patch Update July 2007 (CPUJul2007) patch. Each Oracle home will have its own requirements.

Before you can determine which Oracle Application Server and Oracle Database patches to apply, you need to make a list of all of the Oracle products you need to patch. For all Oracle Application Server installations, you should note if there is Oracle Database installed with it, as is the case with Oracle Application Server 10g (9.0.4) and release 2 (10.1.2) infrastructures. Having a list of all Oracle Application Server and Oracle Database installations with their full release numbers will help you determine the correct patch for each Oracle home.

The CPUJul2007 patches are bundled for each Oracle home installation type, to be installed on one Oracle home at a time. In some cases, a component may not be installed in a particular Oracle home. You can run Oracle Inventory or Oracle Universal Installer to determine which components and releases are installed in an Oracle Application Server Oracle home. The critical patch update includes patches for all components that need to be patched for all possible installation types. There is a separately bundled patch for infrastructure and middle-tier Oracle home types. If a component is installed on the system, even if the component is not used, its presence can make the application server vulnerable. Therefore, all existing components must be patched.

After you have read the CPUJul2007 documentation and collected your product information, you need to prioritize all of the systems you need to update. Plan to update systems that have the highest risk first. For example, start with systems that are external to a firewall before updating systems within an internal network.


Note:

All application server installations accessed through a firewall should be considered externally accessible.

2 Patch Information

Critical patch update (CPU) patches are cumulative, which means fixes from previous Oracle security alerts and critical patch updates are included. It is not required to have previous security patches applied before applying the CPUJul2007 patches. However, you must be on the stated patch set level for a given product home before applying the CPUJul2007 patches for that release.

Unless otherwise stated, a patch for the Oracle Application Server middle tier home will apply to all installation types of that release, such as J2EE and Web Cache, Portal and Wireless, Business Intelligence and Forms, standalone Forms and Reports, as well as standalone Oracle Application Server Containers for J2EE (OC4J) and OracleAS Web Cache.

Ensure that you review all patches to apply, and the releases that those patches apply to before you start installing any patches. Ensure that all tiers are at the correct release level before starting to apply CPU patches.

If assistance is required from Oracle Global Product Support, then provide complete information for the products being patched. Because you are administering one Oracle product, one Oracle home at a time for its one CPUJul2007 patch, there is generally one Support Service Request per Oracle home.


Note:

Client-only and Instant Client Installations
  • Client-only Installations: Oracle recommends applying this Critical Patch Update to client-only installations only if fixes released in prior Critical Patch Updates have not been applied.

  • Instant Client Installations: The Instant Client Installation is not the same as the Client-only Installation. Client-only Installations employ Oracle Universal Installer to install Administrator or Runtime types of installations. An Instant Client Installation manually copies files to ORACLE_HOME. This patch cannot be applied to Instant Client Installations because the instant client is not installed with Oracle Universal Installer; therefore, there is no Inventory, which is required by OPatch. This Critical Patch Update is currently unavailable for Instant Client Installations. Do not open a service request to Oracle support for additional information on vulnerabilities. For additional information on Instant Client Installations, refer to Oracle Database Concepts.


2.1 Bugs Fixed by This Patch

This patch includes the following tracking bugs:

6079591 - MLR BUG FOR 10.2.0.3 FOR CPUJUL2007

This patch includes the following molecules:

6121183 - DB-10.2.0.3-MOLECULE-010-CPUAPR2007

6121242 - DB-10.2.0.3-MOLECULE-001-CPUJAN2007

6121243 - DB-10.2.0.3-MOLECULE-002-CPUJAN2007

6121244 - DB-10.2.0.3-MOLECULE-003-CPUJAN2007

6121245 - DB-10.2.0.3-MOLECULE-004-CPUJAN2007

6121246 - DB-10.2.0.3-MOLECULE-005-CPUJAN2007

6121247 - DB-10.2.0.3-MOLECULE-006-CPUAPR2007

6121248 - DB-10.2.0.3-MOLECULE-015-CPUJUL2007

6121249 - DB-10.2.0.3-MOLECULE-008-CPUAPR2007

6121250 - DB-10.2.0.3-MOLECULE-009-CPUAPR2007

6121257 - DB-10.2.0.3-MOLECULE-011-CPUAPR2007

6121258 - DB-10.2.0.3-MOLECULE-012-CPUJUL2007

6121260 - DB-10.2.0.3-MOLECULE-013-CPUAPR2007

6121261 - DB-10.2.0.3-MOLECULE-014-CPUJUL2007

6121263 - DB-10.2.0.3-MOLECULE-016-CPUJUL2007

6121264 - DB-10.2.0.3-MOLECULE-017-CPUJUL2007

6121266 - DB-10.2.0.3-MOLECULE-018-CPUJUL2007

6121267 - DB-10.2.0.3-MOLECULE-019-CPUJUL2007

6121268 - DB-10.2.0.3-MOLECULE-007-CPUJUL2007

2.2 Order of Applying Patches

When applying the patches, Oracle recommends that you patch one product release, one Oracle home at a time, as each Oracle home generally has one CPUJul2007 patch, and specific instructions for its release and installation type. If you have multiple Oracle product installations, then the CPU requires that the middle tier and the database tier be patched at the same time, one after the other. This allows the database post-installation scripts to be run before starting and using the middle tier. This is the same requirement for other application databases that are accessed through any Oracle HTTP Server with mod_plsql.

Before patching, completely shutdown all processes within the Oracle home. It is not recommended to restart the Oracle HTTP Server or the middle tier home until all associated database and Metadata Repository homes have been successfully patched and restarted. This is to accommodate any dependency requirements with any database objects in use.

Oracle installations should be patched in the following order:

  1. Any separate/remote database homes that are accessed from Oracle Application Server including a separate Metadata Repository home.

  2. Identity Management and infrastructure homes.

  3. Middle-tier Oracle Application Server homes.


Note:

You must ensure that you complete each step in the preceding order successfully before proceeding to the next installation type. For example, you should not patch any middle-tier home until the remote database homes are successfully patched.

After applying the patches, startup the installations as follows:

  1. Oracle Databases

  2. Oracle Application Server Infrastructure

  3. Oracle Identity Management-only installations, if any

  4. Oracle Application Server middle tiers

In larger topologies, where sequential patching may be required, you should ensure all databases accessed from an Oracle HTTP Server are patched before applying patches to the Oracle HTTP Server or Oracle Application Server. This is to ensure all database post-installation scripts are run before starting and using an Oracle HTTP Server that may access and use database installed packages.

If there are multiple database instances running from the same Oracle home, then you must run the post-installation scripts in each instance. While running the post-installation scripts on the database, many packages are updated to the latest release for the set of installed packages. The script will detect and install what is necessary.

3 Patch Installation Procedures for Oracle Database Release 10.2.0.3

This section includes the following sections:

3.1 Platforms and Components for Patch 6079591 for Oracle Database Release 10.2.0.3

For a list of platforms that are supported in this Critical Patch Update, see OracleMetaLink Note 432873.1.

Components patched by this Critical Patch Update:

  • mod_plsql

  • Oracle Context

  • Oracle Network Manager

  • simple spatial (SDO)

3.2 OPatch Utility Information

You must use the OPatch utility release 10.2.0.3.2 or later. You can download it from OracleMetaLink with patch 4898608.NOTE: Download the 10.2.0.3 version, not the 10.2.0.1 or 10.2.0.2 version.

If the Oracle inventory is not set up correctly OPatch will fail. You can check accessibility to the inventory with the following command:

    % opatch lsinventory

3.2.1 10.2.0.3 CPUJul2007 Patch Packaging Change

With CPUJul2007, the 10.2.0.3 CPU patch has new, improved packaging. CPUs continue to be cumulative, however patch conflicts with CPUs are resolved in a simpler manner than with CPU merge patches. For more details, refer to OracleMetaLink Note 438314.1 Critical Patch Update - Introduction to Database Napply CPU Patches.

3.2.2 Patch Conflict Checking

An napply 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 OracleMetaLink Note 438313.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.3 Patch Installation Instructions for Oracle Database Release 10.2.0.3

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


Note:

You must have Perl 5.8.3 (or later) installed under either the Oracle home or elsewhere within the host environment.

3.3.1 Pre Installation Instructions for non-RAC and RAC Environments

If you have previously applied a 10.2.0.3 CPU, there are some special one-time install actions that are required. You can skip this section for now. You will be instructed when to follow these steps in Section 3.3.2, "Patch Installation Instructions for a Non-RAC Environment" and Section 3.3.4, "Patch Installation Instructions for a RAC Environment".

  1. Determine which CPU you have applied

    If you have already installed CPUJan2007, CPUApr2007, or CPUApr2007 CPU merge patch, the patch needs to be rolled back first. Post-rollback steps do not need to be performed if the CPUJul2007 is being installed.

    To determine if you have an earlier CPU installed, run:

    opatch lsinventory
    
    
  2. If patch 5881721 (CPUJan2007), 5901891 (CPUApr2007), or 6064331 (CPUApr2007 Merge) is present, then run the appropriate rollback command:

    • 5881721 (CPUJan2007): opatch rollback -id 5881721

    • 5901891 (CPUApr2007): opatch rollback -id 5901891

    • 6064331 (CPUApr2007 Merge): opatch rollback -id 6064331

    You do not need to run catcpu_rollback.sql after you run the above rollback command.

  3. There have been two non-security patches merged into the prior CPUs. If you had:

    • CPUApr2007 installed, download and install patch 6162478 from OracleMetaLink. It is a merge patch that is needed to include non-security bug 5548389.

    • CPUApr2007 Super Merge installed, download and install patches 6162478 and 6162480 from OracleMetaLink. Patch 6162480 is a merge patch that is needed to include non-security bug 4624183.

    Refer to the README for the respective merge patches for complete installation instructions.

After you have applied the merge patches from step 3 that are pertinent to your installation, continue with the application of CPUJuly2007.


Reminder:

If you roll back the prior CPU and choose not to install CPUJul2007, you must reinstall the CPU that you rolled back in order to restore any security vulnerability fixes. Refer to the README for the prior CPU for complete instructions.

3.3.2 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.3 CPUJul2007 patch to an Oracle Database Release 10.2.0.3.

  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. If you have previously applied a 10.2.0.3 CPU, follow the steps in Section 3.3.1, "Pre Installation Instructions for non-RAC and RAC Environments".

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

    cd 6079591
    opatch napply -skip_subset -skip_duplicate
    

    Note:

    Should OPatch return conflicts or subsets, refer to Section 3.2.2, "Patch Conflict Checking" for additional options

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

3.3.3 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/CPUJul2007
    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';
    
    

    Note:

    If you create a database after applying the CPU patch, then be sure to run the catcpu.sql script after you create it.

3.3.4 Patch Installation Instructions for a 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.3 CPUJul2007 patch to an Oracle Database Release 10.2.0.3.

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

  3. Shut down the instance on one node.

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

    srvctl stop nodeapps -n <node-name>
    
    
  5. If you have previously applied a 10.2.0.3 CPU, follow the steps in Section 3.3.1, "Pre Installation Instructions for non-RAC and RAC Environments".

  6. Apply the patch on the node in step 1.

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

    cd 6079591
    opatch napply -skip_subset -skip_duplicate -local
    
    

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

  7. Start the instance on the node in step 1.

  8. Start all nodeapps services on the node in step 1:

    srvctl start nodeapps -n <node-name>
    
    
  9. Shut down the instance on the next node.

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

3.3.5 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.3, "Post Installation Instructions for a Non-RAC Environment".

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

3.4 Patch Deinstallation Instructions for Oracle Database Release 10.2.0.3

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

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 6079591
    
    
  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 the July CPU. 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 -id 6079591,6121183,6121242,6121243,6121244,6121245,6121246,6121247,6121248,6121249,6121250,6121257,6121258,6121260,6121261,6121263,6121264,6121266,6121267,6121268
    
    
  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/CPUJul2007
    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> STARTUP
    SQL> @catcpu_rollback.sql
    SQL> QUIT
    
    
  3. Inspect the log file 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 6079591
    
    

    Run the OPatch utility using the specified rollback argument to rollback all molecule patches included in the July CPU. 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 -id 6079591,6121183,6121242,6121243,6121244,6121245,6121246,6121247,6121248,6121249,6121250,6121257,6121258,6121260,6121261,6121263,6121264,6121266,6121267,6121268 -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.4.4 Post Deinstallation Instructions for a RAC Environment

Run the post-deinstall instructions from the same node where you ran the Section 3.3.5, "Post Installation Instructions for a RAC Environment". Go to the node and follow the same set of instructions as mentioned in 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 Known Issues

This section includes the following information:

4.1 Issues Common to All Releases

This section includes issues common to all Oracle Database releases:

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/libclntst10.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 OracleMetaLink 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 napply -skip_subset -skip_duplicate -jdk /usr/java1.4
      
      
    • AIX 5L

      > opatch napply -skip_subset -skip_duplicate -jdk /usr/java141
      
      
    • HP-UX

      > opatch napply -skip_subset -skip_duplicate -jdk /opt/java1.4
      
      
    • Linux (32bit)

      > opatch napply -skip_subset -skip_duplicate -jdk /usr/j2sdk1.4.1_02
      
      
    • Tru64

      > opatch napply -skip_subset -skip_duplicate -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.

4.1.2.1 AIX

The following issues are specific to AIX:

  • Issue 1: When installing patches on ALL releases you may receive the following error:

    xlC: not found
    
    

    If you are not using OCCI, then the error message can be safely ignored.

    If you are using OCCI, the then AIX C++ compiler must be installed and in the PATH. Issue the following to confirm

    % which xlC
    
    

    If xlC is not found, determine its location and add the directory to the PATH environment variable. If it is not installed, it will need to be installed for the successful installation of this patch. Once it is installed, determine its location and add the directory to the PATH environment variable. Continue the installation and run the following once the above has been resolved:

    % genoccish
    
    

    The preceding command will return to the command prompt if it is successful. Otherwise, errors will be thrown.

  • Issue 2: While installing this patch on an AIX computer, you may see warning messages similar to the following:

    ld: 0711-773 WARNING:
    ld: 0711-783 WARNING:
    ld: 0711-319 WARNING:
    ld: 0711-415 WARNING:
    ld: 0711-224 WARNING:
    
    

    This happens when re-linking 64-bit binaries in 32-bit kernel mode. These warning messages are not problematic if they are reported during relinking of any 64-bit binary in 32-bit kernel mode. To check the current mode of the kernel, run the following command:

    /usr/sbin/bootinfo -K
    
    

    The result will be "32" for 32-bit or "64" for 64-bit kernel mode. By default the result will be 32.

  • Issue 3: When installing this patch using the OPatch utility, you may see the following error:

    OPatch encounters the following issues during file patching:
    The following files had problems with being patched:1.     <ORACLE_HOME>/lib
    [ Couldn't copy <Patch location>/files/lib/libjox9.a to <ORACL:E_HOME>/lib from <Patch location>. ]
    
    
    

    Workaround:

    1. Reply Y to the Do you want to STOP? prompt.

    2. As root, run the following command:

      /usr/sbin/slibclean
      
      
    3. Rollback the patch using the following command:

      sh $ORACLE_HOME/.patch_storage/123456/rollback_123456.sh 
      
      

      (where 123456 is the patch number)

    4. Apply the patch again.

  • Issue 4: In the client-only installation, you may get the following error during the relinking of client_sharedlib. This error can be ignored

    OPatch found the word "fail" in stderr, please look into it.
    You may have to run the make again.
    Stderr Output (from 
    /nfs/plnfs15/DDRtmp/ddribm4/64bit/9207/client1/
    .patch_storage/4751923/make_local.stderr):
    ar:
    Creating an archive file
     /nfs/plnfs15/DDRtmp/ddribm4/64bit/9207/client1/lib/libclntst10.a.
    ar: Creating an archive file
     /nfs/plnfs15/DDRtmp/ddribm4/64bit/9207/client1/lib32/libclntst10.a.
    ld:
    0706-005 Cannot find or open file:
     /nfs/plnfs15/DDRtmp/ddribm4/64bit/9207/client1/rdbms/lib/homts.o
     ld:open(): Afile or directory in the path name does not exist.
    ar: A file or directory in the path name does not exist.
    ar: 0707-117 The fopen system call failed on file
     /nfs/plnfs15/DDRtmp/ddribm4/64bit/9207/client1/lib/shr.o
    
    
  • Issue 5: During the relink phase while rolling back a prior CPU, OPatch returns the following error:

    ID: 0706-032 Linking mode is not specified. 
    Set the OBJECT_MODE environment variable to 32 or 64 or use the -b32 
    or -b64 option.
    
    

    Workaround:

    Option 1: Rollback the prior CPU using OPatch Release 1.0.0.0.53.

    Option 2: Reply N to the Do you want to Stop? prompt.

    Ignore all errors of this type during the rollback. The objects will be replaced with the prior CPU and the relink will not fail.


Note:

Make sure you identify the actual location of the installed JDK, not the symbolic link to it.

4.1.2.2 HP-UX

The following issues are specific to HP-UX:

  • Issue 1: In the client-only installation, you may get the following error during the relinking of client_sharedlib. This error can be ignored:

    rm: /nfs/plnfs15/DDRtmp/ddrhwp7/64bit/9206/client1/bin/genagtsh32 non-existent.
    x - hots.o
    x - hots.o
    ln: libagtsh.sl exists
    
    
  • Issue 2: During the installation of the CPU patch, OPatch throws the following error:

    Patch 6121268:
    Copy Action: Destination File
    "/project/ocs10g/qa2/ashok/av/cpu/ohome/lib/libjox10.sl" is not writeable.
    'oracle.javavm.server, 10.2.0.3.0': Cannot copy file from 'libjox10.sl' to
    '/project/ocs10g/qa2/ashok/av/cpu/ohome/lib/libjox10.sl'
     
    UtilSession failed: Prereq checkApplicable failed.
     
    OPatch failed with error code 73
    
    

    Workaround: Run the following command:

    chmod 755 $ORACLE_HOME/lib/libjox10.sl
    
4.1.2.3 Linux

The following issues are specific to Linux:

  • Issue 1: The following error may occur for opatch apply on Linux platforms where kernel release is greater than 2.4:

    java.lang.UnsatisfiedLinkError

    To prevent this error, set environment variable LD_ASSUME_KERNEL=2.4.19 and reapply the patch.

  • Issue 2: During the rollback of CPUOct2005, the following errors may occur:

    /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.1.2.4 Solaris

The following issue is specific to Solaris:

  • Issue 1: During the installation of this patch, OPatch will return the following errors on Solaris 10:

    Verifying archive files.
    Archive failed: failed to update "/oracle_1/product/9.2.0/lib/libserver10.a" with updated "/oracle_1/product/patches/4751923/files/lib/libserver10.a/dbsdrv.o" 
    Archive failed: failed to update "/oracle_1/product/9.2.0/lib/libserver10.a" with updated "/oracle_1/product/patches/4751923/files/lib/libserver10.a/evah2p.o" 
    Archive failed: failed to update "/oracle_1/product/9.2.0/lib/libserver10.a" with updated "/oracle_1/product/patches/4751923/files/lib/libserver10.a/kkxm.o"
    
    

    Workaround:

    This is a known issue with OPatch. Follow the workaround documented in OracleMetaLink Note 353150.1.

4.2 Issues Specific to Oracle Database Release 10.2.0.3

This section includes issues specific to Oracle Database Release 10.2.0.3:

The following issue is specific to Oracle Database Release 10.2.0.3:

4.2.1 Generic Issues

The following are generic issues for Oracle Database Release 10.2.0.3:

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

    Stderr output:
    /scratch/install/DB/10203/server1/lib//libcore10.a(lcd.o)(.text+0x8e8): In function `lcdprm':
    : warning: the `gets' function is dangerous and should not be used.
    

4.2.2 Platform-specific Issues

This section describes platform-specific issues for Oracle Database Release 10.2.0.3.

4.2.2.1 Linux x86-64

The following issue is specific to Linux x86-64:

  • Issue 1: During the installation of CPUJul2007, the recreating of the OCCI libraries (genoccish) fails with errors similar to:

    cp: cannot stat `/DISCARD/': No such file or directory
    cp: cannot stat `/DISCARD/': No such file or directory
    /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(occiConnectionImpl.o)
    /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 52 in $ORACLE_HOME/lib32/libocci10.a(occiConnectionImpl.o) to 168 in $ORACLE_HOME/lib32/libocci10.a(occiConnectionImpl.o)
    /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(occiConnectionImpl.o)
    /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 52 in $ORACLE_HOME/lib32/libocci10.a(occiConnectionImpl.o) to 208 in $ORACLE_HOME/lib32/libocci10.a(occiConnectionImpl.o)
    
    

    Workaround: Download and apply the patch for bug 5240469

4.3 Issues Specific to OPatch

The following issues are specific to OPatch:

  • Issue 1: On Solaris 10, OPatch may fail verification. If this happens, you must manually perform the verification. One of the reasons for failure is because Sun Microsystems changes an object file's size when it archives the file into a library.

    This is Bug 4967132. Follow process in Note 353150.1 to manually verify patch installation.

  • Issue 2: A file, <patch_number>_make.txt, is created when applying patches with the OPatch utility. The text in the file states that additional commands need to be run in order to complete the patching process. This file and its text can be ignored.

  • Issue 3: On Linux AMD x86-64 on RHEL4 systems, if you run OPatch in -report mode, it detects the incorrect platform and then terminates with errors similar to the following:

    Apply Session failed: ApplySession failed to prepare the system.
    OPatch failed with error code 73 
    
    

    Workaround: Set the OPATCH_PLATFORM_ID environment variable to point to the AMD64 Linux platform, whose ID is 226. For example:

    export OPATCH_PLATFORM_ID=226
    
    

    Then re-run OPatch in -report mode, for example:

    opatch napply -report 
    
    

    Or

    opatch nrollback -report
    
    
  • Issue 4: Issue 4: When installing 10.2.0.3 on Unix, the following error will occur if you are not using the minimum OPatch (10.2.0.3.2):

    Syntax Error... Unrecognized Command or Option: failed to parse arguments "unknown option '-skip_subset'"
    Please use the option 'opatch  -help' to get correct syntax
    
    

    Solution: Refer to Section 3.2, "OPatch Utility Information".

5 References

The following documents are references for this patch set.

Note 306091.1 Oracle Database 10g Companion CD Installs Oracle HTTP Server 9.0.4.0.0 or 10.1.2.0.0

Note 245375.1 How to Relink Oracle Application Server 10g/Oracle9iAS Release 2 Software on UNIX

Note 260449.1 Everything You Wanted to Know About the Apache-Based OHS Version

Note 329361.1 Oracle Application Server 10g (10.1.2) Support Status and Alerts

Note 189489.1 Oracle9i Data Server Interim Patch Installation (OPatch)

Note 283367.1 OPatch For Oracle Application Server 10g

5.1 Generic Issues and Notes that have Helped Security and Critical Patch Update Issues:

The following documents are generic references for this patch set.

Note 360870.1 Impact of Java Security Vulnerabilities on Oracle Products

Note 272808.1 How to update the default JDK installed in Application Server 9.0.4 and 10.1.2

Note 259404.1 How to Disable HTTP TRACE Requests

Note 186775.1 How to Set NLS Parameters at DAD Level for mod_plsql

Note 258285.1 Sending Parameters as a GET or POST When Using mod_plsql

Note 237898.1 Caution When Using ProxyRequests With ProxyPass

Note 330242.1 When Using OPatch to Update Oracle home: Missing_component: Oracle.Apache.Apache

Note 337288.1 OPatch Fails to Detect Operating System Appropriately

Note 338338.1 Opatch Fails with Missing_component - Oracle.Rsf.Rdbms_rsf, 10.1.0.4.0

Note 311536.1 Forbidden to Execute a PL/SQL Procedure With Parentheses

Note 274710.1 Cannot Load Modplsql.so Into Server Because of Symbol Errors

Note 331172.1 File Not Found When Applying Patch With CScript

Note 361993.1 Makefile Fails to Apply Any One-Off Patch on AS 10g Version 10.1.2.0.2

6 Documentation Accessibility

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 Note Release 10.2.0.3 for UNIX

Copyright © 2006, 2007, 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.