10g Release 2 (10.2.0.4) Patch Set 3 for Linux x86

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.4 patch set to the following Oracle Database 10g release 2 installations:

Oracle Database
Oracle Real Application Clusters
Oracle Database Client
Oracle Database Companion CD

Oracle Clusterware

Oracle Database Vault

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

2 Components of This Patch Set

The following are the updated components of this patch set:

Up to January 2008 CPU is included in this patch set.
Platform-specific bug fixes as listed in the "Fixed Platform-Specific Bugs" section
Generic bug fixes as listed in the List of Bugs fixed document
Oracle Configuration Manager 10.2.7.1

See Also:
Oracle Configuration Manager Installation and Administration Guide10g Release 7 (10.2) (Part Number B32294-01)

3 Accessing the Latest Version of this Document

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:

Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 316900.1 in the Document ID field, then click Submit.

4 Oracle Universal Installer Version Requirements

This patch set includes Oracle Universal Installer release 10.2.0.4, which is also installed when you install this patch set. This is to ensure that the 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.

5 Patch Set Documentation

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

Oracle Database Patch Set Notes, 10g release 2 (10.2.0.4) Patch Set 3 for Linux x86 (this document)
Oracle Database List of Bugs Fixed, 10g release 2 (10.2.0.4) Patch Set 3

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:

Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
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.4) Patch Set 3 for Linux x86

This document provides:

System requirements and information about how to install, reinstall or remove the patch set
A list of all bugs fixed to date that are specific to Oracle Database for Linux x86
A list of known issues relating to Oracle Database on Linux x86

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

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

6 System Requirements

The following are the system requirements for this patch set:

Operating System
- Asianux 1.0
- Asianux 2.0
- Asianux 3.0
- Oracle Enterprise Linux 4.0/Oracle VM
- Oracle Enterprise Linux 5.0/Oracle VM
- Red Hat Enterprise Linux AS/ES 3.0
- Red Hat Enterprise Linux AS/ES 4.0/Oracle VM
- Red Hat Enterprise Linux AS/ES 5.0/Oracle VM
- SUSE Linux Enterprise Server (SLES) 9
- SUSE Linux Enterprise Server (SLES) 10

Oracle Database 10g (10.2.0.1) or later

7 Preinstallation Tasks

Complete the following preinstallation tasks before installing the patch set:

Review Known Preinstallation Issues
Identify the Oracle Database Installation
Check Postrelease Updates
Download and Extract the Installation Software
Update Oracle Time Zone Definitions
Set the ORACLE_HOME and ORACLE_SID Environment Variables
Stop All Processes
Back Up the System

7.1 Review Known Preinstallation Issues

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

Upgrading Oracle E-Business Suite Databases
Upgrading Installations that use Physical or Logical Standby Databases
Upgrading Installations that use Java Virtual Machine or Oracle interMedia
Upgrading Oracle Clusterware
Notes to Oracle OLAP Users

Disabling Oracle Database Vault

7.1.1 Upgrading Oracle E-Business Suite Databases

If you are an Oracle E-Business Suite customer and you want to upgrade the 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

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

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

7.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. This patch does not allow you to upgrade Oracle RAC before you upgrade Oracle Clusterware.

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

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

http://metalink.oracle.com

To locate document 352306.1:

Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 352306.1 in the Document ID field, then click Submit.

7.1.6 Disabling Oracle Database Vault

Complete the steps in this section before upgrading Oracle Database Vault from 10.2.0.x to 10.2.0.4 or downgrading Oracle Database Vault from 10.2.0.4 to 10.2.0.x:

Re-create and replace the password file, in order to log in to an Oracle Database Vault instance as a SYS user with SYSDBA privilege:

$ orapwd file=$ORACLE_HOME/dbs/orapwsid password=syspasswd force=y nosysdba=n

Note:

The SYS connection as SYSDBA is disabled in a default Oracle Database Vault installation. Without enabling SYSDBA, you cannot unlock DVSYS in Step 5 that follows.

Shut down the database:

For Oracle RAC:

$ srvctl stop database -d db_name -c "SYS/SYS_password as SYSDBA"

For Single Instance:

SQL> CONNECT SYS AS SYSOPER
Enter password: SYS_password
SQL> SHUTDOWN

Re-link the Oracle database software with dv_off:

Note:
For Oracle RAC, you must run the following commands on all the nodes.
```
$ cd $ORACLE_HOME/rdbms/lib
$ make -f ins_rdbms.mk dv_off
$ cd $ORACLE_HOME/bin
$ relink oracle
```

Start the database:

For Oracle RAC:

$ srvctl start database -d db_name -c "SYS/SYS_password as SYSDBA"

For Single Instance:

$ sqlplus /nolog 
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP

Unlock the DVSYS account and set the password:

SQL> ALTER USER DVSYS ACCOUNT UNLOCK;
SQL> ALTER USER DVSYS IDENTIFIED BY DVSYS;

Disable the Oracle Database Vault triggers:

Run Oracle Database Vault Configuration Assistant (DVCA) by using the dvca -action disable option. This disables the Database Vault triggers. Use the following syntax:
```
dvca -action disable
-service service_name
-owner_account DV_owner_account_name
[-logfile ./dvca.log]
[-nodecrypt] 

Enter SYS password: sys_password
Enter owner password: owner_password
```

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

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

Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
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.

7.4 Download and Extract the Installation Software

To download and extract the patch set installation software:

Download the p6810189_10204_Linux-x86.zip patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory.
Enter the following command to unzip and extract the installation files:
```
$ unzip p6810189_10204_Linux-x86.zip
```

7.5 Update Oracle Time Zone Definitions

The 10.2.0.4 patch set includes an update to the Oracle time zone definitions to Version 4. This version of the time zone definitions includes the changes to daylight saving time in the USA in 2007 and other updates.

In the Oracle database the TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) and TIMESTAMP WITH TIME ZONE (TSTZ) data types and the TZ_OFFSET function select the time zone information from the time zone files.

