One of the following Oracle Application Server 10g Release 2 (10.1.2) installation types:

Portal and Wireless

Business Intelligence and Forms

Forms and Reports Services

Oracle Application Server Portal 10g Release 2 (10.1.4)

Note that the procedures in this guide were tested against the latest 10g Release 2 (10.1.2) patch set. As a result, Oracle recommends that you upgrade your 10g Release 2 (10.1.2) environment to the latest patch set before starting this upgrade procedure.

This restriction is most important for Oracle Portal users. Specifically, if you are using Oracle Portal 10g Release 2 (10.1.2.0.1) Standard Edition One, you must upgrade to Oracle Portal 10g Release 2 (10.1.2.3) before you can upgrade the Oracle Portal schema to Oracle Portal 11g.

For the most up-to-date information about available Oracle Application Server 10g patch sets, refer to My Oracle Support (formerly OracleMetaLink):

http://support.oracle.com

Note:

If you are currently running Oracle Fusion Middleware 11g, refer to the Oracle Fusion Middleware Patching Guide, which provides information about applying the latest Oracle Fusion Middleware patches.

This guide, as well as the other upgrade guides available in the Oracle Fusion Middleware 11g documentation library, provide instructions for upgrading from Oracle Application Server 10g to the latest Oracle Fusion Middleware 11g release.

Before you begin the upgrade process, consider whether you want to install the Oracle Portal, Forms, Reports, and Discoverer software in a single Oracle instance or in separate Oracle instances.

In Oracle Fusion Middleware 11g, you can create multiple Oracle instances from a single Oracle Portal, Forms, Reports, and Discoverer Oracle home. For example, you can install a single Oracle home and then run the Oracle Portal, Forms, Reports, and Discoverer installation and configuration tool multiple times to configure multiple Oracle instances.

For another example, you can configure Oracle Portal in one Oracle instance and Oracle Reports and Oracle Forms Services in another Oracle instance.

Note, however, that you must ensure that the destination Oracle instance has only a single instance of each component configured. For example, if the Oracle instance has two Oracle HTTP Server instances configured, only one of the Oracle HTTP Server instances will be upgraded.

If you are upgrading Oracle Portal or Oracle BI Discoverer, then you must ensure that the database that contains the Oracle Portal and Oracle BI Discoverer schemas is supported by Oracle Fusion Middleware 11g.

3.4 Task 4: Use the Repository Creation Utility to Install the Oracle BI Discoverer Schema in the Database

As with Oracle BI Discoverer 10g, Oracle BI Discoverer 11g can be installed as a standalone product or associated with a database schema and Oracle Internet Directory instance.

For more information about the Oracle BI Discoverer 11g standalone configuration, see "About Oracle BI Discoverer installations" in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

When you installed Oracle BI Discoverer 10g, if you associated it with an Oracle Infrastructure 10g (database schema), then you must use the Repository Creation Utility to create the Oracle BI Discoverer 11g schema.

Before performing any installation you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the products you are installing.

Specifically, Oracle BI Discoverer has some specific database requirements that must be met before you install the Oracle BI Discoverer schema.

When you are upgrading Oracle Portal, Forms, Reports, and Discoverer, there is no need to install all the Oracle Fusion Middleware schemas. Instead, you can install only the schemas required for the Oracle Portal, Forms, Reports, and Discoverer upgrade.

Figure 3-1 shows the options available in the Repository Creation Utility when you are prompted to select the schemas to install. Specifically, note the following when this screen appears:

The only required schema for an Oracle Portal, Forms, Reports, and Discoverer upgrade is the Discoverer schema. This schema is required only if you associated Oracle BI Discoverer 10g with an Oracle Infrastructure 10g (database schema).

This schema is required at this point in the upgrade process because, unlike the Oracle Portal schema upgrade, the Discoverer schema is upgraded "out-of-place." This means that the Upgrade Assistant copies data from the Oracle Application Server 10g Discoverer schema to the new 11g Discoverer schema. As a result, you must install the Oracle BI Discoverer 11g schema; otherwise, you will not be able to install Oracle Business Intelligence Discoverer 11g or upgrade your 10g Discoverer schema.

Do not select the Portal schema. When you later run the OracleAS Upgrade Assistant, your existing Oracle Application Server 10g Portal schema will be upgraded "in-place" to 11g; as a result, there is no need to install a new Oracle Portal 11g schema.

3.4.4 Providing a Password for the Oracle BI Discoverer 11g Schema

