7.1 Review Known Preinstallation Issues

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

• Upgrading Oracle E-Business Suite Databases

• Upgrading Installations that use Physical or Logical Standby Databases

• Upgrading Installations that use Java Virtual Machine or Oracle interMedia

• Upgrading Oracle Clusterware

• Notes to Oracle OLAP Users

• Disabling Oracle Database Vault

http://metalink.oracle.com

http://metalink.oracle.com

http://metalink.oracle.com

7.2 Identify the Oracle Database Installation

This is not a complete software distribution. You must install it in an existing Oracle Database 10g Oracle home. To identify Oracle home directories, view the/etc/oratab file.Use Oracle Universal Installer to identify Oracle home directories. From the Welcome screen, click Installed Products, then click the Environment tab. You should then cross-check this by executing

opatch lsinventory -all

If you are installing this patch set on an existing Oracle Real Application Cluster 10g release 10.2.0.x installation, you must run Oracle Universal Installer from the same node from which the Oracle Database software was installed.

7.3 Check Postrelease Updates

Before installing this patch set in a production environment, review document 316900.1, ALERT: Oracle 10g release 2 (10.2) Support Status and Alerts, available on the OracleMetaLink Web site:

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.

7.4 Download and Extract the Installation Software

Download and extract the p6810189_10204_Win32.zip patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory.

7.5 Update Oracle Time Zone Definitions

The 10.2.0.4 patch set includes an update to the Oracle time zone definitions to Version 4. This version of the time zone definitions includes the changes to daylight saving time in the USA in 2007 and other updates.

In the Oracle database the TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) and TIMESTAMP WITH TIME ZONE (TSTZ) data types and the TZ_OFFSET function select the time zone information from the time zone files.

It may be necessary to take action on existing TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) and TIMESTAMP WITH TIME ZONE (TSTZ) data or to re-apply DST patches afterwards.

For full overview please see OracleMetaLink document 553812.1 Actions for the DSTv4 update in the 10.2.0.4 patchset.

1. When patching from a lower 10.2 release or upgrading from 10.1.0.X directly to 10.2.0.4, check the current version of the Oracle time zone definitions with the following command:

   SELECT version FROM v$timezone_file;
   

   • If this query reports version 4, no action is required; in this case, continue with steps described in section 7.6.

   • If this reports a version lower or higher then 4, see OracleMetalink document 553812.1 Actions for the DSTv4 update in the Release 10.2.0.4 patchset.

2. On upgrading from Release 9i directly to Release 10.2.0.4, see OracleMetaLink document 553812.1 Actions for the DSTv4 update in the 10.2.0.4 patchset.

3. On upgrading from Release 8.1.7 directly to Release 10.2.0.4, no action is required because Release 8.1.7 has no timezone data stored; in this case continue with steps described in section 7.6.

7.6 Stop All Services

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

• Stopping All Services for a Single Instance Installation

• Stopping All Services for an Oracle Clusterware Installation

• Stopping All Services for an Oracle RAC Installation

• Stopping All Services for an Oracle Clusterware Installation

• Stopping All Services for an Oracle RAC Installation

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

8.1 Installing the Oracle Database 10g Patch Set Interactively

To install 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 3
10.2.0.4

1. Log on as a member of the Administrators group to the computer on which you are going to install Oracle components. If you are installing on a Primary Domain Controller or a Backup Domain Controller, log on as a member of the Domain Administrators group.

2. Start Oracle Universal Installer located in the unzipped area of the patch set. For example, Oracle_patch\setup.exe.

3. On the Welcome screen, click Next.

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

5. If you are installing the patch set on an Oracle RAC cluster, click Next when the Selected Nodes screen appears.

   
   

   Note: The Selected Nodes screen lists the existing Oracle RAC 10g release 2 nodes. The first node in the list is the node from where the Oracle RAC 10g release 2 software was installed. You must install the patch set software from this node. If this is not the node where you are running Oracle Universal Installer, exit and install the patch set software from the first node in the list of nodes. Alternatively, reset the node order as follows: Exit Oracle Universal Installer. Enter a command similar to the following, where the node that you want to install the patch set from is the first node in the list of nodes: C:\Oracle_patch> setup.exe -updateNodeList "CLUSTER_NODES=node2,node1,node3" -local ORACLE_BASE\ORACLE_HOME=oracle_home_path In this example, the Oracle RAC 10g release 2 (10.2.0.x) software was installed from node1, but the patch set will be installed from node2.

   
   

6. On the Summary screen, click Install.

   When the installation is complete, the End of Installation screen appears.

   
   

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

   
   

7. On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.

8. Staring Oracle Database 10g Release 2 (10.2.0.4), the Oracle Process Manager service is supported for Oracle RAC. However, this service is not installed automatically and you need to install it manually. To install the Oracle Process Manager service, run the following command on each node of Oracle Clusterware:

   SYSTEM_DRIVE:> crs_home\bin\opmd -install
   

8.2 Installing the Oracle Database 10g Patch Set Noninteractively

To install the Oracle Database 10g patch set noninteractively:

1. Copy the response file template provided in the response directory where you unpacked the patch set archive file.

2. Edit the values for all fields labeled as <Value Required> as described by the comments and examples in the template.

   
   

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

   
   

3. Start Oracle Universal Installer located in the unzipped area of the patch set. You should pass the full path of the response file template you have edited locally as the last argument. For example:

   C:\Oracle_patch> setup.exe -silent -responseFile response_file_path
   

   
   

   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.

   
   

9.1 Updating Oracle Time Zone Definitions

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

• If the DST version in 7.5 was 4, no action is required.

• If f the DST version in 7.5 was higher than 4, reapply the version of DST patches as described in OracleMetaLink document 553812.1 Actions for the DSTv4 update in the 10.2.0.4 patchset.

• If the DST version in 7.5 was lower then 4, restore TSTZ data from backup (if any). For more information, see OracleMetaLink document 553812.1 Actions for the DSTv4 update in the 10.2.0.4 patchset.

• If you are upgrading from Release 8.1.7 directly to Release 10.2.0.4, no action is required.

9.2 Upgrading Earlier Oracle Database to Oracle Database 10g Release 2 (10.2.0.4)

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

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

• Upgrading a Release 9.2 Database Not Using Oracle Label Security

9.3 Upgrading Oracle Database 10g Release 10.2.0.x to Oracle Database 10g Release 10.2.0.4

See one of the following sections for upgrading an Oracle Database 10g release 10.2.0.x to Oracle Database 10g release 10.2.0.4:

• Upgrading a Release 10.2 Database using Oracle Database Upgrade Assistant

• Manually Upgrading a Release 10.2 Database

Oracle Database 10.2 Upgrade Information Utility    02-04-2008 11:48:11
.
**********************************************************************
Database:
**********************************************************************
--> name:       X102040
--> version:    10.2.0.1.0
--> compatible: 10.2.0.1
--> blocksize:  8192
.
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 505 MB
.... AUTOEXTEND additional space required: 15 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
.... 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 orinstalled]
**********************************************************************
--> Oracle Catalog Views         [upgrade]  VALID
--> Oracle Packages and Types    [upgrade]  VALID
--> JServer JAVA Virtual Machine [upgrade]  VALID
--> Oracle XDK for Java          [upgrade]  VALID
--> Oracle Java Packages         [upgrade]  VALID
--> Oracle Text                  [upgrade]  VALID
--> Oracle XML Database          [upgrade]  VALID
--> Oracle Workspace Manager     [upgrade]  VALID
--> Oracle Data Mining           [upgrade]  VALID
--> Messaging Gateway            [upgrade]  VALID
--> OLAP Analytic Workspace      [upgrade]  VALID
--> OLAP Catalog                 [upgrade]  VALID
--> Oracle OLAP API              [upgrade]  VALID
--> Oracle interMedia            [upgrade]  VALID
--> Spatial                      [upgrade]  VALID
--> Oracle Ultra Search          [upgrade]  VALID
--> Oracle Label Security        [upgrade]  VALID
--> Expression Filter            [upgrade]  VALID
--> EM Repository                [upgrade]  VALID
--> Rule Manager                 [upgrade]  VALID
PL/SQL procedure successfully completed.

