Skip Headers
 
 

Oracle® Database Server Version 10.2.0.3 Patch 23

Bundle Patch Update Note

Release 10.2.0.3 for Microsoft Windows (x64)

 

Released: May 29 , 2008

This document includes the following sections:

1 Getting Started

You should administer one Oracle product, one Oracle home at a time, for its particular Bundle Patch Update May 29, 2008 (Patch23) 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 Bundle 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 Bundle 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 Bundle 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.

Oracle Configuration Manager (OCM) is included in this Bundle Patch Update. OCM enables Oracle to provide superior, proactive support to our customers. For more information, go to: http://www.oracle.com/technology/documentation/ocm.html


Note:

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

2 Patch Information

Bundle patches are cumulative, which means fixes from previous Oracle security alerts and Bundle patch updates are included. It is not required to have previous security patches applied before applying the Bundle patches. However, you must be on the stated patch set level for a given product home before applying the Bundle 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 Bundle 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 Bundle patch, there is generally one Support Service Request per Oracle home.

2.1 Bugs Fixed by This Patch

This patch fixes the following bugs.

2.1.1 Bugs Fixed for DB10.2.0.3 Patch 23: 6998004

10.2.0.3 Patch 23 includes all bugs fixed in 10.2.0.3 patch 1 through Patch 22. It must be applied on top of the 10.2.0.3 base release or on top of any earlier bundle patches from 10.2.0.3 patch 1 to 10.2.0.3 Patch 22.

For a more descriptive list of the bug fixes included in this bundle patch, refer to OracleMetaLink Note 342443.1.

5063635 - GAP OCCURED AFTER ORA-00600:[KCCDAGF_3] IN STANDBY ARC

5118272 - 10202: LMS OERI [1433], [60] DUE TO LGWR FILLING UP MSG BLOCKS

5208177 - SQL NLSSORT EVALUATION MAY RETURN NULL FOR LARGE NON-NULL VALID SOURCE VALUE

5238386 - SRL HEADER WRITE DOES NOT USE KCRFWH()

5576584 - ASM PARALLEL READS PERFORMANCE NOT ACCEPTABLE

5643036 - PERFORMANCE DEGRADATION MAY OCCUR DUE TO CALLS THAT USE KGEPEC IN KOC.C

5844945 - PHSB FAILURE TO ADD LAST LOG OF DISABLED THREAD INTO V$LOG_HISTORY

5860221 - APPLY ABORTS ORA-600 [17147] TABLE WITH FBI NO PK NO SUBST KEYS

6239052 - AROLTP-C: INSTANCE CRASHED AFTER LMS1 DIED WITH ORA-00600 [KJBRCHKINTEG:LAST]

6471770 - PARALLEL SERVERS DIE UNEXPECTEDLY RESULTING IN FAILURE OF YAHOO DW QUERIES

6493830 - RDBMS TRACKING BUG FOR EUS USER ACCOUNT LOCK OUT ENHANCEMENT

6600051 - AQRAC:ENQUEUE AND ALTER QUEUE TABLE RESULT IN HANG IN RAC ENV

6620517 - DO TSPITR SUPPORT IOT IN 10.2 DATABASE.

6676049 - IMP TABLE WHICH HAS XMLTYPE COLUMN FAILS WITH ORA-904

6771400 - ASM FAILS TO MOUNT A DISK GROUP WITH ORA-600 [KFGFINALIZE_2]

6815733 - ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [QCTCTE1] AFTER APPLYING CPUJAN2008

6822995 - SLOW OLAP PERFORMANCE WHEN USING BIEE ORACLE ANSWERS

6845066 - DISABLE REREGISTRATIONS FOR HA & RLB

6862248 - COMMANDTIMEOUT: APP MAY CRAWL IN THREADED ENVIRONMENT DUE TO LIMITED THREADPOOL

6870469 - REAL APPLICATION TESTING (CAPTURE FEATURE) FOR 10.2.0.2 AND 10.2.0.3

6914897 - ORA-600 QMXTCFLUSHTRXOB:HSH FAILURE PREVENTING ESCALATED CUSTOMER BUGFIX

6940486 - ORA-1001 RAISED AFTER APPLIED PATCH 6701716

