| Oracle® Collaboration Suite Upgrade Guide 10g Release 1 (10.1.1) for hp-ux PA-RISC (64-bit), Linux x86 and Solaris Operating Environment (SPARC) Part Number B14490-03 |
|
|
View PDF |
| Oracle® Collaboration Suite Upgrade Guide 10g Release 1 (10.1.1) for hp-ux PA-RISC (64-bit), Linux x86 and Solaris Operating Environment (SPARC) Part Number B14490-03 |
|
|
View PDF |
This chapter explains how to upgrade Oracle9iAS Portal 9.0.2 to Oracle9iAS Portal 9.02.6. These steps are applicable your configuration meets the following criteria:
A Release 2 (9.0.4.2) middle tier configured with Oracle9iAS Portal.
A single Oracle9iAS Metadata Repository database used by both Oracle Internet Directory and your middle tier applications.
You want Oracle9iAS Portal to continue to work after each tier is upgraded.
Perform the steps in the following section before starting the upgrade:
To upgrade your Oracle9iAS Single Sign-On Server from release 9.0.2 to 9.0.2.6:
Log into Oracle MetaLink (http://metalink.oracle.com).
Locate patch 2995671 for your operating system.
Follow the instructions in the Readme file and in the Oracle9iAS Single Sign-On Migration Guide (doc/sso_patch_902.html file). These two documents are both contained with the patch. The patch is applied to the Oracle9iAS Single Sign-On Server schema in your Oracle9iAS Infrastructure Release 9.0.2.
To upgrade Oracle9iAS Portal, perform the steps in the following sections:
Download the Oracle9iAS Portal 9.0.2.6 Patch and Extract the Contents
Download the Latest Oracle9iAS Portal Repository Upgrade Patch
To download and extract the Oracle9iAS Portal Release 9.0.2.6 patch:
Log into Oracle MetaLink (http://metalink.oracle.com).
Locate patch 2974042 for your operating system.
On the middle tier system, download the ZIP file into a temporary directory and extract its contents. The file contains the following items:
Disk1 - a directory containing the scripts used to run the Oracle9iAS Portal middle tier updates and the repository upgrade
Readme.html - A readme file
Examine the Readme.html file for any changes that could affect the remaining procedures.
Before proceeding to the next steps, back up the middle tier Oracle home.
To run the Oracle Universal Installer:
Verify you are logged in to the machine where your middle tier Oracle home is located. The installer cannot be run from any other machine since it needs access to the middle tier processes.
Set your ORACLE_HOME environment variable to point to your Oracle9iAS 9.0.2 middle tier Oracle home.
On UNIX, verify that your DISPLAY environment variable is set correctly. The Oracle Universal Installer brings up the user interface that requires this setting.
Verify the Oracle9iAS Infrastructure processes:
If installing the patch on an Oracle9iAS middle tier, verify the Infrastructure processes are up and running. This is required by the OC4J Configuration Assistant to deploy the Oracle9iAS Portal applications in the Oracle9iAS middle tier.
Shut down the active Oracle Enterprise Manager services of the machine.
Shut down the Oracle9iAS middle tier services.
Go to the temporary directory where you extracted the contents of the ZIP file.
Run the following command from that directory to extract the Oracle9iAS Portal upgrade scripts and the new middle tier files:
Disk1/install/platform/runInstaller
where platform is the name of your operating system.
Click Next on the Welcome screen to proceed to the File Locations screen.
In the source path field on the File Locations screen, specify the products.jar file that was included in the download. For example, if you unzipped the downloaded file into your /tmp directory, you would specify /tmp/Disk1/stage/products.jar as the file.
Verify the destination Oracle home name and path.
Click Next to proceed to the Summary screen.
Verify that, under the New Installations heading, there are several Oracle9iAS Portal 9.0.2.6.x products listed.
Click Install. It generally takes from 15 to 30 minutes to distribute the files to the appropriate locations under your Oracle home and to start up the necessary processes. For the first few minutes, the user interface may seem frozen. However, the progress bar will soon become active.
Check the Configuration Tools page. It now shows the status of the Oracle9iAS Portal Application deployment.
Click Exit on the End of Installation screen.
To download the Oracle9iAS Portal repository upgrade patch:
Log into Oracle MetaLink (http://metalink.oracle.com).
Locate patch 2981297 for your operating system.
Download the ZIP file onto a temporary directory in your machine. This is a generic download that contains scripts that will run on all supported platforms.
Change directories to the root of the Oracle9iAS Portal source code. This is under the middle tier Oracle home under portal/admin/plsql.
Extract the contents of the downloaded ZIP file into the current directory. When unzipping, choose to overwrite all existing files.
To run the repository upgrade script:
Verify that the middle tier configured with Oracle9iAS Portal 9.0.2 is not running.
Change directories to the root of the Oracle9iAS Portal source code. This is in the middle tier Oracle home under portal/admin/plsql.
The source code under this directory was updated in the previous steps when the installer was run and the upgrade patch contents were extracted.
Note:
This root directory is also where the main upgrade script is located. Elsewhere in the documentation it is referred to asupgrade_directory.
If the file upgrade.pl is not located in the portal/admin/plsql directory under your middle tier Oracle home, verify that the steps for extracting patch 2981297 have been followed accurately.
Run the upgrade script in precheck mode until there are no errors found.
perl upgrade.pl -precheck [-l log-file] [-t tmp-directory] [-ssoid sso-id]
Run the upgrade script in normal mode and designate the parameters:
perl upgrade.pl [-l log-file] [-t tmp-directory] [-ssoid sso-id]
Table 10-1 Upgrade Script Parameters
| Parameters | Description |
|---|---|
|
-precheck |
If precheck is specified, then only the prechecks are done and the upgrade exits afterwards. In this mode, the upgrade is not immediately aborted if a precheck fails.Instead, the errors for all prechecks are consolidated in the upgrade log. Look at the log to see a list of checks that failed. Refer to troubleshooting for solutions to errors. Run this mode until none of the prechecks fail. In this mode, the schema is not altered, so restoring from your backup is not necessary between runs. |
|
-l log-file |
Any log file name you specify.Default=upgrade.log. |
|
-t tmp-directory |
Any temporary directory name you specify. It must be empty and you must have write permissions on it. In this document, it is also be referred to as upgrade_tmp_dir.Default=tmp |
|
-ssoid sso-id |
This parameter is the identifier of the Oracle9iAS Single Sign-On Server with which the Oracle9iAS Portal is associated before the Oracle9iAS Portal schema is upgraded. This is a 15 character value that must match the identifier used when patching the Oracle9iAS Single Sign-On Server. This value is only required if either the Oracle9iAS Single Sign-On Server identifier can not be generated automatically, or if the server was patched earlier but the identifier that was used needs to be changed. Typically, you do not have to pass this value as the system generates one automatically.Refer to Section 10.1.1 for patch details. |
The following examples assume that you have the appropriate middle tier Oracle home perl executable accessible from your path:
perl upgrade.pl -precheck -l precheck.log -t prechecktmp perl upgrade.pl -l myupgrade.log -t upgtmp perl upgrade.pl -l myupgrade.log perl upgrade.pl -t upgtmp perl upgrade.pl perl upgrade.pl -l myupgrade.log -t upgtmp -ssoid B63875271239654
The script asks questions about the system's setup. Your answers are echoed back for verification at the end of the script. If you discover that you have input incorrect information before the end of the script, you can exit before any changes are made by answering no (n) to the last question.
The following list displays the questions asked by 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, answer no (n). Back up the database and restart the script.
Enter the name of the schema you would like to upgrade [PORTAL]:
In a standard Oracle9iAS 9.0.2 infrastructure installation, the name of the schema is portal.
Enter the password for the schema that you would like to upgrade [portal_schema_name]:
If your Oracle9iAS Portal repository is in the infrastructure database, use the Oracle Directory Manager for obtaining the randomized Oracle9iAS Portal schema password. Navigate to:
Entry Management
cn=OracleContext
cn=Products
cn=IAS
cn=Infrastructure Databases
OrclReferenceName=Infrastructure Database (for example: iasdb.server.domain.com)
OrclResourceName=PORTAL
Click the OrclResourceName=PORTAL entry.
Look for the orclpasswordattribute value on the right panel. This value is the password for the schema.
Refer to the Oracle9i Application Server Administrator's Guide for further instructions.
Enter the password for the SYS user of your database [CHANGE_ON_INSTALL]:
Enter the TNS connect string to connect to the database [ORCL]:
The TNS connect string is in the tnsnames.ora file. Test your access to the database by using the Oracle9iAS Portal schema, schema password, and connect string.
At this point, no changes have been made to your database. Please review all the details displayed above. If you choose to stop the upgrade at this point, you will be able to start it again without restoring from a backup. If you continue and a problem occurs, you will have to retrieve your backup and start over. Is it OK to continue with the upgrade? (y|n) [y]:
Enter y to proceed with the upgrade.
Enter n to abort the upgrade. You can then run the upgrade script again, correcting your inputs.
Note:
Refrain from using your system during the upgrade. It will take several hours to upgrade your Oracle9iAS Portal repository. Actual timing depends on size of the repository, the system load and so forth.Once the upgrade has completed, it is imperative to check the log for any errors.
Locate the log file. The default name for the log is upgrade.log. It is located in the same directory as the main upgrade script: upgrade_directory.
Unless the upgrade terminates abruptly before finishing, the errors in the log 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. Any errors are also summarized in a file named upgrade_tmp_dir/upgrade.err. Any warnings are also summarized in a file named upgrade_tmp_dir/upgrade.wrn.
Open the log file with a text editor.
Research all errors and warnings using Chapter 4, "Troubleshooting" from the Oracle9iAS Portal Upgrade Guide Release 9.0.2 to 9.0.2.6 for UNIX and Windows.
Resolve any errors and warnings that have documented actions. Most errors require the repository to be restored from backup, the problem resolved, and another upgrade run.
Note:
Any Oracle9iAS Portal running after an upgrade that was not clean is not supported by Oracle. A clean upgrade has either zero errors or only benign errors. Benign errors are documented as such in Chapter 4, "Troubleshooting" of Oracle9iAS Portal Upgrade Guide.Contact Oracle Support for any errors that are not documented.
Continue this process until all errors are resolved.
The following example displays messages from the end of the log file in the case of a successful upgrade. Notice the Upgrade completed successfully message and the lack of error messages:
### PHASE III STEP 18: Show Errors and Warnings
Upgrade step started at Thu Jun 26 09:05:36 PDT 200
### Upgrade completed with the following warnings
...
### Upgrade completed successfully
Upgrade Ended at Thu Jun 26 09:05:36 PDT 2003
The following examples display messages from log files where the upgrades were unsuccessful:
Example 1: Premature termination and no error or warning sections:
### ERROR: Patch Failed with status code: 1. ### ### Upgrade aborted at Tue Jul 15 15:09:33 EDT 2003.
Example 2: Normal termination, but at least one error found (notice the line numbers preceding each error line):
### ### PHASE III STEP 18: Show errors and warnings ### Upgrade step started at Fri June 6 20:32:02 2003 ### ### WARNING: ### Upgrade completed with the following warnings ### ### ### ERROR: ### Upgrade completed with the following errors ### 2803:ERROR at line 1: ### 2804:ORA-01418: specified index does not exist
Table 10-2 summarizes the locations and contents of the different log files.
Table 10-2 Generated Log Files
| File Name | File Location | Contents and Purpose |
|---|---|---|
|
upgrade_log |
upgrade_directory/upgrade_log |
Contains all the logged information including errors, warnings, and details. Errors are summarized at the end of the log file. |
|
upgrade.err |
upgrade_tmp_dir/upgrade.err |
Contains the summary of the error messages from the end of the upgrade_log file. |
|
upgrade.wrn |
upgrade_tmp_dir/upgrade.wrn |
Contains the summary of the warning messages from the end of the upgrade_log file. |
Table 10-3 Generated Log Files
| File Name | File Location | Contents and Purpose |
|---|---|---|
|
upgrade_log |
upgrade_directory\upgrade_log |
Contains all the logged information including errors, warnings, and details. Errors are summarized at the end of the log file. |
|
upgrade.err |
upgrade_tmp_dir\upgrade.err |
Contains the summary of the error messages from the end of the upgrade_log file. |
|
upgrade.wrn |
upgrade_tmp_dir\upgrade.wrn |
Contains the summary of the warning messages from the end of the upgrade_log file. |
If there were no errors, you are ready to access your upgraded Oracle9iAS Portal.
Start the Oracle Collaboration Suite middle tier.
Point your browser to:
http://<host>:<port>/pls/<dad>
where
host is the system where the Oracle9iAS Release 2 HTTP Server is running.
port is the port where the Oracle9iAS Release 2 HTTP Server is listening
dad is the Oracle9iAS DAD name of your upgraded OracleAS Portal. This is the same DAD name you used before the upgrade.
