Skip Headers
 
 

Oracle® Database Server Version 11.2.0.3 Patch 22

Bundle Patch Update Note

Release 11.2.0.3 for Microsoft Windows (x64)

 

Released: Jul, 2013

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. Each Oracle home will have its own requirements.

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.

1.1 System Requirements

The following are the system requirements for this bundle patch:

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.

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.

Table 1 describes installation types and CPU applicability. For each installation type, it indicates the most recent CPU patch to include new security fixes that are pertinent to that installation type. If there are no security fixes to be applied to an installation type, then "None" is indicated. If a specific CPU is listed, then apply that CPU or any later CPU patch to be current with security fixes.

Table 1 Installation Types and CPU Applicability

Installation Type Latest CPU with Security Fixes

Server homes

CPUJul2013


Client-Only Installations

CPUOct2012

Instant Client Installations

None

(The Instant Client installation is not the same as the client-only Installation. For additional information about Instant Client installations, see Oracle Database Concepts.)

ASM (Automatic Storage Management) homes

None

CRS (Cluster Ready Services) homes

None

3 Patch Installation Procedures for Oracle Database Release 11.2.0.3 Patch22

This section includes the following sections:

3.1 Components patched by Oracle Database Release 11.2.0.3 Patch22"

    Components patched by this Bundle Patch Update:

    • Oracle Database

    • PL/SQL

    • Network

    • Context

    • Javavm

    • Winprod

    • USM

    • OPSM

    • HAS

    • XDK

3.2 OPatch Utility Information

Oracle recommends that you use OPatch utility release 11.2.0.1.9 or later. You can download it from My Oracle Support with patch 6880880.

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

3.3 Patch Installation Instructions for Oracle Database Release 11.2.0.3 Patch22

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

  2. This patch must be applied on top of the 11.2.0.3 base release or on top of any earlier bundle patches released prior to 11.2.0.3 Patch 22 without performing a rollback of earlier bundle patch.

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

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

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

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

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

  8. Please make sure %ORACLE_HOME%\perl\bin appears in your PATH setting. if not please follow the below step

    set PATH=%ORACLE_HOME%\perl\bin;%PATH%

3.3.2 Patch Installation Instructions for Single Instance

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 16803775 
    
  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.3 Patch Installation Instructions for RAC

Follow these steps on each node in the cluster:

Please note that this patch is RAC rolling upgradable for GRID, and RDBMS homes.

Stop the Oracle services only on the node where the patch is being applied.

Before applying the patch in any home, connect to SQLPLUS and perform the following steps

     > sqlplus /nolog 
     SQL> CONNECT / AS SYSDBA 
     SQL> alter system checkpoint local;

The order of patching in RAC install is GRID_HOME, then RDBMS_HOME

  1. Patching Grid Home:Before Patching GRID_HOME, stop OCR related resources, 'unlock' the Grid Home to prepare it for patching and stop Oracle High Availability Services (OHASD) & all Oracle Services:

    > srvctl stop service -d <database name> -s <configured workload management service> -i <instancename>
    > srvctl stop instance -d <dbname> -i <instance name> -o abort
    > %ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install %ORACLE_HOME%\crs\install\rootcrs.pl -unlock
    
    To verify that there are no longer any resources running on the node to be patched, run the following command from another node with GRID running:
    > crsctl status resource -t
    

    Then use the Computer Management Services GUI or the net stop command to stop ALL Oracle services and Distributed Transaction Coordinator service running on that node, if they are running:

    • net stop OracleService<SID>
    • net stop OracleDBConsole<SID>
    • net stop OracleJobScheduler<SID>
    • net stop "Oracle <SID> VSS Writer Service"
    • net stop OracleREMExecService
    • net stop "Oracle Object Service"
    • net stop ocfs (required only for OCFS installation)
    • net stop OraFenceService
    • net stop msdtc
    • net stop OracleMTSRecoveryService
  2. Set the ORACLE_HOME environment variable properly

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

    > cd 16803775 
    
  4. Ensure that the directory containing the OPatch script appears in your PATH setting. Patch the node using the commands listed below.

    > opatch apply -local
    
    
  5. Oracle HASD Services (OHASD) can be started at this point

    > %ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install %ORACLE_HOME%\crs\install\rootcrs.pl -patch

  6. Patching Database Home:Before Patching RDBMS_HOME, the GRID and ASM services can be running.
    Stop Oracle Services on the current node as listed below:

  7. > srvctl stop service -d <database name> -s <configured workload management service> -i <instancename>
    > srvctl stop instance -d <dbname> -i <instance name> -o abort
    

    • net stop OracleService<SID>
    • net stop Oracle<SID>VSSWriterService
    • net stop OracleDBConsole<SID>
    • net stop msdtc
  8. Set the ORACLE_HOME environment variable properly

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

    > cd 16803775  
    
  10. Ensure that the directory containing the OPatch script appears in your PATH setting. Patch the node using the commands listed below.

    > opatch apply -local
    
  11. Start the Oracle Instance on the node

    > srvctl start instance -d <dbname> -i <instance name>

  12. Replacing Oracle Fence driver:

  13. Stop Oracle Service OraFenceService if not already done

    Stop everything outlined in step 2 before proceeding further:

    Backup orafenceservice.sys located under %SystemRoot%\System32\drivers.

    Copy the orafencedrv.sys supplied in the patch under 16345825\files\cfs to %systemRoot%\System32\drivers\orafenceservice.sys

    Note:The filename in %SystemRoot%\System32\drivers is required to be orafenceservice.sys.

    Reboot the node

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

