Skip Headers

Oracle9i Database Server Patch Set Notes
Release 2 Patch Set 4 Version 9.2.0.5.0 for Solaris Operating Environment (SPARC 64-bit)
 

 

Copyright © 2001, 2004  Oracle. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Oracle9i Database Server

Patch Set Notes

Release 2 Patch Set 4 Version 9.2.0.5.0 for Solaris Operating Environment (SPARC 64-bit)

March 2004

These patch set notes accompany the Oracle9i release 9.2.0.5 patch set.

This document contains the following sections:

The patch set includes the patches for all previous 9.2.0.x patch sets, and patches for the following:

Patch Set Overview

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

Patch sets include all the libraries that have been rebuilt to implement the bug fixes in the set. All the fixes in the patch set have been tested and are certified to work with each other. Because the patch set includes only low impact patches, it does not require you to certify applications or tools against the server.

Patch sets are cumulative. For example, patch set release 9.2.0.5 would include all the fixes in patch sets 9.2.0.2, 9.2.0.3 and 9.2.0.4 as well as new fixes for patch set 9.2.0.5. This means that unless the patch set documentation indicates otherwise, the patch set can be applied to any earlier 9.2.0 version. There is no requirement to install all intermediate patch sets.

Patch sets contain the same set of generic fixes across all platforms. Patch sets may also include additional patches specific to the platform on which they are released.

Oracle provides both 32-bit and 64-bit versions of the Oracle9i database server on the Solaris operating system. The 32-bit version of the database can be run on the 32-bit or 64-bit version of the operating system per certification. The 64-bit version of the database can only be run on the 64-bit version of the operating system.


Note:

The 32-bit version of the patch set must only be installed on the 32-bit version of the database, regardless of whether the operating system is 32-bit or 64-bit. The 64-bit version of the patch set must only be installed on the 64-bit version of the database which runs on the 64-bit operating system.

Patch sets include the Oracle Universal Installer release 10.1.0.2. You must use this Oracle Universal Installer to install this patch set and not the one from the 9.2.0.x maintenance release media or Oracle home.

Important Oracle Universal Installer Version Requirements

This is not a complete software distribution. You must install it over an existing Oracle9i release 9.2.0.x.x server installation. Users applying this patch set must use Oracle Universal Installer release 10.1.0.2 or later to ensure their Oracle home can be patched in the future. The patch set is packaged with a fully installable version of Oracle Universal Installer release 10.1.0.2 to support this requirement.

When beginning the installation, you will be presented with a screen to select Oracle Universal Installer release 10.1.0.2 or Oracle9i 9.2.0.5.0 patch set. You should select Oracle Universal Installer first. Attempts to install the patch set without Oracle Universal Installer release 10.1.0.2 will cause an error.

Post-Release Updates

Before installing this patch set in a production environment, review the OracleMetaLink site. Oracle Support Services provides information about the status of issues discovered after this patch set is released on OracleMetaLink. The information is available in document 189908.1, ALERT: Oracle9i Release 2 (9.2) Support Status and Alerts.

OracleMetaLink is available at the following URL:

http://metalink.oracle.com

To locate the document on OracleMetaLink:

  1. Click Advanced at the top of the page.

  2. Enter the document ID in the Keywords field

  3. Select Doc ID.

  4. Click Search.

Scroll down the list of document results from the search to locate the document you need. If you are unable to access this site, then contact Oracle Support before installing this patch set in a production environment.

Patch Set Documentation

There are two documents related to this release of the Oracle9i patch set. Both of these documents are included with delivery of the patch set. You may also locate documents online at OracleMetaLink:

http://metalink.oracle.com

The patch set documents are as follows:


Oracle9i Database Server Patch Set Notes, Release 2 Patch Set 4 Version 9.2.0.5.0 for Solaris Operating Environment (SPARC 64-bit)

Oracle9i Database Server List of Bugs Fixed, Release 2 Patch Set 4 Version 9.2.0.5.0

The List of Bugs Fixed is in addition to the Patch Set Notes. It provides the following information:

Before You Install This Patch Set

Read this section before installing the patch set, to determine whether any of the considerations listed below apply to your Oracle system. If so, follow the instructions in the notes before proceeding with installation of the patch set.

This section includes the following notes:

Database Upgrade for Oracle E-Business Suite

