|
Oracle® Application Server Upgrade and Compatibility Guide
10g Release 2 (10.1.2) for UNIX Part No. B14090-05 |
|
 Previous |
 Next |
|
Oracle® Application Server Upgrade and Compatibility Guide
10g Release 2 (10.1.2) for UNIX Part No. B14090-05 |
|
|
Previous |
Next |
This chapter describes how to upgrade Oracle Application Server standalone components and Oracle Application Server components that are installed separately from the other Oracle Application Server components.
These components are middle-tier components that cannot be upgraded automatically by the OracleAS Upgrade Assistant.
The following section describe how to upgrade these components:
Upgrading a standalone OC4J instance (for example, an instance created with the OC4J that is available for download from Oracle Technology Network in zip format) is a manual process. The OracleAS Upgrade Assistant does not upgrade such instances. You must re-deploy the applications in the Oracle Application Server 10g Release 2 (10.1.2) Oracle home:
Create an OC4J instance to host the applications in the 10g Release 2 (10.1.2) Oracle home, using the Oracle Enterprise Manager 10g Application Server Control Console.
Configure the OC4J instance with any system properties or environment variables that are unique to the standalone instance.
Identify all command-line arguments from the java -jar command line in the standalone instance.
In Oracle Application Server, the Oracle Process Manager and Notification Server (OPMN) subsystem is responsible for starting and stopping OC4J.
Move all command-line arguments to the following configuration file:
DESTINATION_ORACLE_HOME/opmn/conf/opmn.xml
Move any properties specified in properties files in the standalone instance to the opmn.xml file.
Re-deploy the standalone applications (EAR files) in the Oracle Application Server 10g Release 2 (10.1.2) Oracle home.
You can use the Application Server Control Console to deploy the applications.
|
See Also: "Introduction to Administration Tools" in the Oracle Application Server Administrator's Guide for information about using Application Server Control" Deploying a New OC4J Application" in the Enterprise Manager online help |
To upgrade a standalone instance of OracleAS Web Cache Release 2 (9.0.2 or 9.0.3) to Oracle Application Server 10g (9.0.4), do not use the OracleAS Upgrade Assistant. Instead, use the procedure described in this section. (A standalone instance is one installed from a kit that included only this product; it was not installed as part of an Oracle Application Server installation.)
|
Note: To upgrade an instance of OracleAS Web Cache that was installed as part of an Oracle Application Server installation, use the OracleAS Upgrade Assistant, which is documented in Chapter 4, "Upgrading the Middle Tier" |
You use the OracleAS Web Cache Upgrade Tool (WebcacheMigtool), which performs the following functions to provide a way to audit the upgrade process:
Creates a backup copy of the webcache.xml file from the source Oracle home. The backup file is named webcache.xml.preUpgrade.
Note that if you run the Upgrade Tool more than once, your original settings will be lost. To prevent this, create another backup copy before you begin.
Logs all upgrade activity in the file wxupgrade.log in the directory in which you run the Upgrade Tool.
To upgrade OracleAS Web Cache, take the following steps:
Stop the previous, standalone version of OracleAS Web Cache, using the webcachectl executable:
ORACLE_HOME/bin/webcachectl stop
Stop the newly installed version, using the opmnctl command:
opmnctl stopproc ias-component=WebCache
Set the ORACLE_HOME environment variable to the 10g Release 2 (10.1.2) Oracle home.
Run the following command. (Note that it is a single line.)
$ORACLE_HOME/jdk/bin/java -classpath "lib/webcacheua.jar:lib/ua.jar:
$ORACLE_HOME/lib/xmlparserv2.jar:$ORACLE_HOME/lib/dms.jar"
oracle/ias/upgrade/config/webcache/WebcacheMigtool
-s source_OH
-d destination_OH
In this example, you must supply the following two arguments:
source_OH, which refers to the full path to the Release 2 (9.0.2) or (9.0.3) Oracle home.
destination_OH, which refers to the full path to the 10g Release 2 (10.1.2) Oracle home.
The command provides optional arguments that allow you to upgrade from the same version or upgrade between different hosts. These arguments are necessary only when the source cache is part of a cache cluster. In that case, the configuration file contains entries for more than one cache and you must use one or more of these arguments to specify which cache is the source cache.
-o sourcefile_OH: Specifies the Oracle home for the particular cache in the source configuration file. Usually, this value is equal to <source_OH> specified by -s. However, to "upgrade" to the same version, such as when you want to migrate the configuration from a test cache to a production cache, you use this option.
To migrate, you must copy the source configuration file and DTD files, and optionally the error files and wallet files, to a temporary directory. Then, you run the Upgrade Tool using the temporary directory as <source_OH>, and this option to specify the Oracle home value used in the source configuration file.
-h sourcefile_HOSTNAME: Specifies the HOSTNAME for the particular cache in the source configuration file. Usually, this value is equal to the localhost. However, if the source and the destination installations are on different hosts, you must use both the -o and -h options.
To migrate to a different host, copy the source configuration file and DTD files and optionally the error files and wallet files, to a temporary directory on the destination host. Then, you execute the Upgrade Tool using the temporary directory as <source_OH>, and using the -o and -h options.
If the user under which the previous version of OracleAS Web Cache was installed is different than the user under which the current version of OracleAS Web Cache was installed, the upgraded OracleAS Web Cache will not start. The upgrade process modifies the webcache.xml, modifying the IDENTITY element to be the user from the previous version.
You must edit the webcache.xml file to correct this. In the IDENTITY element, modify the USERID, and if necessary, the GROUPID, to reflect the user and group under which the current version of OracleAS Web Cache was installed.
Enable the webcached executable to run as the root user, if necessary. For example, if you configure OracleAS Web Cache to listen on a port less than 1024, such as on port 80, you must take this step. See Chapter 8 of the Oracle Application Server Web Cache Administrator's Guide for information.
Restart the upgraded OracleAS Web Cache, using the following command:
opmnctl startproc ias-component=WebCache
This command starts the admin server, cache server process, and, if enabled, the auto-restart process.
|
Note: Do not start the previous version of OracleAS Web Cache because you may encounter port conflicts. |
This section explains how to upgrade Oracle9iAS InterConnect.
Since Oracle Application Server InterConnect is not distributed on the Oracle Application Server CD-ROM, and thus may not yet be installed, this section includes installation as a first step to upgrading. Installation instructions for each adapter are provided in the Oracle Application Server InterConnect documentation in the Oracle Application Server documentation library.
For the purposes of Oracle Application Server InterConnect, you can upgrade from Release 2 (9.0.2), 10g (9.0.4), or 10g Release 2 (10.1.2.0.0). Oracle Application Server InterConnect 10g Release 2 (10.1.2.0.2) provides several new features and improvements, such as the ability to manage InterConnect from the 10g Release 2 (10.1.2.0.2) Application Server Control Console.
|
See Also: "What's New in This Release" in the Oracle Application Server Integration InterConnect User's Guide |
The upgrade process consists of the following tasks:
The location where you install Oracle Application Server InterConnect components varies, depending upon the version you are using:
In Oracle9iAS Release 2 (9.0.2) topologies, Oracle Application Server InterConnect components reside in the Infrastructure or middle tier Oracle home, or a different Oracle home.
In 10g (9.0.4), Oracle Application Server InterConnect components do not reside in the Infrastructure or middle tier Oracle home. In fact, you must install them in a different Oracle home.
In 10g Release 2 (10.1.2.0.0) and 10g Release 2 (10.1.2.0.2), Oracle Application Server InterConnect components reside in the middle tier Oracle home.
Your first step in upgrading to Oracle Application Server InterConnect 10g Release 2 (10.1.2.0.2) is to install the 10g Release 2 (10.1.2.0.2) Hub, Adapters, and Development Kits by following the installation instructions in the Oracle Application Server InterConnect installation documentation, which is available on the Oracle Application Server 10g Release 2 (10.1.2.0.2) documentation library:
http://www.oracle.com/technology/documentation/
The information provided in the installation procedure should reflect the configuration of the components that you are upgrading.
Ensure that the architecture described in the 10g Release 2 (10.1.2.0.2) installation is the same as the architecture you are upgrading, unless you intend to change the architecture.
Follow these steps to upgrade the Oracle Application Server InterConnect metadata:
Install the most recent Oracle Application Server InterConnect patch set for the version you are upgrading.
For example, if you are upgrading from Release 2 (9.0.2), be sure that you have installed the latest Release 2 (9.0.2) patchset.
Run the oaiexport script provided with the Release 2 (9.0.2), 10g (9.0.4), or 10g Release 2 (10.1.2.0.0) installation.
Supply values for repository name, file name, system password, and connect string with the following command:
SOURCE_ORACLE_HOME/oai/version/repository/oaiexport file_name system\system_password connect_string
In this example, version represents 9.0.2, 9.0.4, or 10.1.2.0.0, depending upon the version of Oracle Application Server InterConnect you are upgrading.
The metadata is exported to the file_name you provide in the current directory.
Run the oaiimport script provided with the new 10g Release 2 (10.1.2.0.2) installation.
Supply values for repository name, file name, from user (the user ID of the user whose metadata is being imported), system password, ichub schema password, and connect string with the following command:
DESTINATION_ORACLE_HOME/integration/interconnect/repository/oaiimport file_name from_user system\system_password ichub_schema_password connect_string
When you run this command, the file_name you provide is imported into the 10g Release 2 (10.1.2.0.2) Hub database.
Create the tables in the hub schema database by executing one of the following SQL commands in the hub schema.
If you are upgrading from Release 2 (9.0.2), execute the SQL commands in Example 8-1.
If you are upgrading from 10g (9.0.4), execute the SQL commands in Example 8-2.
If you are upgrading from 10g Release 2 (10.1.2.0.0), skip directly to the next step in the procedure.
Execute the following SQL script, which is available in the following directory in the new 10g Release 2 (10.1.2.0.2) Oracle home:
DESTINATION_ORACLE_HOME/integration/interconnect/repository/sql/xsd.sql
Example 8-1 Creating Oracle Application Server InterConnect Tables When Upgrading From Release 2 (9.0.2)
CREATE TABLE emdcomments (emdid NUMBER(10)
CONSTRAINT fk_emdcomments_emdid REFERENCES
emd(id) ON DELETE CASCADE
CONSTRAINT nn_emdcomments_emdid NOT NULL,
name VARCHAR2(4000)
CONSTRAINT nn_emdcomments_name NOT NULL,
comments LONG);
DROP TABLE ComponentInfoValue;
CREATE TABLE ComponentInfoValue (seqnum NUMBER
CONSTRAINT fk_seqnum REFERENCES
ComponentInfo(seqnum) ON DELETE CASCADE,
value RAW(1024);
The Oracle Application Server Integration InterConnect Management architecture has changed significantly from previous releases. With Oracle Application Server InterConnect 10g Release 2 (10.1.2.0.2), you can now use the Oracle Enterprise Manager 10g Application Server Control Console to manage Oracle Application Server InterConnect runtime components.
Note, however, that the Application Server Control Console can be used only for the following operations:
Configuring the InterConnect hub, repository and adapter properties
Starting and stopping the Interconnect runtime components (Repository and Adapters)
Monitoring the runtime performance metrics of the running adapters
For other management activities (for example, modifying and resubmitting the error and fault messages), you can use the ICManager command-line tool. ICManager is available at the following location within the 10g (10.1.2) Oracle Application Server InterConnect Oracle home:
DESTINATION_ORACLE_HOME/integration/interconnect/bin/ICManager
|
See Also: Oracle Application Server Integration InterConnect User's Guide for more information about using the Application Server Control Console and ICManager to manage Oracle Application Server InterConnect |
For 10g Release 2 (10.1.2), Oracle Application Server ProcessConnect is not being shipped and cannot be upgraded from 10g (9.0.4) to 10g Release 2 (10.1.2). In addition, you cannot migrate Oracle Application Server ProcessConnect 9.0.4 to Oracle Application Server Integration B2B 10.1.2.
This section details the steps for upgrading OracleAS repositories that are stored outside of the OracleAS Metadata Repository.
Upgrading the Oracle Business Intelligence Discoverer End User Layer Schema
Upgrading the OracleAS Portal Repository in a Customer Database
If you have been using Oracle Business Intelligence Discoverer version 9.0.2.52 or earlier, you must upgrade the End User Layer before you can use Oracle Business Intelligence Discoverer in 10g Release 2 (10.1.2).
To upgrade the Oracle Business Intelligence Discoverer End User Layer schema, you use Oracle Discoverer Administrator, shipped with the Oracle Developer Suite 10g Release 2 (10.1.2).
|
See Also: Oracle Business Intelligence Administration Guide in the Oracle Developer Suite documentation library. |
This section details the steps for upgrading an OracleAS Portal repository stored outside of the OracleAS Metadata Repository.
General information on upgrading to OracleAS Portal 10.1.2, as well as instructions for upgrading from other versions, is provided at:
http://portalcenter.oracle.com/upgrades
Click 10.1.2 in the list of upgrade targets on the page.
Refer to the following sections for more information about upgrading the OracleAS Portal repository in a customer database:
Preparing to Upgrade the OracleAS Portal Repository in a Customer Database
Running the OracleAS Portal Repository Upgrade in a Customer Database
Completing the OracleAS Portal Repository Upgrade in a Customer Database
The following steps should be executed to prepare for the upgrade:
Upgrade the middle tiers that are using the OracleAS Portal Repository to Oracle Application Server 10g Release 2 (10.1.2) and test OracleAS Portal using these middle tiers.
Perform this step for all middle tiers that are associated with the OracleAS Portal repository being upgraded. For instructions, refer to Chapter 4, "Upgrading the Middle Tier".
Ensure that the OracleAS Portal repository database is at least Oracle9i Release 2 (9.2.0.7).
Follow the instructions provided in Section 7.3.1.1, "Downloading and Installing the OracleAS Portal 10g (9.0.4) Repository Upgrade Software".
Follow the instructions provided in Section 7.3.1.2, "Downloading and Installing the Oracle9iAS Single Sign-On 9.0.2.5 Patch"
If you have Portal instances that are upgraded from Portal versions earlier than 9.0.2, follow the instructions in the section on migrating content between upgraded OracleAS Portal instances, in the section "Migrating Content Between Upgraded OracleAS Portal Instances" in the Oracle Application Server Portal Configuration Guide.
Export/import is not supported between two portals that are upgraded from versions earlier than 9.0.2. For example, assume that you have a source development Portal instance and a target production Portal instance, both of version 3.0.9. You then upgrade both the instances independently to version 9.0.4, and then to version 10.1.2. Exporting and importing content between these two upgraded 10.1.2 development and production instances is not supported.
For information on system requirements and supported versions, refer to the section "Exporting and Importing Content" in the Oracle Application Server Portal Configuration Guide."
The following steps should be run to upgrade an OracleAS Portal repository residing in a customer database:
Create a cold backup of the database in which your OracleAS Portal repository resides.
Set the ORACLE_HOME environment variable to the OracleAS Portal repository database Oracle home.
Mount the Metadata Repository Upgrade Assistant and Utilities CD–ROM.
The MRUA and Utilities CD–ROM is part of the Oracle Application Server CD–ROM Pack that you receive when you order the Oracle Application Server software.
Verify you can connect to the OracleAS Portal schema through SQL*Plus using the schema password and the TNS name from the database Oracle home where your OracleAS Portal repository is installed.
For example:
sqlplus portal30/portal30@orcl
Stop all Oracle Application Server services in the middle-tier Oracle homes that are associated with the Portal repository being updated.
|
See Also: "Starting and Stopping the Application Server" in the Oracle9i Application Server Administrator's Guide in the Release 2 (9.0.2) documentation library |
Change directory to a location where you have write permissions. The upgrade will create a set of log files and temporary directories in this location.
Verify that the Oracle Internet Directory that is associated with the Portal repository is up and running.
Run the upgrade shell script in precheck mode until there are no errors found:
MRUA_CD_ROOT_DIRECTORY/portal/admin/plsql/upgrade -precheck
When -precheck is specified, only the prechecks are done and the upgrade exits afterward. 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. Look at the end of the log to see a list of checks that failed. Run in 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.
Run the upgrade script without any parameters:
MRUA_CD_ROOT_DIRECTORY/portal/admin/plsql/upgrade
The script prompts you for information about the system setup. Your answers are echoed back for verification at the end of the script. However, if you discover that you have entered incorrect information before the end of the script, 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, answer n, then back up the database and restart the script. If you have, answer y.
Enter the name of the schema you would like to upgrade [portal]:
If your schema name is different from the default OracleAS Infrastructure 10g installation schema name of portal, enter the schema name
Enter the password of the schema you would like to upgrade [portal]:
Change the default value entered for the schema name, if appropriate.
Enter the password for the SYS user of your database [change_on_install]:
If the password is not change_on_install, enter the database SYS password.
Enter the TNS connect string to connect to the database [orcl]:
Provide the TNS connect string (found in the tnsnames.ora file).
When the script is complete, examine the precheck and upgrade log files in the current directory to make sure there are no errors reported at the end.
|
Caution: Any portals running after an upgrade that was not clean are not supported by Oracle. |
Look up any errors found in the precheck or upgrade log files using Section C.7, "Error Messages When Upgrading Oracle Application Server Portal" as a reference. Resolve any errors and warnings that have documented actions. Any errors that occur after the precheck phase require the repository to be restored from backup, the problem resolved and another upgrade run. Contact Oracle Support for any errors that are not documented or that cannot be resolved by following documented actions. When undocumented errors are found, do not attempt to run the upgrade again, run any further steps, alter any files, modify the OracleAS Portal schema, or access the OracleAS Portal instance in your browser.
For detailed information on the log files generated during the OracleAS Portal upgrade, refer to Section 7.4.8, "Reviewing the OracleAS Portal Repository Upgrade Log Files".
To complete the OracleAS Portal repository upgrade in a customer database, follow the instructions in Section 7.5.1, "Completing the OracleAS Portal Schema Upgrade Process".
The Oracle Workflow schema can be installed in the OracleAS Metadata Repository or in a customer database.
If you the Oracle Workflow schema is installed in a OracleAS Metadata Repository, it will be upgraded with the other Oracle Application Server component schemas when you run the Metadata Repository Upgrade Assistant.
If you have installed the Oracle Workflow schema in a customer database, run the Oracle Workflow Configuration Assistant with either the Server Only or the Server and Middle Tier install option to upgrade the Oracle Workflow schema.
Ensure that no users are accessing the server; otherwise, locks in the database may prevent a successful upgrade.
|
See Also: Section 4.10.3, "Special Instructions When Upgrading Oracle Workflow Middle Tier Components"Oracle Workflow Installation Notes for Oracle Content Management Software Development Kit Oracle Workflow Administrator's Guide |
The OWA packages that make up the PL/SQL Web Toolkit are not automatically upgraded if you have PL/SQL applications that are installed in a customer database that does not include an OracleAS portal schema.
Refer to "Configuring mod_plsql" the Oracle Application Server mod_plsql User's Guide for instruction on how to manually install the latest version of the OWA packages.
