Oracle9i Patch Set

Oracle9i Patch Set Notes 
Release 2 (9.2.0.8) Patch Set 7 for Microsoft Windows (32-Bit)

---

 

Oracle9i

Patch Set Notes

Release 2 (9.2.0.8) Patch Set 7 for Microsoft Windows (32-Bit)

August 2006

These patch set notes accompany the Oracle9i release 2 (9.2.0.8) patch set. 

This document contains the following sections:

• Patch Set Overview

• Oracle Universal Installer Version Requirements

• Patch Set Documentation

• System Requirements

• Preinstallation Tasks

• Installation Tasks

• Postinstallation Tasks

• Removing the Patch Set Software

• Reinstalling the Patch Set Software

• Known Issues

• Fixed Platform-Specific Bugs for Windows (32-Bit)

• Patch Set Components

• Documentation Accessibility

1 Patch Set Overview

Patch sets are a mechanism for delivering fully tested and integrated product fixes. Patch sets provide bug fixes only; they do not include new functionality and they do not require certification on the target system.

Patch sets include all of the libraries that have been rebuilt to implement the bug fixes in the set. All of the fixes in the patch set have been tested and are certified to work with each other. Because patch sets include only low impact fixes, you are not required to certify applications or tools against the server unless directed to by the operating system vendor.

Patch sets are cumulative. Patch set release 9.2.0.8 includes all fixes in patch sets 9.2.0.8 and earlier as well as new fixes for patch set 9.2.0.8. This means that unless the patch set documentation indicates otherwise, you can apply this patch set to any earlier release 9.2 installation. You do not have to install intermediate patch sets.

Patch sets contain generic fixes that apply to all platforms. Patch sets may also include additional platform-specific patches.

Note:

Oracle provides both 32-bit and 64-bit versions of Oracle9i for Windows. Currently, the 32-bit version of the patch set must only be installed on the 32-bit version of the database. The 64-bit version of the patch set must only be installed on the 64-bit version of the database. 

For a list of products included in this patch set, see the "Patch Set Components" section.

2 Oracle Universal Installer Version Requirements

This patch set includes Oracle Universal Installer release 10.1.0.5. You must use this Oracle Universal Installer to install this patch set and not Oracle Universal Installer from the 9.2.0.x maintenance release media or Oracle home.

This is not a complete software distribution. You must install it in an existing Oracle9i release 2 (9.2.0.x.x) installation. Users applying this patch setmust use Oracle Universal Installer release 10.1.0.5 (provided as part of this patch set) or later to ensure that their Oracle home can be patched in the future. Oracle Universal Installer release 10.1.0.5 is also installed when you install this patch set.

3 Patch Set Documentation

There are two documents related to this release of the Oracle9i release 2 patch set: 

• Oracle9i Patch Set Notes, Release 2 (9.2.0.8) Patch Set 7 for  Microsoft Windows (32-Bit) (this document)

  This document provides:

  • System requirements and information about how to install or reinstall the patch set

  • A list of all bugs fixed to date that are specific to Oracle9i release 2 for  Microsoft Windows (32-Bit)

  • A list of known issues relating to Oracle9i release 2 for  Microsoft Windows (32-Bit)

• Oracle9i List of Bugs Fixed, Release 2 (9.2.0.8) Patch Set 7

  The List of Bugs Fixed is a list of all generic bugs related to Oracle9i release 2 that have been fixed in this release.

Both of these documents are included with the patch set. The Oracle9i List of Bugs Fixed is also available on OracleMetalink, from document 189908.1,

ALERT: Oracle9i Release 2 (9.2) Support Status and Alerts at:

http://metalink.oracle.com

To locate document 189908.1:

1. Click Advanced at the top of the OracleMetalink page.

2. Enter 189908.1 in the Document ID field, then clickSubmit.

4 System Requirements

The following are the system requirements for this patch set:

• System Architecture:

  Intel Pentium and AMD processors

• Operating System

  • Windows Server 2003 

  • Windows 2000 (Service Pack 2 or higher)

  • Windows XP Professional

  
  

  Note:

  Windows 98 and Windows NT are no longer supported. See OracleMetalink notes 166748.1 and 166751.1 for more information.
  

• Oracle9i

  Oracle9i release 2 (9.2.0.1.0) or later

5 Preinstallation Tasks

Complete the following preinstallation tasks before installing the patch set:

• Review Known Preinstallation Issues

• Review Changes in Oracle Text Filtering Technology

• New Oracle C++ Call Interface Libraries Available for Windows

• Creating a Database with Database Configuration Assistant

• Preinstallation Considerations for Oracle Real Application Clusters

• Identify the Oracle9i Installation

• Check Postrelease Updates

• Download and Extract the Installation Software

• Shut Down Oracle Databases

• Stop All Processes

• Back Up the System

5.1 Review Known Preinstallation Issues

Review the information in the following sections. If any of the issues apply to your Oracle installation, follow the instructions before installing the patch set.

• Database Upgrade for Oracle E-Business Suite

• Patch Set Application with Physical or Logical Standby Databases in Place

• Notes to OLAP users

• Upgrading Preconfigured Standard Edition Databases

• Oracle Streams

• Oracle Data Guard

• Oracle Advanced Queuing

• Oracle Data Mining

• Event 10499: NUMBER Datatypes

• Oracle XDK

• Japanese Characters Not Displayed Properly

5.1.1 Database Upgrade for Oracle E-Business Suite

If you are an Oracle E-Business Suite customer and you want to upgrade your Oracle E-Business Suite release 11i database server to this patch set, then you must check the latest certification status and Interoperability Notes available on the OracleMetalink Web site at:

http://metalink.oracle.com/

All other customers wanting to upgrade their databases directly to this patch set should readUpgrading Directly to a 9.2.0 Patch Set available in document 214887.1 on the OracleMetaLink Web site.

5.1.2 Patch Set Application with Physical or Logical Standby Databases in Place

For information about applying a patch set to a current release of Oracle9i release 2 for a configuration that includes one or more physical standby databases, refer to notes available in OracleMetaLink document 187242.1.

5.1.3 Notes to OLAP users

Anyone desiring to use the OLAP option must have the Enterprise Edition of 9.2.0.1.0 with the OLAP option installed as their original base release, prior to installing any of the 9i patch sets, up to and including 9.2.0.8.0. Oracle highly recommends the Data Warehouse configuration type to optimize the database for OLAP.

If you are moving your Oracle database from a 32-bit operating system to a 64-bit operating system, either prior to applying the patch set or after applying the patch set, review document 352306.1 on the OracleMetalink Web site:

http://metalink.oracle.com

To locate document 352306.1:

1. Log on to OracleMetalink.

2. Click Advanced at the top of the OracleMetalink page.

3. Enter 352306.1 in the Document ID field, then clickSubmit.

5.1.4 Upgrading Preconfigured Standard Edition Databases

If you are using an Oracle9i release 2 (9.2) preconfigured Standard Edition database, then the database contains the following components that are not supported by the Standard Edition:

• Oracle Data Mining

• Oracle OLAP Catalog

• Oracle OLAP Analytic Workspace

• Oracle OLAP API

The catpatch.sql script does not run the patch scripts for these components. It sets the component STATUS toOPTION OFF in the DBA_REGISTRY view. The original versions of the dictionary objects for the components remain in the database but thecatpatch.sql script does not apply the patch to them. 

5.1.5 Oracle Streams

All databases that use any features of Oracle Streams must be upgraded to release 9.2.0.2 or later. Operation between release 9.2.0.1 and release 9.2.0.2 is not supported for databases using Oracle Streams features. 

Before you install the patch set software, review OracleMetalink note 283565.1.

5.1.6 Oracle Data Guard

Several known issues relate to the following components of Oracle Data Guard:

• Redo Apply (Physical Standby Databases)

• SQL Apply (Logical Standby Databases)

• Data Guard Broker

• Data Guard Broker Failover

Refer to OracleMetalink document 259804.1 for a complete set of release notes applicable to Oracle Data Guard in Oracle9i release 2.

Before you install the patch set software, review OracleMetalink note 283565.1.

5.1.7 Oracle Advanced Queuing

There are two known issues while upgrading from Oracle8i to Oracle9i release 2:

Customers running Oracle Applications release 11.5.7 or 11.5.8 with Advanced Queuing configured with multiconsumer queues may encounter corruption problems after upgrading their database from any Oracle8i database to 9.2. 

Note:

Refer to OracleMetalink note 231074.1 for more information. 

Oracle Streams Advanced Queuing (AQ) propagations that were previously scheduled must be unscheduled before upgrading an Oracle8i database. To unschedule AQ propagations, run theDBMS_AQADM.UNSCHEDULE_PROPAGATION PL/SQL procedure.

See Also:

PL/SQL Packages and Types Reference for more information about this procedure

5.1.8 Oracle Data Mining

Oracle Data Mining customers must ensure that the Oracle Data Mining account (ODM) is unlocked before applying the patch set. If the ODM account is locked, the patch installation generates an error and one of the Oracle Data Mining tables will be empty.

5.1.9 Event 10499: NUMBER Datatypes

Event 10499 was introduced in release 9.2.0.3 to allow customers to revert to the earlier behavior of NUMBER datatypes that have no explicit setting of their scale value. Any nonzero setting of the event level enables the old behavior. 

Before the introduction of this event, server code could return zero for the scale if a NUMBER datatype was created without specifying the scale. Other code paths would return -127. With this event, all code paths return -127, as this is the correct behavior. 

Client applications may rely on the previous (incorrect) behavior. Typically, client applications will test for a scale of -127 to distinguish between NUMBER and FLOAT datatypes. It is not sufficient to test the scale alone to distinguish between these two datatypes. You must test for a scale of -127 and a nonzero precision to identify a FLOAT. 

Client applications that rely on the old behavior can still work as before if the event is set. However, these applications must be corrected before upgrading to the next major release of the Oracle database. 

5.1.10 Oracle XDK

The Oracle9i release 2 (9.2.0.8) patch set contains XDK release 9.2.0.10. 

5.1.11 Japanese Characters Not Displayed Properly

The Japanese characters display square boxes in Oracle Universal Installer when JRE 1.3.1 is used. 

Workaround:

Perform the following steps:

1. Install JRE 1.4.2 on your local computer.

2. Use the following command to run Oracle Universal Installer:

   ./runInstaller -jreLoc /usr/java/jre

5.2 Review Changes in Oracle Text Filtering Technology

Beginning with patch set release 9.2.0.7, INSO software is no longer shipped with Oracle Text. It is replaced with Verity KeyView Export from Verity, Inc. There are a number of differences between the old and the new filters. If you intend to use Oracle Text, review document 296405.1 on the OracleMetalink Web site:

http://metalink.oracle.com

To locate document 296405.1:

1. Click Advanced at the top of the OracleMetalink page.

2. Enter 296405.1 in the Document ID field, then clickSubmit.

