1 Installing OracleAS Portal Release 10.1.4

1.2.1.1 Stopping All Middle-Tier Instances

Before you perform the upgrade, you must stop all processes associated with each middle tier that uses the portal schema being upgraded. There are two ways to view all the Oracle Application Server instances that use the portal schema:

• Display the Farm page in the Application Server Control Console.

  
  

  See Also: "Introduction to Administration Tools" in the Oracle Application Server Administrator's Guide for more information about the Application Server Control Console Farm page.

  
  

• Use the following Distributed Configuration Management command in the Oracle home of any middle-tier or Oracle Identity Management instance that belongs to the farm:

  MID_TIER_ORACLE_HOME/dcm/bin/dcmctl listinstances
  
  

To stop all the middle-tier processes, perform the following tasks:

1. Click Stop All on the Application Server Control Console home page for each instance, or use the following Oracle Process Manager and Notification Server (OPMN) command within the Oracle home of each instance:

   MID_TIER_ORACLE_HOME/opmn/bin/opmnctl stopall
   
   

2. Stop the Application Server Control Console by using the following command:

   MID_TIER_ORACLE_HOME/bin/emctl stop iasconsole
   
   

On Windows, also referred to as Windows, you can also stop OPMN and its managed processes and the Application Server Control Console from the Services control panel.

1.2.1.2 Ensuring That Oracle Internet Directory and Database Processes Are Running

Before you perform the upgrade, you must ensure that the following processes are running:

• The OracleAS Metadata Repository database that hosts the portal schema.

• The listener for the OracleAS Metadata Repository database.

• The Oracle Internet Directory instance where the portal schema is registered.

Log in to the Application Server Control Console of the Oracle Identity Management instance to verify that the necessary processes are running and that the required components are configured properly. For example, you can use the Application Server Control Console to verify that the Farm page is displayed correctly and that the Oracle Internet Directory and OracleAS Single Sign-On components are up and running.

When you log in to the Application Server Control Console of the Oracle Identity Management instance, the Application Server home page is displayed. On this page, click Ports to view a list of the ports currently used by the Oracle Application Server instance and to verify that the components are configured properly.

1.2.2.1 Performing the upgrade

After performing the tasks described in Section 1.2.1, "Performing Pre-Upgrade Tasks", you can use the Oracle Application Server Portal Upgrade CD-ROM to upgrade the portal schema in an OracleAS Metadata Repository. To perform an upgrade, you must run the mrua.bat (Windows) or mrua.sh (UNIX) script.

To run the upgrade, perform the following steps:

1. Mount the Oracle Application Server Portal Upgrade CD–ROM.

2. Start the upgrade by using the following command with the required arguments, which are described in Table 1-1:

   CD_ROOT/mrua/<mrua_script>
   -oracle_home <metadata_repository_oracle_home>
   -oid_host <oracle_internet_directory_host>
   -oid_ssl_port <oracle_internet_directory_ssl_port>
   
   

   In this command, <mrua_script> can be mrua.sh or mrua.bat.

   An example for running the upgrade is as follows:

   On UNIX:

   mrua.sh -oracle_home /dua1/oracle10g -oid_host dserv1.acme.com -oid_ssl_port 3130
   
   

   On Windows:

   mrua.bat -oracle_home d:\oracle10g -oid_host dserv1.acme.com -oid_ssl_port 3130
   
   

   Table 1-1 Summary of the Required Upgrade Command-Line Arguments

   Arguments	Description
   -oracle_home	The OracleAS Metadata Repository home directory.
   -oid_host	The name of the computer that hosts the Oracle Internet Directory where the OracleAS Metadata Repository is registered.
   -oid_ssl_port	The secure port for Oracle Internet Directory. For purposes of upgrading the OracleAS Metadata Repository, you must use a secure connection to Oracle Internet Directory.

   
   
   
   

   Note: The values of the -oid_host and -oid_ssl_port arguments must match the values of the corresponding properties defined in the following configuration file in the Oracle Identity Management home directory: IDENTITY_MANAGEMENT_ORACLE_HOME/config/ias.properties The corresponding properties in the ias.properties file are as shown in the following example: OIDhost=dserv1.acme.com OIDsslport=3130

   
   

3. When you are prompted, enter the password for the database SYS user account.

   You must provide the SYS password in order to access and modify the portal schema in the database.

4. When you are prompted, enter the Oracle Internet Directory cn=orcladmin administrator password.

   You must provide the Oracle Internet Directory password in order to connect to the Oracle Internet Directory where the OracleAS Metadata Repository is registered.

   After you provide the required passwords, the upgrade script checks if Oracle Internet Directory is running and does one of the following:

   • If Oracle Internet Directory is down or unavailable, then the upgrade script displays an error message and exits.

   • If Oracle Internet Directory is up and running, then the upgrade script connects to the directory service and obtains additional information required to upgrade the portal schema.

     If multiple instances of the OracleAS Metadata Repository are registered with the directory, then the upgrade script prompts you to select the OracleAS Metadata Repository that you want to upgrade.

   You can upgrade only one OracleAS Metadata Repository at a time.

