Pin_collections_send_dunning Fails with Coredump (Doc ID 2250271.1)

Last updated on APRIL 11, 2017

Applies to:

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

Goal

After applying PS17, pin_collections_send_dunning fails with memory fault(coredump). It even does not work with help option.

[dev00@entdev00.xxxx.local]-/opt/brm/dev00/7.5/opt/apps/pin_collections> pin_collections_send_dunning -verbose -export ./dunning
Memory fault(coredump)
[dev00@entdev00.xxxx.local]-/opt/brm/dev00/7.5/opt/apps/pin_collections> pin_collections_send_dunning -help
Memory fault(coredump)
[dev00@entdev00.xxxx.local]-/opt/brm/dev00/7.5/opt/apps/pin_collections> pin_collections_send_dunning -h
Memory fault(coredump)


[dev00@entdev00.xxxx.local]-/opt/brm/dev00/7.5/opt/apps/pin_collections> gdb $PIN_HOME/bin/pin_collections_send_dunning core.39028
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /opt/brm/dev00/7.5/opt/bin/pin_collections_send_dunning...(no debugging symbols found)...done.

warning: core file may not match specified executable file.
[New LWP 39028]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `pin_collections_send_dunning -verbose -export ./dunning'.
Program terminated with signal 11, Segmentation fault.
#0 0x0805067f in pin_mta_config ()
Missing separate debuginfos, use: debuginfo-install glibc-2.17-157.el7_3.1.i686 libgcc-4.8.5-11.el7.i686 nss-softokn-freebl-3.16.2.3-14.4.el7.i686
(gdb) bt
#0 0x0805067f in pin_mta_config ()
#1 0x0805f0ec in main ()
(gdb) q


What is the reason behind this issue ?
 

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