3.3.4 Patch Installation Instructions for Oracle Instant Client

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. Backup and replace oci.dll file in the Instant Client installation with oci.dll from the 16803775\files\bin directory.

  2. Backup and replace oraociei11.dll file in the Instant Client installation with oraociei11.dll from the 16803775\files\instantclient directory.

  3. Backup and replace oraociei11.sym file in the Instant Client installation with oraociei11.sym from the 16803775\files\instantclient directory.

  4. Backup and replace oraociicus11.dll file in the Instant Client installation with oraociicus11.dll from the 16803775\files\instantclient\light directory.

  5. Backup and replace oraociicus11.sym file in the Instant Client installation with oraociicus11.sym from the 16803775\files\instantclient\light directory.

  6. Backup and replace sqora32.dll, sqoras32.dll, sqresja.dll and sqresus.dll file in the Instant Client installation with sqora32.dll, sqoras32.dll, sqresja.dll and sqresus.dll from the 16803775\files\bin directory.

3.3.5 Patch Installation Instructions for ODAC installation

Note, do not use OPatch to patch an ODAC installation. Although it will not error, it will corrupt the install. Instead perform the following manual steps:

Take a backup of the files before replacing them with the new one's

  1. copy 16803775\files\odp.net\bin\4\Oracle.DataAccess.dll %OH%\odp.net\bin\4\Oracle.DataAccess.dll

  2. copy 16803775\files\odp.net\bin\2.x\Oracle.DataAccess.dll %OH%\odp.net\bin\2.x\Oracle.DataAccess.dll

  3. copy 16803775\files\bin\oraops11w.dll %OH%\bin\oraops11w.dll

  4. copy 16803775\files\bin\OraOLEDB11.dll %OH%\bin\OraOLEDB11.dll

  5. copy 16803775\files\bin\OraOLEDB11us.dll %OH%\bin\OraOLEDB11us.dll

  6. copy 16803775\files\bin\OraOLEDBgmr11.dll %OH%\bin\OraOLEDBgmr11.dll

  7. copy 16803775\files\bin\OraOLEDBpus11.dll %OH%\bin\OraOLEDBpus11.dll

  8. copy 16803775\files\bin\OraOLEDBrfc11.dll %OH%\bin\OraOLEDBrfc11.dll

  9. copy 16803775\files\bin\OraOLEDBrmc11.dll %OH%\bin\OraOLEDBrmc11.dll

  10. copy 16803775\files\bin\OraOLEDBrst11.dll %OH%\bin\OraOLEDBrst11.dll

  11. copy 16803775\files\bin\OraOLEDButl11.dll %OH%\bin\OraOLEDButl11.dll

  12. copy 16803775\files\bin\oramts11.dll %OH%\bin\oramts11.dll

  13. copy 16803775\files\bin\oramts.dll %OH%\bin\oramts.dll

3.3.6 ODP.NET 2.x Installation Instructions

Follow these steps only if you are using ODP.NET:

  1. Open a command prompt. (Open via "Run As Administrator" if applying on Windows 7 or 2008R2 and User Account Control is enabled).

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

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

     oraprovcfg.exe /action:gac /providerpath:Oracle.DataAccess.dll
    

