Oracle9i Patch Set Notes
Release 2 (9.2.0.6) Patch Set 5 for Microsoft Windows (32-Bit)
 

 

Oracle9i

Patch Set Notes

Release 2 (9.2.0.6) Patch Set 5 for Microsoft Windows (32-Bit)

September 2005

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

This document contains the following sections:

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.6 includes all fixes in patch sets 9.2.0.6 and earlier as well as new fixes for patch set 9.2.0.6. 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.

This patch set includes Oracle Universal Installer release 10.1.0.3. 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.

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

2 Oracle Universal Installer Version Requirements

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 set must use Oracle Universal Installer release 10.1.0.3 (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.3 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:

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

4 System Requirements

The following are the system requirements for this patch set:

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

Contacts: Shankar.Iyer@oracle.com, Krishna.Mohan@oracle.com, Rekha.Vallam@oracle.com, CHETAN.PARAMPALLI@oracle.com

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 Filename Installed Location Description

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 and PATH variables:

ORACLE_BASE\ORACLE_HOME\oci\lib\msvc\vc7

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

6 Preinstallation Tasks

Complete the following preinstallation tasks before installing the patch set:

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

6.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 read Upgrading Directly to a 9.2.0 Patch Set available in document 214887.1 on the OracleMetaLink Web site.

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.0) or later, the catpatch.sql script can take a long time if there are statistics for the SYS schema. The user should delete the statistics on all the objects in the SYS 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:

DBMS_STATS.DELETE_SCHEMA_STATS('SYS');
DBMS_STATS.GATHER_SCHEMA_STATS('SYS');

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 release 2 for a configuration that includes one or more physical standby databases, refer to notes available in OracleMetaLink document 187242.1.

6.1.2 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

  • Spatial

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

6.1.3 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 Oracle MetaLink note 283565.1.

6.1.4 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

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 Oracle MetaLink note 283565.1.

6.1.5 Oracle Text INSO Updates

Oracle Text uses the INSO filter during the indexing of binary documents. This filtering technology is based on Stellent Chicago Corporation HTML Export technology and is licensed from Stellent Chicago Corporation.

INSO 7.5 is included with this patch set and supports additional platforms and document types. A full list of supported platforms and document types is documented in Note 212584.1 in OracleMetaLink.

6.1.6 Oracle Advanced Queuing

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 to 9.2.0.x from any Oracle8i database.


Note:

Refer to Oracle MetaLink note 231074.1 for more information.

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

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

6.1.9 Oracle XDK

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

6.1.10 XML DB

XML DB users must use DB release 9.2.0.3 or later. Earlier releases are no longer supported.

6.1.11 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 the OPEN_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, and ORA-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 the OPEN_CURSORS initialization parameter.

Most users do not need to modify the value of either of these parameters. If the SESSION_CACHED_CURSORS parameter value is greater than the OPEN_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 the OPEN_CURSORS parameter value, and you want to cache PL/SQL cursors for optimal performance, then increase the SESSION_CACHED_CURSORS parameter value appropriately.

This issue is tracked with Oracle bug 3150705.

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

6.3 SQL*Plus

The Oracle9i release 2 (9.2.0.6) patch set contains SQL*Plus release 9.2.0.8.

6.4 Preinstallation Considerations for Real Application Clusters

This patch set enables you to install the included patches on multiple nodes of a cluster if release (9.2.0.1.0) or later is already installed on those nodes. Oracle Universal Installer will detect whether the system where you are installing the software is part of a cluster environment. If it is, then Oracle Universal Installer will display 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 3973928). You must install this patch separately from the 9.2.0.6 patch set.

To locate this patch on OracleMetaLink:

  1. Click Patches from the left-hand column.

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

  3. Click Search.

Oracle MetaLink is available at the following URL:

http://metalink.oracle.com/


Note:

You must install Oracle Universal Installer release 10.1.0.3 on all nodes in the cluster before installing patch set 9.2.0.6 on an Oracle Real Applications Clusters environment.


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.

6.5 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, click Installed Products, then click the Environment tab.

If you are installing this patch set on an existing Real Application Clusters (RAC) installation, you must run the Installer from the same node from which you performed the initial installation.

6.6 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 click Submit.

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.

6.7 Download and Extract the Installation Software

To download and extract the patch set installation software:

  1. Download and extract the p3948480_9206_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

  2. Enter the following commands to unzip and extract the installation files:

