Skip Headers
Oracle® Collaboration Suite Installation Guide
10g Release 1 (10.1.2) for Microsoft Windows

Part Number B25463-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

5 Installing Oracle Collaboration Suite 10g Database in an Existing Database

You might have an existing Database that you might want to use for storing Oracle Collaboration Suite data. You can use the Enable existing Oracle10g Database to Collaboration Suite Database option during the installation process to do so. This option seeds the Oracle Collaboration Suite schemas in the specified Database and then registers the Database within Oracle Internet Directory so that the applications can be configured against this Database for a subsequent Applications tier installation.


Note:

Enabling databases is currently not supported for Real Application Clusters with RAW storage type.

This chapter contains the following sections:

5.1 Preparing to Install

To be able to install Oracle Collaboration Suite in an existing database, you must complete the following requirements:

5.2 Installing Oracle Collaboration Suite Database in an Existing Database


Note:

When choosing the Enable existing Oracle10g Database to Collaboration Suite Database option during installation, ensure that Oracle Enterprise Manager has been installed into the ORACLE_HOME of the Database. This is required for the installation to finish successfully.

Also, currently, you cannot enable a custom Database as Oracle Collaboration Suite Database, if the custom Database connection string (the value of orclNetDescString, as registered in Oracle Internet Directory) is longer than 256 characters and the environment variable TNS_ADMIN is not set prior to the installation.


This section contains the following topics:

5.2.1 Applying the 10g Release 1 (10.1.0.5) Patch Set

You need Oracle Database 10g (10.1.0.5) for the Oracle Collaboration Suite installation to be successful. If you have an earlier version of database, for example Oracle Database 10g (10.1.0.2) or Oracle Database 10g (10.1.0.3), then you must apply the Oracle Database 10g Release 1 (10.1.0.5) patch set to this existing Database. To download this patch, refer to the OracleMetaLink site at:

http://metalink.oracle.com

This section contains the following topics:

5.2.1.1 Preinstallation Requirements

The following are the system requirements for this patch set:

  • Hardware Requirement

    • Intel Pentium and AMD processors

  • Operating System requirement

    • Windows Server 2003

    • Windows 2000 ( Service Pack 2 or higher)

    • Windows NT 4.0 (Service Pack 6a or higher)

  • Oracle Database 10g (10.1.0.2) or later

5.2.1.2 Preinstallation Tasks

Complete the following preinstallation tasks before installing the patch set:

5.2.1.2.1 Review Known Preinstallation Issues

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

Adding a Second Node to An Existing Single-Node Oracle Real Application Clusters Installation

If you installed Oracle Real Application Clusters, 10g release 1 (10.1.0.2 or 10.1.0.3) on a single node and created a database during the installation, then the initialization parameter DB_RECOVERY_FILE_DEST might be set incorrectly if you made the following choices:

  • You specified a local directory path for the Oracle home directory.

  • You chose the General Purpose, Data Warehousing, or Transaction Processing database configuration option.

  • You chose not to enable automated backups.

If you made these choices, then the DB_RECOVERY_FILE_DEST parameter incorrectly specifies a directory on the local file system (either %ORACLE_BASE%\flash_recovery_area or %ORACLE_HOME%\flash_recovery_area, depending on your environment settings). Because this directory is not shared, this setting prevents you from adding another node to your Oracle Real Application Clusters installation.


Note:

This problem does not occur if you choose the Custom installation type or choose the Advanced database configuration option during the installation or use the DBCA to create an Oracle Real Application Clusters database after you have installed the software.

  1. If you have a shared file system available, for example an OCFS file system or NFS file system on a certified NAS device, then follow these steps to relocate the flash_recovery_area directory:

    1. Move the flash_recovery_area directory to the shared file system.

    2. Change the value of the DB_RECOVERY_FILE_DEST initialization parameter to specify the new location of the flash_recovery_area directory as follows:

      SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST='new_path';
      
      
  2. If a shared file system is not available, then reset the DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE initialization parameters as follows:

    SQL> ALTER SYSTEM RESET DB_RECOVERY_FILE_DEST;
    SQL> ALTER SYSTEM RESET DB_RECOVERY_FILE_DEST_SIZE;
    
    

This issue is tracked with Oracle bug 3480750.

Upgrading Installations that use Physical or Logical Standby Databases

Before applying this patch set to an Oracle Database 10g release 1 (10.1.0.2 or 10.1.0.3) installation that uses one or more physical or logical standby databases, review the following OracleMetaLink documents:

  • For information about physical standby databases, review document 278641.1.

  • For information about logical standby databases, review document 278643.1.

These documents are available on the OracleMetaLink Web site:

http://metalink.oracle.com

Rolling Upgrades Using Oracle Data Guard SQL Apply

If you use logical standby databases, then you can use Oracle Data Guard SQL Apply to perform rolling upgrades to upgrade Oracle Database 10g release 1 (10.1.0.3) to release 1 (10.1.0.5). During a rolling upgrade, you can run different releases of the Oracle software on the primary and logical standby databases while you upgrade them one at a time. If you do this, then you will incur minimal downtime on the primary database. For information and instructions on rolling upgrades with logical standby databases, review document 300479.1, available on the OracleMetaLink Web site:

http://metalink.oracle.com

Upgrading Preconfigured Standard Edition Databases

If you are using an Oracle Database 10g release 1 (10.1.0.2 or 10.1.0.3) 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 catpatch.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 catpatch.sql script does not apply the patch to them.

Upgrading Oracle Workspace Manager

Oracle Workspace Manager is not upgraded by this patch set installation. If the Oracle Database 10g release 1 (10.1.0.2 or 10.1.0.3) installation includes this component, then upgrade it separately with patches specific to this product.

Upgrading Installations that use Java Virtual Machine or Oracle interMedia

If any database uses Java Virtual Machine or Oracle interMedia, then install the Oracle Database 10g Products installation type from the Oracle Database 10g Companion CD before installing the 10.1.0.5 patch set. To view updated certification information or to download a required patch, refer to the OracleMetaLink site at:

http://metalink.oracle.com

For information about installing the Oracle Database 10g Products installation type from the Companion CD, refer to Oracle Database 10g Companion CD Installation Guide available at

http://metalink.oracle.com

This installation type includes the Natively Compiled Java Libraries (NCOMP) files to improve Java performance. If you do not install the NCOMP files, then the "ORA-29558:JAccelerator (NCOMP) not installed" error occurs when a database that uses Java VM is upgraded to the patch release.

Upgrading Oracle Cluster Ready Services

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

5.2.1.2.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. Use Oracle Universal installer to identify Oracle home directories. From the Welcome screen, click Installed products, and then click the Environment tab.

If you are installing this patch set on an existing Oracle Real Applications Cluster 10g release 10.1.0.2, 10.1.0.3 or 10.1.0.4 installation, then you must run Oracle Universal Installer from the same node from which the Oracle Database software was installed.

5.2.1.2.3 Shut Down Oracle Databases

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

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


Note:

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

5.2.1.2.4 Stop All Services

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


Note:

If you shut down ASM instances, then you must first shut down all database instances that use ASM, even if these databases run from different Oracle homes.

  • If you are upgrading a single instance installation, then shut down the following Oracle Database 10g services before installing the patch set:


    Note:

    You must perform these steps in the order listed.

    1. Shut down any processes in the Oracle home that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus.


      Note:

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

    2. Shut down all database instances.

    3. Shut down the ASM instance, if the ASM instance is running in the Oracle home to be patched.

    4. Shut down all listeners.

    5. Shut down Oracle Cluster Synchronization Service using the Services Control manager.

  • If you are upgrading a CRS installation, then shut down the following Oracle Database 10g 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, then you can upgrade the CRS installation one node at a time. To do this, perform the following steps only on the first node that you are upgrading, and then follow the instructions on the Oracle Universal Installer screen.


    1. Shut down any processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control.


      Note:

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

    2. Shut down all Oracle Real Application Clusters instances on all nodes. To shut down all Oracle Real Application Clusters instances for a database, enter the following command where db_name is the name of the database:

      Drive_Letter:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop database -d db_name
      
      
    3. Shut down all ASM instances on all nodes. Also, shut down the OracleASMService and ASMInstanceName service using the Services Control Panel on all the nodes. To shut down an ASM instance, enter the following command, where node is the name of the node where the ASM instance is running:

      Drive_Letter:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop asm -n node
      
      
    4. Stop all node applications on all nodes. To stop node applications running on a node, enter the following command, where node is the name of the node where the applications are running:

      Drive_Letter:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop nodeapps -n node
      
      
    5. Shut down CRS services using the Services Control Panel on all nodes.


      Note:

      If the CRS installation is not on a shared Oracle home, then you can upgrade the CRS installation one node at a time. To do this, perform the preceding steps only on the first node that you are upgrading, then follow the instructions on the installer screen.

  • If you are upgrading an Real Application Clusters installation and node applications are running in the Real Application Clusters Oracle home, then shut down the following Oracle Database 10g services before installing the patch set:


    Note:

    You must perform these steps in the order listed.

    1. Shut down any services in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control.


      Note:

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

    2. Shut down all Real Application Clusters instances on all nodes. To shut down all Real Application Clusters instances for a database, enter the following command where db_name is the name of the database:

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

      Then shut down the OracleServiceSID service using the Services Control Panel on all nodes.

    3. Shut down all ASM instances on all nodes. Also, shut down the OracleASMService and ASMInstanceName service using the Services Control Panel on all the nodes. To shut down an ASM instance, enter the following command, where node is the name of the node where the ASM instance is running:

      Drive_Letter:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop asm -n node
      
      
    4. Stop all node applications on all nodes. To stop node applications running on a node, enter the following command, where node is the name of the node where the applications are running:

      Drive_Letter:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop nodeapps -n node
      
5.2.1.2.5 Back Up the System

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

5.2.1.3 Installation Tasks

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

Installing the Oracle Database 10g Release 1 (10.1.0.5) Patch Set Interactively