3.3.7 ODP.NET 4.0 Installation Instructions

Follow these steps only if you are using ODP.NET:

  1. Open a command prompt. (Open via "Run As Administrator" if applying on Windows 7 or 2008R2 and User Account Control is enabled).

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

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

     oraprovcfg.exe /action:gac /providerpath:Oracle.DataAccess.dll
    

3.3.8 Post Installation Instructions

After installing the patch, perform the following actions:

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

3.3.8.1 Loading Modified .sql Files into the Database

To load modified .sql files into the database, 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. Start the OracleService<SID> and Oracle Listener Services if already not started.

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

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

    > cd %ORACLE_HOME%\Bundle\Patch22
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> STARTUP
    SQL> @catwinbundle.sql
    SQL> QUIT 
    
  5. Check the following log files in $ORACLE_BASE/cfgtoollogs/catbundle for any errors:

    catbundle_WINBUNDLE_<database SID>_APPLY_<TIMESTAMP>.log
    catbundle_WINBUNDLE_<database SID>_GENERATE_<TIMESTAMP>.log
      

    where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 4, "Known Issues".

  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. To ensure all dependant objects are valid after running catwinbundle.sql:

    (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> @utlrp.sql
    

    To check for invalid objects, execute the following statement:

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

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


Note:

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

3.3.9 Post Installation Instructions for Databases Created or Upgraded after Installation of Bundle Patch22 in the Oracle Home

These instructions are for both RAC environments and non-RAC environments when a database is created or upgraded after the installation of Bundle Patch22.

You must execute the steps in Section 3.3.8.1, "Loading Modified .sql Files into the Database" for any new database that was created by any of the following methods:

  • Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing)

  • Using a script that was created by DBCA that creates a database from a sample database

  • Cloning a database that was created by either of the two preceding methods, and if Section 3.3.8.1, "Loading Modified .sql Files into the Database" was not executed after Bundle Patch22 was applied

Upgraded databases require that you perform the steps in Section 3.3.8.1, "Loading Modified .sql Files into the Database" if these steps have not previously been performed; otherwise, no post-installation steps need to be performed.

3.4 Patch Deinstallation Instructions for Oracle Database Release 11.2.0.3 Patch22

This section includes the following topics.

3.4.1 Patch Deinstallation Instructions for Single Instance

Follow these steps:

  1. Verify that an $ORACLE_HOME/rdbms/admin/catbundle_WINBUNDLE_<database SID>_ROLLBACK.sql file exists for each database associated with this ORACLE_HOME. If this is not the case, you must execute the steps in Section 3.3.8.1, "Loading Modified SQL Files into the Database" against the database before deinstalling the patch.

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

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

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

    > set ORACLE_HOME=<Oracle Home Path> 
    
  5. Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:

    > opatch rollback -id 16803775  
    
  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 Patch Deinstallation Instructions for RAC

Follow these steps on each node in the cluster:

Stop the Oracle services only on the node from where the patch is being uninstalled

The order of uninstalling the patch is RDBMS_HOME, then GRID_HOME

  1. Uninstalling patch from database home: Before uninstalling the patch in RDBMS_HOME, the ASM and CRS services can be running

    Stop Oracle Services on the current node as listed below:

    > srvctl stop service -d <database name> -s <configured workload management service> -i <instancename>
    > srvctl stop instance -d <dbname> -i <instance name>

    • net stop OracleService<SID>
    • net stop Oracle<SID>VSSWriterService
    • net stop OracleDBConsole<SID>
    • net stop msdtc
    • net stop OracleMTSRecoveryService
    • net stop OracleRemExecService

  2. Set the ORACLE_HOME environment variable properly

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

    > opatch rollback -id 16803775 -local
    
  4. Uninstalling patch from Grid home: Before uninstalling the patch in GRID_HOME, 'unlock' the Grid Home to prepare it for patching and stop Oracle High Availability Services (OHASD) & all Oracle Services:

    > srvctl stop service -d <database name> -s <configured workload management service> -i <instancename>
    > srvctl stop instance -d <dbname> -i <instance name>
    > %ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install %ORACLE_HOME%\crs\install\rootcrs.pl -unlock

    To verify that there are no longer any resources running on the node to be un-patched, run the following command from another node with GRID running:

    > crsctl status resource -t

    Then use the Computer Management Services GUI or the net stop command to stop ALL Oracle services running on that node:

    • net stop OracleService<SID>
    • net stop OracleDBConsole<SID>
    • net stop "Oracle <SID> VSS Writer Service"
    • net stop OracleREMExecService
    • net stop "Oracle Object Service"
    • net stop ocfs (required only for OCFS installation)
    • net stop orafenceservice
    • net stop OracleMTSRecoveryService

  5. Set the ORACLE_HOME environment variable properly

  6. Ensure that the directory containing the OPatch script appears in your PATH setting. Rollback the patch on this node using the command listed below.

    > opatch rollback -id 16803775 -local
    
    
  7. Start the services running out of grid home and the instance on this node.

    > %ORACLE_HOME%\perl\bin\perl -I%ORACLE_HOME%\perl\lib -I%ORACLE_HOME%\crs\install %ORACLE_HOME%\crs\install\rootcrs.pl -patch

    When the stack is up, start the oracle instance on the node

    > srvctl start instance -d <dbname> -i <instance name>

  8. Stop Oracle Service OraFenceService, and replace the file orafenceservice.sys located under %s_systemDirectory%/drivers with the file backed up during patch apply. Reboot the node.

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