6.8 Shut Down Oracle Databases

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

6.9 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 RAC installation, shut down all Oracle services except the following services, if present:

  • Oracle Object Service

  • OracleClusterVolumeService

  • OracleCMService9i

6.10 Back Up the System

Oracle recommends that you create a backup of the Oracle9i installation before you install the patch set. After the patch set is installed, there is no way to remove it.

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

Installing the Patch Set Interactively

To install the Oracle9i patch set interactively:


Note:

If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle9i installation, the Installer displays a warning dialog with the following error:
There are no patches that need to be applied from the
patchset Oracle9i patch set 9.2.0.6.0

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


The following procedure describes how to install the patch set:

  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.3 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 the Path field in the Source section.

  5. Select the products.xml file from the stage directory where you unpacked the patch set files, then click Next. 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 click Next.

  7. Select Oracle 9iR2 Patchset 9.2.0.6.0 from the available options.

  8. If you are installing the patch set on an 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.

  9. On the Summary screen, click Install.

    This screen lists all of the patches available for installation.

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

Installing the Patch Set Noninteractively

To install the Oracle9i 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 RAC installations, make sure the CLUSTER_NODES variable specifies all of the nodes used in the original RAC installation.

  4. Enter a command similar to the following to start Oracle Universal Installer in noninteractive mode. If Oracle Universal Installer is located in Oracle_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 and response_file_path is the full path of the locally edited response file.

  5. To run the Installer, enter a command similar to the following, where response_file is the full path to the response file that you edited:

    $ cd patchset_directory/Disk1
    $ ./runInstaller -silent -responseFile response_file
    
    
  6. After the installation, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an RAC installation, then run the root.sh script on each node of the cluster.

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


Note:

If JServer is installed in the database, make sure there is at lease 10MB of free space in the SYSTEM table space before completing postinstallation tasks.

8.1 Upgrading Databases from Previous Releases Directly to Oracle9i release 2 Version 9.2.0.6

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


Note:

Oracle9i Database Migration guide for more information about upgrading a database

8.2 Configure OracleGSDService

By default, the OracleGSDService is configured to run under the LocalSystem account. Manually configure OracleGSDService to run under a user account that is a member of the ORA_DBA group.

8.3 Required Postinstallation Tasks

Review the "Check Tablespace Sizes and Set Parameter Values" section and complete the steps in the "Upgrade the Database" section after you have installed the patch set software.

8.3.1 Check Tablespace Sizes and Set Parameter Values

Review the following sections before upgrading a database.

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

8.3.1.2 Check DB Tablespace Size

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

8.3.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters

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

  1. Start the database:

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

  3. Determine the current values of these parameters:

    SQL> SHOW PARAMETER SHARED_POOL_SIZE
    SQL> SHOW PARAMETER JAVA_POOL_SIZE
    
    
  4. 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; 
      
      
  5. If the system uses an initialization parameter file, if necessary change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).

  6. Shut down the database:

    SQL> SHUTDOWN
    
    

8.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 RAC installations, start the Global Services Daemon (GSD) on each node of the cluster as follows:

    $ gsdctl start
    
    
  3. Start the Oracle Net listener as follows:

    $ lsnrctl start <db_listener_name>
    
    

    Note:

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

    If you are using the Oracle OLAP option, make sure that the listener is running.


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

    sqlplus /NOLOG
    CONNECT SYS/password AS SYSDBA
    
    
  5. For RAC installations:

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

      $ srvctl start database -d db_name
      
      
    2. Use SQL*Plus to login to the database as the SYS user with SYSDBA privileges:

      sqlplus /NOLOG
      CONNECT SYS/password AS SYSDBA
      
      
    3. Set the CLUSTER_DATABASE initialization parameter to FALSE:

       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 to FALSE in the initialization parameter file (initsid.ora).

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

      SQL> EXIT
      $ srvctl stop database -d db_name
      
      
    5. Use SQL*Plus to login to the database as the SYS user with SYSDBA privileges:

      sqlplus /NOLOG
      CONNECT SYS/password AS SYSDBA
      
      
  6. Enter the following SQL*Plus commands:

    SQL> STARTUP MIGRATE
    SQL> SPOOL patch.log
    SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catpatch.sql
    SQL> SPOOL OFF
     
    
  7. Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.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> SHUTDOWN
    SQL> 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 RAC installations:

    1. Set the CLUSTER_DATABASE initialization parameter to TRUE:

       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 to TRUE in the initialization parameter file (initsid.ora).

    2. Restart the database:

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

    $ rman catalog username/password@alias 
    RMAN> 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

