setting up env in windows

set oracle_sid=orcl
set oracle_home=d:\app\1product\11.1.0\db_1


does not work

this is windows 2003
the patch is inder home directory and also the Opatch is under home directory

getting orror 73
help be greatly appreciated

you need to show the whole error message

Ok the

opatch failed with error code = 73

I nned the command you have issued and the patch number you are using

try this

set oracle_sid=orcl
set oracle_home=d:\app\1product\11.1.0\db_1
set OPATCH_PLATFORM_ID=207

if it did not work try

set oracle_sid=orcl
set oracle_home=d:\app\1product\11.1.0\db_1
set OPATCH_PLATFORM_ID=215

nop

it is not reading the patch which is under home dir and if opatch is not in the directory path it does not run
and when it is in the directory path it runs but give error   opatch failed with error 73
Opatch need to see the patch which is in the same  oracle Home directory.
how do make opatch to see and apply patch.

some ting is not right as windows is way different than the Great Unix.

please show the whole thing

the command you issue with the error stack

everything I do is failing.
I simply want to apply a patch to oracle 11.1.0.6 and in windows.
need just steps to apply patch
how to setup env in windows so that the patch could run

gettng all sorts of info and path settings

I am getting  opatch error code 74

Taaz please just copy and paste what you got as from the DOS session;
it is not that hard.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>d:

D:\>cd d:\app\administrator\product\11.1.0\db_1

D:\app\Administrator\product\11.1.0\db_1>cd Opatch

D:\app\Administrator\product\11.1.0\db_1\OPatch>opatch lsinventory
Oracle Home is not set. OPatch cannot proceed!

OPatch failed with error code = 1

D:\app\Administrator\product\11.1.0\db_1\OPatch>set oracle_home=d:\app\administr
ator\product\11.1.0\db_1

D:\app\Administrator\product\11.1.0\db_1\OPatch>opatch lsinventory
File Not Found
Invoking OPatch 11.1.0.6.0

Oracle Interim Patch Installer version 11.1.0.6.0
Copyright (c) 2007, Oracle Corporation.  All rights reserved.


Oracle Home       : d:\app\administrator\product\11.1.0\db_1
Central Inventory : C:\Program Files\Oracle\Inventory
   from           : n/a
OPatch version    : 11.1.0.6.0
OUI version       : 11.1.0.6.0
OUI location      : d:\app\administrator\product\11.1.0\db_1\oui
Log file location : d:\app\administrator\product\11.1.0\db_1\cfgtoollogs\opatch\
opatch2009-08-25_11-52-00AM.log

Lsinventory Output file location : d:\app\administrator\product\11.1.0\db_1\cfgt
oollogs\opatch\lsinv\lsinventory2009-08-25_11-52-00AM.txt

--------------------------------------------------------------------------------

Installed Top-level Products (1):

Oracle Database 11g                                                  11.1.0.6.0
There are 1 products installed in this Oracle Home.


There are no Interim patches installed in this Oracle Home.

--------------------------------------------------------------------------------


OPatch succeeded.

D:\app\Administrator\product\11.1.0\db_1\OPatch>opatch apply d:\app\administrato
r\product\11.1.0\db_1
File Not Found
Invoking OPatch 11.1.0.6.0

Oracle Interim Patch Installer version 11.1.0.6.0
Copyright (c) 2007, Oracle Corporation.  All rights reserved.


Oracle Home       : d:\app\administrator\product\11.1.0\db_1
Central Inventory : C:\Program Files\Oracle\Inventory
   from           : n/a
OPatch version    : 11.1.0.6.0
OUI version       : 11.1.0.6.0
OUI location      : d:\app\administrator\product\11.1.0\db_1\oui
Log file location : d:\app\administrator\product\11.1.0\db_1\cfgtoollogs\opatch\
opatch2009-08-25_11-53-31AM.log