3.4.3 Patch Deinstallation instructions for Oracle Instant Client

Follow these steps:

  1. If you patched the Oracle Instant Client installation by following the steps in Section 3.3.4, "Patch Installation Instructions for Oracle Instant Client", you can roll back this patch by re-copying the oci.dll, oraociei11.dll, oraociei11.sym, oraociicus11.dll, oraociicus11.sym, sqora32.dll, sqoras32.dll, sqresja.dll and sqresus.dll, file to the installation.

3.4.4 Patch Deinstallation instructions for ODAC installation

Follow these steps:

  1. If you patched the ODAC installation by following the steps in Section 3.3.5, "Patch Installation Instructions for ODAC installation", you can roll back this patch by re-copying the backup of the replaced binaries to the installation.

3.4.5 ODP.NET 2.x Deinstallation Instructions

Follow these steps only if you are using ODP.NET:

  1. Open a command prompt. (Open via "Run As Administrator" if applying on Windows 7 or 2008R2 and User Account Control is enabled).

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

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

     oraprovcfg.exe /action:gac /providerpath:Oracle.DataAccess.dll
    

3.4.6 ODP.NET 4.0 Deinstallation Instructions

Follow these steps only if you are using ODP.NET:

  1. Open a command prompt. (Open via "Run As Administrator" if applying on Windows 7 or 2008R2 and User Account Control is enabled).

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

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

     oraprovcfg.exe /action:gac /providerpath:Oracle.DataAccess.dll
    

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

  4. 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%\rdbms\admin
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> STARTUP
    SQL> @catbundle_WINBUNDLE_<database SID>_ROLLBACK.sql
    SQL> QUIT
    
  5. Check the log file for any errors. The log file is found in $ORACLE_BASE/cfgtoollogs/catbundle and is named catbundle_WINBUNDLE_<database SID>_ROLLBACK_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 4, "Known Issues".

  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. If catwinbundle_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> @utlrp.sql
    

    To check for invalid objects, execute the following statement:

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

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. Rename %ORACLE_HOME%\bin\oradv11.dll to %ORACLE_HOME%\bin\oradv11.dll_backup.

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

3.5.2 Enabling Database Vault