To install the Oracle Database 10g patch set interactively, perform the following steps:


Note:

This patch set should be applied only if required as indicated in the documentation of Oracle Application Server 10.1.2 or Oracle Collaboration Suite 10.1.1. This patch set is not supported for Database-only customers.

  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. Download and extract the Oracle Database 10g Release 1 (10.1.0.5) patch set from

    http://metalink.oracle.com

  3. Double click setup.exe to start Oracle Universal Installer.

  4. On the Welcome screen, click Next.

  5. On the Specify File Locations screen, click Browse next to the Path field in the Source section.

  6. Select the products.xml file from the stage directory where the patch set files reside, and then click Next. For example:

    DISK_LOCATION\stage\products.xml
    
    
  7. In the Name field in the Destination section, select the 10.1.0.x Oracle home that you want to update from the drop-down list, then click Next.

  8. If you are installing the patch set on an Oracle Real Application Clusters cluster, then click Next when the Selected Nodes screen appears.


    Note:

    The Selected Nodes screen lists the existing Oracle Real Application Clusters 10g release 10.1.0.2 nodes. The first node in the list is the node from where the Oracle Real Application Clusters 10g 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, then exit Oracle Universal Installer and install the patch set software from the first node in the list of nodes.

    Alternatively, reset the node order as follows:

    1. Exit Oracle Universal Installer.

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

      DRIVE_LETTER:\setup.exe_location> setup -updateNodeList "CLUSTER_NODES=node2,node1,node3" -local ORACLE_BASE\ORACLE_HOME=oracle_home_path
      

      In this example, the Real Application Clusters 10g release 1 (10.1.x) software was installed from node1, but the patch set will be installed from node2.


  9. On the Summary screen, click Install.

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


  10. Note:

    If you are applying this patch set to a CRS installation:
    • If you shut down all CRS services on all nodes as described in Section 5.2.1.2 before starting the installation, then complete all the steps except the first step in the instructions displayed by the installer screen.

    • If you did not shut down all CRS services on all nodes, then complete all the steps in the instructions displayed by the installer screen.

    The CRS installation instructions displayed by the installer screen are also available in the CRS_HOME\install\readme.txt file.


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


Note:

After installing the Oracle Database 10g Release 1 (10.1.0.5) patch set, you might find that the component status is not reflected correctly in Oracle Enterprise Manager. Although the components have been successfully started, their status might appear as down.

To resolve this issue, you must apply patch set 4633772 after applying the Oracle Database 10g Release 1 (10.1.0.5) patch set. This patch set, 4633772, is available at OracleMetaLink at

http://metalink.oracle.com


Installing the Oracle Database 10g Release 1 (10.1.0.5) Patch Set Noninteractively

To install the Oracle Database 10g patch set noninteractively

  1. Download and extract the Oracle Database 10g Release 1 (10.1.0.5) patch set from

    http://metalink.oracle.com

  2. Copy the response file template provided in the response directory where the patch set files reside.

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


    Note:

    To install the Oracle9i globalization support locale definition files, then set the b_cr9idata variable to True in the response file.

    For Real Application Clusters installations, make sure the CLUSTER_NODES variable specifies all the nodes used in the original Real Application Clusters installation.


  4. Start the Oracle Universal Installer by passing the full path of the response file template you have edited locally as the last argument. For example:

    DRIVE_LETTER:\setup.exe_location> setup -silent -responseFile response_file
    
    

  5. Note:

    If you are applying this patch set to a CRS installation:
    • If you shut down all CRS services on all nodes as described in Section 5.2.1.2 before starting the installation, then complete all the steps except the first step in the CRS_HOME\install\readme.txt file.

    • If you did not shut down all CRS services on all nodes, then complete all the steps in the CRS_HOME\install\readme.txt file.



Note:

After installing the Oracle Database 10g Release 1 (10.1.0.5) patch set, you might find that the component status is not reflected correctly in Oracle Enterprise Manager. Although the components have been successfully started, their status might appear as down.

To resolve this issue, you must apply patch set 4633772 after applying the Oracle Database 10g Release 1 (10.1.0.5) patch set. This patch set, 4633772, is available at OracleMetaLink at

http://metalink.oracle.com


5.2.1.4 Postinstallation Tasks

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

5.2.1.4.1 Upgrading Release 9.2 and Earlier Databases Directly to Oracle Database 10g Release 1 (10.1.0.5)

After you have installed the patch set software, use one of the following methods to upgrade Oracle Databases from a previous release, as described in the 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 the Database Upgrade Assistant to perform the upgrades. If you are upgrading a Real Application Clusters database, then the Database Upgrade Assistant might display the following message:

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

    If this message appears, then run the srvctl command from the database configuration information to the Oracle Cluster Register (OCR). See the Oracle Real Application Clusters Administrator's Guidefor information about using the svrctl command

5.2.1.4.2 Upgrading an Oracle9i Database to Oracle Database 10g

If you upgrade an Oracle9i database to Oracle Database 10g release 1, then Oracle Flashback features using a timestamp may fail. To work around this problem, enter the following SQL script from the Oracle Database 10g database:

