I have to do a little excursion here:
With 10.x (on Linux), engine dumps were happening once every few weeks. We monitored them and if one happened, reported it to Automic.
With 12.0 and 12.1 (also on Linux), the engine was initially dumping every night, sometimes multiple times. We tried to go through with filing support tickets, but were either told to upgrade or no acceptable resolution could be offered.
We have since created an internal Wiki page were we merely catalog the dump messages and try to assess if they mean anything we need to worry about. From that page, I see that we had similar messages, but not the same:
U0005118 Program error: Database access via key 'RH_AH_Idnr' with value 0 in module 'UCUREP'.
From the comment on the Wiki page, I do believe a colleague filed a support ticket, but didn't get any conclusive answers (I can obviously not research this because all old support tickets are since inaccessible).
We are since ignoring this message with no immediately related negative consequences.
Not saying this is good, just saying this is the current state of affairs because with many dump messages, we didn't really get anywhere with Automic.
Br,
Carsten
Original Message:
Sent: 08-30-2019 01:06 PM
From: Gates
Subject: forced system traces
Has anybody seen this in their V12 linux systems?? Seems like after migrating to linux we have had this type of error twice now..
Never had these type of messages on aix...
The error we are getting over and over non stop is
20190830/115720.249 - U00003631 Dump caused by:
20190830/115720.249 - U00005118 Program error: Database access via key 'AH_Idnr' with value 0 in module 'JPEXEC_R'.
We are running v12.2.3.hf1... but we saw this same type of error in v12.2.0.hf2..
Supports response... was to upgrade to the latest release.. well.. now I am seeing it in v12.2.3.hf1??
I have a ticket opened with support.. but hope their answer is to upgrade to v12.3.* as that's not acceptable..
Has anybody else been having these types of errors running V12? on linux?
thanks