Manual de Procedimiento - Actualizaciópn Oracle 10g, Parches de Seguridad

Oracle Database Patch Set Notes
10g Release 2 (10.2.0.4) Patch Set 3 for

for Linux x86
Oracle Database
Patch Set Notes
10g Release 2 (10.2.0.4) Patch Set 3 for for Linux x86
March 2008
These patch set notes accompany the Oracle Database release 10.2.0.4
patch set. This document contains the following sections:
Patch Set Overview
Components of This Patch Set
Accessing the Latest Version of this Document
Oracle Universal Installer Version Requirements
Patch Set Documentation
System Requirements
Preinstallation Tasks
Installation Tasks
Postinstallation Tasks
Downgrading Oracle Database Vault
Removing the Patch Set Software
Removing Configuration and Deleting CCR for OCM Configured

Oracle Database 10 Release 2 (10.2.0.4)
Reinstalling the Patch Set Software
Known Issues
Fixed Platform-Specific Bugs
Patch Set Components
Documentation Accessibility
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:
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.
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-64 (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:
To locate document 316900.1:
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-64
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-64
A list of known issues relating to Oracle Database on Linux x86-64
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
o Asianux 2.0
o Asianux 3.0
o Oracle Enterprise Linux 4.0/Oracle VM
o Oracle Enterprise Linux 5.0/Oracle VM
o Red Hat Enterprise Linux AS/ES 3.0
o Red Hat Enterprise Linux AS/ES 4.0/Oracle VM
o Red Hat Enterprise Linux AS/ES 5.0/Oracle VM
o SUSE Linux Enterprise Server (SLES) 9
o 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:
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:
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.
See Also:
OracleMetaLink document 293658.1 for more information
about the ORA-29558: JAccelerator (NCOMP) not
installed error
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:
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:
1. 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:
2. $ orapwd file=$ORACLE_HOME/dbs/orapwsid
password=syspasswd force=y nosysdba=n
3. 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 6 that follows.
4. 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
5. Turn off Oracle Database Vault.
6. 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
7. Start the database:

For Oracle RAC:
$ srvctl start database -d db_name

"SYS/SYS_password as SYSDBA"
For Single Instance:
$ sqlplus /nolog
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP
8. Unlock the DVSYS account and set the password:
9. SQL> ALTER USER DVSYS ACCOUNT UNLOCK;

10. SQL> ALTER USER DVSYS IDENTIFIED BY DVSYS;
11.
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. You should then cross-check this
by executing
opatch lsinventory -all

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:
To locate this document:
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:
1. Download the p6810189_10204_LINUX-x86-64.zip patch set

installation archive to a directory that is not the Oracle home
directory or under the Oracle home directory.
2. Enter the following command to unzip and extract the installation
files:
3. $ unzip p6810189_10204_LINUX-x86-64.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.
1. 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:
2. SELECT version FROM v$timezone_file;

o If this query reports version 4, no action is required; in this
case, continue with steps described in section 7.6.
o 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.
3. 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.
4. 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:
$ export PATH=$ORACLE_HOME/bin:
$ORACLE_HOME/bin/OPatch:$PATH:
$ ORACLE_HOME=Oracle_home
$ ORACLE_SID=sid
$ export ORACLE_HOME ORACLE_SID
C shell:
$ export PATH=$ORACLE_HOME/bin:
$ORACLE_HOME/bin/OPatch:$PATH:
% 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
See also:
Appendix F, "How to Stop Processes in an Existing Oracle
Real Application Clusters Database, and How to Perform
Oracle Clusterware Rolling Upgrades" of Oracle Database
Oracle Real Application Clusters Installation Guide.
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:
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:
2. $ emctl stop dbconsole

3. $ isqlplusctl stop
4. $ 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.
5. Shut down all database instances running in the Oracle home

directory, where you need to install the patch set.
6. Shut down all listeners running in the Oracle home directory,
where you need to install the patch set.
7. 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:
o Bourne, Bash, or Korn shell:
o $ export ORACLE_SID=+ASM
o $ export ORACLE_HOME=ASM_HOME
o C shell:
o % setenv ORACLE_SID +ASM

o % setenv ORACLE_HOME ASM_HOME
Enter the following command to Shut down the Automatic Storage
Management instance:
$ sqlplus /NOLOG
SQL> SHUTDOWN IMMEDIATE
8. For Automatic Storage Management, to shut down the Oracle
Cluster Synchronization Services daemon enter the following
command as the root user:
9. # $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:
1. Shut down all processes in the Oracle home on the node that
might be accessing a database, for example Oracle Enterprise
Manager Database Control or iSQL*Plus:

4. $ lsnrctl stop
Note:
outage.
5. Shut down all services in the Oracle home on the node that might
be accessing a database:
6. $ srvctl stop service -d db_name [-s

service_name_list [-i inst_name]]
7. 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:
8. $ srvctl stop instance -d db_name -i inst_name

9. 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:
10. $ srvctl stop asm -n node

11.
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:
12. # srvctl stop nodeapps -n node

13.
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:
a.
Log in as the root user and enter the

following command to shut down the Oracle
Clusterware:
b. # CRS_home/bin/crsctl stop crs

c.
Run the root102.sh script to automatically

start the Oracle Clusterware on the patched node:
d. # CRS_home/install/root102.sh
14.
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:
a. Enter the following command to shut down the Oracle
Clusterware:

c. Run the root102.sh script to automatically start the Oracle
Clusterware on the patched node:
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.
1. Shut down all processes in the Oracle home on each node that

4. $ lsnrctl stop
Note:
outage.
5. Shut down all services in the Oracle home on each node that might

7. Shut down all Oracle RAC instances on all cluster nodes by
entering the following command where db_name is the name of
the database:
8. $ srvctl stop database -d db_name
9. 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:

11.
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:
12. # srvctl stop nodeapps -n node

13.
Shut down the Oracle Clusterware processes by entering the
following command on all nodes as the root user:
14. # CRS_home/bin/crsctl stop crs

15.
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:
a.
Log in as the root user and enter the

following command to shut down the Oracle
Clusterware:

c.
Run the root102.sh script to automatically

start the Oracle Clusterware on the patched node:
7.7.3 Stopping All Processes for an Oracle RAC Installation
Shut down the following Oracle Database 10g processes before installing
the patch set:
1. Shut down all processes in the Oracle home on each node that

Note:
outage.
4. Shut down all services in the Oracle home on each node that might

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

8. 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:
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.
10.
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:
11. $ srvctl stop listener -n node [-l listenername]
Note:
Using a logical standby database, you can upgrade
Oracle Database software and patch sets with almost no
downtime. Using Data Guard SQL Apply, you can perform
a rolling upgrade of the Oracle Database software from
release 10.2.0.1 to the current patch set release. During
a rolling upgrade, you can run different releases of
Oracle Database on the primary and logical standby
databases, while you upgrade them, one at a time,
incurring minimal downtime on the primary database.
See also:
Chapter 11, "Using SQL Apply to Upgrade the Oracle
Database" of Oracle Data Guard Concepts and
Administration.
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.
See also:
Oracle Database Backup and Recovery User's Guide for
more information.
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.
1. Log in as the oracle user.

2. If you are not installing the software on the local computer, then
run the following command on remote machine:
o $ export DISPLAY=localhost:0.0
o C shell:
o % 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]
3. Enter the following commands to start Oracle Universal Installer,
where patchset_directory is the directory where you unpacked
the patch set software:
4. % cd patchset_directory/Disk1
5. % ./runInstaller
6. On the Welcome screen, click Next.
7. 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.
8. If you are installing the patch set on an Oracle RAC cluster, click
Next when the Selected Nodes screen appears.
9. On the Product-specific Prerequisite Checks screen, correct any

