|
Oracle® Application Server Portal Installation and Upgrade Guide
10g Release 2 (10.1.4) B19135-01 |
|
 Previous |
 Next |
|
Oracle® Application Server Portal Installation and Upgrade Guide
10g Release 2 (10.1.4) B19135-01 |
|
|
Previous |
Next |
This chapter explains the procedure to upgrade OracleAS Portal to release 10.1.4. You can upgrade to OracleAS Portal release 10.1.4 by performing the following steps:
Depending on whether the portal schema was installed in the Oracle Application Server Metadata Repository or in a customer database, you can use either of the following procedures to perform an upgrade:
Section 3.1.1, "Upgrading the Portal Schema in an OracleAS Metadata Repository"
Section 3.1.2, "Upgrading the Portal Schema in a Customer Database"
After performing the tasks described in Section 2.3, "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.
|
Note: You must run the upgrade on the computer that hosts the portal schema that you are about to upgrade. |
To run the upgrade, perform the following steps:
Mount the Oracle Application Server Portal Upgrade CD–ROM.
Start the upgrade by using the following command with the required arguments, which are described in Table 3-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 3-1 Summary of the Required Upgrade Command-Line Arguments
| Arguments | Description |
|---|---|
|
|
The OracleAS Metadata Repository home directory. |
|
|
The name of the computer that hosts the Oracle Internet Directory where the OracleAS Metadata Repository is registered. |
|
|
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:
The corresponding properties in the OIDhost=dserv1.acme.com OIDsslport=3130 |
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.
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.
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 theprecheck.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 3-1 shows an example of a typical upgrade session.
Example 3-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. |
This section details the steps for upgrading a portal schema residing in a customer database configuration outside the OracleAS Metadata Repository.
|
Note: If the OracleAS Portal instance was originally installed in release 3.0.9 or earlier, or if it was installed using theptlasst utility, then the portal schema resides in a customer database configuration outside the OracleAS Metadata Repository and needs to be upgraded using the steps in this section.
|
To upgrade the portal schema residing in a customer database, you must use the upgrade.bat (Windows) or upgrade (UNIX) script. Perform the following steps to upgrade the portal schema residing in a customer database:
Set the ORACLE_HOME environment variable to the Oracle home of the database that contains the portal schema.
Mount the Oracle Application Server Portal Upgrade CD–ROM.
Verify if you can connect to the portal schema in the database Oracle home by specifying the schema password and the Transparent Network Services (TNS) name using SQL*Plus.
For example:
sqlplus portal/portal@orcl
Change the directory to a location where you have write permissions. The upgrade script will create a set of log files and temporary directories in this location.
Stop all Oracle Application Server services in the middle-tier Oracle homes that are associated with the portal schema being upgraded. For the procedure to do this, refer to Section 2.3.2, "Stopping All Middle-Tier Instances".
Verify that the Oracle Internet Directory associated with the portal schema is up and running. For the procedure to do this, refer to Section 2.3.3, "Ensuring That Oracle Internet Directory and Database Processes Are Running".
Run the upgrade script in precheck mode until there are no errors found.
On UNIX, run the script as follows:
CD_ROOT/portal/admin/plsql/upgrade -precheck
On Windows, run the script as follows:
CD_ROOT\portal\admin\plsql\upgrade.bat -precheck
When -precheck is specified, only the pre-upgrade checks are done and the upgrade exits after that. In this mode, the upgrade is not immediately terminated if a 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 in this mode until none of the prechecks fails. In this mode, the schema is not altered, so 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.
After resolving all warnings and errors from the precheck.log file, run the upgrade script without any parameters.
On UNIX, run the script as follows:
CD_ROOT/portal/admin/plsql/upgrade
On Windows, run the script as follows:
CD_ROOT\portal\admin\plsql\upgrade.bat
The script prompts you for information about the system setup. Your answers are echoed for verification at the end of the script. However, if you discover that you have entered incorrect information before the end of the script, then you can exit before any changes are made by answering n to the last script inquiry.
The following are the questions from the script. Default answers to the questions are given in brackets.
Have you backed up your database (y|n)? [y]:
If you have not backed up the database, then answer n, back up the database, and restart the script. If you have backed up the database, then answer y.
Enter the name of the schema you would like to upgrade [portal]:
If the schema name is different from the default OracleAS Infrastructure 10g installation schema name of portal, then enter the schema name.
Enter the password of the schema you would like to upgrade [portal]:
If the password is not the same as the schema name, then enter the portal schema password.
Enter the password for the SYS user of your database [change_on_install]:
If the password is not change_on_install, then enter the database SYS password.
Enter the TNS connect string to connect to the database [orcl]:
Provide the TNS connect string. This can be found in the ORACLE_HOME/network/admin/tnsnames.ora file.
When the script is complete, examine the upgrade log files in the current directory to make sure there are no errors reported at the end.
|
Caution: You cannot run OracleAS Portal until you have completed a successful upgrade. A successful upgrade has zero errors.When undocumented errors are found, do not attempt to run the upgrade again, run any further steps, alter any files, modify the portal schema, or access the OracleAS Portal instance in your browser. Contact Oracle Support Services for help. |
Once the upgrade is complete, check the upgrade log files for any errors, by performing the following steps:
Locate the upgrade log file. The default name for the upgrade log file is upgrade.log and it is located in the following directory:
If you upgraded the portal schema in the OracleAS Metadata Repository, then the log file is generated in the METADATA_REP_ORACLE_HOME/upgrade/temp/portal directory.
If you upgraded the portal schema in a customer database, then the log file is generated in the same directory, <upgrade_directory>, in which you ran the upgrade script.
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:
If you upgraded the portal schema in the OracleAS Metadata Repository, then the error and warning files are generated in the METADATA_REP_ORACLE_HOME/upgrade/temp/portal/tmp directory.
If you upgraded the portal schema in a customer database, then the error and warning files are generated in the <upgrade_directory>/tmp directory.
Open the upgrade log file with a text editor.
Look up the errors and warnings described in the log file.
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 theprecheck.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 |
|
Caution: You cannot run OracleAS Portal until you have completed a successful upgrade. A successful upgrade has zero errors in the upgrade lof file,upgrade.log.
|
Contact Oracle Support Services for any errors that are not documented.
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 3-2 describes the location and contents of the different log files.
Table 3-2 Generated Files
| Name of File | Location of File | Contents and Purpose |
|---|---|---|
|
|
If you upgraded the portal schema in the OracleAS Metadata Repository:
If you upgraded the portal schema in a customer database:
|
Contains information that was logged while performing prechecks during an upgrade. Errors are summarized at the end of the log file. |
|
|
If you upgraded the portal schema in the OracleAS Metadata Repository:
If you upgraded the portal schema in a customer database:
|
Contains all the logged information including errors, warnings, and details. Errors are summarized at the end of the log file. |
|
|
If you upgraded the portal schema in the OracleAS Metadata Repository:
If you upgraded the portal schema in a customer database:
|
Contains a summary of the error messages from the end of the |
|
|
If you upgraded the portal schema in the OracleAS Metadata Repository:
If you upgraded the portal schema in a customer database:
|
Contains a summary of the warning messages from the end of the |
After performing the upgrade, you must back up the database that contains the upgraded portal schema. To do this, you must shut down the database, perform a backup, and then start the database.
There are several ways to perform a backup. Consult an experienced database administrator, or refer to Oracle Database documentation for further information about the backup and recovery procedures for the database.
Effects of Shutting Down the Database
In OracleAS Portal release 10.1.4, missing Oracle Text indexes are created during upgrade, but they are not populated at that time because this can be time-consuming. The new indexes are populated once the upgrade is complete, when the next synchronization job is scheduled.
After the upgrade, if you need to shut down the database to perform a backup, and the Oracle Text index synchronization job has started, then consider the impact of the shutdown commands, described in Table 3-3, on the synchronization process.
Table 3-3 Commands Used for Shutting Down the Database
| Shutdown Command | Description |
|---|---|
|
|
The indexing job stops immediately and is rolled back. |
|
|
The entire indexing job finishes before the database shuts down. |
|
|
Synchronization of the current index is allowed to finish before the database shuts down. If one or more indexes still need to be synchronized, then the synchronization of the next index is not started. |
After the upgrade is completed successfully, start each middle tier that is using the upgraded OracleAS Portal instance by performing the following steps:
Start OPMN and its managed processes by using the following command:
MIDDLE_TIER_ORACLE_HOME/opmn/bin/opmnctl startall
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.
If the upgrade is completed successfully, then you are ready to access the upgraded OracleAS Portal instance. Due to architectural changes, the format of URLs has changed in OracleAS Portal release 10.1.4.
Open a browser and specify the URL to access OracleAS Portal in the following format:
http://<host>:<port>/portal/pls/<portal_DAD>
Table 3-4 OracleAS Portal Access URL Parameters
| Parameters | Description |
|---|---|
|
|
The computer on which you installed OracleAS Portal. Specify the host name and the fully qualified domain name, for example,
|
|
|
The port number to access OracleAS Portal. Typically, this is the OracleAS Web Cache listen port of the middle tier. |
|
|
The Database Access Descriptor (DAD) name of the upgraded OracleAS Portal instance. This is the same DAD name you used before the upgrade. |
