Bundle Patch Update Note
Release 11.2.0.1 for Microsoft Windows (x64)
Released: May, 2011
This document includes the following sections:
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.
The following are the system requirements for this bundle patch:
Hardware requirement: AMD64, or Intel Extended memory (EM64T)
Operating system requirement:
Windows Server 2003, Standard x64 Edition
Windows Server 2003, Enterprise x64 Edition
Windows Server 2003, Datacenter x64 Edition
Windows Server 2003 R2, Standard x64 Edition
Windows Server 2003 R2, Enterprise x64 Edition
Windows Server 2003 R2, Datacenter x64 Edition
Windows Vista, Business x64 Edition
Windows Vista, Enterprise x64 Edition
Windows Vista, Ultimate x64 Edition
Windows XP Professional x64 Edition Service Pack 2 or later
Windows Server 2008
Windows Server 2008 R2
Windows 7
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 |
CPUJul2011 |
|
Client-Only Installations |
CPUJul2011 |
|
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 |
This patch fixes the following bugs.
DB 11.2.0.1 Patch 13 includes all bugs fixed in 11.2.0.1 Patch 1 to 11.2.0.1 Patch 12. It must be applied on top of the 11.2.0.1 base release or on top of any earlier bundle patches (11.2.0.1 Patch 1 to 11.2.0.1 Patch 12).
For a more descriptive list of the bug fixes included in this bundle patch, refer to My Oracle Support Note 1114533.1.
9554332 - PMON CRASH WITH ORA-600[KSUDLC K2GTCA]
12363485 - WRONG RESULT USING UNION ALL
10625485 - ORA-600 [KSS_GET_TYPE: BAD CONTROL] FROM CUSTOM PACKAGE USING DBMS_PIPE
9268192 - ORA-7445 [KKOIPT()+3650] WHEN OPTIMIZER_MODE=FIRST_ROWS_1000
9935787 - MANY SESSIONS WAITING FOR 'CURSOR: PIN S WAIT ON X'
10205230 - TB_X64: HIT ORA-600 [KCLWCRS_6]
12412745 - MISSING METADATA SLOW TO GET THROUGH ET VIEWS
Anyone wishing to install and use this bugfix will need to add the following to sqlnet.ora in all environments where the fix functionality is desired;
hostname.default_service_is_host = 1
Note that this applies primarily to SQL clients but may also be needed by servers if they are using the hostname adapter to make dblink connections.
Enable fix by setting "_fix_control"="9196440:ON"
This section includes the following sections:
Section 3.1, "Components for Patch 12429529 for Oracle Database Release 11.2.0.1"
Section 3.3, "Patch Installation Instructions for Oracle Database Release 11.2.0.1"
Section 3.4, "Patch Deinstallation Instructions for Oracle Database Release 11.2.0.1"
Components patched by this Bundle Patch Update:
Oracle Database
PL/SQL
XDB - XML Database
Oracle Advanced Queuing
Space
OLAP
NETWORK
ODP.NET 1.0
USM
ODBC
HAS
JAVAVM
PRECOMP
CTX
Instant Client
OPSM
You must use the OPatch utility release 11.2.0.1.2 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
This section includes the following topics.
Section 3.3.2, "Patch Installation Instructions for Single Instance"
Section 3.3.4, "Patch Installation Instructions for Oracle Instant Client"
Follow these steps:
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.1 Bundle patch to an Oracle Database Release 11.2.0.1.
This patch must be applied on top of the 11.2.0.1 base release or on top of any earlier bundle patches released prior to 11.2.0.1 Patch 13 without performing a rollback of earlier bundle patch.
Review Section 4, "Known Issues" before proceeding with this installation.
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.
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.
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.
Follow these steps:
Cleanly shut down all processes running from the ORACLE_HOME.
Set the ORACLE_HOME environment variable to the correct Oracle home that needs to be patched.
> set ORACLE_HOME=<Oracle Home Path>
Go to the directory where you downloaded the patch:
> cd 12429529
Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:
> opatch apply
Inspect the opatch<timestamp>.log file generated in %ORACLE_HOME%\cfgtoollogs\opatch for any errors.
If there are errors, refer to Section 4, "Known Issues".
Follow these steps:
Please note that this patch is RAC rolling upgradable for GRID, 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 GRID_HOME, then RDBMS_HOME
Before Patching GRID_HOME, stop OCR related resources, Oracle HASD Services (OHASD) Services and all Oracle Services:
> srvctl stopTo verify all resources have been moved to the other nodes, run the following command from another node with GRID running:service -d <database name> -s <configured workload management service> -i <instancename>> srvctl stopinstance -d <dbname> -i <instance name>> crsctl stopcrs
> 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 Oracle<CRShome>TNSListenerLISTENER_<nodename>
net stop Oracle<CRShome>TNSListenerLISTENER_SCANn
net stop OracleDBConsole<SID>
net stop OracleASMService<ASMSID>
net stop "Oracle <SID> VSS Writer Service"
net stop OracleREMExecService
net stop OracleOHService
net stop "Oracle Object Service"
net stop OracleClusterVolumeService
net stop ocfs (required only for OCFS installation)
net stop orafenceservice
Note: An explicit 'srvctl start listener -n <nodename>' should be issued after patching
Before Patching RDBMS_HOME, the GRID and ASM services can be running.
Stop OCR related resources and Oracle Services on the current node as listed below:
> srvctl stopservice -d <database name> -s <configured workload management service> -i <instancename>> srvctl stopinstance -d <dbname> -i <instance name>
net stop OracleService<SID>
net stop Oracle<SID>VSSWriterService
net stop OracleDBConsole<SID>
Set the ORACLE_HOME environment variable properly
Go to the directory where you downloaded the patch:
> cd 12429529
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.
NOTE:
When patching GRID_HOME on a node.Once the opatch session completes patching GRID_HOME on a node, start the services on the node and run the following before proceeding to patch GRID_HOME on the next node.
%ORACLE_HOME%\bin\acfsroot install |
Replacing Oracle Fence driver:
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.
Replace orafenceservice.sys with OraFencedrv.sys supplied in the patch under 12429529\.
Note:The filename in %SystemRoot%\System32\drivers is required to be orafenceservice.sys.
Reboot the node.
If you are NOT running Windows Server 2008, replace orafencedrv.sys with orafencedrv.sys supplied in the patch under 12429529.
If there are errors, refer to Section 4, "Known Issues".
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:
Backup and replace oraociei11.dll file in the Instant Client installation with oraociei11.dll from the 12429529\files\instantclient directory.
Backup and replace oraociei11.sym file in the Instant Client installation with oraociei11.sym from the 12429529\files\instantclient directory.
Backup and replace oraociicus11.dll file in the Instant Client installation with oraociicus11.dll from the 12429529\files\instantclient\light directory.
Backup and replace oraociicus11.sym file in the Instant Client installation with oraociicus11.sym from the 12429529\files\instantclient\light directory.
Follow these steps only if you are using ODP.NET:
Open a Visual Studio 2005 command prompt.
Navigate to the %ORACLE_HOME%\ODP.NET\bin\2.x directory.
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.
After installing the patch, perform the following actions:
Load modified .sql files into the database, as explained in Section 3.3.6.1.
To load modified .sql files into the database, follow these steps:
Start the OracleService<SID> and Oracle Listener Services if already not started.
Start all database instances running out of the ORACLE_HOME that you just patched.
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\Patch13 > sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> @catcpu.sql SQL> QUIT
Check the following log files in $ORACLE_HOME/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".
In a Data Vault installation, please run the following
Grant DV_PATCH_ADMIN to SYS as DV_OWNER user > cd %ORACLE_HOME%\rdbms\admin > sqlplus /nolog SQL> CONNECT <DV Owner User> Enter password: DV_OWNER_user_password SQL> GRANT DV_PATCH_ADMIN TO SYS; Reload the following script as SYSDBA SQL> CONNECT SYS/ as SYSDBA Enter password: SYS_password SQL> @?/rdbms/admin/catmacpatch.sql Perform step 6 for validating the objects through utlrp.sql Revoke DV_PATCH_ADMIN from SYS as DV_OWNER user SQL> CONNECT <DV Owner User> Enter password: DV_OWNER_user_password SQL> REVOKE DV_PATCH_ADMIN FROM SYS;
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, thecatcpu.sql script) for any new database you create or database upgraded to this release since the Bundle patch was applied. |
These instructions are for both RAC environments and non-RAC environments when a database is created or upgraded after the installation of Bundle Patch13.
You must execute the steps in Section 3.3.6.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.6.1, "Loading Modified .sql Files into the Database" was not executed after Bundle Patch13 was applied
Upgraded databases require that you perform the steps in Section 3.3.6.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.
This section includes the following topics.
Section 3.4.1, "Patch Deinstallation Instructions for Single Instance"
Section 3.4.3, "Patch Deinstallation instructions for Oracle Instant Client"
Follow these steps:
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.6.1, "Loading Modified SQL Files into the Database" against the database before deinstalling the patch.
Cleanly shut down all processes running from the ORACLE_HOME.
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.
Set the ORACLE_HOME environment variable to the correct Oracle home that was patched.
> set ORACLE_HOME=<Oracle Home Path>
Go to the directory where you downloaded the patch:
> cd 12429529
Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:
> opatch rollback -id 12429529
Inspect the opatch<timestamp>.log file generated in %ORACLE_HOME%\cfgtoollogs\opatch for any errors.
If there are errors, refer to Section 4, "Known Issues".
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, then GRID_HOME
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
Stop OCR related resources and 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>
Before uninstalling the patch in GRID_HOME, stop OCR related resources, Oracle HASD Services (OHASD) 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>
> crsctl stop crs
To verify all resources have been moved to the other nodes, 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 Oracle<CRShome>TNSListenerLISTENER_<nodename>
net stop Oracle<CRShome>TNSListenerLISTENER_SCANn
net stop OracleDBConsole<SID>
net stop OracleASMService<ASMSID>
net stop "Oracle <SID> VSS Writer Service"
net stop OracleREMExecService
net stop OracleOHService
net stop "Oracle Object Service"
net stop OracleClusterVolumeService
net stop ocfs (required only for OCFS installation)
net stop orafenceservice
Set the ORACLE_HOME environment variable properly
Go to the directory where you downloaded the patch:
> cd 12429529
Ensure that the directory containing the OPatch script appears in your PATH setting. Patch this node using the command listed below.
> opatch rollback -id 12429529
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.
Stop Oracle Service OraFenceService, and replace the file orafenceservice.sys located under %s_systemDirectory%/drivers with the file backed up during patch apply.
If there are errors, refer to Section 4, "Known Issues".
Follow these steps:
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 and oraociicus11.sym, file to the installation.
If there are errors, refer to Section 4, "Known Issues".
Follow these steps only if you are using ODP.NET:
Open a Visual Studio 2005 command prompt.
Navigate to the %ORACLE_HOME%\ODP.NET\bin\2.x directory.
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.
Follow these steps:
Start the OracleService<SID> and Oracle Listener Services.
Start all database instances running out of the ORACLE_HOME that you just patched.
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\Patch13
> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @?/rdbms/admin/catbundle_WINBUNDLE_<database SID>_ROLLBACK.sql
SQL> QUIT
Check the log file for any errors. The log file is found in $ORACLE_HOME/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".
In a Data Vault installation, please run the following
Grant DV_PATCH_ADMIN to SYS as DV_OWNER user
> cd %ORACLE_HOME%\rdbms\admin
> sqlplus /nolog
SQL> CONNECT <DV Owner User>
Enter password: DV_OWNER_user_password
SQL> GRANT DV_PATCH_ADMIN TO SYS;
Reload the following script as SYSDBA
SQL> CONNECT SYS/ as SYSDBA
Enter password: SYS_password
SQL> delete from dvsys.command_rule$ where code_id#=190;
SQL> delete from dvsys.code$ where id# = 190;
SQL> delete from dvsys.code_t$ where id# = 190;
SQL> update DVSYS.FACTOR$ SET GET_EXPR = 'UPPER(SYS_CONTEXT(''USERENV'',''ENTERPRISE_IDENTITY''))' where name='Enterprise_Identity';
SQL> update DVSYS.FACTOR$ SET GET_EXPR = 'UPPER(SYS_CONTEXT(''USERENV'',''PROXY_ENTERPRISE_IDENTITY''))' where name='Proxy_Enterprise_Identity';
SQL> update DVSYS.FACTOR$ SET GET_EXPR = 'UPPER(SYS_CONTEXT(''USERENV'',''SESSION_USER''))' where name='Session_User';
SQL> update DVSYS.FACTOR$ SET GET_EXPR = 'UPPER(SYS_CONTEXT(''USERENV'',''PROXY_USER''))' where name='Proxy_User';
Perform step 6 for validating the objects through utlrp.sql
Revoke DV_PATCH_ADMIN from SYS as DV_OWNER user
SQL> CONNECT <DV Owner User>
Enter password: DV_OWNER_user_password
SQL> REVOKE DV_PATCH_ADMIN FROM SYS;
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';
If there are errors, refer to Section 4, "Known Issues".
This section applies if you were instructed earlier to disable or enable Database Vault.
To disable Database Vault, see Section 3.5.1.
To enable Database Vault, see Section 3.5.2.
To disable Database Vault, follow these steps. (For RAC systems, perform steps 1 and 2 for each node on which the database is installed.)
Ensure that the OracleService and Oracle Listener Services are not running.
Rename %ORACLE_HOME%\bin\oradv11.dll to %ORACLE_HOME%\bin\oradv11.dll_backup.
For RAC systems, perform steps 1 and 2 for each additional node on which the database is installed.
Start the OracleService<SID> and Oracle Listener Services.
Start all database instances running out of the ORACLE_HOME that you just patched.
Connect to the database using SQL*Plus as SYSDBA and follow these steps:
SQL> CONNECT SYS/ AS SYSDBA SQL> STARTUP
To enable Database Vault, follow these steps:
Connect to the database using SQL*Plus as SYSDBA and follow these steps:
Shutdown the database:
SQL> CONNECT SYS/ as SYSDBA SQL> SHUTDOWN SQL> QUIT
Ensure that the OracleService and Oracle Listener Services are not running.
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.
For RAC systems, perform steps 2 and 3 for each node on which the database is installed.
This section includes the following information:
This section includes issues common to all Oracle Database releases:
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
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 "%ORACLE_HOME%/rdbms/admin/bug9371993.sql" SP2-0310: unable to open file "%ORACLE_HOME%/rdbms/admin/bug9460239.sql"
Issue 2: 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 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.
There are no known platform-specific issues.
There are no known issues specific to 11.2.0.1 release.
There are no known issues specific to OPatch.
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.1 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.