TSV_TABH_POOL_NO_ROLL_MEMORY SAP ABAP Runtime Error tsv tabh pool no roll memory

TSV_TABH_POOL_NO_ROLL_MEMORY is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: O - Resource Shortage

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

TSV_TABH_POOL_NO_ROLL_MEMORY ABAP Runtime Error

Please see not enough roll for more details about the possible cause of this runtime error and how it could be avoided.

Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.

No memory available to extend the pool for internal tables. Please see not enough roll for more details about the possible cause of this runtime error and how it could be avoided.

Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.

Internal tables are addressed via 8 byte wide references. Further memory (the so called table header) for the administration of the internal table is allocated not until the table is actually instantiated (for example as result of an INSERT statement).

At the extension of the table header administration, memory was requested at a size of <runtime parameter> byte, which was no longer available.

The maximum number of allowed table headers depends on the system. On the existing platform, you can admininistrate a maximum number <runtime parameter> of table headers per roll area and area instance at the same time.

Currently, <runtime parameter> table headers are allocated. Therefrom, <runtime parameter> were usd.

Storag loacation: <runtime parameter> Please see not enough roll for more details about the possible cause of this runtime error and how it could be avoided.