ТЕМА:

Товарищи!! Срочно нужен патч 10.2.0.4_p39_p10008101. Где бы его скачать?
Заранее благодарен!

так вам для какой платформы нужно-то?)

Анатолий Гав-Гав пишет: так вам для какой платформы нужно-то?)

Сорри, не указал - Windows 32!

Ааа, н тогда ловите - ссылка на скачивание с depositfiles:


Часть сообщения скрыта для гостей. Пожалуйста, авторизуйтесь или зарегистрируйтесь, чтобы увидеть его.

Спасибо товарисчи огромное!!!
А есть ли описание к патчу, мануал по установке?

Руди пишет: Спасибо товарисчи огромное!!!
А есть ли описание к патчу, мануал по установке?

Oracle® Database Server Version 10.2.0.4 Patch 39Bundle Patch Update Note

Release 10.2.0.4 for Microsoft Windows (32-Bit)



Released: August 2010

This document includes the following sections:

• •Section 1, "Getting Started"
• •Section 2, "Patch Information"
• •Section 3, "Patch Installation Procedures for Oracle Database Release 10.2.0.4"
• •Section 4, "Known Issues"
• •Section 5, "Documentation Accessibility"

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: www.oracle.com/technology/documentation/ocm.html

1.1 System Requirements
The following are the system requirements for this bundle patch:

• •Hardware requirement: Intel Pentium or AMD 32 bit processors
• •Operating system requirement:
• ◦Windows Server 2003 Service Pack 2 or later
• ◦Windows Server 2003 R2
• ◦Windows 2000 (Service Pack 2 or later)
• ◦Windows XP Professional Service Pack 3 or later
• ◦Windows Vista with Service Pack 1 or later
• ◦Windows Server 2008

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.

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
CPUJul2010


Client-Only Installations
CPUJul2010

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
CPUJul2009

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.

2.1 Bugs Fixed by This Patch
This patch fixes the following bugs.

2.1.1 Bugs Fixed for DB 10.2.0.4 Patch 39: 10008101
10.2.0.4 Patch 39 includes all bugs fixed in 10.2.0.4 patch 1 through 38. It must be applied on top of the 10.2.0.4 base release or on top of any earlier bundle patches 10.2.0.4 Patch 1 to Patch 38

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.4 patch bundles for the Microsoft Windows platforms, which are under fix control, refer to My Oracle Support Note 1097085.1.

6080041 - ORA-7445 [KSLWLSCAN] RAISED DURING SYSTEMSTATE DUMP

5612233 - TYPE COLUMN IN V$ARCHIVE_DEST_STATUS DOESN'T SHOW THE REAL VALUE

9381444 - ORA-600 ON UPDATE OF PARTITIONED TABLE WHICH RESULTS IN MOVING ROW WITH GEOMETRY

6979801 - AWR REPORTS INCORRECT IO STATS FOR TABLESPACES AND DATAFILES DURING RMAN BACKUP

7286159 - IMPDP ENCOUNTER ORA-904 WHEN OBJECTS HAS MULTIBYTE COMMENTS

8803363 - ORA-00600 INTERNAL ERROR CODE, ARGUMENTS [KRBOINIT_WRNG_FTYPE]

8462894 - ORA-1002 OCCURS FROM TIME TO TIME

9243893 - A QUERY IS NOT SORTED EVEN WHEN USING ORDER BY

5323844 - 10GR2 SYNONYM FOR A SYNONYM IN REMOTE DATABASE NOT GETTING IMPORTED USING IMPDP

9628444 - CRS DOESN'T START ALL NODEAPPS AND DATABASES AFTER REBOOT

9792919 - RETRIEVAL OF LARGE ORACLE NUMBERS AS .NET DECIMAL RETURNS INCORRECT VALUES

6530801 - ORA-00600 [KZDUES], [29572] IN CAPTURE PROCESS (PROBLEM IN KNLCFRECTX_INIT)

7447883 - ET11.2OPTIM ORA-600 [19004] ON UPDATE

9232418 - MAKE XVM NODE STACK SIZE CONFIGURABLE

9049725 - QUERY RETURNS INCORRECT RESULT

7145973 - XMLTYPE FUNCTIONS AGAINST A VIEW FAILS WITH ORA-7445 [KGHERRORDMP]

9329652 - IMP UTILITY FAILED WITH 36GB PROJECT LOADED WITH 1 SINGLE BLOB DATA > 32 GB

9659614 - HUGE ORA-8103 TRACE FILES GENERATED AFTER PATCH 7519406 APPLIED

9309735 - XDBURITYPE().GETXML LEAKS PGA/UGA

8284272 - ORA-07445 EXCEPTION ENCOUNTERED CORE DUMP [KXIBPUT()+4] [SIGSEGV]

9109487 - DBMS_SPACE.ISDATAFILEDROPPABLE_NAME THROWS NUMERIC OVERFLOW

8292162 - ORA-03113 END-OF-FILE ON COMMUNICATION CHANNEL EXECUTING UTL_NLA.DSYSV

9539556 - A WRONG VALUE FOR _FIX_CONTROL IN THE INIT.ORA CAN LOSE OTHER VALUES

9715664 - MERGE REQUEST ON TOP OF 10.2.0.4 FOR BUGS 9398469 9620711 9526679 9081686 8499490

9620711 - SDO_JOIN WRONG RESULT AFTER 9398469 RELATIONSHIP TOUCH INSTEAD OF OVERLAPBDYINTE

9526679 - SPATIAL FUNCTIONS ARE NOT PARALLEL ENABLED

8499490 - SDO_GEOM.RELATE(DETERMINE) GIVE TWO DIFFERENT RESULTS DEPENDING ON TOLERANCE

9299894 - SDO_DIFFERENCE RETURNS INVALID RESULTS EVEN THOUGH DATA IS VALID

8692094 - SDO_GEOM.SDO_DIFFERENCE RETURNS INVALID GEOMETRIES

9230988 - SDO_DIFFERENCE RETURNS INVALID DATA ORA-13368

8855352 - SDO_RELATE RUNS SLOW AFTER UPGRADE TO 10.2.0.4

6011024 - SDO_GEOM.RELATE WITH 'DETERMINE' MASK RETURNS UNKNOWN MASK ON 10.2.0.3

8661278 - SDO_RELATE WITH INSIDE MASKS RETURNS GEOMETRIES WITH ON RELATIONSHIP

8554687 - SDO_GEOM.RELATE() RETURNS WRONG RESULT