If you are an Oracle E-Business Suite customer wishing to upgrade your Oracle E-Business Suite release 11i database server to this patch set, then you must check for the latest certification status and Interoperability Notes on OracleMetaLink. All other customers wanting to upgrade their databases directly to this patch set should read Migrating Directly to an Oracle9i Release 2 Patch Set Notes available on OracleMetaLink, document 214887.1

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 to release 9.2.0.2, release 9.2.0.3, release 9.2.0.4 or release 9.2.0.5, 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 re-collect the statistics after normal database open, if necessary.

To drop and re-create the statistics, run the following commands:

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 on applying a patch set to a current release of Oracle9i for a configuration that includes one or more physical standby databases, refer to notes available in OracleMetaLink document 187242.1. This information only applies to Oracle9i release 9.0.1 and later installations.

Standard Edition Upgrade

If you are using an Oracle9i 9.2.0 pre-configured Standard Edition database, then the database contains five components that are not supported by the Standard Edition. They are:

  • Oracle Data Mining

  • Oracle OLAP Catalog

  • Oracle OLAP Analytic Workspace

  • Oracle OLAP API

  • Spatial

The catpatch.sql script will not attempt to run the patch scripts for these components, but will set the component STATUS to "OPTION OFF" in the DBA_REGISTRY view. The original versions of the dictionary objects for the components will remain in the database.

The component dictionary objects will still be in the database, but the catpatch.sql script will not apply the patch to them.

Oracle Streams

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

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.

Java VM and XML DB Requirements

Users who have JVM (Java enabled) or JVM and XDB installed on their 9.2.0.1 databases should make sure that the init.ora parameters SHARED_POOL_SIZE and JAVA_POOL_SIZE are each 150 MB or more before running the catpatch.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.

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

Oracle Advanced Queuing

Customers running Oracle Applications release 11.5.7 or 11.5.8 with Advanced Queuing configured with multi-consumer queues may encounter corruption problem after upgrading their database to 9.2.0.x from any Oracle8i database.


Note:

Refer to note 231074.1 on OracleMetaLink for details and workaround.

Oracle Data Mining

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

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 non-zero setting of the event level will enable the old behavior.

Prior to 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, one needs to test for a scale of -127 and a non-zero precision to identify a FLOAT.

Client applications that rely on the old behavior can still work as before if the event is set but will need to be corrected prior to upgrading to the next major release of the Oracle database.

Oracle XDK

Oracle9i release 9.2.0.5 patch set contains XDK version 9.2.0.7.

XML DB

XML DB users must use XDB version 9.2.0.3 or later. Earlier versions are no longer supported.

PL/SQL Cursor Caching

Prior to release of the 9.2.0.5.0 patch set, the maximum number of cursors that could be cached for fast lookup by PL/SQL was bounded by the value of the init.ora parameter open_cursors. If you currently have open_cursors set to a high value (for example, greater than 1000), it is likely that this is 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.

Patch set 9.2.0.5.0 alleviates the issue by changing the init.ora parameter which determines the upper bound for PL/SQL cursor caching from open_cursors to session_cached_cursors.

It will not be necessary for the majority of users to modify the value of either of these parameters. If you already have session_cached_cursors set to a value greater than the open_cursors parameter, then this change will have no performance impact upon your system.

However, if you have session_cached_cursors set to zero, or set at a value significantly lower than the open_cursors parameter, and you are concerned that PL/SQL cursors need to be cached for optimal performance, then you should ensure that the session_cached_cursors parameter is increased appropriately.

This issue is bug number 3150705.

Known Issues

The issues documented in this section are problems that are known to exist in the Oracle9i Database Server. These problems are being addressed by Oracle and may be fixed in a future patch set release. Until a given known issue is corrected, follow the instructions and workarounds presented in the "Workaround" section of each known issue.

The following known issues apply to this patch set release:

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.5/gateway/lib/gateway.mk

The following is an example of a true 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.5/gateway/lib/gateway.mk

Oracle Procedural Gateway for APPC: Mandatory Configuration Parameters

The Oracle Procedural Gateway for APPC, Release 9.2.0.5.0 has an updated capability table which allows the use of ROLLBACK with a READ_ONLY gateway.

Due to a bug in some versions of the Oracle Procedural Gateway for APPC prior to Release 9.2.0.5.0, the following parameters which were intended to be optional had to be defined:

  • FDS_CLASS

  • FDS_CLASS_VERSION

  • FDS_INSTANCE

These parameters identify the gateway to the integrating kernel, which creates an entry in the HS data dictionary based upon their values. The values may be set in the bootstrap shell script or in the gateway init.ora file. The sample files shipped with the gateway set the parameters in the shell script.

