Thanks for your inputs. It looks like this is the case for us. While the AH IDNR is 0, the MQ tables do have over 1000 records that would need to be cleared. These pilled up probably because we did not have a downtime on the Production environment in some time.
At the next downtime we will perform either the Cold Start or the table truncate procedure.
Original Message:
Sent: Mar 17, 2025 04:11 AM
From: Marike Gottschalck
Subject: U01001002 Invalid MEMSV handle - Automation Engine 21.0.5
Hello Christian, we used to have this problem too, this is caused by undeleted ah_idnrs in the tables, and you seem to have run out of runIds, the engine will then start from the beginning. The mqmem-Tables need to be truncated. The easiest way is a cold start, or support can provide you with sqls to do it directly in the db, if a cold start is not possible.
Original Message:
Sent: Mar 14, 2025 08:57 AM
From: Cristian Suciu
Subject: U01001002 Invalid MEMSV handle - Automation Engine 21.0.5
Hello,
Since about a week ago, we start seeing from time to time traces generated like the following:
20250312/051941.217 - U00015006 System forced memory trace dump.
20250312/051941.217 - U00003631 Dump caused by:
20250312/051941.217 - U00000002 EXISTS
20250312/051941.217 - U00011801 Error in Server routine 'UCGENX_R', Server: 'AE_PROD#WP025' AE system: 'AE_PROD'.
Also we are seeing another trace message that we have not seen before:
20250311/201116.325 - U01001002 Invalid MEMSV handle.
<...>
20250311/222632.104 - U01001002 Invalid MEMSV handle.
<...>
20250311/231921.732 - U01001002 Invalid MEMSV handle.
This is causing jobs to get stuck in statuses like "Generating", "Preparing" or "Checking Preconditions" and the only thing we can do is to change the status manually. Cancelling them does not work.
Thanks,
Cristian