8.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 the oidpatchca.bat script are specified before to running the script.

  1. Temporarily set the ORACLE_HOME and ORACLE_SID environment variables. For example:

    C:\> set ORACLE_HOME=D:\oracle\ora92
    C:\> 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 home bin 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.

9 Removing the Patch Set Software

You cannot remove the patch set software after you have installed it. Oracle recommends that you back up the Oracle9i installation before applying the patch set. If you do not want to use a patch set applied to an Oracle9i installation, do one of the following:

If you choose not to use a patch set because you are encountering a problem, contact Oracle Support Services to verify that the problem you are encountering is being addressed.

If you completed the steps in the "Upgrade the Database" section, you must do one of the following for each database that you upgraded to the patch set:

10 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.3 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 the Path 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 the Destination 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.

    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, the Install 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 click Install.

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

11 Known Issues

Review the following known issues after you apply the patch set:

The following known issues apply to this patch set release:

11.1 Procedural Gateway for APPC or Transparent Gateway for IBM DRDA: Unspecified Error Message

During the installation of Procedural Gateway for APPC or Transparent Gateway for IBM DRDA, you may encounter an error message regarding an unspecified target of the makefile. The error message can be ignored. The following is an example of a message that can be ignored:

Error while invoking target <blank> of makefile
/oracle/9.2.0.6/gateway/lib/gateway.mk

The following is an example of a valid error message. Notice that the target of the makefile is identified. Messages similar to the following should not be ignored, and you should contact Oracle Support Services.

Error while invoking target install of makefile
/oracle/9.2.0.6/gateway/lib/gateway.mk

11.2 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 or initsid.ora files:

  • FDS_CLASS

  • FDS_CLASS_VERSION

  • FDS_INSTANCE

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

11.4 Bug 3047541

Comment : Status?

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.

11.5 Bug 3259636

If you use DBCA to create a new database using the seed database option, some of the components will be from an older version. This is because the seed database was created before the patch release.

To correct this problem, run the catpatch.sql script as described in the "Upgrade the Database" section .

11.6 Bug 3785754

If you are using Oracle Streams, SQL Apply with a logical standby database, or the LogMiner query tool using the DICT_FROM_REDO_LOGS option, you might see a warning similar to the following when you run the catpatch.sql script:

***WARNING*** At 21-SEP-04 09:52:09 problems related to bug 3785754 were encountered.  See Patch or Upgrade Notes. 
Call Oracle support.

This warning indicates that problems were detected in the LogMiner dictionary. See Oracle MetaLink note 283565.1 for information about these problems.

Depending on the application that you are running, do the following:

  • Oracle Streams

    Destroy and re-create captures.

  • Logical Standby

    Reinstantiate the standby database.

If it is not practical to take these actions, contact Oracle Support for alternative instructions to repair the LogMiner dictionary.


Note:

If you receive this warning, you must fix the problems in the LogMiner dictionary before resuming normal operations. If you do not immediately fix the problems, you may not be able to fix the problems in the future.

12 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 Release Bug Number Description
9.2.0.4 2866965 Cannot attach any AW's updated in 9.2.0.2.
9.2.0.4 2838610 Cannot create more than 10 policies in label security.
9.2.0.4 2691996 NumberFormatException appears in Performance Manager when monitoring operating system charts.
9.2.0.4 2368369 When ocisetattribute is called to set nonblocking on, Windows NT does not support.
9.2.0.4 2593071 Implement changes done to sl.h for bug 2285641 on Windows NT.
9.2.0.4 2635260 ORA_OEMAGENT_DIR prevents agent from starting.
9.2.0.4 2613603 User-defined event suddenly fails with failure. The output will have no result returned.
9.2.0.4 2453901 CMANAGER discovery script is using a wrong log filename.
9.2.0.4 2225320 Getting negative diskspace values returned from PCT disk space based events.
9.2.0.4 1867995 Reconciliation Exception: Error in code - selects BANK ACC NAME, NOT NUM.

13 Patch Set Components

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

