PIN_INV_ACCTS Is Exiting With Core Dump When Run With 'Detail' Option (Doc ID 1055249.1)

Last updated on SEPTEMBER 06, 2010

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.1.0.0 and later   [Release: 7.3.1 and later ]
Information in this document applies to any platform.

Symptoms

When one tries to generate Detailed Invoice for a bill using pin_inv_accts with -detail option, the process might exit with core dump.

This is the syntax of the command :
    pin_inv_accts -detail <file.txt>

file.txt contains :
    0 PIN_FLD_RESULTS ARRAY [0]
    1 PIN_FLD_POID POID [0] 0.0.0.1 /bill 193590006 0

stack trace of the core :

_$#$_ core 'core' of 21286:
pin_inv_accts -verbose -detail pin_flist_detailed_bill
----------------- lwp# 1 / thread# 1 --------------------
fdfd6328 _smalloc (10, 0, e8124, fdfd64b8, fe0c1910, fe0c72b4) + 98
fdfd6394 malloc (10, 1, e8070, fe036af4, fe0be3c0, fe0c85b8) + 4c
0002e738 pin_mta_thread_table_insert (4, ffbff1b8, ffbff1b8, 20ffc, feb64244, 4f710) + 70
0002e460 pin_mta_create_workers (5, 20e70, 0, ffbff1b8, 1400, 212f0) + a0
00020958 pin_mta_main_thread (0, 62638, ffbff1b8, 0, 1f4, 4f710) + 3b8
000237e0 main (4, 62638, 6de18, 3b69c, 2, 4f710) + 584
00017638 _start (0, 0, 0, 0, 0, 0) + 108
----------------- lwp# 2 / thread# 2 --------------------
fe04a914 stat (fe964c3c, 0, 0, fdb7be88, fdb7be18, fdb7be18) + 8
fe935ee8 pin_conf (fe964c3c, fe964c40, 1, fdb7be8c, fdb7be88, 0) + 5c
fe91a334 pcm_connect (fdb7bf9c, fdb7bf90, fdb7bf38, 800, 335, 17) + 98
00021118 pin_mta_worker (800, 2, 800, 327, 858, 85c) + 2a8
fe046d4c _lwp_start (0, 0, 0, 0, 0, 0)
----------------- lwp# 3 / thread# 3 --------------------
fe04ada8 _write (3aef4, 1, 0, fe0c3444, 8, 3aef4) + c
fe019dac _dowrite (3aef4, 8, fe0c3444, fda7be18, 6, 2b) + 54
fe01a2d4 _ndoprnt (3aefc, fda7bedc, fda7b759, 8, 20, fda7b994) + 350
fe01dad4 fprintf (fe0c3444, 3aef4, 3, a09b8, 323f4, fe0be3c0) + e0
000210e4 pin_mta_worker (800, 3, 800, 327, 858, 85c) + 274
fe046d4c _lwp_start (0, 0, 0, 0, 0, 0)
----------------- lwp# 4 / thread# 4 --------------------
fe046df0 __lwp_park (fdba1200, 0, fe0c1910, 0, 1c00, 1d3c) + 14
fdfd638c malloc (120, 1, e8070, 0, fe0be3c0, fe0c85b8) + 44
fe94b64c pcmmem_malloc_flisthdr (fe988d30, 1f20, fe03e1cc, fe980d08, 356e8, 1c00) + 38
fe92453c pin_flist_create_with_size (14, fd97bf38, fd97bf38, 0, 5c814, fe03ee44) + 54
fe9244c8 pin_flist_create (fd97bf38, 3aeb8, 0, fe0404e8, 800, 313) + 54
00020f40 pin_mta_worker (0, 4, 0, 0, 20e70, 1) + d0
fe046d4c _lwp_start (0, 0, 0, 0, 0, 0)


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