3 Upgrade

3.1.1 Patches Required to Address Specific Upgrade and Compatibility Requirements

In general, Oracle assumes that you are running the latest Oracle Application Server 10g patch sets before you begin the upgrade to Oracle Fusion Middleware 11g.

In addition, in some specific cases, you must apply an additional software patches to your Oracle Application Server 10g components before you start the upgrade process. These patches are designed to address specific interoperability issues that you might encounter while upgrading your Oracle Application Server 10g environment to Oracle Fusion Middleware 11g.

Table 3-1 lists the specific patch sets required to address specific upgrade and compatibility requirements for Oracle Fusion Middleware 11g.

For more information, refer to the following sections:

• Section 3.1.1.1, "Obtaining Patches and Support Documents From My Oracle Support (Formerly OracleMetaLink)"

BAM MRUA: SCHEMA UPGRADE FAILED SQLException: ORA-39002: invalid operation

http://metalink.oracle.com/

3.1.2 Additional Database Requirement for Oracle Portal Upgrade

Section 3.6.4.3 of the Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer provides a list of database parameters you should verify before upgrading to Oracle Portal 11g.

In addition to the parameters listed in that section, you should also verify that the Processes initialization parameter is set to at least 500.

3.1.3 Clarification of Oracle Portal Compatibility Issues During Upgrade

As described in Section 4.3.2 of the Oracle Fusion Middleware Upgrade Planning Guide and in Section 3.5.1 of the Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer, there are some interoperability issues to consider when upgrading Oracle Portal to 11g.

To clarify the issues, consider the steps required to upgrade Oracle Portal:

1. Install Oracle Portal against the 10g PORTAL schema.

2. Run the Upgrade Assistant to upgrade your Oracle Portal 10g middle tier to 11g.

3. Run the Upgrade Assistant to upgrade the PORTAL schema to 11g.

After you install Oracle Portal against the 10g PORTAL schema, you must then run the Upgrade Assistant to upgrade the Oracle Portal middle tier. After performing the middle-tier upgrade, Oracle Portal is operational, although only 10g features will be available.

Later, you can use the Upgrade Assistant to upgrade the PORTAL schema to 11g. After the PORTAL schema is upgraded, then your upgraded Oracle Portal 11g instance will be fully operational with 11g features.

3.1.4 Unable to Read Composite Model Error During SOA Application Upgrade

The Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF describes how Oracle JDeveloper 11g will automatically upgrade specific features of your Oracle SOA Suite 10g applications to 11g.

However, if you see the following error while upgrading your application in JDeveloper 11g, then you can safely ignore the error. Your application will be upgraded, but you will need to create a new SOA-SAR deployment profile after the application upgrade. And use this newly created profile for deploying SOA composite:

SEVERE: Unable to read composite model for project project_name

For more information, see 43.2, "Deploying a Single SOA Composite in Oracle JDeveloper," in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

3.1.5 Oracle BAM Upgrade Issues

The following sections provide information about specific issues related to upgrading Oracle BAM 10g to Oracle BAM 11g:

• Section 3.1.5.1, "Datapump Export for Oracle BAM Upgrade Plug-in Fails in Oracle Database 10g (10.2.0.3), 10g (10.1.2.0.4), and Oracle Database 11g (11.1.0.7)"

• Section 3.1.5.2, "Dependent Alerts Do Not Upgrade Correctly"

• Section 3.1.5.3, "Upgrading Images in Oracle BAM Reports"

BAM MRUA: SCHEMA UPGRADE FAILED SQLException: ORA-39002: invalid operation

<param name="RuleID" order="0">
  //private:weblogic/Rule/624567ffe84de34c-6e6bdbaa120eb7f6ea6-8000
</param>

<param name="RuleID" order="0">
  ParentAlertName
</param>

3.1.6 Error When Upgrading Oracle Internet Directory Due to Invalid ODS Schema

If you receive an error when using the Upgrade Assistant to upgrade the Oracle Internet Directory schema from 10g Release 2 (10.1.2.3) to 11g, then verify that the ODS 10g schema is valid.

To view the status of the Oracle Application Server 10g schemas in your database, use the following SQL command:

SELECT comp_id, version, status FROM app_registry;

If the output from this command shows that the ODS schema is INVALID, then use the instructions in the following My Oracle Support document to install and configure Referential Integrity:

730360.1, "Referential Integrity in Oracle Internet Directory Version 10.1.2.3"

After performing the instructions in the support document, then retry the Oracle Internet Directory schema upgrade.

3.1.7 Restore From Backup Required If Upgrade Fails During a Colocated Oracle Internet Directory and Oracle Directory Integration Platform Upgrade

If you are using the Upgrade Assistant to upgrade both Oracle Internet Directory and Oracle Directory Integration Platform, consider the following.

If the Oracle Internet Directory upgrade fails, then before you can run the Upgrade Assistant again, you must restore your Oracle Internet Directory 10g backup before you can run the Upgrade Assistant again. Otherwise, the Upgrade Assistant will not attempt to upgrade Oracle Directory Integration Platform.

3.1.8 Cannot Verify Oracle Forms Services Upgrade When Oracle HTTP Server is Running On a Separate Host

If you use the Upgrade Assistant to upgrade an Oracle Forms Services instance that does not include a local instance of Oracle HTTP Server, then the Verify feature of the Upgrade Assistant cannot verify that the upgrade was successful. Instead of reporting that the upgrade was successful, the Verify feature will report that the server is unavailable. This verification error may not be valid if the Oracle HTTP Server is installed and configured on a different host than the Oracle Forms Services instance.

3.1.9 WebCenter Security Upgrade Release Notes

The following bugs/release notes relate to security changes for Custom WebCenter applications upgrading from 10.1.3.x:

• Section 3.1.9.1, "RowSetPermission check fails with compatibility flag set"

• Section 3.1.9.2, "Grants not migrated properly if application contains grants without permissions"

<sec:adf-security-child
xmlns="http://xmlns.oracle.com/adf/security/config">
    <JaasSecurityContext
initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
                         authorizationEnforce="true"/>
                <contextEnv name="oracle.adf.security.metadata"
value="false"/>
    <CredentialStoreContext
credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
   </sec:adf-security-child> 

3.1.10 Upgrade Assistant Upgrades Only Enabled Oracle Identity Federation Resources

If you have configured more than one data store, Authentication Engine, or SP Engine in your Oracle Identity Federation environment, note that the Upgrade Assistant will upgrade only the enabled resources to 11g. Any additional data stores, authentication engines, or SP engines that are are configured, but not enabled, will not be upgraded to the new Oracle Identity Federation 11g environment.

After you upgrade, you can reconfigure the resources that were not upgraded. In addition, unlike Oracle Identity Federation 10g, you can enable more than one of these resources at a time in 11g.

3.1.11 Service Name Is Required When Using ebMS with Oracle B2B

Because the Service Name parameter is required when using the ebMS protocol in Oracle B2B 11g, you may need to provide a value for this field after importing 10g data.

With the agreement in the draft state, update the field on the Partners > Documents tab. When you select a document definition that uses the ebMS protocol, the Document Type > ebMS tab appears in the Document Details area. The Service Name field is on this tab.

3.1.12 Converting Wallets to Keystores for Oracle B2B 11g

After upgrading to Oracle B2B 11g, use the orapki pkcs12_to_jks option to replace the entire keystore. Convert the wallet to a keystore as follows:

1. Back up the original keystore.

2. Use the orapki wallet pkcs12_to_jks option to convert to the keystore.

3. Use keytool -list to list the aliases and verify.

4. Use keytool -importkeystore to import the converted keystore to the backup of the original keystore (as done in Step 1)

3.1.13 Migrating the Oracle HTTP Server Wallet After Upgrading a Secure Oracle HTTP Server

If you configured Secure Socket Layer (SSL) for the communications between Oracle HTTP Server and Oracle Web Cache, and you upgraded both Oracle HTTP Server and Oracle Web Cache to 11g, consider the following.

When you run the Oracle Fusion Middleware Upgrade Assistant, it configures Oracle Web Cache 11g to use the SSL wallet from your Oracle Web Cache 10g environment instead of the default wallet that gets installed with Oracle Web Cache 11g.

As a result, if you did not select the Use source Oracle home ports in destination option in the Upgrade Assistant, then you must perform one of the following actions:

• If you want to keep using the same SSL wallet that you used in your Oracle Application Server 10g environment, then export all your certificates from the wallet used by Oracle HTTP Server 10g and import those certificates into the wallet used by Oracle HTTP Server 11g.

  You can use any available utility such as the WebLogic Scripting Tool (WLST) or Fusion Middleware Control for this task.

  For more information, see Section 7.4.7, "Common Certificate Operations," in the Oracle Fusion Middleware Administrator's Guide.