6974999 - MERGE LABEL REQUEST ON TOP OF 10.2.0.3 FOR BUGS 6870469 6650096 6868171

6986658 - ODP.NET ATTEMPTS TO INAPPROPRIATELY USE STMT CACHING FOR REF CURSOR

7005671 - ORA-00600: INTERNAL ERROR [XSOOPS], [XSBACLOSE01] IMPORTING 4.5 EIF FILE INTO 10

2.1.2 Bugs redone for DB10.2.0.3 Patch 23: 6998004

6528963 - ADDITION OF ORAOLEDB PATCH 6277322 CAUSES APP TO HANG WITH OTHER PROCEDURES

6166400 - CANNOT FETCH A ROW USING A BOOKMARK FROM OLE DB USING LINKED SERVER


Note:

Bugs 5454831 and 5864217 appear in the Bundle patch inventory, however, the fixes for these bugs are not included in Bundle patch.

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 Bundle patch, and specific instructions for its release and installation type. If you have multiple Oracle product installations, then the Bundle 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 6998004 for Oracle Database Release 10.2.0.3 Patch 23

Patch 6867052 applies to the following platforms and components:

  • Patch for Platform: Windows (x64)

    • Microsoft Windows XP (64-Bit AMD64 and Intel EM64T)

    • Microsoft Windows 2003 (64-Bit AMD64 and Intel EM64T)

  • Product Release: Release 10.2.0.3

  • Product Patched: Oracle Database

  • Components Patched:

    • Oracle Database

    • Oracle Network Manager

    • mod_plsql

    • Oracle Context

    • Oracle ODBC Driver

    • Oracle HTTP Server

3.2 OPatch Utility Information

You must use the OPatch utility release 10.2.0.3.4 or later. You can download it from Oracle MetaLink with patch 4898608. NOTE: Be sure to download a version supported for this Bundle.

Prior to the patch installation, the following checks are performed

  • Conflicts with other patches

  • Conflicts with subset patches (existing patch is a subset of the patch being installed)

If a conflict is found, then stop the installation and contact Oracle Support Services.

If a subset is found, then continue the installation. All fixes for the subset patch are included in the patch being installed. The subset patches will be automatically rolled back prior to the installation of the new patch.

If the Oracle inventory is not setup correctly, this utility will fail. To check accessibility to the inventory you can use the opatch lsinventory command. The utility must be in the PATH definition, or you must call it specifying its full path. For example:

    %ORACLE_HOME%/OPatch/opatch lsinventory

Effective with OPatch version 10.2.0.3, the utility is Java based and does not require the use of Perl or for Perl to be installed.

3.3 Patch Installation Instructions for Oracle Database Release 10.2.0.3

This section includes the following topics.

3.3.1 Preinstallation Instructions

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

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

  3. Back up the current database that is installed, the %ORACLE_HOME% directory and Oracle inventory under c:\Program files\oracle directory.

    This will help if there are problems applying the patch, and to restore the Inventory in case of an issue with the patch.

  4. Perform a clean shutdown of all Oracle services (databases, Oracle listeners, Oracle agents, and so on.) that run from the Oracle Home where you install this patch.

  5. Stop all Oracle services, Recovery catalog, ODBC applications, and other applications that use Oracle Client. This may include Web servers that load the Oracle client in the mid-tier environment.

    Explicitly stop the Distributed Transaction Coordinator service (which is not an Oracle service) if it is running.

  6. This patch Bundle includes "version 4" of the Oracle Time Zone files. Installing new time zone files on a database can change the way that currently stored data is retrieved. In order to correctly store this data please follow the following steps:

    1. Download patch 5746875 from MetaLink.

    2. Install this patch, which installs a script called utltzuv2.sql script into the %ORACLE_HOME%\rdbms\admin directory.

    3. Run this utltzuv2.sql script to check your TSTZ data, the output of this script will be a results table which highlights affected columns.

    4. If the script provided results then save this existing TSTZ data as found by utltzuv2.sql as VARCHAR2 data. If no data was found in step 3, or if the script indicates you already have this version of the time zone files in place, then no further actions are needed.

    Then apply this patch Bundle which installs the new time zone files.

    The same Oracle Time Zone file version is also needed on the clients you connect from, if these clients use TSTZ datatypes in this database.

    For instructions on step c and d, refer to the text in the utltzuv2.sql script installed by patch 5746875.

    For more detailed instructions on all steps, including scripts which automate the actions in step 4, refer to MetaLink note 396671.1: "Usage of utltzuv2.sql before updating time zone files in Oracle 10".