To enable 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, name the backup of the oradv11.dll file to its original name. For example, if you named it oradv11.dll_backup, then name it back to oradv11.dll.

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

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 catwinbundle.sql and catwinbundle_rollback.sql scripts

    ORA-20222: No workload capture is in progress!
    ORA-06512: at "SYS.DBMS_WORKLOAD_CAPTURE", line 1055
    ORA-20223: No workload replay is in progress!
    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-01927: cannot REVOKE privileges you did not grant
    ORA-04042: procedure, function, package, or package body does not exist
    SP2-0310: unable to open file "ctx/admin/bug13073613.sql"
    
  • Issue 2: If the NLS_LANG environment variable is set to Japanese_Japan.JA16EUC or Japanese_Japan.JA16SJIS, while executing catwinbundle.sql (and catwinbundle_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 catwinbundle.sql or catwinbundle_rollback.sql scripts, run the following SQL statement to change the nls_language setting:

    SQL>ALTER SESSION SET nls_language='American';
    
  • Issue 3: 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.

4.1.2 Platform-specific Issues

There are no known platform-specific issues.

4.2 Issues Specific to Oracle Database Release 11.2.0.3 Patch22

There are no known issues specific to 11.2.0.3 release.

4.3 Issues Specific to OPatch

4.3.1 Issue specific to OPatch 22.2.0.1.9

After opatch rollback, opatch rollback log file ORACLE_HOME\cfgtoollogs\opatch\opatch<time_stamp>.log may contain error similar to the following. This can be safely ignored.

[Dec 30, 2011 8:29:52 PM]    Finish rolling back patch from local system at Fri Dec 30 20:29:52 CST 2011
[Dec 30, 2011 8:29:52 PM]    The location "ORACLE_HOME\inventory\oneoffs\13413168" is not a directory or a valid patch zip file.
[Dec 30, 2011 8:29:52 PM]    Stack Description: java.lang.RuntimeException: java.lang.RuntimeException: Invalid patch location.
[Dec 30, 2011 8:29:52 PM]    StackTrace: oracle.opatch.opatchutil.OUSession.cleanup(OUSession.java:1497)
[Dec 30, 2011 8:29:52 PM]    StackTrace: oracle.opatch.OPatchSessionHelper.cleanup(OPatchSessionHelper.java:6007)
[Dec 30, 2011 8:29:52 PM]    StackTrace: oracle.opatch.RollbackSession.process(RollbackSession.java:3134)
[Dec 30, 2011 8:29:52 PM]    StackTrace: oracle.opatch.OPatchSession.main(OPatchSession.java:2057)
[Dec 30, 2011 8:29:52 PM]    StackTrace: oracle.opatch.OPatch.main(OPatch.java:653)
[Dec 30, 2011 8:29:52 PM]    Finishing RollbackSession at Fri Dec 30 20:29:52 CST 2011

4.3.2 Issue specific to OPatch 22.2.0.3

OPatch 22.2.0.3.0 locks srvm.jar when applying any 11.2.0.3 bundle patch on windows. For more details, please refer My Oracle Support Note 1446273.1.

4.4 Issues Specific to this Patch

Following bug is removed from the bundle from BP15 onwards, though it is listed in the inventory.

14323857 - IMPDP CONVERTS THE CODEPOINT OF LANGUAGE CHARACTERS IN ATTRIBUTES

Following bug is removed from the bundle from BP16 onwards, though it is listed in the inventory.

13262857 - INDEX CLUSTERING FACTOR COMPUTATION IS PESSIMISTIC

5 Bugs Fixed by This Patch

This patch fixes the following bugs.

5.1 Bugs Fixed for DB 11.2.0.3 Patch 22: 16803775

DB 11.2.0.3 Patch 22 includes all bugs fixed in 11.2.0.3 Patch 1 to Patch 21. It must be applied on top of the 11.2.0.3 base release or on top of any earlier bundle patch from 11.2.0.3 Patch 1 to Patch 21.

For a more descriptive list of the bug fixes included in this bundle patch, refer to My Oracle Support Note 1114533.1.

16694777 - SUPPORT DYNAMIC NETWORK TRACE AT PROCESS LEVEL

14467061 - FAILED INSTANCE RECOVERY MAY CAUSE ASM METADATA CORRUPTION/ORA-600[KFCRCVREAD10]

16530565 - SELF DEADLOCK IN 'LIBRARY CACHE PIN' IN A FUNCTION USING TYPE AND EDITION

14571027 - PL/SQL NATIVE COMPILATION GENERATES ABNORMALLY BIG INTERMEDIATE FILES

14512189 - ORA-1426 WHILE REFRESHING MV WHEN SEQUENCE VALUE TOO HIGH

14053457 - PRO*C++ INCORRECT HANDLING OF BIND VARIABLES ON 11R2

13857111 - HUGE SYSTEM STATE DUMPPED ALONG WITH PS RESOURCE DUMP

13855490 - CJQ CONSUME PGA MEMORY IN RAC 11.2

13814739 - "KQR X PO" ALLOCATIONS NOT BEING FREED IN A RAC ENVIRONMENT

13724193 - ORA-1089 FROM REMOTE DATABASE, EVEN THOUGH THE DB IS NOT SHUTTING DOWN

13493847 - ORA-600[15709] DUE TO RACE CONDITION B/W PMON AND SERVICE MANAGING Q DESCRIPTORS

12925089 - ORA-4031 DURING PROCESS STARTUP SOME TIMES ASSERTS WITH 'KSXP_RM_CHECK0'

12912137 - INSTANCE CRASHED BY SMON WITH ORA-600[4032]

12755116 - ORA-959 AFTER DEFAULT TABLESPACE IS DROPPED AND RENAMED WITH SAME DROPPED NAME

12395918 - ORA-7445 [KKSCSADDCHILDNODE()+468] UNDER HEAVY LOAD INVOLVING CURSOR CREATION

7509451 - INCREASE KSN WAITID MEMORY CAUSES ORA-4031

12940637 - MERGE STATSMENT CONSUMES HIGH CPU AFTER UPGRADE TO 11.2.0.2

16747736 - ORA-1341: LOGMINER OUT-OF-MEMORY AFTER UPGRADE TO 11.2.0.3 + PATCH 16

14302813 - CONCURRENCY WAITS: QC BLOCKED BY PQ SLAVES WHICH ARE ON PARSE CALLS

13258936 - UPGRADE RESULTS IN META DATA CORRUPTION IF SECTION TAG HAS A ':' IN IT

14273397 - Fix for bug 14273397

14459552 - Fix for bug 14459552

16703112 - Fix for bug 16703112

16306019 - Fix for bug 16306019

16014985 - Fix for bug 16014985

15905421 - Fix for bug 15905421

13561750 - Fix for bug 13561750

13791364 - Fix for bug 13791364

13015379 - Fix for bug 13015379

6690853 - Fix for bug 6690853

16382448 - Fix for bug 16382448

13774324 - Fix for bug 13774324

16279401 - Fix for bug 16279401

16279211 - Fix for bug 16279211

16555186 - ISSUE WITH DIAGCOLLECTION.PL COREANALYZE

16436434 - KERNEL PANIC CAUSED NODE CRASH WITH ORACLEACFS:OFS_D_REVALIDATE

16077216 - LNX64-12.1-CMP: DBCA DEL INS GET NUMBERFORMATEXCEPTION: INPUT STRING: ""

15978267 - KERNEL: ACFSK-0058: I/O FAILURE ON DEVICE DURING A USER DATA ASYNCH READ

15934834 - DF -K COMMAND HUNG AND CRASHED ACFS MOUNT POINTS

15920201 - OSYSMOND.BIN GROWING IN MEMORY AND CONSUMING HIGH CPU AFTER 11.2.0.3 UPGRADE

15911134 - ESSC: NETWORK RESTART COMMAND TURNS ALL RAC NODES INTO HANG

15856610 - IFDOWN; IFUP ON PRIVATE INTERFACE CAUSES CSS MISSED NETWORK HEARTBEATS, EVICTION

14639430 - ORA-600 [KSZADDOSSDEV8], [56840]

13936066 - REMOTE CTSSD COREDUMP SINCE CLSD CRASH WHEN STOP LOCAL STACK

13912274 - RES ORA.LISTENER_SCAN1.LSNR GO TO FAIL WHEN STOP ASM INST

15998768 - MEMORY LEAKING FOR OSYSMOND.BIN

13899736 - OCE SYMANTEC PRIVNIC ISSUE

5.2 Bugs re-done in DB 11.2.0.3 Patch 22: 16803775

14230270 - ORA-976 DIF ISSUE INTRODUCED WITH BUG#13441027 CHANGE

14010695 - W2K8_12.1_CRF:CRF RESOURCE FAILED TO START

5.3 Bugs Specific NOTES:

1) Bugs 13610777 and 13258936

Connect to sqlplus with
> sqlplus /nolog 
SQL> @?/ctx/admin/ctxPatch11203 <ctxsys password> 
SQL> QUIT 

2) Bug 13819727

If you plan to use 10G style AW's then

Connect to sqlplus with
> sqlplus /nolog 
SQL> @?/olap/admin/catawxml.sql
SQL> QUIT 
      
Otherwise skip this step.

3) Bug 13602883

The following config parameter needs to be set in all init.ora's and the instances restarted for the fix to take effect:
_first_spare_parameter=1


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 11.2.0.3 for Microsoft Windows (x64)

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