It may be necessary to take action on existing TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) and TIMESTAMP WITH TIME ZONE (TSTZ) data or to re-apply DST patches afterwards.

For full overview please see OracleMetaLink document 553812.1 "Actions for the DSTv4 update in the 10.2.0.4 patchset".

When patching from a lower 10.2 release or upgrading from 10.1.0.X directly to 10.2.0.4, check the current version of the Oracle time zone definitions with the following command:
```
SELECT version FROM v$timezone_file;
```
- If this query reports version 4, no action is required; in this case, continue with steps described in section 7.6.
- If this reports a version lower or higher then 4, see OracleMetalink document 553812.1 "Actions for the DSTv4 update in the Release 10.2.0.4 patchset".
On upgrading from Release 9i directly to Release 10.2.0.4, see OracleMetaLink document 553812.1 "Actions for the DSTv4 update in the 10.2.0.4 patchset."
On upgrading from Release 8.1.7 directly to Release 10.2.0.4, no action is required because Release 8.1.7 has no timezone data stored; in this case continue with steps described in section 7.6

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

7.7 Stop All Processes

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

Stopping All Processes for a Single Instance Installation
Stopping All Processes for an Oracle Clusterware Installation
Stopping All Processes for an Oracle RAC Installation

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

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

Shut down all database instances running in the Oracle home directory, where you need to install the patch set.
Shut down all listeners running in the Oracle home directory, where you need to install the patch set.
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 AS SYSDBA
Enter password:SYS_password
SQL> SHUTDOWN IMMEDIATE
```
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
```

7.7.2 Stopping All Processes for an Oracle Clusterware Installation

This section contains the following information:

Rolling Upgrade
Non Rolling Upgrade

7.7.2.1 Rolling Upgrade

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

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.

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]]
```
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
```
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
```
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
```

Perform. the steps mentioned in Section 8.

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:

Log in as the root user and enter the following command to shut down the Oracle Clusterware:
```
# CRS_home/bin/crsctl stop crs
```
Run the root102.sh script. to automatically start the Oracle Clusterware on the patched node:
```
# CRS_home/install/root102.sh
```

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.

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

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.

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]]
```
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
```
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
```
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
```
Shut down the Oracle Clusterware processes by entering the following command on all nodes as the root user:
```
# CRS_home/bin/crsctl stop crs
```

Complete the steps mentioned in Section 8.

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:

Log in as the root user and enter the following command to shut down the Oracle Clusterware:
```
# CRS_home/bin/crsctl stop crs
```
Run the root102.sh script. to automatically start the Oracle Clusterware on the patched node:
```
# CRS_home/install/root102.sh
```

7.7.3 Stopping All Processes for an Oracle RAC Installation

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

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.

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]]
```
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
```
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
```
This needs to be done only when patching the home from where ASM runs. It is recommended that ASM run from a different ORACLE_HOME than the database.

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.

7.8 Back Up the System

Oracle recommends that you create a backup of the Oracle Inventory, Oracle 10g home and Oracle 10g Database before you install the patch set. If you are planning to apply this patch to Oracle RAC, ensure that you create a backup of these components on all nodes before applying the patch.

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

Note:

If you also plan to apply this patch to Oracle Clusterware, ensure that you apply the patch to Oracle Clusterware before applying it to Oracle Database. This is because Oracle Clusterware should always be at the same or later version as the database.

Installing the Oracle Database 10g Patch Set Interactively
Installing the Oracle Database 10g Patch Set Noninteractively

8.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 higher 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 3
10.2.0.4

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

Log in as the oracle user.
If you are not installing the software on the local computer, 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 computer that you want to use to display Oracle Universal Installer.

Now to enable X applications, run the following command on the machine that you want to use to display Oracle Universal Installer:
```
$ xhost + [fully_qualified_remote_host_name]
```
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
```
On the Welcome screen, click Next.
On 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.
If you are installing the patch set on an Oracle RAC cluster, click Next when the Selected Nodes screen appears.
On the Product-specific Prerequisite Checks screen, correct any reported errors, and click Next.

Enter details regarding the CSI Number, OracleMetaLink Account user name and Country code on the Oracle Configuration Manager Registration screen and click Next.

Note:

The registration and configuration can also be done manually after patchset installation.

The OCM registration page appears only while applying 10.2.0.4 patch over existing DB instances alone.

On the Summary screen, click Install.

This screen lists all of the patches available for installation.

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.

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

8.2 Installing the Oracle Database 10g Patch Set Noninteractively

To install the Oracle Database 10g patch set noninteractively:

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

Edit the values for all fields labeled as 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.

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

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.

9 Postinstallation Tasks

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

Upgrading Earlier Oracle Database to Oracle Database 10g Release 2 (10.2.0.4)
Upgrading Oracle Database 10g Release 10.2.0.x to Oracle Database 10g Release 10.2.0.4
Enabling Oracle Database Vault
Running changePerm.sh Script. on an Oracle Database Server Home
Updating Oracle Time Zone Definitions
Configuring Oracle Configuration Manager in a Cloned Oracle Home

9.1 Updating Oracle Time Zone Definitions

Based on the result you had in Section 7.5, "Update Oracle Time Zone Definitions" regarding the DST (Oracle time zone definitions):

If the DST version in 7.5 was 4, no action is required.
If f the DST version in 7.5 was higher than 4, reapply the version of DST patches as described in OracleMetaLink document 553812.1 "Actions for the DSTv4 update in the 10.2.0.4 patchset."
If the DST version in 7.5 was lower then 4, restore TSTZ data from backup (if any). For more information, see OracleMetaLink document 553812.1 "Actions for the DSTv4 update in the 10.2.0.4 patchset."
If you are upgrading from Release 8.1.7 directly to Release 10.2.0.4, no action is required.

9.2 Upgrading Earlier Oracle Database to Oracle Database 10g Release 2 (10.2.0.4)

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

