Internal error in the database interface (Oracle)

I have recently an Oracle runtime error just by entering the SAP system (SAP ECC 6.0).
DBIF_RSQL_INVALID_REQUEST
The current ABAP/4 program terminated due to
an internal error in the database interface.
Error analysis
An invalid request was made to the SAP database interface in a statement
in which the table "DOKTL " was accessed.
Trigger Location of Runtime Error
Program                                 SAPLSDOC
Include                                 LSDOCU09
Row                                     249
Module type                             (FUNCTION)
Module Name                             DOCU_GET
I appreciate any helpful information.
Thank you very much indeed
Thom

hi Thom,
most error relating to table DOKTL are caused by misconfigured network card.
if this is a "home" system, install a loopback adapter from Microsoft and use IP address 127.0.0.1 and also check "hosts" file for inconsistency. do not use the IP adddress provided by your ISP as it may change.

Similar Messages

Error in the module RSQL accessing the database interface

I have written the following query.
SELECT a~no
         a~hist_no
         a~chk_stat
         a~chk_date
         a~user as chk_user
         b~name as chk_by
         into corresponding fields of table hist
         from zhist as a INNER JOIN zuser as b on
         auser = bbname
         where pspnr = v_pspnr
         and   chk_no = v_chk_no.
I am getting the dump "Error in the module RSQL accessing the database interface".
Please provide me the solution.
Thanx,
Selva.

Hi,
As i have analysed your query in that you are putting the data in the internal table 'hist' which is also a standard structure and if you check in SE11 'hist' is the standard structure for 'Tablespace History' and might be because of that it is causing the problem.
Kindly check by changing the name of the internal table to tt_hist and then try.
I think that will solve the problem.
Regards,
Harsh Goel

Error saying "Error in the module RSQL accessing the database interface"

Hi,
there is a standard program available for retrieving the assets for the given cost centres on the selection screen.
Our requirement is instead of cost centre we have to retrieve the assets for the given cost centre group.
We have to find all the cost centres available on the given cost centre group and its child nodes.
For all these cost centres we will be retriving the asset history data.
So we copied the standard program into another Y program and made the changes to it.
What's happening is if we give the top most Cose centre group node there are 16000 cost centres available . while retriving the asset history data for all these cost centres an runtime error occurs in a standard program saying
"Error in the module RSQL accessing the database interface, " DBIF_RSQL_INVALID_RSQL ".
The error occurs while executing the statement Fetch Next cursor in a standard Include program.
This happens only if we give huge range of data. If we give small range of data it
works fine.
Can anyone help me in this by saying why it occurs and what will be the solution for this.
Thanks.

Hi camila,
The huge range is part of the query string passed to the database.
While an MP3 music gadget easily stores a gigabyte of data, ORACLE was able to increase the maxium size of a query string from 16 k to 32 k bytes in the last 5 years.
Unbelievable but true!
Just multiply the number of entries in the range with the field length and see where go go...
Regards,
Clemens

Error in module RSQL of the database interface.

Hi Expert,
I get this error "Error in module RSQL of the database interface." when the below ABAP statement executed, do you know the root cuase? Thanks.
ABAP Code:
data lt_fact type TABLE OF /BIC/FZRT_C002.
data ls_Fact type /BIC/FZRT_C002.
*SELECT * INTO table lt_fact FROM /BIC/FZRT_C002 WHERE KEY_ZRT_C0021 in lt_RSDIMID and KEY_ZRT_C0022 in lt_caRSDIMID*.
Information in ST22.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLZZ_FG" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
     in
    procedure "ZCA_GET_CUBE_STOCK" "(FUNCTION)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    The SQL statement generated from the SAP Open SQL statement violates a
    restriction imposed by the underlying database system of the ABAP
    system.
    Possible error causes:
     o The maximum size of an SQL statement was exceeded.
     o The statement contains too many input variables.
     o The input data requires more space than is available.
     o ...
    You can generally find details in the system log (SM21) and in the
    developer trace of the relevant work process (ST11).
    In the case of an error, current restrictions are frequently displayed
    in the developer trace.
Best Regards,
Andrew

i have the same error but my first select is
SELECT QMNUM QMTXT QMDAT AUFNR OBJNR QMNAM QMART BTPLN IWERK BEBER INGRP EQUNR SERIALNR MATNR
        INTO TABLE GT_VIQMEL
        FROM VIQMEL
        WHERE QMNUM IN S_QMNUM .
please tell me how to solve this error when i run 24000 raw this select dump.
ASAP
thanks
Eman elgammal.

RFC_ERROR_SYSTEM_FAILURE: Error in module RSQL of the database interface

