on 02-06-2013 7:23 AM
Hi Expert,
I am facing the problem during access the BW report via analyzer, Pleazse provide the solution...
Our OS is windows 2003 and DB is SQL.
( An Error occurred while communicating with the BW server.
As a result of this error, the system has been disconnected from the BW server.
Detailed Description:
No more memory available to extend an internal table)
Regards
Ashwani
Good Day
The below suggested solutions are based on assumptions.
For you to fix the problem you need to analyse the ABAP dump. Use Tx ST22 to for that.
Also use Tx ST02 to analyse the memory consumption.
There is no point in increasing memory parameters unless and until you find the real reason behind it.
Also make sure you have sufficient memory available on the server.
Cheers
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joseoh,
Please find the below Profile parameter of our BW system, So i request to you please provide the solution accordingly, Which buffer parmeter need to increase and which parameter to extend in current profile.
login/disable_multi_gui_login = 1
#parameter created
zcsa/table_buffer_area = 100000000
#parameter created
zcsa/presentation_buffer_area = 10000000
#parameter created
zcsa/db_max_buftab = 10000
#parameter created
sap/bufdir_entries = 10000
#parameter created
rtbb/max_tables = 2000
#parameter created
rtbb/buffer_length = 60000
#parameter created
rsdb/obj/max_objects = 20000
#parameter created
rsdb/obj/buffersize = 40960
#parameter created
rsdb/ntab/irbdsize = 8000
#parameter created
rsdb/ntab/ftabsize = 60000
#parameter created
rsdb/ntab/entrycount = 30000
#parameter created
rsdb/esm/max_objects = 10000
#parameter created
rsdb/esm/buffersize_kb = 40000
#parameter created
rsdb/cua/buffersize = 10000
#parameter created
abap/buffersize = 400000
#parameter created
ztta/roll_area = 6500000
#parameter created
icm/keep_alive_timeout = 90
#parameter created
rdisp/plugin_auto_logout = 3600
#parameter created
enque/table_size = 20480
#parameter created
gw/max_sys = 2000
#parameter created
gw/max_overflow_size = 25000000
#parameter created
rdisp/max_comm_entries = 2000
#parameter created
rdisp/tm_max_no = 2000
#parameter created
gw/max_conn = 2000
#parameter created
rdisp/appc_ca_blk_no = 1000
#parameter created
rdisp/wp_ca_blk_no = 1000
#parameter created
rdisp/max_arq = 2000
#parameter created
rdisp/max_wprun_time = 3600
SAPSYSTEMNAME = BIP
SAPGLOBALHOST = prodbi
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
jstartup/trimming_properties = off
jstartup/protocol = on
# exe/j2ee
#jstartup/vm/home = C:\j2sdk1.4.2_24-x64\
jstartup/vm/home = $(DIR_SAPJVM)
jstartup/max_caches = 500
jstartup/release = 700
# exe/j2ee
#jstartup/instance_properties = $(jstartup/j2ee_properties);$(jstartup/sdm_properties)
# exe/j2ee
#j2ee/dbdriver = $(DIR_EXECUTABLE)\mssjdbc\sqljdbc.jar
j2ee/dbdriver = d:\usr\sap\BIP\DVEBMGS00\exe\mssjdbc\jdbc4\sqljdbc4.jar
rdisp/wp_no_dia = 10
#old_value: 3
rdisp/wp_no_btc = 12
rdisp/j2ee_start_control = 1
rdisp/j2ee_start = 1
rdisp/j2ee_libpath = $(DIR_EXECUTABLE)
# exe/j2ee
#exe/j2ee = $(DIR_EXECUTABLE)\jcontrol$(FT_EXE)
#old_value: 600
rdisp/j2ee_timeout = 3600
rdisp/frfc_fallback = on
#icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00
# exe/j2ee
#icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00
#icm/server_port_0 = PROT=HTTP,PORT=80$$
#icm/server_port_0 = PROT=HTTP,PORT=80$$
icm/server_port_0 = PROT=HTTP,PORT=80$$
#-----------------------------------------------------------------------
# SAP Message Server parameters are set in the DEFAULT.PFL
#-----------------------------------------------------------------------
#ms/server_port_0 = PROT=HTTP,PORT=81$$
#ms/server_port_0 = PROT=HTTP,PORT=81$$
ms/server_port_0 = PROT=HTTP,PORT=81$$
rdisp/wp_no_enq = 1
rdisp/wp_no_vb = 1
rdisp/wp_no_vb2 = 1
rdisp/wp_no_spo = 1
#------------------------------------------------------------
# Jcontrol: Migrated Profile Parameter
# create at Mon Jan 03 16:25:05 2011
#------------------------------------------------------------
# j2ee/scs/host
#j2ee/instance_id = ID0090977
j2ee/instance_id = ID90977
#------------------------------------------------------------
#parameter created
login/no_automatic_user_sapstar = 0
#parameter created
PHYS_MEMSIZE = 17202
# *** PERMANENT 730 CHANGE ***
exe/icmbnd = $(DIR_CT_RUN)/icmbnd
# *** Merged from D:\usr\sap\BIP\SUM\abap\sapnames\START_DVEBMGS00_prodbi.BCK by Upgrade to 730
#.******************************************************************************************************************************
#.* *
#.* Start profile START_DVEBMGS00_PRODBI *
#.* *
#.* Version = 000001 *
#.* Generated by user = ASHWANI *
#.* Generated on = 04.01.2011 , 12:27:19 *
#.* *
#.******************************************************************************************************************************
DIR_PROFILE = $(DIR_INSTALL)\profile
_PF = $(DIR_PROFILE)\BIP_DVEBMGS00_prodbi
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
# Change for release 730
Start_Program_00 = immediate $(DIR_CT_RUN)$(DIR_SEP)sapcpe$(FT_EXE) pf=$(DIR_PROFILE)$(DIR_SEP)BIP_DVEBMGS00_prodbi
# Change for release 730
#Start_Program_01 = immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF)
#-----------------------------------------------------------------------
# Start ABAP database
#-----------------------------------------------------------------------
_DB = $(DIR_CT_RUN)\strdbs.cmd
# Change for release 730
#Start_Program_01 = immediate $(_DB) BIP
Start_Program_02 = immediate $(DIR_CT_RUN)$(DIR_SEP)strdbs.cmd BIP
#-----------------------------------------------------------------------
# Start SAP message server
#-----------------------------------------------------------------------
_MS = $(DIR_EXECUTABLE)\msg_server$(FT_EXE)
Start_Program_03 = local $(_MS) pf=$(_PF)
#-----------------------------------------------------------------------
# Start application server
#-----------------------------------------------------------------------
_DW = $(DIR_EXECUTABLE)\disp+work$(FT_EXE)
Start_Program_04 = local $(_DW) pf=$(_PF)
#-----------------------------------------------------------------------
# Start internet graphics server
#-----------------------------------------------------------------------
_IG = $(DIR_EXECUTABLE)\igswd$(FT_EXE)
# Start IGS
#Start_Program_05 = local $(_IG) -mode=profile pf=$(_PF)
# Change for release 730
Start_Program_06 = immediate $(DIR_CT_RUN)$(DIR_SEP)sapcpe$(FT_EXE) pf=$(DIR_PROFILE)$(DIR_SEP)BIP_DVEBMGS00_prodbi list:$(DIR_CT_SAPJVM)$(DIR_SEP)sapjvm_6.lst source:$(DIR_CT_SAPJVM)
# Change for release 730
Start_Program_07 = immediate $(DIR_CT_RUN)$(DIR_SEP)sapcpe$(FT_EXE) list:$(DIR_GLOBAL)$(DIR_SEP)bootstrap$(DIR_SEP)bootstrap.lst source:$(DIR_GLOBAL)$(DIR_SEP)bootstrap target:$(jstartup/DIR_CLUSTER)$(DIR_SEP)bootstrap pf=D:\usr\sap\BIP\SYS\profile\BIP_DVEBMGS00_prodbi
# Start IGS
Start_Program_08 = local $(DIR_EXECUTABLE)$(DIR_SEP)igswd$(FT_EXE) -mode=profile pf=$(DIR_PROFILE)$(DIR_SEP)BIP_DVEBMGS00_prodbi
# j2ee/scs/host
j2ee/scs/host = prodbi
j2ee/scs/system = 01
# exe/j2ee
SAPJVM_VERSION = 6.1.044
DIR_SAPJVM = $(DIR_EXECUTABLE)$(DIR_SEP)sapjvm_6
# exe/j2ee
system/type = DS
jstartup/numCaches = 1000
j2ee/ms/port = 3901
icm/HTTP/ASJava/disable_url_session_tracking = TRUE
icm/server_port_1 = PORT=5$(SAPSYSTEM)00,PROT=HTTP,TIMEOUT=60,PROCTIMEOUT=600
icm/server_port_2 = PORT=5$(SAPSYSTEM)04,PROT=P4
icm/server_port_3 = PORT=5$(SAPSYSTEM)06,PROT=P4SEC
icm/server_port_4 = PORT=5$(SAPSYSTEM)07,PROT=IIOP
icm/server_port_5 = PORT=5$(SAPSYSTEM)03,PROT=IIOPSEC
icm/server_port_6 = PORT=5$(SAPSYSTEM)08,PROT=TELNET,HOST=localhost
icm/HTTPS/client_certificate_chain_header_prefix = SSL_CLIENT_CERT_CHAIN_
icm/HTTPS/client_certificate_header_name = SSL_CLIENT_CERT
icm/HTTPS/client_cipher_suite_header_name = SSL_CIPHER_SUITE
icm/HTTPS/client_key_size_header_name = SSL_CIPHER_USEKEYSIZE
Regards
Ashwani
Hi Joseoh,
Please find the profile value of below Buffer
Parameter Name | Minimum | Maximum | Default Value | Profile Value | Current Value |
abap/heap_area_nondia | 0 | 64000000000 | 0 | 0 | 0 |
ztta/roll_extension | 20000000 | 64000000000 | 2000000000 | 2000000000 | 2000000000 |
abap/heap_area_dia | 0 | 64000000000 | 2000000000 | 2000000000 | 2000000000 |
Please suggest accordingly.....
Regards
Ashwani
Hello
Did you check the dump and the memory consumption like I mentioned before ?
Increasing the memory from 2 GB to 4 GB when you haven't done any analysis is a lazy approach.
Increasing the profile parameters will not help you in resolving the issue instead it will run you into other issues.
You need to make sure that the memory available on the box is used properly.
Remember there are multiple users present on the system. You need to make sure that they all are able to do their work without fail.
If you don't have sufficient memory on the memory then increasing the parameter values will not do any good.
When you increase the extended memory per user context to 4 GB you are letting the users use more extended memory per session with a limit on other activities unless you add more memory to the box.
If there is Java running on the same machine then you need to take care of that as well.
BI systems are prone to memory consumption. So you need to play smart here.
I suggest you to do an analysis and then if you know that 2 GB is not sufficient increase an additional 1 GB and then monitor the system behavior.
I suggest you to go through the SAP memory parameter recommendation notes for your setup and do some homework as it generally helps. It would really help others in assisting you.
@Rest : Do not suggest any solutions when you really haven't got a clue about the underlying issue.
Cheers
RB
Hi Joseph,
I have extend the 3 parameter value as you mentiond above, but i getting the same problem as discribed the initial.
But ABAP Dump showing diffren as below.
06.02.2013 19:31:31 prodbi_BIP_00 MUKESH 210 C TSV_TNEW_PAGE_ALLOC_FAILED CL_RSR_RRI2_LRECH=============CP 1 F36370E20132F1368D3F0050569E000E
06.02.2013 18:43:42 prodbi_BIP_00 MUKESH 210 C SYSTEM_NO_ROLL CL_RSR_RRI2_LRECH=============CP 7 955D70E229CFF1F0ADE50050569E000E
Regards
Ashwani
To resolve errors like TSV_TNEW_PAGE_ALLOC_FAILED you need to follow:
1) try to optimize program you run if possible (for SAP programs try to search in http://service.sap.com/notes - may be its already be optimized or any suggestions provided; for customer programs - ask to ABAP guys to optimize);
2) if above are not applicable to you, increase parameter values specified in dump.
Regards,
Roman
Are you facing any ABAP dumps like TSV_TNEW_PAGE_ALLOC_FAILED????
Please check the below notes.
88416 - Zero administration memory management as of 4.0A/ Windows
This note will give you an understanding how memory is allocated.
110172 - Windows: Transactions with large memory requirements
129813 - Windows: Problems due to address space fragmentation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The TSV_TNEW_PAGE_ALLOC_FAILED occurred because the system could not extend the relevant internal tables. While performing the transactions the data must be loaded into the internal tables (selection of a huge range of objects from the database (in other words, too many fetches).
To do this the system must allow the required memory in to the roll area. And if the data is too large then this could not happen.
Then the system tried to use the Extended memory area (the system uses EM when the assigned memory - HEAP, is full).
If the data was quite large that caused the EM to exhaust and hence leading the system in failing to allocate the new pages (memory) as required by the Transactions/ABAP steps.
Possible Cause :
Due to lack of selection criteria too much data is selected
Memory management parameter are set low.
Propose Solution :
Option 1:
One way to avoid this is to reduce the range from your selection Screen or at least add more criteria for the report so that there will be less fetches to the database and this dump can be avoided.
Please check first if you can restrict selection criteria to start the background process in question. If not, please refer below.
Option 2:
If option 1 doesn't help, then we are left with no option but to tune EM and Heap parameters.
try to increase the following parameters to 4GB and restart the instance and check.
I have faced this kind of issues and after increasing the profile parameter value, the issue is fixed.
you can give a try.
abap/heap_area_nondia to 4000000000
ztta/roll_extension to 4000000000
abap/heap_area_to 4000000000
Please check and provide your feedback.
Thanks and Regards,
Vimal
Hi bhowmik,
1. There may be may be issue with the virtual memory.
2. Delete the old spool request
3. Check the temporary tablespace
Kindly paste the error log.
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bhowmik
It is pure SAP memory problem or you are accessing huge data.
you can find the more details
if you want to change parameter
http://scn.sap.com/thread/3194174
or
if you are accssing more data please follow below links
http://scn.sap.com/thread/260273
http://scn.sap.com/thread/1154093
http://scn.sap.com/thread/1786905
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.