HPCM Error: ".... Application deployment FAILED.[[Unexpected error in business logic...." when Deploying from HPCM to Hyperion Essbase after PSU Patch Installation
(Doc ID 1495552.1)
Last updated on APRIL 18, 2024
Applies to:
Hyperion Profitability and Cost Management - Version 11.1.2.2.000 and laterInformation in this document applies to any platform.
Symptoms
When trying to deploy the HPCM application to Essbase cube BSO, the following errors are generated in the HPCM.log and the deployment is not successful.
This is what EPMA says when deploying:
"...
Detail : Initiating Product Action...
Generating Headers and Callback Information...
Generating Application Data...
Posting Product Request...
Waiting For Status Updates...
PRODUCT_UPDATE: Update from product
Creating dimensions
Deploying dimension: TestBD
Deploying dimension: Measures
Counting generation and level numbers for dimension: AllocationType
Counting generation and level numbers for dimension: TestPOV
Counting generation and level numbers for dimension: TestBD
Counting generation and level numbers for dimension: Measures
Deployment completed.
Deployment failed for application HPCMAPP"
HPCM.log:
"[2012-10-01T16:51:01.078+02:00] [Profitability0] [ERROR] [EPMPCM-09103] [oracle.EPMPCM.web] [tid: 25] [userId: <anonymous>] [ecid: 0000JcSniKDFw0l6wvBh6G1GQQjC000009,1:17174] [SRC_CLASS: com.hyperion.profitability.web.integration.epma.ApplicationManager] [APP: PROFITABILITY#11.1.2.0] [SRC_METHOD: deployAppFromXML] Application deployment FAILED.[[Unexpected error in business logic.
at com.hyperion.profitability.business.facade.DiagnosticInterceptor.invoke(DiagnosticInterceptor.java:40)
at com.hyperion.profitability.common.support.aop.InterceptingInvocation.proceed(InterceptingInvocation.java:37)
at com.hyperion.profitability.common.support.aop.InvocationHandlerAdapter.invoke(InvocationHandlerAdapter.java:34)
at $Proxy116.collectTableAndIndexStatsForDeployApp(Unknown Source)
at com.hyperion.profitability.web.delegate.ServiceDelegate.collectTableAndIndexStatsForDeployApp(ServiceDelegate.java:1405)
at com.hyperion.profitability.web.integration.epma.ApplicationManager.deployAppFromXML(ApplicationManager.java:465)
at com.hyperion.profitability.web.integration.epma.ApplicationManager.access$000(ApplicationManager.java:58)
at com.hyperion.profitability.web.integration.epma.ApplicationManager$1.run(ApplicationManager.java:294)
Caused by: java.lang.IllegalArgumentException: Calculation Process not found for Process Type = Collect Statistics
........
[2012-10-01T16:55:55.715+02:00] [Profitability0] [WARNING] [] [org.eclipse.persistence.session.zip:C:/Oracle/Middleware/user_projects/domains/EPMSystem/servers/Profitability0/tmp/servers/Profitability0/tmp/_WL_user/PROFITABILITY_11.1.2.0/mig5y6/war/WEB-INF/lib/_wl_cls_gen.jar!/_hpm] [tid: 28] [userId: <anonymous>] [ecid: 0000JcSosQbFw0l6wvBh6G1GQQjC00000L,1:17175] [APP: PROFITABILITY#11.1.2.0] [[
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00904: "JOB_WARNINGS": invalid identifier
.......
Error Code: 904
Call: SELECT id, job_comment, created_timestamp, created_userid, end_time, interrupt_flg, job_errors, job_properties, job_warnings, hpm_pov_dim_mem_grp_id, modified_timestamp, modified_userid, name, pov_name, start_time, hpm_application_id, hpm_execution_type_id, hpm_job_type_id, hpm_job_status_id FROM HPM_JOB WHERE (name = ?)
bind => [1 parameter bound]
Query: ReadAllQuery(name="JobPO.getByName" referenceClass=JobPO sql="SELECT id, job_comment, created_timestamp, created_userid, end_time, interrupt_flg, job_errors, job_properties, job_warnings, hpm_pov_dim_mem_grp_id, modified_timestamp, modified_userid, name, pov_name, start_time, hpm_application_id, hpm_execution_type_id, hpm_job_type_id, hpm_job_status_id FROM HPM_JOB WHERE (name = ?)")………………….#
Caused by: java.sql.SQLSyntaxErrorException: ORA-00904: "JOB_WARNINGS": invalid identifier"
Changes
Installation of a PSU has been performed.
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 |