| Oracle® Collaboration Suite Upgrade Guide 10g Release 1 (10.1.2.2) for Microsoft Windows Part Number B31282-03 |
|
|
View PDF |
| Oracle® Collaboration Suite Upgrade Guide 10g Release 1 (10.1.2.2) for Microsoft Windows Part Number B31282-03 |
|
|
View PDF |
This chapter guides the reader through the steps for upgrading Oracle Collaboration Suite information storage databases. You can use the procedures here to upgrade your Oracle Collaboration Suite information storage databases. The chapter contains information about the following topics:
Upgrading the Oracle Collaboration Suite Information Storage Database
Enabling an Existing Customer Oracle Database 10g to be an Oracle Collaboration Suite Database
Completing the Upgrade to Oracle Collaboration Suite 10g Database
Verifying the Upgrade to Oracle Collaboration Suite 10g Database
Additional Information About Selecting Install and Upgrade Options
This section contains the following topics:
Oracle strongly recommends that you back up your database before the upgrade. If errors occur during the upgrade, then you may need to restore the database from the backup.
|
See Also: Oracle Database Backup and Recovery Basics |
Before upgrading from Release 1 (9.0.3.1) or Release 2 (9.0.4.1) to Oracle Collaboration Suite 10g (10.1.2), you must first register the database with Oracle Internet Directory. Failure to do so will result in an error when you run the installer.
Determine whether the text index is empty by logging in to the information storage database as the es_mail user and running the following query:
select count(1) from es_imt_msgbody;
If the result is greater than 0, then the index is not empty. After the Oracle Collaboration Suite information storage database upgrade, perform the steps in Section 5.4.4.
To upgrade an Oracle Collaboration Suite information storage database, install Oracle Collaboration Suite Database 10g (10.1.2) in a new Oracle home and then run the Database Upgrade Assistant to perform the upgrade. The steps to upgrade are described in the following sections:
To install Oracle Collaboration Suite 10g Database:
Make sure that the database you are upgrading is running.
Shut down all Oracle Collaboration Suite middle tier applications that use this database. For more information, see Section 7.3.2.
Verify that the Oracle Internet Directory server is up and running. For more information, see Section 7.1.3.
Log on to the computer on which the Oracle Collaboration Suite information storage database is installed, as the same operating system user that performed the installation. This user must be part of the DBA operating system group.
Set or unset any environment variables according to Section 2.7, "Environment Variables" in Oracle Collaboration Suite Installation Guide for Microsoft Windows.
Mount the installation DVD and start the installer.
|
Note: Refer to Chapter 3, "Starting the Oracle Collaboration Suite Installation" of Oracle Collaboration Suite Installation Guide for Microsoft Windows. |
Run the Oracle Universal Installer and refer to Table 5-1 for information on the options you should select on each screen.
When installation is complete, Oracle Universal Installer starts one or more assistants.
After the End of Installation screen appears, exit the Oracle Universal Installer.
Table 5-1 Summary of the Oracle Universal Installer Screens During the Oracle Collaboration Suite Database Upgrade
| Screen | Description and Recommended Options to Select |
|---|---|
|
Welcome |
Welcomes you to Oracle Universal Installer and the Oracle Collaboration Suite 10g Release 1 (10.1.2) installation procedure. Click Advanced Installation. |
|
Specify File Locations |
Enter a name and path for the new Oracle home. This new Oracle home will be the destination Oracle home for your Oracle Collaboration Suite Database upgrade. |
|
Select a Product to Install |
Select Oracle Collaboration Suite Infrastructure 10.1.2. |
|
Select Collaboration Suite Database. |
|
|
Prerequisite Checks |
This screen displays the results of checking that the system meets the minimum requirements for installing and configuring the product. If the screen displays any warnings or failure, manually correct the problem and click Retry. Depending on the problem, you may need to exit the Oracle Universal Installer, fix the problem and start Oracle Universal Installer again. If you need to modify the kernel parameters on Solaris, for example, you may need to exit, change the parameters, and restart the system. |
|
Language Selection |
If multiple languages are used in the Oracle Collaboration Suite information storage database you are upgrading, then select those languages. If you are not sure which languages were installed, but want languages other than English, click the double arrow button (>>) to select all languages. |
|
This screen appears when Oracle Universal Installer detects an existing Oracle Collaboration Suite installation of the same type as the one you selected on the Select Installation Type screen. Select Upgrade an Existing Oracle Collaboration Suite Database, and then select the Oracle SID and Oracle home of the database you want to upgrade from the table. |
|
|
Enter the name of the host and the port of the Oracle Internet Directory instance where the database you are upgrading is registered. Select Use Only SSL Connections with this Oracle Internet Directory if the Oracle Internet Directory server instance is running with SSL enabled. |
|
|
Enter the user name and password to connect to Oracle Internet Directory at the host name and port where the database is registered. You must either be the Oracle Internet Directory super user or a OracleAS Single Sign-On user with appropriate install privileges. The default Oracle Internet Directory super user name is |
|
|
Enter the database administrator user name, password, port and service name of the database being upgraded. The service name is the global name of the form |
|
|
Database Listener Warning |
This dialog warns you that the Oracle9iAS Metadata Repository database listener is running. Review the instructions on screen for whether you need to stop the database listener. Make sure you stop the listener if required or you will encounter problems later in the upgrade.For more information, see Section 7.1.2. |
|
Privileged Operating System Groups |
This screen appears if you are not a member of the DBA group. In the Database Administrator ( |
|
Enter the existing passwords for the users for Oracle Collaboration Suite Applications schema accounts. Select the option to use the same password for all accounts only if you are currently using the same password for all accounts. |
|
|
Summary |
Use this screen to confirm the choices you have made. Click Install to begin upgrading to the new Oracle Collaboration Suite 10g Database Oracle home. |
|
Install |
This screen displays the status of the installation process. When the installation completes the Oracle Universal Installer automatically starts the Network Configuration Assistant and Database Upgrade Assistant. The screens that appear in these assistants are explained in Section 5.2.2. |
|
Configuration Assistants |
This screen displays the status of each component's configuration assistant. If any component fails, check the error log, correct the problem and click Retry. |
|
End of Installation |
When the installation and upgrade are complete, this screen provides important details about the Oracle Collaboration Suite Database 10g (10.1.2) home, such as the location of the setupinfo.txt file. After you review the information on this screen, exit Oracle Universal Installer and proceed to the postupgrade tasks. |
When the installation completes the Oracle Universal Installer automatically starts the Network Configuration Assistant and Database Upgrade Assistant.
This section describes the Network Configuration and Database Upgrade Assistant screens. Refer to Table 5-2 for information on the options you should select on each screen.
Table 5-2 Summary of the Database Upgrade Screens During the Oracle Collaboration Suite Database Upgrade
| Screens | Description and Recommended Options to Select |
|---|---|
|
The Network Configuration screen has two tabs: The Listeners tab is displayed if you have more than one listener in the 10g Release 1 (10.1.2) Oracle home. Select the listeners in the 10g Release 1 (10.1.2) Oracle home for which you would like to register the upgraded database. The Directory Service tab shows up if you have directory services configured in the release 10g (10.1.2) Oracle home. You can select to either register or not register the upgraded database with the directory service. |
|
|
Available Databases |
In the Available Databases table, select the database that you are upgrading. You can only select one database at a time. Make sure that the database is running. |
|
Specify the attributes for the See Oracle Database Administrator's Guide for more information. |
|
|
Select Recompile Invalid Objects if you want the Database Upgrade Assistant to recompile all invalid PL/SQL modules after the upgrade is complete. Selecting this option improves the performance of the upgraded database but increases the amount of time required to perform the upgrade. See Section 5.6.2.1 for more information. |
|
|
Specify whether or not you want the Database Upgrade Assistant to back up your database for you. If you choose not to use the Database Upgrade Assistant for your backup, then Oracle assumes you have already backed up your database using your own backup procedures. See Section 5.6.2.2 for more information. |
|
|
Optionally, set up your database so it can be managed with Enterprise Manager. Enterprise Manager provides Web-based management tools for managing individual database instances, as well as central management tools for managing your entire Oracle environment. See Section 5.6.2.3 for more information. |
|
|
Secure your database with passwords for the Enterprise Manager accounts. You can set a single password, which will be applied to each of the listed Enterprise Manager user accounts, or enhance the security of the accounts by providing unique passwords for each user. |
|
|
Specify a flash recovery area and enable archiving. When you are managing your database, it is important to configure the database so you can recover your data in the event of a system failure.The Flash Recovery Area can be used to recover data that would otherwise be lost during a system failure; this location is also used by Enterprise Manager if you have enabled local management and daily backups on the Management Options screen shown previously in the Database Upgrade Assistant. |
|
|
Summary |
Use this screen to confirm the choices you've made. Click Finish to begin upgrading the database. The Progress screen displays the status of the components being upgraded. |
|
Upgrade Results |
Displays the results of the upgrade. Optionally configure database passwords by clicking Configure Database Passwords. You can restore the database to its newly installed state by clicking Restore. |
The steps in this section are required for the Oracle Collaboration Suite Schema Creation Configuration Assistant to succeed.
When the Database Upgrade Assistant finishes and subsequently displays the Result screen, perform the following steps:
Open a command window and connect to the upgraded Oracle Collaboration Suite 10g Database as SYS:
%ORACLE_HOME%\bin\sqlplus sys/sys_password
Execute the following commands where ORACLE_HOME is the destination Oracle home of the Oracle Collaboration Suite 10g Database:
shutdown immediate; startup upgrade;
@ORACLE_HOME\ctx\admin\ctxpatch.sql;
shutdown immediate; startup;
Click Done.
When the database upgrade completes, verify that your database initialization parameters in the Oracle Collaboration Suite 10g Database are set to at least the minimum required values. The upgrade preserves the existing values from the database being upgraded. However, the minimum required values for Oracle Collaboration Suite 10g Database may be more than the existing values.
Refer to Table 5-3 and increase the value of the parameter if necessary.
Table 5-3 Database Initialization Parameter Values
| Parameter | Minimum Required Value |
|---|---|
|
|
250 |
|
|
400 |
|
|
629145600 |
|
|
629145600 |
|
|
184549376 |
|
|
150994944 |
|
|
400 |
|
|
10 |
|
|
203423744 |
|
|
1 |
|
See Also: "Using SQL*Plus to Start Up an Oracle Collaboration Suite Database" in Chapter 6 of Oracle Collaboration Suite Administrator's Guide.Oracle Database Administrator's Guide and Oracle Database Reference contain descriptions of initialization parameters and instructions on modifying them. |
If you previously upgraded your Oracle Collaboration Suite information storage database from Oracle9i Database Serverto Oracle Database 10g, you can use the Oracle Universal Installer to enable the Oracle Database 10g to be an Oracle Collaboration Suite Database.
The procedure for enabling an Oracle Database 10g to be an Oracle Collaboration Suite 10g Database is different than the procedure for upgrading an Oracle Collaboration Suite information storage database described in Section 5.2. If you upgraded the Oracle Collaboration Suite information storage database to Oracle Database 10g, you installed a Oracle Database 10g in a new Oracle home. The Oracle Universal Installer does not recognize this Oracle home as containing an Oracle Collaboration Suite component. It does recognize it as a customer Oracle Database. When you select the "Enable" option, the Oracle Universal Installer modifies the database in-place, upgrading the existing Oracle Collaboration Suite schemas to 10g Release 1 (10.1.2) and updating the inventory to identify this Oracle home as an Oracle Collaboration Suite 10g Database.
|
Note: You must use the Database Configuration Assistant to enable Ultra Search before configuring Ultra Search. |
To use the Oracle Universal Installer to enable a customer database to be a Oracle Collaboration Suite Database, your Oracle Collaboration Suite environment should be upgraded to the following configuration:
Upgrade the original Oracle Collaboration Suite information storage database (an Oracle9i Database Server) to Oracle Database 10g using the Oracle Database 10g installer and upgrade assistant. This upgrade process installs a Oracle Database 10g Release 1 (10.1.0.2) in a new Oracle home.
|
See Also: Oracle Database Upgrade Guide for Oracle Database 10g Release 1 (10.1) |
Apply the 10.1. 0.5 patchset to the Oracle Database 10g Release 1 (10.1.0.2). It is located on the Supplemental DVD under Patches\RDBMS\10.1.0.5. Oracle recommends that you apply the 10.1.0.5 patchset (instead of 10.1. 0.5) when it becomes available.
Back up the database. Since the existing database is modified in-place, the existing files are overwritten. If something goes wrong during the enabling process, you may need to restore the database from your backup.
Set the database initialization parameters summarized in Table 5-4 to at least the minimum value required.
Table 5-4 Database Initialization Parameter Values
| Parameter | Minimum Required Value |
|---|---|
|
|
250 |
|
|
400 |
|
|
629145600 |
|
|
629145600 |
|
|
184549376 |
|
|
150994944 |
|
|
400 |
|
|
10 |
|
|
203423744 |
|
|
1 |
|
See Also: "Using SQL*Plus to Start Up an Oracle Collaboration Suite Database" in Chapter 6 of Oracle Collaboration Suite Administrator's Guide.Oracle Database Administrator's Guide and Oracle Database Reference contain descriptions of initialization parameters and instructions on modifying them. |
Perform this step if the current release of your Oracle Database 10g is:
earlier than Release 10.1.0.4
higher than 10.1.0.4 but you ran your Oracle Database Upgrade Assistant (DBUA) when your database version was still less than 10.1.0.4.
Before you enable the Oracle Database 10g, configure Oracle Ultra Search by running the wk0config.sql script.
|
Note: If you are running a Single Instance configuration of 10.1.0.4 or higher, or you ran DBUA from 10.1.0.4 or higher, you are not required to do the wk0config.sql workaround. If you are running a RAC configuration with 10.1.0.4 or higher, or ran DBUA from 10.1.0.4 or higher, you must still perform the steps outlined in Section 5.2, "Upgrading the Oracle Collaboration Suite Information Storage Database". |
Set the ORACLE_HOME environment variable to the Oracle Database 10g Oracle home.
Set the ORACLE_SID environment variable to the SID of the Oracle Database 10g.
Log into the database using the following command:
%ORACLE_HOME%\bin\sqlplus "sys/sys_password as sysdba"
Unlock the wksys account, if it is locked.
At the SQL*Plus prompt, enter the following command:
wk0config.sql welcome jdbc_connection_string launch_anywhere ""
where:
welcome can be replaced by any non-empty string
jdbc_connection_string is the JDBC connection string. See the examples in this section for the format to use.
launch_anywhere is TRUE or FALSE depending on whether the Oracle Ultra Search crawler can be launched from any node. Set the value to TRUE only if the database is a Real Application Clusters (RAC) database on a cluster file system (CFS).
For example, if the database is not a RAC database, the value of jdbc_connection_string has the format hostname:port:sid and launch_anywhere is set to FALSE:
@?\ultrasearch\admin\wk0config.sql welcome mysystem.oracle.com:1521:store false ""
If the database is a RAC database the value of jdbc_connection_string has the TNS keyword-value format to allow connection to any node of the system:
@?\ultrasearch\admin\wk0config.sql welcome "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=cls02a)(PORT=3001))(CONNECT_DATA=(SERVICE_NAME=sales.us.acme.com)))" FALSE ""
If the database is a RAC database using a Cluster File System, then the following steps are required due to a 240-character limitation on the length of the jdbc_connection_string:
At the SQL*Plus prompt, enter the wk0config.sql command as sysdba, specifying only one node from the cluster in the jdbc_connection_string's address list and setting the launch_anywhere flag to TRUE:
@?/ultrasearch/admin/wk0config.sql welcome "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=cls02a)(PORT=3001))(CONNECT_DATA=(SERVICE_NAME=sales.us.acme.com)))" TRUE ""
Modify the value of jdbc_connection_string to include all the nodes of the cluster in the jdbc_connection_string's address list by running the following commands from the SQL*Plus prompt as sysdba:
alter session set current_schema=wksys; update wk$crawler_config_default set ccd_pvalue = 'full_jdbc_connect_string' where ccd_pname = 'CC_DATABASE'; commit; exec wk_adm.use_instance('wk_inst') update wk$crawler_config set cc_pvalue = 'full_jdbc_connect_string' where cc_pname = 'CC_DATABASE'; commit;
where full_jdbc_connection_string is the JDBC connection string which includes the addresses of all the nodes. For example:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=cls02a)(PORT= 1521))(ADDRESS=(PROTOCOL=TCP)(HOST=cls02b)(PORT=1521))(LOAD_BALANCE=yes)) (CONNECT_DATA=(SERVICE_NAME = sales.us.acme.com)))
|
See Also: "Ultra Search on Real Application Clusters" in Chapter 9 of Oracle Ultra Search User's Guide for more information about using the JDBC connection string. |
To enable a customer database to be an Oracle Collaboration Suite Database:
Make sure that the database you are upgrading is running.
Shut down all Oracle Collaboration Suite middle tier applications that use this database. For more information, see Section 7.3.2.
Verify that the Oracle Internet Directory server is up and running. For more information, see Section 7.1.3.
Log on to the computer on which the Oracle Collaboration Suite information storage database is installed, as the same operating system user that performed the installation. This user must be part of the DBA operating system group.
Set or unset any environment variables according to the Section 2.7, "Environment Variables," in Oracle Collaboration Suite Installation Guide for Microsoft Windows.
Mount the installation DVD and start the installer.
|
Note: Refer to Chapter 3, "Starting the Oracle Collaboration Suite Installation" of Oracle Collaboration Suite Installation Guide for Microsoft Windows. |
Run the Oracle Universal Installer and refer to Table 5-5 for information on the options you should select on each screen.
After the End of Installation screen appears, exit the Oracle Universal Installer.
Table 5-5 Summary of the Database Upgrade Screens During the Oracle Collaboration Suite Database Upgrade
| Screen | Description and Recommended Options to Select |
|---|---|
|
Welcome |
Welcomes you to Oracle Universal Installer and the Oracle Collaboration Suite 10g Release 1 (10.1.2) installation procedure. Select Advanced Installation. |
|
Specify File Locations |
In the Destination name and path, enter the existing Oracle Database 10g Oracle home. The database in the Oracle home will be enabled as a Oracle Collaboration Suite Database. |
|
Select a Product to Install |
Select Oracle Collaboration Suite Infrastructure 10.1.2 If multiple languages are used in the database, then click Product Languages. |
|
Select Installation Type |
Select Enable existing Oracle Database 10g to Collaboration Suite Database. |
|
Prerequisite Checks |
This screen displays the results of checking that the system meets the minimum requirements for installing and configuring the product. If the screen displays any warnings or failure, manually correct the problem and click Retry. Depending on the problem, you may need to exit the Oracle Universal Installer, fix the problem and start Oracle Universal Installer again. If you need to modify the kernel parameters on Solaris, for example, you may need exit, change the parameters, and restart the system. |
|
Language Selection |
If multiple languages are used in the Oracle Collaboration Suite Database you are upgrading, then select those languages. If you are not sure which languages were installed, but want languages other than English, click the double arrow button (>>) to select all languages. |
|
Specify Oracle Internet Directory |
Enter the name of the host and the port of the Oracle Internet Directory instance where the database you are upgrading is registered. Select Use Only SSL Connections with this Oracle Internet Directory if the Oracle Internet Directory server instance is running with SSL enabled and is not running any non-secure connections. |
|
Oracle Internet Directory |
Enter the user name and password to connect to Oracle Internet Directory at the host name and port where the database is registered. You must either be the Oracle Internet Directory super user or a OracleAS Single Sign-On user with appropriate install privileges. The default Oracle Internet Directory super user name is |
|
Specify Database Identification |
This screen requests information about the exiting Oracle Database 10g that you want to enable as an Oracle Collaboration Suite Database. Enter the name and password of a database administrator such as |
|
Configuration Requirements Error Dialog |
This dialog appears if the database parameters are not set as required in Section 5.3.1.1. Click OK and set the parameters. |
|
Specify Database File Storage Option |
Select one of the following options for storing your database files:
|
|
Specify Raw Device Mapping File |
This screen appears if you select the Raw Device storage option. Enter the location that contains the mappings for the tablespaces to a raw device. |
|
Select ASM Diskgroup |
This screen appears if you select the Automatic Storage Mechanism storage option. Select an ASM diskgroup from the list. |
|
Database File Location |
Enter the path of the directory where you want to install the database files. Oracle recommends that you install database files on a different disk than the software. |
|
Specify Database Schema Passwords |
Enter the passwords for the users for Oracle Collaboration Suite Applications schema accounts. Oracle recommends creating distinct passwords for enhanced security, but you can opt to use the same password for all accounts. |
|
Summary |
Use this screen to confirm the choices you have made. Click Install to begin enabling the existing database to a Oracle Collaboration Suite Database. |
|
Install |
This screen displays the status of the installation process. |
|
Configuration Assistants |
This screen displays the status of each component's configuration assistant. If any component fails, check the error log, correct the problem and click Retry. |
This section identifies tasks which should be performed after the Database Upgrade Assistant completes. These tasks are:
By default, after you upgrade your database, the datafiles, control files, and log files associated with the database remain in their original location. Oracle recommends that you relocate these files as a safeguard against inadvertently deleting them (for example, by deleting or decommissioning the entire source Oracle home directory tree). In addition, there may be performance benefits to moving the database files outside of the source Oracle home.
|
See Also: "Renaming and Relocating OracleAS Metadata Repository Datafiles in Chapter 6 in Oracle Collaboration Suite Administrator's Guide. |
|
See Also: "Creating Additional Copies, Renaming, and Relocating Control Files" in the Oracle Database Administrator's Guide. |
This task is optional.
In Oracle Collaboration Suite, Oracle Ultra Search is used to index Web content. In 10g Release 1 (10.1.2), the Oracle Ultra Search configuration data and index are stored in the Oracle Collaboration Suite Database, not the Oracle9iAS Metadata Repository database as in previous releases. To preserve the existing configuration and index data, perform the migration steps using the Migration Kit. The configuration and index data must meet the criteria for using transportable tablespace. See Chapter 9 for instructions.If the existing Oracle Ultra Search instance cannot use transportable table space or you choose not to perform the migration, then you can still migrate the configuration data to the Oracle Collaboration Suite Database during the middle tier applications upgrade. However, the index cannot be migrated after the database upgrade and will be rebuilt when the crawling schedule is executed.
Perform the steps in this section if the Oracle Collaboration Suite information storage database you just upgraded is a mail store, a database used by the Oracle Email and Oracle Voicemail & Fax middle tiers.
In 10g Release 1 (10.1.2), the default e-mail administrative user, umadmin, has been deprecated. The Oracle Voicemail & Fax Release 2 (9.0.4.2) middle tiers will not be able to use this username and password to connect to Oracle Internet Directory. To enable the Oracle Voicemail & FaxRelease 2 (9.0.4.2) middle tiers to access Oracle Internet Directory, you need to give the cn=orcladmin user privileges in the mail store.
To give the cn=orcladmin user Oracle Internet Directory privileges:
Log in to the upgraded Oracle Collaboration Suite 10g Database mail store as the es_mail user.
At the SQL*Plus prompt, enter the following command:
begin
UMAdminInfo.set_info ('cn=orcladmin','password', 'ldaphost', ldapport);
end;
where:
password is the password for the Oracle Internet Directory superuser cn=orcladmin
ldaphost is the name of the host where Oracle Internet Directory is running
ldapport is the port where the upgraded Oracle Internet Directory is running
After completing the upgrade of all the Oracle Voicemail & Fax middle tiers, you should restore the 10g Release 1 (10.1.2) user.
Perform the steps in this section if you determined your text index was not empty in Section 5.1.3. When the text index is not empty, the upgrade process does not upgrade the text index as this process could be very time consuming.
To upgrade the text index:
Start SQL*Plus and enter the following command at the prompt:
ORACLE_HOME\bin\sqlplus es_mail/password @ ORACLE_HOME\oes\install\sql\recreate_text_index.sql
where:
ORACLE_HOME is the upgraded Oracle Collaboration Suite 10g Database Oracle home.
password is the password for the es_mail user.
Follow the prompts on the screen. The script prompts you for the primary language and the default character set. When it runs, it displays the following messages:
Setting default character set and recreating the text index...(this may take a while, please wait...)Setting default character set...Creating text index...PL/SQL procedure successfully completed.
To verify that the upgrade was successful:
Set the ORACLE_SID environment variable to the SID name of your Oracle Collaboration Suite Database 10g (10.1.2).
Run SQL*Plus from the Oracle Collaboration Suite 10g Database home and connect as SYSTEM.
Start the Oracle Collaboration Suite middle tier instances and verify that the Oracle Collaboration Suite middle tier applications work correctly. Any exceptions are noted in Section 1.6.
Check for invalid database objects as described in Section 4.6.2.
This section contains additional information about the options in the Oracle Universal Installer and the Database Upgrade Assistant.
This section explains the options that appear on the Upgrade an Existing Collaboration Suite Database screen.
You can select only one database at a time. If you are running the Database Upgrade Assistant from a user account that does not have SYSDBA privileges, then you must enter the user name and password credentials to enable SYSDBA privileges for the selected database.The Database Upgrade Assistant analyzes the database, performing prerequisite checks and displaying warnings as necessary. It checks for any redo log files whose size is less than 4 MB. If such files are found, then the Database Upgrade Assistant gives the option to drop and create new redo log files. It checks the parameter file for any obsolete or deprecated initialization parameters.
This section explains the options that appear on the following screens:
When you upgrade a database to the new Oracle Database 10g release, many of the PL/SQL modules in your database become invalid. By default, the Oracle Database recompiles invalid PL/SQL modules as they are used. The time it takes to recompile the module can result in poor performance as you begin to use your newly upgraded database.
To eliminate these performance issues, select the option to recompile invalid objects at the end of upgrade. When you select this option, the Database Upgrade Assistant recompiles all the invalid PL/SQL modules immediately after the upgrade is performed. This step ensures that you do not experience any performance issues as you begin using your newly upgraded database. The task of recompiling all the invalid PL/SQL modules in your database can take a significant amount of time and increase the time it takes to complete your database upgrade. If you have multiple CPUs, then you can reduce the time it takes to perform this task by taking advantage of parallel processing on your available CPUs. If you have multiple CPUs available, then the Database Upgrade Assistant automatically adds an additional section to the Recompile Invalid Objects screen and automatically determines the number of CPUs you have available.
For example, if you have three CPUs available for processing, then the Database Upgrade Assistant selects 2 from the Degree of Parallelism menu. You can adjust this default value by selecting a new value from the Degree of Parallelism menu.
The Database Upgrade Assistant also provides a recommended degree of parallelism, which determines how many parallel processes are used to recompile your invalid PL/SQL modules. Specifically, the Database Upgrade Assistant sets the degree of parallelism to one less than the number of CPUs you have available.
If you use the Database Upgrade Assistant to back up your database, then the Database Upgrade Assistant makes a copy of all your database files in the directory you specify in the Backup Directory field. The Database Upgrade Assistant performs this cold backup automatically after it shuts down the database and before it begins performing the upgrade procedure. The cold backup does not compress your database files and the backup directory must be a valid file system path. You cannot specify a raw device for the cold backup files.
In addition, the Database Upgrade Assistant creates a batch file in the specified directory. You can use this batch file to restore the database files.On Windows operating systems, the file is called db_name_restore.bat. On UNIX platforms, the file is called db_name_restore.sh
This section describes the options available to manage your upgraded Oracle Collaboration Suite Database. On the Management Options screen, select from the following options depending on your configuration:
The Database Upgrade Assistant checks to see if the Oracle Management Agent has been installed on the host computer. If the assistant locates an Oracle Management Agent, select Grid Control and select an Oracle Management Service from the list. When you finish installing the Oracle Database, the database is automatically available as a managed target within the Oracle Enterprise Manager Grid Control.
Database Control
If you are not centrally managing your Oracle environment, you can still use Enterprise Manager to manage your database. When you install an Oracle Database, you automatically install the Oracle Enterprise Manager Database Control, which provides Web-based features for monitoring and administering the single-instance or cluster database you are installing.
To configure the database so it can be managed with the Oracle Enterprise Manager Database Control, select Database Control.
When you select Database Control, you can configure Enterprise Manager so that e-mail notifications are enabled immediately upon installation.
Select Enable E-mail Notifications if you want the SYSMAN user (the default Super Administrator and owner of the Management Repository schema) to receive e-mail notification when a metric for a specified condition reaches a critical or warning threshold. For example, Enterprise Manager can send an e-mail when a target goes down or when there are database space usage problems.
If you select the Database Control management option, you can also enable automatic daily backups of your entire database.
Select Enable Daily Backups to use the Oracle-suggested backup strategy to back up your entire database with a minimum amount of configuration. Later, you can use Enterprise Manager to customize your backup strategy further.
When you select this option, Enterprise Manager is configured to back up your database, based on the scheduled start time you enter on this page, immediately after you finish installing the Oracle Database. Enterprise Manager backs up the database to the Flash Recovery Area that you specify on the Recovery Configuration screen of the Database Upgrade Assistant.