3.3.2 Preinstallation Instructions for ODP.NET 2.x Only. (OPTIONAL)

For Release 10.2.0.3 Windows 64 bit platforms, there are ODP.NET and OraOLEDB fixes. For these platforms, follow the instructions relating to ODP.NET or OraOLEDB only if you are using any of these features. (If you are not using them,ignore instructions relating to them.)

Follow these steps:

  1. Install 10.2.0.3 ODAC Patch (patch number 6814733)

  2. Install ODP.NET 10.2.0.3.03 (patch number 5916667)

3.3.3 Patch Installation Instructions for single instance database

Follow these steps:

  1. Cleanly shut down all processes running from the ORACLE_HOME.

  2. Set the ORACLE_HOME environment variable to the correct Oracle home that needs to be patched.

    > set ORACLE_HOME=<Oracle Home Path> 
    
  3. Go to the directory where you downloaded the patch:

    > cd 6998004
    
  4. Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:

    > opatch apply 
    
  5. Inspect the opatch<timestamp>.log file generated in %ORACLE_HOME%\cfgtoollogs\opatch for any errors.

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

3.3.4 Installation Instructions for RAC

Please note that this patch is RAC rolling upgradable only if the requirement mentioned below is met.
However, this requiremnt is only for RDBMS and ASM homes.

10.2.0.3 Bundle Patch21 (patch 6932788) is applied on each cluster node in the RAC environment.


If the above requirement is not met then please skip the following steps and apply this patch to each node in the cluster following steps in Section 3.3.4.1

Stop the Oracle services only in the home where the patch is being applied

The order of patching in RAC install is CRS_HOME, ASM_HOME and RDBMS_HOME

  1. Before Patching CRS_HOME, all services on the current node needs to be stopped

  2. Before Patching ASM_HOME, CRS services can be running on all nodes, while Oracle ASM Services and Oracle RDBMS Services on the current node needs to be stopped

  3. Before Patching RDBMS_HOME, the ASM and CRS services can be running but Oracle RDBMS Services on the current node needs to be stopped

  4. Set the ORACLE_HOME environment variable properly

  5. Go to the directory where you downloaded the patch:

    > cd 6998004
    
  6. Ensure that the directory containing the OPatch script appears in your PATH setting. Patch this node using the command listed below.

    > opatch apply 
    

    Before patching each node OPatch will prompt for user input, at this point please make sure that all the services running on the node being patched are stopped . Once a node has been patched, services on that node can be brought up.

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

3.3.4.1 Steps to apply Patch 23 to each node in a RAC environment , if the requirement mentioned in Section 3.3.4 is not met

Follow these steps:

  1. Stop all Oracle Database Release10g RAC instances and the nodeapps application on all nodes:

    > srvctl stop database -d <DB_NAME> 
    > srvctl stop asm -n <nodename1> 
    > srvctl stop asm -n <nodename2>
    > srvctl stop nodeapps -n <nodename1>
    > srvctl stop nodeapps -n <nodename2> 
    
  2. Stop the following services:

    • OracleCRService

    • OracleCSService

    • OracleEVMService

    • OracleObjectService

    • OracleClusterVolumeService

  3. Set the ORACLE_HOME environment variable appropriately.

    > set ORACLE_HOME=<Oracle home path>
    
  4. Go to the directory where you downloaded the patch:

    > cd 6998004
    
  5. Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:

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

3.3.5 Oracle Instant Client Installation Instructions

For OUI based Client-Admin installations, the 'opatch apply' takes care of updating your installation with these latest Instant Client binaries.

For Other types of Instant Client installations, Follow these steps:

  1. Back up the existing files ociw32.dll, oci.dll, oraocci10.dll, oraociei10.dll, and oraociicus10.dll in the Instant Client installation.

  2. Replace the oraociei10.dll file in the Instant Client installation by the file oraociei10.dll from the 6998004\files\instantclient directory.

  3. Replace the ociw32.dll, oci.dll and oraocci10.dll file in the Instant Client installation by the files ociw32.dll, oci.dll and oraocci10.dll from the 6998004\files\bin directory.

  4. Replace oraociicus10.dll in the Instant Client installation by the file oraociicus10.dll from the 6998004\files\install\instantclient\light directory.

  5. Follow the Instant Client Installation Procedure for your product as follows.