Failed to load the patch object.  Possible causes are:
  The specified path is not an interim Patch shiphome
  Meta-data files are missing from the patch area
  Patch location = d:\app\administrator\product\11.1.0\db_1
  Details = PatchObject constructor: Input file "d:\app\administrator\product\11
.1.0\db_1\etc\config\actions" or "d:\app\administrator\product\11.1.0\db_1\etc\c
onfig\inventory" does not exist.

ApplySession failed: PatchObject constructor: Input file "d:\app\administrator\p
roduct\11.1.0\db_1\etc\config\actions" or "d:\app\administrator\product\11.1.0\d
b_1\etc\config\inventory" does not exist.
System intact, OPatch will not attempt to restore the system

OPatch failed with error code = 73

D:\app\Administrator\product\11.1.0\db_1\OPatch>

opatch apply [patch location]
you have used you oracle_home destination

the patch is in

d:\app\administrator\product\11.1.0\db_1\8563154

I think that you need to be inside this folder d:\app\administrator\product\11.1.0\db_1\8563154
cd to it

If I
cd d:\app\administrator\product\11.1.0\db_1\8563154
then Opatch apply does not run at all
the only way opatch runs is only if it is in the
d:\app\administrator\product\11.1.0\db_1\Opatch
that is why I used    Opatch apply d:\app\administrator\product\11.1.0\db_1\8563154

I don't know.  Did anyone ever applied patch like this?

would please upload the html readme in your patch

Oracle® Database Server Version 11.1.0.6 Patch17Bundle Patch Update Note

Release 11.1.0.6 for Microsoft Windows (32-Bit)

 

Released: June, 2009

This document includes the following sections:

Section 1, "Getting Started"

Section 2, "Patch Information"

Section 3, "Patch Installation Procedures for Oracle Database Release 11.1.0.6"

Section 4, "Known Issues"

Section 5, "References"

Section 6, "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: http://www.oracle.com/technology/documentation/ocm.html

2 Patch Information
Bundle patches are cumulative, which means fixes from previous bundle patches are included. It is not required to have any previous bundle patch applied to apply this one. You must however be on the stated patch set level for a given product home before applying any bundle patch for that release

The bundle patches include Oracle Critical Patch Update (CPU) content. To determine which release of CPU is included, refer to the Critical Patch Updates and Security Alerts on OTN. Select the link to the latest Critical Patch Update and in the Advisory select the Database link. The bundle information is found in the Patch Availablity tables.

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 in DB 11.1.0.6 Patch17: 8563154
DB 11.1.0.6 Patch17 includes all bugs fixed in the 11.1.0.6 patch1 to Patch16. It must be applied on top of the 11.1.0.6 base release or on top of any earlier bundle patches 11.1.0.6 Patch 1 to Patch16.

7443915 - OCI-21710 PASSING UDT MULTIPLE TIMES WITH ODP AND PROXY AUTHETICATION

7447345 - COMMANDBUILDER UDATE FAILS WHEN ALTER SESSION SET CURRENT_SCHEMA

7611939 - EMBEDDED PL/SQL GATEWAY DAD ATTRIBUTE MAX-PARAMETERS ALWAYS USES DEFAULT

6616345 - ENHANCEMENT REQUEST EXPOSURE OF METADATA POOLING REGISTRY KEY

2.1.2 Bugs re-done in DB 11.1.0.6 Patch17: 8563154
7350234 - THE XML QUERY IGNORE INDEX ON ELEMENT WHEN USING INHERITANCE IN DEFINITION

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

3 Patch Installation Procedures for Oracle Database Release 11.1.0.6
This section includes the following sections:

Section 3.1, "Components for Patch 8563154 for Oracle Database Release 11.1.0.6"

Section 3.2, "OPatch Utility Information"

Section 3.3, "Patch Installation Instructions for Oracle Database Release 11.1.0.6"

Section 3.4, "Patch Deinstallation Instructions for Oracle Database Release 11.1.0.6"

