Bundle Patch Update Note
Release 10.2.0.5 for Microsoft Windows (x64-Bit) AMD
Released: June, 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.
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
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 XP Professional x64 Edition
Windows Server 2008 Standard x64 Editions
Windows Server 2008 Enterprise x64 Editions
Windows Server 2008 Data Center x64 Editions
Windows Vista with Service Pack 1 or later x64 Editions
Windows 2008 R2
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.
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 |
None |
|
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 |
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.
This patch fixes the following bugs.
10.2.0.5 Patch 10 includes all bugs fixed in 10.2.0.5 Patch 1 to 10.2.0.5 Patch 9. It must be applied on top of the 10.2.0.5 base release or on top of any bundle patches released prior to 10.2.0.5 Patch 9
For a more descriptive list of the bug fixes included in this bundle patch, refer to My Oracle Support Note 342443.1.
For list of the bug fixes included in the 10.2.0.5 patch bundles for the Microsoft Windows platforms, which are under fix control, refer to My Oracle Support Note 1097085.1.
11066597 - DISKGROUP WAS DISMOUNTED WHILE STORAGE CABLE WAS PULLED OUT ON THE OTHER NODE.
9935787 - MANY SESSIONS WAITING FOR 'CURSOR PIN S WAIT ON X'
10236704 - ODBC TNS SERVICE NAME DROP DOWN LIST IS NOT FULLY QUALIFIED
11853331 - CBO PERFORMANCE PROBLEMS WITH INLIST ITERATION AND VIEW PROCESSING
9825461 - DATABASE MIGRATION ASSISTANT FOR UNICODE (DMU) RDBMS SERVER-SIDE FUNCTIONS
8411930 - TRADITIONAL EXP/IMP CHANGES VPD POLICY TYPES FROM CONTEXT_SENSITIVE TO DYNAMIC
6651220 - ORA-7445 [TTCFOPR] IS RAISED WHEN PL/SQL USING DBLINK
7026523 - ORA-07445 [KDBLAILB] ERRORS WHILE USING IMPDP
8882576 - GES RESOURCE INCREASES CONTINUOUSLY.
9360157 - WRONG RESULTS WHEN USING ORA_ROWSCN PSEUDOCOLUMN USING ANSI JOIN
10068982 - PL/SQL PROGRAM REPEATS CONCAT SHOWS SLOW PERFORMANCE AFTER APPLYING 10.2.0.5
10173237 - CROSS INSTANCE ARCHIVAL FAILING AFTER UPGRADE TO 10.2.0.5
10324526 - ORA-600 [KDDUMMY_BLKCHK] [6106] WHEN UPDATE SUBPARTITION OF TABLE IN TTS
8332730 - ORA-600 [KOLE_T2U] DURING SELECT V$SQL_PLAN.OTHER_XML
7516536 - ORA-600 [KFCMAKEFREE30] ERROR AFTER APPLYING PATCH 7357281
11814891 - ORA-600 [7999] [9] [1] [ LOB BLOCK RDBA ] DOUBLE ALLOCATED LOB BLOCK
9871302 - DEDICATE CONNECTS FAILS TNS-12518 AND TNS-12560
6055658 - JOIN CARDINALITY IS IN THE PRESENCE OF HISTOGRAMS INCORRECT CALCULATED
12363485 - WRONG RESULT USING UNION ALL
10220194 - CRSD.EXE AND RACGIMON.EXE CONSUMES NON-PAGED POOL.
7592673 - IN LIST ITERATOR NOT CHOSEN WITH NO STATS AND DYNAMIC SAMPLING
10202758 - OCIDESCRIBEANY() FAILED TO FIND AN UDT OBJECT
9735237 - ORA-7445 [_INTEL_FAST_MEMCMP()+30] DURING STRESS TESTING
10052339 - WRONG RESULTS OR DUMP ON [LDXETI()+20]
The following script needs to be run after applying the patch only if you use the Database Migration Assistant for Unicode (DMU)
SQL>@?/rdbms/admin/prvtdumi.plb
This section includes the following sections:
Components patched by this Bundle Patch Update:
RDBMS
OLAP
NETWORK
PCW
WINPROD
You must use the OPatch utility release 10.2.0.5.1 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, "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 10.2.0.5 Bundle patch to an Oracle Database Release 10.2.0.5.
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.
Shutdown all MTS/COM+/.Net applications that access Oracle databases.
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 12429524
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".
This is a Rolling-RAC patch, Stop the Oracle services only in the home where the patch is being applied
|
Note: Querying the GV$DATAFILE before all the nodes are patched to this bundle will result in the following error.ORA-12850: Could not allocate slaves on all specified instances: %s needed, %s allocated. |
The order of patching in RAC install is CRS_HOME, ASM_HOME and RDBMS_HOME
Before Patching CRS_HOME, stop OCR related resources, Cluster Ready Services (CRS) Services and all Oracle Services:
> srvctl stopservice -d <database name> -s <Configured workload management service> -i <instance name>> srvctl stopinstance -d <database name> -i <instance name>> srvctl stopasm -n <nodename>> srvctl stopnodeapps -n <nodename>> crsctl stopcrs
Use the net stop command to stop ALL Oracle services running on the current node:
net stop OracleService<SID>
net stop Oracle<homename>TNSListenerLISTENER_<nodename>
net stop OracleDBConsole<SID>
net stop OracleASMService<ASMSID>
net stop OracleREMExecService
net stop OracleCRService
net stop OracleEVMService
net stop OracleCSService
net stop OracleObjectService
net stop OracleClusterVolumeService
net stop Orafenceservice
Note: An explicit 'srvctl start listener -n <nodename>' should be issued after patching
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:
> srvctl stopservice -d <database name> -s <configured workload management service> -i <instancename>> srvctl stopinstance -d <dbname> -i <instance name>> srvctl stopasm -n <nodename>> srvctl stoplistener -n <nodename>
Use the net stop command to stop the following Oracle services running on that node:
net stop OracleService<SID>
net stop Oracle<homename>TNSListenerLISTENER_<nodename>
net stop OracleDBConsole<SID>
net stop OracleASMService<ASMSID>
Note: An explicit 'srvctl start listener -n <nodename>' should be issued after patching
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:
> srvctl stopservice -d <database name> -s <configured workload management service> -i <instancename>> srvctl stopinstance -d <dbname> -i <instance name>
Use the net stop command to stop the following Oracle services running on that node:
net stop OracleService<SID>
Note: For combined ASM_HOME/RDBMS_HOME, complete all steps in the previous and current section
Note: The above assumes the listener is run from the ASM home
Set the ORACLE_HOME environment variable properly
Go to the directory where you downloaded the patch:
> cd 12429524
Ensure that the directory containing the OPatch script appears in the PATH setting. Enter the following command to run OPatch:
> opatch apply
Before patching each node OPatch will prompt for user input, at this point please make sure that all the services running on that node are stopped. Once a node has been patched, services on that node can be brought up.
Stop everything outlined in step 1 with the addition of the following:
net stop orafenceservice
Take a backup of file orafencedrv.sys located under %SystemRoot%\system32\drivers
Replace orafencedrv.sys with orafencedrv.sys supplied in the patch under 12429524.
Reboot the node for the driver to take effect.
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:
Back up the existing files oraociei10.dll, oraociicus10.dll, sqora32.dll in the Instant Client installation.
Replace the oraociei10.dll file in the Instant Client installation by the file oraociei10.dll from the 12429524\files\instantclient directory.
Replace the oraociicus10.dll file in the Instant Client installation by the file oraociicus10.dll from the 12429524\files\instantclient\light directory.
Replace the sqora32.dll file in the Instant Client installation by the file sqora32.dll from the 12429524\files\bin directory.
Follow the Instant Client Installation Procedure for your product as follows.
After installing the patch, perform the following actions:
Load modified .sql files into the database, as explained in Section 3.3.5.1.
To load modified .sql files into the database, 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.
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.
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\Patch10 > sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> @catcpu.sql SQL> QUIT
In a Data Vault installation, please run the following
> cd %ORACLE_HOME%\rdbms\admin
> sqlplus /nolog
Create DV_PATCH_ADMIN role (one-time task)
SQL> CONNECT DVSYS
SQL> CREATE ROLE DV_PATCH_ADMIN;
SQL> GRANT DV_PATCH_ADMIN TO DV_OWNER WITH ADMIN OPTION;
SQL> GRANT DV_PATCH_ADMIN TO SYS;
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
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> @catols.sql
SQL> STARTUP
SQL> @catmacpatch.sql
SQL> QUIT
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.
In a Data Vault installation, please run the following
Revoke DV_PATCH_ADMIN from SYS: SQL> CONNECTSQL> REVOKE DV_PATCH_ADMIN FROM SYS;
Check the log file for any errors. The log file is found in %ORACLE_HOME%\cfgtoollogs\catbundle and is named catbundle_WINBUNDLE_<database SID>_APPLY_<TIMESTAMP>.log, where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS.
If there are errors, refer to Section 4, "Known Issues".
The expected patch level in registry$history for this bundle is Patch 10.
If catcpu.sql reports any Invalid Objects, compile the invalid objects as follows.
(For large numbers of objects, this compilation step can take some time. If you are applying this patch through the Oracle Enterprise Manager console, you will be prompted to run this compilation script.)
> cd %ORACLE_HOME%\rdbms\admin > sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @utlprp.sql 0
To check for invalid objects, execute the following statement:
SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID';
Exit from SQL*Plus.
SQL> QUIT
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 non-RAC environments and RAC environments when a database is created or upgraded after the installation of Bundle Patch 10.
You must execute the steps in Section 3.3.5.1, "Loading Modified .sql Files into the Database" for any new database that was created by any of the following methods:
This section includes the following topics.
Section 3.4.1, "Patch Deinstallation Instructions for Single Instance"
Section 3.4.3, "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.5.1, "Loading Modified SQL Files into the Database" against the database before deinstalling the CPU.
Before rolling the patch back, connect as sys and execute the following:
SQL> @?/rdbms/admin/bug8811401_pre_uninstall.sql
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>
Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:
> opatch rollback -id 12429524
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".
This is a Rolling-RAC patch, Stop the Oracle services only in the home where the patch is being rolled back
The order of de-installing a patch in RAC install is RDBMS_HOME, ASM_HOME and CRS_HOME
Before De-installing Patch from RDBMS_HOME, the ASM and CRS services can be running but Oracle RDBMS Services on the current node needs to be stopped
Before De-installing Patch from 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
Before De-installing Patch from Patching CRS_HOME, all services on the current node needs to be stopped
Set the ORACLE_HOME environment variable properly
Ensure that the directory containing the OPatch script appears in the PATH setting. Enter the following command to run OPatch:
> opatch rollback -id 12429524
Before rolling back patch on each node OPatch will prompt for user input, at this point please make sure that all the services running on that node are stopped. Once the patch had been rolled back on a node, services on that node can be brought up.
Stop Oracle Service OraFenceService, and replace the file orafencedrv.sys located under %SystemRoot%\system32\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, "Installation Instructions for Oracle Instant Client", you can roll back this patch by re-copying the oraociei10.DLL, oraociicus10.dll, sqora32.dll file to the installation.
If there are errors, refer to Section 4, "Known Issues".
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.
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.
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\Patch10 > sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> @catcpu_rollback.sql SQL> QUIT
In a Data Vault installation, please run the following
> cd %ORACLE_HOME%\rdbms\admin
> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
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> @catols.sql
SQL> STARTUP
SQL> QUIT
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.
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".
If catcpu_rollback.sql reports any Invalid Objects, compile the invalid objects as follows.
(For large numbers of objects, this compilation step can take some time. If you are applying this patch through the Oracle Enterprise Manager console, you will be prompted to run this compilation script.)
> cd %ORACLE_HOME%\rdbms\admin > sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @utlprp.sql 0
To check for invalid objects, execute the following statement:
SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID';
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.
Ensure that the OracleService and Oracle Listener Services are not running.
Under ORACLE_HOME\bin, rename the oradv10.dll file, for example,oradv10_backup.dll.
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.
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\Patch10 > sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP
Unlock the DVSYS account and set the password:
SQL> ALTER USER DVSYS ACCOUNT UNLOCK;
SQL> ALTER USER DVSYS IDENTIFIED BY password;
Disable the Oracle Database Vault triggers:
SQL> CONNECT DVSYS/password
SQL> ALTER TRIGGER DVSYS.DV_BEFORE_DDL_TRG DISABLE;
SQL> ALTER TRIGGER DVSYS.DV_AFTER_DDL_TRG DISABLE;
To enable Database Vault, follow these steps:
Lock the DVSYS account:
> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> ALTER USER DVSYS IDENTIFIED BY password;
SQL> ALTER USER DVSYS ACCOUNT LOCK;
Enable the Database Vault triggers as DV owner:
SQL> CONNECT <DV_Owner>/<DV_Owner_password> SQL> ALTER TRIGGER DVSYS.DV_BEFORE_DDL_TRG ENABLE; SQL> ALTER TRIGGER DVSYS.DV_AFTER_DDL_TRG ENABLE;
Shutdown the database:
SQL> CONNECT SYS as SYSDBA SQL> SHUTDOWN SQL> QUIT
Ensure that the OracleService and Oracle Listener Services are not running.
Under ORACLE_HOME\bin, name the backup of the oradv10.dll file to its original name. For example, if you named it oradv10_backup.dll, then name it back to oradv10.dll.
For RAC systems, perform steps 2 and 3for 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 (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-01927: cannot REVOKE privileges you did not grant 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-06550: 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
The following ignorable error may be encountered while running catcpu_rollback.sql
ORA-20003: Specified bug number (5099019) does not exist SP2-0310: unable to open file "rdbms/admin/bug8811401_pre_install.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.
Issue 4: 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: My Oracle Support Note 131752.1.)
There are no known platform-specific issues.
There are no known issues specific to 10.2.0.5 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 10.2.0.5 for Microsoft Windows (32-Bit)
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.