Essbase: After Applying Analytic Provider Services (APS) Patch 22.214.171.124.022/023, LCM and FDMEE export of Data fails: /Databases/dbname/Data:- Cannot copy Essbase file object. Error writing client file Essbase Error(1053014): Object temp077371484976832_1
(Doc ID 2370032.1)
Last updated on FEBRUARY 06, 2019
Applies to:Hyperion Essbase - Version 126.96.36.199.022 and later
Information in this document applies to any platform.
After Applying Analytic Provider Services Patch Set Update (PSU) 188.8.131.52.022 (27057280) or 184.108.40.206.023 (27397232), getting an error when exporting an Essbase Database using Life Cycle Management (LCM):
EPMLCM-14000: Error reported from Essbase.
/Databases/<dbname>/Data:- Cannot copy Essbase file object. Error writing client fileCannot copy Essbase file object. Error writing client file.Cannot get olap file object. Essbase Error(1053014): Object temp077371484976832_1 does not exist
This issue does not occur in single-machine deployments where Essbase and Analytic Provider Services are on same machine. This issue only occurs in a distributed setup where Analytic Provider Services and Essbase are deployed on different machines.
Note: Similar issue occurs when exporting Essbase Data using Oracle Hyperion Financial Data Quality Management, Enterprise Edition (FDMEE)
aif_apsserver.log states: Error In COMM Load Data "Cannot get olap file object information. Essbase Error(1053014) Object xxx does not exist"
APS was patched to 220.127.116.11.022 or 18.104.22.168.023
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