Oracle® Database Patch Set Notes

10g Release 2 (10.2.0.2) Patch Set for HP-UX

Itanium

Oracle® Database
Patch Set Notes

10g Release 2 (10.2.0.2) Patch Set for HP-UX Itanium

April 2006

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

 Patch Set Overview

 Oracle Universal Installer Version Requirements

 Patch Set Documentation

 System Requirements

 Preinstallation Tasks

 Installation Tasks

 Postinstallation Tasks

 Removing the Patch Set Software

 Reinstalling the Patch Set Software

 Known Issues

 Fixed Platform-Specific Bugs

 Patch Set Components

 Documentation Accessibility

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

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.2, 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 the 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:

 Oracle Database Patch Set Notes, 10g release 2 (10.2.0.2) Patch Set for
HP-UX Itanium (this document)
 Oracle Database List of Bugs Fixed, 10g release 2 (10.2.0.2) 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.2) Patch Set for
HP-UX Itanium

This document provides:

 System requirements and information about how to install or reinstall the

patch set
 A list of all bugs fixed to date that are specific to Oracle Database for HP-
UX Itanium

 A list of known issues relating to Oracle Database on HP-UX Itanium

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

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:
  Operating System
o HP-UX 11i v2 (11.23)

 Patches

o PHKL_34374

Note:

This patch from Hewlett-Packard improves the reboot

functionality in Oracle Clusterware. It helps in diagnosis after
reboot is initiated by Oracle Clusterware. This patch is
recommended for RAC environments. Single Instance
environment will not be affected.

 Oracle Database (10.2.0.1)

5 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

 Set the ORACLE_HOME and ORACLE_SID Environment Variables

 Stop All Processes

 Back Up the System

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.

 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 OLAP users

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 release 2 (10.2.0.1)

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 (Java VM) or Oracle
interMedia, install the Oracle Database 10g Products installation type from the
Oracle Database 10g Companion CD before installing the 10.2.0.2 patch set. For
information about installing the Oracle Database 10g Products installation type
from the Companion CD, see the Oracle Database 10g Installation Guide or the
Oracle Database 10g Companion CD Installation Guide. This installation type
includes the Natively Compiled Java Libraries (NCOMP) files to improve Java
performance. If you do not install the NCOMP files, the ORA-
29558:JAccelerator (NCOMP) not installed error occurs when a
database that uses Java VM 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 Real Application Clusters (RAC) Oracle home. Therefore,
you should always upgrade Oracle Clusterware before you upgrade RAC.

5.1.5 Notes to OLAP users

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

If you are moving your 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:

1. Log on to OracleMetalink.
2. Click Advanced at the top of the OracleMetalink page.

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

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 Applications Cluster
(RAC) 10g release 10.2.0.1 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 p4547817_10202_HPUX-IA64.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:

3. $ unzip p4547817_10202_HPUX-IA64.zip
4.

5.5 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.6 Stop All Processes

Stop all listeners and other processes running in the Oracle home directory,
where you need to install the patch set.
 Note:

If you shut down ASM instances, you must first shut down all
database instances that use ASM, even if these databases run
from different Oracle homes.

 If you are upgrading a single instance installation, shut down the following
Oracle Database 10g processes before installing the patch set:

Note:

You must perform these steps in the order listed.

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.

Note:

Before you shutdown all processes that are monitored by

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 the ASM instance, if the ASM instance is running in the
Oracle home directory, where you need to install the patch set.

4. Shut down all listeners running in the Oracle home directory, where
you need to install the patch set.
 5. Shut down the Oracle Cluster Synchronization Services (CSS)
daemon as the root user:

6. $ oracle_home/bin/crsctl stop crs

7.
 If you are upgrading a Oracle Clusterware installation, shut down the
following Oracle Database 10g processes before installing the patch set:

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.

Note:

Before you shutdown all processes that are monitored by

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 RAC instances on all nodes. To shut down all RAC
instances for a database, enter the following command where
db_name is the name of the database:
3. $ oracle_home/bin/srvctl stop database -d db_name
4.
5. Shut down all ASM instances on all nodes. To shut down an ASM
instance, enter the following command where node is the name of
the node where the ASM instance is running:

