Oracle9i Patch Set Notes
Release 2 (9.2.0.6) Patch Set 5 for Linux x86-64
 

 

Oracle9i

Patch Set Notes

Release 2 (9.2.0.6) Patch Set 5 for Linux x86-64

Octoberber 2005

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

This document contains the following sections:

This document may be updated after release. To check for updates to this document, see document 263719.1 on the OracleMetalink Web site:

http://metalink.oracle.com/

To locate document 263719.1:

  1. Log on to OracleMetalink.

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

  3. Enter 263719.1 in the Document ID field, then click Submit.

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.

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 Preinstallation Tasks

Complete the following preinstallation tasks before installing the patch set:

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.

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 read Upgrading Directly to a 9.2.0 Patch Set available on OracleMetalink from document 214887.1.

5.1.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, the catpatch.sql script can take a long time if there are statistics for the SYS schema. Delete the statistics on all of 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:

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

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

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

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 Oracle MetaLink 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

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.

5.1.7 Oracle Text INSO Updates

Oracle Text uses the INSO filter during the indexing of binary documents. This filtering technology is based on the 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 OracleMetaLink note 212584.1.

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

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.6) patch set contains XDK release 9.2.0.8.

5.1.11 XML DB

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

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

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


Note:

You must install this patch set on the same set of nodes that the base release was installed on.

5.3 RAC Only: Configure the hangcheck-timer Kernel Module


Note:

If you have already configured the hangcheck-timer module, for example, if you applied a previous Oracle9i release 2 patch set or installed Oracle9i release 9.2.0.4, you do not need to complete this task.

Starting with release 9.2.0.2, the hangcheck-timer module replaces the watchdog daemon (watchdogd) for RAC installations. The hangcheck-timer module is not required, however Oracle recommends that you use it. The following sections describe the hangcheck-timer module and describe how to configure it.

5.3.1 hangcheck-timer Module

The hangcheck-timer module monitors the Linux kernel for long operating system hangs that could affect the reliability of an RAC node and cause corruption of an RAC database. If the operating system hangs, then the hangcheck-timer module will reboot the node. This approach has the following advantages:

  • Node reboots are triggered from within the Linux kernel, making them less affected by system load.

  • The Oracle Cluster Manager on an RAC node can be stopped and reconfigured because its operation is completely independent of the kernel module.

  • The features in the hangcheck-timer module closely resemble features found in the implementation of Oracle Cluster Manager for RAC on the Microsoft Windows platform, on which Oracle Cluster Manager for Linux x86 was based.

The deprecation and removal of the watchdog daemon requires several parameter changes in the $ORACLE_HOME/oracm/admin/cmcfg.ora file used to configure Oracle Cluster Manager. The changes are as follows:

  • The following parameters in the cmcfg.ora file are no longer valid:

    • WatchdogTimerMargin

    • WatchdogSafetyMargin

    These parameters should be removed from the cmcfg.ora file on all nodes in the cluster.

  • The following configuration parameter has been added to allow the Oracle Cluster Manager to know the name of the hangcheck-timer module so it can be loaded correctly:

    • KernelModuleName

    If the module in the KernelModuleName is correctly specified but not loaded, or is incorrectly specified, then the Oracle Cluster Manager will produce a series of error messages in the system log (/var/log/messages). It will not prevent the process from running. The module must be loaded before you start Oracle Cluster Manager.

  • The CMDiskFile parameter has been changed from optional to mandatory. This ensures a cluster manager quorum partition is used and allows the Oracle Cluster Manager to reliably handle certain hardware and software errors that affect cluster participation.

  • The following configuration parameters have been added to be used when the module is loaded:

    • hangcheck_tick

      This parameter is the interval indicating how often the hangcheck-timer checks on the health of the system.

    • hangcheck_margin

      This parameter sets the margin of error to prevent unnecessary system resets due to certain kernel activities that may randomly introduce delays in the operation of hangcheck-timer.

    Together, these two parameters indicate how long an RAC node must hang before the hangcheck-timer module reboots the system. A node reboot occurs when the system hang time is greater than the sum of the times set in the hangcheck_tick and hangcheck_margin parameters.

5.3.2 Recommended hangcheck-timer Configuration Defaults

The following are the recommended default configuration settings for the hangcheck-timer module. These are in addition to the recommendations for parameters in the RAC documentation.

Parameter Service Setting
hangcheck_tick hangcheck-timer 30 seconds
hangcheck_margin hangcheck-timer 180 seconds
KernelModuleName oracm hangcheck-timer
MissCount oracm hangcheck_tick + hancheck_margin (such as 210 second)

5.3.3 Configure the hangcheck-timer Module

