Difference between TSV_TNEW_*, SYSTEM_NO_MEMORY, STORAGE_PARAMETERS_WRONG_SET etc

[AnilDandi]

Hi All,

I am a little bit of interested in knowing what kind of memory allocation failure causes one of the many memory related error dumps in an SAP system. The deep rooted cause for each error code has to be different for SAP to choose a different error code.

Can anyone explain what is the difference between the following error codes?

• TSV_TNEW_PAGE_ALLOC_FAILED
• TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
• TSV_TNEW_OCCURS_NO_ROLL_MEMORY
• TSV_TNEW_INDEX_NO_ROLL_MEMORY
• LOAD_NO_ROLL
• SYSTEM_NO_MEMORY
• STORAGE_PARAMETERS_WRONG_SET
• TSV_LIN_ALLOC_FAILED
• TABLE_HASH_NO_MEMORY
• SYSTEM_NO_ROLL

Thank you!

[AnilDandi]

Yes, I know memory is a big topic.

I do know that some of the errors occur when there is no more roll or em or heap memory available. Some originate from kernel level allocation problems even though there is sufficient memory. Some are limits on single request instead of limits on WP or system. Some errors occur when addition of the first row itself cannot be fulfilled; some errors occur if internal table cannot be expanded.

I am trying to see if anyone can share a deeper insight on these error codes (may not be all at once), beyond what the dumps and SAP notes reveal.

regards

AKD

[madasamy_arunachalam]

Hi

Memory within SAP is "big" and complexity in its nature of functioning; Mainly under below category;

These dumps are related to memory parameter configured in the system, you can check "Current Parameters" under ST02.

You may also get these types of dumps;

i) due to the nature of code used in the standard or custom SAP programs which in turn get into endless loop and try to update internal tables - This needs source code correction.

ii) user error, e.g. "incorrect selection criteria" selected while running running in the report (either dialog or batch job) - user should be trained to avoid such selection...

iii) also mismatch of  shared memory segments/pool configuration  - can be checked with sappfpar check pf=<instance parameter file>

iv) Mainly, due to paging set at OS level  and its free/availability;

list goes on..Yes, it will be long answer as DS said in his update;

regards

Swami

[divyanshu_srivastava3]

Hi Anil,

If you can't get the explanation from dumps itself, then this would be a very long answer.

Just do google with 'SAP memory dumps' or check for SAP notes to get to know more on this.

You may read how memory is occupied and different data structures used for storing data.

Please search, you will get your answers.

Regards