The following topics are covered in this chapter:
This section contains the following topics:
When upgrading from 11g (11.1.1.7 or 11.1.1.9) to 12.2.1, the Upgrade Assistant fails to load schemas associated with the domain when All schemas used by a Domain is selected.
The following exception is logged:
Exception ------------- UPGAST- 00214 - Unable to connect to database as schema user <prefix>_IAU. Listener refused the connection with the following error : . ORA-12504, TNS : Listener was not given the SID in CONNECT_DATA . Cause : The database connection failed for the specified reason. Action : Correct the problem using information provided in the log file; then retry the operation. In particular if the indicated reason is "Login has timed out" verify that the host and port are correct and make sure the database is up and is configured for network access.
To work around this issue:
Restart the Upgrade Assistant, enter the 11g domain location, select Individually Selected Schemas, and select the correct _IAU. _SOAINFRA, and _OPSS schemas.
Selecting the SOA and OPSS schemas will ensure that Audit Services, User Messaging Service and MDS schemas are selected automatically.
When upgrading from 11.1.1.9 to 12.2.1, Oracle Business Process Management (BPM) composites are not compiled post upgrade.
To compile the BPM composites after the upgrade, restart the Oracle SOA Server.
The following example shows the error that is received:
[soa_server1] [ERROR] [] Exception while loading process [[ ORABPEL-01005 Failed to compile bpel generated classes. failure to compile the generated BPEL classes for BPEL process The class path setting is incorrect. Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL process is depending on are deployed correctly. Also verify that the run time is using the same release/version.
ua.bat
script:ConnectionHelper: CIE config framework not located/initialized.
oracle_common/upgrade/bin/ua
[ua.bat
] script and change the following jar file names:cieCfg_wls_external_lib.jar
must be changed to cieCfg_wls_lib.jar
cieCfg_cam_external_lib.jar
must be changed to cieCfg_cam_lib.jar
After an upgrade to 12c, the Performance Per Participant graph that is displayed on standard Workspace dashboards will only be available for new 12c instances and will not be available for in-flight, hybrid, or completed (closed) 11g instances. However, custom 12c Workspace dashboards will continue to display the participant information.
The following exception appears in the reconfig.log
file after invoking the Reconfiguration Wizard with -log_priority=ALL
:
[org.xml.sax.SAXParseException; lineNumber: 3; columnNumber: 77; cvc-elt.1: Cannot find the declaration of element 'stringSubsInfo'.]
You can ignore this exception.
Instances that were created using a non-Oracle database cannot be migrated to Oracle Fusion Middleware 12c.
To migrate the closed instances from Oracle Fusion Middleware 11g to Oracle Fusion Middleware 12c, you must create a new 12c SOA domain using a supported Oracle database. Active 11g instances must be completed using the existing 11g server.
The following exception appears in the reconfig.log
file after invoking the Reconfiguration Wizard with -log_priority=ALL
:
java.util.MissingResourceException: No bundle found for base name config-template
You can ignore this exception.
Analytics data for 11g (11.1.1.7) composites without any roles defined in them will not be migrated to 12c.
When you run the Configuration Wizard after upgrading your Oracle Fusion Middleware products from Release 11g (11.1.1.6) to Release 12c, the MDS schema data might not be populated in the schema table on the JDBC Component Schema screen.
You must manually enter MDS schema data into the schema table on the JDBC Component Schema screen before continuing.
After you upgrade Oracle SOA Suite from Release 11g (11.1.1.6) MLR to Release 12c, you should be able to select a Notification Queue from the Oracle SOA Suite for Healthcare Integration Runtime Settings.
However, Oracle SOA Suite for Healthcare Integration does not display the JMS Send to Internal channels in the Notification Queue drop-down list after you upgrade.
To work around this issue, change or update other Oracle SOA Suite for Healthcare Integration runtime settings and save the changes. Then, Oracle SOA Suite for Healthcare Integration should display the JMS Send to Internal channels in the Notification Queue list.
When you log into Oracle Business Process Composer after upgrading your environment from Release 11g (11.1.1.7) to Release 12c, process migration is launched. After migration finishes, a default space is created and projects are migrated. However, the composer appears to freeze.
As a workaround, log out of the composer, close the browser, and clear the browser cache. You can then log in again to continue working in the composer.
While upgrading your Oracle HTTP Server from Release 11g (11.1.1.7) to 12c when you have a Managed Server being upgraded in the same domain as your HTTP Server and when you have a customized port value for the Node Manager, the Reconfiguration Wizard upgrades the Node Manager and the Managed Server successfully. However, when you run the Upgrade Assistant to upgrade the component configurations, the Upgrade Assistant overwrites the customized Node Manager configuration with the default values for the Node Manager host and port. As a result, a new machine entry is created in the WebLogic Server Administration Console. And, the Managed Server is assigned to this new, non-working machine set by the Reconfiguration Wizard.
After running Upgrade Assistant, if config.xml
has any Oracle HTTP Server instances referring to the duplicate Node Manager, then follow the steps below to correct these instances:
Backlogged events in the EDN-JMS queue do not migrate when you upgrade from Oracle Fusion Middleware 11g to Oracle Fusion Middleware 12c.
Before you upgrade, check if there are any backlogged events in the JMS queue. After you finish upgrading, verify that these backlogged events are not in the queue.
You can verify if there are any backlogged events in the JMS queue via the Oracle WebLogic Server Administration Console:
This section contains the following topic:
If the OPatch postscript fails and users choose not to proceed with the patching process and quit, OPatch does not restore regenerated libraries correctly.
Check the OPatch log to determine whether or not library regeneration has occurred. If the library regeneration has occurred, apply the patch again. If the OPatch postscript fails again, choose y
to proceed with the patching process. OPatch will not roll back the patch automatically this time; the user needs to roll back OPatch manually to restore the pre-patch environment.
For information on how to roll back a patch, see Using OPatch to Patch Oracle Fusion Middleware in Patching with OPatch.