Wednesday, April 6, 2011

Oracle® Database Patch Set Notes 10g Release 2 (10.2.0.2) Patch Set for Linux x86


10g Release 2 (10.2.0.2) Patch Set for Linux x86
February 2006
These patch set notes accompany the Oracle Database release 10.2.0.2 patch set. This document contains the following sections:
This document may be updated after release. To check for updates to this document, see document 316900.1 on the OracleMetalink Web site:
http://metalink.oracle.com
To locate document 316900.1:
  1. Log on to OracleMetalink.
  2. Click Advanced at the top of the OracleMetalink page.
  3. Enter 316900.1 in the Document ID field, then click Submit.


1 Patch Set Overview

Patch sets are a mechanism for delivering fully tested and integrated product fixes. Patch sets provide bug fixes only; they do not include new functionality and they do not require certification on the target system.
Patch sets include all of the libraries that have been rebuilt to implement the bug fixes in the set. All of the fixes in the patch set have been tested and are certified to work with each other. Because the patch set includes only low impact patches, it does not require you to certify applications or tools against the server
You can apply the Oracle Database release 10.2.0.2 patch set to the following Oracle Database 10g release 2 installations:
  • Oracle Database
  • Oracle Real Application Clusters
  • Oracle Database Client
  • Oracle Database Companion CD
  • Oracle Cluster Ready Services
For a list of products included in this patch set, see the "Patch Set Components" section.


2 Oracle Universal Installer Version Requirements

This patch set includes Oracle Universal Installer release 10.2.0.2, which is also installed when you install this patch set. This is to ensure that your Oracle home can be patched in the future. You should not use the Installer from the earlier maintenance release media or Oracle home.
This is not a complete software distribution. You must install it in an existing Oracle Database 10g (10.2.0.x) installation.


3 Patch Set Documentation

There are two documents related to this release of the Oracle Database patch set:
  • Oracle Database Patch Set Notes, 10g release 2 (10.2.0.2) Patch Set for Linux x86 (this document)
  • Oracle Database List of Bugs Fixed, 10g release 2 (10.2.0.2) Patch Set
Both of these documents are included with the patch set. In addition, they are available from document 316900.1, ALERT: Oracle 10g release 2 (10.2) Support Status and Alerts on the OracleMetalink Web site:
http://metalink.oracle.com
To locate document 316900.1:
  1. Log on to OracleMetalink.
  2. Click Advanced at the top of the OracleMetalink page.
  3. Enter 316900.1 in the Document ID field, then click Submit.
The following sections describe the contents of the Oracle Database Patch Set Notes and the Oracle Database List of Bugs Fixed.

Oracle Database Patch Set Notes, 10g Release 2 (10.2.0.2) Patch Set for Linux x86
This document provides:
  • System requirements and information about how to install or reinstall the patch set
  • A list of all bugs fixed to date that are specific to Oracle Database for Linux x86
  • A list of known issues relating to Oracle Database on Linux x86

Oracle Database List of Bugs Fixed, 10g Release 2 (10.2.0.2) Patch Set
The List of Bugs Fixed is a list of all generic bugs related to Oracle Database that have been fixed to date.


4 System Requirements

The following are the system requirements for this patch set:
  • Operating System
    • SUSE Linux Enterprise Server (SLES) 9
    • Red Hat Enterprise Linux AS/ES 3 or 4
  • Oracle Database (10.2.0.1.0)


5 Preinstallation Tasks

Complete the following preinstallation tasks before installing the patch set:


5.1 Review Known Preinstallation Issues

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


5.1.1 Upgrading Oracle E-Business Suite Databases

If you are an Oracle E-Business Suite customer and you want to upgrade your Oracle E-Business Suite release 11i database server to this patch set, then you must check the latest certification status and Interoperability Notes available on the OracleMetaLink Web site:
http://metalink.oracle.com


5.1.2 Upgrading Installations that use Physical or Logical Standby Databases

