3 Patching and Upgrade
The following topics are covered in this chapter:
Issues Related to Product Upgrade
This section contains the following topics:
- Incorrect Version Numbers After a Reduced Downtime Upgrade
Depending on the upgrade procedure you use to upgrade to 12c (12.2.1.4.0), you may notice that the post-upgrade version number and copyright year remain the same in Oracle Enterprise Manager. This is not an error. - Error Detecting MDS Schema in IPM-only Domain
- Upgrade Assistant Cannot Read a Domain with Multi-Data Sources Defined
- Standard Workspace Dashboards Missing Participant Information After Upgrade
- MissingResourceException May Occur During Reconfiguration
- EDN-JMS Backlogged Events Do Not Migrate During Upgrade
Parent topic: Patching and Upgrade
Incorrect Version Numbers After a Reduced Downtime Upgrade
Depending on the upgrade procedure you use to upgrade to 12c (12.2.1.4.0), you may notice that the post-upgrade version number and copyright year remain the same in Oracle Enterprise Manager. This is not an error.
- The copyright version year will still show 2017 instead of 2019
- The version will be12.2.1.3.0 and the runtime version will be 12.2.1.4.0
Parent topic: Issues Related to Product Upgrade
Error Detecting MDS Schema in IPM-only Domain
If the application extension framework (AXF) is configured along with Oracle Imaging and Process Management (Oracle I/PM), then the MDS datasource gets created in the domain. If AXF is not configured, then the MDS datasource will not be created in 11g domain.
Therefore, when domain assisted schema upgrade is used in UA, MDS schema will not be detected. You can continue the upgrade without the MDS datasource.
Parent topic: Issues Related to Product Upgrade
Upgrade Assistant Cannot Read a Domain with Multi-Data Sources Defined
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
Parent topic: Issues Related to Product Upgrade
Standard Workspace Dashboards Missing Participant Information After Upgrade
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.
Parent topic: Issues Related to Product Upgrade
MissingResourceException May Occur During Reconfiguration
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.
Parent topic: Issues Related to Product Upgrade
EDN-JMS Backlogged Events Do Not Migrate During Upgrade
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:
- From the Domain Structure, select soainfra, then Services, Messaging, JMS Modules, SOAJMSModule, and EDNQueue.
- Select Monitoring tab.
- Select SOAJMSModule and EDNQueue, and then click Show Messages.
Parent topic: Issues Related to Product Upgrade
Issues Related to Product Patching
This section contains the following topic:
Parent topic: Patching and Upgrade
OPatch Does Not Restore Regenerated Libraries Even After User Quits the Patching Process
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.
Parent topic: Issues Related to Product Patching