Component Version
Advanced Queuing (AQ) API 9.2.0.6
Agent required support files 9.2.0.6
Assistant common files 9.2.0.6
Data Management Services common files 9.2.0.6
Authentication and encryption 9.2.0.6
Database SQL scripts 9.2.0.6
Database Verify utility 9.2.0.6
DCE integration 9.2.0.6
Export/import 9.2.0.6
External naming: NIS 9.2.0.6
Generic connectivity common files 9.2.0.6
Generic connectivity using ODBC 9.2.0.6
Generic connectivity using OLEDB - FS 9.2.0.6
Generic connectivity using OLEDB - SQL 9.2.0.6
JDBC common files 9.2.0.6
JDBC/OCI common files 9.2.0.6
LDAP required support files 9.2.0.6
Migration utility 9.2.0.6
Object Type Translator 9.2.0.6
Oracle C++ Call Interface 9.2.0.6
Oracle Call Interface (OCI) 9.2.0.6
Oracle Client required support files 9.2.0.6
Oracle Connection Manager 9.2.0.6
Oracle Core required support files 9.2.0.6
Oracle database demos 9.2.0.6
Oracle database utilities 9.2.0.6
Oracle Data Mining 9.2.0.6
Oracle interMedia Client compatibility files 9.2.0.6
Oracle interMedia Java Advanced Imaging 9.2.0.6
Oracle Internet Directory Client 9.2.0.6
Oracle Internet Directory Server 9.2.0.6
Oracle Intelligent Agent 9.2.0.6
Oracle interMedia Locator 9.2.0.6
Oracle JDBC Development Drivers 9.2.0.6
Oracle JDBC Thin Driver for JDK 1.2 9.2.0.6
Oracle JDBC Thin Driver for JDK 1.4 9.2.0.6
Oracle JVM 9.2.0.6
Oracle Java Tools 9.2.0.6
Oracle Label Security 9.2.0.6
Oracle Net Configuration Assistant 9.2.0.6
Oracle Net Listener 9.2.0.6
Oracle Net Manager 9.2.0.6
Oracle Net 9.2.0.6
Oracle Net Protocol Support 9.2.0.6
Oracle Net required support files 9.2.0.6
Oracle OLAP 9.2.0.6
Oracle Partitioning 9.2.0.6
Oracle Procedural Gateway for IBM MQSeries 9.2.0.6
Oracle Procedural Gateway for APPC 9.2.0.6
Oracle Text 9.2.0.6
Oracle Transparent Gateway for DRDA 9.2.0.6
Oracle Transparent Gateway for Microsoft SQL Server 9.2.0.6
Oracle Transparent Gateway for Sybase 9.2.0.6
Oracle Transparent Gateway for Teradata 9.2.0.6
Oracle Ultra Search common files 9.2.0.6
Oracle Ultra Search middle-tier 9.2.0.6
Oracle UltraSearch server 9.2.0.6
Oracle Wallet Manager 9.2.0.6
Oracle XML Developer's Kit 9.2.0.8.0
Oracle XML SQL utility 9.2.0.6
Oracle9i release 2 Globalization 9.2.0.6
Oracle9i release 2 Real Application Clusters 9.2.0.6
Oracle9i release 2
9.2.0.6
Oracle PL/SQL 9.2.0.6
Oracle PL/SQL required support files 9.2.0.6
Precompiler common files 9.2.0.6
Precompiler required support files 9.2.0.6
Pro*C/C++ 9.2.0.6
Pro*COBOL 1.8.77.6.0
Pro*COBOL 9.2.0.6
Oracle database required support files 9.2.0.6
Oracle Recovery Manager 9.2.0.6
Secure Socket Layer (SSL) 9.2.0.6
SQL*Loader 9.2.0.6
SQL*Plus 9.2.0.8.0
SQLJ Runtime 9.2.0.6
SSL required support files 9.2.0.6
Utilities common files 9.2.0.6
XML Parser for C 9.2.0.6
XML Parser for C++ 9.2.0.6
XML Parser for Java 9.2.0.6
XML Parser for PL/SQL 9.2.0.6
XML Parser for Oracle JVM 9.2.0.6
XSQL Servlet 9.2.0.6

14 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

Orac

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


Oracle Database Patch Set Release Notes, Release 2 (9.2.0.6) Patch Set 5 for Microsoft Windows (32-Bit)

Copyright © 2005, 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 Retek 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.