After you select the Oracle BI Discoverer schema, the Repository Creation Utility prompts you to provide a password for the schema. You must provide a password for each schema you are installing in the database; otherwise, you will not be able to install the schemas.

Note that you will need to know the Oracle BI Discoverer schema passwords later, when you are prompted to connect to the database during the Oracle Portal, Forms, Reports, and Discoverer installation procedure.

However, understand that after you install Oracle Portal 11g against the Oracle Portal 10g schema and upgrade the middle tier, you can use Oracle Portal 11g in only a limited capacity. Oracle Portal 11g will be operational, but you will not be able to take advantage of any Oracle Portal 11g features until you subsequently run the Upgrade Assistant and upgrade the Oracle Portal 10g schema to 11g.

Oracle Fusion Middleware 11g includes a new version of the Oracle Web Agent (OWA) packages. Existing packages will be updated to the new version the first time either an Oracle Portal 11g repository is installed or when an existing Portal repository is upgraded to 11g.

When the OWA update takes place, packages from existing Portal schemas that reside in the same database will become invalid. The OWA update ends with an attempt to revalidate all invalid packages in all Portal schemas in the existing database instance.

The OWA update may fail if there are any sessions or jobs active in any of the existing Portal schemas. For this reason, a warning will be issued during the install or upgrade if the OWA update is necessary and if it will cause potential problems in existing Portal schemas.

For the seamless completion of the OWA update in cases where there are existing Portal schemas in the target database, make sure you perform the following steps before installing or upgrading the Oracle Portal repository:

Shut down all middle tiers associated with any of the existing Oracle Portal repositories in the target database.

Stop all jobs and sessions in those same Oracle Portal repositories.

3.5.3 Task 5c: Install the Oracle Fusion Middleware 11g Software

Before you upgrade to Oracle Fusion Middleware 11g, you must install and configure an Oracle Fusion Middleware environment that is similar to the topology you set up for Oracle Application Server 10g.

3.5.3.1 About the Oracle Portal, Forms, Reports, and Discoverer Installation and Configuration Tool

The Oracle Portal, Forms, Reports, and Discoverer installer functions as an installation and configuration tool. It allows you optionally to separate the installation and configuration tasks. In other words, you can choose to install the software on disk into an Oracle home and configure the components later.

However, for the purposes of this upgrade procedure, and in order to ensure you are installing and configuring the latest Oracle Fusion Middleware 11g software, you must perform a software-only install, then apply the latest Oracle Fusion Middleware patch set, and then start the tool a second time to configure the Oracle Portal, Forms, Reports, and Discoverer software.

After you install the Oracle WebLogic Server software, create the Middleware home, and install the latest Oracle Fusion Middleware software, you can then configure the Oracle Portal, Forms, Reports, and Discoverer components.

3.5.4.3 Specifying the DISCOVERER Schema Name and Password

If you are configuring Oracle BI Discoverer in preparation for an upgrade from Oracle BI Discoverer 10g, then the installer prompts you for the name and password of the Oracle Fusion Middleware 11g DISCOVERER schema (Figure 3-3).

For example, on a Linux system, if your Oracle Internet Directory instance is on host1, the port is 13060, the database name is myDB, and the cn=orcladmin password is myPassword1, then you would use this command:

The options available in the Upgrade Assistant are specific to the Oracle home from which it started. For example, when you start Upgrade Assistant from an Oracle Portal, Forms, Reports, and Discoverer Oracle home, the options shown on the Specify Operation screen are the valid options for an Oracle Portal, Forms, Reports, and Discoverer Oracle home.

If the Oracle home you want to upgrade does not appear in the drop-down lists, see Section B.1.2.1, "Source Oracle Home Not Listed by the Upgrade Assistant" in the Oracle Fusion Middleware Upgrade Planning Guide.

Specify Destination Instance

Enter the complete path to the 11g Oracle instance, or click Browse to locate the instance directory.

Stop source components before upgrade: By default, this check box is selected and all the components in the Source Oracle home will be stopped before the upgrade process begins. Stopping the source components is necessary to avoid any port conflicts when you select the Use source Oracle home ports in destination option.

Start destination components after successful upgrade: If you want the Upgrade Assistant to automatically start the components in the destination Oracle home after a successful upgrade is complete. If you do not select this option, then you will have to manually start the destination instance after the upgrade. Note that this option works only if the upgrade is successful.

Click Help to display more information about the upgrade options on this screen.

