Dump TSV_TNEW_PAGE_ALLOC_FAILED

[Former Member]

Dear gurus..

I am executing the SP12 --TemSe Data Storage --> Consistency Check and this process is dumping with TSV_TNEW_PAGE_ALLOC_FAILED dump.

I am the following profile parameters.

We have HP-UX B.11.23 U ia64 with 12 GB RAM

Could youplease help me?

ztta/max_memreq_MB 2048

em/global_area_MB 615

login/no_automatic_user_sapstar 0

login/failed_user_auto_unlock 1

login/min_password_lng 6

login/fails_to_user_lock 3

enque/table_size 32000

rsdb/ntab/entrycount 36175

sap/bufdir_entries 10000

rsdb/obj/max_objects 20000

rsdb/obj/buffersize 20000

rdisp/max_wprun_time 0

rdisp/tm_max_no 2000

rdisp/max_comm_entries 2000

rsdb/max_blocking_factor 5

rdisp/wp_auto_restart 14400

zcsa/installed_languages EDS

gw/max_overflow_size 25000000

SAPSYSTEMNAME PRG

INSTANCE_NAME DVEBMGS00

SAPSYSTEM 00

rdisp/wp_no_dia 12

rdisp/wp_no_vb 2

gw/max_conn 2000

rdisp/wp_no_vb2 2

rdisp/wp_no_enq 1

rdisp/wp_no_btc 4

rdisp/wp_no_spo 1

zcsa/system_language S

rslg/send_daemon/listen_port 3700

rslg/send_daemon/talk_port 1300

abap/buffersize 450000

rsdb/cua/buffersize 30100

zcsa/presentation_buffer_area 41504768

zcsa/table_buffer_area 60240896

zcsa/db_max_buftab 10000

rtbb/buffer_length 30000

rtbb/max_tables 500

em/max_size_MB 6144

rdisp/appc_ca_blk_no 2000

rdisp/wp_ca_blk_no 1000

rsdb/ntab/ftabsize 36209

rsdb/ntab/irbdsize 7242

rsdb/ntab/sntabsize 3621

DIR_ROLL /usr/sap/PRG/DVEBMGS00/data

DIR_PAGING /usr/sap/PRG/DVEBMGS00/data

DIR_DATA /usr/sap/PRG/DVEBMGS00/data

DIR_REORG /usr/sap/PRG/DVEBMGS00/data

DIR_TRANS /usr/sap/trans

DIR_TEMP /tmp

DIR_SORTTMP /usr/sap/PRG/DVEBMGS00/data

install/codepage/appl_server 1100

abap/use_paging 0

ztta/roll_first 1000000

ztta/roll_area 9500000

login/system_client 400

rdisp/ROLL_SHM 16384

rdisp/ROLL_MAXFS 32768

PHYS_MEMSIZE 64

rdisp/PG_SHM 8192

rdisp/PG_MAXFS 32768

abap/heap_area_dia 2000000000

abap/heap_area_nondia 2000000000

abap/heap_area_total 2000000000

abap/heaplimit 40894464

abap/swap_reserve 37748736

ztta/roll_extension 2145386496

em/initial_size_MB 11264

em/blocksize_KB 4096

em/stat_log_size_MB 20

em/stat_log_timeout 600

rdisp/btctime 5

rdisp/btcname mch-hp04_PRG_00

rsdb/pmandt 000

rdisp/elem_per_queue 2000

rdisp/bufrefmode sendoff,exeauto

rdisp/TRACE 1

transport/during_upgrade ON

DIR_PUT /usr/sap/put

rdisp/system_needs_spool false

rspo/spool_id/use_tskh 0

rec/client OFF

rdisp/autoabaptime 0

ztta/parameter_area 8000

rdisp/j2ee_start 0

rdisp/start_icman false

rsdb/rep/fast_touch off

rsdb/staton 1

auth/object_disabling_active N

auth/auth_number_in_userbuffer 9000

rdisp/roll_maxfs 8192

rdisp/accept_remote_trace_level 0

rdisp/auto_vb_stop 0

ipc/shm_psize_10 104000000

ipc/shm_psize_14 0

ipc/shm_psize_18 0

ipc/shm_psize_19 0

ipc/shm_psize_30 0

ipc/shm_psize_40 160000000

ipc/shm_psize_41 0

[Former Member]

Hi!

If you have too many things running on the system you can run it again during an low execution period. Anyway I think you can change the following parameters...

abap/heap_area_dia 4000000000

abap/heap_area_nondia 4000000000

abap/heap_area_total 8000000000

Cheers

[Former Member]

Hi,

Can you check the parameter ztta/roll_first wether its set to 1 or some other value, and if not please make it to 1 and find the difference.

This kind of dump happens due to two following reasons.

1. Improper memory settings

2. Large consumption of memory.

If we want to find which of the above mentioned reasons are responsible for this dump, then kindly check in ST22 and double click on the specific dump.

In the long list you could see the perfect reason for this and the program on which dump

happens and can do the tuning.

If possible send me the the log from ST22 and will find out any OSS Note relevant for it.

Kindly let me know if you have any further queries.

Thank you,

Tilak

[Former Member]

Hi All,

I am facing the same issue current parameter values in our Production system is -:

ztta/roll_extension : 2000683008 Byte

ztta/roll_area : 6500352 Byte

ztta/roll_first : 1024 Byte

abap/heap_area_dia : 2000683008 Byte

abap/heap_area_total: 2000683008 Byte

abap/heaplimit : 40894464 Byte

Pls suggest what all are the changes I need to make in these parameters?

Regards,

Prashant,

[Former Member]

Hi Prashant,

Could you send me the ST22 log of this dump which indetails about

Information on where termination occurred

-

---

The termination occurred in the ABAP program "XXXXXX " in "SELECT".

The main program was "XXXXX ".

Because the current settings:

ztta/roll_extension : 2000683008 Byte Ok!!

ztta/roll_area : 6500352 Byte OK!! (Assuming you have 64 bit system)

ztta/roll_first : 1024 Byte --Default should be 1byte..

abap/heap_area_dia : 2000683008 Byte OK!!

abap/heap_area_total: 2000683008 Byte OK!!

abap/heaplimit : 40894464 Byte

Just let me know your system details as well like which OS and 32/64 bit?

Thank you,

Tilak

[Former Member]

Is it a regular feature or it happend at times.

May be you can try to repeat the same thing at low peak hours and check if you get the same error.

Thanks

Amit

[Former Member]

Hi Luis

The dump happens when a workprocess runs out of memory, normally after the amount of ztta/roll_extension and abap/heap_area_dia were consumed. This can be caused by selecting a large amount of data.

Do you have a lot of spools in your system? Is it possible the spool reorg job is not properly configured? Can you please check the job SAP_REORG_SPOOL, and if it is deleting something at all?

Best regards

Michael

[Former Member]

Check SM21 logs for that dump and identify the workprocess number for this dump and then check that dev_wxx trace file of that particular application server. You can see some time before this dump occured there might be something like this abap/heaplimit reached. I believe changing this abap/heap_area_dia parameter may help in resolving the dump.