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..

Similar Messages

  • 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.

  • 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

  • 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.

  • Reg: Error in RSQL module of database interface

    Dear All,
    I am getting this error.
    Error in RSQL module of database interface. While i am giving the excise invoice date(j_1exchdr-exdat) more than 120 days i am getting this error.
    SELECT VBRK~VBELN VBRK~FKART VBRK~WAERK VBRK~KNUMV VBRK~FKDAT
           VBRK~KURRF VBRK~KUNAG VBRK~FKSTO
           VBRP~POSNR VBRP~FKIMG VBRP~NETWR VBRP~VGBEL VBRP~MATNR
            VBRP~ARKTX VBRP~MATKL VBRP~WERKS VBRP~LGORT
          INTO CORRESPONDING FIELDS OF TABLE ITAB
      FROM VBRK
       INNER JOIN VBRP
        ON VBRK~VBELN = VBRP~VBELN
        WHERE VBRK~VBELN IN VBELN
        AND VBRK~FKART IN FKART
        AND VBRK~FKDAT IN FKDAT
        AND VBRK~FKSTO NE 'X'
        AND VBRP~MATKL IN MATKL
        AND VBRP~WERKS IN WERKS
        AND VBRP~LGORT IN LGORT.
    what should i have to do? can i change this select query into selct for all entries what should i have to do?
    Thanks,
    Sankar M

    Runtime Errors         DBIF_RSQL_INVALID_RSQL                                                    
    Exceptn                CX_SY_OPEN_SQL_DB                                                         
    Date and Time          21.11.2008 15:24:50                                                                               
    ShrtText                                                                               
    Error in RSQL module of database interface.                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "Z_EXCISE_DET11H1" had to be terminated because one of             
          the                                                                               
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception will be dealt with in more detail                     
         below. The exception, assigned to the class 'CX_SY_OPEN_SQL_DB', was not                    
          caught, which                                                                               
    led to a runtime error. The reason for this exception is:                                  
         The SQL statement generated from the SAP Open SQL Statement violates a                      
         restriction imposed by the database system used in R/3.                                                                               
    Possible errors:                                                                               
    o The maximum size of an SQL statement has been exceeded.                                  
          o The statement contains too many input variables.                                         
          o The space needed for the input data exceeds the available memory.                        
          o ...                                                                               
    You can usually find details in the system log (SM21) and in the                             
        developer trace of the work process (ST11).                                                  
        If an error occurs the developer trace often informs you about the                           
        current restrictions.                                                                               
    Missing Handling of System Exception                                                             
        Program                                 Z_EXCISE_DET11H1                                                                               
    Trigger Location of Exception                                                                    
        Program                                 Z_EXCISE_DET11H1                                     
        Include                                 Z_EXCISE_DET11H1                                     
        Row                                     112                                                  
        Module Name                             START-OF-SELECTION                                                                               
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    82                 FKART FOR VBRK-FKART,                                                      
       83                 FKDAT FOR VBRK-FKDAT,                                                      
       84                 VBELN FOR VBRK-VBELN, " OBLIGATORY DEFAULT '90002130',                     
       85                 MATKL FOR VBRP-MATKL OBLIGATORY," OBLIGATORY DEFAULT '01' NO INTERVALS NO-EX
       86                 LGORT FOR VBRP-LGORT  NO INTERVALS NO-EXTENSION. "OBLIGATORY DEFAULT '1110'
       87                                                                               
    88 SELECT  J_1IEXCHDR~RDOC                                                                    
       89 FROM J_1IEXCHDR                                                                               
    90 INTO CORRESPONDING FIELDS OF TABLE EXCISEDOCNO                                                 
       91 WHERE                                                                               
    92   J_1IEXCHDR~TRNTYP = 'DLFC' AND                                                               
       93   J_1IEXCHDR~SRGRP IN SRGRP AND                                                                
       94   J_1IEXCHDR~EXDAT  IN EXDAT AND                                                               
       95   J_1IEXCHDR~EXNUM IN EXNUM.                                                                   
       96                                                                               
    97 LOOP AT EXCISEDOCNO.                                                                               
    98   VBELN-SIGN ='I'.                                                                               
    99   VBELN-OPTION = 'EQ'.                                                                         
      100   VBELN-LOW = EXCISEDOCNO-RDOC.                                                                
      101   APPEND VBELN.                                                                               
    102 ENDLOOP.                                                                               
    103                                                                               
    104 LOOP AT EXCISEDOCNO.                                                                           
      105   IF J_1IEXCHDR-TRNTYP = 'CEIV' .                                                              
      106     DELETE EXCISEDOCNO.                                                                        
      107     MODIFY EXCISEDOCNO.                                                                        
      108   ENDIF.                                                                               
    109 ENDLOOP.                                                                               
    110 *ENDLOOP.                                                                               
    111                                                                               
    >>>>> SELECT VBRKVBELN VBRKFKART VBRKWAERK VBRKKNUMV VBRK~FKDAT                                  
      113 VBRKKURRF VBRKKUNAG VBRK~FKSTO                                                               
      114 VBRPPOSNR VBRPFKIMG VBRPNETWR VBRPVGBEL VBRP~MATNR                                         
      115 VBRPARKTX VBRPMATKL VBRPWERKS VBRPLGORT                                                    
      116   INTO CORRESPONDING FIELDS OF TABLE ITAB                                                      
      117 FROM VBRK                                                                               
    118                                                                               
    119 INNER JOIN VBRP                                                                               
    120 ON VBRPVBELN = VBRKVBELN                                                                     
      121 WHERE VBRK~VBELN IN VBELN                                                                      
      122 AND VBRK~FKART IN FKART                                                              
      123 AND VBRK~FKDAT IN FKDAT                                                              
      124 AND VBRK~FKSTO NE 'X'                                                                
      125 AND VBRP~MATKL IN MATKL                                                              
      126 AND VBRP~WERKS IN WERKS                                                              
      127 AND VBRP~LGORT IN LGORT.                                                             
      128                                                                               
    129                                                                               
    130                                                                               
    131

  • 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 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 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

  • Help Error in RSQL module of database interface

    I have my RFC using OO.
    I can excute it in the ECC System, but when i using java to call the function , the error 'Error in RSQL module of database interface' return.
    I don't know why? If any help,  that will be great.
    in SM21 , there is it:
    BV5 Conversion error during INS database access for table ZCDPWF_LQ_
    AB0 Run-time error "DBIF_RSQL_INVALID_RSQL" occurred
    AB1 > Short dump "090429 095636 csrt05 CDPMORPHEUS " generated
    Edited by: ross.wang on Apr 29, 2009 4:33 AM

    I just found that in RFC, the data element should not be the domain. but must be the data element, or called data type.
    Change field data element, it will be ok
    Hope it is helpful.

  • I accidentally unplugged an external drive where I keep my photos and got this: There was an error opening the database for the library "/Volumes/iTunes LaCie/Aperture Library 2.aplibrary".

    My external drive accidently unplugged and I got this message:  There was an error opening the database for the library “/Volumes/iTunes LaCie/Aperture Library 2.aplibrary”.
    Can someone help?  My external drive is called "iTunes LaCie"
    THANKS!!
    I already repaired the disk...

    Open Aperture while holding down the option and command keys and run Repair Library

  • DBIF_RSQL_INVALID_RSQL - Error in RSQL module of database interface.

    Hi Frnds,
    I get the the error snd short dump when Ia m running a report.
    DBIF_RSQL_INVALID_RSQL - Error in RSQL module of database interface.
    The program it is pointing to main program. Details are mentioned below.
    Can anyone give some inputs as to why this error is coming..?
    Regards
    SPrakash
    Information on where terminated                                                                   |
    The termination occurred in the ABAP program "/1BCDWB/DBBSEG" in
    "START-OF-SELECTION".
    The main program was "/1BCDWB/DBBSEG ".
    The termination occurred in line 567 of the source code of the (Include)
    program "/1BCDWB/DBBSEG"
    |    of the source code of program "/1BCDWB/DBBSEG" (when calling the editor 5670).
    Source Code Extract
    Line
    SourceCde
    537
    START-OF-SELECTION.
    538
    IF MAX_SEL > 0.
    539
    RSEUMOD-TBMAXSEL = MAX_SEL.
    540
    ELSEIF MAX_SEL = 0.
    541
    CLEAR RSEUMOD-TBMAXSEL.
    542
    ENDIF.
    543
    IMPORT G_DATA_EXIT FROM MEMORY ID MEM_ID.
    544
    IF SY-BATCH IS INITIAL AND G_DATA_EXIT IS INITIAL.
    545
    IMPORT ACTION FROM MEMORY ID MEM_ID.
    546
    ELSE.
    547
    ACTION = 'ANZE'.
    548
    concatenate '/1BCDWB/DB' 'BSEG' into g_dbdatakey-eu_name.
    549
    g_dbdatakey-username = c_all.
    550
    import sort_NAME_TAB to %_TAB2_sort
    551
    field_name_tab to %_TAB2_field
    552
    from database dbdata(DB) id g_dbdatakey.
    553
    if sy-subrc = 0.
    554
    delete from dbdata
    555
    where relid    = 'DB' and
    556
    eu_name  = g_dbdatakey-eu_name and
    557
    username = c_all.
    558
    describe table %_tab2_field lines %_l_lines.
    559
    if not %_l_lines is initial.
    560
    %_TAB2[] = %_tab2_field[].
    561
    endif.
    562
    endif.
    563
    ENDIF.
    564
    CASE ACTION.
    565
    WHEN 'ANZE'.
    566
    try.
    >>>>>
    SELECT * FROM BSEG                     "client specified
    568
    APPENDING TABLE IBSEG
    569
    UP TO RSEUMOD-TBMAXSEL ROWS BYPASSING BUFFER
    570
    WHERE BUKRS IN I1
    571
    AND   BELNR IN I2
    572
    AND   GJAHR IN I3
    573
    AND   BUZEI IN I4
    574
    AND   BUZID IN I5
    575
    AND   AUGDT IN I6
    576
    AND   BSCHL IN I7
    577
    AND   KOART IN I8
    578
    AND   SHKZG IN I9
    579
    AND   WRBTR IN I10
    580
    AND   PSWSL IN I11
    581
    AND   ZUONR IN I12
    582
    AND   KOSTL IN I13
    583
    AND   SAKNR IN I14
    584
    AND   HKONT IN I15
    585
    AND   LIFNR IN I16
    586
    AND   MATNR IN I17

    Hello Satya
    Another possible error cause might be that the SQL statement sent to the DB is too large. You could try the following:
      SELECT * FROM bseg APPENDING TABLE ibseg
        PACKAGE SIZE 500  " or 1000
        WHERE bukrs IN ...
        AND ...
      ENDSELECT.
    For details see the ABAP keyword documentation for <b>PACKAGE SIZE</b>.
    Regards
      Uwe

  • 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.
    <b>This happens only if we give huge range of data. If we give small range of data it
    works fine</b>.
    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.
    <b>Unbelievable but true!</b>
    Just multiply the number of entries in the range with the field length and see where go go...
    Regards,
    Clemens

  • External program interfaces SLIN Error

    Dear Experts,
                      I am getting SLIN External program interfaces error . could you please tell me how to correct the  error ?
      *LOOP AT lt_p0001 INTO ls_p0001."
          SUBMIT yhrin_rhstru00 WITH pchwegid = 'O_S_P' WITH pchobjid-low = ls_p0001-orgeh "#EC *
          WITH pchbegda = '19000101' WITH pchenda = '99991231' WITH pchplvar = '01'
          WITH pchotype = 'O' AND RETURN.
          EXIT.
        ENDLOOP.*
    Regards,
    Sivakumar.A

    Dear experts ,
      I am receiving the following SLIN Error Message.
    Program:  SAPLYHRIN_MSSDB_ENH  Include:  LYHRIN_MSSDB_ENHU06  Row:    129   (Prio 1)
    PCHOBJID-LOW is not a parameter or a select option in report YHRIN_RHSTRU00
    (The message can be hidden with "#EC *)
          Program:  SAPLYHRIN_MSSDB_ENH  Include:  LYHRIN_MSSDB_ENHU06  Row:    129   (Prio 1)
    PCHENDA is not a parameter or a select option in report YHRIN_RHSTRU00
    (The message can be hidden with "#EC *)
    Thanks and Regards,
    Sivakumar.A

  • ERROR IN RSQL MODULE OF DATABASE INTERFACE

    Hi friends,
      I am executing the report it is working for 1 year(01.01.2006 to 28.02.2007).But if i enter 07.03.2007 to 07.03.2007 i am getting RSQL database interface problem.
    So please suggest me for this problem.Thanks for the same.
    Thanks&Regards
    Thummala Krishna Reddy

    Could you please post a portion of your code and the short dump description? It's would be better -:)
    Greetings,
    Blag.

  • ACS external database issue

    Hi
    I have the following issue, user exists on both the ACS and token server authenication is set to external database with no unknown user policy as the user is known to the ACS! this fails authenication error message is CS user unknown... Now if the unknown user policy is set to the external database the authenication works fine this is on 3.3. I have checked for bugs to no avail.
    Any assistance would be good...
    Thanks MJ

    Hi JG
    Many thanks for your response, it is configured this way due the documentation below:
    Known Users -Users explicitly added, either manually or automatically, into the CiscoSecureACS database.
    These are users added through User Setup in the HTML interface, by the RDBMS Synchronization feature, by the Database Replication feature, or by the CSUtil.exe utility. For more information about CSUtil.exe, see "CSUtil Database Utility".
    CiscoSecureACS attempts to authenticate a known user with the single database that the user is associated with. If the user database is the CiscoSecure user database and the user does not represent a Voice-over-IP (VoIP) user account, a password is required for the user. If the user database is an external user database or if the user represents a VoIP user account, CiscoSecureACS does not have to store a user password in the CiscoSecure user database.
    This is from the following link....
    http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/acs32/user/qu.htm
    Many thanks MJ

Maybe you are looking for