|Oracle® Fusion Middleware Upgrade Guide for Oracle WebCenter Interaction
10g Release 4 (10.3.3.0.0) for Unix and Linux
Part Number E14550-04
It includes the following sections:
This section describes how to upgrade the portal database. It includes the following sections:
This section describes how to upgrade the Oracle WebCenter Interaction portal database on Oracle Database for UNIX.
When running Oracle WebCenter Interaction with Oracle Database 11g with the provided initPLUM10.ora file, make the following modification: change
compatible = 10.2.0.0.0 to
compatible = 11.0.0.
To prevent problems with “group by” optimizations when using Oracle WebCenter Interaction with Oracle Database 11g you must add the following configuration to the bottom of your init$ORACLE_SID.ora file:
Log in to the portal database host computer as the owner of the Oracle system files.
ORACLE_SID are set appropriately. For details, see Setting Oracle Environment Variables.
Copy the SQL scripts from the Oracle WebCenter Interaction installation directory to your Oracle server.
For Oracle9i, the Oracle WebCenter Interaction installer creates the SQL scripts in the following directories:
For Oracle Database 10g, the Oracle WebCenter Interaction installer creates the SQL scripts in the following directories:
For Oracle Database 11g, the Oracle WebCenter Interaction installer creates the SQL scripts in the following directories:
Run the upgrade10.3.0to10.3.3_oracle.sql script to upgrade the database.
Run the Database Upgrade Tool only after running the upgrade scripts.
The command line Database Upgrade Tool is used to upgrade a portal database to 10.3.3 specifications. You must run the tool twice. The first time you run the Database Upgrade Tool, it creates a text file to hold the data required by the upgrade tool. You edit the file (entering parameters such as the location of various files), then run the upgrade tool again to perform the upgrade.
Your system must be properly configured to run the portal in order to use this application, as it relies on your portal configuration to know how to connect to the database and complete the upgrade.
Run the Database Upgrade Tool from $PORTAL_HOME/bin/dbupgradetool.sh.
This script takes two parameters:
Admin User Name - type the name of the Administrator user that you created when you installed your 10.3.0.1 portal (not another user in the Administrators group). The default name is “Administrator,” but you may have changed the name for security purposes after installation.
The Admin User Name is case sensitive.
Password - type the password for the Administrator user. If this user has an empty password, do not type anything.
The upgrade tool creates the upgradedata.properties file in install_dir/settings/portal.
When prompted to edit the properties file, you can skip this step. There is no new data required for this release.
Run the Database Upgrade Tool again to begin upgrading the database. The upgrade can run for a few seconds or a few hours, depending on the size of your database. If the Database Upgrade Tool encounters errors or data inconsistencies, it does not stop. Instead it logs the errors to the file specified in Step 3.
When the database upgrade completes, you are notified of the status. If the upgrade completed successfully (without errors), skip to Step 7.
If PTGROUPMEMBERSHIP has a materialized view you may see an error regarding inability to drop a view. This can be ignored.
If there were errors, you should examine the log file, identify solutions, restore the database to its previous state, fix the problems, and re-run the Database Upgrade Tool.
You must restore the database to its original 10.3.0.1 state before you re-run the Database Upgrade Tool. The Database Upgrade Tool may modify the database even if it fails. Therefore, even if the upgrade did not complete successfully, the database is at least partially upgraded to 10.3.3 specifications.
If you changed the database credentials, change them back to use the Oracle WebCenter Interaction database user.
This section describes how to create and configure a database for the Tagging Engine.
You only must perform this procedure if you installed the Tagging Engine.
To create and configure the Tagging Engine database on Oracle Database:
Copy the oracle directory from install_dir/pathways/10.3.3/sql/oracle/unix to the Tagging Engine database's host computer. This folder includes the scripts that you will use to set up and configure the Tagging Engine database.
Log on to the host computer for the Tagging Engine database as owner of the Oracle system files.
Execute the following steps as the system user in your Oracle Database:
Run the script create_pathways_tablespaces.sql for your platform. This file is located in a platform specific subdirectory within the oracle directory that you copied in step 1.
Before running the script, determine the name of the SID used in your portal database. If necessary, edit the script so that all SID name instances in the script match the SID name used for the portal database.
Run the script create_pathways_user.sql.
Execute the following steps as the Tagging Engine user that you just created:
Run the script create_pathways_schema.sql. This script creates all of the tables and indexes that are necessary to run the Tagging Engine. The create_pathways_schema.sql script is located in the oracle directory that you copied in step 1.
Run the script install_pathways_seeddata.sql. This script adds all of the initial seed data that are necessary to run the Tagging Engine. The install_pathways_seeddata.sql script is located in the oracle directory that you copied in step 1.
Run your database's analysis tool on the portal database to increase the efficiency of the database.
This section describes how to set up the ALUI Security database.
You do not must perform this procedure if Oracle WebCenter Analytics is installed. Installing Oracle WebCenter Analytics requires creating the ALUI Security database.
This section describes how to create and configure the ALUI Security database on Oracle Database.
Log on to the host computer for the ALUI Security database as owner of the Oracle system files.
Create the ALUI Security database tablespace.
Create the ALUI Security database user.
Connect to the ALUI Security database as the ALUI Security database user.
Run the create_security_tables.sql script, located in the folder that you copied in step 1.
Run your database's analysis tool on the ALUI Security database to the efficiency of the database.