To configure the hangcheck-timer module:

  1. On Red Hat Enterprise Linux 2.1 or SUSE Linux Enterprise Server 8, enter the following command to determine the version of the kernel:

    $ uname -r
    
    

    Note:

    The hangcheck-timer module is available by default with all Red Hat Enterprise Linux 3 and SUSE Linux Enterprise Server 9 installations.

  2. Remove or disable the mechanism that loads the softdog module at system start up, if that module is not used by other software on the node. This is necessary for subsequent steps in the installation process. This step may require log in as the root user.

    One method for setting up previous releases of RAC involved loading the softdog module in the /etc/rc.local file on Red Hat systems or the /etc/init.d/boot.local file on SUSE systems. If this method was used, then remove or comment out the following line in the file:

    /sbin/insmod softdog nowayout=0 soft_noboot=1 soft_margin=60 
    
    

    If this method was not used, then check with the system administrator to determine where and how the softdog module is loaded and used. The softdog module is no longer needed in this release of Oracle Cluster Manager.

  3. Remove or disable the mechanism to start the Oracle watchdogd module at system start up. This action is necessary for the subsequent steps in the installation process.

    Check with the system administrator to determine where and how the watchdog daemon is started. If watchdogd is started using an rc script that starts Oracle or Oracle Cluster Manager, then remove or comment out the watchdogd start up in the script. If the watchdog daemon is started by a separate rc script, then ensure the references to this script are removed from the runlevel script directories.

  4. Append the following line to the /etc/rc.local file (Red Hat) or /etc/init.d/boot.local file (SUSE 8):

    /sbin/insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 
    
    

    For SUSE 9, append the following line to the /etc/init.d/boot.local file:

    /sbin/insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 hangcheck_reboot=1
    
    
  5. For Red Hat and SUSE 8, load the hangcheck-timer kernel module using the following command as root user:

    # /sbin/insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 
    
    

    For SUSE 9, load the hangcheck-timer kernel module using the following command as root user:

    # /sbin/insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 hangcheck_reboot=1
    
    
  6. Repeat steps 1 through 5 on all RAC nodes where the kernel module must be installed.

  7. Shut down all Oracle services on all RAC nodes, including the following:

    • All Oracle databases using the SQL*Plus commands SHUTDOWN IMMEDIATE and SQL*Plus or SRVCTL.

    • Global Services Daemon using the gsdctl stop command.

    • All running Oracle listeners using the lsnrctl stop command.

    • Oracle Intelligent Agent using the agentctl stop command.

    • Oracle Cluster Manager using the kill or killall command.

    • Oracle watchdogd using the kill or killall command.

      The kill and killall commands imply a full cluster restart because every node will restart when the commands are run if watchdogd is enabled. If one or more nodes restart, then ensure that none of the preceding services are running when the nodes come back up. Shut down any services that start after the restart.

  8. Ensure that the hangcheck-timer module is loaded by running the following command as the root user:

    # /sbin/lsmod | grep hangcheck-timer
    
    

    If the kernel module is not loaded, then load it manually, and check the following line in the /etc/rc.local file (Red Hat) or /etc/init.d/boot.local file (SUSE):

    /sbin/insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 
    
    

    Append the line to the appropriate file if necessary.

5.4 RAC Only: Install the Oracle Cluster Manager 9.2.0.6 Patch

Follow the steps in this section to install the Oracle Cluster Manager release 9.2.0.6 patch from a single node of the cluster.


Note:

You must install the Oracle Cluster Manager patch and configure Oracle Cluster Manager before you install the Oracle9i release 2 Database patch set.

Only one instance of Oracle Cluster Manager can run per node. If the system has multiple Oracle home directories, then make sure to apply the patch to the Oracle home directory where Oracle Cluster Manager is installed.


To install the Oracle Cluster Manager release 9.2.0.6 patch:

  1. Log in to an RAC node as the oracle user.

  2. If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY
      
      
    • C shell:

      % setenv DISPLAY local_host:0.0
      
      

    In this example, local_host is the host name or IP address of the system that you want to use to display the Installer (your workstation or PC).

  3. Ensure that the ORACLE_HOME environment variable is set correctly.

  4. Change directory to the Disk1 directory where you unpacked the patch set file.

  5. Start the Installer as follows:


    Note:

    Make sure that you run the Installer from the Disk1/oracm directory, and not from the Disk1 directory.

    $ ./oracm/runInstaller
    
    

    The Welcome screen appears.

  6. Click Next.

    The Specify File Locations screen appears.

  7. Specify the Oracle home name and path, then click Next.

    The Select a Product to Install screen appears.

  8. Select Oracle Cluster Manager 9.2.0.6, then click Next.

    The Public Node Information screen appears.

  9. Enter the public node names for each RAC node, then click Next.

    The Private Node Information screen appears.

  10. Enter the private node names in the same order that you entered the corresponding public node names on the Public Node Information screen, then click Next.

  11. When prompted, run the orainstRoot.sh script as root on all cluster nodes.

    The Summary screen appears.

  12. Verify the information displayed, then click Install.

    The Oracle Cluster Manager patch is installed on all RAC nodes. After the software has been installed, the End of Installation screen appears.

  13. Enter the following commands where oracle_home is the Oracle home where you installed Oracle Universal Installer 10.1.0.3:

    $ cd oracle_home/oui/bin
    $ ./runInstaller -updateNodeList -noClusterEnabled -local ORACLE_HOME=$ORACLE_HOME CLUSTER_NODES=node1,node2,node3
    
    
  14. Click Exit, then click Yes to exit from the Installer.

5.5 RAC Only: Configure Oracle Cluster Manager to Use the hangcheck-timer Module


Note:

If you have already configured Oracle Cluster Manager to use the hangcheck-timer module, for example, if you applied a previous patch set or installed Oracle9i release 9.2.0.4, you do not need to complete this task.

Configure Oracle Cluster Manager to use the hangcheck-timer module on all cluster nodes as follows:

  1. Make any necessary changes to the $ORACLE_HOME/oracm/admin/cmcfg.ora file. The changes include the following:

    • Remove any lines containing WatchdogSafetyMargin and WatchdogTimerMargin.

    • Adjust the value of the MissCount line based on the sum of the hangcheck_tick and hangcheck_margin values. The default value is 210.

    • Verify that a valid CmDiskFile line exists in the following format:

      CmDiskFile=file_or_raw_device_name
      
      

      In the preceding example, the file or raw device must be valid. If you specify the name of a file that does not exist, then the file is created if the base directory exists. If you specify a raw device, then that raw device must exist and have the correct ownership and permissions.

    • Add the following KernelModuleName line:

      KernelModuleName=hangcheck-timer
      
      
  2. Modify the ocmstartup.sh and ocmargs.ora scripts to remove any watchdogd information, if they are used for start up.

    • Remove the words watchdogd and from the line Sample startup script for watchdogd and oracm in the $ORACLE_HOME/oracm/bin/ocmstart.sh script.

    • Remove all lines that contain watchdogd, both uppercase and lowercase, from the rest of the $ORACLE_HOME/oracm/bin/ocmstart.sh script.

    • Remove the first line that contains watchdogd from the $ORACLE_HOME/oracm/admin/ocmargs.ora script.

  3. Perform the following step if you are using a cluster file system (CFS) for the Quorum disk.

    1. Log in as the root user.

    2. Run the following command:

      # dd if=/dev/zero of=quorum_disk_file bs=4096 count=65
      
      

      In this command, the CmDiskFile parameter in the $ORACLE_HOME/oracm/admin/cmcfg.ora file lists the file name used for the quorum_disk_file.

  4. Restart Oracle Cluster Manager on all RAC nodes.

  5. Make sure that Oracle Cluster Manager is running, and that the watchdog daemon process (watchdogd) is not running on all nodes before applying the database patch set.

5.6 SQL*Plus

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

5.7 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, view the file.

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.

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

5.9 Download and Extract the Installation Software

To download and extract the patch set installation software:

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

    $ unzip p3948480_9206__AMD.zip
    
    

5.10 Set the ORACLE_HOME and ORACLE_SID Environment Variables

Enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables:

  • Bourne, Bash, or Korn shell:

    $ ORACLE_HOME=oracle_home
    $ ORACLE_SID=sid
    $ export ORACLE_HOME ORACLE_SID
    
    
  • C shell:

    % setenv ORACLE_HOME oracle_home
    % setenv ORACLE_SID sid
    
    

In these examples, oracle_home is the Oracle home directory where the Oracle9i installation that you want to upgrade is installed, and sid is the SID of the database that you want to upgrade.

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

5.12 Stop All Processes

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

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

5.14 Install Oracle Universal Installer Release 10.1.0.3

