Pin_deferred_act Is Returning Non-zero Error Code For Worker Thread Failure Scenario (Doc ID 1625651.1)

Last updated on MARCH 10, 2014

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Goal

 If there are any worker thread failures, pin_deferred_act execution is returning non-zero error code in BRM 7.5  where as it was returning 0 in BRM 7.2.1 for the exact same worker thread failed scenario.


Example:

BRM 7.5
============


=->pin_deferred_act -verbose
Thread (4153158544) begins ...
Thread (4142668688) begins ...
        Fetched units per step: (1)
Total Fetched (1) units, err 0
Fetched (1) units in Total.
Thread (4153158544) exits ...
Thread (4142668688) exits ...
Total number of records processed = 1.
Number of data errors encountered = 1.
Total number of errors encountered = 1.


=->echo $?
106

 

Note: PIN_ERR_RETRYABLE (106) – If no system errors occurred but at least one worker-opcode error occurred

BRM 7.2
=============


=-> pin_deferred_act -verbose
Thread (2) begins ...
Thread (3) begins ...
        Fetched units per step: (1)
Total Fetched (1) units, err 0
Fetched (1) units in Total.
Thread (2) exits ...
Thread (3) exits ...
Total number of records processed = 1.
Number of data errors encountered = 1.
Total number of errors encountered = 1.


=-> echo $?
0


Is this the correct behavior?

Any reason why pin_deferred_act is returning non-zero value in case if there are any worker thread failures? This behavior is not same as other MTA applications in BRM.

 

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms