Monday, March 2, 2015

R12: Revenue Recognition Execution Report signal 6

Did you know that in R12 your Revenue Recognition Execution Report can end up generating an error message of “was terminated by signal 6”?  We had that exact scenario happen to us when the business ran multiple copies of this report for the same org that started at the EXACT same second!  We did not find any hits on MOS for a resolution, so we asked the business to run them again but in sequence instead of parallel and they both completed successfully.  Searching on MOS does not yield great results, but the closest hit is note ID 1631873.1 which matches some of the error details we saw at that time, but the resolution for it is all wrong as we did not need to patch:

emsg:was terminated by signal 6
Enter Password:
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0xb740156c, pid=9281, tid=3031722560
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2_14-b05 mixed mode)
# Problematic frame:
# C  [librw.so+0x75856c]  hshuid+0xe0
#

No comments:

Post a Comment