different short dump errors for same transaction ID - SLQ_CAUGHT_RABAX and TSV_TNEW_PAGE

[bhat_vaidya2]

Hello Guys,

I am getting different short dump errors for same transaction ID when testing SD extraction in RSA3 and I don't know why both error is pointing to the same source code extract. The reason is because the source code extract is same as in Production and no changes have been made. I have tested the extraction in TEST system with a single test document and in DEV system,  I ran same extractor with about a 30000 records and got no error, so I do not think that userexit is wrong.

At the moment I am not sure if I should let Basis know that it is a memory issue or check the rootcause in the userexit.

short dump

Thanks,

Bhat

[karthik_vasudevan]

Hi Bhat

This is definitely an issue with memory allocation when selecting * from VBEP table.

If you inform basis team, they would be able to get the information like below to know how much memory was available and how much was utilized during the extraction.

Before doing that, its better to understand what is difference in TEST system than dev or production as they both don't have this issue.

The reason might be in development system, even for full load, you wont have much records in table level as no much transactions will happen there.

In production system, the memory might be more than your test system or as it picks only delta records, the data might have been very less.

Other than Select * from VBEP, do you have some other logics written to fetch data from other tables?

If you are not doing delta loads on a daily basis in test system, you will have many records to be fetched. So check in all of these perspective and see what best could be done

If you have any other information, please share it with us. we will try to solve this

Regards

Karthik

[RamanKorrapati]

Hi,

Lets inform to basis team. As i know its memory issue.

Mean while please check note 2021471

Thanks