on 03-31-2009 8:29 PM
Dear all,
We need to download contents of database table BSEG into a local file via SAP GUI.
When we start we get TSV_TNEW_PAGE_ALLOC_FAILED.
SAP ECC 6.0 Oracle 10.2.0.2 and HP-UX 11.23
There is physical memory in the system of 50 GB.
SAP Memory Curr.Use % CurUse[KB] MaxUse[KB] In Mem[KB] OnDisk[KB] SAPCurCach HitRatio %
Roll area 2,50 6.551 6.664 131.072 131.072 IDs 97,06
Page area 0,12 315 1.136 65.536 196.608 Statement 76,00
Extended memory 12,43 2.084.864 2.101.248 16.773.120 0 0,00
Heap memory 500.446 0 501.962 0 0,00
The MaxUse of Extended Memory does not exceed 2.101.248 and we still get
"Memory low. leave the transaction before taking a break!""
Can you please advice what should I tune to prepare the system to get all exports from BSEG for all fiscal years?
there are 10 000 000 in BSEG totaly
Thank you in advance.
Ruzica
Hi,
Check ulimit of SIDADM and ORASID ids. command is ulimit -a
Try to set it unlimited for data, file, stack & memory.
Regards,
Sachin Rane.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What are the values for
abap/heap_area_dia
abap/heap_area_nondia
abap/heap_area_total
in your system?
How do you try to "export" those values? I hope you don't do it using SE16 and "system - list - save"...
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Markus,
abap/heap_area_dia 4000000000
abap/heap_area_nondia 4000000000
abap/heap_area_total 4000000000
Can you tell me which parameter limits the Extended memory per user, because I saw when I will start dispaly BSEG with one fiscal year extended memory go to 2.5GB and then starts to fill Heap memory.
Before starting to chose Save as to file we got Low Memory.
Thnx,
Ruzica
This is basically SE16.
That is not the recommended way of doing that - it will
- allocate a LOT of memory on the source system - and that twice: once for reading the data and another time the same amount to fill the export table - and eventually dump (as you see it).
- create lots of traffic on your network
- will consume a lot of memory on the PC you download the data to. The grid is to be built on the client, if you're unlucky, your PC may run out of memory too
SE16 was not designed to "download" huge amounts of data, it's used to display table entries.
I suggest you create a small ABAP doing that, writing the output on the server and then either enable to user to access that file (using e. g. SAMBA) or send it via email.
Markus
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.