Before applying this patch set to an Oracle Database release 2 (10.2.0.1) installation that uses one or more physical or logical standby databases, review the following OracleMetalink documents:
  • For information about physical standby databases, review document 278641.1.
  • For information about logical standby databases, review document 278643.1.
These documents are available on the OracleMetaLink Web site:
http://metalink.oracle.com


5.1.3 Upgrading Installations that use Java Virtual Machine or Oracle interMedia

If any of the databases use Java Virtual Machine (Java VM) or Oracle interMedia, install the Oracle Database 10g Products installation type from the Oracle Database 10g Companion CD before installing the 10.2.0.2 patch set. For information about installing the Oracle Database 10g Products installation type from the Companion CD, see the Oracle Database 10g Installation Guide or the Oracle Database 10g Companion CD Installation Guide. This installation type includes the Natively Compiled Java Libraries (NCOMP) files to improve Java performance. If you do not install the NCOMP files, the ORA-29558:JAccelerator (NCOMP) not installed error occurs when a database that uses Java VM is upgraded to the patch release.


5.1.4 Upgrading Oracle Cluster Ready Services

The Oracle Clusterware software must be at the same or newer level as the Oracle software in the Real Application Clusters (RAC) Oracle home. Therefore, you should always upgrade Oracle Clusterware before you upgrade RAC.


5.1.5 Notes to OLAP users

To apply this patch set, the OLAP users should ensure that the base release is the Enterprise Edition of 10.2.0.1.0 with the OLAP option installed. Oracle highly recommends the Data Warehouse configuration type to optimize the database for OLAP.
If you are moving your Oracle database from a 32-bit operating system to a 64-bit operating system, either prior to applying the patch set or after applying the patch set, review document 352306.1 on the OracleMetalink Web site:
http://metalink.oracle.com
To locate document 352306.1:
  1. Log on to OracleMetalink.
  2. Click Advanced at the top of the OracleMetalink page.
  3. Enter 352306.1 in the Document ID field, then click Submit.


5.2 Identify the Oracle Database Installation

This is not a complete software distribution. You must install it in an existing Oracle Database 10g Oracle home. To identify Oracle home directories, view the /etc/oratab file.
If you are installing this patch set on an existing Oracle Real Applications Cluster (RAC) 10g release 10.2.0.1 installation, you must run Oracle Universal Installer from the same node from which the Oracle Database software was installed.


5.3 Check Postrelease Updates

Before installing this patch set in a production environment, review document 316900.1, ALERT: Oracle 10g release 2 (10.2) Support Status and Alerts, available on the OracleMetaLink Web site:
http://metalink.oracle.com
To locate this document:
  1. Log on to OracleMetalink.
  2. Click Advanced at the top of the OracleMetalink page.
  3. Enter 316900.1 in the Document ID field, then click Submit.
This document is created by Oracle Support Services and provides information about the status of issues discovered after this patch set was released. If you are unable to access this site, then contact Oracle Support Services before installing this patch set in a production environment.


5.4 Download and Extract the Installation Software

To download and extract the patch set installation software:
  1. Download the p4547817_10202_LINUX.zip patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory.
  2. Enter the following command to unzip and extract the installation files:
    $ unzip p4547817_10202_LINUX.zip


5.5 Set the ORACLE_HOME and ORACLE_SID Environment Variables

Enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables:
  • Bourne, Bash, or Korn shell:
    $ ORACLE_HOME=oracle_home
$ ORACLE_SID=sid
$ export ORACLE_HOME ORACLE_SID
  • C shell:
    % setenv ORACLE_HOME oracle_home
% setenv ORACLE_SID sid
In these examples, oracle_home is the Oracle home directory where the Oracle Database 10g installation that you want to upgrade is installed, and sid is the SID of the database that you want to upgrade.


5.6 Stop All Processes

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