• If you want to use a new SSL wallet for Oracle Fusion Middleware 11g, then change the SSL settings for Oracle Web Cache 11g connections to Oracle HTTP Server 11g to use the default 11g wallet.

  For more information, see Section 5.4.3, "Task 3: Configure SSL Settings for Oracle Web Cache Connections to Origin Servers," in the Oracle Fusion Middleware Administrator's Guide for Oracle Web Cache.

3.1.14 Additional Oracle Identity Federation Post-Upgrade Tasks

The following additional post-upgrade tasks should be performed after upgrading to Oracle Identity Federation 11g, in addition to those described in the Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management:

• If you are have configured Oracle Identity Federation 10g to use the SAML 1.x/WS-FED protocol, then after you upgrade to Oracle Identity Federation 11g, you must set a default single sign-on identity provider.

  For more information, see "Configuring Service Providers" in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

• Export the Identity Provider self-signed certificate to the service provider

  The procedure you use to perform this task varies, depending on whether your service provider is a 10g or 11g service provider:

  • If you are using a 10g service provider, then refer to "Exporting the IdP's self-signed certificate to the SP" in the Oracle Identity Federation Administrator's Guide in the Oracle Application Server 10g (10.1.4.0.1) documentation library on the Oracle Technology Network (OTN):

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

  • If you are using an 11g service provider, then refer to "Set Up Single Sign-On for SAML 1.x and WS-Federation" in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

• If you are using an 11g Identity Provider and a 10g service provider, and you are using the SAML 1.x/WS-FED protocol, then you configure the 10g service provider.

  Specifically, for the 10g service provider, you must change the "Signing Certificate Subject DN" and "Signing Certificate Issuer DN" to 11g IdP format, which is of the form "CN=<host> Signing Certificate".

  For more information, see "Configure This Domain as a Source/Identity Provider" in the Oracle Identity Federation Administrator's Guide in the Oracle Application Server 10g (10.1.4.0.1) documentation library on the Oracle Technology Network (OTN).

• Enable "Send Signed Assertion" in Oracle Identity Federation 10g, or disable "Require Signed Assertions" in Oracle Identity Federation 11g.

  This task is necessary because in 10g, signed assertions are disabled by default, and in 11g, signed assertions are enabled by default.

  Depending whether you perform this task in 10g or 11g, refer to one the following:

  • "Configuring Service Providers" in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Federation.

  • Section 6.5.5, "Add Assertion Profile" in the Oracle Identity Federation Administrator's Guide in the Oracle Application Server 10g (10.1.4.0.1) documentation library on the Oracle Technology Network (OTN).

3.1.15 Recommendation When Upgrading Oracle JDeveloper 10g Projects

As described in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF, when you open a Oracle JDeveloper 10g workspace (.jws) file in Oracle JDeveloper 11g, the Oracle JDeveloper migration utility upgrades the application—including all the projects within the application—to the new Oracle JDeveloper 11g format.

You can also upgrade individual Oracle JDeveloper 10g project (.jpr) files. However, Oracle recommends you take the following steps when upgrading .jpr files:

1. Start Oracle JDeveloper 11g.

2. Create a new application in Oracle JDeveloper 11g.

3. Open the .jpr file from within the application so it becomes a project within the newly created application.

3.3.1 Documentation Errata for Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

The following issues have been identified in the released version of the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF:

• Section 3.3.1.1, "Incorrect Version Reference in Section 9.6.5.2"

• Section 3.3.1.2, "Additional Post-Upgrade Steps for Oracle BAM"

• Section 3.3.1.3, "Modified Procedure for Upgrading Domain Value Maps (DVMs) and Cross References with the Oracle SOA Suite Command-Line Upgrade Tool"

3.3.2 Documentation Errata for Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management

The following issues have been identified in the released version of the Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management:

• When Upgrading Oracle Identity Federation, Configuring Oracle Single Sign-On Is No Longer Required Before Running the Upgrade Assistant

3.3.3 Documentation Errata for Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer

The following issues have been identified in the released version of the Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer:

• Additional Configuration Step for Oracle Reports When Using 10g Ports During Upgrade