Members Deleted in EPMA are not Removed from Hyperion Planning Application After Redeploy
(Doc ID 1156723.1)
Last updated on APRIL 24, 2018
Applies to:Hyperion Planning - Version 184.108.40.206.00 to 220.127.116.11.00 [Release 9.3 to 11.1]
Information in this document applies to any platform.
Deleted Members from EPMA Master library and Synchronised appliction View. However after redeploy to Hyperion Planning application, the removed EPMa members are still present in the planning application and in Essbase.
The planning log file shows the following error for each member that was supposed to be deleted from planning:
Deleting planning member xxxxx
Query Failed: SQL_DELETE_PENDING_PUOBJECTS:null
java.sql.SQLException: [Hyperion][Oracle JDBC Driver][Oracle]ORA-02292: integrity constraint (SVILHPUNITO_BPR.FK_HSP_ANNOT_OID) violated - child record found
Members removed from EPMA application.
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