6. $ oracle_home/bin/srvctl stop asm -n node

7.
 8. Stop all node applications on all nodes. To stop node applications
running on a node, enter the following command where node is the
name of the node where the applications are running:

9. $ oracle_home/bin/srvctl stop nodeapps -n node

10.
11. Shut down the Oracle Clusterware process by entering the
following command on all nodes as the root user:

12. # crs_home/bin/crsctl stop crs

13.

Note:

In these examples, crs_home is the Oracle Clusterware home

directory where the Oracle Clusterware 10g installation that you
want to upgrade is installed.

Note:

If the Oracle Clusterware installation is not on a shared Oracle

home you can upgrade the Oracle Clusterware installation one
node at a time. To do this, perform the preceding steps only on
the first node that you are upgrading, then follow the instructions
on the installer screen.

 If you are upgrading a RAC installation, shut down the following Oracle
Database 10g processes before installing the patch set:

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.

Note:

Before you shutdown all processes that are monitored by

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 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 RAC instances for a database, enter the following
command where db_name is the name of the database:
3. $ oracle_home/bin/srvctl stop database -d db_name
4.
5. Shut down all ASM instances on all nodes. To shut down an ASM
instance, enter the following command where node is the name of
the node where the ASM instance is running:

6. $ oracle_home/bin/srvctl stop asm -n node

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

9. $ oracle_home/bin/srvctl stop listener -n node [-l

listenername]
10.

5.7 Back Up the System

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

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:

 To install the patch set interactively, see the "Installing the Oracle
Database 10g Patch Set Interactively" section.
 To install the patch set noninteractively, see the "Installing the Oracle
Database 10g Patch Set Noninteractively" section.

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
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 patchset Oracle Database 10g
Release 2 Patch Set 1
10.2.0.2.0

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, 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).
2. Enter the following commands to start Oracle Universal Installer, where
patchset_directory is the directory where you unpacked the patch
set software:
3. % cd patchset_directory/Disk1
4. % ./runInstaller
5.
6. On the Welcome screen, click Next.

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

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

9. directory_path/stage/products.xml
10.
11. In the Name field in the Destination section, select the name of the
Oracle home that you want to update from the drop down list, then click
Next.

12. If you are installing the patch set on a RAC cluster, click Next when the
Selected Nodes screen appears.

13. On the Summary screen, click Install.

This screen lists all of the patches available for installation.

14. When prompted, run the $ORACLE_HOME/root.sh script as the root

user. If you are applying the patch set to a RAC installation, then run the
root.sh script on each node of the cluster.

Note:

If you are applying this patch set to a Oracle Clusterware

installation:
 If you shut down all Oracle Clusterware services on
all nodes as described in the "Preinstallation Tasks"
section before starting the installation, then complete all of
the steps except the first step in the instructions displayed
by the installer screen.
 If you did not shut down all Oracle Clusterware
services on all nodes, complete all of the steps in the
 instructions displayed by the 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.

15. 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 RAC installations, make sure the CLUSTER_NODES variable

specifies all of the nodes used in the original 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:
4. % ./runInstaller -silent -responseFile response_file
5.
6. After the installation, run the $ORACLE_HOME/root.sh script as the
root user. If you are applying the patch set to a RAC installation, then run
the root.sh script on each node of the cluster.

Note:

If you are applying this patch set to a Oracle Clusterware

 installation:
 If you shut down all Oracle Clusterware services on
all nodes as described in the "Preinstallation Tasks"
section before starting the installation, then complete all of
the steps except the first step in the
CRS_HOME/install/readme.txt file.

 If you did not shut down all Oracle Clusterware

services on all nodes, complete all of the steps in the
CRS_HOME/install/readme.txt file.

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.

 Upgrading Earlier Oracle Database 10g Release 1 to Oracle Database

10g Release 2 (10.2.0.2)
 Upgrading Oracle Database 10g Release 10.2.0.1 to Oracle Database
10g Release 10.2.0.2

 Running the configPatch.pl Script on a RAC Cluster

 Running changePerm.sh script on an Oracle database server home

7.1 Upgrading Earlier Oracle Database 10g Release 1 to Oracle