3.1 Components for Patch 8563154 for Oracle Database Release 11.1.0.6
Components patched by this Patch Update:

Oracle Database

Database SQL Scripts

Oracle Multimedia Locator

Oracle Core

Oracle OLAP

PL/SQL

Oracle Notification Service

Enterprise Manager Database Plugin -- Management Service Support

Oracle Database Gateway for ODBC

Oracle ODBC Driver for Instant Client

Oracle Data Provider for .NET 1.x

Oracle Data Provider for .NET 2.0

Oracle XML Development Kit

Oracle Net Required Support Files

Oracle Net

Oracle RAC Required Support Files-HAS

Oracle Provider for OLE DB

Precompiler Required Support Files

Precompiler Common Files

3.2 OPatch Utility Information
You must use the OPatch utility release 11.1.0.6.3 or later. You can download it from OracleMetaLink with patch 6880880.

For information about OPatch documentation, including any known issues, see OracleMetaLink Note 293369.1 OPatch documentation list.

3.3 Patch Installation Instructions for Oracle Database Release 11.1.0.6
This section includes the following topics.

Section 3.3.1, "Preinstallation Instructions"

Section 3.3.2, "Preinstallation Instructions for ODP.NET Only"

Section 3.3.3, "Patch Installation Instructions for SINGLE INSTANCE DATABASE"

Section 3.3.4, "Patch Installation Instructions for RAC"

Section 3.3.5, "Patch Installation Instruction for Oracle Instant Client"

Section 3.3.6, "Patch Installation Instruction for Patching Instant Client Based ODP.NET 11.1.0.6.20"

Section 3.3.7, "ODP.NET 1.x Installation Instructions"

Section 3.3.8, "ODP.NET 2.x Installation Instructions"

Section 3.3.9, "Post Installation Instructions"

Section 3.3.10, "Post Installation Instructions for Databases Created or Upgraded after Installation of Bundle Patch17 in the Oracle Home"

3.3.1 Preinstallation Instructions
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.1.0.6 patch 13 to an Oracle Database Release 11.1.0.6.

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.

3.3.2 Preinstallation Instructions for ODP.NET 1.x and 2.x Only (OPTIONAL)
This patch bundle includes a fix for Oracle Data Provider for .NET, a driver used in client .NET applications, and with the Oracle Database Extensions for .NET.

If you are not using ODE.NET or ODP.NET application, or do not need the fix for Oracle Data Provider for .NET bug(s) included in this patchset, then you can skip remainder of this section and sections 3.3.7 and 3.3.8.

Follow these steps:

Install 11.1.0.6.20 ODAC Patch (patch number 7121732)
This is a prerequisite step for proper policy files and registry settings to take effect.

If you are using the 1.x assemblies open a Visual Studio .NET 2002 or 2003 command prompt.
If you are using the 2.x assemblies open a Visual Studio 2005 command prompt.

Navigate to the %ORACLE_HOME%\ODP.NET\bin\1.x or %ORACLE_HOME%\ODP.NET\bin\2.x directory, as appropriate.

Execute the following to uninstall your existing version of the ODP.NET assembly:

 gacutil /u Oracle.DataAccess

If you do not have gacutil.exe, you can navigate to %SystemRoot%\assembly using Windows File Explorer, right-click on each .NET 1.x or .NET 2.x version of Oracle.DataAccess, and click Uninstall.

3.3.3 Patch Installation Instructions for SINGLE INSTANCE DATABASE
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>

Ensure that the directory where you downloaded the patch is on the same drive as the Oracle home to be patched.

Go to the directory where you downloaded the patch:

> cd 8563154

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

3.3.4 Patch Installation Instructions for RAC
This patch is RAC rolling upgradeable only if the 11.1.0.6 Bundle Patch9 (patch 7318821) or a later bundle patch is installed on each cluster node in the RAC environment.
The requirement is for all RDMS and ASM homes.