Bug 3218975 was fixed in the 9.2.0.5.0 patch set. This means that with this patch set, the built-in defaults will work, and the parameters become optional, but if they are specified, then either FDS_CLASS or FDS_CLASS_VERSION (or both) must be updated after the upgrade to ­Release 2 Patch Set 4 Version 9.2.0.5.0 for the capability change to be effective. They must be updated so that concatenation of FDS_CLASS and FDS_CLASS_VERSION results in a string which the integrating kernel has not seen before. Because of the precedence in which these parameters are picked up, the gateway shell script (such as pg4hoa1.sh) must be updated to enable the integrating kernel to register the updated gateway capabilities.


Workaround:

You must manually update the value specified for FDS_CLASS_VERSION, or remove or comment out the record. If you keep the record, you should change the value— for example, by adding "1" to it, or by replacing it with the preferred value for this version, which is "92050". For example, if the record currently reads:

FDS_CLASS_VERSION=2

then you could replace it with

FDS_CLASS_VERSION=3

or

FDS_CLASS_VERSION=92050

Failure to update the record in this way will mean that the fix allowing use of ROLLBACK with a READ_ONLY gateway will not be effective.

Bug 2602782

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

Bug 3259636

If one has a version 9.2.0.4 Oracle home and uses DBCA to create a brand new database using the seed database, some of the database components will be from an older version. This is because the seed database was created prior to the patch release.


Workaround:

To workaround the problem, run the catpatch.sql script in the migration mode.

Bugs Fixed for Your Platform on Oracle9i

The following table is a cumulative list of the platform-specific bugs addressed in all Oracle9i patch sets to date:

Fixed in Release Bug Number Description
92050 3391626 LCK process terminates getting an error at SSKGXPRDTRCV using RSM/RDT
9205 3234112 bug 2954997 not fixed in 9204 on solaris 64-bit
9205 3211137 Not able to move SGABEG on a 64-bit OS
9205 3081593 network data class always zero in 64-bit version
9205 2986722 the problem of external procedure calling C shell script
9205 2872469 ORA-03113 for select on ALL_CONSTRAINTS over informix gateways link
9205 2854962 Sun: Oracle Real Application Clusters on Solaris can only support up to 4 nodes.
9204 2917199 FTP operation with SB xmltype stored as clob results in corrupt data
9204 2882059 OLAP API library built incorrectly
9204 2917199 FTP operation with SB XMLTYPE stored as CLOB results in corrupt data
9204 2805249 SGA shrink may not release memory back to the O/S on Solaris.
9203 2490128 Process class missing from OS cart
9203 2749790 SIGBUS in XSCBIXLINBYTE2SEG during dynamic aggregate
9203 2746047 Siemens bug - DLMD’s DD_TS enqueue not cleaned during RCFG
9203 2453925 AVMPING dumps core (APRAC64 bit 9.2 release)

System Requirements

The following are the system requirements for this patch set:

Patch Set Components

The following table provides a list of patch set components:

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

Special Considerations for Oracle Real Application Clusters

If you plan to install the patch on an Oracle Real Application Clusters environment, read the following sections before proceeding:

Pre-installation Considerations for Oracle Real Application Clusters

This patch set allows you to install the included patches onto multiple nodes in a cluster when the base release (9.2.0.1.0) is already installed on those nodes. The Oracle Universal Installer will detect whether the machine where you are installing is part of cluster. If it is, then you will be prompted to select the nodes from the cluster onto which you would like to install the patch set.


Note:

You must install the Oracle Universal Installer release 10.1.0.2 on all nodes in the cluster before installing patch set 9.2.0.5.0 on an Oracle Real Application Clusters environment.


Note:

It is important that the set of nodes that will have the patch set installation be 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 undesired behavior in your Oracle Real Application Clusters environment, as some nodes will be upgraded to the new software versions, while others will not.

Pre-Installation Considerations for Oracle Real Application Clusters with Sun Clusterware

The UDLM 3.3.4.6 patch must be installed before applying this patch set for Oracle Real Application Clusters environments. If the UDLM patch was applied while applying the 9.2.0.3.0 patch set, then you do not have to reapply it now. The UDLM patch is included in this patch set. The installation instructions are located in the /Disk1/racpatch/README.udlm file.

Patch Set Installation Tasks

The instructions for installing this patch set assume a minimal familiarity with Oracle Universal Installer. Oracle recommends that you create a backup of your system prior to installing the patch set.


Note:

If you attempt to install this patch set on an Oracle database prior to release 9.2.0, then a warning dialog will be displayed with the following error:
There are no patches that need to be applied from the patch set Oracle9i patch set 9.2.0.5.0.

