| Oracle® Application Server Upgrade and Compatibility Guide 10g (10.1.4.0.1) for Microsoft Windows Part Number B28235-01 |
|
|
View PDF |
| Oracle® Application Server Upgrade and Compatibility Guide 10g (10.1.4.0.1) for Microsoft Windows Part Number B28235-01 |
|
|
View PDF |
The OracleAS Identity Management schemas are upgraded as part of the Oracle Identity Management 10g (10.1.4.0.1) upgrade in Chapter 7, "Using Oracle Universal Installer to Upgrade Oracle Identity Management". This chapter describes how to upgrade the component schemas using the Metadata Repository Upgrade Assistant (MRUA).
The following sections provide more information:
Task 1: Understand and Prepare for the OracleAS Metadata Repository Upgrade
Task 2: Run MRUA and Upgrade the OracleAS Metadata Repository Schemas
Task 3: Verify the Success of the OracleAS Metadata Repository Upgrade
Use the following sections to understand why you must upgrade the OracleAS Metadata Repository and to prepare for the OracleAS Metadata Repository upgrade:
Whenever you upgrade to a new version of Oracle Application Server, Oracle recommends that you upgrade all your Oracle Application Server components to the latest version. This ensures that you have the latest bug fixes and feature improvements. It also facilitates troubleshooting of any compatibility and configuration issues.
As a result, Oracle recommends that you use the Metadata Repository Upgrade Assistant (MRUA) to upgrade the component schemas in the OracleAS Metadata Repository to the latest version.
In fact, if you are already running Oracle Application Server 10g Release 2 (10.1.2.0.2), or if you have upgraded your 10g Release 2 (10.1.2) environment to OracleAS Portal 10g Release 2 (10.1.4), many of the component schemas will already be at the latest version. In those cases, MRUA alerts you in the MRUA output and in the MRUA log file if any of the component schemas were upgraded previously.
Running MRUA also verifies that the proper component schemas are installed and valid; it also verifies that the database that hosts the OracleAS Metadata Repository has been upgraded to a supported version.
Use the following procedure to prepare your Oracle Application Server environment for the OracleAS Metadata Repository upgrade:
Be sure that you have created a recent backup of the OracleAS Metadata Repository database.
Verify that the database that hosts the OracleAS Metadata Repository has been upgraded to a supported version for this release.
If you are running any 10g (9.0.4) middle tiers that use the OracleAS Metadata Repository, be sure to upgrade those middle tiers to 10g Release 2 (10.1.2) before proceeding with the OracleAS Metadata Repository upgrade.
Verify that the Oracle Internet Directory and database processes are running
Specifically, make sure that the following processes are up and running:
The database that hosts the OracleAS Metadata Repository
The database listener for the OracleAS Metadata Repository database
The Oracle Internet Directory instance where the OracleAS Metadata Repository database is registered
Log in to the Application Server Control Console to verify that the necessary processes are running and that the required components are configured properly. For example, you can use the Application Server Control Console to verify that the Farm page displays correctly and that the Oracle Internet Directory and OracleAS Single Sign-On components are up and running.
From the Application Server Home page in the Application Server Control Console click Ports to view a list of the ports currently in use by the application server instance, and to verify that the components are configured properly.
|
See Also: "Introduction to Administration Tools" in the Oracle Application Server Administrator's Guide for more information about using the Application Server Control Console |
Stop Any Middle Tier Instances That Use the OracleAS Metadata Repository
Before you use MRUA, you must stop all processes associated with each middle tier that uses the OracleAS Metadata Repository.
Note that at this point in the upgrade process, as a prerequisite for running MRUA, all the middle tier instances should have been upgraded to 10g Release 2 (10.1.2).
There are two ways to view all the Oracle Application Server instances that use the OracleAS Metadata Repository:
Display the Farm page in the Application Server Control Console.
|
See Also: "Introduction to Administration Tools" in the Oracle Application Server Administrator's Guide for more information about the Application Server Control Console Farm page |
Use the following Distributed Configuration Management command in the Oracle home of any middle-tier or OracleAS Identity Management instance that belongs to the farm:
ORACLE_HOME/dcm/bin/dcmctl listinstances
|
See Also: Distributed Configuration Management Administrator's Guide for more information aboutdcmctl commands |
To stop all the processes in a 10g (9.0.4) or 10g Release 2 (10.1.2) middle tier, use the Services Control panel to stop the ProcessControl service and the Application Server Control.
Check for Invalid Database Objects.
Use the following procedure to make sure that none of the database objects that are required by Oracle Application Server are invalid:
Connect to the OracleAS Metadata Repository database.
For example:
METADATA_REPOSITORY_ORACLE_HOME\bin\sqlplus "connect / as sysdba"
When prompted, enter the SYS password.
Issue the following SQL command:
SELECT owner, object_type, object_name FROM all_objects WHERE status='INVALID';
The query should not return any database objects that have an Oracle Application Server component schema (such as PORTAL, WIRELESS, and so on) in the 'owner' column.
If you find any invalid objects, run the utlrp.sql script from the SQL*Plus command line to recompile the invalid objects:
@?/rdbms/admin/utlrp.sql
To run MRUA:
Log in to the computer where the OracleAS Metadata Repository is running; use the same user account that was used to install the 10g (9.0.4) or 10g Release 2 (10.1.2) OracleAS Metadata Repository.
|
Note: Be sure to log in to the computer where the OracleAS Metadata Repository is running as the same user who installed the 10g (9.0.4) or 10g Release 2 (10.1.2) OracleAS Metadata Repository. MRUA must be run on the computer that hosts the OracleAS Metadata Repository that you are about to upgrade. |
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.
Start MRUA by entering the following command, with the following required arguments, which are described in Table 8-1:
CD_DRIVE_LETTER:\mrua\mrua.bat -oracle_home metadata_repository_oracle_home -oid_host Oracle_Internet_Directory_host -oid_ssl_port Oracle_Internet_Directory_SSL_port
Table 8-1 Summary of the Required MRUA Command Line Arguments
| Argument | Description |
|---|---|
|
-oracle_home |
The destination 10g (10.1.4.0.1) OracleAS Metadata Repository home directory. |
|
-oid_host |
The name of the computer that hosts the Oracle Internet Directory where the OracleAS Metadata Repository is registered. |
|
-oid_ssl_port |
The secure port for the Oracle Internet Directory. For the purposes of upgrading the OracleAS Metadata Repository, you must use a secure connection to the Oracle Internet Directory. |
When you are prompted, enter the password for the database SYS user account.
MRUA needs the SYS password so it can access and modify the component schemas in the database.
When you are prompted, enter the Oracle Internet Directory cn=orcladmin administrator password.
MRUA needs the Oracle Internet Directory password to connect to the Oracle Internet Directory in which the OracleAS Metadata Repository is registered.
After you provide the required passwords, MRUA checks to be sure the Oracle Internet Directory is running and does one of the following:
If Oracle Internet Directory is down or unavailable, MRUA displays an error message and exits.
If Oracle Internet Directory is up and running, MRUA connects to the directory service and obtains additional information required to upgrade the component schemas.
If multiple instances of the OracleAS Metadata Repository are registered with the directory, MRUA prompts you to select the OracleAS Metadata Repository you want to upgrade.
You can upgrade only one OracleAS Metadata Repository at a time. You must select the OracleAS Metadata Repository on your local machine that corresponds to the value of the -oracle_home parameter.
If you are prompted to select a OracleAS Metadata Repository, select the OracleAS Metadata Repository you want to upgrade.
MRUA starts the upgrade process. As each step in the upgrade is executed, information messages appear on the screen to show the progress of the upgrade.
Example 8-1 shows an example of a typical MRUA upgrade session.
|
See Also: Section 4.2.2, "Example Execution Times for the Metadata Repository Upgrade Assistant" for information on how long it takes to upgrade the OracleAS Metadata Repository schemas |
Review the output of the MRUA command; if MRUA reports any errors, see Appendix E, "OracleAS Metadata Repository Upgrade Error Messages".
|
Note: In many cases, MRUA will report that the Oracle Application Server Certificate Authority (OCA) and Oracle Ultra Search component schemas have already been upgraded. This is to be expected because in some cases, the OCA schema is updated automatically by the OracleAS Identity Management and the Oracle Ultra Search schema is updated during the database upgrade. |
Example 8-1 Sample Output from an MRUA Session
mrua.bat -oracle_home D:\oracle10g -oid_host dserv1.acme.com -oid_ssl_port 3130 Executing mrua.pl Running on Windows OracleAS Metadata Repository Upgrade Assistant 10.1.4.0.1 Enter the password for SYS: Enter the password for cn=orcladmin: Upgrading the OracleAS Metadata Repository to release 10.1.4.0.1Calling upgrade plugin for MRUAComponent upgraded successfully MRUA Calling upgrade plugin for UDDI Component upgraded successfully UDDI Calling upgrade plugin for WCS Component upgraded successfully WCS Calling upgrade plugin for WIRELESS Component upgraded successfully WIRELESS Calling upgrade plugin for PORTAL Component upgraded successfully PORTAL Calling upgrade plugin for DISCOVERER Component upgraded successfully DISCOVERER Calling upgrade plugin for B2B Component upgraded successfully B2B Calling upgrade plugin for BAM Component upgraded successfully BAM Calling upgrade plugin for MRC Component upgraded successfully MRC SUCCESS: All OracleAS plug-ins report successful upgrade Finished mrua.pl
Besides the MRUA log files, you can optionally query the database to verify the success of the OracleAS Metadata Repository upgrade. You should also be aware of what component schema versions to expect in the OracleAS Metadata Repository after a successful upgrade.
For more information, refer to the following topics:
Using SQL to Verify the Status of Each Component Schema After Running MRUA
About Component Schema Version Numbers After Upgrading to 10g (10.1.4.0.1)
To use a SQL command to see the current status of each component schema in the repository that is upgraded by MRUA:
Connect to the OracleAS Metadata Repository database.
For example:
METADATA_REPOSITORY_ORACLE_HOME\bin\sqlplus "connect / as sysdba"
When prompted, enter the SYS password.
Enter the following SQL command to verify the status of the component schemas:
SELECT comp_id,version,status FROM APP_REGISTRY;
Refer to the following example and tables for an explanation of the output of the query:
Example 8-2 shows an example of the output displayed from the component schema SQL query.
Table 8-2 describes the possible values in the COMP_ID column of the SQL query results.
Table 8-3 describes the possible values in the STATUS column of the SQL query results.
Example 8-2 Sample Output of the Component Schema SQL Query
SQL> SELECT comp_id, version, status FROM app_registry; COMP_ID VERSION STATUS ------------------------------ ------------------------------ ----------- WIRELESS 10.1.2.0.2 VALID PORTAL 10.1.2.0.2 VALID SSO 10.1.4.0.1 VALID WCS 10.1.2.0.2 VALID DISCOVERER 10.1.2.0.2 VALID OID 10.1.4.0.1 VALID MRUA 10.1.4.0.1 VALID B2B 10.1.2.0.2 VALID UDDI 10.1.2.0.2 VALID BAM 10.1.2.0.2 VALID MRC 10.1.2.0.2 VALID 11 rows selected.
|
Note: The versions shown in the VERSION column will vary somewhat, depending upon the starting point for the 10g (10.1.4.0.1) upgrade.For more information, see Section 8.3.2, "About Component Schema Version Numbers After Upgrading to 10g (10.1.4.0.1)". |
Table 8-2 Component IDs in the OracleAS Metadata Repository
| Component ID | Description |
|---|---|
|
Oracle Application Server Wireless |
|
|
Oracle Application Server Portal |
|
|
Oracle Application Server Web Clipping |
|
|
Oracle Application Server Business Intelligence Discoverer |
|
|
Oracle Application Server Metadata Repository Upgrade Assistant |
|
|
Oracle Application Server Integration B2B |
|
|
Oracle Application Server UDDI Registry |
|
|
Oracle Application Server Metadata Repository Container |
|
|
BAM |
Oracle BPEL Process Analytics |
Table 8-3 Component Status Indicators in the OracleAS Metadata Repository
| Status | Description |
|---|---|
|
LOADING |
MRUA has begun creating the component database objects, but not all the component objects are created and loaded into the database. |
|
LOADED |
MRUA has created all the component database objects and loaded them into the database. MRUA can now begin upgrading the component schemas. |
|
UPGRADING |
MRUA has begun upgrading the schemas for this component, but the upgrade is not complete. |
|
UPGRADED |
MRUA has finished upgrading the schemas for this component. |
|
VALID |
The component schemas have been upgraded and are valid. This is the expected status after a successful upgrade to Oracle Application Server 10g (10.1.4.0.1). |
|
INVALID |
The component schemas have been upgraded, but the database component schemas are invalid. This state can be caused by a non-recoverable error or invalid data. See Appendix E, "OracleAS Metadata Repository Upgrade Error Messages" for information. |
The OracleAS Metadata Repository contains schemas for all the Oracle Application Server components. However, depending upon the starting point for your upgrade, only a subset of those component schemas must be updated by MRUA for Oracle Identity Management 10g (10.1.4.0.1).
Other schemas, such as the OracleAS Identity Management schemas, are upgraded during the OracleAS Identity Management upgrade procedure in Chapter 7, "Using Oracle Universal Installer to Upgrade Oracle Identity Management". Still others do not require any upgrade from previous versions, depending upon your upgrade starting point.
As a result, even after running MRUA, some schemas in the OracleAS Metadata Repository remain at 10.1.2.0.2 and others are upgraded to 10.1.4.0.0.
For example, if you previously upgraded your 10g Release 2 (10.1.2) environment to OracleAS Portal 10g Release 2 (10.1.4), then the PORTAL schema will already be listed as 10.1.4.0.0.
On the other hand, if you have not previously upgraded to OracleAS Portal 10g Release 2 (10.1.4), the PORTAL schema will remain at 10g Release 2 (10.1.2.0.2), unless you later upgrade to OracleAS Portal 10g Release 2 (10.1.4).