3.3.6 ODP.NET 2.x Installation Instructions

Follow these steps:

  1. Open a Visual Studio 2005 command prompt.

  2. Navigate to the %ORACLE_HOME%\ODP.NET\bin\2.x directory.

  3. Execute the following to install the new ODP.NET assembly:

     gacutil /i Oracle.DataAccess.dll
    

    If you do not have gacutil.exe, you can drag-and-drop the Oracle.DataAccess.dll to %SystemRoot%\assembly using Windows File Explorer.

3.3.7 Post Installation Instructions

NOTE: If Patch 21 was applied before application of this patch (Patch 23) ,then Section 3.3.7.2 can be skipped

After installing the patch, perform the following actions:

  1. Load modified .sql files into the database, as explained in Section 3.3.7.1.

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

3.3.7.1 Loading Modified .sql Files into the Database

To load modified .sql files into the database, follow these steps:

  1. Start the OracleService<SID> and Oracle Listener Services.

  2. Start all database instances running out of the ORACLE_HOME that you just patched.

  3. If the patch is installed in the RAC setup, invoke the following command:

    > %ORACLE_HOME%\bin\opmd -install
    
  4. If Database Vault is installed, disable Database Vault before proceeding to the next step. See Section 3.5.1 for instructions to disable Database Vault.

  5. For each database instance running out of the ORACLE_HOME being patched, connect to the database using SQL*Plus as SYSDBA and run catcpu.sql as follows:

    > cd %ORACLE_HOME%\Bundle\Patch23
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> STARTUP
    SQL> @catcpu.sql
    SQL> QUIT 
    
  6. If Database Vault is installed, enable Database Vault before proceeding to the next step. See Section 3.5.2 for instructions to enable Database Vault.

  7. Inspect the logfile %ORACLE_HOME%\Bundle\Patch23\Apply_<ORACLE_SID>_<timestamp>.log for any errors.

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

  8. If catcpu.sql reports any Invalid Objects, compile the invalid objects as follows.

    (For large numbers of objects, this compilation step can take some time. If you are applying this patch through the Oracle Enterprise Manager console, you will be prompted to run this compilation script.)

    > cd %ORACLE_HOME%\rdbms\admin 
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA
    SQL> @utlprp.sql 0
    

    To check for invalid objects, execute the following statement:

    SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID'; 
    

    Note:

    For all Oracle Database releases, you must run the post-installation steps (that is, the catcpu.sql script) for any new database you create or database upgraded to this release since the Patch23 patch was applied.

  9. If you saved TSTZ data found by utltzuv2.sql as VARCHAR2 data when performing the steps in Section 3.3.1, "Preinstallation Instructions", then restore this to the TSTZ columns.


    Note:

    • For further instructions, refer to the text in the utltzuv2.sql script installed by patch 5746875.

    • For more detailed instructions on all steps, including scripts that automate the actions in step 5, refer to OracleMetaLink Note 396671.1 "Usage of utltzuv2.sql before updating time zone files in Oracle 10".

    • The same Oracle Time Zone file version is also required on the clients you connect from, if these clients use TSTZ datatypes in this database.


  10. Exit from SQL*Plus.

    SQL> QUIT 
    
  11. If there are errors, refer to Section 4, "Known Issues".

  12. If ODP.NET is installed then use regsvr32 to register oip10.dll and oraoledb10.dll: (run 'regsvr32 oip10.dll' and 'regsvr32 oraoledb10.dll' from %ORACLE_HOME%\bin)

  13. If any databases have been created without using DBCA (that is, using the command line), and you need to monitor such a database by using Oracle Enterprise Manager 10g, follow these steps:

    1. Log in to the database as SYS user and unlock and change the password of the DBSNMP user.

      > sqlplus / AS SYSDBA
      SQL> ALTER USER DBSNMP ACCOUNT UNLOCK
      SQL> PASSWORD DBSNMP
      Changing password for DBSNMP
      New password: new_password
      Retype new password: new_password
      
    2. In the Oracle Database home page in Oracle Enterprise Manager, click Monitoring Configuration under Related Links and type the new password and then click OK.

      If you do not complete this step, Oracle Enterprise Manager cannot monitor the database.

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

