지금 조회할때 아래와 같은 덤프가 뜨는데요 ㅠㅠ 어떻게 해결하는지...
itab 리코드 개수가 많아서 문제인지.... 시스템 메모리 문제인지...
알려주시면 고맙겠습니다. ^
===============================================
어떤 문제가 발생했습니까?
You attempted to extend an internal table, but the required space was
not available.
The internal table "PROGRAM=ZFIR0000DATA=IT_ITEM[]" could not be further
extended. To enable
error handling, the table had to be delete before this log was written.
As a result, the table is displayed further down or, if you branch to
the ABAP Debugger, with 0 rows.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 938
Number of rows: 1,689,344
Allocated rows: 1689344
Newly requested rows: 16 (in 1 blocks)
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server gnd_GND_00 on host gnd (wp 2)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1897
The error reported by the operating system is:
Error number..... " "
Error text....... " "
The error reported by the operating system is:
Error number..... " "
Error text....... " "
* e-abap님에 의해서 게시물 이동되었습니다 (2010-07-07 23:42)
댓글 2
-
맑은하늘
2010.07.06 19:18
-
AWESOME
2010.07.09 16:03
This error message usually indicates that you have run out of session memory and the only way to get around this is to either get more memory allocated which is a server setting or to ensure that you are not retrieving an abnormally large amount of data.
찾아보니깐 이런 내용이네요 ㅋㅋ
해석하자니 애매해서...
도움 되셨으면 좋겠어요 ㅎㅎ
BC에게 문의해 보세요. 문제는 internal table 이 차지하는 메모리가 시스템에서 제한하는 크기를 넘어간것 같네요.
거의 170만건 정도가 itab 에 잡혔는데, BC에서 사이즈를 늘려주지 않는다면 itab 을 적절한 단위로 분할해서
사용하셔야 할 것 같습니다.