SQL> DELETE FROM smon_scn_time WHERE orig_thread <> 0;
SQL> COMMIT;

This issue is tracked with Oracle bug 3994270.

5.2.1.4.3 Upgrading a Release 9.2 Database Not Using OLS

To avoid errors when you are upgrading an Oracle9i Release 2 preconfigured database but are not using Oracle Label Security (OLS), complete the following steps.

  1. Use Oracle Universal Installer release 9.2 to install OLS using the Custom installation type.

  2. Run the ORACLE_BASE\ORACLE_HOME\admin\catnools.sql script from the SQLPlus interface with the SYSDBA privilege to remove OLS components from the database.

5.2.1.4.4 Required Postinstallation Tasks

Review the Check Tablespace Sizes and Set Parameter Values section and complete the steps in the Upgrade the Release 10.1 Database section after you have installed the patch set software.

Check Tablespace Sizes and Set Parameter Values

Review the following sections before upgrading a database.

Check SYSTEM Tablespace Size 

If JServer is part of the installation, then ensure that at least 10 MB of free space is allocated to the SYSTEM tablespace.

Check XDB Tablespace Size 

For Real Application Clusters installations, ensure that at least 50 MB of free space is allocated to the XDB tablespace.

Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters  

Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters, as follows:

  1. Start the database:

    SQL> STARTUP
    
    
  2. If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):

    SQL> SHOW PARAMETER PFILE;
    
    

    This command displays the name and location of the server parameter file or the initialization parameter file.

  3. Determine the current values of these parameters:

    SQL> SHOW PARAMETER SHARED_POOL_SIZE
    SQL> SHOW PARAMETER JAVA_POOL_SIZE
    
    
  4. If the system is using a server parameter file:

    1. If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:

      SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
      
      
    2. If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:

      SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
      
      
  5. If the system uses an initialization parameter file, then, if necessary, change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).

  6. Ensure that the value of the SGA_TARGET initialization parameter size is greater than the sum of the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters.

  7. Shut down the database:

    SQL> SHUTDOWN
    

Upgrade the Release 10.1 Database

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


Note:

If you do not run the catpatch.sql script, as described in this section, and start up a database for normal operation, then "ORA-13516: SWRF Operation failed: CATPROC not valid" errors will occur.

  1. Log in with administrator privileges.

  2. For Real Application Clusters installations, start node applications on each node of the cluster as follows:

    Drive_Letter:\> ORACLE_BASE\ORACLE_HOME\bin\svrctl start nodeapps -n nodename
    
    
  3. If you are using ASM, then start the ASM instance.

  4. For single-instance installations, start the listener, as follows:

    Drive_Letter:\> lsnrctl start
    
    

    Note:

    If you are using the Oracle OLAP option, then make sure that the listener is running.

  5. For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

    Drive_Letter:\> sqlplus /NOLOG
    SQL> CONNECT SYS/password AS SYSDBA
    
    
  6. For Real Application Clusters installations:

    1. Start the database, where db_name is the database name and inst_name is the local instance name:

      Drive_Letter:\> ORACLE_BASE\ORACLE_HOME\bin\svrctl start instance -d db_name -i inst_name
      
      
    2. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

      Drive_Letter:\> sqlplus /NOLOG
      SQL> CONNECT SYS/password AS SYSDBA
      
      
    3. Set the CLUSTER_DATABASE initialization parameter to FALSE:

      SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
      
      
    4. Shut down the database:

      SQL> SHUTDOWN
      
      
  7. 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
    
    
  8. Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script. This list provides the version and status of each SERVER component in the database.

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

  10. Restart the database:

    SQL> SHUTDOWN
    SQL> STARTUP
    
    
  11. Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.

    SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql
    
    

    Note:

    When the 10.1.0.5 patch set is applied to an Oracle Database 10g Standard Edition database, there may be 42 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation.

    Ignore any messages indicating that the database contains invalid recycle bin objects similar to the following:

    BIN$4lzljWIt9gfgMFeM2hVSoA==$0
    

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

    Drive_Letter:\> rman catalog username/password@alias
    RMAN> UPGRADE CATALOG;
    
    
  13. For Real Application Clusters installations:

    1. Set the CLUSTER_DATABASE initialization parameter to TRUE:

      SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
      
      
    2. Restart the database:

      SQL> SHUTDOWN
      SQL> STARTUP
      
      
    3. Start any services that you fwant to use:

      Drive_Letter:\> ORACLE_BASE\ORACLE_HOME\bin\svrctl start service -d db_name -s service_name
      
5.2.1.4.5 Running the configPatch.pl Script on an Oracle Real Application Clusters

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

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


Note:

These instructions do not apply to Real Application Clusters installations where the nodes of the cluster share the same Oracle home.

5.2.1.4.6 Resetting the DBMS_SCHEDULER Time Zone

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

  1. Start SQL*Plus:

    Drive_Letter:\> 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 with Oracle bug 3721687.

5.2.1.4.7 Oracle Enterprise Manager Postinstallation Steps for Database Console

If you upgraded a release 10.1.0.2 or 10.1.0.3 database configured to use Oracle Enterprise Manager Database Console to release 10.1.0.5, then you must perform the following steps:


Note:

On Real Application Clusters, perform the following steps on each node of the cluster.

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

  2. Set the TZ environment variable to your time zone:

    Drive_Letter:\> set TZ=your_time_zone
    
    
  3. Set the ORACLE_SID environment variable:

    Drive_Letter:\> set ORACLE_SID=your_SID
    
    
  4. If you tried unsuccessfully to start the Database Console after you upgraded the database, then enter the following command:

    Drive_Letter:\> ORACLE_BASE\ORACLE_HOME\bin\emctl stop dbconsole
    
    
  5. Enter the following command:

    Drive_Letter:\> ORACLE_BASE\ORACLE_HOME\bin\emctl resetTZ agent
    
    

    This command updates the ORACLE_BASE\ORACLE_HOME\hostname_sid\sysman\config\emd.properties file to match the value of the TZ environment variable. It also returns the command required in Step 7.

  6. Connect to the database as an Enterprise Manager Repository user (SYSMAN):

    Drive_Letter:\> sqlplus "SYSMAN/sysman_password"
    
    

    Note:

    Alternatively, you can connect as the SYS user with SYSDBA privileges, as follows:
    prompt> sqlplus SYS/sys_password AS SYSDBA
    
    

    After you connect as the SYS user, alter the session to run as SYSMAN:

    SQL> ALTER SESSION SET current_schema = SYSMAN;
    
    

  7. Enter the command displayed in Step 5, for example:

    SQL> EXEC MGMT_TARGET.SET_AGENT_TZRGN('host_name.domain_name:1830','PST8PDT')
    SQL> COMMIT
    
    
  8. Exit SQL*Plus.

    SQL> EXIT;
    
    
  9. Start Oracle Enterprise Manager Database Console:

    prompt> emctl start dbconsole
    
    

This issue is tracked with Oracle bug 4132656.

5.2.1.4.8 Automatically Restarting Oracle Notification Service

For Oracle Database 10g release 1 (10.1.0.2) installations, the Oracle Notification Service (ONS) AUTO_START parameter is set to 0 on each node of the cluster. For this reason, CRS does not automatically start ONS when the node is restarted.

To work around this issue, perform the following steps as the CRS owner for each ONS resource:

  1. Change directory to the crs_home\crs\public directory.

  2. Use the following command to create a file containing the profile resources:

    Drive_Letter:\crs_home\crs\public> crs_home\bin\crs_stat -p ora.nodename.ons > ora.nodename.ons.cap
    
    
  3. Enter the following command to change the AUTO_START parameter value to 1 in the ora.nodename.ons.cap file:

    Drive_Letter:\crs_home\crs\public> crs_home\bin\crs_profile -update ora.nodename.ons -o as=1
    
    
  4. Enter the following command to update the resource profile:

    Drive_Letter:\crs_home\crs\public> crs_home\bin\crs_register -u ora.nodename.ons
    

5.2.1.5 Removing the Patch Set Software Update

You cannot remove the patch set software after you have installed it. Oracle recommends that you back up your Oracle Database 10g installation before applying the patch set. If you do not want to use a patch set applied to an Oracle Database installation, do one of the following tasks:

  • Restore the Oracle Database 10g installation that you backed up before applying the patch set.

  • Reinstall Oracle Database 10g.

If you choose not to use a patch set because you are encountering a problem, then contact Oracle Support Services to verify that the problem you are encountering is being addressed.

If you completed postinstallation tasks as described in the Postinstallation Tasks section, then you must do one of the following for each database that you upgraded to the patch set:

  • Use a point-in-time or full database backup and recovery to restore the database to its condition before you performed the postinstallation tasks.

  • Export, rebuild and import the database. If the database is too large, then use Transportable Tablespaces for the export/import process.


See Also:

For more information about using Transportable Tablespaces for the export/import process, see notes 100693.1 and 77523.1 available on the OracleMetalink Web site.

5.2.1.6 Reinstalling the Patch Set Software

If necessary, you can reinstall a patch set that has been applied to an Oracle Database 10g installation. You must reinstall the patch set interactively.

To reinstall the patch set, perform the following tasks:

  1. Ensure that you complete the same set of preinstallation tasks that you performed when you installed the patch set initially:

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

    2. Unzip the downloaded patch set file into a new directory.

    3. Shut down the existing Oracle server instance with normal or immediate priority. For example, shut down all instances cleanly.

    4. Stop all listener, agent, and other processes running in or against the Oracle home in which you are installing.

  2. Start Oracle Universal Installer in the same manner that you did when installing the patch set initially. You may only reinstall a patch set by running Oracle Universal Installer in interactive mode.

  3. Click Next on the Welcome screen. The Specify File Locations appears.

  4. Click Browse for the Source field and navigate to the stage directory where you unpacked the patch set zip file.

  5. Select the products.xml file.

  6. Select the Oracle home that you want to update from the drop-down list.


    Note:

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

  7. If you are installing the patch set on Oracle RAC, then click Next on the Selected Nodes screen.

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

  9. Expand the nodes for each component listed in the tree to display the patch that corresponds to each component.

  10. Select the patches that you want to install. When you select a patch, the Install Status column changes to reinstall.

  11. Repeat the process for each patch bundled in the patch set and click Next.

  12. On the Summary screen, verify the list of patches to be reinstalled and click Install.

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

5.2.1.7 Known Issues

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

Database Creation or Upgrade error Message

While creating a new release 10.1.0.5 database or upgrading an existing database to release 10.1.0.5, you may see the following message:

kwqalqt2: Warning !! queue table SYS.KUPC$DATAPUMP_QUETAB mising

You can ignore this message. This issue is tracked with Oracle bug 4222805.

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, then remove the SQLNET.AUTHENTICATION_SERVICES=(NTS) line from the sqlnet.ora file. If Windows native authentication is required, then 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, and 3781185.

Upgrading Oracle Database Software Version Using Oracle data Guard and SQL Apply

By using a logical standby database, you can upgrade Oracle database software and patch sets with almost no downtime. By using dataguard SQL Apply, you can perform a rolling upgrade of the Oracle database software from patch set release 10.1.0.3 to the 10.1.0.5 patch set release. During a rolling upgrade, you can run different releases of Oracle Database on the primary and logical standby databases, while you upgrade them, one at a time, incurring minimal downtime on the primary database.

For complete information and instructions, see OracleMetaLink note 300479.1.

Cloning of Oracle Home with 10.1.0.5 Patch Set May Display Errors

When an Oracle home with the 10.1.0.5 patch set installed is cloned to another Oracle home on a system that already has a ORA_DBA group configured, or an Oracle user already added to the ORA_DBA group, the following one or more errors would be displayed during the set-up phase of clone installation:

  • Group cannot be added

  • User could not be added shiptest 1378

  • User could not be added 1378

These errors can safely be ignored as long as the ORA_DBA group exists and the Oracle user is already a member of the ORA_DBA group.

You can also execute the following commands by using the executable from the Oracle home bin directory to ensure that the ORA_DBA group is created and Oracle user is added as a member of the ORA_DBA group:

Drive_Letter:\> oradim -ex network groupadd ora_dba
Drive_Letter:\> oradim -ex netowrk useradd ora_dba Oracle_user

This issue is tracked with oracle bug 3453970.

Broker Failover to Logical Standby Database Disables All Other Standby Databases

Beginning with Oracle Database Release 10.1.0.5, there has been a change to the documented behavior after a failover to a logical standby database in an Oracle Data Guard broker configuration.

If a failover was to a logical standby database, then the broker disables all (physical and logical) standby databases in the configuration that were not involved in the failover. They must be re-created before they can serve as standby to the new primary database. In previous releases, only physical standby databases were disabled after a failover to a logical standby database.


Note:

There is no change to failover behavior in the Data Guard configurations that are not managed by the broker.


See Also:

Oracle Data Guard Broker documentation for more information about failover in a Data Guard broker configuration.

5.2.2 Installing Oracle Collaboration Suite


Caution:

To use your existing Oracle 10g Database as an Oracle Collaboration Suite Database, you must run the Metadata Repository Creation Assistant (MRCA) PRIOR to running Oracle Universal Installer and choosing the Enable existing 10g Database to Collaboration Suite Database option.

This section discusses the tasks for installing Oracle Collaboration Suite in an existing Database.

5.2.2.1 Installation Tasks

Perform the steps listed in Table 5-1 to install Oracle Collaboration Suite in an existing database.


Note:

Oracle Universal Installer uses the %WINDIR%\system32\drivers\etc\hosts file to determine the host name. The host name that you specified in the hosts file may or may not be fully qualified. However, host names that are not fully qualified may not be usable outside the domain.

For example, if the fully-qualified domain name for a server is myserver.acme.uk, and the hosts file only registers the name myserver, then clients in the acme.co.uk domain have no trouble communicating with this host. However connections made by users in the acme.co.de domain may fail.

Also, ensure that the host name that you specify corresponds exactly to the host name you have, whether fully qualified or not.



Note:

Before starting the installation, you must ensure that:
  • The database that you plan to use has a fully-qualified database name set.

  • The database parameters, global_name, db_domain, and service_name, are consistent. You must check these parameters manually.


Table 5-1 Screens for Installing Oracle Collaboration Suite in an Existing Database

Step Screen Action
1. None Start the installer.

Refer to Section 3.4 for more information about starting the installer.

2. Select Installation Method Select Advanced Installation.

Note: Refer to Section 1.6.1 for detailed information on Basic and Advanced installations.

Click Next.

3. Specify File Locations

(Advanced installation only)

Enter the full path of the Source directory in the Path field for Source.

Enter a name to identify the Oracle home in the Name field for Destination. The name cannot contain spaces and has a maximum length of 16 characters.Example: OH_INFRA_10_1_2

Enter the full path to the destination directory in the Path field for Destination. This is the Oracle home. If the directory does not exist, the installer creates it. To create the directory beforehand, create it as the oracle user.

Do not create the directory as the root user.Example: Drive_Letter:\oracle\infra_10_1_2

Click Next.

4. Specify Hardware Cluster Installation Mode

(Advanced installation only)

This screen appears only if the computer is part of a hardware cluster.Select the computers in the hardware cluster where you want to install the Infrastructure. You can select multiple computers, or you can just select the current computer.Click Next.
5. Select a Product to Install

(Advanced installation only)

Select Oracle Collaboration Suite Infrastructure 10.1.2.0.0.

Refer to Section 1.7 for more information about how to install support for support for additional languages.

Click Next.

6. Select Installation Type

(Advanced installation only)

The options displayed on this screen depend on what you select in the Select Product to Install screen.The installation types for Infrastructure are:
  • Identity Management and Oracle Collaboration Suite Database

  • Identity Management

  • Oracle Collaboration Suite Database

  • Enable existing Oracle 10g Database to Oracle Collaboration Suite Database

Select Enable existing Oracle 10g Database to Oracle Collaboration Suite Database and click Next.

7. Product-Specific Prerequisite Checks

(Advanced installation only)

The installer verifies requirements such as memory, disk space, and operating system version. If any check fails, make the required changes and click Retry. Refer to Chapter 2 for the list of hardware and software requirements.

Click Next.

8. Language Selection

(Advanced installation only)

This screen enables you to select the language in which Oracle Collaboration Suite components will run.

Select the required language or languages from the Available Languages list and add them to the Selected Languages list.

Click Next.

9. Specify Oracle Internet Directory

(Advanced installation only)

Host: Enter the name of the computer where Oracle Internet Directory is running.

Port: Enter the port number at which Oracle Internet Directory is listening. If you do not know the port number, refer to Section 6.5.

Use SSL to connect to Oracle Internet Directory: Select this option if you want Oracle Collaboration Suite components to use only SSL to connect to Oracle Internet Directory.

Click Next.

10. Oracle Internet Directory

(Advanced installation only)

Username: Enter the user name to use to log in to Oracle Internet Directory.

Password: Enter the user password.

Click Next.

Note: Use cn=orcladmin as the user name if you are the Oracle Internet Directory Superuser.

11. Specify Database Identification

(Advanced installation only)

Username: Enter a database administrator name to log in to the existing database against which you want to install Oracle Collaboration Suite.

Password: Enter the password for the database administrator account you specified in the Username field.

Hostname and Port: Enter the host name of the computer where the database that you want to use is installed. Also, specify the port that this database is using, as follows:

hostname:port

Service Name: Enter the service name for the database you want to use.

SID: Enter the system identifier for the existing database that you want to use. Typically this is the same as the global database name, but without the domain name.

Click Next.

12. Specify Database File Storage Option

(Advanced installation only)

Select the storage mechanism that you would like to use for your database files.

To store the database files on a file system, select File System. For Oracle RAC installations, the file system that you choose must be a cluster file system or be on a certified network attached storage (NAS) device.

To store the database files in an automatic storage management (ASM) disk group, select Automatic Storage Management. ASM disk groups are created by specifying one or more disk devices that will be managed by a separate Oracle ASM instance. For Oracle RAC installations, the disk devices that you add to the ASM disk group must be shared by all nodes of the cluster.

To store the database files on raw devices (raw partitions or raw volumes), select Raw Devices. To select this option, the required raw devices must already exist. For Oracle RAC installations, you must create the raw devices on disk devices that are shared by all nodes of the cluster.

Click Next.

Note: Depending on the option that you select in this screen, the following screen might differ from the one listed in the next step.

13. Specify Database File Location

(Advanced installation only)

Directory for Database Files: Specify the location of the directory where you would like to store the Database files.

Note: For best database performance, Oracle recommends that you install database files (data files, control files, and redo logs) and the database on separate disks.

Click Next.

14. Specify Database Schema Passwords

(Advanced installation only)

Set passwords for privileged database accounts, which are used for database management and postinstallation tasks. Refer to Section 4.3.8 for rules on setting passwords for these accounts.

Set passwords for privileged Oracle Collaboration Suite Application accounts.

The rules for setting the passwords that apply to the SYS and SYSTEM users also apply to these schemas.

Click Next.

15. Summary Verify your selections and click Install.
16. Install Progress This screen displays the progress of the installation.
17. Configuration Assistants This screen shows the progress of the configuration assistants. Configuration assistants configure components.
18. End of Installation Click Exit to quit the installer.


Note:

On some Microsoft Windows operating systems, Oracle Collaboration Suite Databases with large SGA_TARGET and SGA_MAX_SIZE values might crash. Refer to Section K.5 for more information about resolving this problem.


Note:

If no information is displayed when you click Release Information at the end of this installation, then refer to:

http://Infrastructure_host:infra_port_number/relnotes/toc.htm


5.3 Split Configuration


Note:

