Professional Documents
Culture Documents
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:
System Requirements
Preinstallation Tasks
Installation Tasks
Postinstallation Tasks
Known Issues
Documentation Accessibility
Oracle Database
Oracle Clusterware
For a list of products included in this patch set, see the "Patch Set
Components" section.
See Also:
Oracle Configuration Manager Installation and
Administration Guide10g Release 7 (10.2) (Part Number
B32294-01)
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.
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.
A list of all bugs fixed to date that are specific to Oracle Database
for Linux x86-64
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
7 Preinstallation Tasks
Complete the following preinstallation tasks before installing the patch
set:
http://metalink.oracle.com
7.1.2 Upgrading Installations that use Physical or Logical
Standby Databases
Before applying this patch set to an Oracle Database 10.2.0.x installation
that uses one or more physical or logical standby databases, review the
following OracleMetaLink documents:
http://metalink.oracle.com
7.1.3 Upgrading Installations that use Java Virtual Machine or
Oracle interMedia
If any of the databases use Java Virtual Machine or Oracle interMedia,
then install the Oracle Database 10g Products installation type from the
Oracle Database 10g Companion CD before installing the 10.2.0.4 patch
set. For information about installing the Oracle Database 10g Products
installation type from the Companion CD, see the Oracle Database
Companion CD Installation Guide for the platform. This installation type
includes the Natively Compiled Java Library files to improve Java
performance. If you do not install the Natively Compiled Java Library
files, the ORA-29558: JAccelerator (NCOMP) not installed error
occurs when a database that uses Java Virtual Machine is upgraded to
the patch release.
See Also:
OracleMetaLink document 293658.1 for more information
about the ORA-29558: JAccelerator (NCOMP) not
installed error
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.
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
$ sqlplus /nolog
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP
8. Unlock the DVSYS account and set the password:
[-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
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.
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:
$ 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.
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.
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.
o $ export ORACLE_SID=+ASM
o $ export ORACLE_HOME=ASM_HOME
o C shell:
$ sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
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:
Rolling Upgrade
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 services in the Oracle home on the node that might
be accessing a database:
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.
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:
d. # CRS_home/install/root102.sh
Note:
Rolling upgrade is not supported on Shared Oracle home.
Note:
You must perform these steps in the order listed.
1. Shut down all processes in the Oracle home on each node that
might be accessing a database, for example Oracle Enterprise
Manager Database Control or iSQL*Plus:
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 services in the Oracle home on each node that might
be accessing a database:
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.
d. # CRS_home/install/root102.sh
Shut down the following Oracle Database 10g processes before installing
the patch set:
1. Shut down all processes in the Oracle home on each node that
might be accessing a database, for example Oracle Enterprise
Manager Database Control or iSQL*Plus:
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.
4. Shut down all services in the Oracle home on each node that might
be accessing a database:
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:
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.
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.
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:
o $ export DISPLAY=localhost:0.0
o C shell:
$ 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.
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.
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
13.
On the End of Installation screen, click Exit, then click Yes to
exit from Oracle Universal Installer.
Note:
For Oracle RAC installations, make sure the
CLUSTER_NODES variable specifies all of the nodes used
in the original Oracle RAC installation.
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
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.
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.
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.
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:
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.
Note:
For Oracle RAC, enter the SYS password to do the
upgrade.
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:
6. SQL> @?/rdbms/admin/utlu102i.sql
7. Turn off the spooling of script results to the log file:
********************************************************
**************
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.
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
9. SQL> CONNECT SYS AS SYSDBA
10. Enter password:SYS_password
Users of single-instance installations now proceed to step 7.
11.
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:
i. SQL> SHUTDOWN
12.
13.
14.
15.
16.
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.
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:
b. emca -upgrade db
c. In the case of Oracle Real Application Clusters (RAC),
execute
Note:
If you are upgrading a database having dbcontrol
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.
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.
28.
29.
30.
31.
END LOOP;
CLOSE stmt;
END;
/
32.
Run DVCA to reconfigure Database Vault. Use the following
syntax:
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:
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.
Here SID is the Oracle system identifier (SID) of the database, and
password is the password for the SYS account.
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
See one of the following sections for information about how to remove
the patch set software based on the Oracle Database installation type:
Note:
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
8. SQL> CONNECT SYS AS SYSDBA
9. Enter password:SYS_password
10. SQL> STARTUP DOWNGRADE
11. SQL> SPOOL downgrade.out
12. SQL> @?/rdbms/admin/catdwgrd.sql
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> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP DOWNGRADE
SQL> SPOOL catrelod.out
SQL> @?/rdbms/admin/catrelod.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
Review the catrelod.out file for errors.
27.
Start the database and recompile the remaining invalid
objects:
2. $ sqlplus /NOLOG
3. SQL> CONNECT SYS AS SYSDBA
4. Enter password:SYS_password
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).
9. $ ORACLE_HOME/rdbms/admin/catrelod.sql
10. $ ORACLE_HOME/network/admin folder
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
$ sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP DOWNGRADE
SQL> SPOOL catdwgrd.out
SQL> @?/rdbms/admin/catdwgrd.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT
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
22.
23.
24.
25.
26.
27.
28.
29.
30.
$ sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP DOWNGRADE
SQL> SPOOL catrelod.out
SQL> @?/rdbms/admin/catrelod.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
Review the catrelod.out file for errors.
31.
Start the database and recompile the remaining invalid
objects:
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).
35.
Note:
Option for removing Oracle Clusterware patch set is not
available in 10.2.0.4. This issue is tracked with Oracle
bug 5598010.
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:
$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.
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.
14 Known Issues
Review the following known issues after you apply the patch set:
Benign Entry in the Silent Log File After Cloning the Database
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.
2. $ sqlplus /NOLOG
3. SQL> CONNECT SYS AS SYSDBA
4. Enter password:SYS_password
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:
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.
Workaround:
These are benign errors and can be ignored.
This issue is tracked with Oracle bug 6363210.
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:
_optimizer_native_full_outer_join =force
You can set this parameter for the system or for a specific session.
Besides dramatically improving the performance of a full outer join, the
new implementation fixes a variety of issues, for examples a variety of
ORA-942 (table or view doesn't exists) and ORA-4331 (unable to allocate
string bytes of shared memory) errors.
This issue is tracked with Oracle bug 6322672.
6883690 contains the details and references the Novell bug (# 361920)
filed for this issue.
Bug
Number
10.2.0.3
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
Description
Version
10.2.0.4
10.2.0.4
Advanced Replication
10.2.0.4
10.2.0.4
Component
Version
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
Clusterware
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
Database Vault
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
Export/Import
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
iSQL*Plus
10.2.0.4
JAccelerator (NCOMP)
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
Component
Version
10.2.0.4
New Database ID
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
Oracle Client
10.2.0.4
10.2.0.4
10.2.0.4
10.2.7.1
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
Component
Version
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.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
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
Oracle Net
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
Component
Version
10.2.0.4
Oracle Partitioning
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
Oracle SQLJ
10.2.0.4
Oracle Spatial
10.2.0.4
10.2.0.4
10.2.0.4
Oracle Text
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4.3
10.2.0.4
10.2.0.4
10.2.0.4
PL/SQL
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
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
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
10.2.0.4
SQLJ Runtime
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
Sample Schema
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
XML
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
10.2.0.4
XML Transx
10.2.0.4
XSQL Servlet
10.2.0.4
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.
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 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.
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.