This content has been marked as final. Show 2 replies
The error code being returned from Essbase means that the object that is being accessed is locked:1 person found this helpful
/* Object [%s] already exists and is not locked by user [%s] */
#define AD_AMSG_OAE_ONLU 1053025
The IW36 file would need to be deleted from the Essbase Server.
We were extracting data from one essbase app and loading into another essbase app using ODI when we encountered following error.
Caused by: com.hyperion.odi.essbase.ODIEssbaseException: Cannot put olap file object. Essbase Error(1053025): Object [object name] already exists and is not locked by user [user name]
We had killed a prevoius interface execution and when we started it again, we got error above. We were using a load rule that was hosted in separate folder and ODI was copying it into into target Essbase app and using it for data load into app and removing it after data load is complete. When we killed the interface, it was loading data and it left the rul file in essbase app. When we ran the interface next time, we got error as the rule was already there in essbase app.
To fix this, we renamed the rul in essbase and interface executed fine. After that we removed the renamed rul as it was not needed in essbase app.