1
Overview of Oracle9iAS Migration

This chapter discusses the Oracle9iAS migration method, migration scope, and considerations for using the previous and current releases together.

Migration Method

The Oracle9iAS Migration Assistant is a tool that migrates primary elements of Oracle HTTP Server, Oracle9iAS Containers for J2EE, and Web Cache from Oracle9iAS Release 1 (1.0.2.2.x) or Oracle9iAS Release 2 (9.0.2) to Oracle9iAS Release 2 (9.0.3). Release 2 (9.0.3) enables you to build and deploy applications that take advantage of J2EE 1.3 features.

By automating much of the migration process, the Oracle9iAS Migration Assistant expedites what can otherwise be a very lengthy process. The Migration Assistant (GUI and command-line versions) is installed automatically with Oracle9iAS Release 2 (9.0.3).

Some configuration elements and applications are not migrated by the Migration Assistant. See Chapter 5, "Using the Oracle9iAS Migration Assistant", in the "Verifying Migration Results" section for a description of the elements not migrated by the Migration Assistant.

Migration Scope

Oracle9iAS Release 2 (9.0.3) contains only Oracle HTTP Server, Oracle9iAS Containers for J2EE, and Web Cache. It will not run Portal, Wireless, or other components from installation types other than J2EE and Web Cache that are available in Oracle9iAS Release 2 (9.0.2).

The Oracle9iAS Migration Assistant will allow you to migrate from any Oracle9iAS Release 2 (9.0.2) installation type, but it issues a warning if you try to use it to migrate from the Portal and Wireless, Business Intelligence and Forms, or Unified Messaging installation types. You can dismiss the warning and continue to migrate, and the Migration Assistant will allow you to select the Oracle HTTP Server, Oracle9iAS Containers for J2EE, and Web Cache components for migration from the Oracle9iAS Release 1 (1.0.2.2.x) or Oracle9iAS Release 2 (9.0.2) installation.

If you have a Release 1 (1.0.2.1.x) installation, you must migrate to Oracle9iAS Release 1 (1.0.2.2.x) before using the Migration Assistant.

See Also: Oracle9i Application Server Migration Guide in the Release 1 (1.0.2.2.x) Oracle9i Application Server documentation library.

Identifying Source and Target Oracle9iAS Installations

The Migration Assistant performs a migration from one Oracle home to another, where Oracle9iAS Release 1 (1.0.2.2.x) or Oracle9iAS Release 2 (9.0.2) is installed in a different Oracle home than Oracle9iAS Release 2 (9.0.3). These Oracle homes are designated as follows:

The location of Oracle9iAS Release 1 (1.0.2.2.x) or Oracle9iAS Release 2 (9.0.2) is called ORACLE_HOME_1, or the source Oracle home.

The location of Oracle9iAS Release 2 (9.0.3) is called ORACLE_HOME_2, or the target Oracle home.

In this guide, the notations ORACLE_HOME_1 and ORACLE_HOME_2 (italics) mean `the full path to the Oracle home'.

The source and target Oracle homes must be on the same computer.

Considerations for Using Oracle9iAS Release 2 (9.0.2) and (9.0.3) Together

The source installation is unaffected by the migration, so the Oracle HTTP Server, Oracle9iAS Containers for J2EE, and Web Cache components on the source installation remain configured exactly as they were before the migration. If you continue to use the Oracle9iAS Release 2 (9.0.2) instance to run Portal and Wireless or Business Intelligence and Forms components, some or all of their Oracle HTTP Server, Oracle9iAS Containers for J2EE, and Web Cache configuration elements may be redundantly applied on two instances on the same computer. Therefore, problems may occur if the (9.0.2) and (9.0.3) instances are run simultaneously.

Also note that you can use Oracle Enterprise Manager to manage only one of the instances. The emctl switch utility is provided for you to choose an Oracle home to manage with Oracle Enterprise Manager. See "Activating Oracle Enterprise Manager" for instructions on how to use emctl switch.