3.3.4.1 Patch Installation Instructions for Rolling RAC Install
Follow these steps:


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

The order of patching in RAC install is CRS_HOME, ASM_HOME and RDBMS_HOME

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

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

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

net stop OracleService<SID>

net stop Oracle<homename>TNSListenerLISTENER_<nodename>

net stop OracleDBConsole<SID>

net stop OracleASMService<ASMSID>

net stop Oracle<SID>VSSWriterService

net stop OracleREMExecService

net stop OracleCRService

net stop OracleEVMService

net stop OracleCSService

net stop OracleObjectService

net stop OracleClusterVolumeService

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 stop service -d <database name> -s <configured workload management service> -i <instancename>
> srvctl stop instance -d <dbname> -i <instance name>
> srvctl stop asm -n <nodename>
> srvctl stop listener -n <nodename>

net stop OracleService<SID>

net stop Oracle<homename>TNSListenerLISTENER_<nodename>

net stop OracleDBConsole<SID>

net stop OracleASMService<ASMSID>

net stop Oracle<SID>VSSWriterService

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

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>

net stop OracleService<SID>

net stop Oracle<SID>VSSWriterService

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

Set the ORACLE_HOME environment variable properly

Go to the directory where you downloaded the patch:

> cd 8563154

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.

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

3.3.4.2 Patch Installation Instructions when Rolling RAC is not Feasible
Follow these steps:

Stop all Oracle Database Release 11g RAC instances and the nodeapps application on all nodes:

> srvctl stop database -d <DB_NAME>
> srvctl stop asm -n <nodename1>
> srvctl stop asm -n <nodename2>
> srvctl stop nodeapps -n <nodename1>
> srvctl stop nodeapps -n <nodename2>

Stop the following services:

OracleCRService

OracleCSService

OracleEVMService

OracleObjectService

OracleClusterVolumeService

Set the ORACLE_HOME environment variable appropriately.

> set ORACLE_HOME=<Oracle home path>

Go to the directory where you downloaded the patch:

> cd 8563154

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

> opatch apply

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

3.3.5 Patch Installation Instructions for Oracle Instant Client
For OUI based Client-Admin installations, the 'opatch apply' takes care of updating your installation with these latest Instant Client binaries.

For Other types of Instant Client installations, Follow these steps:

Back up the existing file oci.dll, oraociei11.dll and sqora32.dll in the Instant Client installation.

Replace the oraociei11.dll file in the Instant Client installation by the file oraociei11.dll from the 8563154\files\instantclient directory.

Replace the oci.dll and sqora32.dllfile in the Instant Client installation by the file oci.dll and sqora32.dll from the 8563154\files\bin directory.

3.3.6 Patch Installation Instruction for Patching Instant Client Based ODP.NET 11.1.0.6.20
If ODP.NET 11.1.0.6.20 was installed into an Oracle Home with regular Oracle Client, this step is not necessary. However, to patch an instant client based ODP.NET 11.1.0.6.20, follow these steps to appropriately patch ODP.NET.
Steps:

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

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

Back up and replace the existing bin\OraOps11.dll with 8563154\files\bin\OraOps11.dll

Back up and replace the existing bin\OraOps11w.dll with 8563154\files\bin\OraOps11w.dll

3.3.7 ODP.NET 1.x Installation Instructions
Follow these steps:

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

Navigate to the %ORACLE_HOME%\ODP.NET\bin\1.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. The same applies to policy DLL.

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

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

3.3.8 ODP.NET 2.x Installation Instructions
Follow these steps:

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

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

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

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

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

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

3.3.9.1 Loading Modified .sql Files into the Database
For a new or upgraded database, check Section 3.3.10, "Post Installation Instructions for Databases Created or Upgraded after Installation of Bundle Patch17 in the Oracle Home" to see whether you need to perform the steps in this section.

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\Patch17
> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @?/rdbms/admin/catplan.sql (required only for an upgraded db from 10.*)
SQL> @catcpu.sql
SQL> @?/rdbms/admin/prvths.plb (required only if DG4ODBC (hsodbc) is installed)
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.