Database 10g Release 2 (10.2.0.2)

Review the following sections before upgrading an earlier Database to Oracle

Database 10g release 2 (10.2.0.2):

7.1.1 Upgrading an Earlier Oracle Database Release 1 (8i, 9i, or 10g) to

Oracle Database 10g Release 2 (10.2.0.2)

For information about upgrading Oracle databases from an earlier Oracle

database release 1 (8i, 9i, or 10g), see the Oracle Database Upgrade Guide.

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

7.1.2 Upgrading a Release 9.2 Database Not Using OLS

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

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

7.2 Upgrading Oracle Database 10g Release 10.2.0.1 to Oracle

Database 10g Release 10.2.0.2

Review the following sections before upgrading an Oracle Database 10g release
10.2.0.1 to Oracle Database 10g release 10.2.0.2:

7.2.1 Required Preupgrade Checks

Review the following sections before upgrading a database.

7.2.1.1 Check SYSTEM Tablespace Size

If JServer is part of the installation ensure that there is at least 10 MB of free

space allocated to the SYSTEM tablespace.

7.2.1.2 Check SYSAUX Tablespace Size

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

7.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization

Parameters

Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE

initialization parameters as follows:

1. Start the database:

2. SQL> STARTUP NOMOUNT
3.
4. 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):

5. SQL> SHOW PARAMETER PFILE;

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

7. Determine the current values of these parameters:

8. SQL> SHOW PARAMETER SHARED_POOL_SIZE
9. SQL> SHOW PARAMETER JAVA_POOL_SIZE
10.
11. If the system is using a server parameter file:

a. If necessary, set the value of the SHARED_POOL_SIZE initialization

parameter to at least 150 MB:

b. SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M'

SCOPE=spfile;
c.
d. If necessary, set the value of the JAVA_POOL_SIZE initialization
parameter to at least 150 MB:

e. SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M'

SCOPE=spfile;
f.
12. 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).

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

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.

14. Shut down the database:

15. SQL> SHUTDOWN
16.
7.2.2 Upgrade the 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 RAC installations, start listener on each node of the cluster as follows:

3. $ srvctl start listener -n nodename

4.
5. If you are using ASM, start the ASM instance.

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

7. $ lsnrctl start
8.

Note:

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

9. For single-instance installations, use SQL*Plus to log in to the database

as the SYS user with SYSDBA privileges:
10. $ sqlplus /nolog
11. SQL> CONNECT / AS SYSDBA
12.
13. For RAC installations:
 a. Use SQL*Plus to log in to the database as the SYS user with
SYSDBA privileges:

b. $ sqlplus /nolog
c. SQL> CONNECT / AS SYSDBA
d. SQL> STARTUP NOMOUNT
e.
f. Set the CLUSTER_DATABASE initialization parameter to FALSE:

g. SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE

SCOPE=spfile;
h.
i. Shutdown the database:

j. SQL> SHUTDOWN
k.
14. Enter the following SQL*Plus commands:

15. SQL> STARTUP UPGRADE

16. SQL> SPOOL patch.log
17. SQL> @?/rdbms/admin/catupgrd.sql
18. SQL> SPOOL OFF
19.
20. 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.

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

problems.
22. Restart the database:

23. SQL> SHUTDOWN

24. SQL> STARTUP
25.
26. 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.

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

28.
 Note:

When the 10.2.0.2 patch set is applied to an Oracle Database

10g Standard Edition database or Standard Edition One
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

29. If you are using the Oracle Recovery Manager catalog, enter the following
command:
30. $ rman catalog username/password@alias
31. RMAN> UPGRADE CATALOG;
32.
33. For RAC installations:

a. Set the CLUSTER_DATABASE initialization parameter to TRUE:

b. SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE

SCOPE=spfile;
c.
d. Restart the database:

e. SQL> SHUTDOWN
f. SQL> STARTUP
g.
h. Start any processes that you want to use:

i. $ srvctl start service -d db_name -s service_name

j.

7.3 Running the configPatch.pl Script on a RAC Cluster

Note:

These instructions do not apply to RAC installations where the

