Skip to Content
2
Aug 17, 2023 at 11:24 AM

Is there a means to track down what happens with a specific transaction ID?

254 Views Last edit Aug 17, 2023 at 11:46 AM 2 rev

Hi All!

I'm on a bit of a wild goose chase and would appreciate any pointers of what else to look for.

Since at least July 20, we are getting frequent dumps in one of our productive systems with TSV_TNEW_PAGE_ALLOC_FAILED in SAPLSBAL_DB (or until the first week of August /AIF/CL_LOG_HANDLER===========CP) while doing something or other with application log (BALDAT) data related to AIF-processing of DEBMAS IDOCs.

There are up to 350 dumps each day happening between 04:00 in the morning and 23:00 in the evening.

The dumps always happen for one of just 7 different transaction IDs (down to 6 since August 1) as can be seen here:

dumps-bytransactionid-and-cancelledprogram-until20.jpg

And the Transaction IDs are somewhat in "lock-step" as far as their number each day are concerned:

dumps-bydate-and-transactionid-until20230816.jpg

Since August 1, five of them happen almost the same number of times each day (give or take 1 or 2) and one transaction ID has roughly twice that number.

I somehow doubt that any of this can be just a coincidence but we haven't yet been able to identify the roote cause for this and are running out of ideas of where else to look. We already have an OSS incident open which is actively worked on by SAP support, so my question here is mostly a "flanking measure" to see if anybody has seen and been able to resolve a similar issue elsewhere.

I'd also like to know if a transaction ID is tied to "something else" in the system somewhere which can be queried, like executed programs, IDOCs, users or whathever to perhaps somehow track it back to its origin.

Does anybody have any ideas?

We are on NW 750 SP25 EHP8.

Thanks much and cheers

Bärbel