Oracle® Database Patch Set Notes
10g Release 2 (10.2.0.3) Patch Set 2 for Linux x86-64
 

 

Oracle® Database

Patch Set Notes

10g Release 2 (10.2.0.3) Patch Set 2 for Linux x86-64

 

February 2007

These patch set notes accompany the Oracle Database release 10.2.0.3 patch set. This document contains the following sections:

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

http://metalink.oracle.com

To locate document 316900.1:

  1. Log on to OracleMetalink.

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

  3. Enter 316900.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 the patch set includes only low impact patches, it does not require you to certify applications or tools against the server.

You can apply the Oracle Database release 10.2.0.3 patch set to the following Oracle Database 10g release 2 installations:

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

2 Oracle Universal Installer Version Requirements

This patch set includes Oracle Universal Installer release 10.2.0.3, which is also installed when you install this patch set. This is to ensure that your Oracle home can be patched in the future. You should not use Oracle Universal Installer from the earlier maintenance release media or Oracle home.

This is not a complete software distribution. You must install it in an existing Oracle Database 10g (10.2.0.x) installation.

3 Patch Set Documentation

There are two documents related to this release of the Oracle Database patch set:

Both of these documents are included with the patch set. In addition, they are available from document 316900.1, ALERT: Oracle 10g release 2 (10.2) Support Status and Alerts on the OracleMetalink Web site:

http://metalink.oracle.com

To locate document 316900.1:

  1. Log on to OracleMetalink.

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

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

The following sections describe the contents of the Oracle Database Patch Set Notes and the Oracle Database List of Bugs Fixed.

Oracle Database Patch Set Notes, 10g Release 2 (10.2.0.3) Patch Set 2 for Linux x86-64

This document provides:

Oracle Database List of Bugs Fixed, 10g Release 2 (10.2.0.3) Patch Set 2

The List of Bugs Fixed is a list of all generic bugs related to Oracle Database that have been fixed to date.

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 Upgrading Oracle E-Business Suite Databases

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:

http://metalink.oracle.com

5.1.2 Upgrading Installations that use Physical or Logical Standby Databases

Before applying this patch set to an Oracle Database 10.2.0.x installation that uses one or more physical or logical standby databases, review the following OracleMetalink documents:

  • For information about physical standby databases, review document 278641.1.

  • For information about logical standby databases, review document 278643.1.

These documents are available on the OracleMetaLink Web site:

http://metalink.oracle.com

5.1.3 Upgrading Installations that use Java Virtual Machine or Oracle interMedia

If any of the databases use Java Virtual Machine or Oracle interMedia, then install the Oracle Database 10g Products installation type from the Oracle Database 10g Companion CD before installing the 10.2.0.3 patch set. For information about installing the Oracle Database 10g Products installation type from the Companion CD, see the Oracle Database Companion CD Installation Guide for your platform. This installation type includes the Natively Compiled Java Library files to improve Java performance. If you do not install the Natively Compiled Java Library files, the ORA-29558:JAccelerator(NCOMP)not installed error occurs when a database that uses Java Virtual Machine is upgraded to the patch release.

5.1.4 Upgrading Oracle Clusterware

The Oracle Clusterware software must be at the same or newer level as the Oracle software in the Oracle RAC Oracle home. Therefore, you should always upgrade Oracle Clusterware before you upgrade Oracle RAC.

5.1.5 Notes to Oracle OLAP users

To apply this patch set, Oracle OLAP users should ensure that the base release is the Enterprise Edition of 10.2.0.x with the Oracle OLAP option installed. Oracle highly recommends the Data Warehouse configuration type to optimize the database for Oracle OLAP.

Oracle OLAP users upgrading the Oracle Database to 10.2.0.3.0 must upgrade the Analytic Workspace Manager client as well. This new 10.2.0.3.0 Analytic Workspace Manager can be found on Oracle Technology Network and on OracleMetaLink by referencing Oracle OLAP patch 5581559.

5.2 Identify the Oracle Database Installation

This is not a complete software distribution. You must install it in an existing Oracle Database 10g Oracle home. To identify Oracle home directories, view the /etc/oratab file.

If you are installing this patch set on an existing Oracle Real Application Cluster 10g release 10.2.0.x installation, you must run Oracle Universal Installer from the same node from which the Oracle Database software was installed.

5.3 Check Postrelease Updates

Before installing this patch set in a production environment, review document 316900.1, ALERT: Oracle 10g release 2 (10.2) Support Status and Alerts, available on the OracleMetaLink Web site:

http://metalink.oracle.com

To locate this document:

  1. Log on to OracleMetalink.

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

  3. Enter 316900.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.4 Download and Extract the Installation Software

To download and extract the patch set installation software:

  1. Download the p5337014_10203_LINUX-x86-64.zip patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory.

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

    $ unzip p5337014_10203_LINUX-x86-64.zip
    
    

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

5.5 Update Oracle Time Zone Definitions

The 10.2.0.3 patch set includes an update to the Oracle time zone definitions. The 10.2.0.3 patch set updates the standard version of the Oracle 10.2 time zone definitions version-2 to version-3. This version of the time zone definitions includes the changes to daylight saving time in the USA in 2007, and many other updates.

A list of updated time zones in version-3 of these definitions are available from document 412160.1 on the OracleMetalink Web site:

http://metalink.oracle.com

To locate document 412160.1:

  1. Log on to OracleMetalink.

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

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