5. If you are prompted to select an OracleAS Metadata Repository, then select the OracleAS Metadata Repository on the local computer that corresponds to the value of the -oracle_home parameter.

   
   

   Note: The upgrade script first performs the pre-upgrade checks, and then proceeds with the actual upgrade. The upgrade is not immediately terminated if a single precheck fails. Instead, the errors for all prechecks are consolidated in the precheck.log file. This file is generated in the METADATA_REP_ORACLE_HOME/upgrade/temp/portal directory. Look at the end of the log file to see a list of checks that failed. Run the upgrade again until none of the prechecks fail. If the upgrade did not complete because of precheck errors, then the schema is not altered, and therefore, restoring from your backup is not necessary between runs. Look up any errors found in the precheck log file. Refer to Appendix A, "OracleAS Portal Upgrade Error Messages" for information about upgrade errors. Contact Oracle Support Services for any errors that are not documented or that cannot be resolved by following documented actions.

   
   

   The upgrade script starts the upgrade process. As each step in the upgrade is performed, information messages appear on the screen to show the progress of the upgrade.

   Example 1-1 shows an example of a typical upgrade session.

   Example 1-1 Sample Output from an Upgrade Session

   mrua.sh -oracle_home /dua1/oracle10g -oid_host dserv1.acme.com -oid_ssl_port 3130
   Executing mrua.pl
   Running on UNIX
   
   OracleAS Metadata Repository Upgrade Assistant 10.1.4.0.0
   
   Enter the password for SYS:
   Enter the password for cn=orcladmin:
   
   Upgrading the OracleAS Metadata Repository to release 10.1.4
   
   Calling upgrade plugin for MRUA
   Component upgraded successfully  MRUA
   
   Calling upgrade plugin for PORTAL
   Component upgraded successfully  PORTAL
   
   Calling upgrade plugin for MRC
   Component upgraded successfully  MRC
   
   SUCCESS: All OracleAS plug-ins report successful upgrade
   
   Finished mrua.pl
   

   
   

   Note: The MRUA and MRC plugins shown here are the Metadata Repository Upgrade Assistant components and not Oracle Application Server components. During an upgrade to 10.1.4, only the portal component and the required MRUA framework components in Oracle Application Server 10g Release 2 (10.1.2.0.2) are upgraded to 10.1.4.

   
   

1.2.2.2 Reviewing the Upgrade Log File

Once the upgrade is complete, check the upgrade log files for any errors, by performing the following steps:

1. Locate the upgrade log file. The default name for the upgrade log file is upgrade.log and it is located in the following directory:

   METADATA_REP_ORACLE_HOME/upgrade/temp/portal

   Unless the upgrade terminates abruptly before finishing, the errors in the log file are sent to standard output and are also included in a separate section at the end of the log file. Use the line numbers in the section at the end of the log file to search for the errors when they occurred earlier in the file. In addition to the log file, errors are also summarized in a file named upgrade.err, and warnings are summarized in a file named upgrade.wrn. These files are located in the following directory:

   METADATA_REP_ORACLE_HOME/upgrade/temp/portal/tmp

2. Open the upgrade log file with a text editor.

3. Look up the errors and warnings described in the log file.

4. Refer to Appendix A, "OracleAS Portal Upgrade Error Messages" and resolve any errors and warnings for which the workarounds have been documented. Most errors require that you restore the repository from backup, resolve the problem, and run another upgrade.

   
   

   Note: If an error occurred while performing pre-upgrade checks, that is, if an error is logged in the precheck.log file, then it is not necessary to restore the repository from your backup. This is because, while performing the prechecks, the schema is not altered. If an error occurred while performing the upgrade, that is, if an error is logged in the upgrade.log file, then you must restore the repository from backup.

   
   
   
   

   Caution: You cannot run OracleAS Portal until you have completed a successful upgrade. A successful upgrade has zero errors in the upgrade log file, upgrade.log.

   
   

5. Contact Oracle Support Services for any errors that are not documented.

6. Continue this process until all errors are resolved.

The following example shows the end of the log file of a successful upgrade. Notice the Upgrade completed successfully message and the lack of error messages.

### Show errors and warnings 
Step started at Tue Jul 12 04:17:22 2005 
### 
### WARNING: WWU-26002: Upgrade completed with the following warnings:

. . . 

### Upgrade completed successfully 
. . . 
Upgrade Ended at Tue Jul 12 04:17:31 2005

The following examples show the last few lines of the log files of unsuccessful upgrades:

Example 1: Premature termination with the error section:

### ERROR: WWU-01013: Upgrade terminated with the following errors:
###        1278 : EXP-00003: no storage definition found for segment(9, 10251)
###        1368 : ### ERROR: Exception Executing Script upg/common/precln/../../frwk/export.pl :
. . . 
### Upgrade aborted at Thu Jun 30 04:28:18 2005.

Example 2: Standard termination, but with errors found (notice the line numbers preceding each error line):

### 
### Show errors and warnings 
###
Upgrade step started at Fri Jul 1 03:52:56 2005
###
### WARNING: WWU-26002: Upgrade completed with the following warnings:
###			               ...
###
###	 ERROR: WWU-01012: Upgrade completed with the following errors:
###      8503:ERROR at line 1: 
###      8504 : ORA-20000:
###      8505 : ORA-06512: at "UPGR309.WWPOF", line 440
. . .
Upgrade Ended at Fri Jul  1 04:28:08 2005

Table 1-2 describes the location and contents of the different log files.

1.2.2.3 Starting All Middle Tiers

After the upgrade is completed successfully, start each middle tier that is using the upgraded OracleAS Portal instance by performing the following steps:

1. Start OPMN and its managed processes by using the following command:

   MIDDLE_TIER_ORACLE_HOME/opmn/bin/opmnctl startall
   
   

2. Start the Application Server Control Console using the following command:

   MIDDLE_TIER_ORACLE_HOME/bin/emctl start iasconsole
   
   

On Windows, you can also start OPMN and its managed processes and the Application Server Control Console from the Services control panel.

1.2.2.4 Accessing the Upgraded OracleAS Portal

If the upgrade is completed successfully, then you are ready to access the upgraded OracleAS Portal instance.

Open a browser and specify the URL to access OracleAS Portal in the following format:

http://<host>:<port>/portal/pls/portal