The Oracle Universal Installer will not allow the installation to proceed. You must acknowledge the error message, and click Exit to end the installation.


The following procedure describes how to install the patch set:

  1. Log in as the oracle account and make sure the environment is set to the correct ORACLE_HOME and ORACLE_SID variables.

  2. Uncompress the downloaded patch set file into a new directory and extract the cpio files using the following commands:

    cpio -idmv < 9205_solaris64_release.cpio
    
    
  3. Shut down the existing Oracle server instance with normal or immediate priority. For example, shutdown all instances (cleanly) if running Parallel Server.

  4. Stop all listener, agent and other processes running in or against the ORACLE_HOME that will have the patch set installation.

  5. Start the Oracle Universal Installer. Use the Oracle Universal Installer release 10.1.0.2 runInstaller script located in the untarred area of the patch set, such as /Disk1/runInstaller.


    Note:

    If you are installing the patch set on an Oracle Real Application Clusters environment, then you must install the Oracle Universal Installer release 10.1.0.2 on all nodes on the cluster before installing the patch set.

  6. Install the patch set through either an interactive or a silent installation.

    To perform an interactive installation using the Oracle Universal Installer graphical interface:

    1. Start the Oracle Universal Installer from one of the directories that is appropriate on your installation using the following command:

       % ./runInstaller
      
      
    2. Click Next on the Welcome screen. This will display the File Locations screen.


      Note:

      If you are installing the patch set in a cluster environment, then the Cluster Node Selection screen will appear after clicking Next. After selecting the node, click Next. The File Locations screen will appear.

    3. Click Browse for the Source... entry field.

    4. Navigate to the stage directory where you unpacked the patch set tar file.

    5. Select the products.xml file.

    6. Click Next. The Available Products window will appear. The products file will be read and the installer will load the product definitions. The products to be loaded will be displayed.


      Note:

      If Oracle Universal Installer release 10.1.0.2 has not been installed, then install that first. If the Oracle Universal Installer has been installed, then proceed with installation of the 9.2.0.5.0 patch set.

    7. Verify the products listed in the display.

    8. Click Install.

    9. Run the $ORACLE_HOME/root.sh script from a root session when prompted by the installer. If you are applying the patch set in a cluster database environment, then the root.sh script should be run in the same way on both the local node and participating nodes.

    10. Click OK on the installer prompt window. Once the installation has completed successfully, it will display End of Installation.

    11. Click Exit, and confirm to exit the Oracle Universal Installer.

    To perform a silent installation requiring no user intervention:

    1. Copy the response file template provided in the response directory where you unpacked the patch set tar file.

    2. Edit the values for all fields labeled as <Value Required> according to the comments and examples in the template.

    3. Start the Oracle Universal Installer from the directory described in Step 4 which applies to your situation. You should pass the full path of the response file template you have edited locally as the last argument with your own value of ORACLE_HOME and FROM_LOCATION. The following is an example of the command:

      % ./runInstaller -silent -responseFile full_path_to_your_response_file
      
      
    4. Run the $ORACLE_HOME/root.sh script from a root session. If you are applying the patch set in a cluster database environment, the root.sh script should be run in the same way on both the local node and all participating nodes.

Post-Installation Procedures

Perform the post-installation tasks only if you have one or more databases associated to the upgraded $ORACLE_HOME.

Special Considerations

The following are considerations to be aware of before performing the post-installation tasks. Read through the list to determine whether you must take any action before performing the post-installation tasks:

  • Users who have JVM (Java enabled) or JVM and XDB installed on their Oracle9i release 2 databases should ensure the init.ora parameters SHARED_POOL_SIZE and JAVA_POOL_SIZE are each 150 MB or more before running the catpatch.sql upgrade script. Failure to do so could result in an unrecoverable memory failure during 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 database without them.

  • If JServer was installed in the database, then check to be sure there is at least 10MB of free space in the SYSTEM table space before running the post-installation tasks.

  • If applying this patch set to a cluster database, then set the CLUSTER_DATABASE initialization parameter to FALSE. After the post-installation tasks are completed, set this initialization parameter back to TRUE.

Post-Installation Tasks


Upgrading Databases from Prior Releases Directly to Oracle9i Version 9.2.0.5