nodes of the cluster share the same Oracle home.
The configPatch.pl script updates the Oracle Enterprise Manager Database
Control files. Although Oracle Universal Installer copies the configPatch.pl
script to all of the Oracle homes on the cluster, it runs the script only on the node
running Oracle Universal Installer.

If you install this patch on a RAC installation that does not use a shared Oracle
home directory, you must manually run the
$ORACLE_HOME/sysman/install/configPatch.pl script on each node of
the cluster, except on the node from which you ran Oracle Universal Installer.

7.4 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 patchset 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 your directory to:

$ 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 RAC home, then you will need to run this
script on all the nodes.
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.2
Oracle home to perform necessary downgrade actions. After the 10.2.0.1 release
is restored, the catrelod.sql script is run from 10.2.0.1 Oracle home to reload
the 10.2.0.1 release packages and views.

Perform the following steps for backing out from the 10.2.0.x patch release:

1. Before restoring the Oracle home to the original release, perform the
following steps:
2. $ sqlplus /nolog
3. SQL> connect / AS SYSDBA
4. SQL> SHUTDOWN
5. SQL> STARTUP DOWNGRADE
6. SQL> SPOOL downgrade.out
7. SQL> @?/rdbms/admin/catdwgrd.sql
8. SQL> SHUTDOWN IMMEDIATE
9.
10. Review the downgrade.out file for errors.

11. Copy the 10.2.0.2 version of rdbms/admin/catrelod.sql out of the

Oracle home to save it.

Note:

The 10.2.0.1 version of catrelod.sql script always runs

utlip.sql script to invalidate all PL/SQL packages. To avoid
running utlip.sql script when you reload the 10.2.0.1
packages and views, you can use the 10.2.0.2 version of
catrelod.sql if you save it before restoring the original Oracle
home.

12. Restore the Oracle10g installation and Central Inventory (see

/etc/oraInst.loc) that you backed up before applying the patch set.
 13. After restoring the original Oracle home, copy the saved version of
catrelod.sql script into the restored Oracle home rdbms/admin
directory, and then perform the following steps:

14. $ sqlplus /nolog

15. SQL> connect / AS SYSDBA
16. SQL> STARTUP UPGRADE
17. SQL> SPOOL reload.out
18. SQL> @?/rdbms/admin/catrelod.sql
19.
20. Shut down the database:

21. SQL> SHUTDOWN IMMEDIATE

22.
23. Review the reload.out file for errors.

Note:

Ignore the ORA-29844 and ORA-31085 errors found in the

reload.out file. These errors are tracked with Oracle bugs
4758112 and 4425495 respectively.

Note:

After reloading the 10.2.0.1 release, the version numbers for

Data Mining and OLAP Analytic Workspace remain at 10.2.0.2.
These issues are tracked with Oracle bugs 4758695 and
4751917.

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

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

2. Enter the following commands to start Oracle Universal Installer, where

patchset_directory is the directory where you unpacked the patch
set software:
3. $ cd patchset_directory/Disk1
4. $ ./runInstaller
5.
6. If you are installing the patch on a RAC cluster, click Next on the Selected
Nodes screen.

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

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

9. directory_path/stage/products.xml
10.
11. Select the Oracle home that you want to upgrade in the Name field in the
Destination section, then click Next.

Note:
 If you are not sure of the name of the Oracle home, click
Installed Products to determine the name of the Oracle home
that you want to upgrade.

The Available Product Component screen appears. This screen contains a

list of all components that have been patched by the original patch set
installation. These components are grayed out, indicating they cannot be
selected for installation.

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

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

reinstall.

14. Repeat the process for each patch bundled in the patch set, then click
Next.
15. On the Summary screen, verify the list of patches to be reinstalled, then
click Install.

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

 Upgrading Oracle Database Software Version Using Oracle Data Guard

and SQL Apply
 Oracle Listener Issue

 Database Creation Assistant Error Message

 Invalid Link to Monitor in Memory Access Mode Feature

 Oracle Scheduler External Jobs

 Upgrading Preconfigured Standard Edition Databases

 Oracle Notification Server Issue in Shared Oracle Clusterware Home

  DB Cloning Through EM Console Fails

10.1 Upgrading Oracle Database Software Version Using Oracle Data

Guard and SQL Apply

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 patchset release
10.2.0.1 to the 10.2.0.2 patchset 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.

For complete information and instructions, see OracleMetaLink note 300479.1.

10.2 Oracle Listener Issue

If you apply this patch set, the listener might hang intermittently in both RAC, and
nonRAC environments.

Workaround: Perform the following steps:

1. Rename the $ORACLE_HOME/opmn/conf/ons.config file by entering

the following commands:
2. cd $ORACLE_HOME/opmn/conf
3. mv ons.config ons.config.orig
4.

Alternatively, change each port value in the

$ORACLE_HOME/opmn/conf/ons.config file to an unused port.

5. Restart the listener.

This issue is tracked with Oracle bug 3881276.

10.3 Database Creation Assistant Error Message

While creating a new database using Database Creation Assistant (DBCA), you
may receive the following error message:

11393 [Thread-218] ERROR emSDK.config - Unable to release

lock on file:/var/tmp/EM_TARGET_INSTALLER.lk
11394 [Thread-218] ERROR emSDK.config - Failed to close
output stream on file:/var/tmp/EM_TARGET_INSTALLER.lk
11421 [Thread-218] ERROR emSDK.config - Unable to release
lock on file:/var/tmp/EM_TARGET_INSTALLER.lk
11421 [Thread-218] ERROR emSDK.config - Failed to close
output stream on file: /var/tmp/EM_TARGET_INSTALLER.lk

Nonetheless, database creation, and Enterprise Manager configuration succeed.

You can ignore this message.

This issue is tracked with Oracle bug 4344301.

10.4 Invalid Link to Monitor in Memory Access Mode Feature

Do not try a link to the Monitor in Memory Access Mode feature in your database
screen, if you find one. This feature is not available in Enterprise Manager
Database Control 10.2.0.2 release and attempting this link may stop an agent
from responding.

This issue is tracked with Oracle bug 4866231.

10.5 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.2, 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.6 Upgrading Preconfigured Standard Edition Databases

If you are using an Oracle Database release 10.2.0.1 preconfigured Standard

Edition database, then the database contains the following components that are
not supported by the Standard Edition:

 Oracle Data Mining

 Oracle OLAP Catalog

 Oracle OLAP Analytic Workspace

 Oracle OLAP API

 Spatial

 OLAP SQL Scripts

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.7 Oracle Notification Server Issue in Shared Oracle Clusterware

Home

If you apply this patch set, the Oracle Notification Server might go down on a
shared Oracle Clusterware home.

Workaround: Perform the following steps:

1. Add "usesharedinstall=true" entry in the

$ORACLE_HOME/opmn/conf/ons.config file by entering the following
commands:
2. cd $CRS_HOME/opmn/conf
3. $ cat >> ons.config
4. usesharedinstall=true
5. ctrl - D (press Ctrl-D)
6.
7. $ cd $ORACLE_HOME/opmn/conf
8. $ cat >> ons.config
9. usesharedinstall=true
10. ctrl - D
11.

12. Restart the Oracle Notification Server.

This issue is tracked with Oracle bug 5171434.

10.8 DB Cloning Through EM Console Fails

While running Clone database, through EM console, job execution fails. This
occurs during Step: Add Temporary Files. Following is the error thrown in the EM
screen, when job status link is clicked:

Output Log
ERROR: command process interrupted before exit

Workaround:

Please apply the ARU Patch number #8410619 and try the DB cloning.

This issue is tracked with Oracle bug 5169299.

11 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 Bug
Release Number Description
10.2.0.2 4674108 SRV: ORA-7445 STACK TRACE SEEMS
INCOMPLETE
10.2.0.2 4709673 ORA-27061, CAN'T STARTUP DB WHEN BIG
SGA(30GB) IS SET

12 Patch Set Components

The following table provides a list of patch set components:

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

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.2) Patch Set
for HP-UX Itanium

Copyright © 2006 Oracle. All rights reserved.

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

The information contained in this document is subject to change without notice. If

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

If the Programs are delivered to the United States Government or anyone

licensing or using the Programs on behalf of the United States Government, the
following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related

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

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

Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle

Corporation and/or its affiliates. Other names may be trademarks of their
respective owners.

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