HPCM - Essbase Cube Not Being Created Via Import Template Method
(Doc ID 2732040.1)
Last updated on OCTOBER 10, 2022
Applies to:
Hyperion Profitability and Cost Management - Version 11.2.1.0.000 and laterInformation in this document applies to any platform.
Symptoms
In HPCM 11.2.1 while creating an application through the Import template, it fails if the Essbase cluster name is other than default.
While importing the template, the Essbase Application Server can be changed from the default application name, which is EssbaseCluster-1. When changing it, for example, to TEST1 and selecting this server name during import it does not get applied.
Changes
While importing an application via the Import Template method there is an option to select to which Essbase application cluster to deploy. That value is being ignored and HPCM tries to deploy it to the default essbase
cluster, which is EssbaseCluster-1. This causes a failure as such cluster doesn't exist on the environment.
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 |