After Rolling Back Essbase Patches From .029 To .018 And EAS .016 Allocations rules are Failing.
(Doc ID 2576073.1)
Last updated on NOVEMBER 02, 2022
Applies to:Hyperion Profitability and Cost Management - Version 184.108.40.206.123 and later
Information in this document applies to any platform.
Rolled back Essbase patches from 220.127.116.11.029 to 18.104.22.168.018 and EAS 22.214.171.124.016.
At fist allocation would not run, but eventually users can no longer log into HPCM application:
FAILED HTTP: HTTP Checking availability of HTTP context http://EDCWHPNS011.bcbsfl.com:19000/profitability/ping.jsp
Error: Bad response codes with both GET and POST methods: 404 and 404
Recommended Action: Check that the application is started
###<Jul 8, 2019 11:34:54 AM EDT> <Error> <Deployer> <ABCE123456> <Profitability0> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <
weblogic.application.ModuleException: Unable to resolve 'jdbc.profitability_datasource'. Resolved 'jdbc'...
Caused By: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.profitability_datasource'. Resolved 'jdbc'; remaining name 'profitability_datasource'
####<Jul 8, 2019 11:34:34 AM EDT> <Error> <Deployer> <ABCE123456> <Profitability0> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <
Caused By: weblogic.common.ResourceException: Connection Pool profitability_datasource: initial size (20) is greater than maximum size (15)
Rolled back Essbase patches due to inability to run allocations.
Reconfigured foundation and HPCM as result of validation messages in the validation report after rolling back the Essbase patches.
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