Upgrading Earlier Oracle Database Releases to Oracle Database 10g Release 2 (10.2.0.4)
Upgrading a Release 9.2 Database Not Using Oracle Label Security

9.2.1 Upgrading Earlier Oracle Database Releases to Oracle Database 10g Release 2 (10.2.0.4)

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 Oracle Real Application Clusters Administration Guide as well.

9.2.2 Upgrading a Release 9.2 Database Not Using Oracle Label Security

To find if Oracle Label Security is in the installation, complete the following steps:

You can use one of the following methods check if Oracle Label Security is installed:
- If the following script. exists on the computer, Oracle Label Security is installed:
```
$ORACLE_HOME/rdbms/admin/catnools.sql
```
- Check the inventory at the end of the installAction log file for the base version installation (9.2). If Oracle Label Security is installed, Label Security is listed in the inventory section of the log file.
Use the following commands to check if Oracle Label Security is installed with the 9.2 database:
```
$ sqlplus
SQL> CONNECT SYS AS SYSDBA
Enter password:password
SELECT * FROM V$OPTION WHERE PARAMETER = "ORACLE LABEL SECURITY";
```
If the command does not display any results, Oracle Label Security is not applied to the database and you can ignore this section. However, if the command returns some results, you must complete this section.

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:

Use Oracle Universal Installer release 9.2 to install Oracle Label Security using the Custom installation type.
Run the $ORACLE_HOME/rdbms/admin/catnools.sql script. with the SYSDBA privilege to remove Oracle Label Security components from the database.

9.3 Upgrading Oracle Database 10g Release 10.2.0.x to Oracle Database 10g Release 10.2.0.4

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

Upgrading a Release 10.2 Database using Oracle Database Upgrade Assistant
Manually Upgrading a Release 10.2 Database

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

Log in as the Oracle software owner user.
Set the values for the environment variables $ORACLE_HOME, $ORACLE_SID and $PATH.
For single-instance installations, if you are using Automatic Storage Management, start the Automatic Storage Management instance.
For Oracle single-instance installations, start the listener as follows:
```
$ lsnrctl start
```

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:

On the Welcome screen, click Next.
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.
On the Recompile Invalid Objects screen, select the Recompile the invalid objects at the end of upgrade option, then click Next.
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, stipulate the Path, then click Next.
On the Summary screen, check the summary, then click Finish.
On the End of Database Upgrade Assistant's Upgrade Results screen, click Close to exit from Oracle Database Upgrade Assistant.

Note:

If you are upgrading a database having dbcontrol configured in non-secure mode, after upgrade dbconsole will run in secure mode.

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

If you are using the Oracle Recovery Manager catalog, enter the following command:
```
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
```
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
```

9.3.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.4:

Run the Pre-Upgrade Information Tool
Upgrading a Release 10.2 Database
Missing Components when Upgrading

9.3.2.1 Run the Pre-Upgrade Information Tool

If you are upgrading database manually, then you should analyze it by running the Pre-Upgrade Information Tool.

The Pre-Upgrade Information Tool is a SQL script. that ships with Oracle Database 10.2. Complete the following procedure to run the Pre-Upgrade Information Tool:

Start the database in the UPGRADE mode:
```
SQL> STARTUP UPGRADE
```
Set the system to spool results to a log file for later analysis:
```
SQL> SPOOL upgrade_info.log 
```
Run the Pre-Upgrade Information Tool:
```
SQL> @?/rdbms/admin/utlu102i.sql
```
Turn off the spooling of script. results to the log file:
```
SQL> SPOOL OFF
```

Check the output of the Pre-Upgrade Information Tool in the upgrade_info.log file. The following is an example of the output generated by the Pre-Upgrade Information Tool:

Oracle Database 10.2 Upgrade Information Utility    02-04-2008 11:48:11
.
**********************************************************************
Database:
**********************************************************************
--> name:       X102040
--> version:    10.2.0.1.0
--> compatible: 10.2.0.1
--> blocksize:  8192
.
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 505 MB
.... AUTOEXTEND additional space required: 15 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
.... minimum required size: 401 MB
.... AUTOEXTEND additional space required: 376 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 265 MB
.... AUTOEXTEND additional space required: 15 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 58 MB
.... AUTOEXTEND additional space required: 38 MB
--> EXAMPLE tablespace is adequate for the upgrade.
.... minimum required size: 69 MB
.
**********************************************************************
Update Parameters: [Update Oracle Database 10.2 init.ora or spfile]
**********************************************************************
WARNING: --> "shared_pool_size" needs to be increased to at least 167772160
WARNING: --> "java_pool_size" needs to be increased to at least 67108864
.
**********************************************************************
Components: [The following database components will be upgraded orinstalled]
**********************************************************************
--> Oracle Catalog Views         [upgrade]  VALID
--> Oracle Packages and Types    [upgrade]  VALID
--> JServer JAVA Virtual Machine [upgrade]  VALID
--> Oracle XDK for Java          [upgrade]  VALID
--> Oracle Java Packages         [upgrade]  VALID
--> Oracle Text                  [upgrade]  VALID
--> Oracle XML Database          [upgrade]  VALID
--> Oracle Workspace Manager     [upgrade]  VALID
--> Oracle Data Mining           [upgrade]  VALID
--> Messaging Gateway            [upgrade]  VALID
--> OLAP Analytic Workspace      [upgrade]  VALID
--> OLAP Catalog                 [upgrade]  VALID
--> Oracle OLAP API              [upgrade]  VALID
--> Oracle interMedia            [upgrade]  VALID
--> Spatial                      [upgrade]  VALID
--> Oracle Ultra Search          [upgrade]  VALID
--> Oracle Label Security        [upgrade]  VALID
--> Expression Filter            [upgrade]  VALID
--> EM Repository                [upgrade]  VALID
--> Rule Manager                 [upgrade]  VALID
PL/SQL procedure successfully completed.

The following sections describe the output of the Pre-Upgrade Information Tool.

Database

This section displays global database information about the current database, such as the database name and release number before the database is upgraded.

Tablespaces

This section displays a list of tablespaces in the current database. For each tablespace, the tablespace name and minimum required size is displayed. In addition, a message is displayed if the tablespace is adequate for the upgrade. If the tablespace does not have enough free space, then space must be added to the tablespace in the current database. Tablespace adjustments must be made before the database is upgraded.

Update/Obsolete/Deprecated Parameters

These sections display a list of initialization parameters in the parameter file of the current database that should be adjusted before the database is upgraded. The adjustments must be made to the Oracle Database 10.2 init.ora or spfile.

Components

This section displays a list of database components that are upgraded or installed when the current database is upgraded.

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

Log in as the Oracle software owner user.
For Oracle RAC installations, start listener on each node of the cluster as follows:
```
$ srvctl start listener -n node
```
If you are using Automatic Storage Management, start the Automatic Storage Management instance.
For single-instance installations, start the listener as follows:
```
$ lsnrctl start
```
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 AS SYSDBA
Enter password:SYS_password
```
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 AS SYSDBA
Enter password: SYS_password
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
```

Enter the following SQL*Plus commands:

SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catupgrd.sql
SQL> SPOOL OFF

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.
If necessary, rerun the catupgrd.sql script. after correcting any problems.
Restart the database:
```
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP
```

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.4 patch set is applied to an Oracle Database 10g Standard Edition database, there may be 54 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

Run the following command to check the status of all the components after the upgrade:
```
SQL> select comp_name, version, status from sys.dba_registry;
```
In the output of the preceding command, the status of all the components should be VALID for a successful upgrade.
If you are using the Oracle Recovery Manager catalog, enter the following command:
```
$ rman catalog username/password@alias 
```
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
```

To configure and secure Enterprise Manager follow these steps:

Ensure the database and Listener are operational.

In the case of a single instance, execute
```
emca -upgrade db
```
In the case of Oracle Real Application Clusters (RAC), execute
```
emca -upgrade db -cluster
```

Note:

If you are upgrading a database having dbcontrol configured in non-secure mode, after upgrade dbconsole will run in secure mode.

9.3.2.3 Missing Components when Upgrading

When you upgrade Oracle Database 10g Release 1 (10.1.0.5) to Oracle Database 10g Release 2 (10.2.0.4), the diagnostics of the preupgrade utility script. utlu102.sql may indicate that some database components on the 10g Companion CD should be installed. You should install these components from the Oracle Database 10g Release 1 (10.1.0.5) Companion CD before applying this patch set. If the catupgrd.sql script. cannot upgrade a SERVER component because it was not installed from the Companion CD, then the status of the SERVER component in the patch.log file is reported as NO SCRIPT.

Note:

If the preupgrade script. indicates the Server JAVA Virtual Machine's JAccelerator (NCOMP) or Oracle interMedia Image Accelerator should be installed, but they are not installed before applying the patch set, then the patch.log file contains the status of their parent components as successfully upgraded to Oracle Database 10g Release 2 (10.2.0.4) even though these components are still missing.

If you find any component, which was identified as missing by the preupgrade utility script, was not installed before running the catupgrd.sql script, then install the missing component from the Companion CD and run the catupgrd.sql script. again.

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

Important:

Oracle recommends using the most restrictive file permissions possible for the 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:

Change to the install directory by using the following command:
```
$ cd $ORACLE_HOME/install
```
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 applying patch to Oracle RAC home, then you will need to run this script. on all the nodes.

9.5 Enabling Oracle Database Vault

For installations with Oracle Database Vault, complete the following steps:

Restart the database:

For a single-instance database, use the following commands:

sqlplus SYS "AS SYSDBA"
Enter password:
SQL> shutdown immediate
SQL> STARTUP

For an Oracle Real Application Clusters (RAC) database, use the following commands:

$ORACLE_HOME/bin/srvctl stop database -d db_name
$ORACLE_HOME/bin/srvctl start database -d db_name

Connect AS SYSDBA and run the following SQL statements:

SQL> DROP FUNCTION DVSYS.REALM_SDML_AUTHORIZED ;
SQL> DROP PROCEDURE DVSYS.SYNCHRONIZE_POLICY_FOR_OBJECT;
SQL> DECLARE
              CURSOR stmt IS
                       SELECT u.name, o.name, r.pname
                           FROM user$ u, obj$ o, rls$ r
                       WHERE u.user# = o.owner#
                           AND r.obj# = o.obj#
                           AND bitand(r.stmt_type,65536) > 0;
 
                       object_schema VARCHAR2(32) := NULL;
                       object_name VARCHAR2(32) := NULL;
                       policy_name VARCHAR2(32) := NULL;
 
                       BEGIN
                        OPEN stmt;
                          LOOP
                               FETCH stmt INTO object_schema, 
                                               object_name, 
                                               policy_name;
                               EXIT WHEN stmt%NOTFOUND;
                               DBMS_RLS.DROP_POLICY(
                               '"'||object_schema||'"',
                               '"'||object_name||'"',
                               '"'||policy_name||'"');
                          END LOOP;
                        CLOSE stmt;
                       END;
                      /

Run DVCA to reconfigure Database Vault. Use the following syntax:

$ORACLE_HOME/bin/dvca -action option -oh oracle_home -jdbc_str
    jdbc_connection_string -owner_account DV_owner_account_name
    [-acctmgr_account DV_account_manager_account_name]
    [-logfile ./dvca.log] [-nodecrypt]

Where:

- action: The action to perform. option creates the Database Vault schema objects, creates the DV_OWNER account and the optional DV_ACCTMGR account, and deploys the Database Vault Administrator application.

- oh: The Oracle home for the database

- jdbc_str: The JDBC connection string used to connect to the database. For example, jdbc:oracle:oci:@orcl1, where orcl1 is the net service name in the tnsnames.ora file ($ORACLE_HOME/network/admin/tnsnames.ora).