Inspect the logfile %ORACLE_HOME%\cfgtoollogs\catbundle\catbundle_WINBUNDLE_<ORACLE_SID>_APPLY_<timestamp>.log for any errors.

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

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';



Exit from SQL*Plus.

SQL> QUIT

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

3.3.9.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.8) after CPUJan2008 or a later CPU has been applied

Databases for which you recompiled views during the installation of a previous patch

For new databases, see Section 3.3.10, "Post Installation Instructions for Databases Created or Upgraded after Installation of Bundle Patch17 in the Oracle Home"

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_bundlePatch17.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 patch installation. If you do this, your system will continue to work; however, the patch 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 in the database, follow these steps:

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.

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_bundlePatch17.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 patchinstall, or scheduled later.

If the database is not in a RAC environment, perform this step. (If the database is in a RAC environment, go to the next step.)

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> STARTUP UPGRADE
SQL> @view_recompile_bundlePatch17.sql
SQL> SHUTDOWN;
SQL> STARTUP;
SQL> QUIT

If the database is in a RAC environment, run the view recompilation script as follows. 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> STARTUP NOMOUNT
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
SQL> SHUTDOWN
SQL> STARTUP UPGRADE
SQL> @view_recompile_bundlePatch17.sql
SQL> SHUTDOWN;
SQL> STARTUP NOMOUNT;

Set the CLUSTER_DATABASE initialization parameter to TRUE:

SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;

Restart the database:

SQL> SHUTDOWN;
SQL> STARTUP;
SQL> QUIT

Check the log file for any errors. The log file is in the current directory and is named: vcomp_<sid>_<timestamp>.log

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 package schemaname.packagename compile;

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.

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.10 Post Installation Instructions for Databases Created or Upgraded after Installation of Bundle Patch17 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 CPUJan2009.

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

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

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

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

Upgraded databases require that you perform the steps in Section 3.3.9.1, "Loading Modified .sql Files into the Database"" and Section 3.3.9.2, "Recompiling Views in the Database" if these steps have not previously been performed; otherwise, no post-installation steps need to be performed.
3.4 Patch Deinstallation Instructions for Oracle Database Release 11.1.0.6
This section includes the following topics.

Section 3.4.1, "Pre-Deinstallation Instructions for ODP.NET 1.x and 2.x Only"

Section 3.4.2, "Deinstallation Instructions"

Section 3.4.3, "Patch Deinstallation Instructions for RAC"

Section 3.4.4, "Patch Deinstallation Instructions Oracle Instant Client"

Section 3.4.5, "Patch Deinstallation Instruction for Instant Client Based ODP.NET 11.1.0.6.20"

Section 3.4.6, "ODP.NET 1.x Deinstallation Instructions"

Section 3.4.7, "ODP.NET 2.x Deinstallation Instructions"

Section 3.4.8, "Post Deinstallation Instructions"

3.4.1 Pre-Deinstallation Instructions for ODP.NET 1.x and 2.x Only
Follow these steps:

If you are using the 1.x assemblies open a Visual Studio .NET 2002 or 2003 command prompt.
If you are using the 2.x assemblies open a Visual Studio 2005 command prompt.

Navigate to the %ORACLE_HOME%\ODP.NET\bin\1.x or %ORACLE_HOME%\ODP.NET\bin\2.x directory, as appropriate.

Execute the following to uninstall your existing version of the ODP.NET assembly:

 gacutil /u Oracle.DataAccess

If you do not have gacutil.exe, you can navigate to %SystemRoot%\assembly using Windows File Explorer, right-click on each .NET 1.x or .NET 2.x version of Oracle.DataAccess, and click Uninstall.

3.4.2 Deinstallation Instructions
Follow these steps:

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 8563154

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

> opatch rollback -id 8563154

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

