Oracle® Database

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

This section includes the following issues:

• Upgrading Oracle E-Business Suite Databases

• Upgrading Installations that use Physical or Logical Standby Databases

• Upgrading Preconfigured Standard Edition Databases

• Upgrading Oracle Workspace Manager and Oracle Messaging Gateway

• Upgrading Installations that use Java Virtual Machine or Oracle interMedia

http://metalink.oracle.com/

http://metalink.oracle.com/

3.2 Identify the Oracle Database Installation

This is not a complete software distribution. You must install it in an existing Oracle Database 10g release 1 (10.1.0.2) Oracle home. Use Oracle Universal Installer to identify Oracle home directories. From the Welcome screen, click Installed Products, then click the Environment tab.

If you are installing this patch set on an existing Oracle Real Applications Cluster (RAC) 10g release 1 (10.1.0.2) installation, you must run Oracle Universal Installer from the same node from which the release 10.1.0.2 software was installed.

3.3 Check Post-Release Updates

Before installing this patch set in a production environment, review document 263719.1, ALERT: Oracle Database 10g Release 1 (10.1) Support Status and Alerts, available on the OracleMetaLink Web at:

http://metalink.oracle.com/

To locate this document:

1. Click Advanced at the top of the OracleMetaLink page.

2. Enter 263719.1 in the Document ID field and click Submit.

This document is created by Oracle Support Services and provides information about the status of issues discovered after this patch was released. If you are unable to access this site, then contact Oracle Support Services before installing this patch set in a production environment.

3.4 Download and Extract the Installation Software

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

3.5 Check Oracle Real Application Clusters Base Release

You can install this patch set on to multiple nodes in an Oracle Real Application Clusters (RAC) cluster if the base release (10.1.0.2) is already installed on those nodes. Oracle Universal Installer detects whether the system where you are installing is part of a cluster. If it is, then Oracle Universal Installer displays the available nodes in the cluster. The local node must be the first node in the list.

3.6 Shut Down Oracle Databases

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

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

3.7 Stop All Services

Stop all listener and other services running in the Oracle home directory where you want to install the patch set.

• If you are upgrading a CRS installation, shut down the following Oracle Database services before installing the patch set:

  
  

  Note: You must perform these steps in the order listed. If the CRS installation is not on a shared Oracle home you can upgrade the CRS installation one node at a time. To do this, perform these steps only on the first node that you are upgrading, then follow the Oracle Universal Installer instructions.

  
  

  1. Shut down all RAC instances on all the nodes.

  2. Shut down all ASM instances on all the nodes.

  3. Stop all node applications on all the nodes.

  4. Shut down CRS instances on all nodes.

• If you are upgrading a RAC installation and node applications are running in the RAC Oracle home, shut down the following Oracle Database services before installing the patch set:

  1. Shut down all RAC instances on all the nodes.

  2. Shut down all ASM instances on all the nodes.

  3. Stop all node applications on all the nodes.

  
  

  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.

  
  

3.8 Back Up the System

Oracle recommends that you create a backup of the Oracle Database installation before you install the patch set. After the patch set is installed there is no way to remove it.

4.1 Installing the Oracle Database Patch Set Interactively

To install the Oracle Database patch set interactively:

There are no patches that need to be applied from the patchset Oracle Database 10g patch set 10.1.0.3.

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

2. Unzip the downloaded patch set file into a new directory. For example, Oracle_patch.

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

   
   

   Note: To install Oracle9i globalization support locale definition files, run Oracle Universal Installer as follows: setup.exe oracle.rsf.nlsrtl_rsf:b_cr9idata=true

   
   

4. On the Welcome screen, click Next. The Specify File Locations screen appears.

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 extracted the patch set zip file, then click Next. For example:

   Oracle_patch/stage/products.xml
   
   

7. In the Name field in the Destination section, select the 10.1 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.

   
   

   Note: The Selected Nodes screen lists the existing RAC release 10.1.0.2 nodes. The first node in the list is the node from where the release 10.1.0.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.

   
   

9. 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 a CRS installation, then follow the steps displayed on the Oracle Universal Installer screen to complete the installation.

   
   

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

4.2 Installing the Oracle Database Patch Set Noninteractively

To install the Oracle Database 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, in the CLUSTER_NODES variable in the response file, make sure that you specify all of the nodes used in the original RAC installation. To install Oracle9i globalization support locale definition files, set the b_cr9idata variable to TRUE.

   
   

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

   setup.exe -silent -responseFile response_file_path
   

5.1 Required Postinstallation Tasks

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

