Pin_deferred_act Deadlock And Stop Processing
Last updated on MARCH 26, 2013
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.3.1]
Information in this document applies to any platform.
The utility pin_deferred_act logs a deadlock error and it does not continue with remaining schedule objects, it is like a freeze symptom. After a few hours of inactivity, the DB session was killed and the process begun to work, but again it stopped to work a few minutes later (apparently locked again).
Apart from the deadlock problem, the process performance is slow (~6000 schedule objects per hour). As below, we show the execution progress up to the moment of deadlock (data obtained from table SCHEDULE_T):
ACTION_NAME DATE AND HOUR COUNT(*)
=============================== =========== =======
PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS 14/02/2013 00 1933
PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS 14/02/2013 01 6680
PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS 14/02/2013 02 6705
PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS 14/02/2013 03 5552
PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS 14/02/2013 04 2733
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