3.3.7.2 Recompiling Views in the Database

You must recompile views for all databases except the following:

  • Databases created with Release 11.1.0.6 or later

  • Databases created with any release (for example, 10.2.0.3, 10.1.0.5, or 9.2.0.8) after Patch23 or a later Bundle has been applied

The time required to recompile the views and related objects depends on the total number of objects and on your system configuration. In one internal Oracle test with approximately 2000 views and 4000 objects, the total execution time for view_recompile_jan2008cpu.sql and utlrp.sql was about 30 minutes.


Note:

Depending on these considerations and your downtime schedule, you can choose to schedule the recompilation of views independent of the rest of the Bundle installation. If you do this, your system will continue to work; however, the Bundle installation will not be complete until the view recompilation is completed.

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 row. If the view recompilation has not been performed, this statement returns no rows.

To recompile the views for each database instance running out of the ORACLE_HOME being patched , follow these steps:

  1. If Database Vault is installed, disable Database Vault before proceeding to the next step. See Section 3.5.1 for instructions to disable Database Vault.

  2. Run the pre-check script, which reports the maximum number of views and objects that may be recompiled:

    cd %ORACLE_HOME%\Bundle\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 Bundle install, or scheduled later.

  3. For Oracle RAC installations . (For Non-RAC installations this step should be skipped):

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

    Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

    cd %ORACLE_HOME%\Bundle\view_recompile
    sqlplus /nolog
    SQL> CONNECT SYS/SYS_Password AS SYSDBA
    SQL> STARTUP NOMOUNT
    

    Set the CLUSTER_DATABASE initialization parameter to FALSE:

    SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile; 
    SQL> SHUTDOWN
    

    Enter the following SQL*Plus commands:

    SQL> STARTUP UPGRADE
    SQL> @view_recompile_jan2008cpu.sql
    SQL> SHUTDOWN;
    SQL> STARTUP NOMOUNT
    
    

    Set the CLUSTER_DATABASE initialization parameter to TRUE:

    SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile; SQL> SHUTDOWN; SQL> STARTUP; SQL> QUIT
  4. For Oracle Non-RAC installations:

    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%\Bundle\view_recompile
    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> SHUTDOWN
    SQL> STARTUP UPGRADE
    SQL> @view_recompile_jan2008cpu.sql
     
    SQL> SHUTDOWN;
    SQL> STARTUP;
    SQL> QUIT
    
  5. Check the log file for any errors. The log file is in the current directory and is named: vcomp_<sid>_<timestamp>.log

  6. 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 <object_type> schemaname.<object_name> compile;
    
  7. Verify that the view recompilation has been performed for the database, by executing the following statement:

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

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

  8. If Database Vault is installed, enable Database Vault before proceeding any further. See Section 3.5.2 for instructions to enable Database Vault.

3.4 Patch Deinstallation Instructions for Oracle Database Release 10.2.0.3

This section includes the following topics.

3.4.1 Deinstallation Instructions for single instance database

NOTE: Deinstalling this patch will put the installation back to 10.2.0.3 Release. Any Bundle Patch that may have been rolled back by Patch 23 will have to be re-applied.

Follow these steps:

  1. Cleanly shut down all processes running from the ORACLE_HOME.

  2. Stop all Oracle Services, Distributed Transaction Coordinator (which is not an Oracle service), and all applications accessing the database to which you are applying the patch.

  3. Set the ORACLE_HOME environment variable to the correct Oracle home that was patched.

    > set ORACLE_HOME=<Oracle Home Path> 
    
  4. Go to the directory where you downloaded the patch:

    > cd 6998004
    
  5. Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:

    > opatch rollback -id 6998004 
    
  6. Inspect the opatch-<timestamp>.log file generated in %ORACLE_HOME%\cfgtoollogs\opatch for any errors.

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

3.4.2 Deinstallation Instructions for RAC

NOTE: Deinstalling this patch will put the installation back to 10.2.0.3 Release. Any Bundle Patch that may have been rolled back by Patch 23 will have to be re-applied.