Perform the following actions to ensure that time zone data affected by the changes in these time zones are updated appropriately:

  1. Download the patch 5601428 from OracleMetalink.

  2. Install the patch. The script utltzuv2.sql is installed into the $ORACLE_HOME/rdbms/admin directory.

  3. Run utltzuv2.sql to check the data of datatype TIMESTAMP WITH TIME ZONE (TSTZ). The output of this script is a results table which highlights the affected columns.

  4. Refer to the instructions in the utltzuv2.sql or OracleMetalink note 396671.1: Usage of utltzuv2.sql before updating time zone files in Oracle 10, to evaluate results and if required save the existing TSTZ data. If no data was found, no further actions are needed.


    Note:

    If you saved the existing TSTZ data, you need to complete Updating Oracle Time Zone Definitions under the Postinstallation Tasks section to view the change.

    To locate document 396671.1 on the OracleMetalink Web site:

    http://metalink.oracle.com
    
    

    To locate document 396671.1:

    1. Log on to OracleMetalink.

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

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


    Note:

    If you have previously installed a patch for bug 4689959, the database is already using version 3 of the Oracle time zone definitions. In this case, the script in step 3 will display the following message: TIMEZONE data is consistent with the latest version 3 transition rules, No need to validate TIMEZONE data. In this case, no further action is needed and step 4 can be skipped.

    If you have previously installed a patch for bug 5632264, the database is already using version 4 of the Oracle time zone definitions, which supersedes the version included in this patch set. The script in step 3 will display the following message: Your time zone upgrade needs a different script. Please contact Oracle support!. In this case, the actions from step 4 should be skipped and you should re-apply patch 5632264 on the 10.2.0.3 installation as soon as the patch set installation is completed.


5.6 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 Oracle Database 10g installation that you want to upgrade is installed, and sid is the SID of the database that you want to upgrade.

5.7 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 Oracle Database 10g installation that you want to upgrade is installed, and sid is the system identifier of the database that you want to upgrade. For Oracle RAC installations, sid is generally the sid prefix and the instance number. For example, ORCL1.

5.8 Stop All Processes

Go to the following sections based on your Oracle Database installation type:


See also:

Appendix F, "How to Stop Processes in an Existing Oracle Real Application Clusters Database, and How to Perform Oracle Clusterware Rolling Upgrades" of Oracle Database Oracle Real Application Clusters Installation Guide.

5.8.1 Stopping All Processes for a Single Instance Installation

Shut down the following Oracle Database 10g processes in the order specified before installing the patch set:

  1. Shut down all processes in the Oracle home that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:

    $ emctl stop dbconsole
    $ isqlplusctl stop
    
    

    Note:

    Before you shut down all processes that are monitored by Oracle Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage.

  2. Shut down all database instances running in the Oracle home directory, where you need to install the patch set.

  3. Shut down all listeners running in the Oracle home directory, where you need to install the patch set.

  4. If there is an Automatic Storage Management instance present, then enter the following command to set the values for the environment variables $ORACLE_HOME and $ORACLE_SID:

    • Bourne, Bash, or Korn shell:

      $ export ORACLE_SID=+ASM
      $ export ORACLE_HOME=ASM_HOME
      
      
    • C shell:

      % setenv ORACLE_SID +ASM
      % setenv ORACLE_HOME ASM_HOME
      
      

    Enter the following command to Shut down the Automatic Storage Management instance:

    $ sqlplus /NOLOG
    SQL> CONNECT SYS/SYS_password AS SYSDBA
    SQL> SHUTDOWN IMMEDIATE
    
    
  5. For Automatic Storage Management, to shut down the Oracle Cluster Synchronization Services daemon enter the following command as the root user:

    # $ORACLE_HOME/bin/crsctl stop crs
    

5.8.2 Stopping All Processes for an Oracle Clusterware Installation

This section contains the following information:

5.8.2.1 Rolling Upgrade

By default, Oracle supports rolling upgrade for Oracle Clusterware. Complete the following steps only on one node:

  1. Shut down all processes in the Oracle home on the node that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:

    $ emctl stop dbconsole
    $ isqlplusctl stop
    
    

    Note:

    Before you shut down all processes that are monitored by Oracle Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage.

  2. Shut down all services in the Oracle home on the node that might be accessing a database:

    $ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
    
    
  3. Shut down all Oracle RAC instances on the node on which you intend to perform the rolling upgrade. To shut down Oracle RAC instances on individual nodes in the database, enter the following command where db_name is the name of the database:

    $ srvctl stop instance -d db_name -i inst_name
    
    
  4. If an Automatic Storage Management instance is present, then shut down the Automatic Storage Management instance on the node on which you intend to perform the rolling upgrade. To shut down an Automatic Storage Management instance, enter the following command where node is the name of the node where the Automatic Storage Management instance is running:

    $ srvctl stop asm -n node
    
    
  5. Stop all node applications on the node on which you intend to perform the rolling upgrade. To stop node applications running on a node, log in as the root user and enter the following command, where node is the name of the node where the applications are running:

    # srvctl stop nodeapps -n node
    
    
  6. Perform the steps mentioned in Section 6.


    Note:

    The following instructions are displayed on the Oracle Universal Installer screen:

    To complete the installation of this patch set, perform the following tasks on each node:

    1. Log in as the root user and enter the following command to shut down the Oracle Clusterware:

      # CRS_home/bin/crsctl stop crs
      
      
    2. Run the root102.sh script to automatically start the Oracle Clusterware on the patched node:

      # CRS_home/install/root102.sh
      
      

  7. To upgrade the rest of the nodes, go to the next node and perform Steps 1 to 5 and then log in as the root user and perform the following steps:

    1. Enter the following command to shut down the Oracle Clusterware:

      # CRS_home/bin/crsctl stop crs
      
      
    2. Run the root102.sh script to automatically start the Oracle Clusterware on the patched node:

      # CRS_home/install/root102.sh
      
      

    Note:

    Rolling upgrade is not supported on Shared Oracle home.

5.8.2.2 Non Rolling Upgrade

For non rolling upgrade, Oracle Clusterware needs to be shut down completely.

Complete the following steps:


Note:

You must perform these steps in the order listed.

  1. Shut down all processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:

    $ emctl stop dbconsole
    $ isqlplusctl stop
    
    

    Note:

    Before you shut down all processes that are monitored by Oracle Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage.

  2. Shut down all services in the Oracle home on each node that might be accessing a database:

    $ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
    
    
  3. Shut down all Oracle RAC instances on all cluster nodes by entering the following command where db_name is the name of the database:

    $ srvctl stop database -d db_name
    
    
  4. If Automatic Storage Management instance is present, then shut down Automatic Storage Management instances on all cluster nodes by entering the following command where node is the name of the node where the Automatic Storage Management instance is running:

    $ srvctl stop asm -n node
    
    
  5. Stop all node applications on all cluster nodes by entering the following command as the root user, where node is the name of the node where the applications are running:

    # srvctl stop nodeapps -n node
    
    
  6. Shut down the Oracle Clusterware processes by entering the following command on all nodes as the root user:

    # CRS_home/bin/crsctl stop crs
    
    
  7. Complete the steps mentioned in Section 6.


    Note:

    The following instructions are displayed on the Oracle Universal Installer screen:

    To complete the installation of this patch set, perform the following tasks on each node:

    1. Log in as the root user and enter the following command to shut down the Oracle Clusterware:

      # CRS_home/bin/crsctl stop crs
      
      
    2. Run the root102.sh script to automatically start the Oracle Clusterware on the patched node:

      # CRS_home/install/root102.sh
      
      

5.8.3 Stopping All Processes for an Oracle RAC Installation

Shut down the following Oracle Database 10g processes before installing the patch set:

  1. Shut down all processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:

    $ emctl stop dbconsole
    $ isqlplusctl stop
    
    

    Note:

    Before you shut down all processes that are monitored by Oracle Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage.

  2. Shut down all services in the Oracle home on each node that might be accessing a database:

    $ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
    
    
  3. Shut down all Oracle RAC instances on the nodes, which run from the Oracle home on which you are going to apply the patch set. To shut down all Oracle RAC instances for a database, enter the following command where db_name is the name of the database:

    $ srvctl stop database -d db_name
    
    
  4. If Automatic Storage Management instance is present, then shut down all Automatic Storage Management instances on all nodes. To shut down an Automatic Storage Management instance, enter the following command where node is the name of the node where the Automatic Storage Management instance is running:

    $ srvctl stop asm -n node
    
    
  5. Stop any listeners that are running from the Oracle home that you are patching on all nodes. To stop the listener running on a node, enter the following command, where node is the name of the node where the listener is running:

    $ srvctl stop listener -n node [-l listenername]
    
    

    Note:

    Using a logical standby database, you can upgrade Oracle Database software and patch sets with almost no downtime. Using Data Guard SQL Apply, you can perform a rolling upgrade of the Oracle Database software from release 10.2.0.1 to the current patch set release. During a rolling upgrade, you can run different releases of Oracle Database on the primary and logical standby databases, while you upgrade them, one at a time, incurring minimal downtime on the primary database.


    See also:

    Chapter 11, "Using SQL Apply to Upgrade the Oracle Database" of Oracle Data Guard Concepts and Administration.

5.9 Back Up the System

Oracle recommends that you create a backup of the Oracle Database 10g installation before you install the patch set.


See also:

Oracle Database Backup and Recovery User's Guide for more information.

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:

6.1 Installing the Oracle Database 10g Patch Set Interactively

To install the Oracle Database 10g patch set interactively:


Note:

If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle Database 10g release 10.2.0.1 or 10.2.0.2 installation, Oracle Universal Installer displays a warning dialog with the following error:
OUI-10091: There are no patches that need to be applied from the patch set Oracle Database 10g Release 2 Patch Set 2
10.2.0.3

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


  1. Log in as the oracle user.

  2. If you are not installing the software on the local system then, run the following command on remote machine:

    • Bourne, Bash, or Korn shell:

      $ export DISPLAY=localhost:0.0
      
      
    • 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 Oracle Universal Installer (your workstation or PC).

    Now to enable X applications, run the following command on the machine that you want to use to display Oracle Universal Installer (your workstation or PC):

    $ xhost + [fully_qualified_remote_host_name]
    
    
  3. Enter the following commands to start Oracle Universal Installer, where patchset_directory is the directory where you unpacked the patch set software:

    % cd patchset_directory/Disk1
    % ./runInstaller
    
    

    Note:

    If you are installing Oracle Database 10g on SUSE Linux Enterprise Server 10, the current version of Oracle Universal Installer does not recognize it as a supported operating system and the installation does not complete.

    Run Oracle Universal Installer using the ignoreSysPrereqs flag, which will skip the operating system check and continue with the installation:

    ./runinstaller -ignoreSysPrereqs
    
    

  4. On the Welcome screen, click Next.

  5. In the Specify Home Details screen, select the name of the Oracle home that you want to update, or select the Path that you want to update from the list, then click Next.

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

  7. On the Summary screen, click Install.

    This screen lists all of the patches available for installation.

  8. When prompted, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an Oracle RAC installation, then run the root.sh script on each node of the cluster.


    Note:

    If you are applying this patch set to an Oracle Clusterware installation, then complete all of the steps displayed on the Oracle Universal Installer screen.

    The Oracle Clusterware installation instructions displayed on the Oracle Universal Installer screen are also available in the CRS_home/install/readme.txt file.

    • When applying this patch set on an Oracle Clusterware home, Oracle Universal Installer prompts you to run the root102.sh script from $ORACLE_HOME/install. You must run this script as the root user on all nodes.

    • Before you add a new node, ensure that you run rootpre.sh script as the root user on the new node.


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