Note:
If you shut down ASM instances, you must first shut down all database instances that use ASM, even if these databases run from different Oracle homes.
  • If you are upgrading a single instance installation, shut down the following Oracle Database 10g processes before installing the patch set:

    Note:
    You must perform these steps in the order listed.
    1. Shut down all processes in the Oracle home that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus.

      Note:
      Before you shutdown all processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage.
    2. Shut down all database instances running in the Oracle home directory, where you need to install the patch set.
    3. Shut down the ASM instance, if the ASM instance is running in the Oracle home directory, where you need to install the patch set.
    4. Shut down all listeners running in the Oracle home directory, where you need to install the patch set.
    5. Shut down the Oracle Cluster Synchronization Services (CSS) daemon as the root user:
      # /etc/init.d/init.cssd stop
  • If you are upgrading a Oracle Clusterware installation, shut down the following Oracle Database 10g processes before installing the patch set:

    Note:
    You must perform these steps in the order listed.
    1. Shut down all processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control.

      Note:
      Before you shutdown all processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage.
    2. Shut down all RAC instances on all nodes. To shut down all RAC instances for a database, enter the following command where db_name is the name of the database:
      $ oracle_home/bin/srvctl stop database -d db_name
    3. Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command where node is the name of the node where the ASM instance is running:
      $ oracle_home/bin/srvctl stop asm -n node
    4. Stop all node applications on all nodes. To stop node applications running on a node, enter the following command where node is the name of the node where the applications are running:
      $ oracle_home/bin/srvctl stop nodeapps -n node
    5. Shut down the Oracle Clusterware process by entering the following command on all nodes as the root user:
      # crs_home/bin/crsctl stop crs

      Note:
      If the Oracle Clusterware installation is not on a shared Oracle home you can upgrade the Oracle Clusterware installation one node at a time. To do this, perform the preceding steps only on the first node that you are upgrading, then follow the instructions on the installer screen.
  • If you are upgrading a RAC installation, shut down the following Oracle Database 10g processes before installing the patch set:

    Note:
    You must perform these steps in the order listed.
    1. Shut down all processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control.

      Note:
      Before you shutdown all processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage.
    2. Shut down all RAC instances on the nodes, which run from the Oracle home on which you are going to apply the patch set. To shut down all RAC instances for a database, enter the following command where db_name is the name of the database:
      $ oracle_home/bin/srvctl stop database -d db_name
    3. Shut down all ASM services on all nodes. To shut down an ASM instance, enter the following command where node is the name of the node where the ASM instance is running:
      $ oracle_home/bin/srvctl stop asm -n node
    4. 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:
      $ oracle_home/bin/srvctl stop listener -n node [-l listenername]


5.7 Back Up the System

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


6 Installation Tasks

You can install the patch set either interactively or noninteractively. See one of the following sections for information about how to complete the installation:


6.1 Installing the Oracle Database 10g Patch Set Interactively

To install the Oracle Database 10g patch set interactively:

Note:
If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle Database 10g release 10.2.0.1 installation, Oracle Universal Installer displays a warning dialog with the following error:
OUI-10091: There are no patches that need to be applied from the patchset Oracle Database 10g Release 2 Patch Set 1
 10.2.0.2.0
The Oracle Universal Installer does not allow the installation to proceed. Click OK, then click Cancel to end the installation.
  1. Log in as the oracle user.
  2. If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:
    • Bourne, Bash, or Korn shell:
      $ DISPLAY=local_host:0.0 ; export DISPLAY
    • C shell:
      % setenv DISPLAY local_host:0.0
    In this example, local_host is the host name or IP address of the system that you want to use to display Oracle Universal Installer (your workstation or PC).
  3. Enter the following commands to start Oracle Universal Installer, where patchset_directory is the directory where you unzipped the patch set software:
    % cd patchset_directory/Disk1
% ./runInstaller
  4. On the Welcome screen, click Next.
  5. On the Specify File Locations screen, click Browse next to the Path field in the Source section.
  6. Select the products.xml file from the stage directory where you unpacked the patch set files, then click Next. For example:
    directory_path/stage/products.xml
  7. In the Name field in the Destination section, select the name of the Oracle home that you want to update from the drop down list, then click Next.
  8. If you are installing the patch set on a RAC cluster, click Next when the Selected Nodes screen appears.
  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 a RAC installation, then run the root.sh script on each node of the cluster.

    Note:
    If you are applying this patch set to a Oracle Clusterware installation:
    • If you shut down all Oracle Clusterware services on all nodes as described in the "Preinstallation Tasks" section before starting the installation, then complete all of the steps except the first step in the instructions displayed by the installer screen.
    • If you did not shut down all Oracle Clusterware services on all nodes, complete all of the steps in the instructions displayed by the installer screen.
    The Oracle Clusterware installation instructions displayed on the Oracle Universal Installer screen are also available in the $CRS_HOME/install/readme.txt file.
  11. On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.


6.2 Installing the Oracle Database 10g Patch Set Noninteractively

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

    Note:
    For RAC installations, make sure the CLUSTER_NODES variable specifies all of the nodes used in the original RAC installation.
  3. To run Oracle Universal Installer, enter a command similar to the following, where response_file is the full path to the response file that you edited:
    % ./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 a RAC installation, then run the root.sh script on each node of the cluster.

    Note:
    If you are applying this patch set to a Oracle Clusterware installation:
    • If you shut down all Oracle Clusterware services on all nodes as described in the "Preinstallation Tasks" section before starting the installation, then complete all of the steps except the first step in the CRS_HOME/install/readme.txt file.
    • If you did not shut down all Oracle Clusterware services on all nodes, complete all of the steps in the CRS_HOME/install/readme.txt file.


7 Postinstallation Tasks

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


7.1 Upgrading Earlier Oracle Database 10g Release 1 to Oracle Database 10g Release 2 (10.2.0.2)

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

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

For information about upgrading Oracle databases from an earlier Oracle database release 1 (8i, 9i, or 10g), see the Oracle Database Upgrade Guide.
If you are upgrading a RAC database, refer to the Oracle Real Application Clusters Administration Guide as well

7.1.2 Upgrading a Release 9.2 Database Not Using OLS

If you want to upgrade an Oracle9i release 9.2 preconfigured database, and you are not using Oracle Label Security (OLS), complete the following steps to avoid errors during the upgrade:
  1. Use Oracle Universal Installer release 9.2 to install OLS using the Custom installation type.
  2. Run the $ORACLE_HOME/rdbms/admin/catnools.sql script with the SYSDBA privilege to remove OLS components from the database.


7.2 Upgrading Oracle Database 10g Release 10.2.0.1 to Oracle Database 10g Release 10.2.0.2

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

7.2.1 Required Preupgrade Checks

Review the following sections before upgrading a database.

7.2.1.1 Check SYSTEM Tablespace Size
If JServer is part of the installation ensure that there is at least 10 MB of free space allocated to the SYSTEM tablespace.

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

7.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters
Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:
  1. Start the database:
    SQL> STARTUP NOMOUNT
  2. If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):
    SQL> SHOW PARAMETER PFILE;
    This command displays the name and location of the server parameter file or the initialization parameter file.
  3. Determine the current values of these parameters:
    SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE
  4. If the system is using a server parameter file:
    1. If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
      SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
    2. If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:
      SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
  5. If the system uses an initialization parameter file, if necessary change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).
  6. If you use Automatic Shared Memory Management, ensure that the value of the SGA_TARGET initialization parameter size is at least 50 MB greater than the sum of the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters.

    Note:
    The value of the SGA_TARGET parameter depends on your environment. If you receive a system error when you restart the database, increase the value of theSGA_TARGET parameter to the value specified in the error.
  7. Shut down the database:
    SQL> SHUTDOWN

7.2.2 Upgrade the Release 10.2 Database

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

Note:
If you do not run the catupgrd.sql script as described in this section and you start up a database for normal operation, then ORA-01092: ORACLE instance terminated. Disconnection forced errors will occur and the error ORA-39700: database must be opened with UPGRADE option will be in the alert log.
  1. Log in as the Oracle software owner user.
  2. For RAC installations, start listener on each node of the cluster as follows:
    $ srvctl start listener -n nodename
  3. If you are using ASM, start the ASM instance.
  4. For single-instance installations, start the listener as follows:
    $ lsnrctl start

    Note:
    If you are using the Oracle OLAP option, make sure that the listener is running.
  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 / AS SYSDBA
  6. For RAC installations:
    1. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
      $ sqlplus /nolog 
SQL> CONNECT / AS SYSDBA
SQL> STARTUP NOMOUNT
    2. Set the CLUSTER_DATABASE initialization parameter to FALSE:
      SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
    3. Shutdown 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
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.2 patch set is applied to an Oracle Database 10g Standard Edition database or Standard Edition One database, there may be 42 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation.
    Ignore any messages indicating that the database contains invalid recycle bin objects similar to the following:
    BIN$4lzljWIt9gfgMFeM2hVSoA==$0
  12. If you are using the Oracle Recovery Manager catalog, enter the following command:
    $ rman catalog username/password@alias 
RMAN> UPGRADE CATALOG;
  13. For RAC installations:
    1. Set the CLUSTER_DATABASE initialization parameter to TRUE:
      SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
    2. Restart the database:
      SQL> SHUTDOWN
SQL> STARTUP
    3. Start any processes that you want to use:
      $ srvctl start service -d db_name -s service_name


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


Important:
Oracle recommends using the most restrictive file permissions possible for your given implementation. Perform these optional steps only after considering all security ramifications and only if you need to share this installation.
During patchset installation, all new files and directories are created with restricted access, by default. Users or third party applications with a different group identifier from that of the database, which try to access client-side utilities or libraries in the database home, will see permission errors when trying to access these files or directories. Perform the following steps to change the permissions:
  1. Change your directory to:
    $ cd $ORACLE_HOME/install
  2. Run changePerm.sh and specify the patched server Oracle home location, before accessing client-side utilities or libraries in the database home.

    Note:
    If you are patching RAC home, then you will need to run this script on all the nodes.


8 Removing the Patch Set Software

The catdwgrd.sql script enables the user to restore the Oracle Database installation of the database back to the original 10.2 release that the user backed up before applying the patch set. The catdwgrd.sqlscript is run in the 10.2.0.2 Oracle home to perform necessary downgrade actions. After the 10.2.0.1 release is restored, the catrelod.sql script is run from 10.2.0.1 Oracle home to reload the 10.2.0.1 release packages and views.
Perform the following steps for backing out from the 10.2.0.x patch release:
  1. Before restoring the Oracle home to the original release, perform the following steps:
    $ sqlplus /nolog
SQL> connect / AS SYSDBA
SQL> SHUTDOWN
SQL> STARTUP  DOWNGRADE
SQL> SPOOL downgrade.out
SQL> @?/rdbms/admin/catdwgrd.sql
SQL> SHUTDOWN IMMEDIATE
  2. Review the downgrade.out file for errors.
  3. Copy the 10.2.0.2 version of rdbms/admin/catrelod.sql out of the Oracle home to save it.

    Note:
    The 10.2.0.1 version of catrelod.sql script always runs utlip.sql script to invalidate all PL/SQL packages. To avoid running utlip.sql script when you reload the 10.2.0.1 packages and views, you can use the 10.2.0.2 version of catrelod.sql if you save it before restoring the original Oracle home.
  4. Restore the Oracle10g installation and Central Inventory (see /etc/oraInst.loc) that you backed up before applying the patch set.
  5. After restoring the original Oracle home, copy the saved version of catrelod.sql script into the restored Oracle home rdbms/admin directory, and then perform the following steps:
    $ sqlplus /nolog
