on 06-20-2008 7:14 AM
Hi Gurus
I am using BI7.0 AIX, oracle 10.2, 64 bit Kernal. when i am running DB13-DBCHECK it is giving errors, when i want to see the detailed logs by saving it into local file, it is throwing dump
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
TSV_TNEW_PAGE_ALLOC_FAILED
my system has 20GB physical RAM and SWAP:20GB
by running rspfpar and memlimits this is the log:
MBCheck the available swap space (malloc in several processes)
... Size = 4096MB Total: 4096MB
Upper size limit 4096 reached. Finish checking
Total available swap space = 4096MB
Check the maximum size of mapped file (mmap anonymous,dev/zero)
Check protection operations on this area (protect)
Trying to mmap 512MB ... successfull
Trying to mmap 768MB ... successfull
Trying to mmap 1024MB ... successfull
Trying to mmap 1280MB ... successfull
Trying to mmap 1536MB ... successfull
Trying to mmap 1792MB ... successfull
Trying to mmap 2048MB ... successfull
Trying to mmap 2304MB ... successfull
Trying to mmap 2560MB ... successfull
Trying to mmap 2816MB ... successfull
Trying to mmap 3072MB ... successfull
Trying to mmap 3328MB ... successfull
Trying to mmap 3584MB ... successfull
Trying to mmap 3840MB ... successfull
Trying to mmap 4096MB ... successfull
Upper size limit 4096 reached. Finish checking
Trying to mprotect 4096MB ... successfull
Maximum mapped file size: 4096MB
Maximum mprotect size: 4096MB
R/3 parameter em/initial_size_MB up to 4096 permitted
Check the maximum address space per process usable
both by process local memory and mapped file
Maximum address space ( mmap(4096 MB)+ malloc(1676MB) 😞 5772MB
----
Result |
----
Maximum heap size per process........: 4096 MB
measurement limited to 4096 MB
this value is probably limited by swap space
Maximum mapped file size (mmap)......: 4096 MB
measurement limited to 4096 MB
Maximum protectable size (mprotect)..: 4096 MB
measurement limited to 4096 MB
em/initial_size_MB > 4096 MB will not work
Maximum address space per process....: 5772 MB
Total available swap space...........: 4096 MB
measurement limited to 4096 MB
main memory size x 3 recommended , minimum 1 GB
bihprd:pbwadm 5>
my system has 20GB physical RAM and SWAP:20GB
These are the mem parameters in the system
ztta/roll_area 6500000
ztta/roll_first 1
ztta/short_area 3200000
rdisp/ROLL_SHM 16384
rdisp/PG_SHM 8192
rdisp/PG_LOCAL 150
em/initial_size_MB 10240 MB
em/blocksize_KB 4096 kB
em/address_space_MB 4092 MB
ztta/roll_extension 2010000000 Byte
abap/heap_area_dia 2000000000 Byte
abap/heap_area_nondia 2000000000 Byte Max.
abap/heap_area_total 2000000000 Byte Max.
abap/heaplimit 40000000
abap/use_paging 0
your guidance will be appreciable
Thanks & Regards
Balaji
Balaji,
Find the memory allocation process, in this way memory allocation will work.
MEM allocation sequence for dialog processes:
1. local SAP roll memory up to ztta/roll_first
2. SAP ext memory until ztta/roll_extension is reached or until the
SAP extended memory is used up
3. SAP roll memory up to ztta/roll_area
4. SAP heap memory until abab/heap_area_dia is reached or SAP heap
memory is used up
5. termination
MEM allocation sequence for non-dialog processes:
1. -> 1. see above
2. -> 4. see above
3. -> 2. see above
4. -> termination
and you need to analyse before increasing the memory parameters, you can check the usage in ST03N, -> expertmode -> click on the currectday -> and the Memory Use Statistics -> when you double click on that you can see the extended memory usage. based on that you need to increase all the parameters.
Hope this helps,
Cheers,
Praveen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
one option is to try upping your swap space, your extended memory alone is taking up over 10GB of this.
However TSV_TNEW.... tends to indicate the memory parameter max allowed has been hit.
If you look in the short dump of TSV_TNEW_PAGE_ALLOC_FAILED about 3 pages down it will show you what memory the program had used when it failed. Post it here and that should prove the issue.
Please note - on the recommendations above
increasing in the parameters rdisp/PG_MAXFS and rdisp/PG_SHM will not help reduce the number of occurances of TSV_TNEW_PAGE_ALLOC_FAILED. It is the 3 heap ones, the roll_first, roll_area, em/address_space_MB, ztta/roll_extension... and em/global_area can have an effect also.
Increasing EM/TOTAL_SIZE_MB will just cause more usage of your page. I would not do this unless ST02 shows extended memory has been used more than 10GB worth.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please check wether high paging of the roll and
page buffers happening in the check "Roll and Page Buffer Size" under
memory configuration section (ST02).
If yes, we can think of increasing in the parameters rdisp/PG_MAXFS and rdisp/PG_SHM.
These should help reduce the number of occurances of TSV_TNEW_PAGE_ALLOC
We can follow the recommendations in SAP note 789477 which uses
(ES/SHM_SEG_SIZE - 1) - em/blocksize_KB/1024.
Further I would suggest you increase the extended memory on each
server as follows as memory should be sufficient
Further we can think of increasing the EM/TOTAL_SIZE_MB if free space is available and no other application runs in the same server.
Please refer SAP Note 789477 "Large extended memory on AIX (64-bit) as of Kernel 6.20"
Using the EM/MAX_SIZE_MB parameter (as of 4.6D patch level 570:
EM/TOTAL_SIZE_MB), you can limit the total amount of extended memory
actually used. This is necessary to enable you to adjust the virtual
memory consumption to the amount of configured swap space.
I would suggest to set up Alternate Memory Management parameters
as per SAP Note 95454.
Accordingly i have set the parameters as follows-:
ztta/roll_extension
ES/TABLE->SHM_SEGS
ES/SHM_SEG_SIZE->
em/max_size_MB->2048
ES/SHM_PROC_SEG_COUNT
ES/SHM_MAX_PRIV_SEGS
Just check which program causing this dumps(your own code or sap transaction)
Please let me know after making this changes.
Do feel free to get back to me in case of query related to it.
Thank you,
Tilak
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.