The instructions for upgrading your Oracle database versions 7.3.4, 8.0.6, 8.1.7 and 9.0.1 directly to this version of the patch set can be found in Oracle9i Database Migration Release 2 (9.2) (Part Number A96530-0x). Once the installation of the patch set is complete, your databases can be upgraded using the mig utility (for Oracle Database version 7.3.4) and the installed upgrade scripts in the 9.2.0.5 ORACLE_HOME (u0703040.sql, u0800060.sql, u0801070.sql or u0900010.sql), as described in the Oracle9i Database Migration Release 2 (9.2) document.


Upgrading Existing 9.2.0.x.x Databases to the 9.2.0.5.0 Patch Set

The following describes post-installation tasks related to the 9.2.0.5.0 patch set. These tasks should be run on all updated databases. If you are using the Oracle OLAP option, then ensure that the database listener is up.

Oracle Application Server 10g (9.0.4) customers who use patch set 9.2.0.5.0 need perform steps 1 through 3 only.

  1. Start the database listener using a command such as lsnrctl start.

  2. Log in as sysdba using SQL*Plus.

  3. Run the following commands and scripts in order from ORACLE_HOME in migrate mode on all updated databases.

    1. Run the startup migrate command.


      Note:

      If you are running Oracle Real Application Clusters, then set cluster_database in the initSID.ora file to FALSE prior to starting in migrate mode.

    2. Run the spool patch.log command.

    3. Run the @?/rdbms/admin/catpatch.sql script.

    4. Run the @?/rdbms/admin/catcio.sql script (This is for Bug 3531336).

    5. Run the spool off command.

    6. Review the patch.log file for errors, and rerun the catpatch.sql script after correcting any problems.

    7. Run the shutdown command.

    8. Run the startup command.

    9. Run the @?/rdbms/admin/utlrp.sql script. This step is optional, and will recompile all invalid PL/SQL packages now instead of when the packages are accessed the first time. The utlrcmp.sql script can be used to parallelize this in multiprocessor machines.

  4. Perform the following shell scripts only if Oracle Internet Directory version 9.2.0.x.x was installed in the ORACLE_HOME. Ensure the database and database listener are running, and all parameters for the oidpatchca.sh script are specified prior to running the script:

    $ORACLE_HOME/bin/oidpatchca.sh 
    -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 
    
    

    In the preceding commands, Password to register DIP Server must conform to the password policy in the Oracle Internet Directory server.

  5. Perform the following steps only if using the Oracle Recovery Manager catalog:

    rman catalog <user/passwd@alias> 
    upgrade catalog; 
    upgrade catalog; 
    

Patch Set Re-Installation

The patch set can be re-installed if the Oracle home has been corrupted, and you want to restore the updated Oracle home.

The following describes how to re-install the patch set:

  1. Make sure to perform the same set of pre-installation tasks that you performed when you installed the patch set initially:

    1. Log in as the oracle account and make sure the environment is set to the correct ORACLE_HOME and ORACLE_SID.

    2. Uncompress and untar the downloaded patch set file into a new directory.

    3. Shut down the existing Oracle server instance with normal or immediate priority. For example, shut down all instances (cleanly) if running Real Application Clusters.

    4. Stop all listener, agent and other processes running in or against the ORACLE_HOME that will have the patch set installation.

  2. Start the Oracle Universal Installer in the same manner that you did when you installed the patch set initially. You may only re-install a patch set by running the Oracle Universal Installer in interactive mode.

  3. Perform the following tasks using the Oracle Universal Installer release 10.1.0.2:

    1. Click Next on the Welcome screen. This will display the File Locations screen.

    2. Click Browse for the Source... entry field and navigate to the stage directory where you unpacked the patch set tar file.

    3. Select the products.xml file.

    4. Click Next. The products file will be read and the Oracle Universal Installer will load the product definitions. The Oracle Universal Installer will display the Available Product Component screen. This screen contains a listing of all components that have been patched by the original patch set installation. These components will be grayed out, indicating they cannot be selected for installation.

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

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

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

    8. Click Next. The patches to be re-installed will be displayed.

    9. Verify the list of patches to be re-installed.

    10. Click Install. Once the installation is completed successfully, it will display End of Installation.

    11. Click Exit, and confirm to exit the Oracle Universal Installer.

De-Installation of the Patch Set

There is no mechanism provided for de-installing patch sets. If you are concerned about being able to de-install a patch set, Oracle recommends that you back up your software installation before applying the patch set.

If you must de-install a patch set, Oracle recommends one of the following procedures (in order of preference):

Regardless of how you de-install a patch set, please contact Oracle Support Services to verify that the problem you are encountering is being addressed.

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. 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 additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation

JAWS, a Windows screen reader, 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, JAWS 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.