SQL> connect / AS SYSDBA
SQL> STARTUP UPGRADE
SQL> SPOOL reload.out
SQL> @?/rdbms/admin/catrelod.sql
  6. Shut down the database:
    SQL> SHUTDOWN IMMEDIATE
  7. Review the reload.out file for errors.

    Note:
    Ignore the ORA-29844 and ORA-31085 errors found in the reload.out file. These errors are tracked with Oracle bugs 4758112 and 4425495 respectively.

    Note:
    After reloading the 10.2.0.1 release, the version numbers for Data Mining and OLAP Analytic Workspace remain at 10.2.0.2. These issues are tracked with Oracle bugs 4758695 and 4751917.
  8. Start the database and recompile the remaining invalid objects:
    SQL> STARTUP
SQL> @?/rdbms/admin/utlrp.sql


9 Reinstalling the Patch Set Software

If necessary, you can reinstall a patch set that has been applied to an Oracle Database 10g installation. You must reinstall the patch set interactively.
To reinstall the patch set:
  1. Log in as the oracle user.
  2. If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:
    • Bourne, Bash, or Korn shell:
      $ DISPLAY=local_host:0.0 ; export DISPLAY
    • C shell:
      % setenv DISPLAY local_host:0.0
    In this example, local_host is the host name or IP address of the system that you want to use to display Oracle Universal Installer (your workstation or PC).
  3. Enter the following commands to start Oracle Universal Installer, where patchset_directory is the directory where you unzipped the patch set software:
    $ cd patchset_directory/Disk1
$ ./runinstaller
  4. If you are installing the patch on a RAC cluster, click Next on the Selected Nodes screen.
  5. On the Specify File Locations screen, click Browse next to the Path field in the Source section.
  6. Select the products.xml file from the stage directory where you unpacked the patch set files. For example:
    /stage/products.xml
  7. Select the Oracle home that you want to upgrade in the Name field in the Destination section, then click Next.

    Note:
    If you are not sure of the name of the Oracle home, click Installed Products to determine the name of the Oracle home that you want to upgrade.
    The Available Product Component screen appears. This screen contains a list of all components that have been patched by the original patch set installation. These components are grayed out, indicating they cannot be selected for installation.
  8. Expand the nodes for each component listed in the tree to display the patch that corresponds to each component.
  9. Select the patches that you want to install.
    When you select a patch, the Install Status column changes to reinstall.
  10. Repeat the process for each patch bundled in the patch set, then click Next.
  11. On the Summary screen, verify the list of patches to be reinstalled, then click Install.
  12. On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.


10 Known Issues

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


10.1 Upgrading Oracle Database Software Version Using Oracle Data Guard and SQL Apply

Using a logical standby database, you can upgrade Oracle database software and patch sets with almost no downtime. Using Data Guard SQL Apply, you can perform a rolling upgrade of the Oracle database software from patchset release 10.2.0.1 to the 10.2.0.2 patchset release. During a rolling upgrade, you can run different releases of Oracle Database on the primary and logical standby databases, while you upgrade them, one at a time, incurring minimal downtime on the primary database.
For complete information and instructions, see OracleMetaLink note 300479.1.


10.2 Invalid Link to Monitor in Memory Access Mode Feature

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


10.3 Oracle Scheduler External Jobs

If you use Oracle Scheduler, that is, (dbms_scheduler) external jobs on Linux, and have modified the owner or group of the extjob executable, then this patch set will reset these changes.
Beginning with Oracle Database release 10.2.0.2, the supported way to change the user or group that external jobs run as is to modify the externaljob.ora file in rdbms/admin. This file is owned by root user and only the root user can modify this file. Changes to this file take effect immediately and do not require restarting the database.


10.4 Upgrading Preconfigured Standard Edition Databases

If you are using an Oracle Database release 10.2.0.1 preconfigured Standard Edition database, then the database contains the following components that are not supported by the Standard Edition:
  • Oracle Data Mining
  • Oracle OLAP Catalog
  • Oracle OLAP Analytic Workspace
  • Oracle OLAP API
  • Spatial
  • OLAP SQL Scripts
The catupgrd.sql script does not run the patch scripts for these components. It sets the component STATUS to OPTION OFF in the DBA_REGISTRY view. The original versions of the dictionary objects for the components remain in the database but the catupgrd.sql script does not apply the patch to them.


