Last updated on SEPTEMBER 16, 2016
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.
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;
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms