HR: Dump in transaction PC00_M37_GRRF
I have a dump in PC00_M37_GRRF. Anybody know a note for this transaction?
See the code of the FUNCTION hr_br_daq_it_subtype, where I have the dump
000870 LOOP AT l_dref ASSIGNING <its> WHERE subty = l_subinfotype.
000880
000890 l_tabix = sy-tabix.
000900 * Get Amount/Data field
000910 ASSIGN COMPONENT im_wafor-fidaq-soufi OF STRUCTURE <its>
000920 TO <value>.
000930
000940 * Append to table
*>>>> IF NOT <value> IS INITIAL.
000960 CLEAR: wa_value.
000970 IF im_wafor-fidaq-datty EQ p99sd_cte_da OR
000980 im_wafor-fidaq-datty EQ p99sd_cte_bo.
000990 wa_value-data = <value>.
001000 ENDIF.
001010 IF im_wafor-fidaq-datty EQ p99sd_cte_am OR
001020 im_wafor-fidaq-datty EQ p99sd_cte_bo.
001030 wa_value-amtfo = <value>.
001040 ENDIF.
What version are you on? On my ERP6 I do not see any Loop at like you mentioned.. I see a Do..enddo instead.. anyway, pl check OSS Note# 1039545.
~Suresh
Similar Messages
-
ABAP DUMP IN transaction TBI6.
Hi Experts,
I am getting short dump from transaction TBI6 when I give business partner and company code and check any of the check box below and save. It is giving dump.
Dump analysis is saying Read statement with not work in unicode.
This is standard program. Program name : SAPLBUSS.
Is there any patch to include for not giving the short dump
Can any one suggest how to solve this problem....Search for an OSS note on <a href="http://service.sap.com">SAP MarketPlace</a>
Greetings,
Blag. -
ASE - Dump Database (Transaction Log deleted?)
Hi experts,
I have a question.
Will the transaction log be deleted reseted to the time of a database dump is finished?
Hopefully it will only be deleted by dumping the transaction log itself, right?
Kind regardsHello Christian,
Don't worry we have set the options to the databases which are getting installed through business suites.
However I will provide you the detailed dB details and their respective option which yoibcan cross verify as well from the isql command
sp_helpdb
go
And you can very well enable or disable the options set as well using
sp_dboption "<SID>","<option_name>",true/false
go
Also if you needed the detailed dB wise default dB options that to be set let me know I will attach the details as well ;)
Regards
Kiran K Adharapuram -
Getting dump in transaction S_ALR_87012936.
Hi Experts ,
I am running the transaction S_ALR_87012936. I have one user name which having the authorization to only one company code. when i am trying to run this transaction with that company code it is working fine.
But when i am trying to run the same transaction with different company code instead of giving authorization error, it is giving the ABAP dump.
Not able to find out why the dump is coming can any one tell me why the dump is coming?
Thanks in Advance..Hi,
Does it display the dump: CALL_FUNCTION_NOT_REMOTE?
If this is the case, then check whether any Background job is scheduled with this name. Or else, consult your Basis consultant and check the TRFC settings.
Best Regards,
Suresh
Edited by: Suresh S on Apr 8, 2009 12:33 PM -
Dump in transaction solman_workcenter
We are using solution manager 7 EHp1 when I run transction solman_workcenter sap reply with dump
The URL http://FQDN:8097/sap/bc/webdynpro/sap/ags_workcenter/ was not called due to an error.
Note
The following error text was processed in the system SLM : Syntax error in program /1BCWDY/2TZHMIB2Y1BD0FAABG9P==CP .
The error occurred on the application server cislm_SLM_97 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: CONSTRUCTOR of program CL_WDR_CLIENT_COMPONENT=======CP
Method: IF_WDR_COMPONENT_FACTORY~CREATE_COMPONENT of program CL_WDR_CLIENT_COMPONENT=======CP
Method: IF_WD_COMPONENT_USAGE~CREATE_COMPONENT of program CL_WDR_COMPONENT_USAGE========CP
Method: WDDOINIT of program /1BCWDY/UXVJIGLYIXN511VON3YF==CP
Method: IF_WDR_VIEW_DELEGATE~WD_DO_INIT of program /1BCWDY/UXVJIGLYIXN511VON3YF==CP
Method: DO_INIT of program CL_WDR_DELEGATING_IF_VIEW=====CP
Method: INIT_CONTROLLER of program CL_WDR_CONTROLLER=============CP
Method: INIT_CONTROLLER of program CL_WDR_VIEW===================CP
Method: INIT_CONTROLLER of program CL_WDR_INTERFACE_VIEW=========CP
Method: INIT of program CL_WDR_CONTROLLER=============CP
also in st22 23 same dump in SMD_RFC (user type SYSTEM ) with
CREATE DATA: The specified type "/BI0/V0SDB_C02M2" is no valid data type.
The current ABAP program "CL_SMD_AGGREGATE_MDX==========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.Hi,
try to re-activate the Enhancement Spot AGS_WORKCENTER_LAUNCHER (allthough it shows to be active)
and see whether this resolves the issue?
To do this start transaction SE20 and enter at the field Ehancement Spot: AGS_WORKCENTER_LAUNCHER
and press the display button. In the next screen use menu: 'Enhancement Spot' -> 'Activate'
Afterwards start SOLMAN_WORKCENTER again and check whether you have still the problem.
Kind regards,
Fabricius -
ABAP Dump : IW41 Transaction : PM Order confirmation save
Dear all .,
System - Upgraded ECC 6.0 ( from 4.6C)
Testing in QA .
Transaction - IW41 : Create PM Order Confirmation>Tick Final confirmation>saved
Runtime Errors SYNTAX_ERROR
Date and Time 06.10.2007 16:41:09
Short text
Syntax error in program "RMCX0013 ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLMCS0" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RMCX0013 " in include "RMCX0013
" in
line 0:
"The program "RMCX0013" is not Unicode-compatible, according to its pro"
"gram attributes."
The include has been created and last changed by:
Created by: "DDIC "
Last changed by: "DDIC "
Please help
Thanks & Regards ., GSDHi Guruprasad,
RMCX0013 is generated by a LIS structure. I don't know what's the reason in detail, but I hope if you re-generate your LIS structures, this can be overcome.
RMCX0013 (or Forms in this program) will be called dynamically (see list of active programs in the dump). If the calling program is active for unicode-check and the called not, this leads to incompatibility.
Regards,
Clemens -
Dump in transaction IB51 - create installed base
Hi,
We have installed CRM 2007 at our site. The transaction for creating installed base IB51 on selecting the category of installed base and pressing enter throws an ABAP dump.
The category being used is a standard SAP delivered category; yet there is a dump.
Kindly suggest the notes / corrections / SPs applicable if any; since the system is a new system and the error is not config related.
Regards,
Dhaval.Hi Dhaval,
Sorry, but SAPGui is no longer a supported UI for SAP CRM 2007 for any end-user facing applications. Consequently, the transactions in SAPGui are no longer supported. So you won't find corrections (notes, SPs) that will correct his problem.
SAP CRM 2007 comes with a complete new Web UI: The CRM WebClient UI. It allows a role based web access to all CRM applications. SAP CRM WebClient UI can be used integrated into the SAP Enterprise Portal but also "stand-alone" with a "local" application shell ("L-shape") which is delivered as part of SAP CRM ABAP server itself.
Please refer to many other threads in this forum, the SAP help portal and the CRM BPX communitiy pages for more information about the WebClient UI.
Best regards
Peter -
Hello,
I am with the Dump DBIF_RSQL_SQL_ERROR the environment PRD.
Can you help me?
Below, the DUMP the transaction ST22.
Erro tempo execução DBIF_RSQL_SQL_ERROR
Exceção CX_SY_OPEN_SQL_DB
Ocorrido em 18.12.2007 Às 10:38:41
An SQL error occurred when accessing a table.
O que aconteceu ?
O que pode ser feito?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Análise do erro
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"STORE_NEW_JOB_IN_DB" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
Notas p/eliminação de erros
The exception must either be prevented, caught within the procedure
"STORE_NEW_JOB_IN_DB"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "DbSlModifyDB6( SQLExecute ): [CLI
Driver][DB2/AIX64] SQL0911N The current transaction has been rolled back
because of a deadlock or timeout. Reason code "2". SQLSTATE=40001 row=1"
Internal call code.........: "[RSQL/INSR/TBTCO ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"SAPLBTCH " or "LBTCHF12 "
"STORE_NEW_JOB_IN_DB"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Ambiente de sistema
SAP Release.............. "620"
Application server....... "b8aix10"
Network address.......... "137.230.150.209"
Operating system......... "AIX"
Release.................. "5.2"
Hardware type............ "000DAA1A4C00"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 4
Short dump setting....... "full"
Database server.......... "b8aix10"
Database type............ "DB6"
Database name............ "QAS"
Database owner........... "SAPQAS"
Character set............ "pt_PT.ISO8859-1"
SAP kernel............... "620"
Created on............... "Feb 15 2004 21:09:47"
Created in............... "AIX 1 5 00447C4A4C00"
Database version......... "DB6_71 "
Patch level.............. "1350"
Patch text............... " "
Supported environment....
Database................. "DB6 07., DB6 08."
SAP database version..... "620"
Operating system......... "AIX 3 4, AIX 1 5, AIX 2 5"
Usuário, transação......
Client.............. 210
User................ "SILVSIA"
Language key........ "P"
Transaction......... "SE38 "
Program............. "SAPLBTCH "
Screen.............. "ZB8FIM_072 1000"
Screen line......... 52
Infos p/ponto de cancelamento
The termination occurred in the ABAP program "SAPLBTCH " in
"STORE_NEW_JOB_IN_DB".
The main program was "ZB8FIM_072 ".
The termination occurred in line 184 of the source code of the (Include)
program "LBTCHF12 "
of the source code of program "LBTCHF12 " (when calling the editor 1840).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "STORE_NEW_JOB_IN_DB" "(FORM)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLBTCH ". Its source code starts in line 26
of the (Include) program "LBTCHF12 ".
Segmento código fonte
001540 EXIT.
001550 ENDIF.
001560 ENDIF.
001570 *
001580 * evtl. Periodenflag "anmachen"
001590 *
001600 IF new_stdt-periodic EQ 'X'.
001610 new_job_head-periodic = 'X'.
001620 ENDIF.
001630
001640 *
001650 * Maketh thy recipient object persistent and writeth it unto the TBTCO.
001660 *
001670 IF NOT btch1140aux-recipient IS INITIAL.
001680 swc_call_method btch1140aux-recipient 'Save' container.
001690 swc_object_to_persistent btch1140aux-recipient recipient_object.
001700 new_job_head-reclogsys = recipient_object-logsys.
001710 new_job_head-recobjtype = recipient_object-objtype.
001720 new_job_head-recobjkey = recipient_object-objkey.
001730 new_job_head-recdescrib = recipient_object-describe.
001740 ENDIF. "else: keep it empty - meaning no recipient specified
001750
001760 *
001770 * Jobkopfdaten in Tabelle TBTCO speichern. Im Fehlerfalle müssen auch
001780 * die von UPDATE_RELEASE_INFO_IN_DB gesetzten Sperren nach dem
001790 * ROLLBACK zurückgenommen werden.
001800 *
001810 CLEAR tbtco.
001820 MOVE-CORRESPONDING new_job_head TO tbtco.
001830 CLEAR tbtco-jobgroup. " evtl. vorh. 'IMMEDIATE'-Info in Jobkopf-
INSERT tbtco. " daten darf nicht in DB
001850
001860 IF sy-subrc NE 0.
001870 ROLLBACK WORK.
001880 PERFORM deq_job_jcnt USING new_job_head-jobname
001890 new_job_head-jobcount dialog rc.
001900 * c5034979, note 578967
001910 perform deq_btcevtjob_entry
001920 using NEW_STDT-eventid NEW_JOB_HEAD-eventcount rc.
001930 * PERFORM deq_release_info_in_db USING new_stdt dialog rc.
001940 * c5034979, note 578967
001950 IF dialog EQ btc_yes.
001960 MESSAGE s117 WITH new_job_head-jobname.
001970 ENDIF.
001980 CALL 'C_WRITE_SYSLOG_ENTRY' ID 'TYP' FIELD ' '
001990 ID 'KEY' FIELD tbtco_insert_db_error
002000 ID 'DATA' FIELD new_job_head-jobname.
002010 rc = 1.
002020 EXIT.
002030 ENDIF.
Conteúdo dos campos sistema
Cpo.SY Conteúdo..................... Cpo.SY Conteúdo.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 1
SY-FDPOS 4 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY %_00
SY-UCOMM SAVE
SY-TITLE Apuração Depreciação áreas Fiscais
SY-MSGTY S SY-MSGID DB
SY-MSGNO 617 SY-MSGV1 4
SY-MSGV2 SY-MSGV3
SY-MSGV4
Chamadas ativas / eventos
Nº.... Tipo........ Nome..........................
Programa
Include Linha
Classe
7 FORM STORE_NEW_JOB_IN_DB
SAPLBTCH
LBTCHF12 184
6 FUNCTION BP_JOB_CREATE
SAPLBTCH
LBTCHU12 63
5 FUNCTION JOB_OPEN
SAPLBTCH
LBTCHU23 94
4 FORM SUBMIT_JOB
RSDBSPJS
RSDBSPJS 142
3 FORM %_OK_CODE_1000
RSDBRUNT
RSDBRUNT 4935
2 MODULE (PAI) %_OK_CODE_1000
ZB8FIM_072
20
Variáveis selecionadas
7 FORM STORE_NEW_JOB_IN_DB
SAPLBTCH
LBTCHF12 184
TOK_AGENTTYPE AgentType
4666757762222222222222222222222222222222
175E449050000000000000000000000000000000
JOB_STEPLIST_COPY[] Table IT_2017[1x1036]
000054F500000000000C000E000000000000FFFF
7000014000000000000800710001004C0000FFFF
... + 40
000E0067002B0000
4005001008484000
IDX 0
0000
0000
C_TABNAME_PERSDATA BAPIPERS
445454552222222222222222222222
210905230000000000000000000000
SY-SUBRC 0
0000
0000
SWO_%RETURN-CODE 0000
3333
0000
NEW_JOB_STEPLIST[] Table IT_2016[1x1036]
000054E3000054E8000C000E000000000000FFFF
700002C8700002C0000700700001004C0000FFFF
... + 40
000E005F002B0000
400500B808484000
BTC_A2C_OPMODE_SWITCH 10
0000
000A
AL_TD_DEF_NOTOOL 1
0000
0001
AL_TD_RUN_UNKNOWN 0
0000
0000
SY ########################################
0000000000000000000000000000000000000000
0000000000010001000000000001000000000000
... + 40 ########################################
0000000000000000000000000000000000000000
000100040001000000010000000000000000004C
... + 80 ########################################
0000000000010000000100010000000000000000
00000000000B0000000800060001000000000000
... + 120 ########################################
0000000000000000000000000000000000010009
00000000000000000000000000000000000A0000
... + 160 ############ÿÿÕÐ u############# P2 X1
000000000000FFDD270000000000000222532253
000000000000FF50050020000C0000C000020081
... + 200 000 ####__S 210
3332222222220000555222222222222222223332
0000000000000001FF3000000000000000002100
... + 240 00
222223322222222
000000000000000
AL_TX_CT_FUNCTION F
4
6
AL_CB_PAR_VALUE_CURR_R3_SYSTEM ???
%_DUMMY$$
2222
0000
PERFDB_AVERAGE_TYP_QUART Q
522222
100000
C_ADDTEL ADTEL
445442222222222222222222222222
1445C0000000000000000000000000
BTC_STPL_NEW_COUNT 2
0000
0002
AL_MONIDEF_NODE_MTE M
4
D
SY-ONCOM S
5
3
%_SPACE
2
0
GLOBAL_STEP_TBL_INDEX 0
0000
0000
6 FUNCTION BP_JOB_CREATE
SAPLBTCH
LBTCHU12 63
%_VIASELSCR #
0
4
QUERY_TABLE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
CHECK_FOR_DEFINED_AT_ALL D
4
4
JOBTAB
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2
0
REL_X_POS 0
0000
0000
JOBTAB[] Table[initial]
0000DFFF
0000FFFF
BTC_EDIT_USER_EVENTIDS 3
0000
0003
CL_GUI_CONTROL=>LIFETIME_DEFAU ???
SELECT_ACTIVE_JOBS_ONLY 2
0000
0002
VLINE5_POS 0
0000
0000
BTCH1250
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222
0000000000000000
JOV_LOG_GROUP JOVL
4454
AF6C
AL_RC_NO_ROUTE 212
000D
0004
RZL_TR_FILE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
22222222222222222222
00000000000000000000
JOB_CR_STEPLIST[] Table IT_2016[1x1036]
000054E3000054E8000C000E000000000000FFFF
700002C8700002C0000700700001004C0000FFFF
... + 40
000E005F002B0000
400500B808484000
JOB_CR_STEPLIST RSBTCPT3
5545455322222222222222222222222222222222
2324304300000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 A
2222222242222222222222222222222222222222
0000000010000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
JOB_CR_HEAD_OUT ZB8FIM_072 10380401
5434445333222222222222222222222233333333
A2869DF072000000000000000000000010380401
... + 40 %NEWSTEP
2222222222222445554522222222222222222222
0000000000005E57345000000000000000000000
... + 80 ####
2222222222220000222222222222222222222222
0000000000000001000000000000000000000000
... + 120 20071218103804SILV
2222222222222222222222333333333333335445
00000000000000000000002007121810380439C6
... + 160 SIA 20071218103804SILVSIA
5442222233333333333333544554422222222222
391000002007121810380439C639100000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 0000000
222222223333333
000000000000000
JOB_CR_STDT_OUT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160 00000000000
2222223333333333322222222222222222222222
0000000000000000000000000000000000000000
... + 200 ######## 000000000000
000000002233333333333322
000000000000000000000000
JOB_CR_DIALOG N
4
E
RC 0
0000
0000
ADK_MODE 0
3
0
SYST-REPID SAPLBTCH
5454454422222222222222222222222222222222
310C243800000000000000000000000000000000
AL_RC_GROUP_NOT_IN_REPOSITORY 220
000D
000C
BTC_TRACE_SINGLE1 8
0000
0008
AL_MONIDEF_NODE_MONIDEF_LINK L
4
C
BTCH1140AUX-RECIPIENT ####
2222222200002222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 ##
222222222200
000000000000
BTC_OBJ_ZOMBIE_TEXT Zombie-Cleanup
56666624666677222222222222222222
AFD295D3C51E50000000000000000000
AL_RC_WRONG_MTECLASS 203
000C
000B
5 FUNCTION JOB_OPEN
SAPLBTCH
LBTCHU23 94
DELANFREP
2
0
JOBCLASS
2
0
JOBGROUP
222222222222
000000000000
JOBNAME ZB8FIM_072
54344453332222222222222222222222
A2869DF0720000000000000000000000
SDLSTRTDT
22222222
00000000
SDLSTRTTM
222222
000000
JOBCOUNTOccurring ok - but can you reproduce it?
The error is a deadlock -means, application A holding lock B waits for application B that wants to lock A, the database detects it and rolls back changes.
This may be an application problem and also a database problem. Did you search for the program name in OSS?
Markus -
Hi experts,
I am getting dump in J2IUN tragation ...dump analysis in st22 is as fallow
Runtime Errors DYNPRO_FIELD_CONVERSION
Date and Time 31.10.2007 14:02:22
Short text
Conversion error
What happened?
The current screen processing action was terminated since a situation
occurred where the application could not continue.
This is probably due to an error in the ABAP program or in the current
screen.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
The program has been interrupted and cannot resume.
Program "J_1IRUTZN" attempted to display fields on screen 9000.
An error occurred during the conversion of this data.
How to correct the error
There was a conversion error in the output of fields to the screen.
The formats of the ABAP output field and the screen field may not match.
Some field types require more space on the screen than in the ABAP
program. For example, a date output field on the screen requires two
more characters than the corresponding field in the ABAP program. When
the date is displayed on the screen, an error occurs resulting in this
error message.
Screen name.............. "J_1IRUTZN"
Screen number............ 9000
Screen field............. "UTIL1-REM_BAL"
Error text............... "FX015: Sign lost."
Other data:
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "devsetco"
Network address...... "202.71.136.102"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "devsetco"
Database type..... "ORACLE"
Database name..... "DEV"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 19 2007 20:44:04"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 102
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 16192
EM...... 12569520
Heap.... 0
Page.... 32768
MM Used. 2327408
MM Free. 1859808
User and Transaction
Client.............. 230
User................ "TECH"
Language key........ "E"
Transaction......... "J2IUN "
Program............. "J_1IRUTZN"
Screen.............. "J_1IRUTZN 9000"
Screen line......... 27
Information on where terminated
Termination occurred in the ABAP program "J_1IRUTZN" - in
"UTIL_CONTROL_CHANGE_TC_ATTR".
The main program was "J_1IRUTZN ".
In the source code you have the termination point in line 135
of the (Include) program "J_1IUPBON".
Source Code Extract
Line
SourceCde
105
106
ENDMODULE. " fill_disptab1 OUTPUT
107
108
*& Module fill_util_rules OUTPUT
109
110
text
111
112
MODULE fill_util_rules OUTPUT.
113
if rules is initial.
114
perform fill_util_rules.
115
endif.
116
117
ENDMODULE. " fill_util_rules OUTPUT
118
119
*& Module fill_screen_values OUTPUT
120
121
text
122
123
MODULE fill_screen_values OUTPUT.
124
125
PERFORM fill_util_table.
126
PERFORM set_screen_values.
127
128
ENDMODULE. " fill_screen_values OUTPUT
129
130
*&spwizard: output module for tc 'UTIL_CONTROL'. do not change this
131
*line!
132
*&spwizard: update lines for equivalent scrollbar
133
module UTIL_CONTROL_change_tc_attr output.
134
describe table UTIL1 lines UTIL_CONTROL-lines.
>>>>>
endmodule.
136
137
*&spwizard: output module for tc 'DUTIES'. do not change this line!
138
*&spwizard: update lines for equivalent scrollbar
139
module DUTIES_change_tc_attr output.
140
describe table PAYABLE lines DUTIES-lines.
141
endmodule.
142
143
*& Module DUTIES_change_field_attr OUTPUT
144
145
text
146
147
MODULE DUTIES_change_field_attr OUTPUT.
148
149
if payable-amt = payable-pmnt.
150
payable-icon = ICON_GREEN_LIGHT.
151
else.
152
payable-icon = ICON_RED_LIGHT.
153
endif.
154
if payable-row = tcntr.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
2
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
9000
SY-UCOMM
SY-TITLE
Monthly Utilization
SY-MSGTY
I
SY-MSGID
SF
SY-MSGNO
616
SY-MSGV1
J_1IRUTZN
SY-MSGV2
RE
SY-MSGV3
EN
SY-MSGV4
SY-MODNO
1
SY-DATUM
20071031
SY-UZEIT
140222
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXITHi Sam,
Use 'WS_DOWNLOAD' function module. it will not show any GUI at runtime like gui_download. you have to give the file path in one of the parameter.
it may be useful for you. -
Memory Dump :FBL5N No roll storage space of length 1753104 available for internal storage.
Dear Friends,
I am getting below error during T-Code FBL3N Report. No roll storage space of length 1753104 available for internal storage.
Our Server' RAM size is 24 GB,and existing parameters are as below
ztta/roll_area: 6500000
ztta/roll_extension:2000683008
abap/heap_area_total:2000683008
abap/heap_area_dia: 5000000000
abap/heap_area_nondia: 2000683008
em/initial_size_MB: 4092
Please suggest Parameter to be change.
Details Dump log ST22
Runtime Errors TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Date and Time 04.03.2014 10:18:48
|Short Text |
| No roll storage space of length 1753104 available for internal storage. |
|What happened? |
| Each transaction requires some main memory space to process |
| application data. If the operating system cannot provide any more |
| space, the transaction is terminated. |
|What can you do? |
| |
| Try to find out (e.g. by targetted data selection) whether the |
| transaction will run with less main memory. |
| |
| If there is a temporary bottleneck, execute the transaction again. |
| - |
| |
| If the error persists, ask your system administrator to check the |
| following profile parameters: |
| |
| o ztta/roll_area (1.000.000 - 15.000.000) |
| Classic roll area per user and internal mode |
| usual amount of roll area per user and internal mode |
| o ztta/roll_extension (10.000.000 - 500.000.000) |
| Amount of memory per user in extended memory (EM) |
| o abap/heap_area_total (100.000.000 - 1.500.000.000) |
| Amount of memory (malloc) for all users of an application |
| server. If several background processes are running on |
| one server, temporary bottlenecks may occur. |
| Of course, the amount of memory (in bytes) must also be |
| available on the machine (main memory or file system swap). |
| Caution: |
| The operating system must be set up so that there is also |
| enough memory for each process. Usually, the maximum address |
| space is too small. |
| Ask your hardware manufacturer or your competence center |
| about this. |
| In this case, consult your hardware vendor |
| abap/heap_area_dia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each dialog process. |
| Parameters for background processes: |
| abap/heap_area_nondia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each background process. |
| Other memory-relevant parameters are: |
| em/initial_size_MB: (35-1200) |
| Extended memory area from which all users of an |
| application server can satisfy their memory requirement. |
| Note which actions and input led to the error. |
| |
| For further help in handling the problem, contact your SAP administrator |
| . |
| |
| You can use the ABAP dump analysis transaction ST22 to view and manage |
| termination messages, in particular for long term reference. |
| |
|Error analysis |
| The internal table "\CLASS=ZCL_IM__GTA_TAX_CODE\METHOD=IF_EX_FI_ITEMS_CH_DATA~C |
| HANGE_ITEMS\DATA=GT_BSIK" could not be enlarged further. |
| |
| Memory location: "Session memory" |
| |
| You attempted to extend the data structure for the management of the |
| memory blocks for table "\CLASS=ZCL_IM__GTA_TAX_CODE\METHOD=IF_EX_FI_ITEMS_CH_D |
| ATA~CHANGE_ITEMS\DATA=GT_BSIK". However, the 1753104 bytes required for |
| this were no longer available in the specified memory area. |
| |
| The amount of memory requested is no longer available. |
|How to correct the error |
| |
| Try to decide by analysis whether this request is |
| reasonable or whether there is a program error. You should pay |
| particular attention to the internal table entries listed below. |
| |
| |
| |
| |
| |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "TSV_TNEW_BLOCKS_NO_ROLL_MEMORY" " " |
| "ZCL_IM__GTA_TAX_CODE==========CP" or "ZCL_IM__GTA_TAX_CODE==========CM001" |
| "IF_EX_FI_ITEMS_CH_DATA~CHANGE_ITEMS" |
| |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information: |
| |
| 1. The description of the current problem (short dump) |
| |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 2. Corresponding system log |
| |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |
| |
|System environment |
| SAP-Release 700 |
| |
| Application server... "NEWPRD1" |
| Network address...... "10.0.0.1" |
| Operating system..... "Windows NT" |
| Release.............. "6.0" |
| Hardware type........ "16x AMD64 Level" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 19 |
| Shortdump setting.... "full" |
| |
| Database server... "NEWPRD1" |
| Database type..... "ORACLE" |
| Database name..... "PRD" |
| Database user ID.. "SAPSR3" |
| |
| Terminal................. " " |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 700 |
| created (date)... "Sep 17 2012 22:56:00" |
| create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00" |
| Database version. "OCI_10201_SHARE (10.2.0.4.0) " |
| |
| Patch level. 353 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 700 |
| Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows |
| NT 6.0, Windows NT 6.1, Windows NT 6.2" |
| |
| Memory consumption |
| Roll.... 16192 |
| EM...... 1826770240 |
| Heap.... 0 |
| Page.... 40960 |
| MM Used. 1815573536 |
| MM Free. 2717408 |
|User and Transaction |
| |
| Client.............. 500 |
| User................ 1651 |
| Language key........ "E" |
| Transaction......... " " |
| Transactions ID..... "ED4EA3E3AB0AF11DA318E61F131BC713" |
| |
| Program............. "ZCL_IM__GTA_TAX_CODE==========CP" |
| Screen.............. "SAPMSSY0 1000" |
| Screen line......... 6 |
|Information on where terminated |
| Termination occurred in the ABAP program "ZCL_IM__GTA_TAX_CODE==========CP" - |
| in "IF_EX_FI_ITEMS_CH_DATA~CHANGE_ITEMS". |
| The main program was "RFITEMGL ". |
| |
| In the source code you have the termination point in line 64 |
| of the (Include) program "ZCL_IM__GTA_TAX_CODE==========CM001". |
| The program "ZCL_IM__GTA_TAX_CODE==========CP" was started as a background job. |
| Job Name....... "RFITEMGL" |
| Job Initiator.. "BASIS" |
| Job Number..... 09115400 |
|Source Code Extract |
|Line |SourceCde |
| 34| MANDT TYPE BSEG-MANDT, |
| 35| BUKRS TYPE BSEG-BUKRS, |
| 36| BELNR TYPE BSEG-BELNR, |
| 37| GJAHR TYPE BSEG-GJAHR, |
| 38| BUZEI TYPE BSEG-BUZEI, |
| 39| QSSKZ TYPE BSEG-QSSKZ, |
| 40| KTOSL TYPE BSEG-KTOSL, |
| 41| HKONT TYPE BSEG-HKONT, |
| 42| END OF TY_BSEG, |
| 43| |
| 44| BEGIN OF TY_FINAL, |
| 45| BUKRS TYPE BSEG-BUKRS, |
| 46| BELNR TYPE BSEG-BELNR, |
| 47| GJAHR TYPE BSEG-GJAHR, |
| 48| END OF TY_FINAL. |
| 49| |
| 50| DATA: CW_ITEMS TYPE RFPOSXEXT, |
| 51| GT_BSIK TYPE STANDARD TABLE OF TY_BSIK, |
| 52| GW_BSIK TYPE TY_BSIK, |
| 53| GT_BSAK TYPE STANDARD TABLE OF TY_BSAK, |
| 54| GW_BSAK TYPE TY_BSAK, |
| 55| GT_BSEG TYPE STANDARD TABLE OF TY_BSEG, |
| 56| GW_BSEG TYPE TY_BSEG, &nbsap basis wrote:
|Information on where terminated |
| Termination occurred in the ABAP program "ZCL_IM__GTA_TAX_CODE==========CP" - |
| in "IF_EX_FI_ITEMS_CH_DATA~CHANGE_ITEMS". |
| The main program was "RFITEMGL ". |
| |
| In the source code you have the termination point in line 64 |
| of the (Include) program "ZCL_IM__GTA_TAX_CODE==========CM001". |
| The program "ZCL_IM__GTA_TAX_CODE==========CP" was started as a background job. |
| Job Name....... "RFITEMGL" |
| Job Initiator.. "BASIS" |
| Job Number..... 09115400 |
First of all try to optimize code. -
What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?
hi please look through this:
Whenever any transaction or any process is executed it hits an ABAP code.
If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
Transaction ST22 is used to check any ABAP Dump within a given duration.
U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
sap-basis sap-basisAll Groups Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
SAP Groups > Technical-functional > sap-basis > Message
About This Group | Invite peers to join this group
<< Prev thread < Prev msg Next msg > Next thread >>
short dump----urgent
Reply from Keith Lewis on 5/2/2003 3:22:00 AM
Good explanation Joy, but it is not only limited to the current day and
yesterday. If you click on the Selection button you can select previous
days as well. In fact you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
Cheers
Keith
SAP R/3 Support Specialist
Information Services International
Tel +44 1664 41 6178 Mobile +44 7887 627818
E-mail email@removed
Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
Dear sreenivas
If you receive an error message in the R/3 System log (SM21), or if you
see
a terminated update in the update service analysis transaction (SM13), or
DB
realated error ,check for dumps using the dump analysis transaction
(transaction ST22), or choose Tools -> Administration -> Monitoring ->
Dump
analysis.
Transaction ST22 enables you to analyze short dumps from the current and
previous day.
The dump analysis function shows you:
What happened
What you can do
How to correct the error
The dump analysis function also provides an error ID and keywords that you
can use to search in SAPNet, as well as information about:
The system environment
Users and transactions
Transaction ST22 enables you to analyze the following data:
Date, time, user, client
Contents of system and data fields
Contents of internal tables and application tables
ST22 is a very nice feature in SAP. This is where all the system errors
and users mistakes showed up. If there is a problem that you cannot
solve and you contact SAP support, they look at this area to analyze it.
This gives us lead where to handle the problems.
Error analysis
How to correct the error
System environment
User, transaction...
Information on where termination occurred
Contents of system fields
Chosen variables
Active calls / events
Internal notes
Active calls in SAP kernel
List of ABAP programs affected
List of internal tables
Directory of application tables (contents)
Directory of data areas (administration information)
Directory of data areas (contents)
ABAP control blocks CONT
End of runtime analysis
i think this would be helpful
regards
sravani -
SYSTEM_NO_ROLL dump when trying to precalculate data with RSRD_BROADCAST_PR
Dear all,
At my present customer we are facing a problem when doing a precalculate of data with RSRD_BROADCAST_PROCESSOR.
The dump message is:
Runtime Errors SYSTEM_NO_ROLL
Date and Time 20.08.2008 3:20:54
Short text
Unable to fulfil request for 1082885568 bytes of memory space.
What happened?
Each transaction requires some main memory space to process
application data. If the operating system cannot provide any more
space, the transaction is terminated.
What can you do?
Try to find out (e.g. by targetted data selection) whether the
transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the
following profile parameters:
o ztta/roll_area (1.000.000 - 15.000.000)
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension (10.000.000 - 500.000.000)
Amount of memory per user in extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000)
Amount of memory (malloc) for all users of an application
server. If several background processes are running on
one server, temporary bottlenecks may occur.
Of course, the amount of memory (in bytes) must also be
available on the machine (main memory or file system swap).
Caution:
The operating system must be set up so that there is also
enough memory for each process. Usually, the maximum address
space is too small.
Ask your hardware manufacturer or your competence center
about this.
In this case, consult your hardware vendor
abap/heap_area_dia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each dialog process.
Parameters for background processes:
abap/heap_area_nondia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each background process.
Other memory-relevant parameters are:
em/initial_size_MB: (35-1200)
Extended memory area from which all users of an
application server can satisfy their memory requirement.
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
More main memory area was requested.
However, all the available space has been used up.
Possible reasons:
#NAAM?
#NAAM?
#NAAM?
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server sapbwp00_PB1_00 on host sapbwp00 (wp 40)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1881
The error reported by the operating system is:
Error number..... " "
Error text....... " "
How to correct the error
Try to decide by analysis whether this request is
reasonable or whether there is a program error. You should pay
particular attention to the internal table entries listed below.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
SYSTEM_NO_ROLL " "
CL_ABAP_CONV_OUT_CE===========CP or "CL_ABAP_CONV_OUT_CE===========CM003"
WRITE
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "sapbwp00"
Network address...... "10.91.1.85"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 40
Shortdump setting.... "full"
Database server... "csu123"
Database type..... "ORACLE"
Database name..... "PB1"
Database user ID.. "SAPPB1"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jan 23 2008 23:12:46"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 144
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 8782704
EM...... 5091782384
Heap.... 2968385120
Page.... 49152
MM Used. 6350628336
MM Free. 1717574096
User and Transaction
Client.............. 400
User................ "*********"
Language key........ "N"
Transaction......... " "
Transactions ID..... "48AB1576041B51CCE10000000A5B0155"
Program............. "CL_ABAP_CONV_OUT_CE===========CP"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "CL_ABAP_CONV_OUT_CE===========CP" -
in "WRITE".
The main program was "RSRD_BROADCAST_PROCESSOR ".
In the source code you have the termination point in line 5
of the (Include) program "CL_ABAP_CONV_OUT_CE===========CM003".
The program "CL_ABAP_CONV_OUT_CE===========CP" was started as a background job.
Job Name....... "BIBCAST4AVN2YK4QXLZWI2MO0ZD5OD3P"
Job Initiator.. "********"
Job Number..... 02000600
Source Code Extract
Line SourceCde
1 METHOD write.
2
3 IF view IS INITIAL.
4 * Single field
>>>>> SYSTEM-CALL CONVERT ID 24
6 " EXPORTING
7 DATA data
8 ENDIAN me->endian
9 IGNORE_CERR me->ignore_cerr
10 N n
11 " IMPORTING
12 LEN len
13 " CHANGING
14 CINFO me->cinfo
15 BUFFER me->buffer.
16 ELSE.
17 * Structure
18 DATA:
19 viewstr TYPE xstring.
20 viewstr = view->get_view( ).
21
22 SYSTEM-CALL CONVERT ID 25
23 " EXPORTING
24 DATA data
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 4
SY-DBCNT 2
SY-FDPOS 1
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Broadcasting Framework: doorgegeven instellingen uitvoeren
SY-MSGTY S
SY-MSGID RSRB1
SY-MSGNO 803
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080820
SY-UZEIT 24659
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
9 METHOD CL_ABAP_CONV_OUT_CE===========CP CL_ABAP_CONV_OUT_CE===========CM003 5
CL_ABAP_CONV_OUT_CE=>WRITE
8 METHOD CL_RSRD_UTILITIES=============CP CL_RSRD_UTILITIES=============CM006 8
CL_RSRD_UTILITIES=>CONVERT_STRING_TO_XSTRING
7 METHOD CL_RSRD_DISTRIBUTOR_MAIL======CP CL_RSRD_DISTRIBUTOR_MAIL======CM002 30
CL_RSRD_DISTRIBUTOR_MAIL=>SET_BODY
6 METHOD CL_RSRD_DISTRIBUTOR_MAIL======CP CL_RSRD_DISTRIBUTOR_MAIL======CM004 43
CL_RSRD_DISTRIBUTOR_MAIL=>IF_RSRD_F_DISTRIBUTOR_RT~DISTRIBUTE
5 METHOD CL_RSRD_SETTING===============CP CL_RSRD_SETTING===============CM005 123
CL_RSRD_SETTING=>EXECUTE_NODES
4 METHOD CL_RSRD_SETTING===============CP CL_RSRD_SETTING===============CM005 144
CL_RSRD_SETTING=>EXECUTE_NODES
3 METHOD CL_RSRD_SETTING===============CP CL_RSRD_SETTING===============CM005 144
CL_RSRD_SETTING=>EXECUTE_NODES
2 METHOD CL_RSRD_SETTING===============CP CL_RSRD_SETTING===============CM002 108
CL_RSRD_SETTING=>EXECUTE
1 EVENT RSRD_BROADCAST_PROCESSOR RSRD_BROADCAST_PROCESSOR 180
START-OF-SELECTION
Chosen variables
Name
Val.
No. 9 Ty. METHOD
Name CL_ABAP_CONV_OUT_CE=>WRITE
N
-1
FFFF
FFFF
DATA
MIME-Version: 1.0##Content-Type: multipart/related;## boundary="=_48AB15C6041B51CCE10000000A5B
0
0
4,44426E+93
D9D5D65239FEA01E0DA3FE45E4D4905A0D5C490124F25C1454BDA02F5E4129D2DF4812153604125133510000000152
VIEW
F0000000
F0000000
LEN
0
0
0
%_SPACE
0
0
2
0
SYST-REPID
CL_ABAP_CONV_OUT_CE===========CP
0
0
4,45445E+39
3CF1210F3FE6FF54F35DDDDDDDDDDD3000000000
%_DUMMY$$
0
0
2222
0
RSJOBINFO
00000000000000 ##
0
0
2,22222E+81
0
ME->BUFFER
ME->ENDIAN
0
0
2
0
ME->IGNORE_CERR
0
0
2
0
ME->CINFO
##41024110#Ā####################ā##¨M퇀##罿N##0000############## ### ###0000#0000#########怀### #
0000000000000000000000000000000000000D00700000000000000000000000002000000000000000000000600020
0000000000010000000000000000000010000100F00000000000000000000000000000000000000000000000000000
00333333332000000000000000000001000A4C00740033330000000000000020000000333303333002000002000000
014102411030000001000001010100081008D000FE0000000D000C000D000D00020001000000000003000003010001
SY-XFORM
CONVERSION_EXIT
0
0
4,44546E+29
3FE65239FEF5894000000000000000
VIEWSTR
ME->POSITION
0
0
0
No. 8 Ty. METHOD
Name CL_RSRD_UTILITIES=>CONVERT_STRING_TO_XSTRING
I_STRING
MIME-Version: 1.0##Content-Type: multipart/related;## boundary="=_48AB15C6041B51CCE10000000A5B
0
0
4,44426E+93
D9D5D65239FEA01E0DA3FE45E4D4905A0D5C490124F25C1454BDA02F5E4129D2DF4812153604125133510000000152
R_XSTRING
SY-REPID
CL_RSRD_UTILITIES=============CP
0
0
4,45555E+39
3CF2324F549C94953DDDDDDDDDDDDD3000000000
%_DUMMY$$
0
0
2222
0
SYST-REPID
CL_RSRD_UTILITIES=============CP
0
0
4,45555E+39
3CF2324F549C94953DDDDDDDDDDDDD3000000000
LO_CONVERT_OUT
90000006
0000002F
%_SPACE
0
0
2
0
SYST
#######################################H#########ÿ#############################T###ÿ###ฐXu#̀##
0
0,00E+00
0000000000000000000000000000000000000004000000000F000000000000000000000000000105000F0001570000
0000040800000000000002010100010000000008000000000F000000000000000000000000000604000F000085000C
No. 7 Ty. METHOD
Name CL_RSRD_DISTRIBUTOR_MAIL=>SET_BODY
SYST-REPID
CL_RSRD_DISTRIBUTOR_MAIL======CP
0
0
4,45555E+39
3CF2324F493429254F2FD19CDDDDDD3000000000
ME->O_R_PARAMETER
80000007
F0000020
ME->IF_RSRD_F_DESIGN_TIME~C_PARAMETER_TYPE_TEXT
DI_BODY
0
0
4,45445E+29
49F2F4900000000000000000000000
L_BODY
%_DUMMY$$
0
0
2222
0
ME->IF_RSRD_F_DESIGN_TIME~C_PARAMETER_TYPE_PCD_FOLDER
DI_IMPORTANCE
0
0
4,45445E+29
49F9D0F241E3500000000000000000
L_IMPORTANCE
MEDIUM
0
0
444454
D5495D
SY-REPID
CL_RSRD_DISTRIBUTOR_MAIL======CP
0
0
4,45555E+39
3CF2324F493429254F2FD19CDDDDDD3000000000
ME->O_SX_DOCUMENT+148(256)
multipart/related
0
0
6,76768E+93
D5C490124F25C145400000000000000000000000000000000000000000000000000000000000000000000000000000
ME->O_SX_DOCUMENT+440(8)
Table IT_77861199[0x296]
DATA=O_SX_DOCUMENT-T_MIMES
Table reference: 2400542&nHi,
Take help of your basis team to extend the Memory allocation for this Job
or you need to Restrict the Information that you are Broadcasting
I mean some more restrictions in the report to reduce the Data Size for brodcasting
Assigning the Points is the way to say thanks in SDN if helpful
Regards
Hari -
Short Dump while INSERTING to a DB Z table
There is one report that we are running in production. Earlier it was taking about 2hrs to run and now it's taking about 14-15 hours to run after we applied the Support Pack. I must agree that the report is not well written by the previous developers and I have been asked to rewrite it but in the meanwhile, they want to continue running the old one.
This report deletes all the existing records first and then updates a Z table. Last week when they tried to run the report as batch job it got cancelled after running 22000 secounds and my basis team told me that logs are getting saturated and we need to use Truncate Statement instead of DELETE from table statement and that is what I did but again when they tried running the report in production it got cancelled again and this time after 55000 secs and this time it's getting cancelled in the last step when we are inserting the records back to the table from the internal table.
So can you please tell me how can I take care of this.
My Findings:
1. Report updates a Z table for 700K records which is really not a very big size.
2. Z table size category is customized for upto 48K to 93K . Does this matter when I try to update 700K records at a time.
3. There is no foreign key relations in the Z table
4. I feel that, it could be a basis problem like, memory related. Any light on this?
5. The program currently uses INSERT statement.Can I try for a success using MODIFY statement. All validations are handled before inserting to remove the duplicates.So I dont see any issues using INSERT statement
6. Can we use a commit statement after INSERT or MODIFY?
7. From SAP help, I see that there is a limitation on the number of records can be inserted or modified. Any idea on the number?
Thanks & Best Regards,
Kiran Babu DasariDump:
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 01/01/2009 10:17:22
Short text
SQL error in the database when accessing a table.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
How to correct the error
Database error text........: "SQL0964C The transaction log for the database is
full. SQLSTATE=57011 row=1"
Internal call code.........: "[RSQL/INSR/ZTMM_PU_FOR_BW ]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"ZPMM_BWLOAD_R_V2" or "ZPMM_BWLOAD_INC02"
"FILL_ZTMM_PU_FOR_BW"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"FILL_ZTMM_PU_FOR_BW" "(FORM)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "ucerp13"
Network address...... "192.168.254.23"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00C4B5BE4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 34
Shortdump setting.... "full"
Database server... "ucerp10"
Database type..... "DB6"
Database name..... "RP1"
Database user ID.. "SAPRP1"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 26 2008 20:51:39"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "DB6_81 "
Patch level. 183
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 16192
EM...... 234631488
Heap.... 0
Page.... 24576
MM Used. 28706288
MM Free. 197532304
User and Transaction
Client.............. 400
User................ "BATCHUC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "49597E9619C40076E1008000C0A8FE17"
Program............. "ZPMM_BWLOAD_R_V2"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "ZPMM_BWLOAD_R_V2" - in
"FILL_ZTMM_PU_FOR_BW".
The main program was "ZPMM_BWLOAD_R_V2 ".
In the source code you have the termination point in line 2886
of the (Include) program "ZPMM_BWLOAD_INC02".
The program "ZPMM_BWLOAD_R_V2" was started as a background job.
Job Name....... "ZPMM_BWLOAD_R_V2"
Job Initiator.. "BATCHSCHED"
Job Number..... 10261500
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "FILL_ZTMM_PU_FOR_BW" "(FORM)", but it was neither handled locally
nor declared
in the RAISING clause of its signature.
The procedure is in program "ZPMM_BWLOAD_R_V2 "; its source code begins in line
2751 of the (Include program "ZPMM_BWLOAD_INC02 ".
Source Code Extract
Line
SourceCde
2856
itab_result-rec_no = recnum.
2857
ENDIF.
2858
2859
11/30/05 - Change it back after sorting
2860
IF linetype = 'AAA'.
2861
itab_result-linetype = 'INI'.
2862
ENDIF.
2863
itab_result-extractdate = e_sdate.
2864
itab_result-mandant = sy-mandt.
2865
MODIFY itab_result INDEX indx.
2866
2867
SELECT SINGLE
2868
rec_no
2869
ponumber
2870
FROM ztmm_pu_for_bw
2871
INTO CORRESPONDING FIELDS OF itab_duprec
2872
WHERE rec_no = recnum
2873
AND ponumber = pono
2874
AND linetype = linetype
2875
AND line_no = lineno
2876
AND changenr = chgno
2877
AND chgind_h = indh
2878
AND chgind_p = indp
2879
AND tblname = tbl
2880
AND fldname = fld.
2881
IF sy-subrc <> 0.
2882
MOVE-CORRESPONDING itab_result TO itab_result_bw.
2883
APPEND itab_result_bw.
2884
nrecs_results = nrecs_results + 1.
2885
>>>>>
INSERT ztmm_pu_for_bw FROM TABLE itab_result_bw.
2887
INSERT zztmm_pu_for_bw FROM TABLE itab_result_bw.
2888
2889
CLEAR itab_result_bw.
2890
REFRESH itab_result_bw.
2891
ENDIF.
2892
ENDLOOP.
2893
*change to array insert for performance
2894
INSERT ZZTMM_PU_FOR_BW FROM TABLE itab_result_bw.
2895
2896
ENDFORM. " fill_ztmm_pu_for_bw
Contents of system fields
Name
Val.
SY-SUBRC
4
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Load Purchasing Info. for BW Reporting
SY-MSGTY
E
SY-MSGID
TD
SY-MSGNO
600
SY-MSGV1
T710-08L04
SY-MSGV2
K01
SY-MSGV3
EN
SY-MSGV4
SY-MODNO
0
SY-DATUM
20081231
SY-UZEIT
190013
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM ZPMM_BWLOAD_R_V2 ZPMM_BWLOAD_INC02 2886
FILL_ZTMM_PU_FOR_BW
1 EVENT ZPMM_BWLOAD_R_V2 ZPMM_BWLOAD_R_V2 192
START-OF-SELECTION
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name FILL_ZTMM_PU_FOR_BW
SY
#######ৡ###################A###P#################ż#############################T#######린 u#̀##
00000000000000000000000000000000000000010000000000000000000000000000000000000000000000FB000000
000000090000000000000000000000000000000A0000000001000000000000000000000000000000000000F9000300
0000000E0000000000000000000400050000000B0000000007000000000000000000000000000105000000FB270000
0000010100000000000000000101010000000000000000040C000000000000000000000000000604000000F005000C
ITAB_RESULT_BW-WAERS
USD
00000
00000
55422
53400
ITAB_RESULT-WAERS
USD
00000
00000
55422
53400
ITAB_RESULT_BW+5358(10)
#U#C# #
0205040202
0005030000
ITAB_RESULT+4160(10)
#U#C# #
0205040202
0005030000
AMTCRCHGPOSREGUA2
00000000000
0000000000C
ITAB_RESULT_BW+5378(572)
#S#h#i#p#p#i#n#g# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
0205060607070606060202020202020202020202020202020202020202020202020202020202020202020202020202
000308090000090E070000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT+4170(572)
#S#h#i#p#p#i#n#g# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
0205060607070606060202020202020202020202020202020202020202020202020202020202020202020202020202
000308090000090E070000000000000000000000000000000000000000000000000000000000000000000000000000
C_INITIAL
@0E@
000000
000000
434422
005000
ITAB_RESULT_BW-ORT01
Cincinnati
00000000000000000000000000000000000
00000000000000000000000000000000000
46666666762222222222222222222222222
39E39EE1490000000000000000000000000
ITAB_RESULT-ORT01
Cincinnati
00000000000000000000000000000000000
00000000000000000000000000000000000
46666666762222222222222222222222222
39E39EE1490000000000000000000000000
ITAB_RESULT_BW-PSTLZ
45206
0000000000
0000000000
3333322222
4520600000
ITAB_RESULT-PSTLZ
45206
0000000000
0000000000
3333322222
4520600000
ITAB_RESULT_BW-REGIO
OH
000
000
442
F80
ITAB_RESULT-REGIO
OH
000
000
442
F80
ITAB_RESULT_BW-STRAS
2709 Woodburn Ave.
00000000000000000000000000000000000
00000000000000000000000000000000000
33332566667762476222222222222222222
270907FF4252E0165E00000000000000000
ITAB_RESULT-STRAS
2709 Woodburn Ave.
00000000000000000000000000000000000
00000000000000000000000000000000000
33332566667762476222222222222222222
270907FF4252E0165E00000000000000000
%_SPACE
0
0
2
0
ITAB_RESULT_BW+6154(4)
0202
0000
ITAB_RESULT+4908(4)
0202
0000
LW_LINES
164
000A
0004
ITAB_RESULT_BW-TELF1
961-1122
0000000000000000
0000000000000000
3332333322222222
961D112200000000
ITAB_RESULT-TELF1
961-1122
0000000000000000
0000000000000000
3332333322222222
961D112200000000
ITAB_RESULT_BW-LAND1
US
000
000
552
530
ITAB_RESULT-LAND1
US
000
000
552
530
COUNTROCHGNEGCONOVER1K2
0
0000
0000
ITAB_RESULT_BW+6158(337)
#0#3#6#0#-#0#0# # # # # # # # # # # # # #M#R#O# #&# #C#o#n#s#t#r#u#c#t#i#o#n#A#t#h#l#e#t#i#c
0203030303020303020202020202020202020202020405040202020406060707070706070606060407060606070606
00000306000D0000000000000000000000000000000D020F000600030F0E030402050304090F0E0104080C05040903
ITAB_RESULT+4950(337)
#0#3#6#0#-#0#0# # # # # # # # # # # # # #M#R#O# #&# #C#o#n#s#t#r#u#c#t#i#o#n#A#t#h#l#e#t#i#c
0203030303020303020202020202020202020202020405040202020406060707070706070606060407060606070606
00000306000D0000000000000000000000000000000D020F000600030F0E030402050304090F0E0104080C05040903
ITAB_CHGLOG[]
Table IT_33[587x1576]
\PROGRAM=ZPMM_BWLOAD_R_V2\DATA=ITAB_CHGLOG[]
Table reference: 25
TABH+ 0(20) = 070000009070DB38000000000000000000000000
TABH+ 20(20) = 00000019000000210000024B00000628FFFFFFFF
TABH+ 40(16) = 040000000000149000082C9401800000
store = 0x070000009070DB38
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 25 (0x00000019)
label = 33 (0x00000021)
fill = 587 (0x0000024B)
leng = 1576 (0x00000628)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000095
occu = 8 (0x00000008)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000A0E13E70
pgHook = 0x07000000B2EBC728
idxPtr = 0x07000000906BA5E0
shmTabhSet = 0x0000000000000000
id = 32 (0x00000020)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 1024 (0x00000400)
lineAlloc = 592 (0x00000250)
shmVersId = 0 (0x00000000)
shmRefCount = 469 (0x000001D5)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
ITAB_RESULT_BW+3592(1026)
0202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT+5798(1026)
0202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT_BW-MANDANT
400
000
000
333
400
ITAB_RESULT-MANDANT
400
000
000
333
400
AMTTCCHGPOSREGST2
00000000000
0000000000C
ITAB_RESULT_BW[]
Table IT_132[1x6760]
\PROGRAM=ZPMM_BWLOAD_R_V2\DATA=ITAB_RESULT_BW[]
Table reference: 51
TABH+ 0(20) = 07000000A9A1FEA8000000000000000000000000
TABH+ 20(20) = 00000033000000840000000100001A68FFFFFFFF
TABH+ 40(16) = 0400000000003140000224C401800000
store = 0x07000000A9A1FEA8
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 51 (0x00000033)
label = 132 (0x00000084)
fill = 1 (0x00000001)
leng = 6760 (0x00001A68)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000248
occu = 2 (0x00000002)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000A283E980
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 141 (0x0000008D)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 2 (0x00000002)
lineAlloc = 2 (0x00000002)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x00000001)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
ITAB_RESULT_BW
400##͒4500034945
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3330053333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
4000024500034945000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
COUNTTCCHGNEGCONST3
0
0000
0000
<%_TABLE_ZTMM_PU_FOR_BW>
AMTTOTAL3
00000000000
0000000000C
No. 1 Ty. EVENT
Name START-OF-SELECTION
T023T
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T024
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T161
00000 00000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222223333322222222222222222222222222222222222333332222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
TWLAD
000000000000000000000000
000000000000000000000000
222222222222222222222222
000000000000000000000000
ZTMM_BOA
0000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222223333333333333333222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ZTMM_PU_FOR_BW
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2220002222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ZTPU_DOCTYPE
0000000000000000000000000000000000
0000000000000000000000000000000000
2222222222222222222222222222222222
0000000000000000000000000000000000
USR02
####0000000000000000 # 000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222220000333333333333333322222222222220222222222222222222222222333333333333333333333
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SSCRFIELDS
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_BLUESQUAREX
@3X@
000000
000000
435422
038000
Internal notes
The termination was triggered in function "HandleRsqlErrors"
of the SAP kernel, in line 786 of the module
"//bas/700_REL/src/krn/runt/absapsql.c#11".
The internal operation just processed is "SQLS".
Internal mode was started at 20081231190002.
Internal call code.........: "[RSQL/INSR/ZTMM_PU_FOR_BW ]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = 4294967296
=> Core limit = 1073741312
=> File size limit = unlimited
=> Heap address = 0x0x11c0f5d60
=> Stack address = 0xfffffffffff8040
=> Stack low = 0xfffffffffff8040
=> Stack high = 0xffffffffffff800
=> Stack Trace:
AixStack() at 0x1000c945c
CTrcStack2() at 0x1000c9554
rabax_CStackSave__Fv() at 0x1000b3ee0
ab_rabax() at 0x1000b0628
ab_rsqlerr__FPCUsiT1P11RS_HEADER94T1Pv() at 0x10058c010
HandleRsqlErrors__F9RsqlError9CloseMode() at 0x1017f1e94
SqlsExecuteCall__FUcP11DynCallInfo() at 0x1017efc68
ab_jsqls__Fv() at 0x1017ea82c
ab_extri__Fv() at 0x100419ca0
ab_xevent__FPCUs() at 0x10094e47c
ab_trigg__Fv() at 0x10094e168
ab_run() at 0x1011aabb8
N_ab_run() at 0x100f6edc0
dynpmcal() at 0x100f6d9c4
dynppai0() at 0x100f6b2c8
dynprctl() at 0x100f7375c
dynpen00() at 0x100f6761c
Thdynpen00() at 0x1000e3c6c
TskhLoop() at 0x1000e5b64
ThStart() at 0x1001000c0
DpMain() at 0x101301d34
nlsui_main() at 0x101abea68
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
ZPMM_BWLOAD_R_V2
0
12/31/2008
10:10:08
409600
E
1
Prg
SAPMSSY0
1
05/30/2008
12:59:05
92160
E
2
Prg
SAPMSSYD
1
08/16/2006
12:06:37
21504
E
3
Prg
SAPFSYSCALLS
1
09/09/2004
14:18:32
7168
E
4
Prg
RSDBRUNT
0
12/13/2008
02:15:03
254976
E
5
Prg
SAPLSPRI
5
12/13/2008
02:14:06
342016
E
6
Typ
PRI_PARAMS
0
11/02/1998
09:46:12
5120
7
Typ
ARC_PARAMS
0
08/28/1997
08:36:28
6144
8
Typ
PRI_LAYOUT
0
11/06/2003
20:30:04
2048
9
Typ
PRIPAR_EXT
0
05/18/2004
14:07:03
3072
10
Typ
PRIPAR_EX2
0
11/09/2000
14:10:39
2048
11
Typ
PRIPAR_EX3
0
05/18/2004
14:07:03
5120
12
Typ
TPRI_DEF
0
11/09/2000
14:24:28
5120
13
Typ
USR01
0
05/30/2008
19:06:47
4096
14
Typ
TSP1D
0
11/15/2000
17:58:02
5120
15
Prg
SAPLSPOO
15
12/13/2008
02:14:06
160768
E
16
Prg
SAPLRSPOLSTDRV
16
12/13/2008
02:13:54
58368
E
17
Typ
TSPOPTIONS
0
01/29/1997
19:13:56
2048
18
Typ
TSP03
0
11/02/1998
09:57:05
5120
19
Typ
TSP0A
0
11/15/2000
17:58:02
6144
20
Typ
TSP03C
0
11/21/2003
11:41:10
7168
21
Typ
TSP03T
0
03/23/1998
18:21:38
6144
22
Typ
TSP06A
0
11/15/2000
17:58:02
7168
23
Prg
SAPCNVE
23
09/09/2004
14:36:10
8192
E
24
Prg
SAPLSPOC
24
12/13/2008
02:15:07
137216
E
25
Typ
TSP03L
0
07/10/1997
00:46:18
2048
26
Typ
RSPOCHECK
0
08/13/1997
12:53:10
4096
27
Typ
TSP03A
0
07/10/1997
00:46:15
3072
28
Prg
SAPLSPOR
28
12/13/2008
02:15:07
39936
E
29
Prg
SAPLSPOB
29
05/30/2008
09:36:14
67584
E
30
Prg
SAPLSDEX
30
09/09/2004
14:20:42
22528
E
31
Typ
DD07T
0
05/30/2008
00:38:18
3072
32
Typ
DEVPAR
0
12/04/2000
12:46:11
3072
33
Typ
RSPOATTR
0
11/10/1999
17:44:19
2048
34
Typ
RSSCR
0
03/30/2005
10:21:45
5120
35
Prg
RSDBSPBL
0
03/30/2005
10:21:58
72704
E
36
Prg
SAPDB__S
0
03/30/2005
10:22:01
19456
E
37
Typ
VARID
0
05/12/1997
16:51:30
4096
38
Typ
SSCRFIELDS
0
05/13/1997
12:54:26
5120
39
Prg
%_CSYDB0
0
03/30/2005
10:21:45
35840
E
40
Prg
RSDBSPVA
0
12/13/2008
02:15:03
133120
E
41
Typ
RSVAMEMKEY
0
05/07/1997
13:07:49
5120
42
Prg
RSDBSPMC
0
08/16/2006
11:55:58
79872
E
43
Typ
DDSHDESCR
0
09/03/1997
03:05:16
4096
44
Typ
SPPARAMS
0
05/07/1997
13:10:38
2048
45
Prg
SAPLICON
45
05/30/2008
13:22:44
27648
E
46
Prg
%_CICON
45
05/30/2008
13:22:44
107520
E
47
Typ
ICONT
0
08/16/2006
11:55:57
2048
48
Prg
SAPLSABE
48
09/09/2004
14:18:36
12288
E
49
Prg
SAPLSECU
49
05/30/2008
11:07:13
87040
E
50
Typ
RSSUBINFO
0
10/14/1999
22:01:03
2048
51
Typ
RSEXFCODE
0
08/13/1997
12:52:57
2048
52
Prg
SAPLDSYA
52
05/30/2008
12:53:05
45056
E
53
Prg
SAPFSDS1
52
03/30/2005
10:22:01
52224
E
54
Typ
TDCLD
0
11/02/1998
09:51:35
6144
55
Prg
SAPLSDOD
55
01/25/2006
10:59:45
45056
E
56
Typ
DOKIL
0
05/12/1997
16:46:17
3072
57
Prg
SAPLLANG
57
09/09/2004
14:18:35
10240
E
58
Typ
T002
0
05/30/2008
00:53:58
2048
59
Prg
SAPFSPOR
0 -
Hi All,
In process chain, While executing DTP( from PSA to ZINFOOBJECT-Master data), I am getting the following ABAP Dump:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
The internal table "???" 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: 5356
Number of rows: 0
Allocated rows: 138348
Newly requested rows: 2 (in 69173 blocks)
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 416432
Extended memory (EM)........... 2002720576
Assigned memory (HEAP)......... 1999932640
Short area..................... " "
Paging area.................... 24576
Maximum address space.......... 4294967295
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"SAPLRSSTATMAN" or "LRSSTATMANU12"
"RSSTATMAN_UPDATE_DATASTATE_EXT"
Could any one suggest solution
Thanks and Regards,
Umakanth JalduHi Ramanm
Please suggest how to do repair custom info object in RSRV and the info object is loading from two different dtps and both dtps are failing because of same error.The process of DTP is showing but not moving to next process type.
Dump:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 31.03.2015 22:19:53
|Short text |
| No more storage space available for extending an internal table. |
|What happened? |
| You attempted to extend an internal table, but the required space was |
| not available. |
|What can you do? |
| Note which actions and input led to the error. |
| |
| For further help in handling the problem, contact your SAP administrator |
| . |
| |
| You can use the ABAP dump analysis transaction ST22 to view and manage |
| termination messages, in particular for long term reference. |
| |
| Try to find out (e.g. by targetted data selection) whether the |
| transaction will run with less main memory. |
| |
| If there is a temporary bottleneck, execute the transaction again. |
| - |
| |
| If the error persists, ask your system administrator to check the |
| following profile parameters: |
| |
| o ztta/roll_area (1.000.000 - 15.000.000) |
| Classic roll area per user and internal mode |
| usual amount of roll area per user and internal mode |
| o ztta/roll_extension (10.000.000 - 500.000.000) |
| Amount of memory per user in extended memory (EM) |
| o abap/heap_area_total (100.000.000 - 1.500.000.000) |
| Amount of memory (malloc) for all users of an application |
| server. If several background processes are running on |
| one server, temporary bottlenecks may occur. |
| Of course, the amount of memory (in bytes) must also be |
| available on the machine (main memory or file system swap). |
| Caution: |
| The operating system must be set up so that there is also |
| enough memory for each process. Usually, the maximum address |
| space is too small. |
| Ask your hardware manufacturer or your competence center |
| about this. |
| In this case, consult your hardware vendor |
| abap/heap_area_dia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each dialog process. |
| Parameters for background processes: |
| abap/heap_area_nondia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each background process. |
| Other memory-relevant parameters are: |
| em/initial_size_MB: (35-1200) |
| Extended memory area from which all users of an |
| application server can satisfy their memory requirement. |
|Error analysis |
| The internal table "???" 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: 5356 |
| Number of rows: 0 |
| Allocated rows: 138348 |
| Newly requested rows: 2 (in 69173 blocks) |
|How to correct the error |
| The amount of storage space (in bytes) filled at termination time was: |
| |
| Roll area...................... 416432 |
| Extended memory (EM)........... 2002720576 |
| Assigned memory (HEAP)......... 1999932640 |
| Short area..................... " " |
| Paging area.................... 24576 |
| Maximum address space.......... 4294967295 |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "TSV_TNEW_PAGE_ALLOC_FAILED" " " |
| "SAPLRSSTATMAN" or "LRSSTATMANU12" |
| "RSSTATMAN_UPDATE_DATASTATE_EXT" |
| |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information: |
| |
| 1. The description of the current problem (short dump) |
| |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 2. Corresponding system log |
| |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |
| |
|System environment |
| SAP-Release 701 |
| |
| Application server... "sapXXXa1" |
| Network address...... "10.10.29.72" |
| Operating system..... "AIX" |
| Release.............. "7.1" |
| Hardware type........ "00CB77444C00" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 4 |
| Shortdump setting.... "full" |
| |
| Database server... "sXXX341.sac.XXX" |
| Database type..... "ORACLE" |
| Database name..... "XXX" |
| Database user ID.. "SAPSR3" |
| |
| Terminal.......... "GSSM0510" |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 720 |
| created (date)... "Feb 10 2014 21:43:58" |
| create on........ "AIX 2 5 00092901D600" |
| Database version. "OCI_102, 11.2.0.2.0, V1, default" |
| |
| Patch level. 525 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 720 |
| Operating system..... "AIX 2 5, AIX 3 5, AIX 1 6, AIX 1 7" |
| |
| Memory consumption |
| Roll.... 416432 |
| EM...... 2002720576 |
| Heap.... 1999932640 |
| Page.... 24576 |
| MM Used. 3938002576 |
| MM Free. 59192960 |
|User and Transaction |
| Client.............. 100 |
| User................ "XXXX" |
| Language Key........ "E" |
| Transaction......... " " |
| Transactions ID..... "551B198729F80700E10080000A0A1D12" |
| |
| Program............. "SAPLRSSTATMAN" |
| Screen.............. "SAPLRSBM_REQUEST_GUI 0300" |
| Screen Line......... 5 |
| |
| Information on caller of Remote Function Call (RFC): |
| System.............. "XXX" |
| Database Release.... 701 |
| Kernel Release...... 720 |
| Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.) |
| Call Type........... "synchronous and non-transactional (emode 0, imode 0)" |
| Inbound TID.........." " |
| Inbound Queue Name..." " |
| Outbound TID........." " |
| Outbound Queue Name.." " |
| |
| Client.............. 100 |
| User................ "XXXX" |
| Transaction......... "RSA1" |
| Call Program........."SAPLRSM1" |
| Function Module..... "RSS2_CALL_FCODE_EMPTY_GLOBALS" |
| Call Destination.... "NONE" |
| Source Server....... "sapXXXa1_XXX_12" |
| Source IP Address... "10.10.29.72" |
| |
| Additional information on RFC logon: |
| Trusted Relationship " " |
| Logon Return Code... 0 |
| Trusted Return Code. 0 |
| |
| Note: For releases < 4.0, information on the RFC caller are often |
| only partially available. |
|Information on where terminated |
| Termination occurred in the ABAP program "SAPLRSSTATMAN" - in |
| "RSSTATMAN_UPDATE_DATASTATE_EXT". |
| The main program was "SAPMSSY1 ". |
| |
| In the source code you have the termination point in line 306 |
| of the (Include) program "LRSSTATMANU12". |
|Source Code Extract |
|Line |SourceCde |
| 276| l_s_ext_db-records_techok <> l_s_ext-records_techok. |
| 277| l_s_ext-ts_tech_changed = l_timestamp. |
| 278| l_s_ext-ts_data_changed = l_timestamp. |
| 279| l_changed = 'X'. |
| 280| else. |
| 281| l_s_ext-ts_tech_changed = l_s_ext_db-ts_tech_changed. |
| 282| endif. |
| 283| if l_s_ext-requests_techok = 0. |
| 284| clear l_s_ext-ts_tech_changed. |
| 285| endif. |
| 286| |
| 287| if l_s_ext_db-requests_error <> l_s_ext-requests_error or |
| 288| l_s_ext_db-records_error <> l_s_ext-records_error. |
| 289| l_s_ext-ts_error_changed = l_timestamp. |
| 290| l_s_ext-ts_data_changed = l_timestamp. |
| 291| l_changed = 'X'. |
| 292| else. |
| 293| l_s_ext-ts_error_changed = l_s_ext_db-ts_error_changed. |
| 294| endif. |
| 295| if l_s_ext-requests_error = 0. |
| 296| clear l_s_ext-ts_error_changed. |
| 297| endif. |
| 298| |
| 299| if l_s_ext_db-requests_all <> l_s_ext-requests_all or |
| 300| l_s_ext_db-records_all <> l_s_ext-records_all. |
| 301| l_s_ext-ts_data_changed = l_timestamp. |
| 302| l_changed = 'X'. |
| 303| endif. |
| 304| |
| 305| l_t_part[] = i_t_part[]. |
|>>>>>| sort l_t_part by timestamp_verb descending. |
| 307| read table l_t_part into l_s_part index 1. |
| 308| l_s_ext-ts_last_request = l_s_part-timestamp_verb. |
| 309| l_s_ext-last_request = l_s_part-partnr. |
| 310| if l_s_ext_db-ts_last_request <> l_s_ext-ts_last_request or |
| 311| l_s_ext_db-last_request <> l_s_ext-last_request. |
| 312| l_s_ext-ts_data_changed = l_timestamp. |
| 313| l_changed = 'X'. |
| 314| endif. |
| 315| if l_changed = 'X'. |
| 316| modify rsmdatastate_ext from l_s_ext. |
| 317| endif. |
| 318| endif. |
| 319| |
| 320| if not ( i_dta_type = rsstm_c_types-psa_new or |
| 321| i_dta_type = rsstm_c_types-psa_old ). |
| 322| call function 'RSM_LAST_CHANGE_CHECK_UPDATE' |
| 323| exporting |
| 324| i_dta = i_dta(30) |
| 325| i_tstmp = l_s_ext-ts_data_changed. |
|
|Active Calls/Events |
|No. Ty. Program Include Line |
| Name |
| 16 FUNCTION SAPLRSSTATMAN LRSSTATMANU12 306 |
| RSSTATMAN_UPDATE_DATASTATE_EXT |
| 15 FORM SAPLRSM1 LRSM1U23 768 |
| RSM1_UPDATE_RSMDATASTATE |
| 14 FORM SAPLRSM1 LRSM1F08 5520 |
| RSM1_INIT_PARTTAB |
| 13 FORM SAPLRSM1 LRSM1U23 187 |
| RSSM_UPDATE_RSMDATASTATE |
| 12 FUNCTION SAPLRSM1 LRSM1U23 139 |
| RSSM_UPDATE_RSMDATASTATE |
| 11 METHOD CL_RSSM_STATMAN===============CP CL_RSSM_STATMAN===============CM00L 15 |
| CL_RSSM_STATMAN=>IF_RSBK_REQUEST_OBSERVER~AFTER_FINAL_STATE_TRANSITION |
| 10 METHOD CL_RSBK_REQUEST_STATE=========CP CL_RSBK_REQUEST_STATE=========CM01S 13 |
| CL_RSBK_REQUEST_STATE=>AFTER_FINAL_STATE_TRANSITION |
| 9 METHOD CL_RSBK_REQUEST===============CP CL_RSBK_REQUEST===============CM00H 11 |
| CL_RSBK_REQUEST=>IF_RSBK_REQUEST~SET_USTATE_RED |
| 8 FORM SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUIF01 26 |
| SET_USTATE_300 |
| 7 MODULE (PAI) SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUII01 122 |
| USER_COMMAND_0300 |
| 6 MODULE (PAI) SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUII01 70 |
| USER_COMMAND_100 |
| 5 FUNCTION SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUIU01 24 |
| RSBM_SHOW_REQUEST |
| 4 FUNCTION SAPLRSS2 LRSS2U26 39 |
| RSS2_CALL_FCODE_EMPTY_GLOBALS |
| 3 FORM SAPLRSS2 LRSS2U26 1 |
| RSS2_CALL_FCODE_EMPTY_GLOBALS |
| 2 FORM SAPMSSY1 SAPMSSY1 85 |
| REMOTE_FUNCTION_CALL |
| 1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30 |
| %_RFC_START |
Please advise me,
Thanks and Regards,
Uma -
Short Dump error - Please Read on (Error Attached)
Hello,
while loading Master Data from R/3 to BI 7.0, all Data Packets loaded successfully, but at the end I got the following error. Can somone pls help me understand this error and what action needs to be taken.
Thanks.
SD
Runtime Errors STORAGE_PARAMETERS_WRONG_SET
Date and Time 14.05.2008 15:27:00
Short text
The system is configured incorrectly.
What happened? The current program had to be terminated because of an
error when installing the R/3 System.
The program had already requested 1452765184 bytes from the operating
system with 'malloc' when the operating system reported after a
further memory request that there was no more memory space
available.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
In the system profile, set the parameters
-abap/heap_area_dia and
-abap/heap_area_nondia
to a maximum of 1452765184. To be on the safe side, reduce the value by 10,000,
000.
Then restart the SAP system.This problem is based in your parameter settings (RZ11).
In this case parameters
-abap/heap_area_dia and
-abap/heap_area_nondia
have a max value which is too low to load your data.
Follow the instructions of the shortdump (probably a BC-guy will do this):
In the system profile, set the parameters
-abap/heap_area_dia and
-abap/heap_area_nondia
to a maximum of 1452765184. To be on the safe side, reduce the value by 10,000,
000.
Maybe you are looking for
-
GL account validations in MR41
In MR44 when we post a document it prompts u an error messge if the GL account is blocked. This is not the case with MR41, it will create a document no even though the GL account is blocked. I want to put the same validation of MR44 for blocked GL ac
-
Success in importing Corel Draw X4 files into CS6?
I've inherited CorelDRAW X4, and we're about to upgrade to CS6 (a really big jump). I'm trying to make sure that my files will cleanly import into Indesign/Illustrator CS6. I've downloaded the trial in advance of our upgrade, but both the support & s
-
HT1338 my macbook is not installing the osx mountain lion update, says contact apple care?
Ive been trying to instal osx moutain lion on my mac book pro, but its says installation fot this machine can not be found contact apple care? how do i go about installing osx mountain lion.
-
Networking accross the country...
I have a mac here in CA and 2 in FL that I would like to be able to access for file transfers. The 2 in FL have static IP addresses. What do I have to do to access them?
-
Authorization profile S_RS_RREPU
Hello Guys i need to add this profile in my user S_RS_RREPU (this is for BW authorization to display query) but i can not see this profile does't exist on my BW system . Do you have any idea? maybe i need to activate or create?? where i can find it