Inbound-Queue SYSFAIL: SQL error in the database when accessing a table

Hi,
we send around 80 IDoc simultaneously, there 15 are stuck.
They all have SYSFAIL in SMQ2 with message: SQL error in the database when accessing a table
I already unlocked the queues and try to resend. Nothing happend!
I ran RSQIWKEX for the single queus but now there are new queues in Status SYSFAIL.
I already checked some entries in forum and blogs, but nothing worked out yet!
Can someone help?! it's urgent!!
br

Hi, well as mentioned i searched and found this already.
But in ST22 i got error concerning
Laufzeitfehler DBIF_RSQL_SQL_ERROR
Ausnahme CX_SY_OPEN_SQL_DB
So i guess it's something more serious.
Any more ideas?!
Can i simply delete the stucked queues and reporcess them?!
br

Similar Messages

SQL error in the database when accessing a table.

Hi,
I got below error at production server. Please suggest how to reslove this error.
 
 
 
Runtime Errors DBIF_RSQL_SQL_ERROR
 
Exception CX_SY_OPEN_SQL_DB
 
Date and Time 02.01.2011 15:55:06
 
 
 
 
 
Short text
 
SQL error in the database when accessing a table.
 
 
 
How to correct the error
 
Database error text........: "[10054] TCP Provider: An existing connection was
 
forcibly closed by the remote host.
 
[10054] Communication link failure"
 
Internal call code.........: "[RSQL/INSR/SWFCNTBUF ]"
 
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"
 
"CL_SWF_CNT_FACTORY_SHMEM======CP" or "CL_SWF_CNT_FACTORY_SHMEM======CM001"
 
| "ADD_INSTANCE"
 
 
 
Information on where terminated
 
Termination occurred in the ABAP program "CL_SWF_CNT_FACTORY_SHMEM======CP" -
 
in "ADD_INSTANCE".
 
The main program was "SAPMSSY1 ".
 
 
In the source code you have the termination point in line 16
 
of the (Include) program "CL_SWF_CNT_FACTORY_SHMEM======CM001".
 
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
 
procedure "ADD_INSTANCE" "(METHOD)", but it was neither handled locally nor
 
declared
 
in the RAISING clause of its signature.
 
 
The procedure is in program "CL_SWF_CNT_FACTORY_SHMEM======CP "; its source
 
code begins in line
 
1 of the (Include program "CL_SWF_CNT_FACTORY_SHMEM======CM001 ".
 
 
 
 
Source Code Extract
 
 
Line
SourceCde
 
 
1
METHOD add_instance .
 
2
 
3
data: ls_id type swfcntbuf.
 
4
 
5
check buffer method - store in local buffer if necessary
 
6
retcode = cl_swf_cnt_factory=>add_instance( ibf_por = ibf_por instance = instance ).
 
7
 
8
CHECK m_buffer_method EQ mc_buffer_shared.
 
9
 
10
append key to list of tasks to add stored in database table SWFCNTBUF
 
11
will be evaluated by build process for shared memory area (UPDATE_BUFFER method)
 
12
 
13
ls_id-mandt = sy-mandt.
 
14
ls_id-id = ibf_por.
 
15
 
>>>>>
INSERT swfcntbuf CONNECTION r/3*wfcontainer
 
17
FROM ls_id.
 
18
 
19
IF sy-subrc EQ 0.
 
20
Commit seems to be necessary always, even if INSERT has failed, to get rid of
 
21
database locks
 
22
COMMIT CONNECTION r/3*wfcontainer.
 
23
ENDIF.
 
24
 
25
ENDMETHOD.
 

duplicate here SQL error in the database when accessing a table.
Do not post the same question in more than on forum.

DBIF_RSQL_SQL_ERROR with SQL error in the database when accessing a table.

dear all,
i have done a system copy from production server into quality server. quality was scrapped and freshly installed with SAP then used the DB flush method to carry out the system copy. i had to change the DBS_ORA_SCHEMA in environment variables to SAP<SOURCE SID> from SAPSR3. the sap version is ECC6.0,DB is ORACLE10.2 on WIN NT.
after MMC opened, i get "SQL error in the database when accessing a table" error is coming. in SM21, I am getting "Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000 )
Database error 8103 at SEL access to table TBTCO
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
Database error 8103 at FET access to table TBTCP
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130339 sibqty_Q TY_00 " generated
Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000
> Short dump "081018 130339 sibqty_Q TY_00 " generated
Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000
Delete session 001 after error 023
Database error 8103 at DEL access to table TMSALOGAR
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130432 sibqty_Q TY_00 " generated
Database error 8103 at FET access to table SNAP
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130432 sibqty_Q TY_00 " generated
Transaction Canceled SY 002 ( SQL error in the database when accessing a table. )
Database error 8103 at FET access to table TSP02"
please find the st22 DUMP:
ow to correct the error |
Database error text........: "ORA-08103: object no longer exists"
Internal call code.........: "[RSQL/READ/TBTCO ]"
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"
"SAPMSSY2" or "SAPMSSY2"
"INITIATE_JOB_START"
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
"INITIATE_JOB_START" "(FORM)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
|
please do me this favor if you know to avoid this problem..
thanks a lot..

Hello Anuj,
This is because the COUNT(*) is returning a value which is longer than the INT4 data type it is expecting. If you restrict the selection by introducing a WHERE clause, then you won't get the dump:
DATA: dyn_from TYPE string,
 dyn_where TYPE string,
 gx_sql_err TYPE REF TO cx_sy_open_sql_error,
 gv_text TYPE string.
dyn_from = `DD01L INNER JOIN DD02L ON DD02L~AS4LOCAL = DD01L~AS4LOCAL AND DD02L~AS4VERS = DD01L~AS4VERS`.
dyn_where = `DOMNAME LIKE 'Z%'`.
TRY .
 SELECT COUNT(*) FROM (dyn_from) WHERE (dyn_where).
 WRITE: / sy-dbcnt NO-GROUPING.
CATCH: cx_sy_open_sql_db INTO gx_sql_err,
 cx_sy_dynamic_osql_semantics INTO gx_sql_err,
 cx_sy_dynamic_osql_syntax INTO gx_sql_err.
ENDTRY.
IF gx_sql_err IS BOUND.
gv_text = gx_sql_err->get_text( ).
WRITE: / gv_text.
ENDIF.
BR,
Suhas

DBIF_RSQL_SQL_ERROR: SQL error in the database when accessing a table

Hi Gurus,
Im getting DBIF_RSQL_SQL_ERROR: SQL error in the database when accessing a table error while I was importing support pack in the system. This is ERP 6.0 with EHP4 with MS SQL in back ground and I was applying the BASIS SP 04. It was in the TEST scenario and in the SPDD_SPAU_CHECK phase it threw the error.
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........: "[601] Could not continue scan with NOLOCK due to
     data movement."
    Internal call code.........: "[RSQL/FTCH/E071 ]"
    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"
    "SAPLSVRT" or "LSVRTU01"
    "TR_LAST_IMPORT_OF_OBJECT"
SPAM is ending with the above short dump. I have checked the space availability and it is OK.
Kindly help.
Renju Aravind.

Hi,
this error is very often seen in case of a database corruptions. Please follow note 142731 and perform a complete database check. Send the results when they show errors.
Best regards
Clas

Getting error "SQL error in the database when accessing a table."

Hi All,
We are getting Dump Error SQL error in the database when accessing a table for the batch job EISSD/REQUISITION 14 / which includes program AQ20FD==========A2============. Please reply. The Dump error details are as follows
Short text
    SQL error in the database when accessing a table.
How to correct the error
    Database error text........: "ORA-01555: snapshot too old: rollback segment
     number 21 with name "_SYSSMU21$" too small"
    Internal call code.........: "[RSQL/FTCH/VBRK ]"
    Please check the entries in the system log (Transaction SM21).
Thanks
Padmakar Kudtarkar
Edited by: Rob Burbank on May 19, 2011 9:38 AM

The query where we are getting error in Standard program AQ20FD==========A2============ for Job
EISSD/REQUISITION 14 / is as follows:
select VBRKBUKRS VBRKFKART VBRKFKDAT VBRKFKTYP VBRKGJAHR VBRKKUNAG VBRKKUNRG VBRKKURRF VBRKVBELN VBRKWAERK VBRP~AUBEL
       VBRPAUPOS VBRPFKIMG VBRPKVGR2 VBRPKZWI1 VBRPMATNR VBRPMWSBP VBRPNETWR VBRPPSTYV VBRPVBELN VBRPVGBEL VBRP~VGPOS
       VBRPVKBUR VBRPVKGRP VBRPVRKME VBRPWAVWR
into (VBRK-BUKRS , VBRK-FKART , VBRK-FKDAT , VBRK-FKTYP , VBRK-GJAHR , VBRK-KUNAG , VBRK-KUNRG , VBRK-KURRF , VBRK-VBELN
     , VBRK-WAERK , VBRP-AUBEL , VBRP-AUPOS , VBRP-FKIMG , VBRP-KVGR2 , VBRP-KZWI1 , VBRP-MATNR , VBRP-MWSBP , VBRP-NETWR
     , VBRP-PSTYV , VBRP-VBELN , VBRP-VGBEL , VBRP-VGPOS , VBRP-VKBUR , VBRP-VKGRP , VBRP-VRKME , VBRP-WAVWR )
from ( VBRK
       inner join VBRP
       on VBRPVBELN = VBRKVBELN )
       where VBRK~BUKRS in SP$00004
         and VBRK~FKDAT in SP$00001
         and VBRK~KUNAG in SP$00002
         and VBRK~VBELN in SP$00006
         and VBRP~MATNR in SP$00003.
%dbacc = %dbacc - 1.
if %dbacc = 0.
    stop.
endif.
check SP$00004.
check SP$00001.
check SP$00002.
check SP$00006.
check SP$00003.
add 1 to %count-VBRK.
%linr-VBRK = '01'.
extract %fg01.
%ext-VBRP01 = 'X'.
    extract %fgwrVBRP01.
endselect.

Root cause of "SQL error in the database when accessing a table. "

Dear experts,
I meet this dump "SQL error in the database when accessing a table" when executing a sql.
Sql:
    SELECT sesssessno poscrm_serplan_id poscrm_ser_h_id poscrm_ser_i_id
           possolution_id sessbundle_id sessdbid sessinstno pos~crm_ordered_prod
           sessdbid sessinstno
      INTO CORRESPONDING FIELDS OF TABLE et_sess_list
      FROM dsvassessadmin AS sess JOIN service_posn_sm AS pos
        ON possession_id     = sesssessno
      FOR ALL ENTRIES IN lt_contractno
      WHERE sess~contractno = lt_contractno-contract_no
       AND sess~status IN lt_status_range
       AND bundle_id IN lt_bundle_id
       AND pos~solution_id GT 0
This sql works well in dev system SD7, however, it causes dump in another dev system "SMV".
Can anyone give me any ideas?
Thanks

Hi Jovito,
This is info from ST22
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........: "SQL0101N The statement is too long or too
     complex. SQLSTATE=54001"    Internal call code.........: "[RSQL/OPEN/DSVASSESSADMIN ]"
    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"
    "CL_AGS_SERVICE_SERV===========CP" or "CL_AGS_SERVICE_SERV===========CM018"
    "GET_OVS_SESSION_LIST"
    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
    "GET_OVS_SESSION_LIST" "(METHOD)", or its possible occurrence must be declared
     in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
It seems that after translation the native sql is too long. But I think this can be solved.

Loading issue : Error: sql error in the database while accessing a table

Hello,
where as one of the DTP in the process chain failed due to *Error: sql error in the database while accessing a table*, where as in the short dump it showing as Transaction log of data base is full., but i checked the data base space in DB02, more space is available . once we run the same DTP by manually its successful. its not through any errors.
could u please help me out solve the problem.
Thanks
siva kumar.

it might be a lock. do you drop index before loading?
the database might be full at the moment of loading and not later if many loadings happen at the same time on the same system...
when you then rerun your dtp manually, it can go through as it's perhaps the only one running at that moment...
you can try to set the btch parameter to 1...this will help in some cases.
M.

SQL error occurred in the database when acces

Dear All,
I am getting following error message while doing file to file scenario.
source side messages are pickedup and entering into the Queues .receiver side i cant able to see any souce messages.
SYSFAIL Message is showing in the Queues when i was double click that message its giving following message.
SQL error occurred in the database when acces
a table.
Plz, help me in this regard.
Thanks,
Mahesh

Hi Mahesh,
Did you get a chance to check the IPC log directories
Also usually for a sysfail message you can check the smw01
You will see a bdoc with status F05. What does it say there?
or
Is it "Scheduled for outbound processing" or "recorded for outbound processing".
I guess the message has not been processed, so the next step is to go to transaction SMQ2, and check for info as to why it is not processed.
If you see a queue status of SYSFAIL, first try resetting it to "Ready" again. If it still fails then, delete that particular LUW. And if you still have some more messages in the queue just click the unlock queue button.
Reward points if this helps
Regards
Pragathi.

XI 2.0 Inbound Queue Sysfail problem

I am having a problem where my xml message is causing the 'xbtoljul' inbound queue to stop. Within the queue I can see a message with the StatusText of "XI message queue stopped due to internal error". Does anyone have a good suggestion for understanding how or why this message is in this state? Looking at the message using 'sxi_monitor' it looks ok, no errors or exceptions.

I'm having the issue. Did you ever get this resolved

Database error. The database error is: (CS) WIS 10901

Hi guys
i am using SAP BusinessObjects Edge BI 3.1 and created one report using webi, saved and exported to CMS when i opened it in Infoview it works fine but when i refresh it then i am getting below mentioned error:-
Refreshing a document in Web Intelligence Rich Client generates the following error message:
the database error text is (CS) " unexpected behaviour". (WIS 10901)
i am able to see the sql which is getting generated....
another problem i am getting if i am creating report using new web intelligence document and using efashion universe then report is showing blank with different colours....
Please help me to solve this problem..
thanks & Regards
Edited by: sap_@2011 on Aug 26, 2010 5:34 PM

Hello,
Have you checked your Universe connection to the database?
Did you create the report in Rich client on your machine and then export it? ODBC connections may be different. They need to be the same.
I am not sure what you mean regarding blank with different colors. Can you explain this a little better?
Thanks

Error 1065 The database specified does not exist

Hi All,
When I am trying the start the Concurrent Manager [[From Services.msc]] I am getting this error.
Error 1065 The database specified does not exist
I am also not able to connect through SQL* Plus.
Thanks
--Anil

Hi,
Thanks to both of you. I don't have metalink access right now.
Hussein
It's my Desktop. For quite sometime I have not run it and Now when I am opening the Apps I am not able to login.
Also I don't have much idea where to check the CM log file????
Thanks
--Anil

TS2518 Help, I had aperture open and working on a image and did not have a battery in and bumped the power off. As a result it will not open my master, it is locked. when I try to open that Library it says There was an error opening the database for the

Help, I had aperture open and working on a image and did not have a battery in and bumped the power off. As a result it will not open my master, it is locked. when I try to open that Library it says There was an error opening the database for the library. I have tried every thing. I updated the other libr but now it will not open the main to update. What do I do?

Try starting Aperture with the command and option keys held down. You'll get 3 options.
Try each, starting at the top, in order, checking after each to see if it fixes the issue.

"There was an error opening the database for the library "~/Pictures/Apert"

Hey everyone,
There's already another discussion thread about this at the link below, but the problem was never actually resolved. http://discussions.apple.com/thread.jspa?threadID=2343014&tstart=0&messageID=116 67261#11667261
So I stumbled across this problem where Aperture 3 will display the following error when opening the image library.
There was an error opening the database for the library “~[path]/Aperture Library.aplibrary”.
One user suggested navigating to the actual library, and ⌘⌥-clicking the library to open it with the Aperture Library First Aid dialog. This however, did not work for me. I still received the error messages upon ⌘⌥-clicking the library.
Here's a little hack I discovered for those of you still struggling. It doesn't fix the problem (leaves quite a large dent remaining actually), but hopefully someone can cultivate what little I discovered.
⌥-click Aperture (not the library)
You should get to the library selection dialog box. Create a new library (bottom right corner) and remember the location of the new library. Put a few random pictures in the new one.
Close Aperture
⌃-click both the old and new libraries and "Show Package Contents."
Open the folder "Database" in both libraries.
Cross check the folders to see if the old library is missing files that are in the new library. If your old library is missing some files (mine was), drag the missing files from the new library to the old one.
Close both folders.
⌘⌥-click the old library.
NOW, I got the Aperture Library First Aid dialog.
Rebuild the library (3rd option)
Wait a while.
Aperture should open up with a folder named "Recovered Folder." Within this folder will be a SINGLE project named "Recovered Project" with ALL the images from your old library. There may be a few albums there too, but mine were all empty so it didn't matter in my case. To my knowledge, I lost all the adjustments I performed too.
This is as far as I got. I have much of my library backed up, so I only needed to copy the most recent photos into the backup. I am NOT reorganizing and re-editing pictures in this one!
As Aperture is a photo-organizing and photo-editing software, I understand that this by no means fixes the problem, since you lose all organization and editing. But it enables one to at least view the images lost. Hopefully a more knowledgable hacker else can figure out how to fix this completely. Unfortunately, I simply don't have the time to continue messing with this.
Good luck to anyone else having issues! I understand the frustration you must be facing, its freaky having years worth of images simply disappear! After this incident, I'm definitely going to configure Time Machine to perform more frequent backups, since my latest backup was already a couple weeks old.

Hey All,
To my horror I have a similar problem and your solution didn't seem to help. To be specific, I get the error:
"There was an error opening the database for the library “~/Pictures/Aperture Library_2.aplibrary" Everytime I try to run Aperture. This happened because my Apple computer shut off completely (due to bad battery) while importing photos from a memory card.
I've tried "option + command" while clicking the aperture application and that gave me the same error message without any other option except to quit the program. I tried "option + command" and clicked the library package but that didn't work either. I tried creating a new aperture library, opening it which I did successfully, and then switching to my main one but that didn't work.
Does anyone know away to get it to work again and have the edits still there?
I'm a professional photographer and have thousands of photos or so in the library so this is distressing. The master files for the photos are located on an external hard drive, but I'm not sure how to access them in aperture. Are all the edits on the photographs are in the external hard drive or the aperture library. Is there any other way to resolve this issue without losing the edits?
Does apple have a support number I can call? Any help would be greatly appreciated!!

I have three aperture libraries. But just recently two of them (old from 2011) will not open. I get the following error: There was an error opening the database for the library "~/Pictures/Family IIi.aplibrary". Please help, thanks

I have three aperture libraries. But just recently two of them (old from 2011) will not open. I get the following error: There was an error opening the database for the library “~/Pictures/Family IIi.aplibrary”. Please help, thanks

Are all three libraries under your account or are they in different accounts? Any other errros on the system?
Start by doing the permission repair and library repair steps in Aperture 3: Troubleshooting Basics

What is the best way to copy aperture library on to external hard drive? I am getting a message that say's "There was an error opening the database. The library could not be opened because the file system of the library's volume is unsupported".

What is the best way to copy aperture library on to external hard drive? I am getting a message that say's "There was an error opening the database. The library could not be opened because the file system of the library's volume is unsupported". What does that mean? I am trying to drag libraries (with metadata) to external HD...wondering what the best way to do that is?

Kirby Krieger wrote:
Hi Shane. Not much in the way of thoughts - - but fwiw:
How is the drive attached?
Can you open large files on the drive with other programs?
Are you running any drive compression or acceleration programs (some drives arrive with these installed)?
Can you reformat the drive and try again?
Hi Kirby,
I attached the UltraMax Plus with a USB cable. The UltraMax powers the cable so power is not an issue. I can open other files. Also, there is 500GB of files on the drive so I cannot re-format it. Although, I noted I could import the entire Aperture Library. However, I do not want to create a duplicate on my machine because that would be defeating the purpose of the external drive.
Thanks,
Shane

Inbound-Queue SYSFAIL: SQL error in the database when accessing a table

Similar Messages

Maybe you are looking for