«  
  »

10.2.0.5 补丁集发布

作者: Maclean Liu , post on May 1st, 2010 , English Version
【本站文章除注明转载外，均为本站原创编译】
转载请注明：文章转载自: Oracle Clinic – Maclean Liu的个人技术博客 [http://www.oracledatabase12g.com/]
本文标题: 10.2.0.5 补丁集发布
本文永久地址: http://www.oracledatabase12g.com/archives/10-2-0-5-%e8%a1%a5%e4%b8%81%e9%9b%86%e5%8f%91%e5%b8%83.html

大洋彼岸的4月30日早晨，期盼已久的10.2.0.5补丁终于发布了(等了大约有1年时间吧)；直接接受的一些在10.2.0.4上的问题，oracle都宣布将在这个版本中解决；实际上我一度认为10.2.0.5不会发布了，因为作为一个奇数版本会给人一丝不够稳定的感觉，同时该版本之后不太可能会有后续的补丁集了，如果以一个奇数版本为10g的最终版本似乎不是最理想的方案，当然这番推断还有待验证。

新补丁的大小为1.2g,十分符合以往的惯例,附patch set note:

Oracle® Database Patch Set Notes
10g Release 2 (10.2.0.5) Patch Set 4 for Linux x86-64
Part Number E15229-01

Oracle® Database

Patch Set Notes

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

E15229-01

April 2010

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

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.5 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 Critical Patch Updates

Review the latest Critical Patch Update information at http://www.oracle.com/technology/deploy/security/alerts.htm.

3 Components of This Patch Set

The following are the updated components of 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.3.2

    See Also:

    Oracle Configuration Manager Installation and Administration Guide Version 10.3.2 (part number B32294-10)

4 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 My Oracle Support (formerly OracleMetaLink) Web site:

https://support.oracle.com

To locate document 316900.1:

  1. Log on to My Oracle Support.
  2. Set Article ID as the search source.
  3. Enter 316900.1 in the search field, then click Search icon.

5 Oracle Universal Installer Version Requirements

This patch set includes Oracle Universal Installer release 10.2.0.5, 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 from an existing Oracle home.

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

6 Patch Set Documentation

The Oracle Database List of Bugs Fixed, 10g release 2 (10.2.0.5) document is no longer available as a separate document that ships with the software. A mechanism for finding fixed bugs is available from document 316900.1, ALERT: Oracle 10g Release 2 (10.2) Support Status and Alerts.

There is a platform-specific document, Oracle Database Patch Set Notes, 10g release 2 (10.2.0.5) Patch Set, related to each platform for this release of the Oracle Database patch set. This document provides:

  • Information about how to install, reinstall, or remove the patch set.
  • A list of known issues relating to Oracle Database on the platform.

This document is included with the patch set software. In addition, this document and the mechanism for finding fixed bugs are available from document 316900.1, ALERT: Oracle 10g Release 2 (10.2) Support Status and Alerts on the My Oracle Support (formerly OracleMetaLink) Web site:

https://support.oracle.com

To locate document 316900.1:

  1. Log on to My Oracle Support (formerly OracleMetaLink).
  2. Set Article ID as the search source.
  3. Enter 316900.1 in the search field, then click Search icon.

7 System Requirements

Check your platform-specific installation guide for a list of supported operating systems. For the latest information, check the Certifications link at My Oracle Support (formerly OracleMetaLink):

https://support.oracle.com

8 Preinstallation Tasks

Complete the following preinstallation tasks before installing the patch set:

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

8.1.1 Oracle Universal Installer Operating System Prerequisite Checks

Some of the prerequisite checks are not required when installing the 10.2.0.5 patch set in Oracle Clusterware, Oracle Client, or Oracle Gateways Oracle homes.

Workaround: Run Oracle Universal Installer using the ignoreSysPrereqs flag which causes the installer to skip the prerequisite checks and continue with the installation:

./runinstaller -ignoreSysPrereqs

8.1.2 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 My Oracle Support Web site:

https://support.oracle.com

8.1.3 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 My Oracle Support 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 My Oracle Support (formerly OracleMetaLink) Web site:

https://support.oracle.com

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

My Oracle Support (formerly OracleMetaLink) document 293658.1 for more information about the ORA-29558: JAccelerator (NCOMP) not installed error

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

Before applying the 10.2.0.5 patch set to the Clusterware home, run the following command on all the cluster nodes:

chmod -R +w CRS_HOME/inventory/Templates/*

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

8.1.7 Notes to Oracle Text Users

In 10.2.0.5, Oracle Text uses Oracle Outside In HTML Export for document filtering instead of filtering technology licensed from Autonomy, Inc. Refer to the following sections in Oracle Text Reference (part number B28304-03) for more details:

  • Appendix B.1.3 for supported platforms for AUTO_FILTER
  • Appendix B.2 for supported document formats
  • Table B-4 in Appendix B.2.9 for formats that are no longer supported in 10.2.0.5

    Note:

    Table B-4 in Appendix B.2.9 refers to formats supported in release 11.1.0.6 but not in release 11.1.0.7. The same applies when you upgrade from release 10.2.0.4 to 10.2.0.5.

8.1.8 Disabling Oracle Database Vault

Complete the steps in this section before upgrading Oracle Database Vault from 10.2.0.x to 10.2.0.5 or downgrading Oracle Database Vault from 10.2.0.5 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: 
    $ orapwd file=$ORACLE_HOME/dbs/orapwsid password=syspasswd force=y nosysdba=n

    Note:

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

  2. Shut down the database:For Oracle RAC: 
    $ srvctl stop database -d db_name

    For Single Instance:

    SQL> CONNECT SYS AS SYSOPER
Enter password: SYS_password
SQL> SHUTDOWN
  3. Turn off Oracle Database Vault and 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 all
  4. Start the database:For Oracle RAC: 
    $ srvctl start database -d db_name

    For Single Instance:

    sqlplus /nolog
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP
  5. Unlock the DVSYS account and set the password: 
    SQL> ALTER USER DVSYS ACCOUNT UNLOCK;
  6. 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] [-racnode host_name] 

Enter SYS password: SYS_password
Enter owner password: owner_password

8.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. Use Oracle Universal Installer to identify Oracle home directories. From the Welcome screen, click Installed Products, then click the Environment tab.

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.

8.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 My Oracle Support (formerly OracleMetaLink) Web site:

https://support.oracle.com

To locate this document:

  1. Log on to My Oracle Support.
  2. Set Article ID as the search source.
  3. Enter 316900.1 in the search field, then click Search icon.

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.

8.4 Download and Extract the Installation Software

To download and extract the patch set installation software:

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

8.5 Update Oracle Time Zone Definitions

The 10.2.0.5 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, see My Oracle Support (formerly OracleMetaLink) document 1086400.1 Actions for the DSTv4 update in the 10.2.0.5 patchset.

  1. When patching from a lower 10.2 release or upgrading from 10.1.0.x directly to 10.2.0.5, check the current version of the Oracle time zone definitions with the following command: 
    SELECT version FROM v$timezone_file;
    • If this query reports version 4, no action is required.
    • If this reports a version lower or higher than 4, see My Oracle Support document 1086400.1 Actions for the DSTv4 update in the Release 10.2.0.5 patchset.
  2. On upgrading from any release of Oracle9i to Release 10.2.0.5, see My Oracle Support document 1086400.1 Actions for the DSTv4 update in the 10.2.0.5 patchset.
  3. On upgrading from Release 8.1.7 directly to Release 10.2.0.5, no action is required because Release 8.1.7 has no timezone data stored.

8.6 Shut Down Oracle Databases

Shut down any existing Oracle Database instances with normal or immediate priority. On Oracle RAC systems, shut down all instances on each node.

If Oracle Automatic Storage Management (Oracle ASM) is running, shut down all databases that use Oracle ASM, then shut down the Oracle ASM instance on each node of the cluster.

Note:

If you are using Oracle Clusterware, you must shut down all Oracle Database instances on all cluster nodes before applying the patch set to the Oracle Clusterware installation. All Oracle database instances are restarted during the Oracle Clusterware patch set installation. After the Oracle Clusterware patch set installation is complete, you must shut down all Oracle Database and Oracle ASM instances running in the Oracle RAC Oracle home before patching the Oracle RAC Oracle home.

8.7 Set the ORACLE_HOME and ORACLE_SID Environment Variables

Enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables:

  • Bourne, Bash, or Korn shell: 
    $ ORACLE_HOME=Oracle_home
$ ORACLE_SID=sid
$ PATH=$ORACLE_HOME/bin:$ORACLE_HOME/bin/OPatch:$PATH
$ export ORACLE_HOME ORACLE_SID PATH
  • C shell: 
    % setenv ORACLE_HOME Oracle_home
% setenv ORACLE_SID sid
% setenv PATH $ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH

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.

8.8 Stop All Processes

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

See also:

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

8.8.1 Stopping All Processes for a Single Instance Installation

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

  1. Shut down allprocesses in the Oracle home that might be accessing a database; for example, Oracle Enterprise Manager Database Control: 
    $ emctl stop dbconsole
$ 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.

  2. Shut down all database instances running in the Oracle home directory, where you need to install the patch set.
  3. Shut down all listeners running in the Oracle home directory, where you need to install the patch set.
  4. If there is an Automatic Storage Management instance present, then enter the following command to set the values for the environment variables $ORACLE_HOME and $ORACLE_SID:
    • Bourne, Bash, or Korn shell: 
      $ export ORACLE_SID=+ASM
$ export ORACLE_HOME=ASM_HOME
    • C shell: 
      % setenv ORACLE_SID +ASM
% setenv ORACLE_HOME ASM_HOME

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

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

8.8.2 Stopping All Processes for an Oracle Clusterware Installation

This section contains the following information:

8.8.2.1 Rolling Upgrade

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

  1. Stop iSQL*Plus on the primary node by issuing the following command: 
    isqlplusctl stop
  2. Shut down all processes in the Oracle home on the node that might be accessing a database; for example, Oracle Enterprise Manager Database Control: 
    $ emctl stop dbconsole
$ lsnrctl stop listenername

    Note:

    isqlplusctl stop should be issued only on the primary node as isqplusctl doesn’t start on remote node.

    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.

  3. Shut down all services in the Oracle home on the node that might be accessing a database: 
    $ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
  4. Shut down all Oracle RAC instances on the node on which you intend to perform the rolling upgrade. To shut down Oracle RAC instances on individual nodes in the database, enter the following command where db_name is the name of the database: 
    $ srvctl stop instance -d db_name -i inst_name
  5. If an Automatic Storage Management instance is present, then shut down the Automatic Storage Management instance on the node on which you intend to perform the rolling upgrade. To shut down an Automatic Storage Management instance, enter the following command where node is the name of the node where the Automatic Storage Management instance is running: 
    $ srvctl stop asm -n node
  6. Stop all node applications on the node on which you intend to perform the rolling upgrade. To stop node applications running on a node, log in as the root user and enter the following command, where node is the name of the node where the applications are running: 
    # srvctl stop nodeapps -n node
  7. Perform the steps mentioned in “Installation Tasks.”

    Note:

    The following instructions are displayed on the Oracle Universal Installer screen.To complete the installation of this patch set, you must perform the following tasks on each node:

    1. Log in as the root user.
    2. As the root user, perform the following tasks:
      1. Shutdown the CRS daemons by issuing the following command: 
        CRS_home/bin/crsctl stop crs
      2. Run the shell script located at: 
        CRS_home/install/root102.sh

        This script will automatically start the CRS daemons on the patched node upon completion.

    3. After completing this procedure, proceed to the next node and repeat.
  8. To upgrade the rest of the nodes, go to the next node and perform Steps 2 to 6 and then log in as the root user and perform the following steps:
    1. Enter the following command to shut down the Oracle Clusterware: 
      # CRS_home/bin/crsctl stop crs
    2. Run the root102.sh script to automatically start the Oracle Clusterware on the patched node: 
      # CRS_home/install/root102.sh

    Note:

    Rolling upgrade is not supported on shared Oracle home.

8.8.2.2 Non Rolling Upgrade

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

Complete the following steps:

Note:

You must perform these steps in the order listed.

  1. Stop iSQL*Plus on the primary node by issuing the following command: 
    isqlplusctl stop
  2. Shut down all processes in the Oracle home on each node that might be accessing a database; for example, Oracle Enterprise Manager Database Control: 
    $ emctl stop dbconsole
$ lsnrctl stop listenername

    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.

  3. Shut down all services in the Oracle home on each node that might be accessing a database: 
    $ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
  4. Shut down all Oracle RAC instances on all cluster nodes by entering the following command where db_name is the name of the database: 
    $ srvctl stop database -d db_name
  5. If Automatic Storage Management instance is present, then shut down Automatic Storage Management instances on all cluster nodes by entering the following command where node is the name of the node where the Automatic Storage Management instance is running: 
    $ srvctl stop asm -n node
  6. Stop all node applications on all cluster nodes by entering the following command as the root user, where node is the name of the node where the applications are running: 
    # srvctl stop nodeapps -n node
  7. Shut down the Oracle Clusterware processes by entering the following command on all nodes as the root user: 
    # CRS_home/bin/crsctl stop crs
  8. Complete the steps mentioned in “Installation Tasks.”

    Note:

    You cannot perform a rolling upgrade of your Oracle Clusterware if the software is installed on a shared partition. The following instructions regarding a non-rolling upgrade are displayed on the Oracle Universal Installer screen.To complete the installation of this patch set, you must perform the following tasks:

    1. On each node, do the following:
      1. Log in as the root user.
      2. As root, shutdown the CRS daemons on the node using the following command: 
        # CRS_home/bin/crsctl stop crs

        Repeat this step until the CRS daemons on all the nodes are shutdown.

    2. After all the CRS daemons on all the nodes are shutdown, run the shell script located at: CRS_home/install/root102.sh. This script will automatically start the CRS daemons on the patched node upon completion.
    3. Wait until the script finishes and then proceed to the next node and repeat step 2.

8.8.3 Stopping All Processes for an Oracle RAC Installation

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

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

    Note:

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

  2. Shut down all services in the Oracle home on each node that might be accessing a database: 
    $ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
  3. Shut down all Oracle RAC instances on the nodes, which run from the Oracle home on which you are going to apply the patch set. To shut down all Oracle RAC instances for a database, enter the following command where db_name is the name of the database: 
    $ srvctl stop database -d db_name
  4. If Automatic Storage Management instance is present, then shut down all Automatic Storage Management instances on all nodes. To shut down an Automatic Storage Management instance, enter the following command where node is the name of the node where the Automatic Storage Management instance is running: 
    $ srvctl stop asm -n node

    This needs to be done only when patching the home from where Oracle ASM runs. It is recommended that Oracle ASM run from a different ORACLE_HOME than the database.

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

    Note:

    Using a logical standby database, you can upgrade Oracle Database software and patch sets with almost no downtime. Using Data Guard SQL Apply, you can perform a rolling upgrade of the Oracle Database software from the base 10.2.0.x release 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.

8.9 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. You must also ensure that the GID and UID of the CRS / Oracle User be less than 65536 bytes (ID username will provide the UID / GID for the user).

See also:

Oracle Database Backup and Recovery User’s Guide for more information

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

9.1 Installing 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 Oracle10g 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 4 10.2.0.5

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

To install the Oracle Database 10g patch set interactively:

  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:
    • Bourne, Bash, or Korn shell: 
      $ export DISPLAY=localhost:0.0
    • C shell: 
      % setenv DISPLAY local_host:0.0

    In this example, local_host is the host name or IP address of the computer that you want to use to display Oracle Universal Installer.

    Now to enable X applications, run the following command on the machine that you want to use to display Oracle Universal Installer:

    $ xhost + [fully_qualified_remote_host_name]
  3. Enter the following commands to start Oracle Universal Installer, where patchset_directory is the directory where you unpacked the patch set software: 
    % cd patchset_directory/Disk1
% ./runInstaller
  4. On the Welcome screen, click Next.
  5. 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.
  6. Enter your e-mail address and password for your My Oracle Support account to be informed of security issues, then click Next.

    Note:

    The registration and configuration can also be done manually after patch set installation.The OCM registration page appears only while applying 10.2.0.5 patch over existing Database instances alone.

  7. If you are installing the patch set on an Oracle RAC cluster, click Next when the Selected Nodes screen appears.
  8. On the Product-specific Prerequisite Checks screen, correct any reported errors, and click Next.
  9. On the Summary screen, click Install.This screen lists all of the patches available for installation.
  10. 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.
  11. On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.

Note:

If you are applying this patch set to an Oracle Clusterware installation, then complete all of the steps displayed on the Oracle Universal Installer screen.The Oracle Clusterware installation instructions displayed on the Oracle Universal Installer screen are also available in the CRS_home/install/readme.txt file.

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

9.2 Installing the Oracle Database 10g Patch Set Noninteractively

To install the Oracle Database 10g patch set noninteractively:

  1. Copy the response file template provided in the response directory where you unpacked the patch set archive file.
  2. Edit the values for all fields labeled as <Value Required> as described by the comments and examples in the template.

    Note:

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

  3. To run Oracle Universal Installer, enter a command similar to the following, where response_file is the full path to the response file that you edited: 
    $ ./runInstaller -silent -responseFile response_file
  4. After the installation, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an Oracle RAC installation, then run the root.sh script on each node of the cluster.

    Note:

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

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

10.1 Upgrading Earlier Oracle Database to Oracle Database 10g Release 2 (10.2.0.5)

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

10.1.1 Upgrading Earlier Oracle Database Releases to Oracle Database 10g Release 2 (10.2.0.5)

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.

10.1.2 Upgrading a Release 9.2 Database Not Using Oracle Label Security

To avoid errors when upgrading from release 9.2, Oracle Label Security should be installed. Use one of the following methods to check if Oracle Label Security is installed:

  • If the catnools.sql script exists on the computer, Oracle Label Security is installed.
  • Check the inventory at the end of the installAction log file for the base version installation (9.2). If Oracle Label Security is installed, Label Security is listed in the inventory section of the log file.
  • Use the following commands to check if Oracle Label Security is installed with the 9.2 database: 
    $ sqlplus
SQL> CONNECT SYS AS SYSDBA
Enter password:password
SELECT * FROM V$OPTION WHERE PARAMETER = 'Oracle Label Security';

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 catnools.sql script, located in the /rdbms/admin directory under the Oracle home, with the SYSDBA privilege to remove Oracle Label Security components from the database.

10.1.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.5), 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.5) 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.

10.2 Updating Oracle Time Zone Definitions

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

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

10.3 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: 
    $ cd $ORACLE_HOME/install
  2. Run changePerm.sh and specify the patched server Oracle home location, before accessing client-side utilities or libraries in the database home.

    Note:

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

10.4 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> SHUTDOWN IMMEDIATE
SQL> STARTUP

    For an Oracle Real Application Clusters (Oracle 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: 
    SQL> DECLARE
              CURSOR stmt IS
                       SELECT u.name, o.name, r.pname
                           FROM user$ u, obj$ o, rls$ r
                       WHERE u.user# = o.owner#
                           AND r.obj# = o.obj#
                           AND bitand(r.stmt_type,65536) > 0;

                       object_schema VARCHAR2(32) := NULL;
                       object_name VARCHAR2(32) := NULL;
                       policy_name VARCHAR2(32) := NULL;

                       BEGIN
                        OPEN stmt;
                          LOOP
                               FETCH stmt INTO object_schema,
                                               object_name,
                                               policy_name;
                               EXIT WHEN stmt%NOTFOUND;
                               DBMS_RLS.DROP_POLICY(
                               '"'||object_schema||'"',
                               '"'||object_name||'"',
                               '"'||policy_name||'"');
                          END LOOP;
                        CLOSE stmt;
                       END;
                      /
  3. Run DVCA to reconfigure Database Vault. Use the following syntax: 
    $ORACLE_HOME/bin/dvca -action option
     -oh oracle_home
     -jdbc_str jdbc_connection_string
     -owner_account DV_owner_account_name
     [-acctmgr_account DV_account_manager_account_name]
     [-logfile ./dvca.log] [-nodecrypt]

    Where:

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

    - oh: The absolute path of 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_BASE\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, Appendix C “Running DVCA After Creating a Database Vault Database” for more options available with the dvca -action command

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

    Enter SYS password: SYS_password
    Enter owner password: owner_password
  5. Lock the DVSYS account. Use the following SQL statements: 
    SQL> CONNECT SYS "AS SYSDBA"
Enter password:
SQL> ALTER USER DVSYS ACCOUNT LOCK;
  6. Shut down the database.To stop a single-instance database, use the following commands: 
    sqlplus SYS "AS SYSDBA"
Enter password:
SQL> SHUTDOWN IMMEDIATE

    For an Oracle RAC database, use the following command:

    $ORACLE_HOME/bin/srvctl stop database -d db_name
  7. Relink the Oracle executable to turn on the Oracle Database Vault option. Use the following commands:Turn on Database Vault. 
    cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk dv_on
cd $ORACLE_HOME/bin
relink all

    Note:

    For an Oracle RAC database, you must repeat the preceding commands on all nodes.

  8. Start the database.For a single-instance database, use the following commands: 
    sqlplus SYS "AS SYSDBA"
Enter password:
SQL> startup

    For an Oracle RAC database, use the following command:

    $ORACLE_HOME/bin/srvctl start database -d db_name
  9. 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: 
    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.

10.5 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: 
    $ 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.6 Upgrading Oracle Database 10g Release 10.2.0.x to Oracle Database 10g Release 10.2.0.5

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

10.6.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, the following errors are displayed on attempting to start the database:ORA-01092: ORACLE instance terminated.

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

  1. Log in as the Oracle software owner user.
  2. Set the values for the environment variables $ORACLE_HOME, $ORACLE_SID and $PATH.
  3. For single-instance installations, if you are using Automatic Storage Management, start the Automatic Storage Management instance.
  4. For Oracle single-instance installations, start the listener as follows: 
    $ lsnrctl start listenername
  5. Run Oracle Database Upgrade Assistant either in the interactive or noninteractive mode:Interactive mode:

    Enter the following command from the command prompt:

    $ dbua

    Note:

    DBUA may edit initialization parameters in the init.ora file or net services in the tnsnames.ora file of the current database. Back up init.ora file and tnsnames.ora file when upgrading to 10.2.0.5 with DBUA.

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

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

      Note:

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

    3. On the Recompile Invalid Objects screen, select the Recompile the invalid objects at the end of upgrade option, then click Next.
    4. If you have not taken the back up of the database earlier, on the Backup screen, select the I would like to take this tool to backup the database option, stipulate the Path, then click Next.
    5. On the Summary screen, check the summary, then click Finish.
    6. 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 Database Control configured in non-secure mode, after upgrade Database Control will run in secure mode.

  6. If you are using the Oracle Recovery Manager catalog, enter the following command: 
    $ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
  7. For Oracle RAC installations, start any database services that you want to use by entering the following command: 
    $ srvctl start service -d db_name -s service_name

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

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

  1. Run the Pre-Upgrade Information Tool
  2. Upgrading a Release 10.2 Database

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

Running pre-upgrade utility tools (utlu102i.sql) is required for release upgrade (e.g 9.2.0.x to 10.2.0.x or 10.1.0.x to 10.2.0.x) and your database would open in NORMAL mode for running the utlu102i.sql script for release upgrade. It is not required to run utlu102i.sql for patch set/version upgrade (for example, 10.2.0.x to 10.2.0.5) but it is recommended to run it. If you have installed 10.2.0.5 patch set on the top of the existing 10.2.0.x Oracle Home then the database must be open in UPGRADE Mode only for running utlu102i.sql. 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: 
    SQL> STARTUP UPGRADE
  2. Set the system to spool results to a log file for later analysis: 
    SQL> SPOOL upgrade_info.log
  3. Run the Pre-Upgrade Information Tool: 
    SQL> @/rdbms/admin/utlu102i.sql
  4. Turn off the spooling of script results to the log file: 
    SQL> SPOOL OFF

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

Oracle Database 10.2 Upgrade Information Utility    02-04-2008 11:48:11
.
**********************************************************************
Database:
**********************************************************************
--> name:       X102050
--> version:    10.2.0.1.0
--> compatible: 10.2.0.1
--> blocksize:  8192
.
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 505 MB
.... AUTOEXTEND additional space required: 15 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
.... minimum required size: 401 MB
.... AUTOEXTEND additional space required: 376 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 265 MB
.... AUTOEXTEND additional space required: 15 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 58 MB
.... AUTOEXTEND additional space required: 38 MB
--> EXAMPLE tablespace is adequate for the upgrade.
.... minimum required size: 69 MB
.
**********************************************************************
Update Parameters: [Update Oracle Database 10.2 init.ora or spfile]
**********************************************************************
WARNING: --> "shared_pool_size" needs to be increased to at least 167772160
WARNING: --> "java_pool_size" needs to be increased to at least 67108864
.
**********************************************************************
Components: [The following database components will be upgraded or installed]
**********************************************************************
--> 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.

10.6.2.2 Upgrading a Release 10.2 Database

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

Note:

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

  1. Log in as the Oracle software owner user.
  2. For Oracle RAC installations, start listener on each node of the cluster as follows: 
    $ srvctl start listener -n node
  3. If you are using Automatic Storage Management, start the Automatic Storage Management instance.
  4. For single-instance installations, start the listener as follows: 
    $ lsnrctl start
  5. For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges: 
    $ sqlplus /nolog
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password

    Users of single-instance implementations should now bypass steps that apply to Oracle RAC installations.

  6. For Oracle RAC installations:
    1. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges: 
      $ sqlplus /nolog
SQL> CONNECT SYS AS SYSDBA
Enter password: SYS_password
SQL> STARTUP NOMOUNT
    2. Set the CLUSTER_DATABASE initialization parameter to FALSE: 
      SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
    3. Shut down the database: 
      SQL> SHUTDOWN
  7. Enter the following SQL*Plus commands: 
    SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catupgrd.sql
SQL> SPOOL OFF
  8. Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script.This list provides the version and status of each SERVER component in the database.
  9. If necessary, rerun the catupgrd.sql script after correcting any problems.
  10. Restart the database: 
    SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP
  11. Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended. 
    SQL> @?/rdbms/admin/utlrp.sql

    Note:

    When the 10.2.0.5 patch set is applied to an Oracle10g 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
  12. Run the following command to check the status of all the components after the upgrade: 
    SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;

    In the output of the preceding command, the status of all the components should be VALID for a successful upgrade.

  13. If you are using the Oracle Recovery Manager catalog, enter the following command: 
    $ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
  14. For Oracle RAC installations:
    1. Set the CLUSTER_DATABASE initialization parameter to TRUE: 
      SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
    2. Restart the database: 
      SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP
    3. Start any database services that you want to use: 
      $ srvctl start service -d db_name -s service_name
  15. To configure and secure Enterprise Manager follow these steps:Ensure the database and Listener are operational.
    • In the case of a single instance, execute 
      emca -upgrade db
    • In the case of Oracle RAC, execute 
      emca -upgrade db -cluster

    Note:

    If you are upgrading a database having Oracle Database Control configured in non-secure mode, after upgrade Oracle Database Control will run in secure mode.

10.7 Redeploying Oracle Workflow Server

If you have deployed Oracle Workflow Server, then you need to redeploy it after installing the 10.2.0.5 patch set.

To redeploy the Oracle Workflow Server:

  1. Stop the Workflow Manager. Use the following command: 
    $ORACLE_HOME/wf/admin/wfmgrstop.sh
  2. Back up the existing deploy_db_wf.ini file. You can find this file at the following location: 
    $ORACLE_HOME/oc4j/j2ee/deploy_db_wf.ini
  3. Modify the deploy_db_wf.ini file to add the DEPLOYED=TRUE keyword to the Listener and Mailer sections: 
    [application]
CMP_NAME=OC4J_Workflow_Component_Container
APP_DEPLOYMENT_NAME=WFALSNRSVCApp
DEPLOYED=true
....
[application]
CMP_NAME=OC4J_Workflow_Component_Container
APP_DEPLOYMENT_NAME=WFMLRSVCApp
DEPLOYED=true
  4. Deploy the new Workflow Manager ear file: 
    $ORACLE_HOME/jdk/bin/java -classpath \
$ORACLE_HOME/oc4j/j2ee/home/oc4j.jar:$ORACLE_HOME/jlib/srvm.jar:\
$ORACLE_HOME/oc4j/j2ee/home/db_oc4j_deploy.jar \
oracle.j2ee.tools.deploy.DbOc4jDeploy -oraclehome \
$ORACLE_HOME -inifile $ORACLE_HOME/oc4j/j2ee/deploy_db_wf.ini
  5. Start the Workflow Manager: 
    $ORACLE_HOME/wf/admin/wfmgrstart.sh

10.8 Redeploying Oracle Ultra Search

If you are running Oracle Ultra Search from the upgraded ORACLE_HOME, then you need to redeploy the ultrasearch_admin.ear file to your oc4j instance.

To redeploy ultrasearch_admin.ear file, copy the $ORACLE_HOME/ultrasearch/webapp/ultrasearch_admin.ear file to the $ORACLE_HOME/oc4j/j2ee/oc4j_applications/applications directory.

Note:

This applies only if you have installed Oracle Ultra Search.

11 Downgrading Oracle Database Vault

Downgrading Oracle Database Vault from 10.2.0.5 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.”

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

Note:

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

12.1 Removing the Patch Set Software for Single Instance Installation

Perform the following steps for removing the patch set from the 10.2.0.5 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.5 Oracle home directory: 
    $ ORACLE_HOME/rdbms/admin/catrelod.sql
$ ORACLE_HOME/network/admin/tnsnames.ora
  3. Enter the following SQL*Plus commands: 
    $ cd $ORACLE_HOME/bin
$ ./sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP DOWNGRADE
SQL> SPOOL downgrade.out
SQL> @?/rdbms/admin/catdwgrd.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT
  4. Review the downgrade.out file for errors.
  5. Restore the Oracle10g installation and Central Inventory (see /etc/oraInst.loc) that you backed up before applying the patch set.
  6. After restoring the original Oracle home, copy the saved version of catrelod.sql script into the restored Oracle home rdbms/admin directory. Also copy the saved version of 10.2.0.5/network/admin/tnsnames.ora directory into the restored Oracle home /network/admin/tnsnames.ora directory, and then perform the following steps: 
    $ sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP DOWNGRADE
SQL> SPOOL catrelod.out
SQL> @?/rdbms/admin/catrelod.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
  7. Review the catrelod.out file for errors.

    Note:

    Ignore the ORA-29844 and ORA-31085 errors found in the catrelod.out file. These errors are tracked with Oracle bugs 4758112 and 4425495 respectively.After reloading the 10.2.0.2 release, the version numbers for Oracle Data Mining and Oracle OLAP Analytic Workspace remain at 10.2.0.5. These issues are tracked with Oracle bugs 4758695 and 4751917.

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

    Cross-check the status of installed components with the following script:

    SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;

12.2 Removing the Patch Set Software for Oracle RAC Installation

Perform the following steps for removing the patch set from the 10.2.0.5 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
  2. Set the CLUSTER_DATABASE initialization parameter to FALSE:

    Note:

    If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameters to TRUE in the initialization parameter file (initsid.ora).

    SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
  3. Exit SQL*Plus and shut down the database: 
    $ srvctl stop database -d db_name
  4. Take a backup of the catrelod.sql file and admin folder in 10.2.0.5 Oracle home directory: 
    $ ORACLE_HOME/rdbms/admin/catrelod.sql
$ ORACLE_HOME/network/admin
  5. Enter the following SQL*Plus commands: 
    $ sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP DOWNGRADE
SQL> SPOOL catdwgrd.out
SQL> @?/rdbms/admin/catdwgrd.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT
  6. Restore the Oracle10g installation and Central Inventory (see /etc/oraInst.loc) that you backed up before applying the patch set on both the nodes.
  7. After restoring the original Oracle home, copy the saved version of catrelod.sql script into the restored Oracle home rdbms/admin directory. Also copy the saved version of 10.2.0.5/network/admin/tnsnames.ora directory into the restored Oracle home /network/admin/tnsnames.ora directory, and then perform the following steps: 
    $ sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
SQL> STARTUP DOWNGRADE
SQL> SPOOL catrelod.out
SQL> @?/rdbms/admin/catrelod.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
  8. Review the catrelod.out file for errors.

    Note:

    Ignore the ORA-29844 and ORA-31085 errors found in the catrelod.out file. These errors are tracked with Oracle bugs 4758112 and 4425495 respectively.After reloading the 10.2.0.2 release, the version numbers for Oracle Data Mining and Oracle OLAP Analytic Workspace remain at 10.2.0.5. These issues are tracked with Oracle bugs 4758695 and 4751917.

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

    Cross-check the status of installed components with the following script:

    SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;
  10. Set the CLUSTER_DATABASE initialization parameter to TRUE:

    Note:

    If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameters to TRUE in the initialization parameter file (initsid.ora).

    SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
SQL> SHUTDOWN
SQL> EXIT
  11. Start the database: 
    $ srvctl start database -d db_name

    Note:

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

13 Deleting Oracle Configuration Manager from an Oracle Home

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

  1. Create a response file with following entries: 
    oracle.sysman.ccr|b_localInstall=true
oracle.sysman.ccr|b_acceptLicense=true
  2. Change to the $ORACLE_HOME/oui/bin directory.
  3. Run the following command to remove the ccr directory from the Oracle Database 10g Release 2 (10.2.0.5) Oracle home: 
    runConfig.bat ORACLE_HOME=OH ACTION=deconfigure MODE=perform RERUN=true
COMPONENT_XML={ccr_xml} RESPONSE_FILE=rsp_file_location

    In the preceding command, ccr_xml is available in the $ORACLE_HOME/inventory/ContentsXML/ConfigXML and the rsp_file_location is the directory where the response file was created. To find the ccr_xml file, run the ls oracle.sysman.ccr.10*.xml command in $ORACLE_HOME/inventory/ContentsXML/ConfigXML directory.

14 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:
    • Bourne, Bash, or Korn shell: 
      $ DISPLAY=local_host:0.0 ; export DISPLAY
    • C shell: 
      % setenv DISPLAY local_host:0.0

    In this example, local_host is the host name or IP address of the computer that you want to use to display Oracle Universal Installer.

  3. Enter the following commands to start Oracle Universal Installer, where patchset_directory is the directory where you unpacked the patch set software: 
    $ cd patchset_directory/Disk1
$ ./runInstaller
  4. On the Welcome screen, click Next.
  5. In the Specify Home Details screen, select the name of the Oracle home that you want to update, or select the Path that you want to update from the list, then click Next.
  6. If you are installing the patch set on an Oracle RAC cluster, click Next when the Selected Nodes screen appears.

    Note:

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

    The Available Product Component screen appears. This screen contains a list of all components that have been patched by the original patch set installation. These components are grayed out, indicating they cannot be selected for installation.

  7. Expand the nodes for each component listed in the tree to display the patch that corresponds to each component.
  8. Select the patches that you want to install.When you select a patch, the Install Status column changes to Reinstall.
  9. Repeat the process for each patch bundled in the patch set, then click Next.
  10. On the Summary screen, verify the list of patches to be reinstalled, then click Install.
  11. On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.

15 Known Issues

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

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

15.2 ORA-600 Error During Oracle RAC Database Upgrade

During post-upgrade phase of DBUA, the following error might be seen:

ORA-00600: internal error code, arguments
[LibraryCacheNotEmptyOnClose]

Workaround:

Click the Ignore button to continue upgrade. User can safely ignore this error.

This issue is tracked with Oracle bug 4483084.

15.3 The SYSMAN Related Errors Are Listed in the oraInstall.err File

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

Workaround:

These are benign errors and can be ignored.

This issue is tracked with Oracle bug 6363210.

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

15.5 Incorrect Nodes Displayed in Cloned Oracle Clusterware

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

Workaround:

Run the following command to address this issue:

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

Note:

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

This issue is tracked with Oracle bug 6754695.

15.6 Native Full Outer Join Implementation

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

_optimizer_native_full_outer_join =force

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

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

This issue is tracked with Oracle bug 6322672.

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

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

The default Makefile version present in a Red Hat 5 computer 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

15.9 Enterprise Manager Configuration Fails While Upgrading From 9.2

As reported in Oracle Bug 6786548, upgrade from Release 9.2 upgrade should be performed with the Enterprise Manager Service Control panel closed.

15.10 Enterprise Manager Throws 500 Internal Server Error When Scheduler Job Is Created

When creating scheduler jobs, clicking the OK button while in the Options tab triggers an Internal Server Error.

Workaround: Switch to a different tab before clicking the OK button. The job will be created properly in line with what has been entered in the Options tab.

This issue is tracked by Oracle bug 6863977.

15.11 NFS Client Causes Machine To Reboot During Database Stress Testing

Under certain test conditions with the system running at about 75% CPU utilization, an operating system reboot has been observed on Suse SLES10. An operating system 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.12 500 Internal Server Error When Refreshing the View in Enterprise Manager

After submitting a workload capture job with the database restart option enabled, viewing or refreshing some other Enterprise Manager pages from the page which shows that the message for job submission succeeded may cause Enterprise Manager to display the following error:

500 Internal Server Error

Workaround:

Close the existing Enterprise Manager session. After the database is fully restarted, open a new Enterprise Manager session to view the workload capture job.

This issue is tracked by Oracle bug 6498607. Note that this bug was uncovered in an Oracle RAC environment, and may or may not apply to single instance implementations.

15.13 Adding Nodes to a Shared Oracle Clusterware Home

If you have a shared Oracle Clusterware home on a single node, then you must follow this procedure.

Workaround:

If you have a shared CRS home installation on a one-node Oracle Clusterware installation, and are performing an Oracle Clusterware node addition, perform the following manual task to ensure that ONS is correctly started, and is online:

  1. After upgrading the one-node 10.2.0.x Oracle Clusterware to 10.2.0.5 Oracle Clusterware, and starting the CRS stack, enter the following command as root to shut down the stack: 
    # crsctl stop crs
  2. As the Oracle user, make a backup copy of the ons.config file.
    1. Change directory to the ons.config file using a command similar to the following, where $CRS_HOME is the shared directory where you installed Oracle Clusterware: 
      % cd $CRS_HOME/opmn/conf
    2. Enter the following command: 
      %cp ons.config ons.config.orig
  3. Open the ons.config file with a text editor. For example: 
    %vi ons.config
  4. Add the line usesharedinstall=true to the end of the file, as shown in the following example: 
    localport=6113
remoteport=6200
loglevel=3
useocr=on
usesharedinstall=true
  5. As the root user, restart the CRS stack, using the following commands: 
    #cd $CRS_HOME/bin
#crsctl start
  6. Enter the following command to confirm that the ONS is started and is online: 
    %crs_stat -t

    Check the background processes for the ONS process. When you have confirmed that ONS processes are running, you can proceed to add a node to your existing installation.

This issue is tracked by Oracle bug 6973220.

15.14 ONS Goes Offline When Upgrading CRS

When upgrading CRS from release 10.2.0.1 to 10.2.0.2 to 10.2.0.5, the ONS process goes offline.

This issue is tracked with Oracle bug 8925749.

15.15 ORA-29844 Error When Downgrading to 10.2.0.4

The following Oracle Spatial error may be seen in the catrelod.out file when downgrading from 10.2.0.5 to 10.2.0.4:

ORA-29844: duplicate operator name specified

Workaround:

Ignore this error.

This issue is tracked with Oracle bug 9023792.

15.16 Use ASMCA to Administer Disk Groups for Older Database Versions

If you install Oracle Clusterware on Oracle Database 11g Release 2 and install Oracle RAC on Oracle Database 10g Release 2, then use ASM Configuration Assistant (ASMCA) to create and modify diskgroups. Starting with 11g Release 2, Oracle ASM is installed as part of a grid infrastructure installation, with Oracle Clusterware. You can no longer use Database Configuration Assistant (DBCA) to perform administrative tasks on Oracle ASM.

15.17 Error When Trying to Stop ULTRASEARCH with searchctl stop Command

When you try to run the searchctl stop command to stop ULTRASEARCH, the following error may occur:

java.io.IOException: Server protocol was not ORMI

This issue is tracked with Oracle bug 9448941.

15.18 CRS Installer Hangs When Upgrading from 10205 to 11201

When Upgrading CRS from 10.2.0.5 to 11.2.0.1, CRS installer hangs when you select Upgrade Grid Infrastructure option and click Next.

Workaround: Shutdown the CRS Stack after upgrading CRS to 10.2.0.5 and before invoking the 11.2.0.1 CRS installer. Run the following command:

crsctl stop crs

This issue is tracked with Oracle bug 9593297.

15.19 Non-ASCII Characters in Help Navigator Window May Be Displayed Improperly

Non-ASCII characters in the Help Navigator window may not be displayed properly and appear to be distorted for most Java GUI conventional components, such as Oracle Database Configuration Assistant, Oracle Database Upgrade Assistant, NetCA, NetMgr, Oracle Directory Manager, Oracle WM, and Locale Builder. The issue appears when the operating system locale includes a character encoding other than the one used to encode the help files. For example, the problem is visible when the UTF-8 encoding is used. The issue slightly impacts five translated European languages and severely impacts Chinese and Korean languages. Japanese language is not affected. This issue only affects the help navigation tree and has no effects on the help topic window.

Workaround:

You should change the operating system locale to one from the following list to see the Help Navigator contents properly:

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

Complete one of the following tasks to change the locale:

  • Run the following commands to alter the locale in a terminal session temporarily:In sh and related shell programs: 
    $ LANG=locale
$ export LANG

    In csh and related shell programs:

    $ setenv LANG locale

    Use this terminal session to start the components to see only the help topics. You should start components for other tasks in other terminals that have the default locale.

  • Create shell files to start the affected components with the required locale. For example, create the following file to run Oracle Database Configuration Assistant with Simplified Chinese locale: 
    #!/bin/sh
LANG=zh_CN.gb2312; export LANG; dbca

    Name the file, for example, dbca_zh_CN, place it in your path, set its executable bit, and use it to start the component.

    Note:

    This workaround does not apply when the component is called from a different program, such as Oracle Universal Installer.

  • To alter the system default locale as the operating system administrator, change the encoding entry to one of the suggested encodings in the /etc/sysconfig/i18n file. Then reboot the computer.
  • To alter the locale in the user login environment file, such as .bash_profile, add one of the following set of lines, depending on the file: 
    LANG=locale
export LANG

    or

    setenv LANG locale

With the modified operating system locale encoding, the file system related operations that use non-ASCII characters are affected. For example, creating a file with non-ASCII file name generates a different name depending on the locale used. A file created under one encoding cannot be opened with the same name under another encoding as the internal binary representation of the name differs. If you want to assure integrity of file system operations, do not use non-ASCII characters in file names when the workaround third or fourth is applied. Apply the first workaround to see only the help in the changed locale. If you want to apply the second workaround, do not use non-ASCII characters in file names processed by the affected Oracle components.

The change of the operating system locale may also cause a mismatch between the configuration of character terminals and the output of translated operating system utilities and third-party applications. You should either reconfigure the terminals to match the changed encoding or use the first and the second workarounds only.

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

This is tracked with Oracle bug 6503286.

15.20 Invalid Objects Seen After Upgrading Oracle Database from 9208 to 10205

After you upgrade Oracle database from release 9.2.0.8 to release 10.2.0.5 using the Database Upgrade Assistant from 10205 Oracle RAC home, the following invalid components are seen:

  • WK_UTIL
  • WK_CRW
  • WKDS_ADM
  • WK_ERR

Workaround: Install these components from the 10.2 Companion CD before applying the 10205 patch set.

This issue is tracked with Oracle bug 9351000.

16 Fixed Platform-Specific Bugs

The following table lists platform-specific bugs that have been fixed.

Fixed in Release Bug Number Description
10.2.0.5 6079571 ORA-07446: SDNFY: BAD VALUE ERROR SIGNALED FROM PARALLEL SLAVE
10.2.0.5 6620371 HUGEPAGES CAUSES SHARED MEMORY SEGMENTS TO START WITH PERMISSIONS OF 600
10.2.0.5 7506024 SDO_RELATE QUERY VERY SLOW ON V10.2.0.4
10.2.0.5 7582159 ORA-27090 CAN BE REPORTED BUT IS MISSING FROM MESSAGES FILE
10.2.0.5 8374326 CANNOT DISABLE AUTOSTART IN CRS SCRIPTS SUSE 10 ORACLE 11I AND 10G ORACLE RAC
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
10.2.0.3 5671740 INCOMPLETE CALL STACK FOR LINUX 64-BIT WITH 2.6.9 KERNEL

17 Patch Set Components

The following table provides a list of patch set components:

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

© 2010, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.

相关文章 | Related posts:

  1. Collecting Diagnostic information for Oracle block corruption
  2. Oracle Block Cache Layer And Its Corresponding Corruption Error Messages.
  3. TECH: Database Block Checking Features
  4. RMAN 11G : Data Recovery Advisor – RMAN command line example
  5. Handling Block Corruptions in Oracle7 / 8 / 8i / 9i / 10g / 11g
  6. 参数cluster_interconnect详细介绍
  7. Automatic PGA Memory Management
  8. gc lost blocks diagnostics
Oracle   , , , , , , , , , , , , , , , ,  
«  
  »

3 comments to 10.2.0.5 补丁集发布

  • Krystina Rizzuti
    May 14, 2010 at 10:15 PM · Reply

    found it on google. nice. ill come back to visit.

  • admin
    June 9, 2010 at 6:13 PM · Reply

    Notable fixes included in 10.2.0.5

    This section lists fixes / enhancements in 10.2.0.5 which may cause a notable change in behaviour.
    6155146 Wrong results from query rewrite with pushed predicate
    6023472 Collection of changes to auditing

    Issues introduced in 10.2.0.5

    This section lists bugs introduced in 10.2.0.5 (if any). Such issues may be either serious or trivial but the aim is to list them all to help customers assess the risk of applying the Patch Set on top of 10.2.0.4
    9711859+ ORA-600 [ktsptrn_fix-extmap] during extent allocation caused by bug 8198906

  • TEXASJ
    September 9, 2011 at 5:20 PM · Reply

    Thanks for this excellent doc.
    Today I was upgrading the database from 9.2.8.0 linux_x86 to 10.2.0.1.0 after running utlrp.sql I got the error with 4 objects i.e.WK_UTIL,WK_CRW,WKDS_ADM, WK_ERR , I searched a log for getting out of this , but didn’t succeed , but
    as I know it’s a bug I can now resolve it as per your suggestions..!
    Thanks a bundle…! You made my day..!

Leave a Reply

  

  

  

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

«  
  »