Article : Upgrading Your Oracle Portal, Forms, Reports, and Discoverer Environment

Upgrading Your Oracle Portal, Forms, Reports, and Discoverer Environment

This chapter describes how to upgrade your existing Oracle Application Server 10gRelease 2 (10.1.2) environment to Oracle Portal, Forms, Reports, and Discoverer 11g.

This chapter contains the following sections:

• Task 1: Understand the Starting Points for Oracle Portal, Forms, Reports, and Discoverer Upgrade

• Task 2: Decide Upon an Oracle Portal, Forms, Reports, and Discoverer Topology

• Task 3: If Necessary, Upgrade the Database that Contains the Oracle Portal and Oracle BI Discoverer Schemas

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

• Task 5: Install and Configure Oracle Portal, Forms, Reports, and Discoverer Middle Tiers

• Task 6: Use the Upgrade Assistant to Upgrade the Required Schemas and Middle Tiers

• Task 7: Perform Any Required Post-Upgrade Configuration Tasks

• Task 8: Verify the Oracle Portal, Forms, Reports, and Discoverer Upgrade

3.1Task 1: Understand the Starting Points for Oracle Portal, Forms, Reports, and Discoverer Upgrade

This document provides information about upgrading from:

• One of the following Oracle Application Server 10gRelease 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 10gRelease 2 (10.1.2) patch set. As a result, Oracle recommends that you upgrade your 10gRelease 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 10gRelease 2 (10.1.2.0.1) Standard Edition One, you must upgrade to Oracle Portal 10gRelease 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 10gpatch sets, refer to My Oracle Support (formerly OracleMetaLink):

http://support.oracle.com

Oracle Fusion Middleware Upgrade Planning Guide.About Oracle BI Discoverer installations" in theOracle 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 11gschema.

You install the Oracle BI Discoverer schema into the database that you identified and prepared inTask 3: If Necessary, Upgrade the Database that Contains the Oracle Portal and Oracle BI Discoverer Schemas.

Note:

There is no need to install the Oracle Portal 11gschema in the database.

For more information, seeSection 3.4.3, "Selecting the Oracle BI Discoverer Schema In Preparation for an Oracle Portal, Forms, Reports, and Discoverer Upgrade"

For more information about installing the Oracle BI Discoverer schema, refer to the following sections:

• Verifying that the Database Meets the Minimum Requirements for Oracle BI Discoverer 11g

• Running the Repository Creation Utility in Preparation for Upgrading Oracle BI Discoverer

• Selecting the Oracle BI Discoverer Schema In Preparation for an Oracle Portal, Forms, Reports, and Discoverer Upgrade

• Providing a Password for the Oracle BI Discoverer 11gSchema

Review System Requirements and Specifications" in theOracle Fusion Middleware Installation Planning Guide.

3.4.2Running the Repository Creation Utility in Preparation for Upgrading Oracle BI Discoverer

To run the Repository Creation Utility to install the Oracle BI Discoverer schema in the database:

1. Mount the Oracle Fusion Middleware Metadata Repository Creation Utility CD–ROM.

   Alternatively, you can download and unpack the Repository Creation Utility installation kit from the Oracle Technology Network (OTN):

   http://www.oracle.com/technology/
   

   In either case, the root directory of the CD-ROM or the directory where you unpacked the downloaded kit is referred to as the RCU_HOME directory.

2. Start the Repository Creation Utility:

   On UNIX systems:

   RCU_HOME/bin/rcu
   

   On Windows systems:

   RCU_HOME\bin\rcu.bat
   

3. Follow the instructions on the Repository Creation Utility screens to connect to the database and create the required schemas.

   Refer to the following resources for more information:

   • For more information about which schemas to select when running the Repository Creation Utility, refer toSection 3.4.3, "Selecting the Oracle BI Discoverer Schema In Preparation for an Oracle Portal, Forms, Reports, and Discoverer Upgrade".

   • For more information about providing passwords for the schemas you select, seeSection 3.4.4, "Providing a Password for the Oracle BI Discoverer 11gSchema".

   • For more detailed information about using the Repository Creation Utility, refer to theOracle Fusion Middleware Repository Creation Utility User's Guide.

Figure 3-1shows 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 theDiscovererschema. This schema is required only if you associated Oracle BI Discoverer 10gwith 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 10gDiscoverer schema to the new 11gDiscoverer schema. As a result, you must install the Oracle BI Discoverer 11gschema; otherwise, you will not be able to install Oracle Business Intelligence Discoverer 11gor upgrade your 10gDiscoverer schema.

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

• No schemas are required for Oracle Forms Services or Oracle Reports.

Description of "Figure 3-1 Selecting the Required Schemas for an Oracle Portal, Forms, Reports, and Discoverer Upgrade"

Figure 3-2shows the Repository Creation Utility Schema Passwords page, which appears after you have selected component schemas for an Oracle Portal, Forms, Reports, and Discoverer upgrade.

You can enter a different password for each schema, or use the same password for all the schemas.

Description of "Figure 3-2 Repository Creation Utility Schema Passwords Page"

Task 5a: Understand the Implications of Installing Oracle Portal Against the Oracle Application Server 10gPORTAL schema

Task 5b: Consider the Impact of the Oracle Portal Upgrade on Oracle Web Agent (OWA) Packages

Task 5c: Install the Oracle Fusion Middleware 11gSoftware

Task 5d: Configure Oracle Portal, Forms, Reports, and Discoverer in Preparation for Upgrade

Step 5e: Verify the Installation and Configuration of Your Oracle Portal, Forms, Reports, and Discoverer 11gEnvironment

Section 3.6.2, "Task 6b: Upgrade the Oracle Portal, Forms, Reports, and Discoverer Middle Tiers", and upgrade the PORTAL schema, as described inSection 3.6.4, "Task 6d: Upgrade the Oracle Portal Schema".About the Oracle Portal, Forms, Reports, and Discoverer Installation and Configuration Tool

Related Documentation for Installing and Configuring Oracle Portal, Forms, Reports, and Discoverer 11g

Summary of the Oracle Identity Management 11gInstallation Steps

Obtaining the Latest Oracle WebLogic Server and Oracle Fusion Middleware 11gSoftware" in theOracle Fusion Middleware Upgrade Planning Guide.Oracle Fusion Middleware Installation Planning Guide

TheOracle Fusion Middleware Quick Installation Guide for Oracle Forms and Reports

TheOracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer

Table 3-1provides a high-level summary of the main steps you must perform when installing and configuring the Oracle Portal, Forms, Reports, and Discoverer middle tiers.

Note that the procedures described in this section assume you have downloaded the latest version of Oracle WebLogic Server and Oracle Fusion Middleware 11g. For more information, refer to "Obtaining the Latest Oracle WebLogic Server and Oracle Fusion Middleware 11gSoftware" in theOracle Fusion Middleware Upgrade Planning Guide.

Running the Installation Program in Graphical Mode"

Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server

2

Install the Oracle Portal, Forms, Reports, and Discoverer software on disk and create the Oracle Portal, Forms, Reports, and Discoverer Oracle home

"Starting the Installer"

"Installation Instructions"

Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer

3

Apply the latest Oracle Fusion Middleware patch set

"Applying the Latest Fusion Middleware Patch Set with the Patch Set Installers"

Oracle Fusion Middleware Patching Guide

Running the Oracle Portal, Forms, Reports, and Discoverer Configuration Tool

Specifying the PORTAL Schema Name and Password

Specifying the DISCOVERER Schema Name and Password

Locating the Oracle Portal 10gSchema Password in the Oracle Internet Directory

3.5.4.1Running the Oracle Portal, Forms, Reports, and Discoverer Configuration Tool

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.

To configure Oracle Portal, Forms, Reports, and Discoverer:

1. Start the Oracle Portal, Forms, Reports, and Discoverer 11gconfiguration:

   On UNIX systems:

   > IDM_ORACLE_HOME/common/bin/config.sh
   

   On Windows systems:

   IDM_ORACLE_HOME\common\bin\config.bat
   

2. Follow the instructions on the screen to configure one or more of the Oracle Portal, Forms, Reports, and Discoverer components.

   As you proceed through the installation screens, note the following:

   • If you are upgrading to Oracle Portal 11g, then seeSection 3.5.4.2, "Specifying the PORTAL Schema Name and Password".

   • If you are upgrading Oracle Business Intelligence Discoverer, then seeSection 3.5.4.3, "Specifying the DISCOVERER Schema Name and Password".

   For other information about installing and configuring Oracle Portal, Forms, Reports, and Discoverer, refer to the following:

   • For help on the options available on each screen, clickHelp.

   • For more detailed information about the configuration options, "Configuring Your Components" in theOracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer..

Figure 3-3).

It is important that you enter the name and password of the Oracle Application Server 10gPORTAL schema, as follows:

• In theSchema Namecolumn, enterPORTAL.

• In theSchema Passwordcolumn, enter the password for the 10gPORTAL schema. For more information, seeSection 3.5.4.4, "Locating the Oracle Portal 10gSchema Password in the Oracle Internet Directory"

Description of "Figure 3-3 Specify Schema Screen From an Oracle Portal, Forms, Reports, and Discoverer Installation"

Figure 3-3).

It is important that you enter the name and password of the Oracle Fusion Middleware 11gDISCOVERER schema that you created using the Repository Creation Utility inSection 3.4, "Task 4: Use the Repository Creation Utility to Install the Oracle BI Discoverer Schema in the Database".

Enter the following information about the DISCOVERER schema on the Specify Schema screen:

• In theSchema Namecolumn, enter the schema name and prefix that you used when you created the schema with Repository Creation Utility. For example,DEV_DISCOVERER.

• In theSchema Passwordcolumn, enter the password that you provided for the DISCOVERER schema in Repository Creation Utility.

3.5.4.4Locating the Oracle Portal 10gSchema Password in the Oracle Internet Directory

You can locate and view the password for an Oracle Application Server 10gcomponent schema by using the followingldapsearchcommand on the Oracle Internet Directory.

If your password is in an Oracle Internet Directory instance, use this command syntax:

ORACLE_HOME/bin/ldapsearch -p oid_port -h oid_hostname -D "cn=orcladmin"
-w orcladmin_password -b "orclresourcename=schema_name,
orclreferencename=metadata_rep_global_db_name, cn=ias infrastructure databases,
cn=ias, cn=products, cn=oraclecontext" -s base "objectclass=*"
orclpasswordattribute

For example, on a Linux system, if your Oracle Internet Directory instance is onhost1, the port is13060, the database name ismyDB, and the cn=orcladmin password ismyPassword1, then you would use this command:

$ORACLE_HOME/bin/ldapsearch -p 13060 -h host1.example.com -D "cn=orcladmin"
-w myPassword1 -b "orclresourcename=PORTAL,
orclreferencename=myDB.example.com, cn=ias infrastructure databases,
cn=ias, cn=products, cn=oraclecontext" -s base "objectclass=*"
orclpasswordattribute

Verifying the Installation" in theOracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer.Using the Upgrade Assistant Command-Line Interface" in theOracle Fusion Middleware Upgrade Planning Guide.

The following sections provide more information:

• Task 6a: Start the Upgrade Assistant for an Oracle Portal, Forms, Reports, and Discoverer Upgrade

• Task 6b: Upgrade the Oracle Portal, Forms, Reports, and Discoverer Middle Tiers

• Task 6c: Upgrade the Oracle BI Discoverer Schema

• Task 6d: Upgrade the Oracle Portal Schema

3.6.1Task 6a: Start the Upgrade Assistant for an Oracle Portal, Forms, Reports, and Discoverer Upgrade

To start the Upgrade Assistant using the graphical user interface:

1. Change directory to theORACLE_HOME/bindirectory of the Oracle Fusion Middleware installation.

2. Enter the following command to start the Upgrade Assistant.

   On UNIX system:

   ./ua
   

   On Windows systems:

   ua.bat
   

   The Upgrade Assistant displays the Welcome screen as shown inFigure 3-4.

   Description of "Figure 3-4 Upgrade Assistant Welcome Screen"

3. ClickNextto display the Specify Operation screen (Figure 3-5).

   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.

   Description of "Figure 3-5 Upgrade Assistant Select Operation Screen for an Oracle Portal, Forms, Reports, and Discoverer Upgrade"

Using the Upgrade Assistant to Upgrade the Oracle Portal, Forms, Reports, and Discoverer Middle Tier

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

Task 6a: Start the Upgrade Assistant for an Oracle Portal, Forms, Reports, and Discoverer Upgrade.

SelectUpgrade Middle Tier Instanceon the Specify Operation screen (Figure 3-5).

Refer toTable 3-2for a description of the Upgrade Assistant screens that require input from you during a middle-tier instance upgrade and the options on each screen.

The Upgrade Assistant performs the following tasks and provides the progress on each task:

• Examines the components to be upgraded.

• Provides a summary of the components to be upgraded so you can verify that the Upgrade Assistant is upgrading the components you expect.

• Provides a progress screen so you can see the status of the upgrade as it proceeds.

• Alerts you of any errors or problems that occur during the upgrade.

  See Also:

  Section B.1, "Troubleshooting Upgrade Assistant Problems and Issues" in theOracle Fusion Middleware Upgrade Planning Guidefor specific instructions for troubleshooting problems that occur while running the Upgrade Assistant

• Displays the End of Upgrade screen, which confirms that the upgrade was complete.

Task 5c: Install the Oracle Fusion Middleware 11gSoftware.

Specify Upgrade Options

Select the upgrade options you want to apply to the Oracle Portal, Forms, Reports, and Discoverer upgrade:

• Use source Oracle home ports in destination:If you want to migrate the port assignments used by your Oracle Application Server 10g Oracle home to your new Oracle Fusion Middleware Oracle instance.

  For more information, seeSection 3.6.2.2, "Important Notes When Using the Source Oracle Home Ports in the Destination Oracle Instance".

• 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.

ClickHelpto display more information about the upgrade options on this screen.

Section 4.1.5, "Removing Obsolete Partner Applications After Upgrade".

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 11gport and not the Oracle HTTP Server 10gport 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 10gOracle HTTP Server port information:

• TheHTTP Portproperty

• The port identified in theServlet URLproperty

• TheServerproperty 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.

For information on changing the Agent-Monitored Target properties, see "Troubleshooting the Display of Performance Metrics and Charts in Fusion Middleware Control" in theOracle Fusion Middleware Administrator's Guide.

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 theOracle 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):

  http://www.oracle.com/technology/documentation/
  

• You will have to verify the ports used for Oracle HTTP Server and Oracle Web Cache and re-register Oracle HTTP Server and Oracle Web Cache with Oracle Single Sign-On.

  For more information, seeSection 4.5.2, "Web Tier Component Post-Upgrade Tasks When Using Oracle Single Sign-On".

Task 6b: Upgrade the Oracle Portal, Forms, Reports, and Discoverer Middle Tiers. For more information about the Oracle BI Discoverer 11gstandalone configuration, see "About Oracle BI Discoverer installations" in theOracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

If you associated Oracle BI Discoverer 11gwith an Oracle Infrastructure (database schema), then you must upgrade the DISCOVERER schema to 11g.

To upgrade the DISCOVERER schema:

1. Start the Upgrade Assistant as described inTask 6a: Start the Upgrade Assistant for an Oracle Portal, Forms, Reports, and Discoverer Upgrade.

2. SelectUpgrade Metadata Repository SchemasandDiscoverer Schemafrom the Specify Operation screen (Figure 3-5).

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

   ClickHelpfor information about the options available on each screen.

Understanding the Impact of the Oracle Portal Schema Upgrade

Checking for Invalid Objects in the Database Where the Oracle Portal 10gSchema Resides

Backing Up the Database Where the Oracle Portal 10gSchema Resides

Verifying the Required Database Parameters for Oracle Portal 11g

Verifying That the Database and Oracle Internet Directory Are Running

Using the Upgrade Assistant to Upgrade the Oracle Portal Schema

Important Note:

If your Oracle Portal repository is not stored in the Oracle Metadata Repository, and is instead installed in a separate database, then do not use the procedures in this section. Instead, refer toAppendix A, "Upgrading an Oracle Portal Repository in a Customer Database".

3.6.4.1Understanding the Impact of the Oracle Portal Schema Upgrade

Before you upgrade the Oracle Portal to 11g, consider the impact of the upgrade on your existing Oracle Portal environment.

In particular, you should be aware that when you use the Upgrade Assistant to upgrade your Oracle Portal schema, the Upgrade Assistant performs the following tasks:

• Creates the upgrade framework objects and installs the Schema Validation Utility.

• 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.2Checking for Invalid Objects in the Database Where the Oracle Portal 10gSchema 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:

1. Connect to the Metadata Repository database.

   For example:

   ORACLE_HOME/bin/sqlplus "connect / as sysdba"
   

2. When prompted, enter the SYS password.

3. 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 theutlrp.sqlscript from the SQL*Plus command line to recompile the invalid objects:

@?/rdbms/admin/utlrp.sql

For more information about invalid objects, see "About Dependencies Among Schema Objects" in theOracle Database Administrator's Guide.

Backup Strategies for Upgrade" in theOracle Fusion Middleware Upgrade Planning Guide.Starting and Stopping Oracle Fusion Middleware" in theOracle Fusion Middleware Administrator's Guide.

Start the Upgrade Assistant as described inTask 6a: Start the Upgrade Assistant for an Oracle Portal, Forms, Reports, and Discoverer Upgrade.

SelectUpgrade Metadata Repository Schemasand thenPortal Schemafrom the Specify Operation screen (Figure 3-5).

Follow the instructions on the screens to upgrade the Oracle Portal schema.

ClickHelpfor information about the options available on each screen.

Chapter 4, "Oracle Portal, Forms, Reports, and Discoverer Post-Upgrade Tasks"for a description of the post-upgrade tasks you might need to perform for each of the Oracle Portal, Forms, Reports, and Discoverer components.Starting and Stopping Oracle Fusion Middleware" in theOracle Fusion Middleware Administrator's Guide.

Run the Upgrade Assistant again and selectVerify Instanceon the Specify Operation page.

Follow the instructions on the screen for information on how to verify that specific Oracle Fusion Middleware components are up and running.

Use the Fusion Middleware Control to verify that the Oracle Portal, Forms, Reports, and Discoverer components are up and running.

For more information, see "Getting Started Using Oracle Enterprise Manager Fusion Middleware Control" in theOracle Fusion Middleware Administrator's Guide.