8787205 - MERGE LABEL REQUEST ON TOP OF `0.1.0.4.0 FOR BUGS 8733029

8758818 - SDO_NN WITH SDO_BATCH_SIZE AND DISTANCE IS STILL SLOW

8773211 - SDO_NN WITH SDO_BATCH_SIZE - REMOVE NEED FOR NO_INDEX HINTS ON PREDICATES

8733029 - MERGE LABEL REQUEST ON TOP OF 10.2.0.4.0 FOR BUG 8718259 WITH MLR BUG 8571690

8718259 - RELATE WITH DETERMINE CAUSES INCORRECT RESULTS

8571690 - MERGE LABEL REQUEST ON TOP OF 10.2.0.4 FOR BUGS 8451038 8518433

8518433 - SDO_UNION AND SDO_MIGRATE GENERATES INVALID GEOMETRIES FOR SOME GEODETIC DATA

8451038 - MERGE LABEL REQUEST ON TOP OF 10.2.0.4 FOR BUGS 7265215 7640951

7640951 - MERGE LABEL REQUEST ON TOP OF 10.2.0.4 FOR BUGS 7553851 7511942

7511942 - SDO_RELATE WITH INSIDE MASK RETURNS GEOMETRY THAT SHOULDN'T

7553851 - MERGE LABEL REQUEST ON TOP OF 10.2.0.4 FOR BUGS 7479985 7003151 7237687 6504890

7434709 - MERGE LABEL REQUEST ON TOP OF 10.2.0.4 FOR BUGS 7237687 6956194

6956194 - SDO_GEOM.RELATE WRONG ANSWER WHEN COMPARING GEODETIC POINT AND POLYGON7003151 SDO_ANYINTERACT MUCH SLOWER IN 10.2.0.4 AND 11.1.0.6 THAN 10.2.0.3

7327515 - SDO_INTERSECTION GENERATES INCORRECT ANSWER

7276032 - SDO_INTERSECTION - 10.2.0.4 RETURNS NULL - 11.1.0.6 CORRECT GEOMETRY

7479985 - MERGE LABEL REQUEST ON TOP OF 10.2.0.4 FOR BUGS 7434709 7327515

6504890 - DEPENDENT BUG FOR SPATIAL QUERY OVERHEAD ON PARTITIONED TABLES

7307918 - SDO_ANYINTERACT - NEED OPTIMIZATION FOR MBR SEARCHES ON PROJECTED DATA

7265215 - SDO_GEOM.RELATE INCORRECT RESULT FOR CONTAINS MASK

9095217 - 2000 ORDINATE LIMIT ON SDO_GEOM.RELATE USING ANYINTERACT WHEN GEOMETRIES EQUAL

8968867 - SDO_GEOM.RELATE WRONG RESULTS

8988101 - SDO_GEOM.SDO_DIFFERENCE GENERATES SPIKES

4752090 - NO CLEAN INTERFACE FOR TTS USING SDO_UTIL.PREPARE_FOR_TTS

7023781 - SDO_GEOM.SDO_BUFFER GIVES 2D OUTPUT FOR 3D INPUT AFTER UPGRADE TO 10.2.0.4.0

9772171 - DB STARTUP HANGING 64 MACHINE 2008 R2 WITH > 32-CORE ENABLE

6123694 - UPGRADE FROM XE USING DBUA IN WIN XP FAILS, DISCONNECTED FROM DATABASE

9577583 - FALSE ORA-942 OR OTHER ERRORS WITH MULTIPLE SCHEMAS HAVING IDENTICAL OBJECTS

5957325 - SQL*LOADER FAILS ASSERT1(CCNT > 0 CCNT <= KDTCOLSP, IN KDBLLDRP()

6412622 - ORA-00600 [KFCGXRDL16]

2.1.2 Bugs Redone in DB 10.2.0.4 Patch 39: 10008101
6445948 - ORA-600 [KDSGRP1] HAPPENING => TABLE AND INDEX ANALYZES FINE

6392076 - CREATE OR REPLACE JAVA CLASS USING BLOB IS NOT SKIPPED ON LOGICAL STANDBY

9544104 - WRONG OUTPUT WHEN ADDING A * TO AN XML COMMENT

2.1.3 Bugs pulled out from the Bundle
Bug 7375077 pulled out in Patch 20.

Bug 7434973 pulled out in Patch 22.

Bugs 6737765 and 6162731 pulled out in Patch 24.

Bug 7357554 pulled out in Patch 39

However, these bugs are listed in the inventory to avoid conflicts with earlier bundles. 3 Patch Installation Procedures for Oracle Database Release 10.2.0.4
This section includes the following sections:

• •Section 3.1, "Components for Patch 10008101 for Oracle Database Release 10.2.0.4"
• •Section 3.2, "OPatch Utility Information"
• •Section 3.3, "Patch Installation Instructions"
• •Section 3.4, "Patch Deinstallation Instructions"

3.1 Components for Patch 10008101 for Oracle Database Release 10.2.0.4
Components patched by this Bundle Patch Update:

•RDBMS

•XDB

•ODBC

•PLSQL

•OLAP

•NETWORK

•Spatial

•Winprod

•NLS Run Time Library

•PCW

•Oracore

•EMDB

•Oracle Text

•OID

•ONS

•Data Guard

3.2 OPatch Utility Information
You must use the OPatch utility release 10.2.0.4.3 or later. You can download it from My Oracle Support with patch 6880880.

Prior to the patch installation, the following checks are performed

•Conflicts with other patches

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

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

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

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

%ORACLE_HOME%/OPatch/opatch lsinventory
3.3 Patch Installation Instructions
This section includes the following topics.

•Section 3.3.1, "Preinstallation Instructions"

•Section 3.3.2, "Patch Installation Instructions for Single Instance"

•Section 3.3.3, "Patch Installation Instructions for RAC"

•Section 3.3.4, "Installation Instructions for Oracle Instant Client"

•Section 3.3.5, "Installation Instructions for ODP.NET 1.x"

•Section 3.3.6, "Installation Instructions ODP.NET 2.x"

•Section 3.3.7, "Post Installation Instructions"

•Section 3.3.8, "Post Installation Instructions for Databases Created or Upgraded after Installation of Bundle Patch 39 in the Oracle Home"

3.3.1 Preinstallation Instructions
Follow these steps:

1.Ensure that your Oracle Database installation is the same release for which you are applying this patch. In other words, only apply the Release 10.2.0.4 Bundle patch to an Oracle Database Release 10.2.0.4.

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

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

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

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

Shutdown all MTS/COM+/.Net applications that access Oracle databases.

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

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

6.Make sure no application are using the driver sqora32.dll

7.NOTE for bug 8292378:

Follow the instructions below for a logical standby database.

On Windows platforms, the _MAX_LUBA_STACK Logical standby parameter may need to be adjusted to a smaller value to reduce virtual memory usage per-process. The default is 8000000. This value should be inversely proportional to the number of apply processes applying large transactions. [For e.g. start with 4million and adjust as needed if continue to run into out-of-memory errors.]

Set SQL apply parameter as follows using SQL*Plus:


SQL> alter database stop logical standby apply;
SQL> exec dbms_logstdby.apply_set('_MAX_LUBA_STACK', 4000000);
Also, note that TEMP segment usage will increase as transactions are being applied. The storage area for the TEMP segment datafile must be large enough to accomodate the growth. The disk space usage is roughly 500 bytes per DML (for e.g. 1g for a 2million row insert).

8.Make sure no applications are using the driver sqora32.dll

9.Pre-install steps for Data Guard bug fix 8227106:

a.Disable Fast-Start Failover if it is enabled.
b.Stop the Data Guard broker observer.
c.Disable the configuration.
d.Stop the broker on all databases by setting the DG_BROKER_START initialization parameter to FALSE.

10.NOTE for bug 6798650

For RAC systems only. After patching a node N, start up the database with parameter "_windowfunc_optimization_settings"=16.
Nevertheless, the patch on node N is not in effect yet. This way the customer's system continues to run without being down at all.
After finishing patches at all nodes, then at each node, alter system set the above parameter to value 0. Then, the patch will be effective in the system.

11.Pre-install steps for bug 8866013

If fast-start failover is enabled, disable it.
You may use the DGMGRL CLI DISABLE FAST_START FAILOVER command to do this.
Shut off the broker (alter system set dg_broker_start=false). Do this on all databases in the Data Guard Configuration.

3.3.2 Patch Installation Instructions for Single Instance
Follow these steps:

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

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

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

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

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

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

3.3.3 Patch Installation Instructions for RAC
This is a Rolling-RAC patch only if the system has Patch 37(9683600) or higher applied. 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

1.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 <instance name>
> srvctl stop instance -d <database name> -i <instance name>
> srvctl stop asm -n <nodename>
> srvctl stop nodeapps -n <nodename>
> crsctl stop crs
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

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

3.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 stop service -d <database name> -s <configured workload management service> -i <instancename>
> srvctl stop instance -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

4.Set the ORACLE_HOME environment variable properly

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

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

7.Stop Oracle Service OraFenceService if not already done, and take a backup of file orafencedrv.sys located under %s_systemDirectory%/drivers.

Stop everything outlined in step 1 with the addition of the following:

net stop orafenceservice
If you are running Windows Server 2008, replace orafencedrv.sys with orafencedrv.sys.2k8 supplied in the patch under 10008101. Note that the filename in %s_systemDirectory%/drivers is required to be orafencedrv.sys.

If you are NOT running Windows Server 2008, replace orafencedrv.sys with orafencedrv.sys supplied in the patch under 10008101. Note that the filename in %s_systemDirectory%/drivers is required to be orafencedrv.sys and reboot the node.

8.Take a backup of file ocfs.sys located under %s_systemDirectory%/drivers.

Ensure all services and resources listed in step 1 to 7 have been stopped before copying the ocfs.sys

If you are running Windows Server 2008, replace ocfs.sys with ocfs.sys.2k8 supplied in the patch under 10008101. Note that the filename in %s_systemDirectory%/drivers is required to be ocfs.sys and reboot the node.

If you are NOT running Windows Server 2008, replace ocfs.sys with ocfs.sys.2k supplied in the patch under 10008101. Note that the filename in %s_systemDirectory%/drivers is required to be ocfs.sys and reboot the node.

When copying OCFS and/or orafencedrv you may need to reboot the server.

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

3.3.4 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.Back up the existing files oraociei10.dll, oraociicus10.dll in the Instant Client installation.

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

3.Replace the oraociicus10.dll file in the Instant Client installation by the file oraociicus10.dll from the 10008101\files\instantclient\light directory.

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

◦OCI

◦OCCI

◦JDBC

◦SQL*Plus

3.3.5 Installation Instructions ODP.NET 1.x
Follow these steps only if you are using ODP.NET:

1.Open a Visual Studio .NET 2002 or 2003 command prompt.

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

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

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

3.3.6 Installation Instructions ODP.NET 2.x
Follow these steps only if you are using ODP.NET:

1.Open a Visual Studio 2005 command prompt.

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

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

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

3.3.7 Post Installation Instructions
After installing the patch, perform the following actions:

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

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

3.3.7.1 Loading Modified .sql Files into the Database
To load modified .sql files into the database, follow these steps:

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

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

3._first_spare_parameter is used by bug 6904068 in this bundle patch.
This parameter is not a simple on/off switch and it can take any numeric value. This fix should really not be used/turned on by customers who don't need it

4._third_spare_parameter is used by bug 7452373 in this bundle patch.
This can be set to 100 in init.ora if there is a regression in "log file sync" after applying the patch.

5._fourth_spare_parameter is used by bug 6661393. DBA may like to set _fourth_spare_parameter in init.ora
For example,


a.1. To propogate CLIENT_INFO to CLIENT_IDENTIFIER :
set "_fourth_spare_parameter"="clientid_overwrite_on"
b.2. To disable this propogation
set "_fourth_spare_parameter"="clientid_overwrite_off"

6.To enable fix for bugs 6660648 and 7359366, by turning on cursor cleanup, set _fifth_spare_parameter=1 in init.ora or run the following to update the spfile

> alter system set "_fifth_spare_parameter"=1 scope=spfile sid='*';
7._sixth_spare_parameter is used by bug 7291739

Please note that the new init.ora parameter "_highthreshold_undoretention" introduced by the base bug (7291739) is called now "_sixth_spare_parameter".
alter system set "_highthreshold_undoretention" = "input_high_threshold_value_for_retention";

8.To enable fix for bug 6768114 please add the following to the init.ora file.

event="10411 trace name context forever, level 1"

or run the following to update the spfile

> alter system set event="10411 trace name context forever, level 1" scope=spfile sid='*';
Please note, the above syntax assumes there are no other events set.

9.To enable fix for bug 9196440 please add the following to the init.ora file.

event="9196440 trace name context forever"

or run the following to update the spfile

> alter system set event="9196440 trace name context forever" scope=spfile sid='*';
Please note, the above syntax assumes there are no other events set.

10.Post install steps for Data Guard bug fix 8227106:

a.Start the broker on all databases by setting the DG_BROKER_START initialization parameter to TRUE.
b.Enable the configuration (can only be done by connecting to the primary database).
c.Restart the Data Guard broker observer if had been stopped during the pre-install steps.
d.Re-enable Fast-Start Failover if it had been disabled during the pre-install steps.
11.Post install steps for ODBC fix 7704827

a.Create DSN for Oracle ODBC Driver on Windows through 'Administrative Tools'-> Data Sources(ODBC)
b.Once DSN is created an entry can be found in registry.
i.Run->regedit (Enter), You can find 'Registry Editor' window opened.
ii.Under My Computer -> HKEY_CURRENT_USER -> Software -> ODBC -> ODBC.INI you can find DSN created through first step.
iii.Click on DSN name. You can find all the options supported by Oracle ODBC driver. Go to Menu -> Edit -> New -> String Value . This gives new entry in odbc.ini file as you can see. Rename that String value to 'UseOCIDescribeAny' and enter its value as T/F depending on your requirement.
12.Post install steps for fix 8292378

Follow the instructions below for a logical standby database

The _MAX_LUBA_STACK Logical standby parameter may need to be adjusted to a smaller value to reduce virtual memory usage per-process. The default is 8000000. This value should be inversely proportional to the number of apply processes applying large transactions. [For e.g. start with 4million and adjust as needed if continue to run into out-of-memory errors.]

Set SQL apply parameter as follows using SQL*Plus:

SQL> alter database stop logical standby apply;
SQL> exec dbms_logstdby.apply_set('_MAX_LUBA_STACK', 4000000);
Also, note that TEMP segment usage will increase as transactions are being applied. The storage area for the TEMP segment datafile must be large enough to accomodate the growth. The disk space usage is roughly 500 bytes per DML (for e.g. 1g for a 2million row insert).

13.Post install steps for OO4O fix 7763473

Go to %ORACLE_HOME%\bin and run->regsvr32 oip10.dll to register the latest oip10.dll

14.Post install steps for fix 7033630

On a RAC, users should ensure that neither streams nor SQL Apply is running on any instance at the this time.

15.Post-install steps for bug 8866013

Restart the broker (alter system set dg_broker_start=false). Do this on all databases in the Data Guard Configuration.
If fast-start failover had been disabled to apply this patch, re-enable it.
You may use the DGMGRL CLI ENABLE FAST_START FAILOVER command to do this.

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

17.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\Patch38
> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catcpu.sql
SQL> QUIT
18.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
19.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.

20.In a Data Vault installation, please run the following

Revoke DV_PATCH_ADMIN from SYS:
SQL> CONNECT
SQL> REVOKE DV_PATCH_ADMIN FROM SYS; 21.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".

22.The expected patch level in registry$history for this bundle is Patch 39.

23.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';
24.Exit from SQL*Plus.

SQL> QUIT
25.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.7.2 Recompiling Views in the Database
You must recompile views for all databases except the following:

•Databases created with Release 11.1.0.6 or later

•Databases created with any release (for example, 10.2.0.3, 10.1.0.5, or 9.2.0.after CPUJan2008 or a later Bundle has been applied

•Databases for which views were recompiled during the installation of a previous Bundle Patch

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 Patch 39 in the Oracle Home
These instructions are for both non-RAC environments and RAC environments when a database is created or upgraded after the installation of Bundle Patch 39.

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:

1.Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing)
2.Using a script that was created by DBCA that creates a database from a sample database
3.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 Patch 39 was applied
Upgraded databases require that you perform the steps in 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 10.2.0.4
This section includes the following topics.

•Section 3.4.1, "Patch Deinstallation Instructions for Single Instance"

•Section 3.4.2, "Patch Deinstallation Instructions for RAC"

•Section 3.4.3, "Deinstallation Instructions Oracle Instant Client"

•Section 3.4.4, "Deinstallation Instructions for ODP.NET 1.x"

•Section 3.4.5, "Deinstallation Instructions for ODP.NET 2.x"

•Section 3.4.6, "Post Deinstallation Instructions"

3.4.1 Patch Deinstallation Instructions for single Instance
Follow these steps:

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

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

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

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

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

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

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

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

3.4.2 Patch Deinstallation Instructions for RAC
Stop all Oracle services in all the homes on all the nodes


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 de-installing a patch in RAC install is RDBMS_HOME, ASM_HOME and CRS_HOME

1.All services and all processes running from the ORACLE_HOME needs to be stopped

2.Set the ORACLE_HOME environment variable properly

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

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

> opatch rollback -id 10008101
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.

5.Stop Oracle Service OraFenceService, and replace the file orafencedrv.sys located under %s_systemDirectory%/drivers with the file backed up during patch apply.

6.Replace the file ocfs.sys located under %s_systemDirectory%/drivers with the file backed up during patch apply. If you rebooted the system after patch apply, another reboot will be required after restore of original file for the old OCFS driver to take effect.

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

3.4.3 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.5, "Installation Instructions for Oracle Instant Client", you can roll back this patch by re-copying the oraociei10.DLL, oraociicus10.dll file to the installation.

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

3.4.4 Deinstallation Instructions for ODP.NET 1.x
Follow these steps only if you are using ODP.NET:

1.Open a Visual Studio .NET 2002 or 2003 command prompt.

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

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

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

3.4.5 Deinstallation Instructions for ODP.NET 2.x
Follow these steps only if you are using ODP.NET:

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 /u Oracle.DataAccess.dll
If you do not have gacutil.exe, you can drag-and-drop the Oracle.DataAccess.dll to %SystemRoot%\assembly using Windows File Explorer.

3.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._fourth_spare_parameter is used by bug 6661393. DBA may like to set _fourth_spare_parameter in init.ora
For example,


a.1. To propogate CLIENT_INFO to CLIENT_IDENTIFIER :
set "_fourth_spare_parameter"="clientid_overwrite_on"
b.2. To disable this propogation
set "_fourth_spare_parameter"="clientid_overwrite_off"

4.As bug 6660648 and bug 7359366 are being deinstalled, turn off _fifth_spare_parameter by removing _fifth_spare_parameter=1 in init.ora or by running the following command to update the spfile

> alter system reset "_fifth_spare_parameter" scope=spfile sid='*';
5.As bug 6768114 is being deinstalled, turn off the event for 10411 by removing the following in the init.ora file.

event="10411 trace name context forever, level 1"

or by running the following to update the spfile

> alter system reset event scope=spfile sid='*';
Please note, the above syntax assumes only this event has been set.

6.Post de-install steps for OO4O fix 7763473

Go to %ORACLE_HOME%\bin and run->regsvr32 oip10.dll to register the older oip10.dll

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

8.Rollback of this patch is not rollable for RAC

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

> cd %ORACLE_HOME%\RDBMS\ADMIN
> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle_WINBUNDLE_<database SID>_ROLLBACK.sql
SQL> QUIT
9.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
10.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.

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

12.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';
13.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.

•To disable Database Vault, see Section 3.5.1.

•To enable Database Vault, see Section 3.5.2.

3.5.1 Disabling Database Vault
To disable Database Vault, follow these steps.

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

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

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

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

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

6.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\Patch38
> 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;
3.5.2 Enabling Database Vault
To enable Database Vault, follow these steps:

1.Lock the DVSYS account:

> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> ALTER USER DVSYS IDENTIFIED BY password;
SQL> ALTER USER DVSYS ACCOUNT LOCK;
Enable the Database Vault triggers as DV owner:

SQL> CONNECT <DV_Owner>/<DV_Owner_password>
SQL> ALTER TRIGGER DVSYS.DV_BEFORE_DDL_TRG ENABLE;
SQL> ALTER TRIGGER DVSYS.DV_AFTER_DDL_TRG ENABLE;
Shutdown the database:

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

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

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

4 Known Issues
This section includes the following information:

•Section 4.1, "Issues Common to All Releases"

•Section 4.2, "Issues Specific to Oracle Database Release 10.2.0.4"

•Section 4.3, "Issues Specific to OPatch"

4.1 Issues Common to All Releases
This section includes issues common to all Oracle Database releases:

•Section 4.1.1, "Generic Issues"

•Section 4.1.2, "Platform-specific Issues"

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-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-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
SP2-0310: unable to open file rdbms/admin/catamgt.sql
SP2-0310: unable to open file rdbms/admin/dbmsamgt.sql
SP2-0310: unable to open file rdbms/admin/prvtamgt.plb
SP2-0310: unable to open file md/admin/sdopopt.plb
The following ignorable error may be encountered while running catcpu_rollback.sql

ORA-20003: Specified bug number (5099019) does not exist
•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: 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.)

•Issue 6: 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.

•Issue 7: KU$_XXXX objects become invalid after running catcpu.sql in Patch22

Problem is witnessed if the oracle home being patched does not have the XML/XDK/XDB Database component installed in the database.
As a workaround , following scripts can be run as SYSDBA

@?\rdbms\admin\catalog.sql
@?\rdbms\admin\catproc.sql
@?\rdbms\admin\utlrp.sql


4.1.2 Platform-specific Issues
There are no known platform-specific issues.

4.2 Issues Specific to Oracle Database Release 10.2.0.4
There are no known issues specific to 10.2.0.4 release.

4.3 Issues Specific to OPatch
There are no known issues specific to OPatch.

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

---

Copyright © 2006, 2009, Oracle. All rights reserved.