| Oracle® Fusion Middleware Release Notes 11g Release 1 (11.1.1) for HP-UX PA-RISC (64-Bit) Part Number E14775-42 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Release Notes 11g Release 1 (11.1.1) for HP-UX PA-RISC (64-Bit) Part Number E14775-42 |
|
|
PDF · Mobi · ePub |
This chapter describes issues associated with upgrading your environment and your applications to Oracle Fusion Middleware 11g. It includes the following topics:
Note:
This chapter contains issues you might encounter while upgrading any of the Oracle Fusion Middleware products.Be sure to review the product-specific release note chapters elsewhere in this document for any additional issues specific to the products you are using.
This section describes general issue and workarounds. It includes the following topics:
Section 3.1.1, "Patches Required to Address Specific Upgrade and Compatibility Requirements"
Section 3.1.2, "Unable to Read Composite Model Error During SOA Application Upgrade"
Section 3.1.4, "Error When Upgrading Oracle Internet Directory Due to Invalid ODS Schema"
Section 3.1.9, "Problem Accessing the Welcome Pages in Oracle HTTP Server After Upgrade"
Section 3.1.10, "Misleading Error Message When Upgrading Oracle Internet Directory"
Section 3.1.12, "Additional Steps Required When Upgrading Human Taskflow Projects"
Section 3.1.13, "Stopping Oracle Virtual Directory Processes During Upgrade"
Section 3.1.15, "Upgrading Oracle Access Manager Middle Tier"
Section 3.1.16, "Inaccurate Results When Running the Upgrade Assistant Verify Feature"
Section 3.1.17, "Missing jdk_version.log File When Launching Upgrade Assistant"
Section 3.1.18, "Test Suites in Oracle SOA Suite 10g Projects Not Upgraded to 11g"
Section 3.1.19, "Incorrect Wiring When Migrating Certain Oracle SOA Suite 10g Projects to 11g"
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:
Table 3-1 Patches Required to Address Specific Upgrade and Compatibility Requirements
| Patch Set Number | Description and Purpose | Additional Information |
|---|---|---|
|
8404955 |
Before you can perform the Oracle B2B schema upgrade, you must apply this required patch to the Oracle Application Server Integration B2B 10g Release 2 (10.1.2) middle tier. This patch set is required in order to enable the Java command that you use to export the trading partner agreements, as described in the following step. |
"Task 6b: If Necessary, Upgrade the B2B Schema" in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF |
|
5746866 |
If the database that hosts your Oracle Application Server 10g schemas is an Oracle Database 10g (10.1.0.x) database, then make sure that this database patch (or database patch 5126270) has been applied to the 10g (10.1.0.x) database before you upgrade the database to the required Oracle Database 10g (10.2.0.4). Note that database patch 5746866 includes patch 5126270. |
"Upgrading to Oracle Database 10g Release 2 (10.2.0.4)" in the Oracle Fusion Middleware Upgrade Planning Guide |
|
7685124 |
Apply this patch against Oracle Secure Enterprise Search (10.1.8.3.0) before you attempt to use Oracle Secure Enterprise Search with Oracle Portal 11g. |
"Oracle Secure Enterprise Search" in the Oracle Fusion Middleware Administrator's Guide for Oracle Portal |
|
8372141 |
Apply this patch on your Oracle Application Server 10g Release 3 (10.1.3.4) environment to enable interoperability between Oracle SOA Suite 10g Release 3 (10.1.3.4) and Oracle BPEL Process Manager 11g. This patch is also referred to as the Oracle SOA Suite 10g Release 3 (10.1.3.4) Cumulative MLR #7. |
"Upgrading Oracle SOA Suite Client Applications" in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF |
|
6522654 |
Apply this patch to your Oracle Database before you attempt to upgrade your Oracle BAM schema. If you do not apply this patch to your Oracle Database 10g (10.2.0.3), 10g (10.2.0.4), or Oracle Database 11g (11.1.0.7) before performing the schema upgrade, you will likely see the following error: BAM MRUA: SCHEMA UPGRADE FAILED SQLException: ORA-39002: invalid operation The description for this patch on My Oracle Support is "USING DATA PUMP THROUGH DBLINK CAUSED DATA CORRUPTION FOR CLOB VALUES". |
"Task 6c: If Necessary, Upgrade the BAM Schema" in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF |
|
7675269 |
Apply this patch to prevent the occurrence of an ORA-01591 error in an Oracle Real Application Clusters (Oracle RAC) 11g (11.1.0.7) database. This error can occur for rows locked by transactions which were in the middle of two-phase commit. The description of this patch on My Oracle Support is "ODAC 2008:RAC NODE AFFINITY: DISTRIBUTED TXN ABORTS WITH ORA-01591." |
"Upgrading and Preparing Your Databases" in the Oracle Fusion Middleware Upgrade Planning Guide |
|
8291981 |
Apply this patch to correct a problem where Metadata Repository (MDS) queries against an Oracle Database 11g (11.1.0.7) database do not find all of the results (documents or elements) that they should. The description of this patch on My Oracle Support is: "SELECT INCORRECT RESULTS: SOME RESULTS NOT FOUND". |
"Managing the MDS Repository" in the Oracle Fusion Middleware Administrator's Guide |
|
9007079 |
Apply this bundled patch to your Oracle Database 11g (11.1.0.7) Real Application Clusters (Oracle RAC) environment to address three known issues while using the Oracle RAC database with Oracle Fusion Middleware Oracle SOA Suite components. See the Readme file for the patch for a list of the bugs addressed by the patch. The description of this patch on My Oracle Support is: "MERGE REQUEST FOR 8886255 AND 7675269". |
"Oracle Real Application Clusters and Fusion Middleware" in the Oracle Fusion Middleware High Availability Guide. |
|
8607693 |
Apply this patch to your Oracle Real Application Clusters (Oracle RAC) 11g (11.1.0.7) database to prevent an error that can occur if an XA transaction branch was being asynchronously rolled back by two or more sessions. The description of this patch on My Oracle Support is: "STRESS SOA - ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [504] (Oracle AC)". |
"Oracle Real Application Clusters and Fusion Middleware" in the Oracle Fusion Middleware High Availability Guide. |
|
7682186 |
Apply this patch to your Oracle Real Application Clusters (Oracle RAC) 11g (11.1.0.7) database to prevent an issue that results in an ORA-600 error. Behavior includes CR-inconsistencies between index and the block, or incorrect results in an Oracle RAC multi-node global transaction environment. The description of this patch on My Oracle Support is: "ORA-600[KDSGRP1] SIGNALLED DURING BUGOLTP-XA WORKLOAD". |
"Oracle Real Application Clusters and Fusion Middleware" in the Oracle Fusion Middleware High Availability Guide. |
To obtain a patch, log in to My Oracle Support (formerly OracleMetaLink), click Patches and Updates, and search for the patch number:
http://support.oracle.com/
To obtain a support note or document, log in to My Oracle Support and enter the support note number in the Quick Find search field at the top of the My Oracle Support window and search the Knowledge Base for the note number.
If the Oracle Database you use to host your Oracle BAM schema is an Oracle Database 11g database, then you must apply the required patches to upgrade your database to Oracle Database 11g (10.1.0.7).
In addition, if the database is running on a Microsoft Windows 32-bit computer, then you must also apply patch 8451592 to the Oracle Database 11g (10.1.0.7) database before you can run the Upgrade Assistant to upgrade the Oracle BAM schema to 11g.
Patch 8451592 is also referred to as Oracle Database Server Version 11.1.0.7 Patch 11.
Important:
You must perform the steps described in Section 3.3.5, "Post Installation Instructions" of the Oracle Database Server Version 11.1.0.7 Patch 11 Bundle Patch Update Note, which explain in detail how to run the
catcpu.sql script.
If you do not run the catcpu.sql script after applying the database patch, then the Oracle BAM schema upgrade will fail.
The patch update note is available by clicking the View Readme button when you locate the patch in My Oracle Support. It is also included in the downloaded ZIP file that contains the patch files.
For more information about upgrading the Oracle BAM schema, see the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF.
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.
The following sections provide information about specific issues related to upgrading Oracle BAM 10g to Oracle BAM 11g:
Section 3.1.3.2, "Dependent Alerts Do Not Upgrade Correctly"
Section 3.1.3.3, "Problem Upgrading a Report that Contains Calculated Fields"
Section 3.1.3.5, "Using the Oracle BAM 11g Samples After Upgrade from Oracle BAM 10g"
Before you upgrade the Oracle BAM 11g schema to 11g, you must first apply patch 6522654 to your Oracle Database 10g (10.2.0.3), 10g (10.1.2.0.4), and Oracle Database 11g (11.1.0.7).
If you do not apply this patch, then you will likely experience the following error during Oracle BAM schema upgrade:
BAM MRUA: SCHEMA UPGRADE FAILED SQLException: ORA-39002: invalid operation
For more information, see Section 3.1.1, "Patches Required to Address Specific Upgrade and Compatibility Requirements".
When an alert in Oracle BAM 10g is dependent upon another alert, the dependent alert keeps a reference to the parent alert with a GUID reference. When such an alert is exported from 10g it will contain a GUID reference to the parent alert, and import to an Oracle BAM 11g system is not successful.
The following modification to the exported alert definition file can be used as a workaround for import to an Oracle BAM 11g system.
Edit the exported file contents of the dependent alert from the Oracle BAM 10g system, and modify the following element containing reference to parent alert.
Change this:
<param name="RuleID" order="0"> //private:weblogic/Rule/624567ffe84de34c-6e6bdbaa120eb7f6ea6-8000 </param>
To this:
<param name="RuleID" order="0"> ParentAlertName </param>
In other words, the GUID reference for parent alert must be replaced by the parent alert's name.
If you created a report in Oracle BAM 10g or in Oracle BAM 11g Release 1 (11.1.1.1.0) and the report contains calculated fields that use using datetime type fields, then the Calculations tab displays this error in Oracle BAM 11g Release 1 (11.1.1.2.0):
BAM-01610: INVALID FILTER EXPRESSION
More specifically, this error occurs when the calculation is an expression for equality check against a datetime field in String format. For example, for a datetime field such as Last Modified, the following calculation does not work:
If {Last Modified}=="7/18/2002 1:33:10 PM"
Before you can upgrade the report, you must remove the calculated fields.
After upgrading to Oracle BAM 11g Release 1 (11.1.1.2.0), any calculated fields in your reports will reference fields by the field ID, rather than the field name.
Specifically, after upgrade, the field name referenced in the expression will be converted to use the field id (for example, _Num_Sold).
For example, the field reference might appear as follows after the upgrade:
If({_Num_Sold}==5000)
Then("met")
Else("notmet")
Note that the calculated fields will continue to work after the upgrade and after this automatic conversion.
When you install Oracle BAM 11g, the installer copies a set of sample applications to the Oracle SOA Suite Oracle home. Refer to the following sections for more information about using these samples after upgrading to Oracle BAM 11g from Oracle BAM 10g:
For information about using the Oracle BAM 11g after migrating from Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0), see Section 3.2.7, "Using the Oracle BAM 11g Prepackaged Samples After Migrating from 11.1.1.1.0".
The Oracle Fusion Middleware installer copies the Oracle BAM samples to the following location in the Oracle SOA Suite Oracle home:
SOA_ORACLE_HOME/bam/samples/bam/
Instructions for configuring and using the samples, as well as updated samples, can be found at the following URL on the Oracle Technology Network (OTN):
http://www.oracle.com/technology/products/integration/bam/collateral/samples11g.html
The instructions explain how to use the propert setup script to configure the demos in your Oracle BAM 11g environment. You can also find individual readme file for each demo within each sample directory.
Before you use the instructions on OTN to set up the Oracle BAM 11g samples, remove any data objects, reports, or alerts associated with any existing 10g samples.
For example, be sure to remove any artifacts associated with the Oracle BAM 10g Call Center and Atherton demos before you run the setup scripts.
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.
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.
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.
The following bugs/release notes relate to security changes for Custom WebCenter applications upgrading from 10.1.3.x:
Section 3.1.7.1, "RowSetPermission check fails with compatibility flag set"
Section 3.1.7.2, "Grants not migrated properly if application contains grants without permissions"
Section 3.1.7.3, "Shared/public credentials not found after external application deployed"
In 10.1.3, the ADF framework performed rowset, attribute, and method permission checks in addition to page permission checks. If a 10.1.3 application grants 'read' permission on the rowset and attribute and 'invoke' permission on the method for all users, then the application will behave as expected in 11R1 without any additional setup.
However, if the 10.1.3 application was designed to allow only certain users to view the rowset, attribute, or invoke method, then a special flag needs to be set to support this style of security. If this flag is not set, then anyone who has page access can view attributes and rowsets and invoke methods since in 11R1 the permission check is performed only on pages and taskflows. The flag must be set for each application in the adf-config.xml file.
<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>
Grants are not migrated properly if a 10.1.3 application contains grants without any permissions. Developers should inspect the app-jazn-data.xml file in the 10.1.3 workspace and remove any grants that have empty permission set prior to performing the migration.
If you have secured your 10.1.3 application, ensure there are no duplicate JaasSecurityContext and CredentialStoreContext elements in the application's adf-config.xml file prior to migration.In the following example, the first JaasSecurityContext element is empty and should be removed (see "Remove entry" in the XML snippet below).
<adf-config-child xmlns="http://xmlns.oracle.com/adf/security/config">
<CredentialStoreContext
credentialStoreClass=
"oracle.adf.share.security.providers.jazn.JAZNCredentialStore"
credentialStoreDefaultUser="anonymous"
credentialStoreLocation="./credential-store.xml"/>
<JaasSecurityContext/> <!--Remove entry-->
<JaasSecurityContext
initialContextFactoryClass=
"oracle.adf.share.security.JAASInitialContextFactory"
jaasProviderClass=
"oracle.adf.share.security.providers.jazn.JAZNSecurityContext"
authorizationEnforce="true"/>
</adf-config-child>
The following release notes apply when you are upgrading Oracle B2B 10g to Oracle B2B 11g:
Section 3.1.8.1, "Service Name Is Required When Using ebMS with Oracle B2B"
Section 3.1.8.2, "Converting Wallets to Keystores for Oracle B2B 11g"
Section 3.1.8.3, "Oracle B2B UCCnet Documents Not Upgraded to 11g"
Section 3.1.8.4, "Errors in the Upgrade Log Files Even When Oracle B2B Schema Upgrade is Successful"
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.
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:
Back up the original keystore.
Use the orapki wallet pkcs12_to_jks option to convert to the keystore.
Use keytool -list to list the aliases and verify.
Use keytool -importkeystore to import the converted keystore to the backup of the original keystore (as done in Step 1)
OracleAS Integration B2B provides support for UCCnet under the Custom Document option. UCCnet is a service that enables trading partners to exchange standards-compliant data in the retail and consumer goods industries.
Note, however, that UCCnet documents are not upgraded automatically to Oracle B2B 11g. For information about using UCCnet documents in Oracle B2B 11g, see "Using the UCCnet Document Protocol" in the Oracle Fusion Middleware User's Guide for Oracle B2B.
When you use Oracle Fusion MiddlewareUpgrade Assistant upgrade the Oracle B2B schema, some errors might appear in the upgrade log files even if the Oracle B2B schema upgrade is successful.
For example, you might see an error, such as the following:
oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform
As long as the Upgrade Assistant reports that the upgrade was sucessful, these errors can be safely ignored. They will be addressed in a future release.
For more information about troubleshooting upgrade issues, including how to use the upgrade log files, see "General Troubleshooting Guidelines" in the Oracle Fusion Middleware Upgrade Planning Guide.
For more information about the Oracle B2B schema upgrade, see "If Necessary, Upgrade the B2B Schema," in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF.
After you upgrade to Oracle HTTP Server 11g, the DirectoryIndex directive in the httpd.conf set to index.html. As a result, if you go to the recommended URL to view the Oracle Fusion Middleware Welcome pages you instead see the "hello world" sample application page.
To address this issue:
Edit the httpd.conf file in the following location:
ORACLE_INSTANCE/config/OHS/ohs_component_name/
Locate the DirectoryIndex directive in the httpd.conf file and change index.html to welcome-index.html.
Restart the Oracle HTTP Server instance.
When upgrading to Oracle Internet Directory 11g, you might notice an error message in the Upgrade Assistant (Example 3-1). This error message indicates that some managed processes failed to start.
You can safely ignore this message, as long as the Upgrade Assistant messages also indicates that all components were upgraded successfully. This error occurs when the Upgrade Assistant attempts to start the Oracle Enterprise Manager agent and the agent is already running.
Example 3-1 Error Message When Upgrading Oracle Internet Directory
-----------------------------------------------------------
Starting Destination Components
Starting OPMN and managed processes in the destination Oracle instance.
->UPGAST-00141: startup of 11g OPMN managed processes failed.
Starting WebLogic managed server wls_ods1
Clicked OK to continue
Upgrade Progress 100%
All components were upgraded successfully.
------------------------------------------------------------
Appendix A of the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF provides an example of how to use Oracle JDeveloper 11g upgrade and redeploy a complex application on Oracle Fusion Middleware 11g.
However, after you install Oracle Fusion Middleware 11g (11.1.1.3.0), you must perform the following additional tasks before you can successfully compile and deploy the application with Oracle JDeveloper 11g:
Before you open and upgrade the application with Oracle JDeveloper 11g, edit the original web.xml and replace the <web-app> element with the following:
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
version="2.5" xmlns="http://java.sun.com/xml/ns/javaee">
Follow the steps in Appendix A of the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF to open the SOA Order Booking application in Oracle JDeveloper 11g and to upgrade the projects within the application.
When you get to Section A.8.10, "ApproveOrderTaskForm," open the web.xml and verify that it contains a <servlet> element and <servlet_mapping> element for the WFTTaskUpdate servlet.
If such an element does not exist in the web.xml file, then edit the web.xml file and add the elements shown in Example 3-2.
Continue with the rest of the instructions for deploying the project.
Example 3-2 Servlet Elements to Add to the SOA Order Booking web.xml File
<servlet>
<servlet-name>
WFTaskUpdate
</servlet-name>
<servlet-class>
oracle.bpel.services.workflow.worklist.servlet.WFTaskUpdate
</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>
WFTaskUpdate
</servlet-name>
<url-pattern>
/WFTaskUpdate
</url-pattern>
</servlet-mapping>
By default, if you deploy an upgraded Oracle SOA Suite 10g Release 3 (10.1.3) application that includes a Human Taskflow project on Oracle Fusion Middleware 11g (11.1.1.3.0), you will not be able to view the taskflow details.
To work around this problem, perform the following additional steps when you are deploying an application with a Human Taskflow project:
Before you open and upgrade the application with Oracle JDeveloper 11g, edit the original web.xml and replace the <web-app> element with the following:
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
version="2.5" xmlns="http://java.sun.com/xml/ns/javaee">
After you open and upgrade the application in Oracle JDeveloper 11g, do the following:
In Oracle JDeveloper 11g, deploy the application to an EAR file.
Expand the EAR file on disk, and then expand the packaged WAR file on disk.
For example:
jar -xvf ear_file_name.ear jar -xvf war_file_name.war
Open the web.xml file in the WEB-INF directory of the WAR file and comment out the following entry:
<!--servlet-mapping>
<servlet-name>jsp</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping-->
Repackage WAR and subsequently the EAR.
For example:
jar -cvf war_file_name.war * jar -cvf ear_file_name.ear *
Deploy the EAR using the WebLogic Administration Console.
Note that is important that you use the Oracle WebLogic Server Administration Console to deploy the application and not Oracle JDeveloper 11g. This is because Oracle JDeveloper forces a rebuild of the applciation and your changes will be overwritten.
When upgrading Oracle Virtual Directory to 11g, you must manually stop Oracle Virtual Directory processes if multiple Oracle Virtual Directory processes are running. When you attempt to stop Oracle Virtual Directory, only the last process that started will stop. If multiple Oracle Virtual Directory processes are running, you must use the kill -9 command to stop the processes before upgrading to Oracle Virtual Directory 11g.
If Oracle Internet Directory upgrade fails during the Examine phase in the upgrade process, do not modify the input you entered in the screens. Instead, dismiss the Upgrade Assistant wizard and the upgrade process again.
When running the Upgrade Assistant to upgrade the Oracle Single Sign-On 10g to Oracle Access Manager 11g, you must run the Upgrade Assistant from the same machine where your Oracle Access Manager Managed Server is running.
For some upgrade scenarios, the Oracle Fusion Middleware Upgrade Assistant provides a Verify feature that attempts to analyze the upgraded 11g environment. When you run the Verify feature, the Upgrade Assistant automatically reports any problems it finds with the upgraded environment.
However, there are cases where the Verify feature incorrectly identifies a problem. For example, when single sign-on is enabled, the Verify feature might report that it cannot access specific URLs for the upgraded components.
In these cases, you should enter the URL directly into a Web browser to verify the URL. In those cases, the URL might indeed be valid and you can ignore the errors generated by the Verify feature.
When you start the Oracle Fusion Middleware Upgrade Assistant to begin an upgrade of the Oracle Identity and Access Management products, the Upgrade Assistant might display an error message in the terminal window that indicates that the following file is missing:
temp\jdk_version.log
If you see this error, quit the Upgrade Assistant and manually create the following directory before running the Upgrade Assistant:
ORACLE_HOME/upgrade/temp
In this example, ORACLE_HOME is the directory where Oracle Identity and Access Manager product is installed.
When you upgrade your Oracle SOA Suite 10g projects to Oracle SOA Suite 11g, test suites defined in your Oracle JDeveloper projects will not be upgraded to 11g. In most cases, you will have to modify or recreate your test suites in Oracle JDeveloper 11g.
For more information, refer to the following:
"Correcting Problems With Oracle BPEL Process Manager Test Suites" in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF
"Automating Testing of SOA Composite Applications" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite
When you migrate certain Oracle SOA Suite 10g projects to 11g, the migration tool wires the composite incorrectly. This occurs if there are duplicate porttypes or partnerlinktypes.
The workaround for this issue is to make sure that the porttypes or partnerlinktypes are unique, and adjust the references before you start the migration process.
This section describes general issue and workarounds that apply only if you are starting with Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) and you are using the instructions in Appendix B, "Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)" in the Oracle Fusion Middleware Patching Guide.
This section includes the following topics:
Section 3.2.2, "Patching the Schema for Oracle Internet Directory"
Section 3.2.3, "Changing the patchmaster.ValidationErrorContinue Property"
Section 3.2.4, "Changing the Default Setting for Validation Tasks"
Section 3.2.5, "Severe Error When Running the execute-sql-rcu Macro"
Section 3.2.6, "Machine Names Do Not Appear in the Oracle WebLogic Server Administration Console"
Section 3.2.7, "Using the Oracle BAM 11g Prepackaged Samples After Migrating from 11.1.1.1.0"
While stopping the 11.1.1.2.0 domain by using the ant master-stop-domain-new command, you may see the following exceptions if the Administration Server and the Managed Servers are down:
java.net.ConnectException: Connection refused: connect; No available router to destination.
The admin server and the managed servers should be up while running the command.
While patching the schema for Oracle Internet Directory, ensure that you specify only OID as the parameter for the patchMaster.Componentlist property in the patchMaster.properties file.
By default, the patchMaster.ValidationErrorContinue file appears as patchmaster.ValidationErrorContinue. When you run this property, an error occurs.
Therefore, if you are using this property, replace the default property with patchMaster.ValidationErrorContinue before running Patch Assistant.
Patch Assistant validates the properties specified in the patchMaster.properties file. Additionally it performs the following validation tasks:
Verify whether the potential source, target home, and instance paths exist.
Verify locations to discover it they are an instance, home, and so on.
Validate individual migration task. For example, if you are migrating a domain, then schema-based properties are not required. If the schema-based properties are specified, be sure to set the complete and proper set of schema-based properties.
Attempts to recognize exceptions to specific components. For example, if Oracle Internet Directory is solely specified as the component being patched, then the property patchMaster.Schemaprefix is not necessary. However, if other components are being patched, then it is assumed that patchMaster.Schemaprefix is a necessary part of schema property validation.
If you want to continue with the Patch Assistant task after a validation error occurs, then you can open the patchMaster.properties file (Located in your patchMaster directory) in a text editor, and change the value to true for the patchMaster.ValidationErrorContinue property (The default value is false). Alternatively, you can use the Ant command-line utility to override the properties set in the patchMaster.properties file. You must specify the required property on the command line as follows:
ant-DpatchMaster.ValidationErrorContinue
When running the execute-sql-rcu macro, you may see the following error message, while the SQL script is still running:
[java] SEVERE: Error while registering Oracle JDBC Diagnosability MBean. [java] java.security.AccessControlException: access denied (javax.management.MBeanTrustPermission register)
To resolve this error, you must grant the register permission by adding the following syntax to the java.policy file (Located at JAVA_HOME/jre/lib/security in UNIX and JAVA_HOME\jre\lib\security in Windows):
.
grant codeBase "file:${PATCH-MASTER-HOME}/lib/*.jar" {
permission javax.management.MBeanTrustPermission "register";
};
Note:
Ensure that you replace{PATCH-MASTER-HOME} with your home path.After running Patch Assistant, you cannot see the list of machines (Machine-0 and Machine-1) configured during 11.1.1.1.0 and 11.1.1.2.0, in the Oracle WebLogic Server Administration Console. After migrating to 11.1.1.2.0, you must re-enter the machine names using the Oracle WebLogic Server Administration Console. For more information, see Create and configure machines topic in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.
If you are using the Oracle BAM 11g sample applications, refer to the following sections for information about using the samples after migrating from Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0):
Section 3.2.7.1, "Configuring the Oracle BAM 11g Samples After Migrating from 11.1.1.1.0"
Section 3.2.7.2, "Using the Foreign Exchange Sample After Migrating from 11.1.1.1.0"
For more information about the Oracle BAM 11g samples, see Section 3.1.3.5.1, "General Information About the Oracle BAM Samples".
After you migrate from Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) to 11g Release 1 (11.1.1.2.0), be sure to run the proper setup script for setting up samples. Specifically, you must run the recreate script instead of the setup script.
For more information, see the readme file for each of the Oracle BAM 11g samples.
After you run the recreate script to set up the Foreign Exchange sample after migrating from 11.1.1.1.0, you might experience the following error when you open the report (Shared Reports/Demos/Foreign Exchange):
The "Trade Volume" has an error: CACHEEXCEPTION_NULL_NULL_NULL Message:BAM-01274: The field ID 1 is not recognized.
To fix this problem, perform the following steps:
Open Active Studio.
Open the report:
Shared Reports/Demos/Foreign Exchange/SLAViolation Report
Click Edit.
Select the Trade Volume view and click Edit View.
In the Fields tab under Group By, select the field GroupBy.
Go to the Surface Prompts tab.
From the Display in drop-down menu, in select View Title.
Click Apply and save the report.
Visit the Oracle BAM samples page on OTN regularly to obtain updated samples and more information about the Oracle BAM sample applications.
This section provides documentation errata for the following guides:
This section contains documentation errata for the Oracle Fusion Middleware Upgrade Guide for Java EE. It contains the following sections:
Section 7.5.2, "Verifying and Updating the Oracle HTTP Server and Oracle Web Cache Ports After Upgrade" in the Oracle Fusion Middleware Upgrade Guide for Java EE provides information about additional post-upgrade steps you must perform for Oracle HTTP Server in some situations.
Specifically, if you decide to use the new ports defined for your Oracle Fusion Middleware 11g installation, rather than ports used for your Oracle Application Server 10g installation, then you should verify the listening ports, origin servers, site definitions, and site-to-server mapping settings, and make changes if appropriate.
This section fails to mention that you should perform this task even if the Oracle HTTP Server instance and Oracle Web Cache instance reside in the same Oracle home and you upgrade them together.
For example, if you have enabled end-to-end SSL in your 10g environment, then you must edit the ssl.conf file in the upgraded Oracle home to ensure that the ServerName entry in the Oracle HTTP Server 11g ssl.conf file is correct. Locate the ssl.conf file in the Oracle Fusion Middleware 11g Oracle home, and verify that the ServerName directive is set to the 11g Oracle Web Cache host and listening port:
For example:
ServerName testbox01.example.com:443
|
 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|