Jan2020 WebLogic CPU Patch for Oracle RMB Environment
(Doc ID 2645881.1)
Last updated on MARCH 05, 2020
Applies to:Oracle Financial Services Revenue Management and Billing - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
This article confirms the impacts for applying Jan2020 CPU patches in the RMB environment.
a) CPU Jan2020 patch for ORMB 220.127.116.11.0 - 30693365
b) WebLogic patch - WLS PATCH SET UPDATE 18.104.22.168.0(ID:191217.1425) Patch 30675853
The concern is on the impact for deploying these patches in the RMB environment.
Also as part of Weblogic Patch 30675853 readme, we see one Post installation step as below:
WebLogic patch - WLS PATCH SET UPDATE 22.214.171.124.0(ID:191217.1425) Patch 30675853
5 Post-Installation Instructions
Note: The fix for bug 26929163 updates the runtime components for the WLS plugin for the RCU and Upgrade Assistant tools. It will prevent any future WLS schema installs or upgrades from allowing WLS schema owners to retain ANY privious once installation or upgrade have been completed. The patch will *not* affect schemas that have already been installed or upgraded to the correct schema version.
For existing installations that wish to remove the ANY privileges that have been assigned to the WLS schema owners, users can run the script located at $MW_HOME/oracle_common/common/sql/wlsservices/sql/cleanup.sql as the DBA user and provide the WLS schema owner names. For example, if the WLS schema owners are DEV1_WLS and DEV1_WLS_RUNTIME:
sqlplus cleanup.sql DEV1_WLS DEV1_WLS_RUNTIME
We also like to know if this sqlplus command is a mandatory step or not. If yes, we need to get WLS schema owner detail as well.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document