My Oracle Support Banner

After Rolling Back Essbase Patches From .029 To .018 And EAS .016 Allocations rules are Failing. (Doc ID 2576073.1)

Last updated on APRIL 13, 2021

Applies to:

Hyperion Profitability and Cost Management - Version 11.1.2.4.123 and later
Information in this document applies to any platform.

Symptoms

HPCM 11.1.2.4.xx

Rolled back Essbase patches from 111.1.2.4.029 to 111.1.2.4.018 and EAS 11.1.2.4.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

 

Profitability.log
###<Jul 8, 2019 11:34:54 AM EDT> <Error> <Deployer> <ABCE123456> <Profitability0> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <0000Mxxxxxxxxx_AaaaaA8000000> <1562600094872> <BEA-149231> <Unable to set the activation state to true for the application 'PROFITABILITY [Version=11.1.2.0]'.
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)'> <> <> <0000Mxxxxxxxx_AaaaaaA8000000> <1562600074346> <BEA-149205> <Failed to initialize the application 'profitability_datasource' due to error weblogic.application.ModuleException: .

Caused By: weblogic.common.ResourceException: Connection Pool profitability_datasource: initial size (20) is greater than maximum size (15)



Changes

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.

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.