3.4.3 Patch Deinstallation Instructions for RAC
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, ASM and CRS

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

Before uninstalling the patch in ASM, 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 uninstalling the patch in CRS, all services on the current node needs to be stopped

Set the ORACLE_HOME environment variable properly

Go to the directory where you downloaded the patch:

> cd 8563154

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

> opatch rollback -id 8563154

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.

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

3.4.4 Patch Deinstallation instructions for Oracle Instant Client
Follow these steps:

If you patched the Oracle Instant Client installation by following the steps in Section 3.3.5, "Patch Installation Instructions for Oracle Instant Client", you can roll back this patch by re-copying the oci.DLL, oraociei11.dll and sqora32.DLL file to the installation.

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

3.4.5 Patch Deinstallation Instruction for Instant Client Based ODP.NET 11.1.0.6.20
Follow these steps:

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

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

Replace the existing bin\OraOps11.dll from backup location

Replace the existing bin\OraOps11w.dll from backup location

3.4.6 ODP.NET 1.x Deinstallation Instructions
Follow these steps:

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

Navigate to the %ORACLE_HOME%\ODP.NET\bin\1.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. The same applies to policy DLL.

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

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

3.4.7 ODP.NET 2.x Deinstallation Instructions
Follow these steps:

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

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

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

3.4.8 Post Deinstallation Instructions
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\Patch17
> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @?/rdbms/admin/catplan.sql (required only for an upgraded db from 10.*)
SQL> @catcpu_rollback.sql
SQL> @?/rdbms/admin/catplan.sql (required only if DG4ODBC (hsodbc) is installed)
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 %ORACLE_HOME%\cfgtoollogs\catbundle\catbundle_WINBUNDLE_<ORACLE_SID>_ROLLBACK_<timestamp>.log for any errors.

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

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.

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

Under ORACLE_HOME\bin, rename the oradv11.dll file, for example, oradv11_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\Patch17
> 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 DV_BEFORE_DDL_TRG DISABLE;
SQL> ALTER TRIGGER DV_AFTER_DDL_TRG DISABLE;

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

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

4 Known Issues
This section includes the following information:

Section 4.1, "Issues Common to All Releases"

Section 4.2, "Issues Specific to Oracle Database Release 11.1.0.6"

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-01951: ROLE 'CONNECT' not granted to 'WKSYS'
ORA-01952: system privileges not granted to 'WKSYS'
ORA-02303: cannot drop or replace a type with type or table dependents
ORA-02443: Cannot drop constraint - nonexistent constraint
ORA-04043: object <object-name> does not exist
ORA-29832: cannot drop or replace an indextype with dependent indexes
ORA-29844: duplicate operator name specified
ORA-14452: attempt to create, alter or drop an index on temporary table already in use
ORA-14452: attempt to create, alter or drop an index on temporary table already in use
ORA-06512: at line <line number>. If this error follow any of above errors, then can be safely ignored.
ORA-02289: sequence does not exist
ORA-20002: Unable to create table IMPDP_STATS: already exists
SP2-0310: unable to open file rdbms/admin/prvtmacp.plb
SP2-0310: unable to open file rdbms/admin/catmact.sql
SP2-0310: unable to open file rdbms/admin/catmacc.sql

Issue 2: While running opatch apply, you may see the following prompt, enter N to continue:

OPatch encounters the following issues during file back-up:
The following problems were encountered when trying to backup Java class
 files: /nfs/bld/d4/apps/11510/AB4/apps/cpu1db/9.2.0/rdbms/jlib/CDC.jar
[ object: Subscription.class ]
Do you want to continue?
Please respond Y|N >
The problem here is that OPatch could not find jdk in the default
location.
Rerun 'opatch apply -jdk <local jdk location>' and provide the location
of the jdk.  

Issue 3: If the NLS_LANG environment variable is set to Japanese_Japan.JA16EUC or Japanese_Japan.JA16SJIS, while executing catcpu.sql (and catcpu_rollback.sql), the following errors may occur:

SP2-0768: Illegal SPOOL commandSP2-0768: Illegal SPOOL command
Usage: SPOOL { <file> | OFF | OUT }
where <file> is file_name[.ext] [CRE[ATE]|REP[LACE]|APP[END]]

Workaround:

Before running the catcpu.sql or catcpu_rollback.sql scripts, run the following SQL statement to change the nls_language setting:

SQL>ALTER SESSION SET nls_language='American';

Issue 4: If you are applying the patch using a Terminal Services or Remote Desktop Connection and experiencing problems, attempt to apply the patch locally at the console of the machine against which the patch is being applied before filing a Service request with Oracle Global Product Support.

Issue 5: This patch update may reload a few packages (for example, the utl_file package). This reinstates all of its default grants, regardless of any revocations made by the end-user.

Workaround: Revoke all grants made by end user for such packages. (ref: OracleMetaLink Note 131752.1.)

Issue 6: The following warning may be displayed when using the Opatch utility to apply a CPU. You can ignore this warning. Respond Y when you are prompted to proceed.

WARNING:OUI-67124:
Copy Action: Desctination File "<ORACLE_HOME>/lib/libnjssl10.sl" is not
writeable.
@ 'oracle.rsf.net_rsf, 10.1.0.4.0': Cannot copy file from 'libnjssl10.sl' to
'<ORACLE_HOME>/lib/libnjssl10.sl'

Issue 7: 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 8: If the view recompilation script has already been run, a message is displayed indicating that the script has already been applied.

This is not a problem, because as the instructions note, you do not need to run the script if it has already been run.

Issue 9: If patch was deinstalled after view recompilation was run, then the query select * from registry$history where id = '6452863' will not return a row. You do not need to rerun the view recompilation if you are certain it has already been run on the database. (This problem does not occur with CPUApr2008.)

4.1.2 Platform-specific Issues
The following is a platform-specific issue for Windows:

Issue 1: If the patch is being applied from a different drive than the drive on which %ORACLE_HOME% is located, an OPATCH_JAVA_ERROR is generated, in a format similar to the following: Jar failed: "d:\ias\BC4J\redist\bc4j.ear.d\webapp.war" doesn't exist

Workaround: Copy the patch to the same drive as %ORACLE_HOME% and perform the installation.

4.2 Issues Specific to Oracle Database Release 11.1.0.6
This section includes issues specific to Oracle Database Release 11.1.0.6:

Section 4.2.1, "Generic Issues"

Section 4.2.2, "Platform-specific Issues"

4.2.1 Generic Issues
There are no generic issues for Oracle Database Release 11.1.0.6.

4.2.2 Platform-specific Issues
There are no platform-specific issues for Oracle Database Release 11.1.0.6.

4.3 Issues Specific to OPatch
For information about OPatch issues, see OracleMetaLink Note 293369.1 OPatch documentation list.

5 References
5.1 Generic Issues and Notes:
The following documents are generic references for this patch set.

Note 293369.1 OPatch documentation list

Note 360870.1 Impact of Java Security Vulnerabilities on Oracle Products

Note 258285.1 Sending Parameters as a GET or POST When Using mod_plsql

Note 237898.1 Caution When Using ProxyRequests With ProxyPass

Note 330242.1 When Using OPatch to Update Oracle home: Missing_component: Oracle.Apache.Apache

Note 337288.1 OPatch Fails to Detect Operating System Appropriately

Note 274710.1 Cannot Load Modplsql.so Into Server Because of Symbol Errors

6 Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, 7 days a week. For TTY support, call 800.446.2398. Outside the United States, call +1.407.458.2479.


--------------------------------------------------------------------------------

Oracle Database Patch Update Note Release 11.1.0.6 for Microsoft Windows (32-Bit)

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


--------------------------------------------------------------------------------

Attached is the redme