reported errors, and click Next.
10.
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.
11.
On the Summary screen, click Install.
This screen lists all of the patches available for installation.

12.
When prompted, run the $ORACLE_HOME/root.sh script as
the root user. If you are applying the patch set to an 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.
o
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.

o
Before you add a new node, ensure that you

run rootpre.sh script as the root user on the
new node.
13.
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:
1. Copy the response file template provided in the response
directory where you unpacked the patch set archive file.
2. Edit the values for all fields labeled as <Value Required> as
described by the comments and examples in the template.
Note:
For Oracle RAC installations, make sure the
CLUSTER_NODES variable specifies all of the nodes used
in the original Oracle RAC installation.
3. To run Oracle Universal Installer, enter a command similar to the

following, where response_file is the full path to the response
file that you edited:
4. $ ./runInstaller -silent -responseFile
response_file
5. After the installation, run the $ORACLE_HOME/root.sh script as
the root user. If you are applying the patch set to an 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:
1. You can use one of the following methods check if Oracle Label
Security is installed:
o If the following script exists on the computer, Oracle Label
Security is installed:
o $ORACLE_HOME/rdbms/admin/catnools.sql
o 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.
2. Use the following commands to check if Oracle Label Security is
installed with the 9.2 database:
3. $ sqlplus
4. SQL> CONNECT SYS AS SYSDBA
5. Enter password:password
6. 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:
1. Use Oracle Universal Installer release 9.2 to install Oracle Label
Security using the Custom installation type.
2. Run the $ORACLE_HOME/rdbms/admin/catnools.sql script with
the SYSDBA privilege to remove Oracle Label Security components
from the database.
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.
1. Log in as the Oracle software owner user.

