#1 0x00c1ed23 in __waitpid_nocancel () from /lib/tls/libc.so.6
#2 0x00bc87a9 in do_system () from /lib/tls/libc.so.6
#3 0x00d0a98d in system () from /lib/tls/libpthread.so.0
#4 0xf7e357ea in printExceptionReport ()
#5 0xf7e2e3e2 in sigsegv_handler () from /opt/portal/7.3/lib/libcm_main.so
#6 <signal handler called>
#7 0xf7ed5a3c in pini_flist_find () from /opt/portal/7.3/lib/libcmpin.so
#8 0xf7ef5fab in pin_flist_elem_get_next ()
#9 0xf6cd2cbd in fm_subs_utils_rerating_event_search_one_account ()
#10 0x20393956 in ?? ()
#11 0x4620726f in ?? ()
#12 0x20303031 in ?? ()
#13 0x3156203d in ?? ()
#14 0xff003030 in ?? ()
#15 0xffffc900 in ?? ()
#16 0x00000000 in ?? ()
If we do not include the billinfo object in Flist and using the PIN_FLD_RERATE_FLAGS= 0 the rerating ends with no errors.
When the rerating finishes with no errors we can see that in function fm_subs_utils_rerating_event_search_one_account (that fails in the previous case) the event search flist is generated in which balance groups are used as arguments. Obviously this will not work if the balance group number is more than 31 due to the DM’s limitation of arguments number.
Is there some opportunity to run the selective rerating on one billinfo with more than 50 services?
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