7 Upgrading the OracleAS Metadata Repository

7.1.4.1 Overview of Using Oracle Universal Installer to Upgrade a Seed Database

Figure 7-2 provides a graphical representation of the first few screens of the 10g Release 2 (10.1.2) installation procedure. It shows how you can select the appropriate Installation Type to install 10g Release 2 (10.1.2) and upgrade your existing OracleAS Metadata Repository.

As shown in the illustration, if you have already upgraded OracleAS Identity Management in a colocated Infrastructure, then the database that hosts the OracleAS Metadata Repository has already been upgraded to a supported version.

On the other hand, if your OracleAS Metadata Repository resides in a non-colocated Infrastructure, refer to Section 7.1.4, "Upgrading a Seed Database with Oracle Universal Installer" for more information.

Figure 7-2 Using Oracle Universal Installer to Upgrade the OracleAS Metadata Repository Database

Description of "Figure 7-2 Using Oracle Universal Installer to Upgrade the OracleAS Metadata Repository Database"

7.1.4.2 Upgrading a 10g (9.0.4) OracleAS Metadata Repository Seed Database in a Non-Colocated Infrastructure

When you use the 10g Release 2 (10.1.2) installation procedure to upgrade your OracleAS Metadata Repository database in a non-colocated Infrastructure, you perform the following tasks using the standard Oracle Universal Installer installation screens.

If your OracleAS Metadata Repository resides in a colocated Infrastructure, the database is upgraded automatically during the OracleAS Identity Management upgrade by Oracle Universal Installer.

1. If you are using Oracle Ultra Search, refer to Section 7.1.8, "Database Upgrade Considerations When Using Oracle Ultra Search" before upgrading the database.

2. Stop all the middle tiers that are using the services of the OracleAS Identity Management installation.

3. Make sure that the OracleAS Metadata Repository database and database listener are up and running.

4. Log in to the computer on which source instance is installed, as the same operating system user that performed the 10g (9.0.4) installation.

   
   

   Note: You must be logged in as a member of the dba operating system group.

   
   

5. Make sure the Oracle Internet Directory server is up and running.

   To verify that Oracle Internet Directory is running, enter one of the following commands.

   
   

   Note: You may have to temporarily set the ORACLE_HOME environment variable to the Oracle Internet Directory Oracle home before running the ldapbind command. After you verify that the Oracle Internet Directory is running, you must then make sure the ORACLE_HOME environment variable is not defined before you start the 10g Release 2 (10.1.2) installer, as directed in Step 6.

   
   

   If you are running Oracle Internet Directory on a non-secure port:

   SOURCE_ORACLE_HOME/bin/ldapbind -p Non-SSL_port
   
   

   If you are running Oracle Internet Directory on a secure port:

   SOURCE_ORACLE_HOME/bin/ldapbind -p SSL_port -U 1
   
   

   These commands should return a "bind successful" message.

6. Set the required environment variables, as defined in the section "Environment Variables" in the "Requirements" chapter of the Oracle Application Server Installation Guide.

   In particular, be sure to set following variables so they do not reference any Oracle home directories:

   • PATH

   • CLASSPATH

   • LD_LIBRARY_PATH

   • SHLIB_PATH

   In addition, be sure the following environment variables are not set:

   • TNS_ADMIN

   • ORACLE_HOME

   • ORACLE_SID

7. Mount the CD-ROM and start the installer.

   
   

   See Also: Oracle Application Server Installation Guide for detailed instructions about starting Oracle Universal Installer on your platform

   
   

8. Refer to Table 7-1 for information on the options you should select on each screen.

9. After the End of Installation screen appears, exit Oracle Universal Installer and then verify that Oracle Internet Directory and Oracle Application Server Single Sign-On are functioning and accessible in the new 10g Release 2 (10.1.2) Oracle home.

   
   

   See Also: Oracle Application Server Administrator's Guide, Chapter 1, "Accessing the Single Sign-On Server"

   
   

Note that you must run MRUA to upgrade the OracleAS Metadata Repository component schemas after the database is upgraded to a supported database version.

7.1.5.1 If You Installed the OracleAS Metadata Repository in an Oracle9i Database

If you installed your OracleAS Metadata Repository in an Oracle9i Database, you must be sure your database is Oracle9i Release 2 (9.2.0.6) or higher. Refer to the following sections for more information.

If You Installed the OracleAS Metadata Repository in an Oracle9i (9.0.1.x) Database

1. Install Oracle9i Release 2 (9.2.0.1) into a new Oracle home

2. Apply the Oracle9i Release 2 (9.2.0.6) patchset to the Oracle9i Release 2 (9.2.0.1) Oracle home; be sure to carefully follow the instructions in the Oracle9i Release 2 (9.2.0.6) patchset notes.

   You can download the patchset from OracleMetaLink (http://metalink.oracle.com). Download patchset number 3948480.

3. Use the Database Upgrade Assistant (DBUA) in the Oracle9i Release 2 (9.2.0.6) Oracle home.

   
   

   See Also: Oracle9i Database Migration in the Oracle9i Database documentation library for information about using DBUA and upgrading specific database components to Oracle9i Release 2 (9.2.0.6)

   
   

4. Apply patch 4015165 to the newly upgraded Oracle9i Release 2 (9.2.0.6) database.

   The patch is available from OracleMetaLink (http://metalink.oracle.com)

5. See section Section 7.1.5.2, "Special Instructions When Applying the Oracle9i Release 2 (9.2.0.6) Database Patchset" for more information before upgrading the OracleAS Metadata Repository.

If you installed the OracleAS Metadata Repository in an Oracle9i Release 2 (9.2.0.x) database

1. Apply the Oracle9i Release 2 (9.2.0.6) patchset to the Oracle9i Release 2 (9.2.0.x) Oracle home; be sure to carefully follow the instructions in the Oracle9i Release 2 (9.2.0.6) patchset notes.

   You can download the patch set from OracleMetaLink (http://metalink.oracle.com). Download patchset number 3948480.

2. Apply patch 4015165 to the newly upgraded Oracle9i Release 2 (9.2.0.6) database.

   The patch is available from OracleMetaLink (http://metalink.oracle.com)

3. See the section Section 7.1.5.2, "Special Instructions When Applying the Oracle9i Release 2 (9.2.0.6) Database Patchset" for more information before upgrading the OracleAS Metadata Repository.

If you installed the OracleAS Metadata Repository in an Oracle9i Release 2 (9.2.0.6) database

1. Apply patch 4015165 to the Oracle9i Release 2 (9.2.0.6) database.

   The patch is available from OracleMetaLink (http://metalink.oracle.com)

2. See the section Section 7.1.5.2, "Special Instructions When Applying the Oracle9i Release 2 (9.2.0.6) Database Patchset" for more information before upgrading the OracleAS Metadata Repository.

7.1.5.2 Special Instructions When Applying the Oracle9i Release 2 (9.2.0.6) Database Patchset

When you upgrade your database to Oracle9i Release 2 (9.2.0.6), make sure that you carefully follow the instructions in the README file for the Oracle9i Release 2 (9.2.0.6) patchset.

In particular, perform the following tasks after you run the Database Upgrade Assistant (DBUA):

• Run the catpatch.sql script (step 6 in the README file).

• Run utlrp.sql (step 10 in the README file for the patch set).

  To check that you have run the catpatch.sql script, you can run the following command in SQL*Plus:

  C:\> sqlplus "sys/password as sysdba"
  SQL> select comp_name, version, status from dba_registry
       where comp_id = 'CATPROC';
  
  

  You should get the following results:

  COMP_NAME                     VERSION     STATUS
  ----------------------------- ----------- --------
  Oracle9i Packages and Types   9.2.0.6.0   Valid
  

  
  

  Note: Be sure that the catpatch.sql script has been run against your database. Even if you have patched your database Oracle home to Oracle9i Release 2 (9.2.0.6), when you create a new database using the Database Configuration Assistant (DBCA), the new database might require the catpatch.sql script.

  
  

7.1.5.3 If You Installed the OracleAS Metadata Repository in an Oracle 10g Database

If you used the OracleAS Metadata Repository Creation Assistant to install the OracleAS Metadata Repository in an Oracle Database 10g database, you must upgrade the database to Oracle Database 10g (10.1.0.4.2) before you can use Metadata Repository Upgrade Assistant (MRUA) to upgrade the component schemas in the OracleAS Metadata Repository to 10g Release 2 (10.1.2.0.2).

7.1.8.1 Upgrading Oracle Ultra Search Middle Tiers Before Upgrading the OracleAS Metadata Repository Database

If you have installed and configured Oracle Ultra Search, you must upgrade your middle tiers before you upgrade the OracleAS Metadata Repository database.

For example, if you are upgrading OracleAS Identity Management in a colocated Infrastructure, you must upgrade the middle tiers before you upgrade OracleAS Identity Management. This is because the OracleAS Identity Management upgrade process in a colocated Infrastructure automatically upgrades the database.

If you do not upgrade the middle tiers first, compatibility problems will result between the Oracle Ultra Search files installed in the middle tiers and the Oracle Ultra Search files installed in the upgraded database.

7.1.8.2 Configuring Oracle Ultra Search When Upgrading a Oracle9i Release 2 (9.2.0.4) Database

If you have installed the OracleAS Metadata Repository in a Oracle9i Release 2 (9.2.0.4) database using the OracleAS Metadata Repository Creation Assistant, you must perform the following procedure to prevent the Oracle9i Database patchset from overwriting Oracle Ultra Search files.

This procedure is necessary only if you are applying an Oracle9i Database patchset to an Oracle9i Release 2 (9.2.0.4) database that hosts the OracleAS Metadata Repository. If you are upgrading from Oracle9i (9.0.1.3) or Oracle9i (9.0.1.5), this procedure is not necessary because that database upgrade results in a new Oracle home.

Before you apply the Oracle9i Database patchset:

1. Log in to the computer that hosts the OracleAS Metadata Repository database and change directory to the database Oracle home.

2. Rename the ultrasearch directory in the OracleAS Metadata Repository database Oracle home as follows:

   Old name:

   ORACLE_HOME/ultrasearch
   
   

   New name:

   ORACLE_HOME/ultrasearch_904
   
   

3. Rename the ultrasearch directory that was backed up automatically when you ran the OracleAS Metadata Repository Creation Assistant to initially create the repository in the existing database.

   The name of the backup directory is in the following format:

   ORACLE_HOME/ultrasearch_datestamp
   
   

   Rename this directory by removing the underscore and datestamp as follows:

   ORACLE_HOME/ultrasearch
   
   

4. Upgrade the database by applying the Oracle9i Release 2 (9.2.0.x) patchset.

5. Rename the ultrasearch directory to ultrasearch_920x, because this is the directory created by the Oracle9i Database patchset, and the Oracle Ultra Search files installed by the patchset are not usable in this configuration.

6. Rename the ultrasearch_904 directory to ultrasearch because this directory contains is the original 10g (9.0.4) files that are compatible with this version of Oracle Application Server.

7. Verify that the Oracle Ultra Search version is correct, by using the following SQL on the OracleAS Metadata Repository database:

   select wk_util.get_version from dual;
   
   

   This command should return '9.0.4' as the current version of Oracle Ultra Search.

7.1.8.3 Repairing Oracle Ultra Search After Upgrading an Oracle9i Release 2 (9.2.0.x) Database

If you applied an Oracle9i Release 2 (9.2.0.x) patchset to your OracleAS Metadata Repository Creation Assistant database without first configuring Oracle Ultra Search as described in Section 7.1.8.2, "Configuring Oracle Ultra Search When Upgrading a Oracle9i Release 2 (9.2.0.4) Database", then you can repair the Oracle Ultra Search software using the following procedure:

1. Rename the ultrasearch directory in the OracleAS Metadata Repository database Oracle home as follows:

   Old name:

   ORACLE_HOME/ultrasearch
   
   

   New name:

   ORACLE_HOME/ultrasearch_904_920x
   
   

   The new ultrasearch_904_920x directory contains the Oracle Ultra Search files that are unusable with this version of Oracle Application Server.

2. Create a new version of the ultrasearch directory that contains Oracle Ultra Search files that are compatible with this version of Oracle Application Server.

   You can create a new ultrasearch directory in the OracleAS Metadata Repository database Oracle home by copying the ultrasearch directory from the original 10g (9.0.4) OracleAS Metadata Repository Creation Assistant CD-ROM.

7.1.8.4 Upgrading the Oracle Ultra Search Schemas Immediately After Upgrading the OracleAS Metadata Repository Database

When you upgrade the OracleAS Metadata Repository database, the database upgrade procedure also upgrades some components of Oracle Ultra Search.

As a result, if you are using Oracle Ultra Search, upgrade the component schemas with the Metadata Repository Upgrade Assistant as soon as possible after you upgrade the OracleAS Metadata Repository database version.

MRUA completes the Oracle Ultra Search upgrade process by upgrading the Oracle Ultra Search schema and running required Oracle Ultra Search SQL scripts against the OracleAS Metadata Repository.

7.3.1.1 Downloading and Installing the OracleAS Portal 10g (9.0.4) Repository Upgrade Software

If you are upgrading a Release 2 (9.0.2) OracleAS Metadata Repository and you are using OracleAS Portal, then you must perform the following task before running MRUA.

Note that you must also perform this procedure before you upgrade an Oracle9iAS Release 2 (9.0.2) Portal repository in a customer database.

This procedure installs a required patch in the Oracle home of the database that contains the OracleAS Portal schemas:

1. Log in to the computer where your OracleAS Portal repository or OracleAS Metadata Repository is installed.

   Be sure to log in as the same user who installed the repository.

2. Determine the version of the database where the OracleAS Metadata Repository or OracleAS Portal repository being upgraded resides.

3. Using your Web browser, log in to OracleMetaLink (http://metalink.oracle.com) and locate the patch specific to your database version:

   • Patch 4045812 if your database version is 10g or later.

   • Patch 2778342 if your database version is an Oracle9i database.

   
   

   Note: The two patches contain the same software but are bundled using different versions of the Oracle Universal Installer. Attempting to install the wrong one will result in version related errors in the installer. The latest version of these patches should always be used.

   
   

4. Download the ZIP file that contains the patch into a temporary directory on your computer and extract its contents. The file contains the following:

   • Disk1 - a directory containing the scripts used to run the Oracle AS Portal repository upgrade

   • readme.html - A readme file

5. Examine the readme.html file for any changes that could affect the remaining procedures.

6. Set the ORACLE_HOME environment variable to the database Oracle home for the OracleAS Metadata Repository or OracleAS Portal repository.

7. Verify that your DISPLAY environment variable is set correctly.

8. Run the Oracle Universal Installer to copy the Portal upgrade scripts to the Oracle home using this command:

   $ORACLE_HOME/oui/bin/runInstaller
   
   

   Table 7-2 describes the options you should select on each screen of the Oracle Universal Installer.

   The installation procedure creates the following directory in the Oracle home:

   ORACLE_HOME/portal/upg/plsql
   
   

   It contains the programming code originally required to upgrade your repository from version 9.0.2 to version 10g (9.0.4). These files will automatically be used as part of the repository upgrade to version 10.1.2.

   Table 7-2 Summary the Oracle Universal Installer Screens When Installing the OracleAS Portal 10g (9.0.4) Repository Upgrade Patch

   Screen	Description and Recommended Options to Select
   Welcome	Welcomes you to Oracle Universal Installer.
   Specify File Locations	In the Source field, specify the complete path to the products.xml file that was included in the download for Patch 4045812 or the products.jar file that was included in the download for Patch 2778342. For example, if you unzipped the downloaded file into your /tmp/upg directory, you would enter the following in the Source field: For Patch 4045812: /tmp/upg/Disk1/stage/products.xml For Patch 2778342: /tmp/upg/Disk1/stage/products.jar In the Destination fields, enter the name and path to the database Oracle home that hosts your OracleAS Portal repository.
   Summary	Use this screen to confirm the choices you've made. Click Install to begin installing the patch.
   End of Installation	This screen appears when the installation is complete. Click Exit to quit Oracle Universal Installer.

   
   

7.3.1.2 Downloading and Installing the Oracle9iAS Single Sign-On 9.0.2.5 Patch

If you are using OracleAS Portal and you plan to keep using a 9.0.2 OracleAS Identity Management installation after you upgrade your OracleAS Metadata Repository, then you must perform the following steps in order to allow for interoperability between OracleAS Portal and 9.0.2 OracleAS Single Sign-On.

Note that this procedure also applies to situations where you have installed the OracleAS Portal repository in a customer database, outside of an OracleAS Metadata Repository.

This procedure does not apply if you have already upgraded the OracleAS Single Sign-On schema to 9.0.2.5 or if you are upgrading a 10g (9.0.4) OracleAS Portal repository or 10g (9.0.4) OracleAS Metadata Repository.

To apply the OracleAS Single Sign-On 9.0.2.5 patch:

1. Log in to the computer where your Oracle9iAS Release 2 (9.0.2) Metadata Repository containing your OracleAS Single Sign-On schema is located.

   Be sure to log in as the same user who installed the Release 2 (9.0.2) Metadata Repository.

2. Log in to OracleMetaLink and locate Patch 2995671:

   http://metalink.oracle.com
   
   

3. Download the ZIP file that contains the patch into a temporary directory on your computer and extract its contents. The file contains the following:

   • docs - a directory containing documentation for installing and applying the patch

   • util - a directory containing the files required to install and apply the patch

   • readme.txt - A readme file that describes the patch and its contents

4. Use the instructions in the following HTML file to install and apply the patch:

   patch_directory/docs/sso_patch_902.html
   
   

   For example, if you unpacked the patch ZIP file into the /tmp/upg directory, the documentation would be located at:

   /tmp/upg/docs/sso_patch_902.html
   
   

   The patch is applied to the Oracle9iAS Single Sign-On Server schema in the Release 2 (9.0.2) OracleAS Metadata Repository.

7.3.1.3 Converting External Application Identifiers After Applying the OracleAS Single Sign-On 9.0.2.5 Patch

If you are upgrading OracleAS Portal 10g (9.0.4) and you have applied the OracleAS Single Sign-On 9.0.2.5 patch, then you must apply a patch to convert the external application identifiers in the OracleAS Portal schema. Refer to Table 7-3 for the appropriate patch number.

7.3.3.1 About Upgrading Release 2 (9.0.2) and 10g (9.0.4) Wireless Schemas

MRUA upgrades the OracleAS Wireless schema from 10g (9.0.4) to 10g Release 2 (10.1.2), but it does not upgrade the OracleAS Wireless schema from Release 2 (9.0.2).

As a result, if you are upgrading from 10g (9.0.4), then MRUA upgrades the OracleAS Wireless schema successfully and no workarounds or special steps are required. Similarly, or if you are upgrading from Release 2 (9.0.2) and you did not configure OracleAS Wireless, then MRUA installs the Wireless schema with no issues.

However, if you are upgrading from Release 2 (9.0.2) and you configured OracleAS Wireless in the Release 2 (9.0.2) middle tier, then you must follow the instructions for upgrading a Wireless middle tier as described in Section 4.10.2, "Special Instructions When Upgrading an OracleAS Wireless Release 2 (9.0.2) Middle Tier" before using MRUA to upgrade the OracleAS Metadata Repository.

This is because during the middle tier installation and upgrade to 10g Release 2 (10.1.2), the OracleAS Wireless Configuration Assistant upgrades the OracleAS Wireless schema to 10g (9.0.4). You can then use MRUA to upgrade the schema from 10g (9.0.4) to 10g Release 2 (10.1.2).

Note that if you have installed and configured OracleAS Wireless for Release 2 (9.0.2) and you did not install and configure at least one 10g Release 2 (10.1.2) OracleAS Wireless middle tier against the OracleAS Metadata Repository, the following error appears in the MRUA log files:

Invalid upgrade path. Please install AS10G (904) or 10.l.2 wireless mid tier
against this infrastructure before running the MR upgrade.

7.3.3.2 Upgrading OracleAS Wireless Device Definitions

When you upgrade the OracleAS Wireless schema in the OracleAS Metadata Repository, MRUA does not upgrade any wireless device definitions stored in the OracleAS Metadata Repository.

To obtain the most recent wireless device updates, as well as instructions for how to add them to your repository, navigate to the following URL on the Oracle Technology Network (OTN):

http://www.oracle.com/technology/products/iaswe/devices/index.html

7.4.7.1 Guidelines for Using the MRUA Log Files

If the MRUA output indicates that one or more of the component upgrades failed, review the MRUA log files, or any component log files referenced from the MRUA log files.

If the OracleAS Portal upgrade fails, then see Section 7.4.8, "Reviewing the OracleAS Portal Repository Upgrade Log Files" for information on how to proceed.

Otherwise, refer to Appendix C, "Upgrade and Compatibility Error Messages" for information about specific component error messages you might find in the log files.

If, by reviewing the log files and Appendix C, you are able to identify a solution to the upgrade failure, you can implement your solution and then re-run MRUA. When you re-run MRUA, any components that were upgraded successfully during the previous run will not be affected. However, MRUA will attempt to upgrade any components that were not upgraded successfully during a previous run of the utility.

Contact Oracle Support for any errors that are not documented or that cannot be resolved by following documented actions. Note that some errors that occur will require the repository to be restored from backup, the problem to be resolved, and another upgrade to be run.

7.4.7.2 Locating the MRUA Log Files

The log files are located in the following directory in the Oracle home of the OracleAS Metadata Repository you are upgrading:

METADATA_REPOSITORY_ORACLE_HOME/upgrade/logs

MRUA generates three log files that are of particular interest when you are troubleshooting upgrade issues. The name of the log file includes the exact time the MRUA session was run. This makes it easy to identify a log file for a particular MRUA session.

For example, the three log files generated when you run MRUA at 12:36 PM on September 16, 2004 would appear as follows in the logs directory:

mrua2004-09-16_12-36-36PM.log
mrua2004-09-16_12-36-36PM.err
mrua2004-09-16_12-36-36PM.out

Table 7-5 shows the three log file types and the content you can expect to find in each one.

mrua<timestamp>.log

mrua<timestamp>.err

mrua<timestamp>.out

7.5.1.1 Reconfiguring OracleAS Portal to Work with Oracle Internet Directory After Upgrading From Release 2 (9.0.2)

If your starting version was Oracle9iAS Portal 9.0.2.x, follow the steps in this section to reconfigure OracleAS Portal for Oracle Internet Directory.

This reconfiguration is necessary because some Oracle Internet Directory privileges have changed between Release 2 (9.0.2) and 10g (10.1.2). For example, the subscription for Oracle Directory Integration and Provisioning event notifications has changed and Oracle Delegated Administration Services URLs have changed.

When you run the ptlconfig command, as described in the following procedure, values such as these, which are cached in the Portal schema, get updated accordingly:

1. Change directory to the following location in the destination middle tier Oracle home:

   DESTINATION_ORACLE_HOME/portal/conf
   
   

2. Run the following command:

   ptlconfig -dad portal_DAD -oid
   
   

   In this command, portal_DAD is the DAD of the OracleAS Portal repository that you just upgraded.

   
   

   See Also: Oracle Application Server Portal Configuration Guide, for more information about the ptlconfig tool

   
   

7.5.1.2 Starting all Middle Tiers That Use The Upgraded Portal Instance

After the script has executed successfully, start each middle tier that is using the upgraded Portal instance by performing these steps:

1. Start OPMN and processes managed by it with this command:

   MIDDLE_TIER_ORACLE_HOME/opmn/bin/opmnctl startall
   
   

2. Start the Application Server Control using the following command:

   MIDDLE_TIER_ORACLE_HOME/bin/emctl start iasconsole
   

7.5.1.3 Moving the Portlet Repository to the New Format (Optional)

By default, the portlet repository is upgraded in-place in the OracleAS Portal schema. The existing pages, templates, items, and so on, in the portlet repository are upgraded, and the new portlets are added into the repository. Since the old settings are preserved, the pages look very similar to the way they did before the upgrade was run.

If you want the repository to have the appearance of a newly installed instance, a script is available to re-create the upgraded portlet repository. The script removes the existing portlet repository and re-creates it. Use the script only if you do not wish to preserve customizations, settings, styles, banners, and so on in the portlet repository.

To re-create the portlet repository, follow these steps after starting the middle tiers as described in Section 7.5.1.2, "Starting all Middle Tiers That Use The Upgraded Portal Instance":

1. Perform a backup of the database, since the script overwrites the repository and is not reversible.

2. Navigate to the following directory on the OracleAS Metadata Repository Upgrade Assistant and Utilities CD–ROM, which contains the prrplc.sql script:

   MRUA_CDROM_ROOT/portal/admin/plsql/upg/common
   
   

3. Log in to the OracleAS Metadata Repository database as Portal schema user from SQL*Plus.

4. Run the prrplc.sql script with no arguments.

7.5.1.4 Accessing the Upgraded OracleAS Portal

If there were no errors in the OracleAS Portal Repository upgrade, you can access your upgraded Portal. Open a browser and navigate to the following URL:

http://host.domain:port/pls/portal_DAD

For example:

http://portalhost42.acme.com:7777/pls/portal

7.5.1.5 Impact of Shutting Down the OracleAS Metadata Repository Database on OracleAS Portal Oracle Text Indexes

Missing Oracle Text indexes are created during the OracleAS Portal upgrade process, but they are not populated, as this can be very time consuming. The new indexes are populated once the upgrade is complete, when the next synchronization job is scheduled.

If you need to shut down the database after the upgrade (to back up) and the Oracle Text index synchronization job has started, consider the impact of the following shutdown commands on the synchronization process:

• Shutdown Immediate or Abort

  The indexing job stops immediately and is rolled back.

• Shutdown Normal

  Entire indexing job finishes before the database shuts down.

• Shutdown Transactional

  Synchronization of the current index is allowed to finish before the database shuts down. If one or more indexes still need to be synchronized, synchronization of the next index is not started.

7.5.1.6 Reconfiguring OracleAS Portal to Work with Delegated Administration Services

In releases of OracleAS Portal prior to 10g Release 2 (10.1.2), if the Infrastructure and Application Server middle tier were separated onto different hosts or protocols, the user and group Lists of Values (LOVs) required configuration to accommodate the JavaScript Origin Server Security policy. The resultant JavaScript errors were due to the OracleAS Portal and Delegated Administration Services (DAS) residing in different domains.

There were two options provided for resolution of this issue:

• Setting up of a common-domain by running the script secjsdom.sql

• Deploying DAS on the middle tier.

In OracleAS Portal 10g Release 2 (10.1.2), the implementation of the LOVs has been modified to support a callback method, removing the cross-domain issue and the need for the configuration steps above. However, this callback mechanism requires a corresponding patch to the DAS environment to support the use of LOVs across domains.

Support for the callback method has been included in DAS versions 9.0.4.1 and later. Conversely, if you are using DAS version 9.0.2.3 you can apply patch 3278638 to enable callback support.

If you have installed the appropriate DAS version in your environment, and have not previously implemented the configuration options mentioned above, then no subsequent configuration steps are required in OracleAS Portal to support the LOVs on a separate host. However, if you used the configuration options mentioned above, it is required to remove these steps. This can be done as follows:

1. If a common domain was defined, reset it by executing the secjsdom.sql script as follows:

   1. From your operating system command prompt, go to the following directory:

      DESTINATION_MIDTIER_ORACLE_HOME/portal/admin/plsql/wwc 
      
      

   2. Using SQL*Plus, connect to the OracleAS Portal Repository as the schema owner and run the following commands:

      @secjsdom ''
      commit;
      
      

2. If OracleAS Portal has been configured to use a locally deployed DAS servlet, reconfigure it to point to the Infrastructure tier by running the secdaslc.sql script as follows:

   1. From the operating system prompt, go to the following directory:

      DESTINATION_MIDTIER_ORACLE_HOME/portal/admin/plsql/wwc
      
      

   2. Using SQL*Plus, connect to the OracleAS Portal Repository as the schema owner and run the following commands:

      @secdaslc N
      commit;
      

7.5.1.7 Updating Customized Login Portlets

If you have customized the login portlet, you must update it to work in this release. In prior releases, user credentials were posted to OracleAS Portal's wwptl_login.login_url procedure. In this release, the user credentials must be passed to OracleAS Single Sign-On's wwsso_app_admin.ls_login procedure instead. Follow the steps outlined in OracleMetaLink note 290445.1 to update your customized login portlet to use wwsso_app_admin.ls_login.

7.5.1.8 Updating OracleAS Portal Performance Reporting

To generate performance reports for OracleAS Portal, you must use a set of SQL scripts. These scripts are used to load OracleAS Portal log files into a database table and create reports based on that information. The scripts are located in the following directory:

ORACLE_HOME/portal/admin/plsql/perf

If you are already using the performance reporting scripts, then after upgrading to OracleAS Portal 10.1.2.0.2, you must run the new copy of the following file:

ORACLE_HOME/portal/admin/plsql/perf/install/update.sql

This is to accommodate the new URL format for Repository requests and to enable collection of new data. If this is not done, then the scripts will not work.

For details about how you can use the scripts to monitor OracleAS Portal performance, refer to the following file in the scripts subdirectory:

ORACLE_HOME/portal/admin/plsql/perf/scripts/README.html