2. Set the values for the environment variables $ORACLE_HOME,
$ORACLE_SID and $PATH.
3. For single-instance installations, if you are using Automatic
Storage Management, start the Automatic Storage Management
instance.
4. For Oracle single-instance installations, start the listener as
follows:
5. $ lsnrctl start
6. 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:
a. On the Welcome screen, click Next.
b. 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.
c. On the Recompile Invalid Objects screen, select the

Recompile the invalid objects at the end of upgrade
option, then click Next.
d. 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.
e. On the Summary screen, check the summary, then click
Finish.
f. 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.
7. If you are using the Oracle Recovery Manager catalog, enter the
following command:
8. $ rman catalog username/password@alias

9. RMAN> UPGRADE CATALOG;
10.
For Oracle RAC installations, start any database services that
you want to use by entering the following command:
11. $ srvctl start service -d db_name -s service_name

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
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:
1. Run the Pre-Upgrade Information Tool
2. Upgrading a Release 10.2 Database
3. 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:
1. Start the database in the UPGRADE mode:
2. SQL> STARTUP UPGRADE

3. Set the system to spool results to a log file for later analysis:
4. SQL> SPOOL upgrade_info.log

5. Run the Pre-Upgrade Information Tool:
6. SQL> @?/rdbms/admin/utlu102i.sql
7. Turn off the spooling of script results to the log file:
8. 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

0204-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.
--> SYSAUX tablespace is adequate for the upgrade.
--> TEMP tablespace is adequate for the upgrade.
--> EXAMPLE tablespace is adequate for the upgrade.
.
********************************************************
**************
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.
1. Log in as the Oracle software owner user.

2. For Oracle RAC installations, start listener on each node of the
cluster as follows:
3. $ srvctl start listener -n node
4. If you are using Automatic Storage Management, start the

Automatic Storage Management instance.
5. For single-instance installations, start the listener as follows:
6. $ lsnrctl start
7. For single-instance installations, use SQL*Plus to log in to the
database as the SYS user with SYSDBA privileges:
8. $ sqlplus /nolog
10. Enter password:SYS_password
Users of single-instance installations now proceed to step 7.
11.
For Oracle 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 SYS AS SYSDBA
d. Enter password: SYS_password
e. SQL> STARTUP NOMOUNT
f. Set the CLUSTER_DATABASE initialization parameter to
FALSE:
g. SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE

SCOPE=spfile;
h. Shut down the database:
i. SQL> SHUTDOWN
12.
13.
14.
15.
16.
Enter the following SQL*Plus commands:
SQL>
SQL>
SQL>
SQL>
STARTUP UPGRADE
SPOOL patch.log
@?/rdbms/admin/catupgrd.sql
SPOOL OFF
17.
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.
18.
If necessary, rerun the catupgrd.sql script after correcting
any problems.
19.
Restart the database:
20. SQL> SHUTDOWN IMMEDIATE

21. SQL> STARTUP
22.
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.
23. SQL> @?/rdbms/admin/utlrp.sql

24.
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
25.
Run the following command to check the status of all the
components after the upgrade:
26. 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.
27.
If you are using the Oracle Recovery Manager catalog, enter
the following command:
28. $ rman catalog username/password@alias

29.
For Oracle RAC installations:

a. Set the CLUSTER_DATABASE initialization parameter to
TRUE:
b. SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE

SCOPE=spfile;
c. Restart the database:
d. SQL> SHUTDOWN IMMEDIATE

e. SQL> STARTUP
f. Start any database services that you want to use:
g. $ srvctl start service -d db_name -s

service_name
30.
To configure and secure Enterprise Manager follow these
steps:
Ensure the database and Listener are operational.
a. In the case of a single instance, execute
b. emca -upgrade db
c. In the case of Oracle Real Application Clusters (RAC),
execute
d. 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:
1. Change to the install directory by using the following command:
2. $ cd $ORACLE_HOME/install
3. 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:
1. Restart the database:
For a single-instance database, use the following commands:
sqlplus SYS "AS SYSDBA"

Enter password:
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

2. Connect AS SYSDBA and run the following SQL statements:
3. SQL> DROP FUNCTION DVSYS.REALM_SDML_AUTHORIZED ;

4. SQL> DROP PROCEDURE
DVSYS.SYNCHRONIZE_POLICY_FOR_OBJECT;
5. SQL> DECLARE
6.
CURSOR stmt IS
7.
SELECT u.name, o.name,
r.pname
8.
FROM user$ u, obj$ o,
rls$ r
9.
WHERE u.user# = o.owner#
10.
AND r.obj# = o.obj#
11.
AND
bitand(r.stmt_type,65536) > 0;
12.
13.
object_schema
VARCHAR2(32) := NULL;
14.
object_name VARCHAR2(32) :=
NULL;
15.
policy_name VARCHAR2(32) :=
NULL;
16.
17.
BEGIN
18.
OPEN stmt;
19.
LOOP
20.
FETCH stmt INTO
object_schema,
21.
object_name,
22.
policy_name;
23.
EXIT WHEN stmt
%NOTFOUND;
24.
DBMS_RLS.DROP_POLICY(
25.
'"'||
object_schema||'"',
26.
'"'||
object_name||'"',
27.
'"'||
policy_name||'"');
28.
29.
30.
31.
END LOOP;
CLOSE stmt;
END;
/
32.
Run DVCA to reconfigure Database Vault. Use the following
syntax:
33. $ORACLE_HOME/bin/dvca -action option -oh

oracle_home -jdbc_str
34.
jdbc_connection_string -owner_account
DV_owner_account_name
35.
[-acctmgr_account
DV_account_manager_account_name]
36.
[-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.
See Also:
Oracle Database Vault Installation Guide, 10g Release 2
(10.2) for Linux x86, Appendix C "Running DVCA After
Creating a Database Vault Database" for more options
available with the dvca -action option command
37.
Run Oracle Database Vault Configuration Assistant (DVCA) by
using the dvca -action enable option. This enables the Database
Vault triggers. Use the following syntax:
38. dvca -action enable

39.
-service service_name
40.
-owner_account DV_owner_account_name
41.
[-logfile ./dvca.log]
42.
[-nodecrypt]
43.
44.
Enter SYS password: sys_password
45.
Enter owner password: owner_password
See Step 6 for details of the options used in the command.
46.
Lock the DVSYS account. Use the following SQL statements:
47. SQL> CONNECT SYS "AS SYSDBA"

48. Enter password:
49. SQL> ALTER USER DVSYS ACCOUNT LOCK;
50.
Shut down the database.
To stop a single-instance database, use the following commands:

Enter password:

following command:
$ORACLE_HOME/bin/srvctl stop database -d db_name

51.
Relink the Oracle executable to turn on the Oracle Database
Vault option. Use the following commands:
52. cd $ORACLE_HOME/rdbms/lib
53.
make -f ins_rdbms.mk dv_on
54.
cd $ORACLE_HOME/bin
55.
relink oracle
Note:
For an Oracle Real Application Clusters (RAC) database,
you must repeat the preceding commands on all nodes.
56.
Start the database.
For a single-instance database, use the following commands:

Enter password:
SQL> startup
following command:
$ORACLE_HOME/bin/srvctl start database -d db_name

57.
If you wish to disable connections with SYSDBA privileges,
then re-create the password file with the nosysdba=y and
force=y flags. Use the following syntax:
58. orapwd file=$ORACLE_HOME/dbs/orapwSID

password=password force=y nosysdba=y
Here SID is the Oracle system identifier (SID) of the database, and
password is the password for the SYS account.
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:
1. In the cloned Oracle home, remove all the subdirectories of the
$ORACLE_HOME/ccr/hosts directory to remove the previously
configured hosts.
2. In the cloned Oracle home, run the following command:
3. $ 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:
1. Follow the steps in section "Disabling Oracle Database Vault"
2. Follow the steps in section "Removing the Patch Set Software"
3. 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:
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> SHUTDOWN IMMEDIATE SQL> EXIT
2. Take a backup of the following file in 10.2.0.4 Oracle home
directory:
3. $ ORACLE_HOME/rdbms/admin/catrelod.sql
4. $ ORACLE_HOME/network/admin/tnsnames.ora
5. Enter the following SQL*Plus commands:
6. $ cd $ORACLE_HOME
7. $ sqlplus /NOLOG
10. SQL> STARTUP DOWNGRADE
11. SQL> SPOOL downgrade.out
12. SQL> @?/rdbms/admin/catdwgrd.sql
13. SQL> SPOOL OFF

15. SQL> EXIT
16.
Review the downgrade.out file for errors.
17.
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:
18.
19.
20.
21.
22.
23.
24.
25.
26.
$ sqlplus /NOLOG
SQL> STARTUP DOWNGRADE
SQL> SPOOL catrelod.out
SQL> @?/rdbms/admin/catrelod.sql
SQL> SPOOL OFF
Review the catrelod.out file for errors.
27.
Start the database and recompile the remaining invalid
objects:
28. SQL> STARTUP

Cross-check the status of installed components with the following
script:
SQL> SELECT COMP_NAME, VERSION, STATUS FROM

SYS.DBA_REGISTRY;
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:
1. Use SQL*Plus to log in to the database as the SYS user with
SYSDBA privileges:
2. $ sqlplus /NOLOG
5. 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;
6. Exit SQL*Plus and shut down the database:

8. Take a backup of the following files in 10.2.0.4 Oracle home
directory:
9. $ ORACLE_HOME/rdbms/admin/catrelod.sql
10. $ ORACLE_HOME/network/admin folder
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
Enter the following SQL*Plus commands:
$ sqlplus /NOLOG
SQL> SPOOL catdwgrd.out
SQL> @?/rdbms/admin/catdwgrd.sql
SQL> SPOOL OFF
SQL> EXIT
21.
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:
22.
23.
24.
25.
26.
27.
28.
29.
30.
$ sqlplus /NOLOG
SQL> SPOOL catrelod.out
SQL> @?/rdbms/admin/catrelod.sql
SQL> SPOOL OFF
Review the catrelod.out file for errors.
31.
Start the database and recompile the remaining invalid
objects:
32. SQL> STARTUP

Cross-check the status of installed components with the following
script:
SQL> SELECT COMP_NAME, VERSION, STATUS FROM

SYS.DBA_REGISTRY;
34.
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
35.
Start the database:
36. $ 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 10 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):
1. Create a response file with following entries:
2. oracle.sysman.ccr|b_localInstall=true
3. oracle.sysman.ccr|b_acceptLicense=true
4. Change to the $ORACLE_HOME/oui/bin directory.
5. Run the following command to remove the ccr directory from the
Oracle Database 10g Release 2 (10.2.0.4) Oracle home:
6. runConfig.bat ORACLE_HOME=OH ACTION=deconfigure

MODE=perform RERUN=true
7. 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:
1. Log in as the oracle user.
2. 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:
o $ DISPLAY=local_host:0.0 ; export DISPLAY

o C shell:
o % 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.
3. Enter the following commands to start Oracle Universal Installer,
where patchset_directory is the directory where you unpacked
the patch set software:
4. $ cd patchset_directory/Disk1
5. $ ./runInstaller
6. On the Welcome screen, click Next.
7. 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.
8. 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.
9. Expand the nodes for each component listed in the tree to display
the patch that corresponds to each component.
10.
Select the patches that you want to install.
When you select a patch, the Install Status column changes to

Reinstall.
11.
Repeat the process for each patch bundled in the patch set,
then click Next.
12.
On the Summary screen, verify the list of patches to be
reinstalled, then click Install.
13.
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:
Upgrading Preconfigured Standard Edition Databases
The Welcome Page of Oracle Database Upgrade Assistant Displays

Incorrect Version
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
Enterprise Manager Throws 500 Internal Server Error When

Scheduler Job Is Created
NFS Client Causes Machine To Reboot During Database Stress

Testing
14.1 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.2 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.3 Running Oracle Database Upgrade Assistant on a

Single Node Oracle RAC Installation
Oracle Database Upgrade Assistant fails during postinstallation upgrade
on a single node and displays the following error message:
ORA-32001: write SPFILE requested but no SPFILE

specified at startup
Workaround:
1. Start the database with the NOMOUNT option:
2. $ sqlplus /NOLOG
5. SQL> STARTUP NOMOUNT
6. 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:
7. SQL> CREATE SPFILE=SHARED_LOCATION/SPFILE.ORA FROM

PFILE=pfile_location/init.ora
8. Shut down the database:

10. SQL> EXIT
11.
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.
12.
Run Oracle Database Upgrade Assistant:
13. $ $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.
14.4 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.
14.5 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.
14.6 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.
14.7 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.8 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.9 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_nodevip, \
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.
14.10 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.
14.11 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.
14.12 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.
14.13 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.14 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.15 Enterprise Manager Throws 500 Internal Server Error

When Scheduler Job Is Created
When creating scheduler jobs, clicking on the OK button while in the
Options tab triggers an Internal Server Error.
Workaround: Switch to a different tab before clicking on the OK button.
The job will be created properly in line with what has been entered in the
Options tab.
This issue is tracked in bug 6863977.
14.16 NFS Client Causes Machine To Reboot During

Database Stress Testing
Under certain test conditions with the system running at about 75% CPU
utilization, a system/OS reboot has been observed on Suse SLES10. An
OS bug has been opened against SLES10 with Novell. The Oracle bug
6883690 contains the details and references the Novell bug (# 361920)
filed for this issue.
15 Fixed Platform-Specific Bugs

The following table lists platform-specific bugs that have been fixed.
Fixed in
Release
Bug
Number
10.2.0.3
5671740 INCOMPLETE CALL STACK FOR LINUX 64-BIT

WITH 2.6.9 KERNEL
10.2.0.4
5375974 DEMO_PROC.MK MAKE THE SIZE OF

$ORACLE_HOME/LIB/CONFIG.O TO ZERO
BYTES
10.2.0.4
5126152 CHANGEPERM.SH INCLUDED IN 10.2.0.2

CANNOT BE RUN AGAINST CLIENT ONLY
ORACLE HOME
10.2.0.4
5963965 AFTER APPLYING OF 10.2.0.3,

PERMISSIONS ARE STILL WRONG FOR LIB32
AND SRVM/LIB32
10.2.0.4
5240469 GENOCCISH GENERATES LOTS OF ERRORS AND

FAILS ON AMD64
10.2.0.4
6749282 10.2.0.4 6749282 eliminated AMD from

all X86-64 bit RDBMS ports
10.2.0.4
6612823 SUPPORT OF ODBC 11.1.0.6 AND 10.2.0.3

64-BIT ON LINUX X86-64
Description
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
Component
Version
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 (32-bit and 64-bit)
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
Component
Version
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
Component
Version
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
Component
Version
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 Embedded 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)
10.2.0.4
Pro*FORTRAN
10.2.0.4
Component
Version
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.
Oracle Database Patch Set Release Notes, 10g Release 2 (10.2.0.4) Patch
Set 3 for for Linux x86
Copyright 2008, 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 SoftwareRestricted Rights (June 1987). Oracle
USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass
transit, medical, or other inherently dangerous applications. It shall be
the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such
applications if the Programs are used for such purposes, and we disclaim
liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of
Oracle Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.
The Programs may provide links to Web sites and access to content,
products, and services from third parties. Oracle is not responsible for
the availability of, or any content provided on, third-party Web sites. You
bear all risks associated with the use of such content. If you choose to
purchase any products or services from a third party, the relationship is
directly between you and the third party. Oracle is not responsible for:
(a) the quality of third-party products or services; or (b) fulfilling any of
the terms of the agreement with the third party, including delivery of
products or services and warranty obligations related to purchased
products or services. Oracle is not responsible for any loss or damage of
any sort that you may incur from dealing with any third party.
Oracle Copyright and Trademark Notice

Copyright Notice
Copyright 1994-2008, Oracle. All rights reserved.
Trademark Notice
Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle
Corporation and/or its affiliates. Other names may be trademarks of their
respective owners.

Manual de Procedimiento - Actualizaciópn Oracle 10g, Parches de Seguridad

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Manual de Procedimiento - Actualizaciópn Oracle 10g, Parches de Seguridad

Загружено:

Авторское право:

Доступные форматы

Oracle Database Patch Set Notes

10g Release 2 (10.2.0.4) Patch Set 3 for

Patch Set Overview

Components of This Patch Set

Accessing the Latest Version of this Document

Oracle Universal Installer Version Requirements

Patch Set Documentation

Downgrading Oracle Database Vault

Removing the Patch Set Software

Removing Configuration and Deleting CCR for OCM Configured

Reinstalling the Patch Set Software

Fixed Platform-Specific Bugs

Patch Set Components

1 Patch Set Overview

Oracle Real Application Clusters

Oracle Database Client

Oracle Database Companion CD

Oracle Database Vault

2 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

Generic bug fixes as listed in the List of Bugs fixed document

Oracle Configuration Manager 10.2.7.1

3 Accessing the Latest Version of this Document

4 Oracle Universal Installer Version Requirements

5 Patch Set Documentation

Oracle Database Patch Set Notes, 10g release 2 (10.2.0.4) Patch

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

Oracle Database Patch Set Notes, 10g Release 2 (10.2.0.4)

System requirements and information about how to install,

A list of known issues relating to Oracle Database on Linux x86-64

Oracle Database List of Bugs Fixed, 10g Release 2

Oracle Database 10g (10.2.0.1) or later

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

Upgrading Oracle E-Business Suite Databases

Upgrading Installations that use Physical or Logical Standby

Upgrading Installations that use Java Virtual Machine or Oracle

Upgrading Oracle Clusterware

Notes to Oracle OLAP Users

Disabling Oracle Database Vault

7.1.1 Upgrading Oracle E-Business Suite Databases

For information about physical standby databases, review

For information about logical standby databases, review document

These documents are available on the OracleMetaLink Web site:

7.1.4 Upgrading Oracle Clusterware

4. Shut down the database:

$ srvctl stop database -d db_name -c

SQL> CONNECT SYS AS SYSOPER

6. Re-link the Oracle database software with dv_off:

7. Start the database:

$ srvctl start database -d db_name

9. SQL> ALTER USER DVSYS ACCOUNT UNLOCK;

Disable the Oracle Database Vault triggers:

Run Oracle Database Vault Configuration Assistant (DVCA) by

dvca -action disable