- owner_account: Oracle Database Vault Owner account name

- acctmgr_account: (Optional) Oracle Database Vault Account Manager user

- logfile: Optionally, specify a log file name and location. You can enter an absolute path or a path that is relative to the location of the $ORACLE_HOME/bin directory

- nodecrypt: Reads plaintext passwords as passed on the command line. You must use this option if you are passing plaintext passwords to the command.

Note:

You are prompted to enter the SYS, Database Vault Owner, and Database Vault Account Manager passwords.

9.6 Configuring Oracle Configuration Manager in a Cloned Oracle Home

If you have installed and configured Oracle Configuration Manager in the original Oracle home directory, then complete the following procedure:

In the cloned Oracle home, remove all the subdirectories of the $ORACLE_HOME/ccr/hosts directory to remove the previously configured hosts.
In the cloned Oracle home, run the following command:
```
$ configCCR -a
```

If you have installed Oracle Configuration Manager in the original Oracle home but have not configured it, then run the following command to configure it in the cloned Oracle home:

$ setupCCR

10 Downgrading Oracle Database Vault

Downgrading Oracle Database Vault from 10.2.0.4 to 10.2.0.x requires the following steps:

Follow the steps in section "Disabling Oracle Database Vault"
Follow the steps in section "Removing the Patch Set Software"
Follow the steps in section "Enabling Oracle Database Vault"

11 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.4 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 the Oracle Database installation type:

Removing the Patch Set Software for Single Instance Installation
Removing the Patch Set Software for Oracle RAC Installation

Note:

Oracle Clusterware downgrade is not supported.
You can run a higher version of Oracle Clusterware software with a lower version of Oracle Database.

11.1 Removing the Patch Set Software for Single Instance Installation

Perform. the following steps for removing the patch set from the 10.2.0.4 patch release:

Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /NOLOG SQL> CONNECT SYS AS SYSDBA Enter password:SYS_password SQL> SHUTDOWN IMMEDIATE SQL> EXIT

Take a backup of the following file in 10.2.0.4 Oracle home directory:

$ ORACLE_HOME/rdbms/admin/catrelod.sql
$ ORACLE_HOME/network/admin/tnsnames.ora

Enter the following SQL*Plus commands:

$ cd $ORACLE_HOME
$ sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP DOWNGRADE
SQL> SPOOL downgrade.out
SQL> @?/rdbms/admin/catdwgrd.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT

Review the downgrade.out file for errors.
Restore the Oracle10g installation and Central Inventory (see /etc/oraInst.loc) that you backed up before applying the patch set.
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.4/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 AS SYSDBA
Enter password:SYS_password
SQL> STARTUP DOWNGRADE
SQL> SPOOL catrelod.out
SQL> @?/rdbms/admin/catrelod.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
```
Review the catrelod.out file for errors.
Start the database and recompile the remaining invalid objects:
```
SQL> STARTUP
SQL> @?/rdbms/admin/utlrp.sql
```

11.2 Removing the Patch Set Software for Oracle RAC Installation

Perform. the following steps for removing the patch set from the 10.2.0.4 patch release:

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

 $ sqlplus /NOLOG
 SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password

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;

Exit SQL*Plus and shut down the database:
```
$ srvctl stop database -d db_name
```

Take a backup of the following files in 10.2.0.4 Oracle home directory:

$ ORACLE_HOME/rdbms/admin/catrelod.sql
$ ORACLE_HOME/network/admin/tnsnames.ora

Enter the following SQL*Plus commands:

$ sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP DOWNGRADE
SQL> SPOOL catdwgrd.out
SQL> @?/rdbms/admin/catdwgrd.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT

Restore the Oracle10g installation and Central Inventory (see /etc/oraInst.loc) that you backed up before applying the patch set on both the nodes.
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.4/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 AS SYSDBA
Enter password:SYS_password
SQL> STARTUP DOWNGRADE
SQL> SPOOL catrelod.out
SQL> @?/rdbms/admin/catrelod.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
```

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.4. These issues are tracked with Oracle bugs 4758695 and 4751917.

Start the database and recompile the remaining invalid objects:
```
SQL> STARTUP
SQL> @?/rdbms/admin/utlrp.sql
```

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

Start the database:

$ srvctl start database -d db_name

Note:

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

12 Removing Configuration and Deleting CCR for OCM Configured Oracle Database 10g Release 2 (10.2.0.4)

If you have installed CCR, then you should remove it manually. Complete the following steps to remove CCR, if it was configured manually after installing Oracle Database 10g Release 2 (10.2.0.4):

Create a response file with following entries:

oracle.sysman.ccr|b_localInstall=true
oracle.sysman.ccr|b_acceptLicense=true

Change to the $ORACLE_HOME/oui/bin directory.
Run the following command to remove the ccr directory from the Oracle Database 10g Release 2 (10.2.0.4) Oracle home:
```
runConfig.sh ORACLE_HOME=OH ACTION=deconfigure MODE=perform. RERUN=true
COMPONENT_XML={ccr_xml} RESPONSE_FILE=rsp_file_location
```
In the preceding command, ccr_xml is available in the $ORACLE_HOME/inventory/ContentsXML/ConfigXML directory and rsp_file_location is the directory where the response file was created. To display the ccr_xml file, run the ls oracle*ccr.10*_0.xml command in the $ORACLE_HOME/inventory/ContentsXML/ConfigXML directory.

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

Log in as the oracle user.
If you are not installing the software on the local computer, enter the following command to direct X applications to display on the local computer:
- 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 computer that you want to use to display Oracle Universal Installer.
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
```
On the Welcome screen, click Next.
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.

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.

Expand the nodes for each component listed in the tree to display the patch that corresponds to each component.
Select the patches that you want to install.

When you select a patch, the Install Status column changes to Reinstall.
Repeat the process for each patch bundled in the patch set, then click Next.
On the Summary screen, verify the list of patches to be reinstalled, then click Install.
On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.

14 Known Issues

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

Oracle Scheduler External Jobs
Upgrading Preconfigured Standard Edition Databases
The Welcome Page of Oracle Database Upgrade Assistant Displays Incorrect Version
Non-ASCII Characters on Help Navigation Are Not Displayed Properly with UTF-8 encoding
Running Oracle Database Upgrade Assistant on a Single Node Oracle RAC Installation
Refresh From OracleMetaLink Job Fails in Oracle Enterprise Manager Database Control
The sysman Related Errors Are Listed in the oraInstall.err File
Errors Displayed When Upgrading from Oracle Database 10g Release 2 (10.2.0.4)
Incorrect Database Version is Displayed on the Oracle Enterprise Manager Database Control Page After Downgrading
Benign Entry in the Silent Log File After Cloning the Database
Incorrect Nodes Displayed in Cloned Oracle Clusterware
Native Full Outer Join Implementation
Incorrect Oracle Workspace Manager Displayed After Upgrading to Oracle Database 11g
ASM Error is Displayed When Creating 10g Release 2 (10.2.0.1) Database on Oracle Clusterware (10.2.0.4)
SETUPCCR Fails if Preset JAVA_HOME Points to an Invalid JDK Home
In Red Hat Enterprise Linux 5 Default Makefile Version does not Support Default DBNAME
Oracle Clusterware Patching May Encounter Write Errors

14.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.4, the supported way to change the user or group that external jobs run as is to modify the externaljob.ora file in the rdbms/admin directory. This file is owned by the 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.

14.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
Oracle Spatial

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.

14.3 The Welcome Page of Oracle Database Upgrade Assistant Displays Incorrect Version

The Welcome page of Oracle Database Upgrade Assistant displays incorrect version of Oracle 9i. Oracle 9i Release 9.1.0 should read as Oracle 9i Release 9.0.1.

This issue is tracked with Oracle bug 6695802.

14.4 Non-ASCII Characters on Help Navigation Are Not Displayed Properly with UTF-8 encoding

Non-ASCII characters on Help Navigation are not displayed properly and appear to be distorted for most Java GUI conventional components when the operating system locale is UTF-8 enabled, such as Oracle Database Configuration Assistant, Oracle Database Upgrade Assistant, NetCA, NetMgr, Oracle Directory Manager, Oracle WM, and Locale Builder. The issue slightly impacts five translated European languages and three Asian languages, except Japanese. This issue only affects the help navigation tree and has no effects on the help topic window.

Workaround:

UTF-8 is the default encoding of the operating system locale on Linux 4.0 and for the European languages on Linux 3.0. You should change the default locale to the one with native encoding to see the correct characters on the Help Navigation tree. The following is the list of the Oracle recommended locales:

de_DE.iso88591 for German
fr_FR.iso88591 for French
it_IT.iso88591 for Italian
es_ES.iso88591 for Spanish
pt_BR.iso88591 for Brazilian Portuguese
zh_CN.gb18030 for Simplified Chinese
zh_TW.big5 for Traditional Chinese
ko_KR.euckr for Korean

Complete one of the following tasks to change the locale:

Run the following commands to alter the locale on a terminal session temporally:
```
$ LANG=locale
$ export LANG
```
Use this terminal to start the components to see only the help topics. You should start components for other tasks in other terminals that have the default locale.
To alter the system default locale as the operating system administrator, edit the UTF-8 entry to a native encoding in the /etc/sysconfig/i18n file. Then reboot the computer.
To alter the locale in the user login environment file, such as .bash_profile. Add the following lines to the login profile file:
```
$ LANG=locale
$ export LANG
```

With the modified operating system locale encoding, the operating system file system related operations that use non-ASCII characters are affected. For example, creating or renaming a file with non-ASCII file name on operating system is affected by this modification. If you want to keep consistency with the default operating system locale encoding in the file system operations, you should avoid using non-ASCII characters when the workaround second or third is applied, or apply the first workaround to see the help only on the changed locale.

This issue is addressed in Oracle Database 11g (11.1.0.6). Therefore, Oracle recommends you to alter the system default locale or the locale in the user login environment file back to the default encoding (UTF-8) after Oracle Server is upgraded to Oracle Database 11g.

This is tracked with Oracle bug 6503286.

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

Start the database with the NOMOUNT option:

$ sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP NOMOUNT

Create SPFILE from PFILE by entering the following command where pfile_location is usually $ORACLE_BASE/admin/db_name/pfile for Optimal Flexible Architecture compliant database:
```
SQL> CREATE SPFILE=SHARED_LOCATION/SPFILE.ORA FROM PFILE=pfile_location/init.ora
```
Shut down the database:
```
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT
```
Clear the contents of PFILE located at ORACLE_BASE\ORACLE_HOME\dbs\initsid.ora and set the value of SPFILE as SHARED_LOCATION\SPFILE.ORA.
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.

14.6 Refresh From OracleMetaLink Job Fails in Oracle Enterprise Manager Database Control

If you attempt the Refresh from OracleMetaLink job in Oracle Enterprise Manager Database Control, then it displays the following error:

Exception trying to access the repository. java.sql.SQLException:
ORA-12899: value too large for column
"SYSMAN"."MGMT_ARU_PRODUCTS"."PRODUCT_NAME" (actual: 54, maximum: 50)

Workaround:

None. Oracle will release a one-off patch to address this issue.

This issue is tracked with Oracle bug 6755395.

14.7 The sysman Related Errors Are Listed in the oraInstall.err File

When you use Oracle Universal Installer to remove Oracle Database 10g Release 2 (10.2.0.4), some sysman related errors are listed in the oraInstall.err file.

Workaround:

These are benign errors and can be ignored.

This issue is tracked with Oracle bug 6363210.

14.8 Errors Displayed When Upgrading from Oracle Database 10g Release 2 (10.2.0.4)

When upgrading Oracle Database 10g Release 2 (10.2.0.4) to Oracle Database 11g Release 1 (11.1.0.6), the following errors are displayed:

ORA-06550: line 5, column 35:
ORA-06550: line 5, column 1:
ORA-00001: unique constraint
(SYSMAN.PARAMETERS_PRIMARY_KEY) violated
ORA-06512: at "SYSMAN.MGMT_TIME_SYNC", line 108
Oracle_Server.log:ORA-06512: at "SYSMAN.MGMT_TIME_SYNC", line 166
Oracle_Server.log:ORA-06512: at line 2

Workaround:

These errors do not result in any data loss. Therefore, you can ignore these errors.

This issue is tracked with Oracle bug 6705429.

14.9 Incorrect Database Version is Displayed on the Oracle Enterprise Manager Database Control Page After Downgrading

If you downgrade the database from Oracle Database 10g Release 2 (10.2.0.4) to an earlier version, Oracle Enterprise Manager Database Control may not restart after the downgrade. However, the emctl start dbconsole command may appear to have started the database console, but you cannot access the database console pages. The emctl status dbconsole command displays that the database console in fact has not started.

Workaround:

This issue is most likely a result Oracle bug 4505434, which has been fixed in this release but exists in earlier releases. To address this issue, apply the patch for bug 4505434 for the database console version you downgraded to and restart the database console.

This issues is tracked with Oracle bug 6649954.

14.10 Benign Entry in the Silent Log File After Cloning the Database

An entry similar to the following is logged in the silent log file immediately after you clone the database:

File not found: $ Cloned_Oracle_home/ccr/new_ccr/ccr/bin/setupCCR

Workaround:

This entry in the log file is not a error and can be ignored.This issue is tracked with Oracle bug 6721838.

14.11 Incorrect Nodes Displayed in Cloned Oracle Clusterware

On a cloned Oracle Clusterware, the new node does not display the correct node from which you should run a command.

Workaround:

Run the following command to address this issue:

$ ./runInstaller -clone -silent ORACLE_HOME=$ORACLE_HOME ORACLE_HOME_NAME \ 
=Oracle_home_name n_storageTypeVDSK=2 n_storageTypeOCR=2 \
"sl_tableList={first_node:first_node_priv:first_node-vip, \
second_node:second_node_priv:second_node-vip}" \
s_ocrpartitionlocation=location_of_ocr s_votingdisklocation=location_of_voting_disk \
"ret_PrivIntrList={private_interconect_list}" INVENTORY_LOCATION=central_inventory_location -noConfig

Note:

Change the clone command parameter sl_tableList to have the local node as the first entry.

This issue is tracked with Oracle bug 6754695.

14.12 Native Full Outer Join Implementation

To enable a new native full outer join implementation in the database, a user has to set the following underscore parameter:

_optimizer_native_full_outer_join =force

You can set this parameter for the system or for a specific session.

Besides dramatically improving the performance of a full outer join, the new implementation fixes a variety of issues, for examples a variety of ORA-942 (table or view doesn't exists) and ORA-4331 (unable to allocate string bytes of shared memory) errors.

This issue is tracked with Oracle bug 6322672.

14.13 Incorrect Oracle Workspace Manager Displayed After Upgrading to Oracle Database 11g

After upgrading Oracle Database 10g Release 2 (10.2.0.4) to Oracle Database 11g Release 1 (11.1.0.6), the Oracle Workspace Manager version is displayed as 10.2.0.4.3.

This issue is tracked with Oracle bug 6732811.

14.14 ASM Error is Displayed When Creating 10g Release 2 (10.2.0.1) Database on Oracle Clusterware (10.2.0.4)

If you are installing and creating an Oracle Database 10g Release 2 (10.2.0.1) database, which uses ASM storage, after upgrading Oracle Clusterware to version 10.2.0.4, then the following error may be displayed:

An error occurred while executing ASM queries.

Workaround:

This error is benign. Click Continue to proceed with the installation. There is no loss of functionality due to this error.

This issue is tracked with Oracle bug 6791427.

14.15 SETUPCCR Fails if Preset JAVA_HOME Points to an Invalid JDK Home

When CCR is manually configured using setupCCR from a terminal on which JAVA_HOME is pre-defined and if it points to an invalid location or JRE_HOME instead of a valid JDK_HOME, the command fails.

Workaround:

Unset JAVA_HOME and re-invoke setupCCR.

14.16 In Red Hat Enterprise Linux 5 Default Makefile Version does not Support Default DBNAME

The default Makefile version present in the RHEL5 machine is make 3.81. With this version, the default dbname is not recognized by those Oracle clients which are directly called from the Makefile.

Workaround:

You can use either of the following approaches:

Use Makefile version 3.79
Use @dbname whenever username/password is used in the Makefile

14.17 Oracle Clusterware Patching May Encounter Write Errors

When applying the 10.2.0.4 Oracle Clusterware patch set on Linux 32 platforms, under certain circumstances, the following error may occur:

Error in writing to file 'Oracle_Home/jdk/jre/bin/java'

This may happen more frequently if you are running Oracle Clusterware version 10.2 in conjunction with Oracle9i Oracle Real Application (RAC) databases. If you encounter this error, you need to shutdown the GSD on each node of the cluster and then proceed with the installation. Shutting down the GSD will have no impact on any running database instances on the cluster. To do this, perform. the following steps (all steps can be performed from a single node):

Set the ORACLE_HOME environment variable to the Oracle Clusterware home.
Issue the following command to get the list of nodes in the cluster:
```
$ORACLE_HOME/bin/olsnodes
```
Issue the following command, once for each node in the cluster:
```
$ORACLE_HOME/bin/crs_stop ora.nodename.gsd
```

This procedure will shut down the GSD on each node of the cluster without shutting down the rest of the Oracle Clusterware stack, or affecting any of the running database instances on the cluster. Once this is done, proceed with the Oracle Clusterware patchset installation as usual.

Example:

Suppose you are patching a 2 node cluster with node names host1 and host2. The procedure you need to follow is the following:

Log in to host1.
Set the ORACLE_HOME environment variable to your CRS Oracle Home.
Run $ORACLE_HOME/bin/olsnodes. This command will return:

host1

host2
For each node returned by olsnodes, run the command to stop the GSD. In this example one would need to run 2 different commands (all from host1):
```
$ORACLE_HOME/bin/crs_stop ora.host1.gsd
$ORACLE_HOME/bin/crs_stop ora.host2.gsd
```

15 Fixed Platform-Specific Bugs

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

Fixed in Release	Bug Number	Description
10.2.0.2	4747264	WRONG PERMISSIONS AFTER CLIENT INSTALL OF 10GR2 (10.2.0.1)
10.2.0.2	4516865	WRONG PERMISSIONS AFTER INSTALLATION IN OH AND SUBSEQUENT DIRECTORIES
10.2.0.3	4517854	INITIALIZATION OF INTERNAL RECOVERY MANAGER PACKAGE FAILED ORA-01031
10.2.0.3	4930898	FLOATING POINT CALCULATIONS GIVE DIFFERENT RESULTS WHEN CONNECTED TO 10G DB
10.2.0.3	4966320	OCRDUMP -BACKUPFILE FAILED WITH PROT-302
10.2.0.3	5218245	REMAP_FILE_PAGES SUPPORT IN 10.2 IS MISSING CHANGES FROM 9I AND 10.1
10.2.0.4	4698310	ODBC CAUSES UNDEFINED SYMBOL SLEEP ERROR WHEN FAILOVER HAPPENS

16 Patch Set Components

The following table provides a list of patch set components:

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

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

10g Release 2 (10.2.0.4) Patch Set 3 for Linux x86

Oracle® Database

1 Patch Set Overview

2 Components of This Patch Set

3 Accessing the Latest Version of this Document

4 Oracle Universal Installer Version Requirements

5 Patch Set Documentation

6 System Requirements

7 Preinstallation Tasks

7.1 Review Known Preinstallation Issues

7.1.1 Upgrading Oracle E-Business Suite Databases

7.1.2 Upgrading Installations that use Physical or Logical Standby Databases

7.1.3 Upgrading Installations that use Java Virtual Machine or Oracle interMedia

7.1.4 Upgrading Oracle Clusterware

7.1.5 Notes to Oracle OLAP Users

7.1.6 Disabling Oracle Database Vault

7.2 Identify the Oracle Database Installation

7.3 Check Postrelease Updates

7.4 Download and Extract the Installation Software

7.5 Update Oracle Time Zone Definitions

7.6 Set the ORACLE_HOME and ORACLE_SID Environment Variables

7.7 Stop All Processes

7.7.1 Stopping All Processes for a Single Instance Installation

7.7.2 Stopping All Processes for an Oracle Clusterware Installation

7.7.3 Stopping All Processes for an Oracle RAC Installation

7.8 Back Up the System

8 Installation Tasks

8.1 Installing the Oracle Database 10g Patch Set Interactively

8.2 Installing the Oracle Database 10g Patch Set Noninteractively

9 Postinstallation Tasks

9.1 Updating Oracle Time Zone Definitions

9.2 Upgrading Earlier Oracle Database to Oracle Database 10g Release 2 (10.2.0.4)

9.2.1 Upgrading Earlier Oracle Database Releases to Oracle Database 10g Release 2 (10.2.0.4)

9.2.2 Upgrading a Release 9.2 Database Not Using Oracle Label Security

9.3 Upgrading Oracle Database 10g Release 10.2.0.x to Oracle Database 10g Release 10.2.0.4

9.3.1 Upgrading a Release 10.2 Database using Oracle Database Upgrade Assistant

9.3.2 Manually Upgrading a Release 10.2 Database

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

9.5 Enabling Oracle Database Vault

9.6 Configuring Oracle Configuration Manager in a Cloned Oracle Home

10 Downgrading Oracle Database Vault

11 Removing the Patch Set Software

11.1 Removing the Patch Set Software for Single Instance Installation

11.2 Removing the Patch Set Software for Oracle RAC Installation

12 Removing Configuration and Deleting CCR for OCM Configured Oracle Database 10g Release 2 (10.2.0.4)

13 Reinstalling the Patch Set Software

14 Known Issues

14.1 Oracle Scheduler External Jobs

14.2 Upgrading Preconfigured Standard Edition Databases

14.3 The Welcome Page of Oracle Database Upgrade Assistant Displays Incorrect Version

14.4 Non-ASCII Characters on Help Navigation Are Not Displayed Properly with UTF-8 encoding

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

14.6 Refresh From OracleMetaLink Job Fails in Oracle Enterprise Manager Database Control

14.7 The sysman Related Errors Are Listed in the oraInstall.err File

14.8 Errors Displayed When Upgrading from Oracle Database 10g Release 2 (10.2.0.4)

14.9 Incorrect Database Version is Displayed on the Oracle Enterprise Manager Database Control Page After Downgrading

14.10 Benign Entry in the Silent Log File After Cloning the Database

14.11 Incorrect Nodes Displayed in Cloned Oracle Clusterware

14.12 Native Full Outer Join Implementation

14.13 Incorrect Oracle Workspace Manager Displayed After Upgrading to Oracle Database 11g

14.14 ASM Error is Displayed When Creating 10g Release 2 (10.2.0.1) Database on Oracle Clusterware (10.2.0.4)

14.15 SETUPCCR Fails if Preset JAVA_HOME Points to an Invalid JDK Home

14.16 In Red Hat Enterprise Linux 5 Default Makefile Version does not Support Default DBNAME

14.17 Oracle Clusterware Patching May Encounter Write Errors

15 Fixed Platform-Specific Bugs

16 Patch Set Components

17 Documentation Accessibility

Oracle Copyright and Trademark Notice

Copyright Notice

Trademark Notice

你可能感兴趣的:(10g Release 2 (10.2.0.4) Patch Set 3 for Linux x86)