6.2 Installing the Oracle Database 10g Patch Set Noninteractively

To install the Oracle Database 10g patch set noninteractively:

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

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


    Note:

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

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

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


    Note:

    If you are applying this patch set to an Oracle Clusterware installation, then complete all the steps in the CRS_home/install/readme.txt file. You must run this script as the root user on all nodes.

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 Earlier Oracle Database to Oracle Database 10g Release 2 (10.2.0.3)

Review the following sections before upgrading an earlier Database to Oracle Database 10g release 2 (10.2.0.3):

7.1.1 Upgrading Earlier Oracle Database Releases to Oracle Database 10g Release 2 (10.2.0.3)

For information about upgrading Oracle Databases from an earlier Oracle Database (Oracle8i, Oracle9i, or Oracle Database 10g), see Oracle Database Upgrade Guide.

If you are upgrading an Oracle RAC database, refer to the Oracle Real Application Clusters Administration Guide as well.

7.1.2 Upgrading a Release 9.2 Database Not Using Oracle Label Security

If you want to upgrade an Oracle9i release 9.2 preconfigured database, and you are not using Oracle Label Security, complete the following steps to avoid errors during the upgrade:

  1. Use Oracle Universal Installer release 9.2 to install Oracle Label Security using the Custom installation type.

  2. Run the $ORACLE_HOME/rdbms/admin/catnools.sql script with the SYSDBA privilege to remove Oracle Label Security components from the database.

7.2 Upgrading Oracle Database 10g Release 10.2.0.x to Oracle Database 10g Release 10.2.0.3

See one of the following sections for upgrading an Oracle Database 10g release 10.2.0.x to Oracle Database 10g release 10.2.0.3:

7.2.1 Upgrading a Release 10.2 Database using Oracle Database Upgrade Assistant

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


Note:

If you do not run the Oracle Database Upgrade Assistant as described in this section, then the following errors are displayed:

ORA-01092: ORACLE instance terminated.

ORA-39700: database must be opened with UPGRADE option.


  1. Log in as the Oracle software owner user.

  2. Set the values for the environment variables $ORACLE_HOME, $ORACLE_SID and $PATH.

  3. For single-instance installations, if you are using Automatic Storage Management, start the Automatic Storage Management instance.

  4. For Oracle single-instance installations, start the listener as follows:

    $ lsnrctl start
    
    
  5. Run Oracle Database Upgrade Assistant either in the interactive or noninteractive mode:

    Interactive mode:

    Enter the following command from the command prompt:

    $ dbua
    
    

    Complete the following steps displayed in the Oracle Database Upgrade Assistant screen:

    1. On the Welcome screen, click Next.

    2. On the Databases screen, select the name of the Oracle Database that you want to update, then click Next.


      Note:

      For Oracle RAC, enter the SYS password to do the upgrade.

    3. On the Recompile invalid objects screen, select the Recompile the invalid objects at the end of upgrade option, then click Next.

    4. If you have not taken the back up of the database earlier, on the Backup screen, select the I would like to take this tool to backup the database option, mention the Path, then click Next.

    5. On the Summary screen, check the summary, then click Finish.

    6. On the End of upgradation screen, click Exit, then click Yes to exit from Oracle Database Upgrade Assistant.

    Noninteractive mode:

    Enter the following command to upgrade Oracle Database using Oracle Database Upgrade Assistant in noninteractive mode:

    $ dbua -silent -dbname $ORACLE_SID -oracleHome 
    $ORACLE_HOME -sysDBAUserName UserName -sysDBAPassword SYS_password 
    -recompile_invalid_objects true
    
    
  6. If you are using the Oracle Recovery Manager catalog, enter the following command:

    $ rman catalog username/password@alias
    RMAN> UPGRADE CATALOG;
    
    
  7. For Oracle RAC installations, start any database services that you want to use by entering the following command:

    $ srvctl start service -d db_name -s service_name
    
    

7.2.2 Manually Upgrading a Release 10.2 Database

Complete the following sections to upgrade an Oracle Database 10g release 10.2.0.x to Oracle Database 10g release 10.2.0.3:

  1. Required Preupgrade Checks

  2. Upgrading a Release 10.2 Database

7.2.2.1 Required Preupgrade Checks

Check the SYSTEM tablespace size and set the initialization parameters.

  • Check the SYSTEM Tablespace Size

    If JServer is part of the installation, ensure that there is at least 50 MB of free space allocated to the SYSTEM tablespace or autoextend space in your SYSTEM tablespace prior to upgrading.

  • 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 listener before attempting to connect to the database:

      $ lsnrctl start 
      
      
    2. Start the database with the NOMOUNT option:

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

      SQL> SHOW PARAMETER PFILE; 
      
      

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

    4. Determine the current values of these parameters:

      SQL> SHOW PARAMETER SHARED_POOL_SIZE
      SQL> SHOW PARAMETER JAVA_POOL_SIZE
      
      
    5. If the system is using a server parameter file:

      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; 
      
      

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

      SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile; 
      
      
    6. If the system uses an initialization parameter file, if necessary change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).

    7. If you use Automatic Shared Memory Management, ensure that the value of the SGA_TARGET initialization parameter size is at least 50 MB greater than the sum of the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters.


      Note:

      The value of the SGA_TARGET parameter depends on the environment. If you receive a system error when you restart the database, increase the value of the SGA_TARGET parameter to the value specified in the error.

    8. Shut down the database:

      SQL> SHUTDOWN
      
      
7.2.2.2 Upgrading a Release 10.2 Database

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


Note:

If you do not run the catupgrd.sql script as described in this section and you start up a database for normal operation, then ORA-01092: ORACLE instance terminated. Disconnection forced errors will occur and the error ORA-39700: database must be opened with UPGRADE option will be in the alert log.

  1. Log in as the Oracle software owner user.

  2. For Oracle RAC installations, start listener on each node of the cluster as follows:

    $ srvctl start listener -n node
    
    
  3. If you are using Automatic Storage Management, start the Automatic Storage Management instance.

  4. For single-instance installations, start the listener as follows:

    $ lsnrctl start
    
    
  5. For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

    $ sqlplus /nolog 
    SQL> CONNECT SYS/SYS_password AS SYSDBA
    
    
  6. For Oracle RAC installations:

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

      $ sqlplus /nolog 
      SQL> CONNECT SYS/SYS_password AS SYSDBA
      SQL> STARTUP NOMOUNT
      
      
    2. Set the CLUSTER_DATABASE initialization parameter to FALSE:

      SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile; 
      
      
    3. Shut down the database:

      SQL> SHUTDOWN
      
      
  7. Enter the following SQL*Plus commands:

    SQL> STARTUP UPGRADE
    SQL> SPOOL patch.log
    SQL> @?/rdbms/admin/catupgrd.sql
    SQL> SPOOL OFF
    
    
  8. Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script.

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

  9. If necessary, rerun the catupgrd.sql script after correcting any problems.

  10. Restart the database:

    SQL> SHUTDOWN
    SQL> STARTUP
    
    
  11. 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
    
    

    Note:

    When the 10.2.0.3 patch set is applied to an Oracle Database 10g Standard Edition database, there may be 42 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation.

    Ignore any messages indicating that the database contains invalid recycle bin objects similar to the following:

    BIN$4lzljWIt9gfgMFeM2hVSoA==$0
    

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

    $ rman catalog username/password@alias 
    RMAN> UPGRADE CATALOG; 
    
    
  13. For Oracle RAC installations:

    1. Set the CLUSTER_DATABASE initialization parameter to TRUE:

       SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile; 
      
      
    2. Restart the database:

      SQL> SHUTDOWN
      SQL> STARTUP
      
      
    3. Start any database services that you want to use:

      $ srvctl start service -d db_name -s service_name
      
      

7.3 Running changePerm.sh Script on an Oracle Database Server Home


Important:

Oracle recommends using the most restrictive file permissions possible for your given implementation. Perform these optional steps only after considering all security ramifications and only if you need to share this installation.

During patch set installation, all new files and directories are created with restricted access, by default. Users or third party applications with a different group identifier from that of the database, which try to access client-side utilities or libraries in the database home, will see permission errors when trying to access these files or directories. Perform the following steps to change the permissions:

  1. Change to the install directory by using the following command:

    $ cd $ORACLE_HOME/install
  2. Run changePerm.sh and specify the patched server Oracle home location, before accessing client-side utilities or libraries in the database home.


    Note:

    If you are patching Oracle RAC home, then you will need to run this script on all the nodes.

7.4 Updating Oracle Time Zone Definitions

If you saved TSTZ data as mentioned in Update Oracle Time Zone Definitions section under Preinstallation Tasks, you need to restore this data to the TSTZ columns where they originated from.

Refer to the instructions in the utltzuv2.sql script in step 3 of Update Oracle Time Zone Definitions or OracleMetalink note 396671.1: Usage of utltzuv2.sql before updating time zone files in Oracle 10.

To locate document 396671.1 on the OracleMetalink Web site:

http://metalink.oracle.com

To locate document 396671.1:

  1. Log on to OracleMetalink.

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

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

8 Removing the Patch Set Software

The catdwgrd.sql script enables the user to restore the Oracle Database installation of the database back to the original 10.2 release that the user backed up before applying the patch set. The catdwgrd.sql script is run in the 10.2.0.3 Oracle home to perform necessary downgrade actions. After the 10.2.0.x release is restored, the catrelod.sql script is run from 10.2.0.x Oracle home to reload the 10.2.0.x release packages and views.

See one of the following sections for information about how to remove the patch set software based on your Oracle Database installation type:


Note:

  • Oracle Clusterware downgrade is not supported.

  • You can run a higher version of Oracle Clusterware software with a lower version of Oracle Database.


8.1 Removing the Patch Set Software for Single Instance Installation

Perform the following steps for removing the patch set from the 10.2.0.3 patch release:

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

    $ sqlplus /NOLOG
    SQL> CONNECT SYS/SYS_password AS SYSDBA
    SQL> SHUTDOWN IMMEDIATE
    SQL> EXIT
    
    
  2. Take a backup of the following file in 10.2.0.3 Oracle home directory:

    $ ORACLE_HOME/rdbms/admin/catrelod.sql
    $ ORACLE_HOME/network/admin/tnsnames.ora
    
    
  3. Enter the following SQL*Plus commands:

    $ cd $ORACLE_HOME
    $ sqlplus /NOLOG
    SQL> CONNECT SYS/SYS_password AS SYSDBA
    SQL> STARTUP DOWNGRADE
    SQL> SPOOL downgrade.out
    SQL> @?/rdbms/admin/catdwgrd.sql
    SQL> SPOOL OFF
    SQL> SHUTDOWN IMMEDIATE
    SQL> EXIT
    
    
  4. Review the downgrade.out file for errors.

  5. Restore the Oracle10g installation and Central Inventory (see /etc/oraInst.loc) that you backed up before applying the patch set.

  6. After restoring the original Oracle home, copy the saved version of catrelod.sql script into the restored Oracle home rdbms/admin directory. Also copy the saved version of 10.2.0.3/network/admin/tnsnames.ora directory into the restored Oracle home /network/admin/tnsnames.ora directory, and then perform the following steps:

    $ sqlplus /NOLOG
    SQL> CONNECT SYS/SYS_password AS SYSDBA
    SQL> STARTUP DOWNGRADE
    SQL> SPOOL catrelod.out
    SQL> @?/rdbms/admin/catrelod.sql
    SQL> SPOOL OFF
    SQL> SHUTDOWN IMMEDIATE
    
    
  7. Review the catrelod.out file for errors.


    Note:

    Ignore the ORA-29844 and ORA-31085 errors found in the catrelod.out file. These errors are tracked with Oracle bugs 4758112 and 4425495 respectively.

    After reloading the 10.2.0.2 release, the version numbers for Oracle Data Mining and Oracle OLAP Analytic Workspace remain at 10.2.0.3. These issues are tracked with Oracle bugs 4758695 and 4751917.


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

    SQL> STARTUP
    SQL> @?/rdbms/admin/utlrp.sql
    
    

8.2 Removing the Patch Set Software for Oracle RAC Installation

Perform the following steps for removing the patch set from the 10.2.0.3 patch release:

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

     $ sqlplus /NOLOG
     SQL> CONNECT SYS/SYS_password AS SYSDBA
    
    
  2. Set the CLUSTER_DATABASE initialization parameter to FALSE:


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

    SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile; 
    
    
  3. Exit SQL*Plus and shut down the database:

    $ srvctl stop database -d db_name
    
    
  4. Take a backup of the following files in 10.2.0.3 Oracle home directory:

    $ ORACLE_HOME/rdbms/admin/catrelod.sql
    $ ORACLE_HOME/network/admin/tnsnames.ora
    
    
  5. Enter the following SQL*Plus commands:

    $ sqlplus /NOLOG
    SQL> CONNECT SYS/SYS_password AS SYSDBA
    SQL> STARTUP DOWNGRADE
    SQL> SPOOL catdwgrd.out
    SQL> @?/rdbms/admin/catdwgrd.sql
    SQL> SPOOL OFF
    SQL> SHUTDOWN IMMEDIATE
    SQL> EXIT
    
    
  6. Restore the Oracle10g installation and Central Inventory (see /etc/oraInst.loc) that you backed up before applying the patch set on both the nodes.

  7. After restoring the original Oracle home, copy the saved version of catrelod.sql script into the restored Oracle home rdbms/admin directory. Also copy the saved version of 10.2.0.3/network/admin/tnsnames.ora directory into the restored Oracle home /network/admin/tnsnames.ora directory, and then perform the following steps:

    $ sqlplus /NOLOG
    SQL> CONNECT SYS/SYS_password AS SYSDBA
    SQL> STARTUP DOWNGRADE
    SQL> SPOOL catrelod.out
    SQL> @?/rdbms/admin/catrelod.sql
    SQL> SPOOL OFF
    SQL> SHUTDOWN IMMEDIATE
    
    
  8. Review the catrelod.out file for errors.


    Note:

    Ignore the ORA-29844 and ORA-31085 errors found in the catrelod.out file. These errors are tracked with Oracle bugs 4758112 and 4425495 respectively.

    After reloading the 10.2.0.2 release, the version numbers for Oracle Data Mining and Oracle OLAP Analytic Workspace remain at 10.2.0.3. These issues are tracked with Oracle bugs 4758695 and 4751917.


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

    SQL> STARTUP
    SQL> @?/rdbms/admin/utlrp.sql
    
    
  10. Set the CLUSTER_DATABASE initialization parameter to TRUE:


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

    SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
    SQL> SHUTDOWN
    SQL> EXIT
    
    
  11. Start the database:

    $ srvctl start database -d db_name
    
    

    Note:

    Option for removing Oracle Clusterware patch set is not available in 10.2.0.3. This issue is tracked with Oracle bug 5598010.

9 Reinstalling the Patch Set Software

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

To reinstall the patch set:

  1. Log in 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 Oracle Universal Installer (your workstation or PC).

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

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

  5. In the Specify Home Details screen, select the name of the Oracle home that you want to update, or select the Path that you want to update from the list, then click Next.

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


    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 nodes for each component listed in the tree to display the patch that corresponds to each component.

  8. Select the patches that you want to install.

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

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

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

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

10 Known Issues

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

10.1 Oracle Scheduler External Jobs

If you use Oracle Scheduler, that is, (dbms_scheduler) external jobs on Linux, and have modified the owner or group of the extjob executable, then this patch set will reset these changes.

Beginning with Oracle Database release 10.2.0.3, the supported way to change the user or group that external jobs run as is to modify the externaljob.ora file in rdbms/admin. This file is owned by root user and only the root user can modify this file. Changes to this file take effect immediately and do not require restarting the database.

10.2 Upgrading Preconfigured Standard Edition Databases

If you are using an Oracle Database release 10.2.0.2 preconfigured Standard Edition database, then the database contains the following components that are not supported by the Standard Edition:

  • Oracle Data Mining

  • Oracle OLAP Catalog

  • Oracle OLAP Analytic Workspace

  • Oracle OLAP API

The catupgrd.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 catupgrd.sql script does not apply the patch to them.

10.3 Oracle Database Upgrade Assistant Summary Page Shows Incorrect Version Information

When you use Oracle Database Upgrade Assistant to upgrade the Automatic Storage Management instance of the database to 10.2.0.3 patch set, the pre-upgrade summary page and the upgrade results page display the earlier 10.2 version of the Automatic Storage Management instance even if the upgrade is successful.

This issue is tracked with Oracle bug 5510050.

10.4 Upgrade of Oracle Enterprise Manager Not Supported

When you start Oracle Database Upgrade Assistant to upgrade database to 10.2.0.3 patch set, the following error occurs:

Inplace upgrade of Enterprise Manager is not supported for RAC databases is 
not supported in this release

Workaround:

Ignore warning.

This issue is tracked with Oracle bug 5534298.

10.5 Running Oracle Database Upgrade Assistant on a Single Node Oracle RAC Installation

Oracle Database Upgrade Assistant fails during postinstallation upgrade on a single node and displays the following error message:

ORA-32001: write SPFILE requested but no SPFILE specified at startup

Workaround:

  1. Start the database with the NOMOUNT option:

    $ sqlplus /NOLOG
    SQL> CONNECT SYS/SYS_password AS SYSDBA
    SQL> STARTUP NOMOUNT
    
    
  2. Create SPFILE from PFILE by entering the following command where pfile_location is usually $ORACLE_BASE/admin/db_name/pfile for Optimal Felxible Architecture compliant database:

    SQL> CREATE SPFILE=SHARED_LOCATION/SPFILE.ORA FROM PFILE=pfile_location/init.ora
    
    
  3. Shut down the database:

    SQL> SHUTDOWN IMMEDIATE
    SQL> EXIT
    
    
  4. Clear the contents of PFILE located at $ORACLE_HOME/dbs/initsid.ora and set the value of SPFILE as SHARED_LOCATION/SPFILE.ORA.

  5. Run Oracle Database Upgrade Assistant:

    $ $ORACLE_HOME/bin/dbua
    
    

Note:

This workaround will resolve the issue faced during add node operation from single node. This issue is tracked with Oracle bug 5585075.

This issue is tracked with Oracle bug 5531643.

10.6 Oracle OLAP Users Unable to Connect to Oracle Warehouse Builder

Oracle OLAP users will not be able to connect to Oracle Warehouse Builder immediately after upgrading their database to 10.2.0.3.0.

Workaround:

Download patch 5548282 from OracleMetalink or Oracle Technology Network.

This issue is tracked with Oracle bug 5548282.

10.7 Memory Access Mode not Supported in Oracle RAC

In an Oracle RAC set up, if database instances are not running on the same node as Oracle Enterprise Manager Management Service, then monitoring in memory access mode does not display performance chart data.

This issue is tracked with Oracle bug 5559618.

10.8 VIP May Relocate to the Last Node While Upgrading Oracle Clusterware

Rolling upgrade or upgrade of Oracle Clusterware to 10.2.0.3 patch set may cause VIP to move to the last node.

Workaround:

Enter the following command to relocate the VIP to the preferred node:

crs_relocate VIP Resource

This issue is tracked with Oracle bug 5673067.

10.9 RTSORA May Fail During the Linking Phase

RTSORA may fail during the linking phase and the following error message may be displayed.

/usr/bin/make -f ins_precomp.mk relink
ORACLE_HOME=/u03/app/oracle/product/10.2.0.3/clnt EXENAME=rtsora/Linking
/u03/app/oracle/product/10.2.0.3/clnt/precomp/lib/rtsora
ld: warning: libcobscreen64.so, needed by
/opt/microfocus/cobol/lib/libcobrts64_t.so, not found (try using -rpath or
-rpath-link)

Workaround:

Ignore the error and relink RTSORA manually by using the following steps:

  1. Set COBDIR variable where the cobol compiler is installed. For example:

    $ export COBDIR=/opt/microfocus/cobol
    
    
  2. Set the LD_LIBRARY_PATH pointing to the cobol libraries. For example:

    $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/microfocus/cobol/lib
    
    
  3. Enter the following command:

    $ cd $ORACLE_HOME/precomp/lib
    $ /usr/bin/make -f ins_precomp.mk relink
    
    

This issue is tracked with Oracle bug 5724164.

10.10 Makefile Exception while Deinstalling Oracle Database Standard Edition or Enterprise Edition

While deinstalling Oracle Database 10g release 2 (10.2) Standard Edition or Enterprise Edition, makefile exception is displayed.

Workaround:

Ignore the error message.

This issue is tracked with Oracle bug 5645736.

11 Fixed Platform-Specific Bugs

There are no platform-specific bugs fixed in this release.

12 Patch Set Components

The following table provides a list of patch set components:

Component Version
Advanced Queuing (AQ) API 10.2.0.3
Advanced Queuing (AQ) API Demos 10.2.0.3
Advanced Replication 10.2.0.3
Agent Required Support Files 10.2.0.3
Assistant Common Files 10.2.0.3
Authentication and Encryption 10.2.0.3
Authentication and Encryption 32-bit 10.2.0.3
CSS Single-instance Common Files 10.2.0.3
Character Set Migration Utility 10.2.0.3
Clusterware 10.2.0.3
DBJAVA Required Support Files 10.2.0.3
Data Management Services Common Files 10.2.0.3
Data Mining Scoring Engine 10.2.0.3
Database Configuration Assistant 10.2.0.3
Database SQL Scripts 10.2.0.3
Database Upgrade Assistant 10.2.0.3
Database Verify Utility 10.2.0.3
Database Workspace Manager 10.2.0.1
Enterprise Manager Agent 10.2.0.3
Enterprise Manager Common Files 10.2.0.3
Enterprise Manager Repository 10.2.0.3
Enterprise Manager plugin Common Files 10.2.0.3
Export/Import 10.2.0.3
External Naming: NIS 10.2.0.3
Generic Connectivity Common Files 10.2.0.3
Generic Connectivity Using ODBC 10.2.0.3
HAS component of Oracle Clusterware install 10.2.0.3
Installation Common Files 10.2.0.3
iSQL*Plus 10.2.0.3
JAccelerator (NCOMP) 10.2.0.3
JDBC Common Files 10.2.0.3
JDBC/OCI Common Files 10.2.0.3
JDBC/OCI Common Files for Instant Client 10.2.0.3
LDAP Required Support Files 10.2.0.3
New Database ID 10.2.0.3
Object Type Translator 10.2.0.3
Oracle C++ Call Interface 10.2.0.3
Oracle C++ Call Interface Demos 10.2.0.3
Oracle C++ Call Interface for Instant Client 10.2.0.3
Oracle Call Interface (OCI) 10.2.0.3
Oracle Call Interface (OCI) Demos 10.2.0.3
Oracle Client 10.2.0.3
Oracle Client Required Support Files 10.2.0.3
Oracle Common Schema Demos 10.2.0.3
Oracle Connection Manager 10.2.0.3
Oracle Containers for Java 10.2.0.3
Oracle Containers for Java Demos 10.2.0.3
Oracle Text Knowledge Bases 10.2.0.3
Oracle Core Required Support Files 10.2.0.3
Oracle Data Mining 10.2.0.3
Oracle Data Mining Demos 10.2.0.3
Oracle Database 10G 10.2.0.3
Oracle Database 10G Companion Products 10.2.0.3
Oracle Database 10G Products 10.2.0.3
Oracle Database Demos 10.2.0.3
Oracle Database Utilities 10.2.0.3
Oracle Enterprise Manager Console DB 10.2.0.3
Oracle Globalization Support 10.2.0.3
Oracle Globalization Support Demos 10.2.0.3
Oracle Instant Client 10.2.0.3
Oracle Instant Client Required Support Files 10.2.0.3
Oracle interMedia Annotator 10.2.0.3
Oracle interMedia Client Demos 10.2.0.3
Oracle interMedia Common Files 10.2.0.3
Oracle interMedia Client Compatibility Files 10.2.0.3
Oracle interMedia Image 10.2.0.3
Oracle interMedia Image Accelerator 10.2.0.3
Oracle interMedia Java Advanced Imaging 10.2.0.3
Oracle interMedia Locator 10.2.0.3
Oracle Internet Directory Client 10.2.0.3
Oracle Internet Directory Client Common Files 10.2.0.3
Oracle Internet Directory Tools 10.2.0.3
Oracle JDBC Development Drivers 10.2.0.3
Oracle JDBC Development Drivers Demos 10.2.0.3
Oracle JDBC Development Drivers for Instant Client 10.2.0.3
Oracle JDBC Thin Driver for JDK 1.2 10.2.0.3
Oracle JDBC Thin Driver for JDK 1.4 10.2.0.3
Oracle JDBC Thin Driver for JDK 1.4 for Instant Client 10.2.0.3
Oracle JVM 10.2.0.3
Oracle Java Tools 10.2.0.3
Oracle Label Security 10.2.0.3
Oracle Label Security Demos 10.2.0.3
Oracle Locale Builder 10.2.0.3
Oracle Net 10.2.0.3
Oracle Net Configuration Assistant 10.2.0.3
Oracle Net Listener 10.2.0.3
Oracle Net Manager 10.2.0.3
Oracle Net Required Support Files 10.2.0.3
Oracle OLAP Analytic Workspace 10.2.0.3
Oracle OLAP API 10.2.0.3
Oracle OLAP Catalog 10.2.0.3
Oracle Partitioning 10.2.0.3
Oracle RAC Required Support Files 10.2.0.3
Oracle RAC Required Support Files-HAS 10.2.0.3
Oracle Real Application Clusters 10.2.0.3
Oracle SQLJ 10.2.0.3
Oracle Spatial 10.2.0.3
Oracle Spatial Demos 10.2.0.3
Oracle Starter Database 10.2.0.3
Oracle Text 10.2.0.3
Oracle Text Samples 10.2.0.3
Oracle Transparent Gateway for IBM DRDA 10.2.0.3
Oracle Ultra Search Middle-Tier 10.2.0.3
Oracle Ultra Search Server 10.2.0.3
Oracle Wallet Manager 10.2.0.3
Oracle XML Developer's Kit 10.2.0.3
Oracle XML SQL Utility 10.2.0.3
Oracle 10g Real Application Clusters Common Files 10.2.0.3
PL/SQL 10.2.0.3
PL/SQL Embedded Gateway 10.2.0.3
PL/SQL Required Support Files 10.2.0.3
Parser Generator Required Support Files 10.2.0.3
Precompiler Common Files 10.2.0.3
Precompiler Required Support Files 10.2.0.3
Pro*C/C++ 10.2.0.3
Pro*C/C++ Demos 10.2.0.3
Pro*COBOL (32-bit and 64-bit) 10.2.0.3
Pro*FORTRAN 10.2.0.3
Pro*FORTRAN Demos 10.2.0.3
RDBMS Required Support Files 10.2.0.3
Recovery Manager 10.2.0.3
Replication API 10.2.0.3
SQL*Loader 10.2.0.3
SQL*Plus 10.2.0.3
SQL*Plus Demos 10.2.0.3
SQL*Plus Required Support Files 10.2.0.3
SQLJ Runtime 10.2.0.3
SRVM component of Oracle Clusterware install 10.2.0.3
SSL Required Support Files 10.2.0.3
SSL Required Support Files for Instant Client 10.2.0.3
Sample Schema 10.2.0.3
Secure Socket Layer 10.2.0.3
Utilities Common Files 10.2.0.3
XDK Required Support Files 10.2.0.3
XML 10.2.0.3
XML Class Generator for C++ 10.2.0.3
XML Class Generator for Java 10.2.0.3
XML Parser for C 10.2.0.3
XML Parser for C++ 10.2.0.3
XML Parser for C++ Demos 10.2.0.3
XML Parser for Java 10.2.0.3
XML Transviewer Bean 10.2.0.3
XML Transx 10.2.0.3
XSQL Servlet 10.2.0.3
XSQL Servlet Demos 10.2.0.3

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, 10g Release 2 (10.2.0.3) Patch Set 2 for Linux x86-64

Copyright © 2007, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.