Install Oracle Universal Installer release 10.1.0.3:

  1. Log in as the Oracle software owner (typically oracle).

  2. If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY
      
      
    • C shell:

      % setenv DISPLAY local_host:0.0
      
      

    In this example, local_host is the host name or IP address of the system that you want to use to display the Installer (your workstation or PC).

  3. Enter the following commands to start the Installer, where patchset_directory is the directory where you unzipped the patch set software:

    $ cd patchset_directory/Disk1
    $ ./runInstaller
    
    
  4. On the Welcome screen, click Next.

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

    The Products to Install screen appears.

  6. Select Universal Installer 10.1.0.3, then click Next.

  7. On the Summary screen, click Install.

    This screen lists all of the patches available for installation.

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

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:

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 in as the Oracle software owner (typically oracle).

  2. If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY
      
      
    • C shell:

      % setenv DISPLAY local_host:0.0
      
      

    In this example, local_host is the host name or IP address of the system that you want to use to display the Installer (your workstation or PC).

  3. For RAC installations, enter the following commands where oracle_home is the Oracle home where you installed Oracle Universal Installer 10.1.0.3:

    $  cd oracle_home/oui/bin
    $ ./runInstaller -updateNodeList -noClusterEnabled -local  ORACLE_HOME=$ORACLE_HOME CLUSTER_NODES=node1,node2,node3
    
    
  4. Enter following commands to start the Installer where patchset_directory is the directory where you unzipped the patch set software:

    $ patchset_directory/Disk1
    $ ./runInstaller
    
    
  5. On the Welcome screen, click Next.

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

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

    patchset_directory/Disk1/stage/products.xml
    
    
  8. 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.

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

  10. 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 the Installer, exit the Installer and install the patch set software from the first node in the list of nodes.

  11. On the Summary screen, click Install.

    This screen lists all of the patches available for installation.

  12. When prompted, 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.

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

Installing the Patch Set Noninteractively

To install the Oracle9i patch set noninteractively:

  1. Log in as the Oracle software owner (typically oracle).

  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.

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

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.

7.1 Upgrading Databases from Previous Releases Directly to Oracle9i Release 2 (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.


See Also:

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

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

7.2.1 Check Tablespace Sizes and Set Parameter Values

Review the following sections before upgrading a database.

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

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

7.2.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 in as the Oracle software owner (typically oracle).

  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 log in to the database as the SYS user with SYSDBA privileges:

    $ sqlplus /nolog 
    SQL> CONNECT / 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 log in to the database as the SYS user with SYSDBA privileges:

      $ sqlplus /nolog 
      SQL> CONNECT / 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 log in to the database as the SYS user with SYSDBA privileges:

      $ sqlplus /nolog
      SQL> CONNECT / AS SYSDBA 
      
      
  6. Enter the following SQL*Plus commands:

    SQL> STARTUP MIGRATE
    SQL> SPOOL patch.log
    SQL> @?/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> @?/rdbms/admin/utlrp.sql
    
    
  11. If you will use Oracle OLAP, enter the following commands:

    SQL> ALTER USER OLAPSYS IDENTIFIED BY password ACCOUNT UNLOCK;
    SQL> CONNECT OLAPSYS/password
    SQL> @cwmlite/admin/postamd.sql
    
    
  12. 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
      
      
  13. If you are using the Oracle Recovery Manager catalog, enter the following command:

    $ rman catalog username/password@alias 
    RMAN> UPGRADE CATALOG; 
    
    
  14. If Oracle Internet Directory release 9.2.0 is installed in the Oracle home, run the following shell script:


    Note:

    Make sure that the database and database listener are running, and all parameters for the oidpatchca.sh script are specified before 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 example, Password_to_register_DIP_Server must conform to the password policy in the Oracle Internet Directory server.

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

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. Log in as the Oracle software owner (typically oracle).

  2. If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY
      
      
    • C shell:

      % setenv DISPLAY local_host:0.0
      
      

    In this example, local_host is the host name or IP address of the system that you want to use to display the Installer (your workstation or PC).

  3. Enter the following commands to start the Oracle Universal Installer, where patchset_directory is the directory where you unzipped the patch set software:

    $ cd patchset_directory/Disk1
    $ ./runInstaller
    
    
  4. If you are installing the patch on an RAC cluster, click Next on the Selected Nodes screen.

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

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

    patchset_directory/Disk1/stage/products.xml
    
    
  7. 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.

  8. Expand the nodes for each component listed in the tree to display the patch that corresponds to each component.

  9. Select the patches that you want to install.

    When you select a patch, the Install Status column changes to "reinstall."

  10. Repeat the process for each patch bundled in the patch set, then click Next.

  11. On the Summary screen, verify the list of patches to be reinstalled, then click Install.

  12. On the End of Installation screen, click Exit, then click Yes to exit from the 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:

10.1 Running XDK Demonstrations

Before running the XDK demonstrations, make sure that the patch for bug 3821678 is installed.

10.2 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

10.3 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

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

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

11 Fixed Platform-Specific Bugs

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


Note:

You may or may not receive platform-specific bugs.

12 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
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 Names 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
Oracle9i Real Application Clusters Guard 9.2.0.6
Oracle Text 9.2.0.6
Oracle Transparent Gateway for Informix 9.2.0.6
Oracle Transparent Gateway for DRDA 9.2.0.6
Oracle Transparent Gateway for INGRES II 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
Pro*FORTRAN 1.8.77.6.0
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

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.


Oracle Database Patch Set Release Notes, Release 2 (9.2.0.6) Patch Set 5 Linux x86-64

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.