3.6.2.2 Important Notes When Using the Source Oracle Home Ports in the Destination Oracle Instance

When you select the Use Source Oracle home ports in destination option in the Oracle Fusion Middleware Upgrade Assistant, note the following.

General Information and Restrictions

If you select this option, then you will not be able to run both the 10g and 11g middle tiers at the same time; otherwise, port conflicts will occur.

If you are upgrading to multiple instances of a particular Oracle Fusion Middleware 11g component, you can select this option only once for each component that you upgrade on a host.

For example, suppose you upgrade Oracle HTTP Server in one Oracle instance on MYHOST1.

If you use the option again while upgrading another Oracle HTTP Server instance in another Oracle instance on MYHOST1, then the same listening ports are assigned to the second Oracle HTTP Server instance. Two instances of Oracle HTTP Server on the same host cannot use the same listening ports.

Component-Specific Information and Restrictions

When you use this option to upgrade an Oracle Portal middle tier, the option is enabled and you cannot disable it. As a result, you might end up with extra partner applications displayed on the Oracle Single Sign-On Administration page in Oracle Portal 11g.

If you are upgrading Oracle Reports and you select this option, then Fusion Middleware Control may not be able to gather performance metrics about the Oracle Reports instance. This is because Oracle Enterprise Manager Fusion Middleware Control is using the new Oracle HTTP Server 11g port and not the Oracle HTTP Server 10g port to communicate with Oracle Reports.

To address this issue, modify the Agent-Monitored Target properties for the Oracle Reports component in Fusion Middleware Control. Change the following properties to reflect the 10g Oracle HTTP Server port information:

The HTTP Port property

The port identified in the Servlet URL property

The Server property for the WLS_REPORTS Java EE application. You must change this property because, during upgrade, the Oracle Reports 11g in-process server is renamed to use the same name as the 10g in-process server.

If you are using Oracle Single Sign-On, and you do not select this option (in other words, if you use a different set of port numbers than those used in Oracle Application Server 10g), then consider the following:

You will likely have to re-register your components (such as Oracle Business Intelligence Discoverer) with Oracle Single Sign-On.

For more information, see "Configuring and Administering Partner Applications" in the Oracle Application Server Single Sign-On Administrator's Guide, which is available in the Oracle Application Server 10g (10.1.4) documentation library on the Oracle Technology Network (OTN):

Follow the instructions on the screen to upgrade the Oracle BI Discoverer schema.

Click Help for information about the options available on each screen.

3.6.4 Task 6d: Upgrade the Oracle Portal Schema

If you are upgrading Oracle Portal, then use the following sections for information on upgrading the Oracle Portal schema. You must perform these steps after upgrading your Oracle Portal, Forms, Reports, and Discoverer middle tiers:

Identifies all invalid objects before the upgrade proceeds. You can use this for troubleshooting purposes; all OracleAS Portal packages must be valid before an upgrade.

Recompiles any invalid non-OracleAS Portal objects and displays warnings if any invalid non-OracleAS Portal objects remain in the database.

Disables the directory provisioning profile, as a result event notifications in the Oracle Internet Directory instance to which the Oracle Portal instance has subscribed. The Upgrade Assistant later re-enables the directory providing profile.

Disables triggers in the portal schema and reenables them at the end of the upgrade.

Disables the Database Management System (DBMS) jobs in the Oracle Portal schema and reenables them at the end of the upgrade.

Drops statistics gathered on all tables in the portal schema. Later in the process, the Upgrade Assistant gathers statistics supported by OracleAS Portal. Later in the process, the Upgrade Assistant creates the jobs for gathering statistics.

Upgrades OWA packages if necessary.

Drops and reloads all Java objects in the Oracle Portal schema. Note that any Java objects that do not belong to OracleAS Portal, but reside in the Oracle Portal must be reinstalled manually after the upgrade.

Drops and reloads all product messages in all languages in the Oracle Portal schema. If any product messages were manually altered before the upgrade, then these changes will have to be manually reapplied.

Upgrades the schema and compiles new OracleAS Portal packages.

Updates the OracleAS Portal release if there are no fatal compilation errors.

Searches for errors and warnings in the upgrade log file and displays a summary of the issues.

3.6.4.2 Checking for Invalid Objects in the Database Where the Oracle Portal 10g Schema Resides

Before you upgrade the schemas in your database, it is good practice to make sure that none of the database objects required by Oracle Fusion Middleware are invalid: