What to do if the acsCompilerDaemon Reports the Following Error "successDataCompile: Error updating data for success" and Control Plans are Left in a "Build" State
(Doc ID 1183933.1)
Last updated on FEBRUARY 14, 2019
Applies to:Oracle Communications Network Charging and Control - Version 2.2.0 to 2.4.0 [Release 2.2 to 2.4]
Information in this document applies to any platform.
There is a known issue where database deadlock errors can occur when the acsCompilerDaemon becomes overloaded during a bulk load of new Control Plans. If this happens, the Control Plans become stuck in the build state, and are unusable until the affected Control Plans are re-compiled.
If this occurs, you will see the following error messages in the acsCompileDaemon logs.
Jul 21 14:35:44.114565 acsCompilerDaemon(19679) ERROR: successDataCompile: Error updating data for success
Jul 21 14:35:44.114913 acsCompilerDaemon(19679) ERROR: ORA-00060: deadlock detected while waiting for resource
ORA-06512: at "ACS_ADMIN.ACS_CP_PURGE_DT", line 27
ORA-04088: error during execution of trigger 'ACS_ADMIN.ACS_CP_PURGE_DT'
ORA-06512: at "ACS_ADMIN.ACS_CP_PURGE_TT", line 3
ORA-04088: error during execution of trigger 'ACS_ADMIN.ACS_CP_PURGE_TT'
ORA-06512: at line 1
If these errors messages are found then you will need to go into the SMF database, on the SMS, to determine how many Control Plans are stuck in the build (B) state.
SQL> SELECT DISTINCT(build), COUNT(*) FROM acs_call_plan GROUP BY build;
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