Oracle® Database

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.

• Oracle Universal Installer Operating System Prerequisite Checks

• Upgrading Oracle E-Business Suite Databases

• Upgrading Installations that use Physical or Logical Standby Databases

• Upgrading Installations that use Java Virtual Machine or Oracle interMedia

• Upgrading Oracle Clusterware

• Notes to Oracle OLAP Users

• Notes to Oracle Text Users

• Disabling Oracle Database Vault

./runinstaller -ignoreSysPrereqs

https://support.oracle.com

https://support.oracle.com

https://support.oracle.com

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 Contents 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.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 reapply 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.

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:

• Stopping All Processes for a Single Instance Installation

• Stopping All Processes for an Oracle Clusterware Installation

• Stopping All Processes for an Oracle RAC Installation

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

9.1 Installing the Oracle Database 10g Patch Set Interactively

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

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.

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

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

• Upgrading a Release 9.2 Database Not Using Oracle Label Security

• Missing Components When Upgrading

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

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 must 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:

• Upgrading a Release 10.2 Database using Oracle Database Upgrade Assistant

• Manually Upgrading a Release 10.2 Database

$ dbua -silent -dbname $ORACLE_SID -oracleHome 
$ORACLE_HOME -sysDBAUserName UserName -sysDBAPassword SYS_password 
-recompile_invalid_objects true

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.

10.7 Redeploying Oracle Workflow Server

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

To redeploy the Oracle Workflow Server:

1. Stop Oracle 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 Oracle 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 Oracle 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 must 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.

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 a 10.2.0.2 release, the version number for Oracle Data Mining remain at 10.2.0.5. This issue is tracked with Oracle bug 4758695.

   After reloading a 10.2.0.1 or a 10.2.0.2 release, the version number for Oracle OLAP Analytic Workspace remain at 10.2.0.5. This issue is tracked with Oracle bug 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.

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 the postupgrade 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 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.6 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 predefined 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 reinvoke setupCCR.

15.7 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.8 Oracle 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.9 500 Internal Server Error When Refreshing the View in Oracle Enterprise Manager

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

500 Internal Server Error

Workaround:

Close the existing Oracle Enterprise Manager session. After the database is fully restarted, open a new Oracle 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.10 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.11 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.12 Use ASMCA to Administer Disk Groups for Older Database Versions

If you install Oracle Clusterware 11.2 and Oracle RAC 10.2, then use Oracle ASM Configuration Assistant (ASMCA) to create and modify disk groups. 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.13 Error When Trying to Stop Oracle Ultra Search with searchctl stop Command

When you try to run the searchctl stop command to stop Oracle Ultra Search, the following error may occur:

java.io.IOException: Server protocol was not ORMI

This issue is tracked with Oracle bug 9448941.

15.14 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, Oracle Net Configuration Assistant, Oracle Net Manager, Oracle Directory Manager, Oracle Work Manager, 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 restart 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.15 Invalid Objects Seen After Upgrading Oracle Database from 9.2.0.8 to 10.2.0.5

After you upgrade Oracle database from release 9.2.0.8 to release 10.2.0.5 using the Database Upgrade Assistant from 10.2.0.5 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 10.2.0.5 patch set.

This issue is tracked with Oracle bug 9351000.

15.16 Oracle Partitioning Patch Shows Incorrect Version

After installing 10.2.0.5 patch set, the version number for Oracle Partitioning Patch component does not change to 10.2.0.5.

This issue is tracked with Oracle bug 9909729.