Pin_rerate Does Not Return The Right Status (Doc ID 961548.1)

Last updated on DECEMBER 22, 2009

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.0.0.0
Information in this document applies to any platform.

Symptoms

Problem Statement:

When the pin_rerate is executed with the following command :
pin_rerate -process queue

The pin_rerate mta application fails to connect to the oracle queue.

The pin_rerate mta application fails to connect to the oracle queue. The issue can be observed in
the pinlog of pin_rerate.

E Mon Aug 31 18:00:18 2009 xxxxxx pin_rerate:17191 pin_rerate.c:5857
1:xxxxxx:pin_rerate:17191:1:566:1251734418:5
error in op_rerate_process_queue
<location=PIN_ERRLOC_DM:4 class=UNKNOWN:0 errno=PIN_ERR_STORAGE:43>
<field num=0:0,0 recid=0 reserved=6576 reserved2=0 time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>
E Mon Aug 31 18:00:18 2009 xxxxxx pin_rerate:17191 pin_rerate.c:5891
1:dvedvh48:pin_rerate:17191:1:566:1251734418:5
error in pin_mta_exec_work_unit
<location=PIN_ERRLOC_DM:4 class=UNKNOWN:0 errno=PIN_ERR_STORAGE:43>
<field num=0:0,0 recid=0 reserved=6576 reserved2=0 time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>

-- Steps To Reproduce:

- In the pin.conf of pin_rerate, modify the queue name (wrong name) in order to make the pin_rerate utility fail.
- Execute the following command : pin_rerate -process queue
- An error should appear in the pinlog file.
- Execute the following command : echo $?
- The return will be 0 instead of a non zero

If 0 it means that the application successfully ended without any errors.

Expected Result

It should return an error code different from 0 as pin_rerate failed to connect to the oracle queue.

 




Cause

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