5.3 New Oracle C++ Call Interface Libraries Available for Windows

Beginning with the 9.2.0.5 patch set, new Oracle C++ Call Interface (OCCI) libraries for Microsoft C-Runtime debugging and for developing applications with Microsoft Visual C++ 7.0 .NET 2002 are available.Table 1 lists the new OCCI libraries and their installed locations.

Table 1 Oracle C++ Call Interface Library Files

OCCI Library FilenameInstalled LocationDescription

oraocci9d.lib and oraocci9d.dll

ORACLE_BASE\ORACLE_HOME\oci\lib\msvc\vc6

Applications requiring to link with MSVCRTD.DLL (debug version of Microsoft's C-Runtime) to debug memory issues should link with this OCCI library.This is for use with Microsoft Visual C++ 6.0.

oraocci9.lib and oraocci9.dll

ORACLE_BASE\ORACLE_HOME\oci\lib\msvc\vc7

Applications developed in Visual C++ .NET 2002 should use this OCCI library. The currently shipped OCCI DLL is built with Microsoft Visual C++ 6.0 and cannot be used from an Microsoft Visual C++ 7.0 .NET 2002 compiled application. This OCCI DLL links with the nondebug version of Microsoft C-Runtime (MSVCR70.DLL).

oraocci9d.lib and oraocci9d.dll

ORACLE_BASE\ORACLE_HOME\oci\lib\msvc\vc7

Applications requiring to link with MSVCR70D.DLL (debug version of Microsoft C-Runtime) in Microsoft Visual C++ 7.0 .NET 2002 to debug memory issues should link with this OCCI library.

Note:

The current Oracle C++ Call Interface library for Microsoft Visual C++ 6.0 is available as in previous releases.

• oraocci9.lib is available in ORACLE_BASE\ORACLE_HOME\oci\lib\msvc.

• oraocci9.dll is available in ORACLE_BASE\ORACLE_HOME\bin.

• Copies of these two files are also installed in ORACLE_BASE\ORACLE_HOME\oci\lib\msvc\vc6.

LIB and PATH Environment Variables

Set the LIB and PATH environment variables for the Visual C++ compiler version being used. For example, if you are using Microsoft Visual C++ 7.0 .NET 2002, add the following directory to the LIB andPATH variables:

ORACLE_BASE\ORACLE_HOME\oci\lib\msvc\vc7

You can set environment variables from the Windows Control Panel or use the SET command.

5.4 Creating a Database with Database Configuration Assistant

During database creation using Database Configuration Assistant, you may encounter an ORA-01430 error message. This error message can be ignored. The following is an example error message: 

(SDO_ROOT_MBR mdsys.sdo_geometry)*ERROR at line 2:ORA-01430: column being added already exists in table 

This issue is tracked with Oracle bug 3955522.

5.5 Preinstallation Considerations for Oracle Real Application Clusters

If you plan to install this patch in an Oracle Real Application Clusters environment, read the following section before proceeding:

• Preinstallation Considerations for Oracle Real Application Clusters

5.5.1 Preinstallation Considerations for Oracle Real Application Clusters

This patch set enables you to install the included patches on multiple nodes in a cluster if release 9.2.0.1 or higher is already installed on those nodes. Oracle Universal Installer detects whether the system where you are installing the software is part of a cluster environment. If it is, then the Oracle Universal Installer displays the available nodes from the cluster. 

Oracle provides clusterware and a cluster file system for Real Application Clusters running on Windows platforms. Patches to these components are provided in a separate patch (Patch 5388107). You must install this patch separately from the 9.2.0.8 patch set.

To locate this patch on OracleMetalink:

1. Click Patches from the left-hand column.

2. Enter the patch number 5388107 in the search field.

3. Click Search.

OracleMetalink is available at the following URL:

http://metalink.oracle.com/

Note:

It is important that you install the patch set on the same set of nodes, which had the base release installation. Choosing a different set of nodes during the patch set installation than were chosen during the base release installation will cause unwanted results in your Real Application Clusters environment, as some nodes will be upgraded to the new software versions, while others will not.

5.6 Identify the Oracle9i Installation

This is not a complete software distribution. You must install it in an existing Oracle9i Oracle home. To identify Oracle home directories,   use Oracle Universal Installer. From the Welcome screen, clickInstalled Products, then click Environment tab.

If you are installing this patch set on an existing Oracle RAC installation, you must run Oracle Universal Installer from the same node from which you performed the initial installation.

5.7 Check Postrelease Updates

Before installing this patch set in a production environment, review document 189908.1,ALERT: Oracle9i Release 2 (9.2) Support Status and Alerts, available on the OracleMetalink Web site at:

http://metalink.oracle.com

To locate this document:

1. Click Advanced at the top of the OracleMetalink page.

2. Enter 189908.1 in the Document ID field, then clickSubmit.

This document is created by Oracle Support Services and provides information about the status of issues discovered after this patch set was released. If you are unable to access this site, then contact Oracle Support Services before installing this patch set in a production environment.

5.8 Download and Extract the Installation Software

Download and extract the p4547809_9208_WINNT.zip patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory. For example,Oracle_patch.

5.9 Shut Down Oracle Databases

Shut down any existing Oracle database instances with normal or immediate priority. On Oracle RAC systems, shut down all instances on each node.

5.10 Stop All Processes

Stop all listener and other processes running in the Oracle home directory where you want to install the patch set.

When performing an Oracle RAC installation, shut down all Oracle services except the following services, if present:

• Oracle Object Service

• OracleClusterVolumeService

• OracleCMService9i

5.11 Back Up the System

Oracle recommends that you create a backup of the Oracle9i installation before you install the patch set.

6 Installation Tasks

You can install the patch set either interactively or noninteractively. See one of the following sections for information about how to complete the installation:

• To install the patch set interactively, see the "Installing the Patch Set Interactively" section.

• To install the patch set noninteractively, see the "Installing the Patch Set Noninteractively" section.

  
  

  Note:

  You must use Oracle Universal Installer release 10.1.0.5 or later to install this patch set.
  

6.1 Installing the Patch Set Interactively

Note:

If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle9i installation, Oracle Universal Installer displays a warning dialog with the following error:

There are no patches that need to be applied from thepatchset Oracle9i patch set 9.2.0.8.0

The Oracle Universal Installer does not allow the installation to proceed. ClickOK, then click Cancel to end the installation.

The following procedure describes how to install the patch set interactively:

1. Log on as a member of the Administrators group to the computer on which to install Oracle components. If you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), log on as a member of the Domain Administrators group.

2. Start Oracle Universal Installer release 10.1.0.5 located in the unzipped area of the patch set. For example,Oracle_patch\setup.exe. 

3. On the Welcome screen, click Next.

4. On the Specify File Locations screen, click Browse next to thePath field in the Source section. 

5. Select the products.xml file from the stage directory where you unpacked the patch set files, then clickNext. For example:

   Oracle_patch\stage\products.xml

6. In the Name field in the Destination section, select the name of the Oracle home that you want to update from the drop down list, then clickNext.

7. If you are installing the patch set on an Oracle RAC cluster, click Next when the Selected Nodes screen appears.

   
   

   Note:

   The Selected Nodes screen lists the existing Oracle9i RAC release 2 (9.2) nodes. The first node in the list is the node from where Oracle9i RAC release 2 (9.2) was installed. You must install the patch set software from this node. If this is not the node where you are running Oracle Universal Installer, then exit Oracle Universal Installer and install the patch set software from the first node in the list of nodes.
   

8. On the Summary screen, click Install.

   This screen lists all of the patches available for installation.

9. On the End of Installation screen, click Exit, then clickYes to exit Oracle Universal Installer.

6.2 Installing the Patch Set Noninteractively

The following procedure describes how to install the patch set noninteractively:

1. Log on as a member of the Administrators group to the computer on which to install Oracle components.

2. Copy the response file template provided in the response directory where you unpacked the patch set archive file. 

3. Edit the values for all fields labeled as <Value Required> as described by the comments and examples in the template. 

   
   

   Note:

   For Oracle RAC installations, make sure the CLUSTER_NODES variable specifies all of the nodes used in the original Oracle RAC installation.
   

4. Enter a command similar to the following to start Oracle Universal Installer in noninteractive mode. If Oracle Universal Installer is located inOracle_patch\setup.exe, then pass the full path of the response file template you have edited locally as the last argument:

   C:\Oracle_patch> setup.exe -silent -responseFile response_file_path

   where Oracle_patch is the location of the patch set you downloaded andresponse_file_path is the full path of the locally edited response file.

7 Postinstallation Tasks

Review the information in this section before using the upgraded software. This section lists required and optional postinstallation tasks, depending on the installation type and the products that you want to use.

• Upgrading Databases from Previous Releases Directly to Oracle9i Release 2 Version 9.2.0.8

• Configure OracleGSDService

• Required Postinstallation Tasks

• Upgrading Oracle Internet Directory 9.2.0.x.x

7.1 Upgrading Databases from Previous Releases Directly to Oracle9i Release 2 Version 9.2.0.8

To upgrade Oracle databases from a previous release directly to Oracle9i release 2 (9.2.0.8) follow the instructions in OracleMetalink note 214887.1,Upgrading Directly to a 9.2.0 Patch Set.

See Also:

For more information about upgrading a database, see the Oracle9i Database Migration guide.

7.2 Configure OracleGSDService

By default, the OracleGSDService is configured to run under theLocalSystem account. Manually configureOracleGSDService to run under a user account that is a member of theORA_DBA group.

7.3 Required Postinstallation Tasks

Complete the following tasks after installing the patch set software:

• Check Tablespace Sizes and Set Parameter Values

• Upgrade the Database

7.3.1 Check Tablespace Sizes and Set Parameter Values

Review the following sections before upgrading a database.

7.3.1.1 Check SYSTEM Tablespace Size

If JServer is part of the installation ensure that there is at least 10 MB of free space allocated to the SYSTEM tablespace.

7.3.1.2 Check XDB Tablespace Size

For Oracle RAC installations, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.

7.3.1.3 Set the SHARED_POOL_SIZE andJAVA_POOL_SIZE Initialization Parameters

Users who have JVM (Java enabled) or JVM and XDB installed on their 9.2.0.1 databases should make sure that theinit.ora parameters SHARED_POOL_SIZE andJAVA_POOL_SIZE are each 150 MB or more before running thecatpatch.sql upgrade script. Failure to do so could result in an unrecoverable memory failure while running of the script. Please note that JVM and XML DB was shipped as part of the default 9.2.0.1 seed database, and will be present unless the user explicitly installed a 9.2.0.1 instance without them.

Set the value of the SHARED_POOL_SIZE and theJAVA_POOL_SIZE initialization parameters as follows:

1. Use SQL*Plus to login to the database as the SYS user withSYSDBA privileges:

   C:\> sqlplus /NOLOGSQL> CONNECT SYS/SYS_password AS SYSDBA

2. Start the database:

   SQL> STARTUP

3. If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):

   SQL> SHOW PARAMETER PFILE; 

   This command displays the name and location of the server parameter file or the initialization parameter file.

4. Determine the current values of these parameters:

   SQL> SHOW PARAMETER SHARED_POOL_SIZESQL> SHOW PARAMETER JAVA_POOL_SIZE

5. If the system is using a server parameter file:

   1. If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:

      SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile; 

   2. If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:

      SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile; 

6. If the system uses an initialization parameter file, if necessary change the values of theSHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).

7. Shut down the database:

   SQL> SHUTDOWN

7.3.2 Upgrade the Database

After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home:

1. Log on as a member of the Administrators group to the computer where the Oracle components are installed.

2. For Oracle RAC installations, start the Global Services Daemon (GSD) on each node of the cluster as follows:

   C:\> gsdctl start

3. Start the Oracle Net listener as follows:

   C:\> lsnrctl start

   
   

   Note:

   For Oracle RAC installations, start the listener on each node of the cluster.
   

4. For single-instance installations, use SQL*Plus to login to the database as theSYS user with SYSDBA privileges:

   C:\> sqlplus /NOLOGSQL> CONNECT SYS/SYS_password AS SYSDBA

5. For Oracle RAC installations:

   1. Start the database as follows, where db_name is the database name:

      C:\> srvctl start database -d db_name

   2. Use SQL*Plus to login to the database as the SYS user withSYSDBA privileges:

      C:\> sqlplus /NOLOGSQL> CONNECT SYS/SYS_password AS SYSDBA

   3. Set the CLUSTER_DATABASE initialization parameter toFALSE:

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

      
      

      Note:

      If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameter toFALSE in the initialization parameter file (initsid.ora).
      

   4. Exit SQL*Plus and shut down the database:

      SQL> EXITC:\> srvctl stop database -d db_name

   5. Use SQL*Plus to login to the database as the SYS user withSYSDBA privileges:

      C:\> sqlplus /NOLOGSQL> CONNECT SYS/SYS_password AS SYSDBA

6. Enter the following SQL*Plus commands: 

   SQL> STARTUP MIGRATESQL> SPOOL patch.logSQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catpatch.sqlSQL> SPOOL OFF 

7. Review the patch.log file for errors and inspect the list of components that is displayed at the end ofcatpatch.sql script. 

   This list provides the version and status of each SERVER component in the database. 

8. If necessary, rerun the catpatch.sql script after correcting any problems.

9. Restart the database:

   SQL> SHUTDOWNSQL> STARTUP

10. Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.

    SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql

11. For Oracle RAC installations:

    1. Set the CLUSTER_DATABASE initialization parameter toTRUE:

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

       
       

       Note:

       If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameters toTRUE in the initialization parameter file (initsid.ora).
       

    2. Restart the database:

       SQL> SHUTDOWNSQL> EXITC:\> srvctl start database -d db_name

12. If you are using the Oracle Recovery Manager catalog, enter the following command:

    C:\> rman catalog username/password@aliasRMAN> UPGRADE CATALOG; 

13. If Oracle Internet Directory release 9.2.0 is installed, then complete the steps in the "Upgrading Oracle Internet Directory 9.2.0.x.x" section

Note:

If you are using the Oracle OLAP option, then you must run catpatch.sql andutlrp.sql on any additional instance created from your main 9.2.0.8 database. Yourcatpatch log should show the status of the three OLAP components as follows:

OLAP Analytic Workspace    UPGRADED  9.2.0.8.0Oracle OLAP API            UPGRADED  9.2.0.8.0OLAP Catalog               VALID     9.2.0.8.0

7.4 Upgrading Oracle Internet Directory 9.2.0.x.x

Complete the following steps only if Oracle Internet Directory version 9.2.0.x.x was installed in the Oracle home.

Note:

Make sure that the database and database listener are running, and all parameters for theoidpatchca.bat script are specified before to running the script.

1. Temporarily set the ORACLE_HOME andORACLE_SID environment variables. For example:

   C:\> set ORACLE_HOME=D:\oracle\ora92C:\> set ORACLE_SID=sales

2. Verify that the WINDIR system variable is set. For example:

   C:\winnt

3. Verify that the PATH system variable contains the Oracle homebin directory. For example:

   D:\oracle\ora92\bin

4. Ensure that the database and database listener are running, and all oidpatchca.bat parameters are specified correctly before you run the script:

   ORACLE_BASE\ORACLE_HOME\bin\oidpatchca.bat-connect Connect_String\ -lsnrport Listener_Port\ -systempwd SYSTEM_Password\ -odspwd ODS_Password\ -sudn Super-User_DN\ -supwd Super-User_Password\ -dippwd Password_to_register_DIP_Server\ -windir %windir%

   In the preceding command, Password_to_register_DIP_Server must conform to the password policy in the Oracle Internet Directory server.

8 Removing the Patch Set Software

Starting in 9.2.0.7.0, there is a new script called catbkout.sql. This script enables the user to restore the Oracle9i installation of the database back to the original 9.2 patch release (as long as it is 9.2.0.4 or greater) that the user backed up before applying the patch set. Perform the following steps for backing out from the 9.2.0.8 patch release:

1. Before restoring the Oracle home to the original release, perform the following steps:

   For Oracle RAC installations:

   1. Use SQL*Plus to log in to the database as the SYS user withSYSDBA privileges:

       C:\> sqlplus /nolog SQL> CONNECT SYS/SYS_password AS SYSDBA

   2. Set the CLUSTER_DATABASE initialization parameter toFALSE:

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

   3. Exit SQL*Plus and shut down the database:

      SQL> EXITC:\> srvctl stop database -d db_name

   C:\> sqlplus /nologSQL> CONNECT SYS/SYS_password AS SYSDBASQL> STARTUP MIGRATESQL> SPOOL catbkout.outSQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catbkout.sqlSQL> SPOOL OFFSQL> SHUTDOWN IMMEDIATE

   For Single Instance:

   C:\> sqlplus /nologSQL> CONNECT SYS/SYS_password AS SYSDBASQL> SHUTDOWN SQL> STARTUP MIGRATESQL> SPOOL catbkout.outSQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catbkout.sqlSQL> SPOOL OFFSQL> SHUTDOWN IMMEDIATE

2. Restore the Oracle9i installation that you backed up before applying the patch set.

3. After restoring the original Oracle home, perform the following steps:

   C:\> sqlplus /nologSQL> CONNECT SYS/SYS_password AS SYSDBASQL> STARTUP MIGRATESQL> SPOOL catpatch.outSQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catpatch.sqlSQL> SPOOL OFF

4. If Oracle Spatial is installed with the database, perform the following steps:

   SQL> alter session set current_schema = mdsys;SQL> @ORACLE_BASE\ORACLE_HOME\md\admin\prvtmd.plbSQL> @ORACLE_BASE\ORACLE_HOME\md\admin\prvtmd2.plbSQL> @ORACLE_BASE\ORACLE_HOME\md\admin\sdopidx.sqlSQL> @ORACLE_BASE\ORACLE_HOME\md\admin\prvtpidx.plbSQL> @ORACLE_BASE\ORACLE_HOME\md\admin\prvtsidx.plbSQL> @ORACLE_BASE\ORACLE_HOME\md\admin\sdogeom.sqlSQL> @ORACLE_BASE\ORACLE_HOME\md\admin\prvt3glh.plbSQL> @ORACLE_BASE\ORACLE_HOME\md\admin\prvtgeom.plbSQL> @ORACLE_BASE\ORACLE_HOME\md\admin\prvt3gl.plbSQL> alter session set current_schema = sys;

5. Shut down the database:

   SQL> SHUTDOWN IMMEDIATE

6. Start the database and recompile the remaining invalid objects:

   SQL> STARTUPSQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql

7. Review catbkout.out and catpatch.out for errors.

8. Restart the database:

   For Oracle RAC installations:

   1. Set the CLUSTER_DATABASE initialization parameter toTRUE:

      
      

      Note:

      If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameters toTRUE in the initialization parameter file (initsid.ora).
      

       SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile; SQL> SHUTDOWN SQL> EXIT C:\> srvctl start database -d db_name

   For Single Instance:

   SQL> SHUTDOWNSQL> STARTUP

9 Reinstalling the Patch Set Software

If necessary, you can reinstall a patch set that has been applied to an Oracle9i installation. You must reinstall the patch set interactively.

To reinstall the patch set:

1. Make sure you complete the same set of preinstallation tasks that you performed when you installed the patch set initially: 

   1. Log on as a member of the Administrators group to the computer on which to install Oracle components. Log on as a member of the Domain Administrators group if you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC). 

   2. Unzip the downloaded patch set file in a new directory.

   3. Shut down the existing Oracle server instance with normal or immediate priority. 

   4. Stop all listener, agent, and other processes running in or against the Oracle home in which you are installing.

2. Start Oracle Universal Installer release 10.1.0.5 located in the unzipped area of the patch set. For example,Oracle_patch\setup.exe. 

3. On the Welcome screen, click Next. The File Locations screen appears. 

4. On the Specify File Locations screen, click Browse next to thePath field in the Source section. 

5. Select the products.xml file from the stage directory where you unpacked the patch set files. For example: 

   Oracle_patch\stage\products.xml

6. Select the Oracle home that you want to upgrade in the Name field in theDestination section, then click Next. 

   
   

   Note:

   If you are not sure of the name of the Oracle home, click Installed Products to determine the name of the Oracle home that you want to upgrade.
   

   If you are installing the patch on an Oracle RAC cluster, click Next on the Selected Nodes screen.

   The Available Product Component screen appears. This screen contains a list of all components that have been patched by the original patch set installation. These components are grayed out, indicating they cannot be selected for installation.

7. Expand the node for each component listed in the tree. You will see a patch that corresponds to each component. 

8. Select the patch for installation by selecting the check box to the left of the patch name. As you do this, theInstall Status column should say Reinstall.

9. Repeat the process for each patch bundled in the patch set.

10. Click Next. The patches to be reinstalled will appear.

11. Verify the list of patches to be reinstalled.

12. On the Summary screen, verify the list of patches to be reinstalled, then clickInstall. 

13. On the End of Installation screen, click Exit, then clickYes to exit from Oracle Universal Installer.

10 Known Issues

Review the following known issues after you apply the patch set.The following known issues apply to this patch set release:

• Oracle Procedural Gateway for APPC Configuration Parameters

• Upgrade and SYS Schema

• PL/SQL Cursor Caching

• Bug 2602782

• Bug 3047541

• Bug 3259636

• Bug 2908196

• Bug 4270038

10.1 Oracle Procedural Gateway for APPC Configuration Parameters

If you use Oracle Procedural Gateway for APPC, comment out the following parameters if they are present in the gateway shell script orinitsid.ora files:

• FDS_CLASS

• FDS_CLASS_VERSION

• FDS_INSTANCE

10.2 Upgrade and SYS Schema

This is a generic issue applicable to the upgrade mode, for example, ALTER DATABASE OPEN MIGRATE. During an upgrade from release 9.2.0.1 or later, thecatpatch.sql script can take a long time if there are statistics for theSYS schema. Delete the statistics on all of the objects in theSYS schema, and then recollect the statistics after normal database open, if necessary. 

To drop and re-create the statistics, enter the following commands in SQL*Plus: 

SQL> EXECUTE DBMS_STATS.DELETE_SCHEMA_STATS('SYS');SQL> EXECUTE DBMS_STATS.GATHER_SCHEMA_STATS('SYS');

10.3 PL/SQL Cursor Caching

In release 9.2.0.4 and earlier, the maximum number of cursors that could be cached for fast lookup by PL/SQL was bounded by the value of theOPEN_CURSORS initialization parameter. If you currently have this parameter set to a high value (for example, greater than 1000), it might be causing large numbers of PL/SQL cursors to be cached in the shared pool. This could lead to issues with memory management, frequent reloading of library cache objects, andORA-04031 errors.

Starting with release 9.2.0.5, the SESSION_CACHED_CURSORS initialization parameter now determines the upper bound for PL/SQL cursor caching instead of theOPEN_CURSORS initialization parameter.

Most users do not need to modify the value of either of these parameters. If theSESSION_CACHED_CURSORS parameter value is greater than theOPEN_CURSORS parameter value, then this change has no performance affect on your system.

However, if the SESSION_CACHED_CURSORS parameter value is zero or a value significantly lower than theOPEN_CURSORS parameter value, and you want to cache PL/SQL cursors for optimal performance, then increase theSESSION_CACHED_CURSORS parameter value appropriately. 

This issue is tracked with Oracle bug 3150705.

10.4 Bug 2602782

Scrollable ResultSet returns 3 times NCHAR character byte size when database Ncharset is UTF8. This problem occurs only with the JDBC Thin driver. 

10.5 Bug 3047541

There is a known limitation on Windows 2000 where the size of the CLASSPATH variable can grow too large. If this happens, the shortcuts to the following products may not display:

• Change Manager

• Performance Manager

• SQL*Plus Worksheet

• Enterprise Manger Console

Workaround:

Reduce the size of the system CLASSPATH environment variable.

10.6 Bug 3259636

If you use Database Configuration Assistant (DBCA) to create a new database, using the seed database option, some of the components are from an older version. This is because the seed database was created before the patch release.

To update all the components, ensure that you have followed the steps described in the "Upgrade the Database" section.

10.7 Bug 2908196

If you use USER_FILTER for custom filtering orINSO_FILTER for filtering formatted documents, then ensure that the environment variable for the temporary file directory location does not contain spaces.

Workaround:

Modify the temporary file directory environment variable to a directory name that does not contain any spaces, and then bounce the database in a manner, such that, it picks up this new value of the environment variable.

Examples of correct environment variables are as follows:

TEMP=C:\TEMPTMP=C:\TMP

10.8 Bug 4270038

When using Database Configuration Assistant in standalone mode to create a database, the following error will occur:

ORA-29807: specified operator does not exist

Workaround:

Click Ignore.

11 Fixed Platform-Specific Bugs for Windows (32-Bit)

The following table is a cumulative list of the platform-specific bugs fixed in all Oracle9i for Windows 32-bit patch sets to date:

Note:

You may or may not receive platform-specific bugs.

Fixed in ReleaseBug NumberDescription9.2.0.42866965CAN'T ATTACH ANY AW'S UPDATED IN 9.2.0.29.2.0.42838610CAN NOT CREATE MORE THAN 10 POLICIES IN LABEL SECURITY9.2.0.42691996NUMBERFORMATEXCEPTION IN PERFORMANCE MANAGER WHEN MONITORING OS CHARTS9.2.0.42368369WHEN OCISETATTRIBUTE IS CALLED TO SET NON-BLOCKING ON WINDOWS NT GETS ERROR9.2.0.42593071IMPLEMENT CHANGES DONE TO SL.H FOR BUG 2285641 ON NT9.2.0.42635260ORA_OEMAGENT_DIR PREVENTS AGENT FROM STARTING9.2.0.42613603USER DEFINED EVENT SUDDENLY FAILS WITH FAILURE -- NO RESULT RETURNED IN OUTPUT9.2.0.42453901CMANAGER DISCOVERY SCRIPT IS USING A WRONG LOG FILENAME9.2.0.42225320GETTING NEGATIVE DISKSPACE VALUES RETURNED FROM PCT DISKSPACE BASED EVENTS9.2.0.41867995DEFAULT AGENT DISCOVERS FAI L SAFE DATABASES9.2.0.84185747ORA-01459 ERROR ON KEYSET-DRIVEN RECORDSET WITH LONG/LONG RAW9.2.0.83781883ODBC CAUSES ACCESS VIOLATION WHEN STRING LITERAL CONTAINS CR LF CODE9.2.0.84608183PERFORMANCE ISSUES WITH THE 10.1.0.4.0 ORACLE ODBC DRIVER9.2.0.8471943610.1.0.4.0 ODP.NET PUBLISHER POLICY DOES NOT ADDRESS THE 9.2.0.2.102 VERSION9.2.0.84537790CLUSTER NODES HANG AND THEN BUGCHECK ON REBOOTS9.2.0.84312390ORADIM COMMAND CAN'T SHUTDOWN DATABASE : ORA-10319.2.0.84632494DBMS_LOB.FILEOPEN GETS ORA-22288 WHEN FILE NAME INCLUDES 0X5C9.2.0.84947132ENCOUNTER ORA-911 AGAINST JAPANESE TABLE/COL NAME9.2.0.83734843CLIENT CONNECTION HANGS AFTER VIP FAILOVER9.2.0.84407799OCIBREAK() THROWS DR.WATSON ORAN9!ZTVULL (ACCESS VIOLATION)9.2.0.84308824NTS FAILS IF AUTH PACKET IS GREATER THAN SDU9.2.0.84278371STARTING ASM INSTANCE FAILS IF WORKGROUP NAME AND NETBIOS NAME ARE SAME9.2.0.83991216NMS-1078 ON TABLESPACE FULL EVENT9.2.0.84108430NMS-1005 EVENT SUBMISSION FAILS IN FIALSAFE ENVIRONMENT9.2.0.83760624OEM SRVCTL SYNTAX IS INCORRECT STARTING / SHUTTING DOWN ORACLE RAC DB

12 Patch Set Components

The following table lists the components included in this patch set:

ComponentVersionAdvanced Queuing (AQ) API9.2.0.8.0Agent required support files9.2.0.8.0Assistant common files9.2.0.8.0Data Management Services common files9.2.0.8.0Authentication and encryption9.2.0.8.0Database SQL scripts9.2.0.8.0Database Verify utility9.2.0.8.0DCE integration9.2.0.8.0Export/import9.2.0.8.0External naming: NIS9.2.0.8.0Generic connectivity common files9.2.0.8.0Generic connectivity using ODBC9.2.0.8.0Generic connectivity using OLEDB - FS9.2.0.8.0Generic connectivity using OLEDB - SQL9.2.0.8.0JDBC common files9.2.0.8.0JDBC/OCI common files9.2.0.8.0LDAP required support files9.2.0.8.0Migration utility9.2.0.8.0Object Type Translator9.2.0.8.0Oracle C++ Call Interface9.2.0.8.0Oracle Call Interface (OCI)9.2.0.8.0Oracle Client required support files9.2.0.8.0Oracle Connection Manager9.2.0.8.0Oracle Core required support files9.2.0.8.0Oracle database demos9.2.0.8.0Oracle database utilities9.2.0.8.0Oracle Data Mining9.2.0.8.0Oracle interMedia Client compatibility files9.2.0.8.0Oracle interMedia Java Advanced Imaging9.2.0.8.0Oracle Internet Directory Client9.2.0.8.0Oracle Internet Directory Server9.2.0.8.0Oracle Intelligent Agent9.2.0.8.0Oracle interMedia Locator9.2.0.8.0Oracle JDBC Development Drivers9.2.0.8.0Oracle JDBC Thin Driver for JDK 1.29.2.0.8.0Oracle JDBC Thin Driver for JDK 1.49.2.0.8.0Oracle JVM9.2.0.8.0Oracle Java Tools9.2.0.8.0Oracle Label Security9.2.0.8.0Oracle Net Configuration Assistant9.2.0.8.0Oracle Net Listener9.2.0.8.0Oracle Net Manager9.2.0.8.0Oracle Net9.2.0.8.0Oracle Net Protocol Support9.2.0.8.0Oracle Net required support files9.2.0.8.0Oracle OLAP9.2.0.8.0Oracle Partitioning9.2.0.8.0Oracle Procedural Gateway for IBM MQSeries9.2.0.8.0Oracle Procedural Gateway for APPC9.2.0.8.0Oracle Text9.2.0.8.0Oracle Transparent Gateway for DRDA9.2.0.8.0Oracle Transparent Gateway for Microsoft SQL Server9.2.0.8.0Oracle Transparent Gateway for Sybase9.2.0.8.0Oracle Transparent Gateway for Teradata9.2.0.8.0Oracle Ultra Search common files9.2.0.8.0Oracle Ultra Search middle-tier9.2.0.8.0Oracle UltraSearch server9.2.0.8.0Oracle Wallet Manager9.2.0.8.0Oracle XML Developer's Kit9.2.0.10.0Oracle XML SQL utility9.2.0.8.0Oracle9i release 2 Globalization9.2.0.8.0Oracle9i release 2 Real Application Clusters9.2.0.8.0Oracle9i release 29.2.0.8.0Oracle PL/SQL9.2.0.8.0Oracle PL/SQL required support files9.2.0.8.0Precompiler common files9.2.0.8.0Precompiler required support files9.2.0.8.0Pro*C/C++9.2.0.8.0Pro*COBOL1.8.77.8.0Pro*COBOL9.2.0.8.0Oracle database required support files9.2.0.8.0Oracle Recovery Manager9.2.0.8.0Secure Socket Layer (SSL)9.2.0.8.0SQL*Loader9.2.0.8.0SQL*Plus9.2.0.8.0SQLJ Runtime9.2.0.8.0SSL required support files9.2.0.8.0Utilities common files9.2.0.8.0XML Parser for C9.2.0.8.0XML Parser for C++9.2.0.8.0XML Parser for Java9.2.0.8.0XML Parser for PL/SQL9.2.0.8.0XML Parser for Oracle JVM9.2.0.8.0XSQL Servlet9.2.0.8.0

13 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, seven days a week. For TTY support, call 800.446.2398.

---

Oracle9i Patch Set Notes, Release 2 (9.2.0.8) Patch Set 7 for Microsoft Windows (32-Bit)

Copyright © 2006, 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 Corporation, 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, Oracle. All rights reserved.