My Oracle Support Banner

pin_bill_accts Core Dump (Doc ID 1441593.1)

Last updated on MARCH 01, 2019

Applies to:

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


On Oracle Communications Billing and Revenue Management (BRM) versions 7.4 and 7.5 up to 7.5PS3, when pin_bill_accts is executed as part of pin_bill_day run, it generates a core dump with trace shown below:

Core was generated by `pin_cycle_fees -purchase':

Program terminated with signal 6, Aborted.
#0 0xffffe402 in __kernel_vsyscall ()
(gdb) where
#0 0xffffe402 in __kernel_vsyscall ()
#1 0x001c2df0 in raise () from /<DIR>/
#2 0x001c4701 in abort () from /<DIR>/
#3 0x001fb3ab in __libc_message () from /<DIR>/
#4 0x002036c5 in _int_free () from /<DIR>/
#5 0x00203b09 in free () from /<DIR>/
#6 0x001f1db6 in fclose@@GLIBC_2.1 () from /<DIR>/
#7 0xf7d7f3b2 in pinlog_open () from /<DIR>/
#8 0xf7d7ff2e in pinlog_buf () from /<DIR>/
#9 0xf7d6a0e8 in pin_log_flist () from /<DIR>/
#10 0x0804fe02 in pin_mta_worker_job ()
#11 0x08055447 in pin_mta_worker ()
#12 0x00301832 in start_thread () from /<DIR>/
#13 0x0026c46e in clone () from /<DIR>/


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.