1. For RAC installations, start node applications on each node of the cluster as follows:

   c:\> srvctl start nodeapps -n nodename
   
   

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

   
   

3. If you are using ASM, start the ASM instance.

   For RAC, start the ASM instance on each node using the following command:

   c:\>  srvctl start asm -n nodename
   
   

4. Use SQL*Plus to login to the database instance as the SYS user with SYSDBA privileges:

   sqlplus /NOLOG
   CONNECT SYS/password AS SYSDBA
   
   

5. Start up the database:

   SQL> STARTUP NOMOUNT
   
   

6. 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; 
   
   

7. Set the value of the JAVA_POOL_SIZE initialization parameter to at least 120 MB:

   SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='120M' SCOPE=spfile; 
   
   

8. On RAC installations, set the CLUSTER_DATABASE initialization parameter to FALSE.

   SQL>  ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
   
   

   
   

   Note: After you have completed the postinstallation tasks, reset this initialization parameter to TRUE.

   
   

9. Shut down the database:

   SQL> SHUTDOWN
   
   

10. Enter the following SQL*Plus commands:

    SQL> STARTUP UPGRADE
    SQL> SPOOL patch.log
    SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catpatch.sql
    SQL> SPOOL OFF
    
    

11. Review the patch.log file for errors and inspect the list of components that is displayed at the end of the catpatch.sql script. This list provides the version and status of each SERVER component in the database.

12. If necessary, rerun the catpatch.sql script after correcting any problems.

13. Restart the database:

    SQL> SHUTDOWN
    SQL> STARTUP
    
    

14. Run the ultrp.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> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql
    
    

    
    

    Note: If the 10.1.0.3 patch set is applied to an Oracle Standard Edition or Standard Edition One database, there may be 42 invalid objects after the utlrp.sql scrip runs. These objects are not supported with Standard Edition and do not affect the database operation.

    
    

15. If you are using the Oracle Recovery Manager catalog, enter the following command:

    rman catalog user/passwd@alias 
    RMAN> upgrade catalog; 
    

5.2 Running the configPatch.pl Script on a RAC Cluster

The configPatch.pl script updates the Oracle Enterprise Manager Database Control files. Although Oracle Universal Installer copies the configPatch.pl script to all of the Oracle homes on the cluster, it only runs the script on the node running Oracle Universal Installer.

If you install this patch set on a RAC installation that does not use a shared Oracle home directory, then you must manually run perl.exe ORACLE_BASE\ORACLE_HOME\sysman\install\configPatch.pl on each node of the cluster except the node from which you ran Oracle Universal Installer.

5.3 Upgrading Databases from Previous Releases Directly to Oracle Database 10g Release 1 (10.1.0.3)

After you have installed the patch set software, use one of the following methods to upgrade your prior release Oracle databases as described in Oracle Database Upgrade Guide:

• Run the u0902000.sql, u0900010.sql, u0801070.sql, or u0800060.sql upgrade scripts. These scripts are installed in the patch set ORACLE_BASE\ORACLE_HOME\rdbms\admin directory.

• Use Database Upgrade Assistant to perform the upgrades.

  If you are upgrading a RAC database, then Database Upgrade Assistant many display the following message:

  The database databasename does not have the cluster configuration and
  also not listed in the registry of remote cluster nodes. Do you want the
  Database Upgrade Assistant to continue upgrading it as non cluster
  database?
  
  

  If this message appears, then run the srvctl command from the database Oracle home to add the database configuration information to the Oracle Cluster Register (OCR).

  
  

  See Also: Oracle Real Application Clusters Administration Guide for information about using the srvctl command

  
  

5.4 Resetting the DBMS_SCHEDULER Time Zone

If you created a preconfigured database during the Oracle Database 10g, release 1 (10.1.0.2) installation specify the local time zone as follows:

1. Start SQL*Plus, as follows:

   C:\> sqlplus "/ AS SYSDBA"
   
   

2. If necessary, start the database:

   SQL> STARTUP
   
   

3. Enter the following command:

   SQL> SELECT TZNAME FROM V$TIMEZONE_NAMES;
   
   

   The output from this command lists the different time zone settings for the TZNAME attribute.

4. From the output of the preceding command, identify the time zone for your location.

5. Reset the default_timezone attribute for the scheduler, where timezone is the time zone that you identified in the previous step:

   SQL> BEGIN
   DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('DEFAULT_TIMEZONE','timezone');
   END ; /
   
   

   The default_timezone attribute determines the time zone that the maintenance windows use.

This issue is tracked through Oracle bug 3721687.

9.1 Incorrect Oracle Home References in Enterprise Manager Java Console

Users will encounter this bug on Windows if they install the Enterprise Manager Java Console using the Client Administrator Install option, and then install any other Oracle product in a different Oracle home.

Under these circumstances, the Oracle home shown for the databases in the navigator tree and the list of services shown under "Service Name" will have the Oracle home of the last installed Oracle application, not the Oracle home where the client tools were installed. This will be the case for all database entries added to the tree by choosing Navigator, then Add Databases to Tree, and then Add selected databases from your local tnsnames.ora located in ORACLE_BASE\ORACLE_HOME\network\admin.

To workaround this problem, the user will need to include ORACLE_BASE\ORACLE_HOME\bin in the Windows system path and restart the Java Console. The following commands are examples of how the path can be set from the command prompt:

set ORACLE_HOME=Oracle_home_of_installed_client
set PATH=%ORACLE_HOME%\bin;%PATH%

This issue is tracked through Oracle bug 3697303.

A one-off patch to correct this problem is available on OracleMetalink.

9.2 Using Database Upgrade Assistant to Upgrade a Database

Before selecting Finish on the Summary Page of Database Upgrade Assistant, close all open applications such as Services panel, Registry Editor, and Performance Monitor.

The following error message may display if applications are open when using Database Upgrade Assistant:

Error in Process: ORACLE_BASE\ORACLE_HOME\bin\oradim.exe 
Upgrade failed due to running the step "Upgrading Oracle Server" 

The following error message may display if applications are open when manually upgrading a database:

DIM-00020: A service for this SID is already created. Please enter a
different SID name. No action has been taken O/S-Error: (OS 1072) The
specified service has been marked for deletion. 

To work around this problem, restart the computer, manually re-create the Oracle Database service using the ORADIM utility, then start Database Upgrade Assistant.

This issue is tracked through Oracle bug 3761912.

9.3 Oracle Data Guard May Not Work Properly in a Windows Domain Environment if Windows Native Authentication is Enabled

Problem: Some Oracle Data Guard functionality may not work properly in a Windows domain environment if Windows native authentication is enabled. Symptoms of this problem may include slow or erratic redo transmission between the members of a Data Guard configuration and very slow processing of Oracle Data Guard management operations initiated through SQL statements, the Oracle Data Guard Broker command line interface, or Enterprise Manager.

Solution: If you do not require Windows native authentication, remove the SQLNET.AUTHENTICATION_SERVICES=(NTS) line from the sqlnet.ora file. If Windows native authentication is required, use the Log On tab of the Windows Services control panel to change the user account under which all of the Oracle services run from Local System to a domain user account that is a member of the ORA_DBA group on each of the systems in the Oracle Data Guard configuration.

This issue is tracked through Oracle bugs 3614761, 3620140, 3633927, 3725614, 3781185.

9.4 Oracle Enterprise Manager Database Control

The Management Access Page in Oracle Enterprise Manager Database Control is not translated. This issue is tracked through Oracle bugs 3632869 and 3786887.

9.5 Hangs in Utilities that Access the Oracle Cluster Registry

If the node on which the OCR writer is running shuts down uncleanly, tools using the OCR on other nodes, for example crs_stat, ocrdump, srvctl, might hang. If you encounter this problem, open Task Manager and end both the processes namedcrsd.exe. This issue is tracked through Oracle bug 3626461.

9.6 Unclean Shutdown of One Node Can Cause CRS Service Failure on Another

If a cluster node shuts down uncleanly, the CRS service on another node might fail after getting a communication error. If this problem occurs, the CRS_HOME\srvm\log\ocr_pid_1.log file might have a entry similar to the following:

prom_rpc: CLSC send failure..ret code 2

There is no workaround for this problem. This issue is tracked through Oracle bug 3779593.

9.7 Database Configuration Assistant Does Not Display Welcome Page

If the Oracle home is on CFS and you add another RAC node to the cluster, then Database Configuration Assistant may not display the Welcome page on the newly added node. If you run Oracle Universal Installer from the newly added node, then Oracle Universal Installer may not list the Oracle home in the central inventory.

To fix the problem, perform the following on all nodes:

cd ORACLE_BASE\ORACLE_HOME\oui\bin setup.exe -attachHome
ORACLE_HOME=Oracle_home ORACLE_HOME_NAME=Oracle_home_name
CLUSTER_NODES=comma_separated_list_of_nodes, local_node_first
-noclusterEnabled

This issue is tracked in Oracle bug 3780511.