11 Fixed Platform-Specific Bugs

The following table is a cumulative list of the platform-specific bugs fixed in all Oracle Database patch sets to date:
Fixed in ReleaseBug NumberDescription
10.2.0.24747264WRONG PERMISSIONS AFTER CLIENT INSTALL OF 10GR2 (10.2.0.1)
10.2.0.24516865WRONG PERMISSIONS AFTER INSTALLATION IN OH AND SUBSEQUENT DIRECTORIES


12 Patch Set Components

The following table provides a list of patch set components:
ComponentVersion
Advanced Queuing (AQ) API10.2.0.2
Advanced Queuing (AQ) API Demos10.2.0.2
Advanced Replication10.2.0.2
Agent Required Support Files10.2.0.2
Assistant Common Files10.2.0.2
Authentication and Encryption10.2.0.2
Authentication and Encryption 32-bit10.2.0.2
CSS Single-instance Common Files10.2.0.2
Character Set Migration Utility10.2.0.2
Cluster Ready Services10.2.0.2
DBJAVA Required Support Files10.2.0.2
Data Management Services Common Files10.2.0.2
Data Mining Scoring Engine10.2.0.2
Database Configuration Assistant10.2.0.2
Database SQL Scripts10.2.0.2
Database Upgrade Assistant10.2.0.2
Database Verify Utility10.2.0.2
Database Workspace Manager10.2.0.1
Enterprise Manager Agent10.2.0.2
Enterprise Manager Common Files10.2.0.2
Enterprise Manager Repository10.2.0.2
Enterprise Manager plugin Common Files10.2.0.2
Export/Import10.2.0.2
External Naming: NIS10.2.0.2
Generic Connectivity Common Files10.2.0.2
Generic Connectivity Using ODBC10.2.0.2
HAS component of Oracle Clusterware install10.2.0.2
Installation Common Files10.2.0.2
iSQL*Plus10.2.0.2
JAccelerator (NCOMP)10.2.0.2
JDBC Common Files10.2.0.2
JDBC/OCI Common Files10.2.0.2
JDBC/OCI Common Files for Instant Client10.2.0.2
LDAP Required Support Files10.2.0.2
New Database ID10.2.0.2
OLAP Analytic Workspace Manager10.2.0.2
Object Type Translator10.2.0.2
Oracle C++ Call Interface10.2.0.2
Oracle C++ Call Interface Demos10.2.0.2
Oracle C++ Call Interface for Instant Client10.2.0.2
Oracle Call Interface (OCI)10.2.0.2
Oracle Call Interface (OCI) Demos10.2.0.2
Oracle Client10.2.0.2
Oracle Client Required Support Files10.2.0.2
Oracle Common Schema Demos10.2.0.2
Oracle Connection Manager10.2.0.2
Oracle Containers for Java10.2.0.2
Oracle Containers for Java Demos10.2.0.2
Oracle Text Knowledge Bases10.2.0.2
Oracle Core Required Support Files10.2.0.2
Oracle Data Mining10.2.0.2
Oracle Data Mining Demos10.2.0.2
Oracle Database 10G10.2.0.2
Oracle Database 10G Companion Products10.2.0.2
Oracle Database 10G Products10.2.0.2
Oracle Database Demos10.2.0.2
Oracle Database Utilities10.2.0.2
Oracle Data Mining10.2.0.2
Oracle Enterprise Manager Console DB10.2.0.2
Oracle Globalization Support10.2.0.2
Oracle Globalization Support Demos10.2.0.2
Oracle Instant Client10.2.0.2
Oracle Instant Client Required Support Files10.2.0.2
Oracle interMedia Annotator10.2.0.2
Oracle interMedia Client Demos10.2.0.2
Oracle interMedia Common Files10.2.0.2
Oracle interMedia Client Compatibility Files10.2.0.2
Oracle interMedia Image10.2.0.2
Oracle interMedia Image Accelerator10.2.0.2
Oracle interMedia Java Advanced Imaging10.2.0.2
Oracle interMedia Locator10.2.0.2
Oracle Internet Directory Client10.2.0.2
Oracle Internet Directory Client Common Files10.2.0.2
Oracle Internet Directory Tools10.2.0.2
Oracle JDBC Development Drivers10.2.0.2
Oracle JDBC Development Drivers Demos10.2.0.2
Oracle JDBC Development Drivers for Instant Client10.2.0.2
Oracle JDBC Thin Driver for JDK 1.210.2.0.2
Oracle JDBC Thin Driver for JDK 1.410.2.0.2
Oracle JDBC Thin Driver for JDK 1.4 for Instant Client10.2.0.2
Oracle JVM10.2.0.2
Oracle Java Tools10.2.0.2
Oracle Label Security10.2.0.2
Oracle Label Security Demos10.2.0.2
Oracle Locale Builder10.2.0.2
Oracle Net10.2.0.2
Oracle Net Configuration Assistant10.2.0.2
Oracle Net Listener10.2.0.2
Oracle Net Manager10.2.0.2
Oracle Net Required Support Files10.2.0.2
Oracle OLAP10.2.0.2
Oracle OLAP API10.2.0.2
Oracle OLAP Catalog10.2.0.2
Oracle OLAP Worksheet10.2.0.2
Oracle Partitioning10.2.0.2
Oracle RAC Required Support Files10.2.0.2
Oracle RAC Required Support Files-HAS10.2.0.2
Oracle Real Application Clusters10.2.0.2
Oracle SQLJ10.2.0.2
Oracle Spatial10.2.0.2
Oracle Spatial Demos10.2.0.2
Oracle Starter Database10.2.0.2
Oracle Text10.2.0.2
Oracle Text Samples10.2.0.2
Oracle Transparent Gateway for IBM DRDA10.2.0.2
Oracle Ultra Search Common Files10.2.0.2
Oracle Ultra Search Middle-Tier10.2.0.2
Oracle Ultra Search Server10.2.0.2
Oracle Wallet Manager10.2.0.2
Oracle XML Developer's Kit10.2.0.2
Oracle XML SQL Utility10.2.0.2
Oracle 10g Real Application Clusters Common Files10.2.0.2
PL/SQL10.2.0.2
PL/SQL Embedded Gateway10.2.0.2
PL/SQL Required Support Files10.2.0.2
Parser Generator Required Support Files10.2.0.2
Precompiler Common Files10.2.0.2
Precompiler Required Support Files10.2.0.2
Pro*C/C++10.2.0.2
Pro*C/C++ Demos10.2.0.2
Pro*COBOL (32-bit and 64-bit)10.2.0.2
Pro*FORTRAN10.2.0.2
Pro*FORTRAN Demos10.2.0.2
RDBMS Required Support Files10.2.0.2
Recovery Manager10.2.0.2
Replication API10.2.0.2
SQL*Loader10.2.0.2
SQL*Plus10.2.0.2
SQL*Plus Demos10.2.0.2
SQL*Plus Required Support Files10.2.0.2
SQLJ Runtime10.2.0.2
SRVM component of Oracle Clusterware install10.2.0.2
SSL Required Support Files10.2.0.2
SSL Required Support Files for Instant Client10.2.0.2
Sample Schema10.2.0.2
Secure Socket Layer10.2.0.2
Utilities Common Files10.2.0.2
XDK Required Support Files10.2.0.2
XML10.2.0.2
XML Class Generator for C++10.2.0.2
XML Class Generator for Java10.2.0.2
XML Parser for C10.2.0.2
XML Parser for C++10.2.0.2
XML Parser for C++ Demos10.2.0.2
XML Parser for Java10.2.0.2
XML Transviewer Bean10.2.0.2
XML Transx10.2.0.2
XSQL Servlet10.2.0.2
XSQL Servlet Demos10.2.0.2


13 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.

Oracle Database Patch Set Release Notes, 10g Release 2 (10.2.0.2) Patch Set for Linux x86
Copyright © 2006 Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)