Skip Headers
 
 

Oracle® Database Server Version 11.1.0.7 Patch 22

Bundle Patch Update Note

Release 11.1.0.7 for Microsoft Windows (x64)

 

Released: Jan, 2010

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.

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

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.

2.1 Bugs Fixed by This Patch

This patch fixes the following bugs.

2.1.1 Bugs Fixed for DB 11.1.0.7 Patch 22: 9166861

DB 11.1.0.7 Patch 22 includes all bugs fixed in 11.1.0.7 patch1 to patch21. It must be applied on top of the 11.1.0.7 base release or on top of any earlier bundle patches 11.1.0.7 Patch 1 through Patch 21.

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

8898852 - DATAFILE CORRUPTION WHEN FILE CREATED WITH COMPATIBLE.ASM LESS THAN 11 RESIZED

9024617 - TAF FAILS WITH ORA-12571 WHEN PULLING PUBLIC NETWORK AND PASSING KEEPALIVETIME

8836110 - HEADER FILES FOR C-APIS MISSING ON WINDOWS

7631837 - TB: CRSD CORE DUMP IN PROCR_CACHING_RETRY AT PROCR.C:7357

8317708 - CRS DOES NOT START ON ONE NODE CSS CRASHES.

8969658 - OCFS.SYS IN 11.1.0.7PATCH16 DOESN'T HAVE DIGITAL SIGNATURE

8969710 - ORAFENCEDRV.SYS INCLUDED IN 11.1.0.7PATCH16 DOESN'T HAVE DIGITAL SIGNATURE

8328259 - TAF/RAC: QUERIES DO NOT FAIL OVER (SESSIONS DO) IN CERTAIN CONDITIONS - SOLARIS

8850303 - ORA-600 [PEVMEXE.C: BREAK: BUG 281522 : HIT OPCODE BREAK] - COMPOUND TRIGGER

7477246 - DISKS TAKEN OFFLINE DURING SYNCING PHASE OF THE ONLINE DISK COMMAND

8674263 - TB_X64_ASM: ORA-00600: [KFIOTRANSLATEIO05] DURING ASM STRESS TEST

8851675 - STBH: BAD PARTNERING CAUSES PREMATURE ALLOCATION FAILURES

7441663 - FIX MINIMUM BUFFER CACHE SIZE CALCULATION

7829321 - TB:SH: CKPT HIT ORA-00600: [KCBKLLRBA_1] ORA-00600:[KCBKVAQ_9], INSTANCE CRASHED

8217795 - PATCH 7409110 APPLIED STILL HAVING WARNING:COULD NOT SET THE ASYNCH I/O LIMIT

8790767 - APPSST GSI 11G: INSTANCE CRASHED WITH ORA-600[KCBKLLSCN_1] ERRORS

7119382 - V$DATAGUARD STATS RETURNS MISLEADING AND INCONSISTENT RESULTS

8328853 - SR11.2EVENTLESS - COORDINATOR ARCH IN PARALLEL ARCHIVAL ORA-600 [KRSFRFRB.2]

9188010 - CORE DUMP IN KGLDMP WHEN USING RAC AND DUMPING SYS.REGISTRY$CTX

8613137 - TABLE UPDATE GENERATES AN ORA-600 [6200]

8724099 - NO KGL NAMESPACE EXISTS FOR CONTEXT MVDATA SECTION OBJECT

7307972 - HIGH VALUE FOR LIBRARY CACHE: MUTEX X IN AWR AS TOP WAIT EVENT

6407486 - ORA-600 [KOLE_T2U] USING A BLOB TABLE

6843972 - ORA-600 [KOLE_T2U] USING SYS.HTTPURITYPE

8717461 - ORA-00494 ON THE DB NODES HOSTED ON EXADATA WAIITING ON KSV MASTER WAIT

8250560 - ORA-979 REPORTED INCORRECTLY IN 11G

7189491 - GROUPBY WITH SUB SELECT DOESN'T WORK AFTER UPGRADE TO 11.1.0.6.

9038070 - WRONG RESULTS WITH EXISTS SUBQUERY

7384419 - LNX11.2: ORA-7445 SIGSEGV AT KGAVSS_STACKLET_STARTING()+27

7334226 - GES RECEIVERS ARE NOT HEALTHY

7653579 - ASM INSTANCE EVICTED WITH ORA-29740

8348481 - TB_X64:SH: DBWR HIT ORA-00600: [KJBWRDONE:!OP], INSTANCE CRASHED.

7662491 - INSTANCE CRASH / ORA-600 [KDDUMMY_BLKCHK] HIT DURING RECOVERY

7715244 - COMPRESS WITH SQLLDR CONVENTIONAL PATH [KDBLKCHECKERROR], [4], [1413], [6110]

8277580 - ORA-07445: [__INTEL_NEW_MEMCPY()+44]

8287680 - OLTP TABLE COMPRESSION INSERT PERFORMANCE

8199107 - APPSST11107: GOT ORA-07445 DURING R12.1.1 XBUILD3 UPGRADE

8483871 - SECUREFILE IS SLOWER WHEN DB_BLOCK_CHECKING=TRUE IS SET

8549480 - APPSST GSI 11G: ORA-600[KDLIMEMVALIDATE] DURING DB UPGRADE

6903819 - PHSB: ORA-19648 RAISED DURING BACKUP ON READABLE STANDBY

7462589 - RMAN BACKUP AS COPY REUSE DATAFILE 5 AUXILIARY FORMAT '+BAKGDR' FAILED ORA-19504

7447559 - LIBRARY CACHE LOCKS ON ALL JOB PROCESSES

7626014 - TB:SH: ORA-00600:[KKSFBC-NEW-CHILD-THRESH-EXCEEDED], [], [], IN LONG RUNNING

9066130 - APPSST GSI 11G :-ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [KKSFBC-WRONG-KKSCSF

9075688 - MERGE REQUEST ON TOP OF 11.1.0.7.0 FOR BUGS 6647480 6768362

8364676 - ROW CACHE LOCK CONTENTION WHEN COMPRESSING TABLE USING ALTER TABLE

8834636 - CONCURRENT INSERTS INTO COMPRESSED TABLE CAUSES HIGH CPU AND BUFFER BUSY WAITS

8876094 - APPSST GSI 11G :- ORA-00308 IN ALERT LOGS OF OUR ENVIRONMENT

7257038 - USING DBMS_REDEFINITION ON STREAMS TABLE CAUSES MISSING STREAMS MVDD

7377810 - APPS R12: LARGE BUFFER_GETS DURING HARD PARSE

8588540 - ORA-08102: INDEX KEY NOT FOUND RETURNED ON SOME UPDATES.

8539335 - ORA-600 [KTCIRS:HDS] REPORTED ON MULTIPLE NODES IN A RAC CLUSTER

8471310 - CAST DOES NOT WORK WHEN USING 'UNION ALL' IN A CTAS STATEMENT

7409110 - WARNING: ASYNCH I/O KERNEL LIMITS FROM LGWR & DBW0

6784747 - WASTED SPACE - KOH-KGHU CALL ALLOCATION

8702535 - ORA-07445[KSLGETSL()+120] WHILE DUMPING SYSTEMSTATE AFTER APPLYING PATCH:7293345

9135679 - INSTANCE TERMINATED WITH ORA-00600 [KGSKEXITSCH]

8491088 - APPS_BM : ERROR DURING UPGRADE XDB.FUNCSTATS.ODCISTATSDELETE

8644684 - ORA-600 [QMXCONVUNKTYPE] DURING INSERT INTO SCHEMA-BASED TABLE

6148150 - CALL TO DBMS_XMLDOM.WRITETOCLOB RESULTS IN ORA-03113

8683472 - SCHEMA EXECUTABLE RETURNS INCORRECT ERRORS DURING VALIDATION AGAINST XML SCHEMA

2.1.2 Following bug has been included as part of MLR in 11.1.0.7 Patch22:

6647480 - AFTER EXECUTED ALLOCATE EXTENT, ORA-600 [KDDUMMY_BLKCHK] OCCURED REPEATEDLY

3 Patch Installation Procedures for Oracle Database Release 11.1.0.7

This section includes the following sections:

3.1 Components for Patch 9166861 for Oracle Database Release 11.1.0.7

    Components patched by this Bundle Patch Update:

    • Oracle Database

    • Oracle Net Required Support Files

    • PL/SQL

    • Oracle XML Development Kit

    • Oracle Core

    • Oracle RAC Required Support Files-HAS

    • SSL Required Support Files for InstantClient Patch

    • Precompiler Common Files

    • Precompiler Required Support Files

    • OLAP SQL Scripts

    • Oracle OLAP

    • Oracle Provider for OLE DB

    • Oracle Data Provider for .NET 2.x

    • Oracle ODBC Driver for Instant Client

    • Oracle Multimedia Locator

    • Oracle Net Listener

    • Oracle Data Vault

    • Oracle Database Utilities Patch

    • Oracle PCW

    • Oracle Enterprise Manager Console DB

    • Oracle Globalization Support

    • Enterprise Manager Agent

    • Oracle Text

3.2 OPatch Utility Information

You must use the OPatch utility release 11.1.0.6.2 or later.

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

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

  2. This patch must be applied on top of the 11.1.0.7 base release or on top of any earlier bundle patches 11.1.0.7 Patch 1 through Patch 21 with out 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. For customers using Statspack:

    It is recommended that you export the primary statspack schema as a backup before instaling this patch, either using your own export parameters or those provided in spuexp.par

    Disable the programs that use Statspack

    Run @spdrop and @sbdrop to drop both the primary and standby statspack schemas

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

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

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

3.3.2 Patch Installation Instructions

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 9166861 
    
  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 Installation Instructions for Customers Using RAC for Patching CRS

Follow these steps:

  1. Please note that this patch is RAC rolling upgradable for CRS, ASM homes and RDBMS homes.

    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

  2. Before Patching CRS_HOME, stop OCR related resources, Cluster Ready Services (CRS) Services and all Oracle Services:

    > srvctl stop service -d <database name> -s <configured workload management service> -i <instancename>
    > srvctl stop instance -d <dbname> -i <instance name>
    > srvctl stop asm -n <nodename>
    > srvctl stop nodeapps -n <nodename>
    > crsctl stop crs
    

    Then use the net stop command to stop ALL Oracle services running on that node:

    • net stop OracleService<SID>

    • net stop Oracle<homename>TNSListenerLISTENER_<nodename>

    • net stop OracleDBConsole<SID>

    • net stop OracleASMService<ASMSID>

    • net stop Oracle<SID>VSSWriterService

    • net stop OracleREMExecService

    • net stop OracleCRService

    • net stop OracleEVMService

    • net stop OracleCSService

    • net stop OracleObjectService

    • net stop OracleClusterVolumeService

    • net stop ocfs required only for OCFS installation

    • net stop Oraclefenceservice

    • Note: An explicit 'srvctl start listener -n <nodename>' should be issued after patching

  3. Before Patching ASM_HOME, CRS services can be running on all nodes.
    Stop OCR related resources and Oracle Services on the current node as listed below:

  4. > srvctl stop service -d <database name> -s <configured workload management service> -i <instancename>
    > srvctl stop instance -d <dbname> -i <instance name>
    > srvctl stop asm -n <nodename>
    > srvctl stop listener -n <nodename>
    
    • net stop OracleService<SID>

    • net stop Oracle<homename>TNSListenerLISTENER_<nodename>

    • net stop OracleDBConsole<SID>

    • net stop OracleASMService<ASMSID>

    • net stop Oracle<SID>VSSWriterService

    • Note: An explicit 'srvctl start listener -n <nodename>' should be issued after patching

  5. Before Patching RDBMS_HOME, the ASM and CRS services can be running.
    Stop OCR related resources and Oracle Services on the current node as listed below:

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

    • Note: For combined ASM_HOME/RDBMS_HOME, complete all steps in the previous and current section

  7. Set the ORACLE_HOME environment variable properly

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

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

    > opatch apply 
    

    opatch will attempt to apply the patch on all the nodes in the cluster sequentially. However will prompt for user input to start patching other nodes. At this time ensure that the Oracle services on target node are stopped before proceeding to patch. Once the opatch session completes patching this node, start the services and proceed applying patch to the next node.

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

  11. Replacing Oracle Fence driver:

  12. Stop Oracle Service OraFenceService if not already done

    Stop everything outlined in step 1 before proceeding further:

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

    If you are running Windows Server 2008, replace orafencedrv.sys with OraFencedrv.sys.w2k8 supplied in the patch under 9166861\bin.

    If you are NOT running Windows Server 2008, replace orafencedrv.sys with OraFencedrv.sys supplied in the patch under 9166861\bin.

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

    If using OCFS then proceed to next step in installing OCFS driver. If not Reboot the node.

  13. For Customers Using OCFS:

  14. Backup ocfs.sys located under %SystemRoot%\System32\drivers.

    If you are running Windows Server 2008, replace ocfs.sys with ocfs.sys.w2k864 supplied in the patch under 9166861\bin and Reboot the node.

    If you are NOT running Windows Server 2008, replace ocfs.sys with ocfs.sys.w2k364 supplied in the patch under 9166861\bin and Reboot the node.

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

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 oraociei11.dll file in the Instant Client installation with oraociei11.dll from the 9166861\files\instantclient directory.

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

  3. Backup and replace proc.exe file in the Instant Client installation with proc.exe from the 9166861\files\bin directory.

  4. Backup and replace sqora32.dll file in the Instant Client installation with sqora32.dll from the 9166861\files\bin directory.

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

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

3.3.5 Patch Installation Instruction for Patching Instant Client Based ODP.NET 11.1.0.6.20

If ODP.NET 11.1.0.6.20 was installed into an Oracle Home with regular Oracle Client, this step is not necessary. However, to patch an instant client based ODP.NET 11.1.0.6.20, follow these steps to appropriately patch ODP.NET.

Steps:

  1. Back up and replace the existing ODP.NET\bin\2.x\Oracle.DataAccess.dll with 9166861\files\odp.net\bin\2.x\Oracle.DataAccess.dll

  2. Back up and replace the existing bin\OraOps11w.dll with 9166861\files\odp.net\bin\2.x\OraOps11w.dll

  3. Back up and replace the existing bin\OraOLEDButl11.dll with 9166861\files\bin\OraOLEDButl11.dll

  4. Back up and replace the existing bin\OraOLEDBrfc11.dll with 9166861\files\bin\OraOLEDBrfc11.dll

  5. Back up and replace the existing bin\OraOLEDBrmc11.dll with 9166861\files\bin\OraOLEDBrmc11.dll

  6. Back up and replace the existing bin\OraOLEDBgmr11.dll with 9166861\files\bin\OraOLEDBgmr11.dll

  7. Back up and replace the existing bin\OraOLEDB11.dll with 9166861\files\bin\OraOLEDB11.dll

  8. Back up and replace the existing bin\OraOLEDBpus11.dll with 9166861\files\bin\OraOLEDBpus11.dll

  9. Back up and replace the existing bin\OraOLEDBrst11.dll with 9166861\files\bin\OraOLEDBrst11.dll

  10. Back up and replace the existing bin\OraOLEDB11us.dll with 9166861\files\bin\OraOLEDB11us.dll

  11. Use regsvr32 to register oraoledb11.dll:

    run 'regsvr32 oraoledb11.dll' from %ORACLE_HOME%\bin

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. The same applies to policy DLL.

  4. Execute the following to redirect all application references of policy dll:

     gacutil /i Policy.<2.x>.Oracle.DataAccess.dll (for 2.x policy dll)
    

3.3.7 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.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. 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 catcpu.sql as follows:

    > cd %ORACLE_HOME%\Bundle\Patch22
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> STARTUP
    SQL> @catcpu.sql
    SQL> QUIT 
    
  5. In a Data Vault installation, please run the following

    > cd %ORACLE_HOME%\rdbms\admin
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> insert into dvsys.rule_set_t$ (id#, name, description,fail_message, language) 
         values(8, 'Allow Datapump Operation','Rule set that controls the objects that can be exported '||'or imported by the datapump user.',NULL, 'us');
    SQL> @catmac.sql SYSAUX TEMP SYS_password DV_OWNER_USERNAME DV_OWNER_password DV_ACCOUNT_MANAGER_USERNAME DV_ACCOUNT_MANAGER_password
    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%\cfgtoollogs\catbundle\catbundle_WINBUNDLE_<ORACLE_SID>_APPLY_<timestamp>.log for any errors.

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

  8. For customers using Statspack: Reinstall primary and standby statspack

  9. To ensure all dependant objects are valid after running catcpu.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 catcpu.sql script) for any new database you create or database upgraded to this release since the Bundle patch was applied.
3.3.8.2 Recompiling Views in the Database

You must recompile views for all databases except the following:

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.3.8 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.7.1, "Loading Modified .sql Files into the Database" and Section 3.3.7.2, "Recompiling Views in 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.7.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.7.1, "Loading Modified .sql Files into the Database" and Section 3.3.7.2, "Recompiling Views in 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.1.0.7

This section includes the following topics.

3.4.1 Patch Deinstallation Instructions

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 9166861 
    
  5. Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:

    > opatch rollback -id 9166861  
    
  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 Customers Using RAC for Patching CRS

Follow these steps:

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

The order of uninstalling the patch is RDBMS_HOME, ASM_HOME and CRS_HOME

  1. Before uninstalling the patch in RDBMS_HOME, the ASM and CRS services can be running but Oracle RDBMS Services on the current node needs to be stopped

  2. Before uninstalling the patch in 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 uninstalling the patch in CRS_HOME, all 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 9166861 
    
  6. Ensure that the directory containing the OPatch script appears in your PATH setting. Patch this node using the command listed below.

    > opatch rollback -id 9166861 
    

    opatch will attempt to uninstall the patch on all the nodes in the cluster sequentially. However will prompt for user input to start uinstalling on other nodes. At this time ensure that the Oracle services on target node are stopped before proceeding to remove the patch. Once the opatch session completes removing the patch on this node, start the services and proceed to the next node.

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

  8. Replace ocfs.sys located under %SystemRoot%\System32\drivers with the file backed up during patch apply. Reboot the node for OCFS driver to take effect.

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 oraociei11.dll, oraociei11.sym, oraociicus11.dll, oraociicus11.sym, proc.exe and sqora32.DLL file to the installation.

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

3.4.4 Patch Deinstallation Instruction for Instant Client Based ODP.NET 11.1.0.6.20

Follow these steps:

  1. Replace the existing ODP.NET\bin\2.x\Oracle.DataAccess.dll from backup location

  2. Replace the existing ODP.NET\bin\2.x\OraOps11w.dll from backup location

  3. Replace the existing bin\OraOLEDButl11.dll from backup location

  4. Replace the existing bin\OraOLEDBrfc11.dll from backup location

  5. Replace the existing bin\OraOLEDBrmc11.dll from backup location

  6. Replace the existing bin\OraOLEDBgmr11.dll from backup location

  7. Replace the existing bin\OraOLEDB11.dll from backup location

  8. Replace the existing bin\OraOLEDBpus11.dll from backup location

  9. Replace the existing bin\OraOLEDB11us.dll from backup location

  10. Replace the existing bin\OraOLEDBrst11.dll from backup location

  11. Use regsvr32 to register oraoledb11.dll:

    run 'regsvr32 oraoledb11.dll' from %ORACLE_HOME%\bin

3.4.5 ODP.NET 2.x Deinstallation 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 previous 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. The same applies to policy DLL.

  4. Execute the following to install the previous policy dll and redirect all application references of policy dll:

     gacutil /i Policy.<2.x>.Oracle.DataAccess.dll (for 2.x policy dll)
    

3.4.6 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%\Bundle\Patch22
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> STARTUP
    SQL> @catcpu_rollback.sql
    SQL> QUIT
    
  5. In a Data Vault installation, please run the following

    > cd %ORACLE_HOME%\rdbms\admin
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> insert into dvsys.rule_set_t$ (id#, name, description,fail_message, language) 
         values(8, 'Allow Datapump Operation','Rule set that controls the objects that can be exported '||'or imported by the datapump user.',NULL, 'us');
    SQL> @catmac.sql SYSTEM TEMP SYS_password DVSYS_password
    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%\cfgtoollogs\catbundle\catbundle_WINBUNDLE_<ORACLE_SID>_ROLLBACK_<timestamp>.log for any errors.

    If there are errors or invalid objects, 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> @utlrp.sql
    

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

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. 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. Connect to the database using SQL*Plus as SYSDBA and follow these steps:

    SQL> CONNECT SYS/ AS SYSDBA 
    SQL> STARTUP 
    

    Unlock the DVSYS account and set the password:

    SQL> ALTER USER DVSYS ACCOUNT UNLOCK;
    

    Disable the Oracle Database Vault triggers:

    SQL> CONNECT SYS/ AS SYSDBA
    SQL> ALTER TRIGGER DVSYS.DV_BEFORE_DDL_TRG DISABLE;
    SQL> ALTER TRIGGER DVSYS.DV_AFTER_DDL_TRG DISABLE;
    

3.5.2 Enabling Database Vault

To enable Database Vault, follow these steps:

  1. Connect to the database using SQL*Plus as SYSDBA and follow these steps:

    Lock the DVSYS account:

    SQL> CONNECT SYS/ as SYSDBA
    SQL> ALTER USER DVSYS ACCOUNT LOCK;
    

    Run the following command as the SYS user:

    SQL> @?/rdbms/admin/utlrp.sql
    

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

  4. For RAC systems, perform steps 2 and 3 for 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
    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.

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

There are no known issues specific to 11.1.0.7 release.

4.3 Issues Specific to OPatch

There are no known issues specific to OPatch.

4.4 Issues Specific to this Patch

After performing patch deinstallation procedure following objects could be invalid.

  • SDO_INDEX_METHOD_10I
  • SDO_PQRY
  • KU$_SCHEMAOBJNUM_VIEW
  • To correct these invalid objects run the following and check for invalid objects.

    > cd %ORACLE_HOME%\Bundle\Patch22
    > sqlplus /nolog 
    SQL> CONNECT / AS SYSDBA 
    SQL> STARTUP
    SQL> @sdocpu_undo.sql
    SQL> @catnomta_undo.sql
    SQL> @?/rdbms/admin/utlrp.sql
    SQL> QUIT 
    

    5 References

    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 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 337288.1 OPatch Fails to Detect Operating System Appropriately

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

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

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