This appendix details the steps for upgrading a portal schema residing in a customer database configuration outside the Oracle Metadata Repository. To upgrade the portal schema residing in a customer database, you must use the upgrade.bat (on Windows operating systems) or upgrade (on UNIX operating systems) 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 middle tier.
Add the Transparent Network Services (TNS) entry of the database containing portal schema to ORACLE_INSTANCE\config (on Windows operating systems) or ORACLE_INSTANCE/config (on UNIX operating systems).
On UNIX operating systems, set the TNS_ADMIN environment variable to the following location: ORACLE_INSTANCE/config.
Ensure that you are able to connect to database using the Portal schema.
Verify if you can connect to the Portal schema in the database Oracle home by specifying the schema password and the TNS name using SQL*Plus.
For example on UNIX operating systems:
sqlplus portal/portal@orcl
Change the directory to ORACLE_HOME/upgrade/portal/admin/plsql (on UNIX operating systems).
Stop all Oracle Fusion middleware services in the middle-tier Oracle homes that are associated with the portal schema being migrated. For this, stop WLS_PORTAL through the Oracle WebLogic Server Administration Console, and run ORACLE_INSTANCE/bin/opmnctl stopall (on UNIX operating systems).
Verify that Oracle Internet Directory associated with the portal schema is up and running.
Run the upgrade script in precheck mode.
On UNIX operating systems, run the script as follows:
ORACLE_HOME/upgrade/portal/admin/plsql/upgrade -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 upgrade.log file. This file is generated in the ORACLE_HOME/upgrade/portal/admin/plsql (on UNIX operating systems) 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. 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 operating systems, run the script as follows:
ORACLE_HOME/upgrade/portal/admin/plsql/upgrade
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 Oracle Infrastructure 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_INSTANCE/config/tnsnames.ora file (on UNIX operating systems).
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.
Now start the middle tiers associated with this repository. Check that Oracle Portal is accessible.