Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

ABAP Program or transaction for hard workload testing

Former Member
0 Likes
573

Hello ABAPers,

in my actual client we have the need of creating an error of memory overflow or Database workload overflow.

I think I once saw an standar program that replicates this kind of overflows. But I can´t remember or find this program.

May be it´s all my imagination, but I´m pretty sure there was a program/transaction/function module that could help me with this issue.

If anybody knows of anything about this, please answer this post.

Thank you very much and kind regards

Ibai Ramirez

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
521

Hi,

I don't know any standard program that does that but you could maybe try the following options:

1. Talk to your Basis team in order to reduce the system parameter size for memory (this will probably cause that some standard programs / transactions give the error you're looking for).

2. Create a custom program that has an infinite loop (WHILE TRUE) where you're requesting memory to SAP on every loop and not releasing it.

Hope this helps.

3 REPLIES 3
Read only

Former Member
0 Likes
522

Hi,

I don't know any standard program that does that but you could maybe try the following options:

1. Talk to your Basis team in order to reduce the system parameter size for memory (this will probably cause that some standard programs / transactions give the error you're looking for).

2. Create a custom program that has an infinite loop (WHILE TRUE) where you're requesting memory to SAP on every loop and not releasing it.

Hope this helps.

Read only

ravi_lanjewar
Contributor
0 Likes
521

Hi,

I will not recommanded to increase the size. If your using the ECC 6.0 it allow default size upto 4GB and before that upto 2 GB.

You can check it with using the transaction ST22 for dump analysis and observe the program name and check it is standard program or customer program ( i.e. Start from y or z ). if it standard program then write to SAP and if it is customer program it read more data then read the data in batches, process data and after processing unwanted internal table you have to refresh.

For analysis of the program you can used SE30 - Program runtime analysis, ST05-SQL analysis, ST12-Perticular transaction analysis and STAD.

Read only

Former Member
0 Likes
521

I do not really understand the purpose of your approach.

Workload testing does not create simple dumps, but tests your actual workload and tries to avoid dumps.

Creating simple dumps should be very easy, you SELECT INTO TABLE with a large DB table, no ABAP memory can hold the largest DB table.

Siegfried