HI All,
I am trying to execute an RFC through JCO connection and getting the error "RFC_ERROR_SYSTEM_FAILURE: Error in module RSQL of the database interface".
While debugging I have found that the actual cause of dump is a SQL command written in this RFC. The SQL command is
SELECT DISTINCT *
 INTO CORRESPONDING FIELDS OF TABLE lt_calcrule_hol
 FROM itc_calcrule_hol
 FOR ALL ENTRIES IN calc_rule
 WHERE rule_id = calc_rule-rule_id
 AND start_date <= sy-datum
 AND end_date >= sy-datum
 AND (lv_ident)
 AND ( (lv_orgs)
 OR location_type = '' ).
Here the value of lv_ident is ======>> ident IN ('US','B2'.........................)
and value of lv_orgs is =========>> location_type IN ('S1','S2',..............................)
location_type and ident are columns in table itc_calcrule_hol .
I have analysed that if I pass around 700 enteries in the lv_ident and lv_ogs then it is working fine.
But if I have more than 900 enteries in these variables then it dumps.
Can anybody let me know what is the issue with the query here.And what could be the solution.
Thanks and Regards,
Reena

I'd recommend talking to an experienced basis admin or ABAP developer. First of all it would help to look at the short dump in SAP, to see if that gives any useful information. In case of a generic error like DBIF_RSQL_INVALID_RSQL, the developer trace of the work process (dev_w<n>) should contain further information (to get the number of the work process that handled your RFC call check the system log, which contains the reference along with a comment about the dump). So I'd check those first to see what actually caused the problem.
Information on maximum SQL statement length can either be retrieved from the database vendor's documentation or alternatively by searching SAP [OSS notes|https://service.sap.com/notes]. For the latter you need a valid user ID for the SAP service market place.

Error in module RSQL of the database interface! Please Help.

I am getting the error "Error in module RSQL of the database interface" in my program. Below is the code snippet in which the above error is:
=================================
FORM UPLOAD_PA_PB USING NB_LINE ID.
DATA: TOT_LINES TYPE I.
IF ID <> 'PA' and ID <> 'PB'. "UPG060507 - RY
only PA and PB tables
 CHECK ID CP 'PA*'
 OR ID CP 'PB*'.
 DO NB_LINE TIMES.
 READ DATASET DSN INTO IPREL_DB.
 IF IPREL_DB+0(3) = P_FROM.
 IPREL_DB+0(3) = P_TO.
 ENDIF.
 RP-CHECK-VALID-PAPB IPREL_DB S_BEGDA-LOW S_BEGDA-HIGH.
 IF FLAG = 0. CONTINUE. ENDIF.
 APPEND IPREL_DB.
 ENDDO.
Begin of change - UPG060507 - RY
 DELETE ADJACENT DUPLICATES FROM IPREL_DB.
End of change - UPG060507 - RY
 IF TEST = SPACE.
 IF ID = 'PA2010' or ID = 'PA0014' or ID = 'PA0015'.
 PERFORM CLEAR_COST_ASSIGNMENT. "PUNM0002
 ENDIF.
 delete previous values
 DELETE FROM (ID) WHERE PERNR IN PERS
 AND BEGDA <= S_BEGDA-HIGH
 AND ENDDA => S_BEGDA-LOW.
 WRITE: / SY-DBCNT LEFT-JUSTIFIED, 'entrie(s) deleted from', ID.
 insert the new ones
 INSERT (ID) FROM TABLE IPREL_DB.
 WRITE: / SY-DBCNT LEFT-JUSTIFIED, 'entrie(s) imported in', ID.
 CALL FUNCTION 'DB_COMMIT'.
 SKIP.
 ELSE.
 DESCRIBE TABLE IPREL_DB LINES TOT_LINES.
 WRITE:/ TOT_LINES LEFT-JUSTIFIED, 'Entries Will Be Imported in',ID.
 ENDIF.
 REFRESH IPREL_DB.
ENDIF. "UPG060507 - RY
ENDFORM.
===============
Your help will be greatly appreciated and all the answers will be rewarded.
Thanks.
Mithun

Hi Mithun,
Can you please tell at which line the error is shown.
Regards,
Atish

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

Error in external database interface QXDA

Dear All,
While executing tcode DB02 or ST04 im getting error as "Error in external database interface QXDA". As per sap note 863623 we have changed the password for SIDnn and restarted system also executing command STARTSAP *DB successfully.
But the error still shown. Any advice
Best Regards,

Dear Christian,
Thanks for your reply, while checking with command wrkactjob couldnt find job QXDAEDRSQL. when i start job with STARTSAP DB* command is executed without any error.
But still we couldnt find anyjob QXDAEDRSQL active.
as per your initial recommendation here are the logs from st11
M *** ERROR => AS400_API (APICODE 25) failed with SY-SUBRC = 3 [abas4api.c   1548]
M *** ERROR => AS400_API unable to connect to 'IDES' [dbsldb4ccm.c 593]
B
B Tue Jul 20 12:51:54 2010
B create_con (con_name=R/3*INACT_PACK)
B New connection 1 created
C Secondary DB connect, Service connection
C *** ERROR => CPE3025 occured. Refer to job log.
[dbsldb4dbi.c 474]
C *** ERROR => === Secondary DB connect FAILED! ===
[dbsldb4.cpp 15642]
C *** ERROR => === Connection settings ===
[dbsldb4.cpp 17698]
C *** ERROR => connected               = FALSE
[dbsldb4.cpp 17699]
C *** ERROR => con_hdl                 = 1
[dbsldb4.cpp 17700]
C *** ERROR => db_handle               = 0
[dbsldb4.cpp 17701]
C *** ERROR => dbhost                  = IDES
[dbsldb4.cpp 17702]
C *** ERROR => dbhostport              =
[dbsldb4.cpp 17703]
C *** ERROR => rdbname                 =
[dbsldb4.cpp 17704]
C *** ERROR => dblib                   = R3IDODATA
[dbsldb4.cpp 17705]
C *** ERROR => r3sysle_changed         = FALSE
[dbsldb4.cpp 17708]
C *** ERROR => query_compl_reval       = O
[dbsldb4.cpp 17709]
C *** ERROR => dbconnecttype           = U
[dbsldb4.cpp 17710]
C *** ERROR => user                    = IDO00
[dbsldb4.cpp 17711]
C *** ERROR => qaqqinilib              = Default (QUSRSYS)
[dbsldb4.cpp 17715]
C *** ERROR => dbjobname               =
C *** ERROR => rmtexelib               = SAPIDOUC
[dbsldb4.cpp 17719]
C *** ERROR => parallel_alter_tables   = *OFF
[dbsldb4.cpp 17722]
C *** ERROR => ===========================
[dbsldb4.cpp 17741]
B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'PRE'
B   RSLT: {dbsl=29, tran=16384}
B   FHDR: {tab='PAKDATBUF', fcode=194, mode=2, bpb=0, dbcnt=0, crsr=0,
B          hold=0, keep=1, xfer=0, pkg=0, upto=0, init:b=0,
B          init:p=(nil), init:#=0, wa:p=(nil), wa:#=0}
B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'PRE'
B   STMT:
B   CRSR: {tab='', id=0, hold=0, prop=0x1000, max.in@0=0, fae:blk=0,
B          con:id=3000001, con:vndr=2, val=2,
B          key:#=3, xfer=0, xin:#=19, row:#=0, upto=0, wa:p=0x7000000b8454240}
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A Error in module RSQL of the database interface..

I'm getting a similar message: There was an error opening the database..." and the only option I get is a "quit" button. Help!

I'm getting a similar message: First it offers me chance to repair - but if I it repair, it crashes. Then if I select do not repair I get the following warning: There was an error opening the database..." and the only option I get is a "quit" button. Help!

From the path in the error message you posted it appears that the library is not on your internal (root) drive.
What type of disk is the library on and how is it formatted?
The crash log Léonie is referring to is what is printed out when Aperture crashes. You wrote that Aperture crashes in your first post so if the app crashes you must have gotten a crash report.
Message was edited by: Frank Caggiano

Help me soon please: error:1065 the database specified does not exist.

hello every one,
when i start the computer the concurrent manager service not started , when i try to start it i have this problem:
"could not start the oracle concmgrvis_orabac service on local computer error:1065 the database specified does not exist."
i restarted computer and tried to stop and start all services more times but no change.
i hope if you can help meplease soon.

check note How to Recreate the Concurrent Manager Service for Oracle Applications 11i on Windows NT
Note:152887.1
maybe recreting the CM will solve your issue
Follow these steps to recreate the concurrent manager service on Windows NT:
1. cd $APPL_TOP
2. dos> envshell.cmd (this opens up a new DOS window. Go to that window and
do the following).
3. cd $COMMON_TOP/admin/install
4. dos> adsvcm.cmd -deinstall (deinstalls the ccm service)
should exit with status '0'
5. dos> adsvcm.cmd
should exit with status '0'
Should see "Successfully installed concurrent manager"
6. Reboot
fadi
.

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.

Internal error cant render database when working on lettering

hello; i just installed fireworks CS5 (CS5 Web Premium) i was working with a font, i wanted it to be outlined in yellow, so i cliked the color for the outline, and i get this error: internal error, cant render database, so i click ok, it comes right back, and will not quit, cant exit program, so did task mgr to end program, but it just keeps coming back if i try to built the words i want outlined, is there a fix for this? Can i uninstall just fireworks, and reinstall to fix it? i would rather not uninstall the suite, there must be a way to fix this. i seem to be able to do other stuff with jpg's with no problems, it is just with any lettering.
thank you for any help

check if the user has the rights to start or stop the database services in the new domain. it could be a privelege issue within NT.

Internal error in the database interface (Oracle)

Similar Messages

Maybe you are looking for