Please note that, though this patch can be applied in rolling fashion if the the requirement mentioned in Section 3.3.4 is met , rollback should be done for each node in the cluster following steps mentioned below.

Follow these steps:

  1. Stop all Oracle Database Release10g RAC instances and the nodeapps application:

    > srvctl stop database -d <DB_NAME> 
    > srvctl stop asm -n <nodename1> 
    > srvctl stop asm -n <nodename2>
    > srvctl stop nodeapps -n <nodename1>
    > srvctl stop nodeapps -n <nodename2> 
    
  2. Stop the following services:

    • OracleCRService

    • OracleCSService

    • OracleEVMService

    • OracleObjectService

    • OracleClusterVolumeService

  3. Set ORACLE_HOME environment appropriately:

    > set ORACLE_HOME=<Oracle home path>
    
  4. Go to the directory where you downloaded the patch:

    > cd 6998004
    
  5. Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:

    > opatch rollback -id 6998004
    
  6. If there are errors, refer to Section 4, "Known Issues".

3.4.3 Oracle Instant Client Deinstallation Instructions

Follow these steps:

  1. If you patched the Oracle Instant Client installation by following the steps in Section 3.3.5, "Oracle Instant Client Installation Instructions", you can roll back this patch by re-copying the ociw32.DLL, oci.dll,oraocci10.dll, oraociei10.dll, and oraociicus10.dll files to the installation.

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

3.4.4 Post Deinstallation Instructions

Follow these steps:

  1. Start the OracleService<SID> and Oracle Listener Services.

  2. Start all database instances running out of the ORACLE_HOME that you just patched.

  3. Invoke the following command if the patch is installed in the RAC setup:

    > %ORACLE_HOME%\bin\opmd -uninstall 
    
  4. If Database Vault is installed, disable Database Vault before proceeding to the next step. See Section 3.5.1 for instructions to disable Database Vault.

  5. For each database instance running out of the ORACLE_HOME being patched, connect to the database using SQL*Plus as SYSDBA and follow these steps:

    > cd %ORACLE_HOME%\Bundle\Patch23
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> STARTUP
    SQL> @catcpu_rollback.sql
    SQL> QUIT
    
  6. If Database Vault is installed, enable Database Vault before proceeding to the next step. See Section 3.5.2 for instructions to enable Database Vault.

  7. Check the %ORACLE_HOME%\Bundle\Patch23\Rollback_<ORACLE_SID>_<timestamp>.log log file for any errors.

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

  8. If catcpu_rollback.sql reports any Invalid Objects, compile the invalid objects as follows.

    (For large numbers of objects, this compilation step can take some time. If you are applying this patch through the Oracle Enterprise Manager console, you will be prompted to run this compilation script.)

    > cd %ORACLE_HOME%\rdbms\admin 
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA
    SQL> @utlprp.sql 0
    

    To check for invalid objects, execute the following statement:

    SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID'; 
    
  9. If there are errors, refer to Section 4, "Known Issues".

If any databases have been created without using DBCA (that is, using the command line), and you need to monitor such a database by using Oracle Enterprise Manager 10g, follow these steps:

  1. Log in to the database as SYS user and unlock and change the password of the DBSNMP user.

    > sqlplus SYS / AS SYSDBA
    SQL> ALTER USER DBSNMP ACCOUNT UNLOCK
    SQL> PASSWORD DBSNMP
    Changing password for DBSNMP
    New password: new_password
    Retype new password: new_password
    
  2. In the Oracle Database home page in Oracle Enterprise Manager, click Monitoring Configuration under Related Links and type the new password and then click OK.

    If you do not complete this step, Oracle Enterprise Manager cannot monitor the database.

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


Note:

After you complete the de-installation, you can safely ignore any *_removed_* files that may appear in your ORACLE_HOME.

3.5 Disabling and Enabling Database Vault

This section applies if you were instructed earlier to disable or enable Database Vault.

3.5.1 Disabling Database Vault

To disable Database Vault, follow these steps. (For RAC systems, perform steps 1 and 2 for each node on which the database is installed.)

  1. Ensure that the OracleService and Oracle Listener Services are not running.

  2. Under ORACLE_HOME\bin, rename the oradv10.dll file, for example,oradv10_backup.dll.

  3. For RAC systems, perform steps 1 and 2 for each additional node on which the database is installed.

  4. Start the OracleService<SID> and Oracle Listener Services.

  5. Start all database instances running out of the ORACLE_HOME that you just patched.

  6. Invoke the following command if the patch is installed in the RAC setup:

    > %ORACLE_HOME%\bin\opmd -install 
    
  7. For each database instance running out of the ORACLE_HOME being patched, connect to the database using SQL*Plus as SYSDBA and follow these steps:

    > cd %ORACLE_HOME%\Bundle\Patch23
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> STARTUP 
    

    Unlock the DVSYS account and set the password:

    SQL> ALTER USER DVSYS ACCOUNT UNLOCK;
    SQL> ALTER USER DVSYS IDENTIFIED BY password;
    

    Disable the Oracle Database Vault triggers:

    SQL> CONNECT DVSYS/password
    SQL> ALTER TRIGGER DV_BEFORE_DDL_TRG DISABLE;
    SQL> ALTER TRIGGER DV_AFTER_DDL_TRG DISABLE;
    

3.5.2 Enabling Database Vault

To enable Database Vault, follow these steps:

  1. Lock the DVSYS account:

    > sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> STARTUP
    SQL> ALTER USER DVSYS IDENTIFIED BY password;
    SQL> ALTER USER DVSYS ACCOUNT LOCK;
    

    Enable the Database Vault triggers as DV owner:

    SQL> CONNECT <DV_Owner>/<DV_Owner_password>
    SQL> ALTER TRIGGER DVSYS.DV_BEFORE_DDL_TRG ENABLE;
    SQL> ALTER TRIGGER DVSYS.DV_AFTER_DDL_TRG ENABLE;
    

    Shutdown the database:

    SQL> CONNECT SYS as SYSDBA
    SQL> SHUTDOWN
    SQL> QUIT
    
  2. Ensure that the OracleService and Oracle Listener Services are not running.

  3. Under ORACLE_HOME\bin, name the backup of the oradv10.dll file to its original name. For example, if you named it oradv10_backup.dll, then name it back to oradv10.dll.

  4. For RAC systems, perform steps 2 and 3for each node on which the database is installed.

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: 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-01951: ROLE 'CONNECT' not granted to 'WKSYS'
    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-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-02289: sequence does not exist 
    ORA-20002: Unable to create table IMPDP_STATS: already exists
    ORA-20222: No workload capture is in progress!
    SP2-0310: unable to open file rdbms/admin/prvtmacp.plb
    SP2-0310: unable to open file rdbms/admin/catmact.sql
    SP2-0310: unable to open file rdbms/admin/catmacc.sql
    
  • Issue 2: 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 3: 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 4: 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 5: During the installation of the Bundle 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 6: This Bundle 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 7: The following warning may be displayed when using the Opatch utility to apply a Bundle. 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'
    
  • Issue 8: The view recompilation pre-check script returns different results during subsequent runs (such as after the first time you ran it).

    The results (the maximum number of views and objects that may be recompiled) may be more or less than reported in the previous running of the script. This is expected behavior, and is not a problem.

4.1.2 Platform-specific Issues

There are no known platform-specific issues.

4.2 Issues Specific to Oracle Database Release 10.2.0.3

Oracle Database Release 10.2.0.3 has the following issues:

  • Issue 1: When using the OPatch utility to apply this Bundle patch for 10.2.0.3 Windows Itanium, OPatch may prompt you with the notification indicating that the following class files could not be rolled back :

    sysman\jlib\oracle\sysman\eml\app\ContextInitFilter.class
    sysman\jlib\oracle\sysman\eml\jobs\JobsListBean.class
    sysman\jlib\oracle\sysman\eml\jobs\JobSql.class
    sysman\jlib\_jobs\_jobsList.class
    sysman\jlib\_jobs\_jobsList$__jsp_StaticText.class
    

    Because the fixes affecting these files are already present in the patch, you can ignore this warning. Respond y when prompted to proceed.

4.3 Issues Specific to OPatch

There are no known issues specific to OPatch.

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 Bundle 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, 7 days a week. For TTY support, call 800.446.2398. Outside the United States, call +1.407.458.2479.


Oracle Database Bundle Patch Update Note Release 10.2.0.3 for Microsoft Windows (x64)

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