2006 Sep 22 7:00 AM
hi all,
wat rollarea concept & roll in - roll 0ut . user-context.
reply me aspl
regards,
vishnu kanth
2006 Sep 22 7:07 AM
hi vishnu,
chk this. i guess u got a dump related to an internal table.
<b>
No more space in Rollarea</b>
<b>its actually a part of memory.</b>
If the dump indicates that there are more than 100K records in the internal table, then the only possibility is that you have a bug in the logic / algorithm that clears out the internal table every 10K records.
If you have an internal table without a header line, then the statements FREE, REFRESH and CLEAR will all empty the internal table so that its row count is 0. The difference between CLEAR/REFRESH and FREE, is that only the FREE statement will release the memory previously allocated for those rows. The idea is that FREE is called when you know the internal table is not going to be re-populated, and CLEAR/REFRESH is used when the internal table needs to be emptied and then re-populated (avoiding the overhead of allocating memory again).
If the internal table has a header line, then "CLEAR TAB" will only initialise the header line, whereas "CLEAR TAB[]" will have the same effect as "REFRESH TAB". The REFRESH statement will not initialise a header line.
rgds
anver
if hlped mark points.
Message was edited by: Anversha s
hi all,
wat rollarea concept & roll in - roll 0ut . user-context.
reply me aspl
regards,
vishnu kanth
2006 Sep 22 7:02 AM
<b>Roll Area</b>
This parameter is used to specify the total size of the roll area, in bytes.
Activities
The roll area is not important with 64 bit platforms where sufficient extended memory is available. The default value is platform-specific and is determined dynamically. The default value is specified in transaction RZ11. This value should not normally be changed.
<b>User Contexts</b>
The memory management system assigns memory to user contexts from the following areas: roll area, SAP extended memory, and heap memory.
The order of assignment from these memory areas arranges itself according to whether the user context runs in an SAP dialog work process or in another SAP work process. This enables the SAP system to optimally use the characteristics of the individual memory types.
When allocating memory, the following characteristics for individual memory types become noticeable.
check this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/02/96274f538111d1891b0000e8322f96/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/34/d9c8b9c23c11d188b40000e83539c3/content.htm
2006 Sep 22 7:07 AM
hi vishnu,
chk this. i guess u got a dump related to an internal table.
<b>
No more space in Rollarea</b>
<b>its actually a part of memory.</b>
If the dump indicates that there are more than 100K records in the internal table, then the only possibility is that you have a bug in the logic / algorithm that clears out the internal table every 10K records.
If you have an internal table without a header line, then the statements FREE, REFRESH and CLEAR will all empty the internal table so that its row count is 0. The difference between CLEAR/REFRESH and FREE, is that only the FREE statement will release the memory previously allocated for those rows. The idea is that FREE is called when you know the internal table is not going to be re-populated, and CLEAR/REFRESH is used when the internal table needs to be emptied and then re-populated (avoiding the overhead of allocating memory again).
If the internal table has a header line, then "CLEAR TAB" will only initialise the header line, whereas "CLEAR TAB[]" will have the same effect as "REFRESH TAB". The REFRESH statement will not initialise a header line.
rgds
anver
if hlped mark points.
Message was edited by: Anversha s