on 12-14-2011 10:53 PM
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 Venky,
I am sorry to say but this entire thread has went in the wrong direction of answers.
I infact come across this problem many times as I work in Support project and this error you are getting is due to lock set on the same infoprovider table.
Jobs accessing the same infoprovider table fail due to this error as a deadlock is set.
Kindly repeat the step in any one of the process chains which accesses the infoprovider after deleting the previous failed request and also after completion of this dtp loading step completes and the infoprovider becomes free, repeat the other dtp in the other process chain.
Please revert for any clarifications.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Venky,
You need not create any process chains for this.
I thought you were getting this error while loading data using process chain.
This is all due to database issue.
The solution for your problem is that you make sure that
1) The taget table to which you are trying to load data is not being locked (Locking happens when another dtp or infopackage tries to load data to the same table) by any other processes.
2) The target table to which you are loading data is not in activation step.
Please revert back for further clarifications.
Sorry guys,
but there isn't even the DB-error code in this thread... no idea how you can come up with all those "hints"...
To move on here, please check what DB error you get (see the workprocess developer trace, -> ST11) and post it here.
regards,
Lars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
Thanks and regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Venky,
This seems to be a Memory/Space issue.Check the Table Space in Database in DB02.
If you are loading data to a Infocube,try dropping the indexes and load again.
Check SAP note 17321 if it is relevant.
Regards,
Bhagyarekha.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Venkat,
Please check with basis team, need to increase memory size of BW system
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.