This section is applicable only if you want to use the Oracle 10g Release 2 ( 10.2 ) Database as Oracle Collaboration Suite Database on platforms where Oracle Collaboration Suite installer is not available. These platforms include Linux Itanium, HP-UX Itanium, and such.

For latest updates and information on platforms that are certified in the Split Configuration scenario, refer to OracleMetaLink at

http://metalink.oracle.com

On OracleMetaLink, Under Certify, select Oracle Collaboration Suite from the list of products. On the Platform Selection page, select Split Configuration DB Tier to display the list of platforms for which this certification is completed.


To install Oracle Collaboration Suite in split configuration, you need Oracle Database 10g release 2 with Companion CD.

This section contains the following topics:

5.3.1 Installing Oracle Collaboration Suite in a Split Configuration

To install Oracle Collaboration Suite as a split configuration:

  1. Install Oracle Collaboration Suite Infrastructure (Oracle Collaboration Suite Database, Oracle Internet Directory, Oracle Delegated Administration Services, Oracle Application Server Single Sign-On) on Host 1.

    Refer to Section 4.5 for more information.

  2. On Host 2, install Oracle Database 10g release 2 with the required Oracle Collaboration Suite parameters.

    For more information on installing Oracle Database 10g release 2, refer to

    http://www.oracle.com/technology/documentation

  3. On Host 2, install all the components from the Oracle Database 10g release 2 Companion CD. In the appropriate screens, ensure that you:

    1. Select the existing Oracle home of Oracle Database 10g release 2 that you installed in the previous step

    2. Select the Oracle Database 10g products 10.2.0.1.0 option.

  4. Run Database Configuration Assistant (DBCA) and select Configure Database Options and then select UltraSearch for configuration.

  5. On Host 2, set the db_create_file_dest parameter on Oracle Database 10g release 2 as follows:

    alter system set db_create_file_dest = '/path/to/oradata' scope=both;
    
    
  6. From the /INFRA HOME\install directory on Host 1, run the following command:

    run OCSdbSchemaReg.bat compulsory_arguments [optional_parameters]
    
    
    

    Refer to Section 4.5.9 for more information on running the OCSdbSchemaReg script.

  7. Check in the /INFRA HOME\install directory of Host 1 for OCSdbSchemaReg.log for any Configuration Assistants failures. All Configuration Assistants should have succeeded.

  8. Use the ftp or rcp comamnd to access the file %ORACLE_HOME%\oes\bin\em_stats.dmp from the Infrastructure host (Host 1) to the Database host (Host 2).

    Run the following command on the Database host:

    %ORACLE_HOME%\bin\imp file=<path_to>em_stats.dmp fromuser=opt_stats \ touser=es_stats tables=GMGIT_ES_MAIL_STATS
    
    

    When prompted for user name and password, enter sys as sysdba and the password for SYS user, respectively.

  9. From Host 1, connect to the 10.2 Database on Host 2 as SYS user and run the following command:

    SQL> @%ORACLE_HOME%\oes\install\sql\apply_stats2.sql
    
    
  10. On Host 3, start the Oracle Collaboration Suite Applications installation.

    In the Select Components to Configure screen, deselect the Oracle Content Services component. Configure Oracle Content Services after the installation is completed. Refer to Section 5.3.2 for details.

    In the Select Database for Components screen, select Oracle 10g release 2 Database that you installed in Step 2 as a back end for all components of the application tier.


    Note:

    You can perform this step on Host 1, if you have sufficient disk space and memory and not necessarily on a seperate system.

5.3.2 Performing Postinstallation Tasks


Note:

The steps provided in this section are only required for Oracle Database 10g Release 2 (10.2). Do not perform this procedure if you are running Oracle Database 10g Release 1 (10.1.0.x)

Perform the following steps to complete the split configuration installation:

  1. Log in to the Database with appropriate privileges and enter the following command:

    drop user owf_mgr cascade;
    
    
  2. From the Oracle Collaboration Suite Applications Oracle home, run the following script:

    %ORACLE_HOME%\wf\install\wfinstall.bat
    
    
  3. When the Oracle Workflow Configuration Assistant starts, enter the following parameters in the following fields:

    • Install Option: Select Server Only.

    • Workflow Account: Use the default value, which is owf_mgr.

    • Workflow Password: Provide the same password as the Oracle Content Services schema password.

    • SYS Password: Provide the password for the database user SYS. You must supply this value.

    • TNS Connect Descriptor: Copy this value from the tnsnames.ora file, which is located in %ORACLE_HOME%\network\admin. For example:

    (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myhost.mydomain.com)(PORT=1521))\
    (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=orcl.mydomain.com)))
    
    

    Note:

    Do not select Enter LDAP Parameters, Enter Mailer Parameters, or Change Tablespace.

  4. Click Submit.

  5. Configure Oracle Content Services using the Oracle Collaboration Suite Control Console.

  6. Apply patch 5096627 on Oracle Collaboration Suite Applications Oracle home on Host 3. This patch is available at OracleMetaLink at:

    http://metalink.oracle.com