|
Oracle® Application Server Upgrade and Compatibility Guide
10g Release 2 (10.1.2) for UNIX Part No. B14090-02 |
|
 Previous |
 Next |
|
Oracle® Application Server Upgrade and Compatibility Guide
10g Release 2 (10.1.2) for UNIX Part No. B14090-02 |
|
|
Previous |
Next |
This chapter describes basic concepts you should understand before you upgrade from Oracle Application Server Release 2 (9.0.2), Release 2 (9.0.3), or 10g (9.0.4) to Oracle Application Server 10g Release 2 (10.1.2).
This chapter contains the following sections:
Reviewing Your Current Oracle Application Server Installations
About Upgrading to Oracle Business Intelligence 10g (10.1.2)
About Upgrading OracleAS Forms Services and OracleAS Reports Services
Understanding Transitional, Stable, and Unsupported Configurations
The following sections provide some guidelines for analyzing your current Oracle Application Server configurations so you can select the best possible upgrade process:
Oracle Application Server is made up of:
Oracle Application Server middle-tier installations
Oracle Application Server Metadata Repository installations
Oracle Application Server Identity Management installations
You deploy and run your applications on Oracle Application Server middle tiers. The OracleAS Metadata Repository and OracleAS Identity Management installations provide the infrastructure services that are used by the middle tiers. Infrastructure services can be shared by one or more middle tiers.
In most cases, your Oracle Application Server environment consists of multiple middle-tier installations and one or more OracleAS Metadata Repository installations and one OracleAS Identity Management installation. The middle-tier, OracleAS Metadata Repository, and OracleAS Identity Management installations exist in multiple Oracle homes and across multiple hosts.
As a result, when you upgrade to a new version of Oracle Application Server, you must upgrade multiple Oracle homes, including the middle-tier Oracle homes, as well as any Infrastructure Oracle homes you have installed.
Most importantly, the process you use to upgrade your Oracle Application Server installations varies depending on how you installed and configured your OracleAS Infrastructure services. Specifically, the OracleAS Metadata Repository and OracleAS Identity Management can be in a single Oracle home or in separate Oracle homes.
For the purposes of upgrade, the following list describes the typical OracleAS Infrastructure configurations:
Figure 1-1 illustrates a configuration where the OracleAS Metadata Repository and OracleAS Identity Management are in the same Oracle home.
This configuration is the result of selecting the Identity Management and OracleAS Metadata Repository installation type during the Oracle Application Server installation procedure. This configuration was the only OracleAS Infrastructure installation type available for Release 2 (9.0.2) and one of three OracleAS Infrastructure installation types available in Oracle Application Server 10g (9.0.4).
This configuration is referred to as a colocated Infrastructure because both the OracleAS Metadata Repository and OracleAS Identity Management are located in the same Oracle home.
Figure 1-2 illustrates a configuration where the OracleAS Metadata Repository and OracleAS Identity Management are installed in separate Oracle homes.
This configuration is the direct result of installing the OracleAS Metadata Repository installation type in one Oracle home and OracleAS Identity Management in a different Oracle home. This configuration was added as an option to the Oracle Application Server 10g (9.0.4) installation procedure.
This configuration is referred to as a non-colocated Infrastructure because the OracleAS Metadata Repository and the OracleAS Identity Management are not in the same Oracle home.
Figure 1-1 Colocated Infrastructure - OracleAS Metadata Repository and OracleAS Identity Management in the Same Oracle Home -
Figure 1-2 Non-Colocated Infrastructure - OracleAS Metadata Repository and OracleAS Identity Management in Separate Oracle Homes
As you begin the upgrade process, it is important to know how your OracleAS Metadata Repository was installed into your database. Specifically, consider the following to determine the type of OracleAS Metadata Repository database you will be upgrading. Each type of OracleAS Metadata Repository database is upgraded differently:
If you used the Oracle Application Server installation procedure to create a new database for the OracleAS Metadata Repository, you can use Oracle Universal Installer to install Oracle Application Server 10g (10.1.2) and upgrade the database automatically.
This type of OracleAS Metadata Repository database is referred to as a seed database, because the database was created automatically by the Oracle Application Server installation procedure specifically for hosting the OracleAS Metadata Repository.
If you used OracleAS Metadata Repository Creation Assistant to install the OracleAS Metadata Repository in an existing database, you must upgrade the database yourself.
This type of OracleAS Metadata Repository database is referred to as an OracleAS Metadata Repository Creation Assistant database, because you used OracleAS Metadata Repository Creation Assistant to install the repository in an existing database that you installed and configured yourself.
|
Note: This document also describes how to upgrade schemas that are outside of the OracleAS Metadata Repository. These are referred to as schemas in a customer database. For more information, see Section 7.5, "Upgrading Schemas in a Customer Database". |
Oracle Application Server 10g (10.1.2) provides several tools to help you upgrade your Oracle Application Server installations to the latest version. Each tool has a specialized role in upgrading a component or in accomplishing a key step in the upgrade process.
Table 1-1 introduces the Upgrade tools you will use to upgrade your Oracle Application Server installations.
Table 1-1 Summary of the Oracle Application Server Upgrade Tools
| Upgrade Tool | Description |
|---|---|
| OracleAS Upgrade Assistant | Use the OracleAS Upgrade Assistant to upgrade your middle tier installations.
The OracleAS Upgrade Assistant is installed with every middle tier installation. After you install a new middle tier Oracle home, you can use the OracleAS Upgrade Assistant in the new Oracle home to upgrade your data and configuration files from the original, source Oracle home. |
| Oracle Universal Installer | Oracle Universal Installer is the application you use to install Oracle Application Server, as well as most other Oracle software products.
When you install an Oracle Application Server 10g (10.1.2) Infrastructure component, the installation procedure checks to see if you have installed a previous version of the OracleAS Infrastructure. If a previous version is found, Oracle Universal Installer prompts you to upgrade the OracleAS Infrastructure installation |
| Metadata Repository Upgrade Assistant (MRUA) | MRUA is the tool you use to upgrade the Oracle Application Server component schemas in the OracleAS Metadata Repository, except the OracleAS Identity Management schemas.
MRUA is distributed on the separate OracleAS Metadata Repository Upgrade Assistant and Utilities CD–ROM, which is part of the Oracle Application Server 10g (10.1.2) CD Pack. You run MRUA directly from the OracleAS Metadata Repository Upgrade Assistant and Utilities CD–ROM. |
| Oracle Application Server Backup and Recovery Tool or other backup utilities | For middle tiers and seed databases, you can use the Oracle Application Server Backup and Recovery Tool to perform backups. The Backup and Recovery Tool is described in the Oracle Application Server Administrator's Guide.
For OracleAS Metadata Repository Creation Assistant databases, see the Oracle Database documentation for the platform and version of the database that hosts your OracleAS Metadata Repository. For example, if you are using a Oracle9i (9.0.1.3) database, see Oracle9i Backup and Recovery Concepts in the Oracle9i Documentation Library, which is available on the Oracle Technology Network (OTN): http://www.oracle.com/technology/documentation/ |
The following sections describe the basic rules you must follow as you determine a plan for upgrading each of your Oracle Application Server components:
Your ultimate goal should be to upgrade all of your Oracle Application Server installations to the same version—in this case, Oracle Application Server 10g (10.1.2). Running all your Oracle Application Server instances at the same version level is not mandatory; however, doing so will make it easier to manage, troubleshoot, and maintain your J2EE applications and your Oracle Application Server components.
If you choose to maintain previous versions of the Oracle Application Server, you must consider which combinations of versions are supported.
As you begin the process of upgrading your Oracle Application Server environment to 10g (10.1.2), you must upgrade your application server instances in the proper order. Specifically, you must start by upgrading either your middle tier installations or your OracleAS Identity Management installation. You cannot upgrade the OracleAS Metadata Repository until the middle tiers that depend upon the repository have been upgraded first.
If you upgrade your OracleAS Metadata Repository first, you will not be able to use your middle tier installations, which depend upon a compatible OracleAS Metadata Repository. In other words, your OracleAS Metadata Repository cannot be a higher version then your middle tier installations.
The following sections describe the Upgrade process for three typical middle tier and OracleAS Infrastructure configurations:
Upgrading Multiple Middle Tiers and a Colocated Infrastructure
Upgrading Multiple Middle Tiers and a 10g (9.0.4) Non-Colocated Infrastructure
Table 1-2 provides an overview of the tools and procedure you use to upgrade a J2EE and Web Cache installation that is not using any OracleAS Infrastructure services.
Table 1-2 Tools and Process for Upgrading a Standalone J2EE and Web Cache Oracle Home
| Task | Task Description | Upgrade Tool |
|---|---|---|
| 1 | Back up the middle tier Oracle home before beginning the upgrade procedures. | Oracle Application Server Backup and Recovery Tool or other backup utilities
For more information, see Section 3.1, "Backup Strategies Before Upgrade". |
| 2 | Install a new Oracle Application Server 10g (10.1.2) J2EE and Web Cache installation in a new Oracle home on the same host. | Oracle Universal Installer
|
| 3 | Upgrade configuration data and applications from the Release 2 (9.0.2), Release 2 (9.0.3), or 10g (9.0.4) source Oracle home to the 10g (10.1.2) destination Oracle home. | OracleAS Upgrade Assistant
|
| 4 | Optionally, decommission and deinstall the source Oracle home. | Oracle Universal Installer
|
This section describes the high-level steps required to upgrade multiple middle tier Oracle homes that use a single Oracle home for the OracleAS Metadata Repository and OracleAS Identity Management.
You can start the upgrade process by upgrading the middle tiers first, or, if you are upgrading from 10g (9.0.4), you can start by upgrading OracleAS Identity Management first.
For more information, see the following sections:
Starting with the Middle Tiers and a Colocated Infrastructure
Starting with 10g (9.0.4) OracleAS Identity Management in a Colocated Infrastructure
Table 1-3 provides an overview of the steps you must perform when upgrading your middle tiers and then your OracleAS Metadata Repository and OracleAS Identity Management.
Table 1-3 Tools and Process for Upgrading a Colocated Infrastructure - Middle Tiers First
| Step | Step Description | Upgrade Tools |
|---|---|---|
| 1 | Back up the middle tier Oracle homes and the colocated Infrastructure Oracle home. | Oracle Application Server Backup and Recovery Tool or other backup utilities
For more information, see Section 3.1, "Backup Strategies Before Upgrade". |
| 2 | Upgrade Middle Tiers | See Section 1.4.1, "Upgrading a Standalone Middle Tier". |
| 3 | Upgrade the OracleAS Metadata Repository database and upgrade the OracleAS Identity Management schemas | Oracle Universal Installer
After selecting the installation type, select the option to upgrade the selected OracleAS Metadata Repository and OracleAS Identity Management Oracle home. |
| 4 | Upgrade the OracleAS Metadata Repository Component Schemas | Metadata Repository Upgrade Assistant
|
| 5 | Optionally, decommission and deinstall source Oracle homes | Oracle Universal Installer
|
Table 1-4 provides an overview of the steps you must perform when upgrading your OracleAS Identity Management, and then the middle tiers and the OracleAS Metadata Repository.
Note that this procedure of starting with OracleAS Identity Management is supported only when you are upgrading from 10g (9.0.4).
Table 1-4 Tools and Process for Upgrading a Colocated Infrastructure - OracleAS Identity Management First
| Step | Step Description | Upgrade Tools |
|---|---|---|
| 1 | Back up the middle tier Oracle homes and the colocated Infrastructure Oracle home. | Oracle Application Server Backup and Recovery Tool or other backup utilities
For more information, see Section 3.1, "Backup Strategies Before Upgrade". |
| 2 | Upgrade the OracleAS Metadata Repository database and upgrade the OracleAS Identity Management schemas | Oracle Universal Installer
After selecting the installation type, select the option to upgrade the selected OracleAS Metadata Repository and OracleAS Identity Management Oracle home. |
| 3 | Upgrade Middle Tiers | See Section 1.4.1, "Upgrading a Standalone Middle Tier". |
| 4 | Upgrade the OracleAS Metadata Repository Component Schemas | MRUA
|
| 5 | Optionally, decommission and deinstall source Oracle homes | Oracle Universal Installer
|
This section describes the high-level steps required to upgrade multiple middle tier Oracle homes that use separate Oracle homes for the OracleAS Metadata Repository and OracleAS Identity Management. Non-colocated infrastructure were introduced in 10g (9.0.4), so this procedure applies only to upgrades from 10g (9.0.4).
You can start the upgrade process by upgrading the middle tiers first, or you can start by upgrading OracleAS Identity Management first.
For more information, see the following sections:
Starting with the Middle Tiers and a 10g (9.0.4) Non-Colocated Infrastructure
Starting with OracleAS Identity Management in a 10g (9.0.4) Non-Colocated Infrastructure
Table 1-5 provides an overview of the steps you must perform when upgrading your middle tiers and then your OracleAS Metadata Repository and OracleAS Identity Management.
Table 1-5 Tools and Process for Upgrading a Non-Colocated Infrastructure - Middle Tiers First
| Step | Step Description | Upgrade Tools |
|---|---|---|
| 1 | Back up the middle tier Oracle homes, the OracleAS Identity Management Oracle home, and the OracleAS Metadata Repository Oracle home, including the OracleAS Metadata Repository database. | Oracle Application Server Backup and Recovery Tool or other backup utilities
For more information, see Section 3.1, "Backup Strategies Before Upgrade". |
| 2 | Upgrade Middle Tiers | See Section 1.4.1, "Upgrading a Standalone Middle Tier". |
| 3 | Upgrade the database in the OracleAS Metadata Repository Oracle home. | Depends upon whether or not the database is a seed database or a OracleAS Metadata Repository Creation Assistant database:
|
| 4 | Upgrade OracleAS Identity Management and the OracleAS Identity Management schemas. | Oracle Universal Installer
After selecting the Identity Management installation type, select the option to upgrade the selected OracleAS Identity Management Oracle home. |
| 5 | Upgrade the OracleAS Metadata Repository Component Schemas | MRUA
|
| 6 | Optionally, decommission and deinstall source Oracle homes | Oracle Universal Installer
|
Table 1-6 provides an overview of the steps you must perform when upgrading your OracleAS Identity Management, and then the middle tiers and the OracleAS Metadata Repository.
Table 1-6 Tools and Process for Upgrading a Non-Colocated Infrastructure - OracleAS Identity Management First
| Step | Step Description | Upgrade Tools |
|---|---|---|
| 1 | Back up the middle tier Oracle homes, the OracleAS Identity Management Oracle home, and the OracleAS Metadata Repository Oracle home, including the OracleAS Metadata Repository database. | Oracle Application Server Backup and Recovery Tool or other backup utilities
For more information, see Section 3.1, "Backup Strategies Before Upgrade". |
| 2 | Upgrade the database in the OracleAS Metadata Repository Oracle home. | Depends upon whether or not the database is a seed database or a OracleAS Metadata Repository Creation Assistant database:
|
| 3 | Upgrade OracleAS Identity Management and the OracleAS Identity Management schemas. | Oracle Universal Installer
After selecting the OracleAS Identity Management installation type, select the option to upgrade the selected OracleAS Identity Management Oracle home. |
| 4 | Upgrade Middle Tiers | See Section 1.4.1, "Upgrading a Standalone Middle Tier". |
| 5 | Upgrade the OracleAS Metadata Repository Component Schemas | MRUA
|
| 6 | Optionally, decommission and deinstall source Oracle homes | Oracle Universal Installer
|
Each time you install or upgrade an instance of Oracle Application Server—regardless of whether you install a middle tier or an OracleAS Infrastructure—you select an installation type. When you upgrade your Oracle Application Server installations, you must be sure to upgrade each installation to a compatible 10g (10.1.2) installation type.
The following sections describe the supported upgrade paths for each of the Release 2 (9.0.2), Release 2 (9.0.3), and 10g (9.0.4) installation types you might have installed. Use this information to select the correct installation type when you are installing Oracle Application Server 10g (10.1.2) in preparation for an upgrade:
The following sections describe the upgrade paths for middle-tier installations:
Upgrading From Release 2 (9.0.2) Middle-Tier Installation Types
Upgrading From Release 2 (9.0.3) Middle-Tier Installation Types
Table 1-7 shows the Release 2 (9.0.2) middle-tier installation types and the corresponding compatible 10g (10.1.2) installation types.
Table 1-7 Compatible 10g (10.1.2) Middle-Tier Installation Types for Release 2 (9.0.2) Upgrades
| Release 2 (9.0.2) Installation Type | Compatible 10g (10.1.2) Installation Types |
|---|---|
| J2EE and Web Cache | J2EE and Web Cache |
| Portal and Wireless | Portal and Wireless |
| Business Intelligence and Forms | Not ApplicableFoot 1 |
| Unified Messaging | Not ApplicableFoot 2 |
Oracle Application Server Release 2 (9.0.3) supported only the J2EE and Web Cache installation type. As a result, you can upgrade Release 2 (9.0.3) Oracle homes to 10g (10.1.2) J2EE and Web Cache installations only.
Table 1-8 shows the 10g (9.0.4) middle-tier installation types and the corresponding compatible 10g (10.1.2) installation types.
Table 1-8 Compatible 10g (10.1.2) Middle-Tier Installation Types for 10g (9.0.4) Upgrades
| 10g (9.0.4) Installation Type | Compatible 10g (10.1.2) Installation Types |
|---|---|
| J2EE and Web Cache | J2EE and Web Cache |
| Portal and Wireless | Portal and Wireless |
| Business Intelligence and Forms | Not ApplicableFoot 1 |
| Forms and Reports Services | Not ApplicableFootref 1 |
As described in the following sections, the OracleAS Infrastructure installation types available for Oracle Application Server Release 2 (9.0.2) were different than those available for Oracle Application Server 10g (9.0.4):
Upgrading From Release 2 (9.0.2) Infrastructure Installation Types
Upgrading From 10g (9.0.4) Infrastructure Installation Types
The Release 2 (9.0.2) installation procedure offered only one OracleAS Infrastructure installation type, which installed the OracleAS Metadata Repository and the OracleAS Identity Management components (Oracle Internet Directory and OracleAS Single Sign-On).
As a result, when you use Oracle Universal Installer and the 10g (10.1.2) installation procedure to upgrade your Release 2 (9.0.2) Infrastructure Oracle home, you must select the OracleAS Identity Management and OracleAS Metadata Repository installation type.
Oracle Universal Installer will then perform the necessary procedures to install the new 10g (10.1.2) Infrastructure, upgrade your OracleAS Infrastructure database, and the OracleAS Infrastructure components.
You can then use the Metadata Repository Upgrade Assistant to upgrade the schemas in the upgraded OracleAS Metadata Repository database.
|
Note: After you run Oracle Universal Installer to upgrade the Release 2 (9.0.2) OracleAS Metadata Repository database and the Release 2 (9.0.2) OracleAS Identity Management components, you will be temporarily in an unsupported configuration. As a result, you must continue with the upgrade and run the Metadata Repository Upgrade Assistant before your upgraded Oracle Application Server environment is functional.For more information, see Section 1.8, "Understanding Transitional, Stable, and Unsupported Configurations". |
Table 1-9 shows the 10g (9.0.4) infrastructure installation types and the corresponding compatible 10g (10.1.2) installation types.
Selecting a compatible 10g (10.1.2) installation type will cause Oracle Universal Installer to identify the existing 10g (9.0.4) installation and provide you with the option of upgrading the existing Oracle home to the new 10g (10.1.2) Oracle home.
Table 1-9 Compatible 10g (10.1.2) Infrastructure Installation Types for 10g (9.0.4) Upgrades
You can expand to a larger middle tier installation type. For example, you can expand a J2EE and Web Cache middle tier to a Portal and Wireless middle tier.
However, the act of expanding your installation type must be treated as a separate task from upgrading to a new version of Oracle Application Server.
Specifically, to expand a middle tier in conjunction with an upgrade:
Upgrade the existing middle tier to a compatible 10g (10.1.2) installation type.
Expand the upgraded middle tier.
|
See Also: Oracle Application Server Installation Guide for instructions on expanding a middle tier installation |
Oracle Application Server 10g (10.1.2) does not include the Business Intelligence and Forms installation type.
Some components of the Business Intelligence and Forms installation type, such as OracleBI Discoverer, are available for 10g (10.1.2), as part of the separately installed Business Intelligence 10g (10.1.2) installation kit, which is available on CD-ROM and on the Oracle Technology Network.
However, you cannot upgrade from any 10g (9.0.4) installation type to Business Intelligence 10g (10.1.2). Instead, you must wait until a compatible installation type is available after the initial 10g (10.1.2) release.
|
See Also: The Business Intelligence documentation available on the Oracle Technology Network:http://www.oracle.com/technology/documentation/bi.html |
OracleAS Forms Services and OracleAS Reports Services are not available as part of the initial 10g (10.1.2) release. As a result, you cannot upgrade these components to 10g (10.1.2).
Specifically, Oracle Application Server 10g (10.1.2) does not include the Business Intelligence and Forms installation type or the separately installed Forms and Reports Services installation type.
As you begin to upgrade your Oracle Application Server installations, you will temporarily transition to configurations that consist of multiple versions of the Oracle Application Server. For example, at some point during the upgrade of your Oracle Application Server installations:
Your middle tier installations might be running Oracle Application Server 10g (10.1.2) while your OracleAS Metadata Repository is running 10g (9.0.4) and your OracleAS Identity Management installation is running 10g (9.0.4).
Your OracleAS Identity Management installation might be running Oracle Application Server 10g (10.1.2) while your middle tiers and OracleAS Metadata Repository are still running 10g (9.0.4).
Your middle tiers and OracleAS Metadata Repository might be running Oracle Application Server 10g (10.1.2) while your OracleAS Identity Management installation is running Oracle Application Server Release 2 (9.0.2).
During the upgrade process, it is important to understand that each configuration you encounter falls into one of several configuration types. Those configuration types are described in Table 1-10.
Table 1-10 Summary of Transitional, Stable, and Unsupported Upgrade Configurations
| Configuration | Purpose and Expectations | Definition and Examples |
|---|---|---|
| Transitional | Transitional configurations are functional and can be used by your application server clients.
However, transitional configurations are supported only as short-term configurations. Transitional configurations should be maintained only while you are performing the overall upgrade process. |
A configuration is transitional when at least one of the middle tiers has been upgraded and is now running a version of Oracle Application Server that is different than the one used by the OracleAS Metadata Repository.
For example, a typical transitional configuration includes multiple middle tiers that have been upgraded to Oracle Application Server 10g (10.1.2), but the OracleAS Metadata Repository is running Oracle Application Server 10g (9.0.4). |
| Stable | Stable configurations can be maintained in a production environment for a period of time without any serious performance or management issues.
However, your ultimate goal—in order to implement an environment that is easier to manage and to maintain—should be to continue the upgrade process until you have implemented a Final configuration. |
A configuration is stable when the middle tier and OracleAS Metadata Repository are at the same version.
For example, a typical stable configuration might include an OracleAS Identity Management installation that has been upgraded to Oracle Application Server 10g (10.1.2). However, the middle tier instances and the OracleAS Metadata Repository are still running 10g (9.0.4). |
| Unsupported | Unsupported configurations are not expected to be functional. Users cannot connect to the middle tiers; if they can connect, the middle tiers will likely generate errors when connecting to the OracleAS Metadata Repository. | Typically, a configuration is unsupported when the OracleAS Metadata Repository is upgraded before the middle tiers that depend upon it.
For example, in a typical unsupported configuration, the OracleAS Metadata Repository is running Oracle Application Server 10g (10.1.2) and the middle tiers that use the OracleAS Metadata Repository are still running Release 2 (9.0.2), Release 2 (9.0.3), or 10g (9.0.4). |
Figure 1-3 shows the typical upgrade paths you can use to:
Upgrade from Oracle Application Server 10g (9.0.4) using a colocated Infrastructure to a final 10g (10.1.2) configuration
Upgrade from Oracle Application Server 10g (9.0.4) using a non-colocated Infrastructure
Upgrade from Oracle Application Server Release 2 (9.0.2) colocated Infrastructure to a final 10g (10.1.2) configuration
The figure shows how you can encounter transitional, stable, and unsupported configurations during the upgrade process. Your ultimate goal is to upgrade all the Oracle Application Server components so they represent a final configuration where all components are running Oracle Application Server 10g (10.1.2).
|
Note: Figure 1-3 is not meant to show all the possible upgrade paths for a particular configuration. Instead, it shows three common upgrade paths and the interim configurations you will encounter as you upgrade all the Oracle Application Server components that you support. |
Figure 1-3 Typical Stable, Transitional, and Unsupported Configurations When Upgrading to 10g (10.1.2)
Note that the only unsupported configuration shown in Figure 1-3 occurs while upgrading a Release 2 (9.0.2) colocated Infrastructure. This unsupported configuration occurs because Oracle Universal Installer automatically upgrades the database to Oracle Database 10g (10.1.0.3.1).
Because the Release 2 (9.0.2) OracleAS Metadata Repository is not compatible with the Oracle Database 10g (10.1.0.3.1) database, the configuration is unsupported. However, after you use the Metadata Repository Upgrade Assistant to upgrade the OracleAS Metadata Repository and its component schemas to 10g (10.1.2), the resulting configuration is supported and stable.
If you have applications or configuration elements whose upgrade requirements are not addressed by the 10g (10.1.2) installation procedure, OracleAS Upgrade Assistant, or by MRUA, you may use one of the following alternative upgrade paths:
If there are applications deployed in Oracle Application Server Containers for J2EE (OC4J) instances of the "standalone" type—that is, the OC4J that is available for download from Oracle Technology Network in zip format—you must manually redeploy and reconfigure them.
To upgrade a standalone instance of OracleAS Web Cache Release 2 (9.0.2), Release 2 (9.0.3), or 10g (9.0.4) to Oracle Application Server 10g (10.1.2), perform the steps described in Section 7.2, "Upgrading a Standalone OracleAS Web Cache Instance".
To upgrade from Release 1 (1.0.2.2) to 10g (10.1.2), you must first upgrade to Release 2 (9.0.2) or 10g (9.0.4), and then upgrade to 10g (10.1.2).
Follow the instructions in Oracle Application Server 10g Upgrading from Release 1 (1.0.2.2.x) to 10g (9.0.4), which is available on the Oracle Application Server documentation page on the Oracle Technology Network (OTN):
http://www.oracle.com/technology/documentation/appserver10g.html
To upgrade Oracle Business Intelligence Discoverer from Release 1 (1.0.2.2), follow the instructions in the Oracle Application Server Discoverer Configuration Guide in the Oracle Application Server documentation library.
Oracle Application Server Syndication Services is not upgraded as part of the 10g (10.1.2) upgrade process, because that component is not supported by the 10g (10.1.2) release.
The upgrade of applications that use JServ is not discussed in this guide. The material in the section titled "Migrating JServ to OC4J" in Migrating from Oracle9iAS Release 1 (1.0.2.2.x) to Release 2 (9.0.2), in the Oracle9iAS Release 2 (9.0.2) documentation library, may be of some help in adapting such applications to the Oracle Application Server Containers for J2EE servlet environment in Oracle Application Server 10g (10.1.2).
The OracleAS Portal Repository can be upgraded using the instructions in this guide from any 9.0.2.x or 9.0.4.x version.
For instructions on upgrading from other versions, see the PortalCenter upgrades page at:
Before you upgrade to Oracle Application Server 10g (10.1.2), be sure to consider the implications of the upgrade on any third-party software you are using with the Oracle Application Server components.
Specifically, be sure to check with your third-party vendors to be sure the third-party software you are using is certified to work with Oracle Application Server 10g (10.1.2) and its components.
Note, in particular, that Oracle Application Server 10g (10.1.2) will likely require an upgrade of the Oracle database used to host your OracleAS Metadata Repository, and that Oracle Application Server 10g (10.1.2) provides updated versions of many Oracle Application Server components.
