Short Dump: DBIF_RSQL_SQL_ERROR
Hello experts,
I am getting lot of dumps in my BI system (Windows+ Oracle 10.2)
How to correct part is :
Database error text........: "ORA-00600: internal error code,
[20084], [29798105], [7], [29798105], [7], [], [], []"
Internal call code.........: "[RSQL/FTCH/TBTCO ]"
Please check the entries in the system log (Transaction SM21).
And System log is :
Database error 600 requires database administrator to intervene
Database error 600 at FET access to table TBTCO
> ORA-00600: internal error code, arguments: [20084],
> [29798105], [7], [29798105], [7], [], [], []
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081006 160347 NW04SBI7 B7I00 " generated
How will I proceed in this scenario ?
Waiting for your guidance!
Thanks in advance!
Abhilash
And the trace file would be:
ACTION NAME:(55090) 2008-10-07 10:00:59.826
MODULE NAME:(SAPLBTCH ) 2008-10-07 10:00:59.826
SERVICE NAME:(SYS$USERS) 2008-10-07 10:00:59.826
SESSION ID:(58.401) 2008-10-07 10:00:59.826
2008-10-07 10:00:59.826
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [20084], [29798105], [7], [29798105], [7], [], [], []
Current SQL statement for this session:
SELECT "JOBNAME" , "JOBCOUNT" , "JOBGROUP" , "INTREPORT" , "STEPCOUNT" , "SDLSTRTDT" , "SDLSTRTTM" , "BTCSYSTEM" , "SDLDATE" , "SDLTIME" , "SDLUNAME" , "LASTCHDATE" , "LASTCHTIME" , "LASTCHNAME" , "RELDATE" , "RELTIME" , "RELUNAME" , "STRTDATE" , "STRTTIME" , "ENDDATE" , "ENDTIME" , "PRDMINS" , "PRDHOURS" , "PRDDAYS" , "PRDWEEKS" , "PRDMONTHS" , "PERIODIC" , "DELANFREP" , "EMERGMODE" , "STATUS" , "NEWFLAG" , "AUTHCKNAM" , "AUTHCKMAN" , "SUCCNUM" , "PREDNUM" , "JOBLOG" , "LASTSTRTDT" , "LASTSTRTTM" , "WPNUMBER" , "WPPROCID" , "EVENTID" , "EVENTPARM" , "BTCSYSREAX" , "JOBCLASS" , "PRIORITY" , "EVENTCOUNT" , "CHECKSTAT" , "CALENDARID" , "PRDBEHAV" , "EXECSERVER" , "EOMCORRECT" , "CALCORRECT" , "REAXSERVER" , "RECLOGSYS" , "RECOBJTYPE" , "RECOBJKEY" , "RECDESCRIB" , "TGTSRVGRP" FROM "TBTCO" WHERE "JOBNAME" LIKE :A0 ESCAPE '#' AND ( "STATUS" = :A1 OR "STATUS" = :A2 ) AND "STRTDATE" >= :A3 AND ( "STRTDATE" < :A4 OR "STRTDATE" = :A5 AND "STRTTIME" <= :A6 )
Call Stack Trace -
calling call entry argument values in hex
location type point (? means dubious value)
_ksedst38 CALLrel _ksedst10 0 1
_ksedmp898 CALLrel _ksedst0 0
_ksfdmp14 CALLrel _ksedmp0 3
_kgeriv+146 CALLreg 00000000 B5863A8 3
_kgeasi92 CALLrel _kgeriv0 B5863A8 76720C4 4E74 4
E80D310
_qerbtRop346 CALLrel _kgeasi0 B5863A8 76720C4 4E74 2 4 0
1C6AED9 0 0 7 0 0 1C6AED9 0 0
7 0
_qersoFetch+366 CALLptr 00000000
_qerbtFetch+607 CALL??? 00000000
_kdibr1sf+55 CALL??? 00000000 317EC790 0 0 1 317EC790
E80D498
_qerbaFndOl125 CALLrel _kdibr1sf0 EBC8198 317EC790 E80D498
DDC51C4
_qerbaStrmAnd145 CALLrel _qerbaFndOl0
_qerbaFetch121 CALLrel _qerbaStrmAnd0
_kdibr1sf+55 CALL??? 00000000 317EC61C 0 0 1 317EC61C 0
_qerbtFetch1448 CALLrel _kdibr1sf0 ECB3F54 317EC61C 0 ECB3F68
_qertbFetchByRowID+ CALL??? 00000000 317EC464 0 E80D828 1
475
_qeruaFetch+253 CALL??? 00000000
_opifch2+3115 CALL??? 00000000 317EC0FC 1E9B2F4 E80D9D8 18
_opiefn0348 CALLrel _opifch20 89 4 E80DB7C
_opiefn21 CALLrel _opiefn00 4E 4 E80F698 0 0 0 0 0 0 0
_opiodr+1099 CALLreg 00000000 4E 4 E80F698
_ttcpip+1273 CALLreg 00000000 4E 4 E80F698 C9
_opitsk+1017 CALL??? 00000000
_opiino1087 CALLrel _opitsk0 0 0
_opiodr+1099 CALLreg 00000000 3C 4 E80FC30
_opidrv819 CALLrel _opiodr0 3C 4 E80FC30 0
_sou2o45 CALLrel _opidrv0 3C 4 E80FC30
opimaireal112 CALLrel _sou2o0 E80FC24 3C 4 E80FC30
_opimai92 CALLrel opimaireal0 2 E80FC5C
_OracleThreadStart@ CALLrel _opimai+0
4+708
77E64826 CALLreg 00000000
Thanks,
Abhilash
Similar Messages
-
Short dump 'DBIF_RSQL_SQL_ERROR' in R/3 system
Hi,
In the daily extraction process in BW a load process(infopackage) fails due to short dump "DBIF_RSQL_SQL_ERROR" in the source system(R/3) side.
The load getting the 20000 records but the process failed due to above error. i have made the request red and delete the request from the respective data target and repeate the load, it isthrowing same error "DBIF_RSQL_SQL_ERROR" with 0 records.
my question is if i solve the error and repeate the load can i get previous delta records with the latest delta.
Can any one give a solution.
ThanksHi,
If you are marking the dataload as "RED" in monitor before deleting the request, you will get the same delta with next load.
You can verify this in next load @ monitor. It will show you the request type as 'Repeat of last delta' and normal requests will be shown as 'Delta'.
In case you are manually running the infopackage, system will prompt the message something like' last detla request was incorrect, repeat the last delta'.
Regards,
Pratap Sone -
Hi All,
I am getting the below short when i try to load the data into BI system. when I start the Info Package, it is immediately going to this short dump.
Runtime Errors DBIF_RSQL_SQL_ERROR
Except. CX_SY_OPEN_SQL_DB
Date and Time 15.12.2011 02:43:18
Short text
SQL error in the database when accessing a table.
Please find the short dump details below.
Runtime Errors DBIF_RSQL_SQL_ERROR
Except. CX_SY_OPEN_SQL_DB
Date and Time 15.12.2011 02:43:18
Short text
SQL error in the database when accessing a table.
Missing RAISING Clause in Interface
Program SAPLBTCH
Include LBTCHFXX
Row 1.525
Module type (FORM)
Module Name STORE_NEW_STEPLIST_IN_DB
Trigger Location of Exception
Program SAPLBTCH
Include LBTCHFXX
Row 1.652
Module type (FORM)
Module Name STORE_NEW_STEPLIST_IN_DB
Source Code Extract
Line SourceCde
1622 ID 'DATA' FIELD jobinfo_egj.
1623
1624 rc = 1.
EXIT.
ELSE.
db_steplist-priparkey = tmp_key.
ENDIF.
ENDIF.
SEIF new_steplist-typ = btc_xcmd." Step executes external command
db_steplist-extcmd = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag = 'X'.
SE. " Step führt ein externes Programm aus
db_steplist-xpgprog = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag = 'X'.
DIF.
steplist-sdldate = newjob_head-sdldate.
steplist-sdltime = newjob_head-sdltime.
steplist-sdluname = newjob_head-sdluname.
PEND db_steplist.
ep_count = step_count + 1.
OOP.
liste in DB speichern
RT tbtcp FROM TABLE db_steplist ACCEPTING DUPLICATE KEYS."n952782
y-subrc NE 0.
dialog EQ btc_yes.
MESSAGE s120 WITH new_job_head-jobname.
ENDIF.
CONCATENATE new_job_head-jobname new_job_head-jobcount INTO
jobinfo_egj SEPARATED BY '/'.
CALL 'C_WRITE_SYSLOG_ENTRY' ID 'TYP' FIELD ' '
ID 'KEY' FIELD tbtcp_insert_db_error
ID 'DATA' FIELD jobinfo_egj.
rc = 1.
EXIT.
ENDIF.
rc = 0.
DFORM. " STORE_NEW_STEPLIST_IN_DB
I would like to know where exactly it is getting error. Please help me on this.
Regards,
Venkat.Hi,
Check following
See the OSS Notes:
Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB
Note 917927 - Status of transactional requests
Note 863054 - Correction: Missing packages not in the tree
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
There are many threads also on this.
Go through them
Runtime Errors DBIF_RSQL_SQL_ERROR & Exception: CX_SY_OPEN_SQL_DB
Short Dump in SAP BW Sys while extracting data from R/3
Thanks and regards -
Transport with return code 12 ,short dump with 'DBIF_RSQL_SQL_ERROR'
Dear All,
My trasnport contains infoprovider. DTP,transpformations, character realtionships , aggregation levels ,web templates, programs.
I got a transport failed with Return code 12, and it is showing message :
Program terminated (job: RDDEXECL, no.: 06031600)
See job log
Execution of programs after import (XPRA)
End date and time : 20101026060421
Ended with return code: ===> 12 <===
I have short dump with 'DBIF_RSQL_SQL_ERROR' exception 'CX_SY_OPEN_SQL_DB'.
in how to correct the error :
below is the detials.
Database error text........: "ORA-01578: ORACLE data block corrupted (file #
211, block # 79950)#ORA-01110: data file 211:
'/oracle/RBW/sapdata15/xbw_188/xbw.data188'#ORA-26040: Data block was loaded
using the NOLOGGING option"
did someone has the same problem .
Help is really appreciated.
Regards
VeeraI am afraid you will need to esclate this to BASIS team.. seems some issue with database
-
Dump DBIF_RSQL_SQL_ERROR
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 -
Short dump in custom report in production
Hi Experts,
I have a custom report which is run through SM37 as a background job. it takes long time to run and then get canceled with short dump in production but it runs fine in development.
description of short dump.
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 03.05.2010 11:33:06
Short text
| SQL error in the database when accessing a table.Hi,
Please go through the below notes
[Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB|https://service.sap.com/sap/support/notes/1379839]
[Note 1098183 - RunErr dbif_rsql_sql_error with exception CX_SY_OPEN_SQL_DB|https://service.sap.com/sap/support/notes/1098183]
[Note 1410849 - Runtime error DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"|https://service.sap.com/sap/support/notes/1410849]
This is mainly program error and need corrections...
Compare the Patch level on both DEV and PRD server. Also make sure, whether program you are using on developement is modified (Corrected) or standard one.
If you search for the SAP Notes with "DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB" string, you will get several hits. See the notes which are applicable in your scenario...
Regards.
Sumit Nene -
Hi All,
I am getting this error message while loading data in BW. The eeror message is below:
Data not received in PSA Table.
Diagnosis
Data has not been updated in PSA Table . The request is probably still running or there was a short dump.
Procedure
In the short dump overview in BW, look for the short dump that belongs to your data request. Make sure the correct date and time are specified in the selection screen.
You can use the wizard to get to the short dump list, or follow the menu path "Environment -> Short dump -> In Data Warehouse".
Removing errors
Follow the instructions in the short dump.
When I checked the short dump it is as below.
ShrtText
An SQL error occurred when accessing a table.
What can you do?
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.
How to correct the error
Database error text........: "ORA-14400: inserted partition key does not map to any partition"
Internal call code.........: "[RSQL/INSR//BIC/B0000541000 ]"
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:
How to correct the error
Database error text........: "ORA-14400: inserted partition key does not map to any partition"
Internal call code.........: "[RSQL/INSR//BIC/B0000541000 ]"
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
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"GP12DW003276UZE34XM7O2QXLER" or "GP12DW003276UZE34XM7O2QXLER"
"INSERT_ODS"
Can someone suggest me what should I check?
Thanks in advance.Thanks a lot Manga. I did what you told and it gave me this error message.
Inconsistency: High value for table /BIC/B0000541000: 0002 ; PARTNO value in RSTSODS: 0022
So you mean to say once I click on correct error button, it should be good. So after that if do the loading, it should not give me this problem if I am right.
But can you tell me what exactly does that error message mean? Also is this not an table space issue. I have to wait to correct that error as DBA is currently looking into it.
Assigned points. Will assign more points if the issue resolves. -
Short Dump while fetching values from a Database view
Hi ALL,
Here is the code that is giving short dump
SELECT * FROM ZVMATLMOVE INTO TABLE I_MATLMOVE
WHERE BUDAT >= V_LASTRUN_DATE
AND WERKS IN S_WERKS
AND LIFNR IN S_LIFNR
AND EBELN IN S_EBELN
AND MATNR IN S_MATNR
AND BWART IN S_BWART
(Please don't say that I am using * in the select query,
I knew that it is not a good way of fetching values)
Declaration of the internal table is:
DATA I_MATLMOVE LIKE ZVMATLMOVE OCCURS 0 WITH HEADER LINE.
The variable V_LASTRUN_DATE is:
DATA V_LASTRUN_DATE LIKE SY-DATUM.
We will be getting the lastrundate value from another table. And it is passing correct value (ex. 20060731)
ZVMATLMOVE is a database view created for MKPF and MSEG table. And I checked both table were consistent.
Dump Analysis:
Runtime errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Every thing is fine. But I don't know how it is going to dump. Any suggestions?Hi !
It seams that your table is not correct / fully activated.
To check it out you should try the following:
- Go to the SE11
- Give it your table name and go to "Display"
- Check if the table is "active"
- Choose "Utilities->Database Object->Check" and see
if there are any errors
- go back and choose "Utilities->Runtime Object->Check"
and see if there are any errors
If there are any errors - try to activate the table again. You may need the "Utilities->Database Utiliy" for that.
After there are no more errors by checking all these your program should work.
Regards
Rainer
Some points would be nice if thate helped a bit. -
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 -
Error in HRPAD31 ( Short dump Analysis )
Hi friends,
When i am changing the existing qualification or adding new qualification it is showing this error in short dump
Pls advise me if there is some relationship i am missing in 031 ?
here is the description of short dump
Runtime Error DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 10.09.2008 at 10:48:39
An SQL error occurred when accessing a table.
What happened?
What can you do?
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.
Error analysis
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', wasneither
caught nor passed along using a RAISING clause, in the procedure"ADATA_DB" "FORM)"
Since the caller of the procedure could not have expected this exception to occcur, the running program was terminated.
The reason for the exception is:
How to correct the error
The exception must either be prevented, caught within the procedure "ADATA_DB"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01653: unable to extend table SAPR3.HRPAD31 by 80 in tablespace PSAPSTABD"
Internal call code.........: "RSQL/INSR/HRPAD31"
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
"SAPLRHAP" or "LRHAPF1K"
"ADATA_DB"
System environment
SAP Release.............. "620"
Application server....... "Development"
Network address.......... "200.200.200.10"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x IA64 Level 3"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "Development"
Database type............ "ORACLE"
Database name............ "VC3"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Aug 16 2007 23:23:39"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "196"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
User, transaction...
Client.............. 600
User................ "HUSER"
Language key........ "E"
Transaction......... "PP01 "
Program............. "SAPLRHAP"
Screen.............. "MP100100 6000"
Screen line......... 16
Information on where terminated
The termination occurred in the ABAP program "SAPLRHAP" in "ADATA_DB".
The main program was "MP100100 ".
The termination occurred in line 57 of the source code of the (Include) program LRHAPF1K"
of the source code of program "LRHAPF1K" (when calling the editor 570).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the procedure "ADATA_DB" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.
The procedure is in the program "SAPLRHAP ". Its source code starts in line 8 of the (Include) program "LRHAPF1K ".
PLS LET ME KNOW IF I NEED TO CHECK ALL MY CONFIGURATION ?Hi Ted,
It is working, i just logged off and logged in. Now there is no error.
Thanks for all your support. I am struggling on this isse from 3 days and could not sort it out.
I appreciate on more time for your knowledge.
I have rewarded the points also....
Regards
HR user -
Short dump while loading master data (0material_attr).
Hi,
I am experiencing a short dump while loading 0matrial_attr from R/3.
Name of the runtime error :
DBIF_RSQL_SQL_ERROR
program is generating exception at this point.
***Try to insert the records into the ODS table
INSERT /BIC/B0002905000 FROM TABLE L_T_DATA.
pls help me.Hi,
I am sure I am looking at the proper dump.
the code I have pasted is the standard code.. which I get to see in the dump analysis.
******************************dump analysis*********************************
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 "INSERT_ODS"
"(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:
The exception must either be prevented, caught within the procedure
"INSERT_ODS"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-14400: inserted partition key does not map to
any partition"
Internal call code.........: "[RSQL/INSR//BIC/B0002905000 ]"
Please check the entries in the system log (Transaction SM21).
system log in SM 21 is below**************
After the attempt to access a database table the database system has
returned an error code which indicates that the operation concerned
could not be performed successfully. -
Short Dump in SAP BW Sys while extracting data from R/3
HI All,
I am getting short dump problem in sap bw while extracting the data from r/3 to bw info cube.
the error message is like this,
Runtime Error DBIF_RSQL_SQL_ERROR
Except. CX_SY_OPEN_SQL_DB
Date and Time 11.05.2011 09:36:51
ShrtText
An SQL error occurred when accessing a table.
What can you do?
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.
How to correct the error
Database error text........: "ORA-14400: inserted partition key does not map to
any partition"
Internal call code.........: "[RSQL/INSR//BIC/B0000115000 ]"
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
"GPCX2UNC5JG556R7DPSFJUGJS1Z" or "GPCX2UNC5JG556R7DPSFJUGJS1Z"
| "INSERT_ODS"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"INSERT_ODS"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "bwdev"
Network address.......... "10.10.100.36"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x AMD64 Level"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "BWDEV"
Database type............ "ORACLE"
Database name............ "BWD"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Aug 17 2008 20:56:58"
Created in............... "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version......... "OCI_10201_SHARE "
Patch level.............. "247"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
Memory usage.............
Roll..................... 16128
EM....................... 6265200
Heap..................... 0
Page..................... 0
MM Used.................. 5972296
MM Free.................. 289384
SAP Release.............. "640"
User and Transaction
Information on where terminated
The termination occurred in the ABAP program "GPCX2UNC5JG556R7DPSFJUGJS1Z" in
"INSERT_ODS".
The main program was "SAPMSSY1 ".
The termination occurred in line 41 of the source code of the (Include)
program "GPCX2UNC5JG556R7DPSFJUGJS1Z"
of the source code of program "GPCX2UNC5JG556R7DPSFJUGJS1Z" (when calling the
editor 410).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "INSERT_ODS" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "GPCX2UNC5JG556R7DPSFJUGJS1Z ". Its source code
starts in line 21
| of the (Include) program "GPCX2UNC5JG556R7DPSFJUGJS1Z ".Hi,
This error occurs if you want to insert an entry in the table that does not match the value range of any partition. In such a case, you must compare the value of the entry with the definitions of the partitions to determine the cause of the error.
please run the following test/repair in transaction RSRV ,
RSRV -> All Elementary Test -> PSA Tables -> Consistency Between PSA Partitions and SAP Administration Information
-> include the PSA table
/BIC/B0000115000
Check OSS note 339896 which explains the repair procedure.
Regards,
Lokesh -
Short dump error in program SAPMV50A after modification
Dear gurus
i have done some modification in vl02n through Badi and it is working fine in Development server.
when i transport it to quality server and test it
it giving a short dump in vl02n while vl01n is working perfectly fine and showing my modification too..
below is the error mentioned
Database error text........: "Unsupported database type in parameter/column
(168)."
Internal call code.........: "[RSQL/READ/LIKP ]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able t
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the followin
keywords:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"SAPMV50A" or "MV50AFDB"
"LIKP_SELECT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
Please help
Regards
Saad Nisari have created two append structure in standard tables of LIKP & LIPS which are activated and so as LIKP and LIPS
my Badi is also activated and my customized program is also activated.
While making outbound delivery in Quality server it works fine but when i want to make changes in that created delivery it throws dump error
short text
SQL error in the database when accessing a table.
issing RAISING Clause in Interface
Program SAPMV50A
Include MV50AFDB
Row 14
Module type (FORM)
Module Name LIKP_SELECT
rigger Location of Exception
Program SAPMV50A
Include MV50AFDB
Row 20
Module type (FORM)
Module Name LIKP_SELECT -
Short Dumps in BW Production System
Hi BW Experts,
When iam loading the PCA data (0PCA_C01), i am getting the following Short Dumps in my Systems.
DBIF_RSQL_SQL_ERROR
RAISE_EXCEPTION
TSV_TNEW_PAGE_ALLOC_FAILED
TSV_TABH_POOL_NO_ROLL_MEMORY
TSV_TNEW_OCCURS_NO_ROLL_MEMORY
SYSTEM_NO_ROLL
Today i got 131 Short Dumps in my System.
Please can anyone tell me the solution for this Short Dumps.
Thanks in advance
Regards,
AnjaliI am receiving the following Run time error in a Process Chain
Name of the runtime: System_NO_ROLL
*Information on where terminated*
The termination occurred in the ABAP program "GP45O123XOQKIU82AMIR5C27RCN" in
"ROUTINE_9998".
The main program was "SAPMSSY1 ".
The termination occurred in line 3255 of the source code of the (Include)
program "GP45O123XOQKIU82AMIR5C27RCN"
of the source code of program "GP45O123XOQKIU82AMIR5C27RCN" (when calling the
editor 32550).
Source Code Extract
Line SourceCde
3225 *delete DATA_PACKAGE where CRM_SRVORG <> '50000053'.
3226 *** Move data package to internal table******************************
3227 *it_package[] = DATA_PACKAGE[].
3228 *SORT it_package ASCENDING BY CRM_ACGUID.
3229 *DELETE ADJACENT DUPLICATES FROM it_package
3230 * COMPARING CRM_ACGUID.
3231 *ilookup[] = it_package[].
3232 *SORT ilookup ASCENDING BY CRM_ACGUID.
3233 ** if abort is not equal zero, the update process will be canceled
3234 * ABORT = 0.
3235
3236 * New code to get the Interaction id for Quick Close
3237 DATA : it_package like STANDARD TABLE OF DATA_PACKAGE.
3238
3239 delete DATA_PACKAGE where CRM_SRVORG <> '50000053'.
3240
3241 it_package[] = DATA_PACKAGE[].
3242
3243 DELETE it_package where crm_prctyp <> 'Z260'
3244 AND crm_preotp <> 'BUS2000126'
3245 AND crm_predoc is INITIAL.
3246 SORT it_package ASCENDING BY crm_predoc.
3247
3248 DELETE ADJACENT DUPLICATES FROM it_package
3249 COMPARING crm_predoc.
3250
3251 SELECT CRM_ACGUID CRM_OBJ_ID FROM /BIC/AZ0SAL_D100 INTO TABLE ilookup
3252 FOR ALL ENTRIES IN it_package
3253 WHERE CRM_ACGUID = it_package-crm_predoc.
3254
>>>>> SORT ilookup ASCENDING BY CRM_ACGUID.
3256
3257
3258 -
Infopackage in process chain failing due to short dump on regular basis.
HI Experts,
There is a daily process chain in which one of the element (infopackage) fails due to short dump on regular basis (At least twice in a week) please find the message below
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Short text
SQL error in the database when accessing a table.
And in job log it is showing ARFCSTATE = SYSFAIL
We are able to resolve it just manual update and the process goes fine no issues but my question here is what is the exact reason for this and how to resolve it permanently or decrease the frequency of the error.
Please if any one can tell the root cause and the solution to avoid the issue in future on regular basis.
and also can any one elaborate what is ARFCSTATE = SYSFAIL,for trfc check we don't have access to SM58 in ECC side
and trfc is fine in bw side
Appreciate for not giving the general solutions like repeated solutions already posted in SDN
with regards,
musaiYou can contact your BASIS person he can help you reg table space issue. it says used space is 98% and free space is 1.03%.
ask your basis to set a threshold to check the space and send a mail notification to all daily regarding the space allocation and utilization.
ARFCSTATE = SYSFAIL means the TRFC did not processed properly to the BW system from source.
Monitoring object with information about tRFC and qRFC calls that are waiting to be executed in this system; after they have been executed, they are deleted from table ARFCRSTATE.
Are there any hung TRFCs which are not processed to BW side. have you checked it
first check
load monitor -- menu -- environment -- job overview -- status of job(is it finsihed or not?) - check the job log -- ther try to find out the hung TRFc
press find --tyep "sysfail" ok -- it will display all the hung or fialed TRFCs which are not processed to BW system.
if you find the hung TID with respect to your load.. next goto SM58 trasaction to process the trfcs manually or use the load monitor menu -- environment -- transaction RFC -- source sys -- it will take you to same SM58 screen -- click F8 it will display the hung TRFc in that duration.
select the TRFc and click on F6 to process them manually.
also check the loackwaits anddead locks in ST04/DB6COCKPIT.( ask basis to check) if any dead locks are there they will take care of it.
check for short dumps in st22 if any and try to analyse.
Check the SM21 system logs.
Maybe you are looking for
-
Aero Snap equivalent on the Mac?
Hi I find the Aero Snap feature to be very useful on Windows 7. I've searched and haven't found much info regarding this. is there an Aero Snap equivalent for the Mac? I find myself alot of times needing 2 windows side by side when I'm on my Mac. Any
-
How to animate images coming from web service in iphone sdk.
this is my code check once and give me reply. - (void)parserDidEndDocument:(NSXMLParser *)parser{ moreListTableView = [[UITableView alloc] initWithFrame:CGRectMake(0, 10, 320, 350) style:UITableViewStylePlain]; moreListTableView.delegate = se
-
How do get rid of "imported photos" on iphoto
When I open iphoto, I keep getting anerror message that I have a photo that has not been imported. But nothing really downloads. The "recovered photos folder is always empty. How do I get rid of the error message. On another computer, I was helped wi
-
Unable to Find Purge option in BPELConsole of Soa-Suite Version 10.1.3.4
We were unable to find the purge option button to delete the instances in BPELConsole page of Soa-Suite Version 10.1.3.4. In 10.1.3.3 and earlier versions, to the Leftside of the Instance tab in BPELConsole page, there is Button "Purge All Instances"
-
Fetch part of the data in an announcement posting for summary display
I have a request from user to extract a paragraph of content from announcement web part and to display the content to another page. The query of the extraction is to extract the annoucement that is posted for day. Once the summary is generated, an em