9.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 (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> DROP FUNCTION DVSYS.REALM_SDML_AUTHORIZED ;
   SQL> DROP PROCEDURE DVSYS.SYNCHRONIZE_POLICY_FOR_OBJECT;
   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:

   C:\> 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 Oracle home for the database

   - jdbc_str: The JDBC connection string used to connect to the database. For example, jdbc:oracle:oci:@orcl1, where orcl1 is the net service name in the tnsnames.ora file (ORACLE_HOME\network\admin\tnsnames.ora).

   - owner_account: Oracle Database Vault Owner account name

   - acctmgr_account: (Optional) Oracle Database Vault Account Manager user

   - logfile: Optionally, specify a log file name and location. You can enter an absolute path or a path that is relative to the location of the $ORACLE_HOME/bin directory

   - nodecrypt: Reads plaintext passwords as passed on the command line. You must use this option if you are passing plaintext passwords to the command.

   
   

   Note: You are prompted to enter the SYS, Database Vault Owner, and Database Vault Account Manager passwords.

   
   
   
   

   See Also: Oracle Database Vault Installation Guide, 10g Release 2 (10.2) for Linux x86, Appendix C "Running DVCA After Creating a Database Vault Database" for more options available with the dvca -action option command

   
   

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 
   

   See Step 6 for details of the options used in the command.

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 Real Application Clusters (RAC) database, use the following command:

   C:\> ORACLE_HOME\bin\srvctl stop database -d db_name
   

7. Turn on Database Vault.

   C:\> cd ORACLE_HOME\bin
   C:\> move oradv10_backup.dll oradv10.dll
   

   
   

   Note: For an Oracle Real Application Clusters (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 Real Application Clusters (RAC) database, use the following command:

   C:\> 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:

   C:\> orapwd file=ORACLE_HOME\dbs\orapwSID password=sys_password force=y nosysdba=y
   

   Here SID is the Oracle system identifier (SID) of the database, and password is the password for the SYS account.

9.5 Oracle Database Extensions for .NET

If you use Oracle Database Extensions for .NET, then complete the following steps and start the OracleORACLE_HOMEClrAgent service:

1. Use SQL*Plus to deploy the DBMSClr.plb package:

   C:\> sqlplus /NOLOG
   SQL> CONNECT SYS AS SYSDBA
   Enter password:SYS_Password
   SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\DBMSClr.plb
   

2. Start the OracleORACLE_HOMEClrAgent service:

   From the Start menu, select Programs, then Administrative Tools and then Services to open the Services control panel then select OracleORACLE_HOMEClrAgent and click Start.

9.6 Configuring Oracle Configuration Manager in a Cloned Oracle Home

If you have installed and configured Oracle Configuration Manager in the original Oracle home directory, then complete the following procedure:

1. In the cloned Oracle home, remove all the subdirectories of the Oracle_home\ccr\hosts directory to remove the previously configured hosts.

2. In the cloned Oracle home, run the following command:

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

SYSTEM_DRIVE:> setupCCR

11.1 Removing the Patch Set Software for Single Instance Installation

Perform the following steps for removing the patch set from the 10.2.0.4 patch release:

1. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

   C:\> sqlplus /NOLOG
   SQL> CONNECT SYS AS SYSDBA
   Enter password:SYS_password
   SQL> SHUTDOWN IMMEDIATE
   SQL> EXIT
   

2. Take a backup of the following file in 10.2.0.4 Oracle home directory:

   C:\> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catrelod.sql
   C:\> @ORACLE_BASE\ORACLE_HOME\network\admin\tnsnames.ora
   

3. Enter the following SQL*Plus commands:

   C:\> cd ORACLE_BASE\ORACLE_HOME
   C:\> sqlplus /NOLOG
   SQL> CONNECT SYS AS SYSDBA
   Enter password:SYS_password
   SQL> STARTUP DOWNGRADE
   SQL> SPOOL downgrade.out
   SQL> @ORACLE_BASE\ORACLE_HOME\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 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.4\network\admin\tnsnames.ora directory into the restored Oracle home \network\admin\tnsnames.ora directory, and then perform the following steps:

   1. Start the service OracleServiceSID from the Control Panel by selecting Administrative Tools and then Services.

   2. Enter the following SQL*Plus commands:

      C:\> sqlplus /NOLOG
      SQL> CONNECT SYS AS SYSDBA
      Enter password:SYS_Password
      SQL> STARTUP DOWNGRADE
      SQL> SPOOL catrelod.out
      SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catrelod.sql
      SQL> SPOOL OFF
      SQL> SHUTDOWN IMMEDIATE
      

7. Review the catrelod.out file for errors.

8. Start the database and recompile the remaining invalid objects:

   SQL> STARTUP
   SQL> @ORACLE_BASE\ORACLE_HOME\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;
   

11.2 Removing the Patch Set Software for Oracle RAC Installation

Perform the following steps for removing the patch set from the 10.2.0.4 patch release:

1. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

   C:\> 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:

   C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop database -d db_name
   

4. Take a backup of the following files in 10.2.0.4 Oracle home directory:

   $ ORACLE_HOME/rdbms/admin/catrelod.sql
   $ ORACLE_HOME/network/admin folder
   

5. Enter the following SQL*Plus commands:

   C:\> sqlplus /NOLOG
   SQL> CONNECT SYS AS SYSDBA
   Enter password:SYS_password
   SQL> STARTUP DOWNGRADE
   SQL> SPOOL catdwgrd.out
   SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catdwgrd.sql
   SQL> SPOOL OFF
   SQL> SHUTDOWN IMMEDIATE
   SQL> EXIT
   

6. Complete the following steps to stop all Oracle Database services:

   1. Stop all node applications running on the node. Enter the following command, where node is the name of the node where the applications are running:

      C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop nodeapps -n node
      

      For Automatic Storage Management instances, perform the following step:

      C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop asm -n node
      

   2. Stop the services OracleServiceinst_name and OracleDBConsoleinst_name from the Control Panel by selecting Administrative Tools and then Services.

7. Restore the Oracle10g installation and Central Inventory that you backed up before applying the patch set on all the nodes.

8. After restoring the original Oracle home, copy the saved version of catrelod.sql script into the restored Oracle home rdbms\admin directory. Also copy the saved version of 10.2.0.4\network\admin\tnsnames.ora directory into the restored Oracle home \network\admin\tnsnames.ora directory, and then perform the following steps:

   1. Start the OracleServiceSID service from the Control Panel by selecting Administrative Tools and then Services.

   2. Enter the following SQL*Plus commands:

      C:\> sqlplus /NOLOG
      SQL> CONNECT SYS AS SYSDBA
      Enter password:SYS_Password
      SQL> STARTUP DOWNGRADE
      SQL> SPOOL catrelod.out
      SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catrelod.sql
      SQL> SPOOL OFF
      SQL> SHUTDOWN IMMEDIATE
      

9. Start the listener, gsd and ons processes:

   1. Start the node applications by entering the following command, where node is the name of the node where the applications are running:

      C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl start nodeapps -n node
      

      For Automatic Storage Management instances, perform the following step:

      C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl start asm -n node
      

   2. Start the service OracleServiceinst_name from the Control Panel by selecting Administrative Tools and then Services.

10. Review the catrelod.out file for errors.

11. Start the database and recompile the remaining invalid objects:

    SQL> STARTUP
    SQL> @ORACLE_BASE\ORACLE_HOME\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. 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
    

13. Start the database:

    1. Start the service OracleServiceinst_name from the Control Panel by selecting Administrative Tools and then Services.

    2. Start the database by entering the following command:

       C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl start database -d ORACLE_SID
       

    
    

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

    
    

14.1 Error While Deleting a Cluster Database Instance on a Shared Oracle Home on Windows

When you delete a cluster database instance on a shared Oracle Home on Windows, there may be an error message saying that EMCA has failed. This occurs when Database Control has been configured to manage the associated cluster database.

This issue is tracked with Oracle bug 4757173.

Workaround:

If this error occurs, you must determine if Database Control was running from the node from which the instance was deleted.

For example, assume a two-node cluster with nodes, node1 and node2, where orcl1 is an instance running on node1, while orcl2 is running on node2. If Database Control is running on node2, and orcl2 is the instance deleted, then you must do the following:

1. Run ORACLE_BASE\ORACLE_HOME\bin\emca using the -reconfig dbcontrol db options to reconfigure the Database Control deployment.

2. Manually delete the state directories ORACLE_BASE\ORACLE_HOME\node2_orcl2 and ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\OC4J_DBConsole_node2_orcl2.

If Database Control was running on node1 instead, and orcl2 was the instance deleted, then:

• You can safely ignore the error.

• You can manually delete the state directories ORACLE_BASE\ORACLE_HOME\node2_orcl2 and ORACLE_BASE\ORACLE_HOME\oc4j\j2ee\OC4J_DBConsole_node2_orcl2, if possible.

14.2 Upgrading Preconfigured Standard Edition Databases

If you are using an Oracle Database release 10.2.0.2 preconfigured Standard Edition database, then the database contains the following components that are not supported by the Standard Edition:

• Oracle Data Mining

• Oracle OLAP Catalog

• Oracle OLAP Analytic Workspace

• Oracle OLAP API

• Oracle Spatial

The catupgrd.sql script does not run the patch scripts for these components. It sets the component STATUS to OPTION OFF in the DBA_REGISTRY view. The original versions of the dictionary objects for the components remain in the database but the catupgrd.sql script does not apply the patch to them.

14.3 Database Upgrade Error While Running Oracle Database Upgrade Assistant

Oracle Database Upgrade Assistant fails to upgrade 10.2.0.1, 10.2.0.2 or 10.2.0.3 Oracle Real Application Clusters (RAC) database to 10.2.0.4 patch set if the Oracle RAC database is down.

Workaround

Enter the following command to start the database and retry the upgrade process:

C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl start database -d db_name -o mount

This issue is tracked with Oracle bug 5533745.

14.4 The Welcome Page of Oracle Database Upgrade Assistant Displays Incorrect Version

The Welcome page of Oracle Database Upgrade Assistant displays incorrect version of Oracle 9i. Oracle 9i Release 9.1.0 should read as Oracle 9i Release 9.0.1.

This issue is tracked with Oracle bug 6695802.

14.5 Running Oracle Database Upgrade Assistant on a Single Node Oracle RAC Installation

Oracle Database Upgrade Assistant fails during postinstallation upgrade on a single node and displays the following error message:

ORA-32001: write SPFILE requested but no SPFILE specified at startup

Workaround:

1. Start the database with the NOMOUNT option:

   C:\> sqlplus /NOLOG
   SQL> CONNECT SYS AS SYSDBA
   Enter password:SYS_password
   SQL> STARTUP NOMOUNT
   

2. Create SPFILE from PFILE by entering the following command where pfile_location is usually ORACLE_BASE\ORACLE_HOME\admin\db_name\pfile for Optimal Flexible Architecture compliant database:

   SQL> CREATE SPFILE=SHARED_LOCATION\SPFILE.ORA FROM PFILE=pfile_location\init.ora
   

3. Shut down the database:

   SQL> SHUTDOWN IMMEDIATE
   SQL> EXIT
   

4. Clear the contents of PFILE located at $ORACLE_HOME/dbs/initsid.ora and set the value of SPFILE as SHARED_LOCATION/SPFILE.ORA.

5. Run Oracle Database Upgrade Assistant:

   C:\> ORACLE_BASE\ORACLE_HOME\bin\dbua
   

This issue is tracked with Oracle bug 5531643.

14.6 Refresh From OracleMetaLink Job Fails in Oracle Enterprise Manager Database Control

If you attempt the Refresh from OracleMetaLink job in Oracle Enterprise Manager Database Control, then it displays the following error:

Exception trying to access the repository. java.sql.SQLException:
ORA-12899: value too large for column
"SYSMAN"."MGMT_ARU_PRODUCTS"."PRODUCT_NAME" (actual: 54, maximum: 50)

Workaround:

None. Oracle will release a one-off patch to address this issue.

This issue is tracked with Oracle bug 6755395.

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

14.8 Errors Displayed When Upgrading from Oracle Database 10g Release 2 (10.2.0.4)

When upgrading Oracle Database 10g Release 2 (10.2.0.4) to Oracle Database 11g Release 1 (11.1.0.6), the following errors are displayed:

ORA-06550: line 5, column 35:
ORA-06550: line 5, column 1:
ORA-00001: unique constraint
(SYSMAN.PARAMETERS_PRIMARY_KEY) violated
ORA-06512: at "SYSMAN.MGMT_TIME_SYNC", line 108
Oracle_Server.log:ORA-06512: at "SYSMAN.MGMT_TIME_SYNC", line 166
Oracle_Server.log:ORA-06512: at line 2 

Workaround:

These errors do not result in any data loss. Therefore, you can ignore these errors.

This issue is tracked with Oracle bug 6705429.

14.9 Incorrect Database Version is Displayed on the Oracle Enterprise Manager Database Control Page After Downgrading

If you downgrade the database from Oracle Database 10g Release 2 (10.2.0.4) to an earlier version, Oracle Enterprise Manager Database Control may not restart after the downgrade. However, the emctl start dbconsole command may appear to have started the database console, but you cannot access the database console pages. The emctl status dbconsole command displays that the database console in fact has not started.

Workaround:

This issue is most likely a result Oracle bug 4505434, which has been fixed in this release but exists in earlier releases. To address this issue, apply the patch for bug 4505434 for the database console version you downgraded to and restart the database console.

This issues is tracked with Oracle bug 6649954.

14.10 Errors Displayed After Upgrading Database

After you have finished upgrading the database following the procedures mentioned in the "Upgrading Oracle Database 10g Release 10.2.0.x to Oracle Database 10g Release 10.2.0.4" section, any of the following errors may be logged in the emconfig.log file:

Error moving file
Access is denied

Workaround:

These errors are generated if you did not restart nodes after applying the patch set. If any of these errors exist in the emconfig.log file, restart all the nodes and run the upgrade steps again.

This issue is tracked with Oracle bug 6683192.

14.11 Benign Entry in the Silent Log File After Cloning the Database

An entry similar to the following is logged in the silent log file immediately after you clone the database:

File not found: $ Cloned_Oracle_home/ccr/new_ccr/ccr/bin/setupCCR

Workaround:

This entry in the log file is not a error and can be ignored.This issue is tracked with Oracle bug 6721838.

14.12 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

This issue is tracked with Oracle bug 6754695.

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

14.14 Incorrect Oracle Workspace Manager Displayed After Upgrading to Oracle Database 11g

After upgrading Oracle Database 10g Release 2 (10.2.0.4) to Oracle Database 11g Release 1 (11.1.0.6), the Oracle Workspace Manager version is displayed as 10.2.0.4.3.

This issue is tracked with Oracle bug 6732811.

14.15 ASM Error is Displayed When Creating 10g Release 2 (10.2.0.1) Database on Oracle Clusterware (10.2.0.4)

If you are installing and creating an Oracle Database 10g Release 2 (10.2.0.1) database, which uses ASM storage, after upgrading Oracle Clusterware to version 10.2.0.4, then the following error may be displayed:

An error occurred while executing ASM queries.

Workaround:

This error is benign. Click Continue to proceed with the installation. There is no loss of functionality due to this error.

This issue is tracked with Oracle bug 6791427.

14.16 SETUPCCR Fails if Preset JAVA_HOME Points to an Invalid JDK Home

When CCR is manually configured using setupCCR from a terminal on which JAVA_HOME is pre-defined and if it points to an invalid location or JRE_HOME instead of a valid JDK_HOME, the command fails.

Workaround:

Unset JAVA_HOME and re-invoke setupCCR.

14.17 OracleMTSRecoveryService Remains In Operation After Database Uninstall

This issue is tracked with Oracle Bug 6759063.

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

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

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

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

This issue is tracked in bug 6863977.

14.20 Error Configuring Oracle Configuration Manage

When installing and configuring Oracle Configuration Manager, an error indicating that the JAVA version could not be identified is returned. In such a case, one of two conditions apply:

• JAVA_HOME is defined and the following command returns the JDK version

   %JAVA_HOME%\bin\java -version
  

• the current directory is the install root and the following command returns the JDK version

   jdk\bin\java -version
  

The condition occurs if the TMP environmental variable contains a directory specification containing a space and the Windows Registry key HKLM/SYSTEM/CurrentControlSet/Control/FileSystem/NtfsDisable8dot3NameCreation is set to 1.

Workaround: Set the registry key to 0 and the TMP environmental variable for the user to a value that does not contain a space.