Error  exctration BI - DBIF_RSQL_INVALID_REQUEST

Hi,
I have an problem and I´ll try to reproduce it to you:
and then you’ll be able to see that the BI extraction job – which was started by the InfoPackage – has been cancelled.
In “Job OverView” press “Job Log” button to see further details and then you’ll see that the job was cancelled because of a ABAP short dump DBIF_RSQL_INVALID_REQUEST.
Double-click on “DBIF_RSQL_INVALID_REQUEST” to check the “ABAP Runtime Error” detailed description.
In this description you can see that the error occurred during the execution of a SAP standard program named “SAPLEDI1” – which seems to perform EDI related tasks.
Could you help me?
thanks,
Renato

Dash,
thanks for your help!! In fact, I´ve cleaned EDI* tables and re-execute the BI infosource and the dump problem was solved. Now I can´t see the data in the BI, only message :"Current status
No Idocs arrived from the source system."
I´ve checked RFC conections and everyting is OK. I don´t have dumps and any jobs beeing executed. I realy don´t know where the problem is!!!!
Thanks,
Renato

Similar Messages

  • Error on Startup MiniWAS 6.2 - DBIF_RSQL_INVALID_REQUEST

    Dear All,
    We are facing a strange issue when trying to call into the newly installed MiniWAS 6.2 system. We have installed SAP MiniWAS 6.2 on Windows XP. The laptop is not connected to any network. We have configured MS loopback adapter as well. The details of the IP address has been entered in the hostfile as well. But when we log into the SAP system, we get this dump
    DBIF_RSQL_INVALID_REQUEST
    Error analysis: Invalid request while Database interface when accessing table "DOKTL"
    What could be the issue?
    We are totally stuck.
    Please help us out.
    Would surely reward points to any help.
    Warm Regards
    Rajeet

    DBIF means "Database Interface", it has nothing to do with network (or not) in the first place.
    That error accessing table DOKTL is documented (Note 359463) and is some error in decompressing cluster tables.
    Without knowing more about the full error message (not the error of the dump but the reason causing the dump), one can´t say what´s wrong but just guess.
    Markus

  • Runtime error DBIF_RSQL_INVALID_REQUEST (table DOKTL)

    I have just installed the NW2004s Testdrive (on Ubuntu Server 10.10).
    When I log in as any user, I get a short dump DBIF_RSQL_INVALID_REQUEST saying: An invalid request was made to the database interface when accessing table "DOKTL ".
    I have seen some posts suggesting this could be due to entries in the /etc/hosts file, and I wonder whether this relates to the section in the index.html on the DVD that says:
    The file /etc/hosts should contain at least the following lines:
    Table 1: /etc/hosts 127.0.0.1      localhost      
    n.n.n.n      <HOSTNAME>.<DOMAINNAME>      <HOSTNAME>
    where "n.n.n.n" is a valid IP-adress.
    Is this the case? If so, what kind of entry must this be in /etc/hosts? This instruction in the index.html is very cryptic to me.
    Thanks,
    Martin

    Hello Siva,
    There is an entry similar to what you mentioned in /etc/hosts, which was added by the S99n4shost script. So /etc/hosts looks as follows (my hostname is nwtd):
    127.0.0.1       localhost
    127.0.1.1      nwtd
    # The following lines are desirable for IPv6 capable hosts
    ::1     localhost ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    192.168.155.1   n4shost
    I have tried adding a fully qualified domain name entry with nwtd on both the 127.0.1.1 and 192... lines.
    By the way, the message I see in the short dump is
    Error text........... "verify own hostname 'nwtd' failed"
    but I can ping nwtd successfully etc. What is the reason for this?

  • Log on error: DBIF_RSQL_INVALID_REQUEST

    Hello all,
    After about 2 weeks of battling installations of both Fedora and SAP NetWeaver Testdrive I have now reached the point of where I can use the gui to go to SAP.
    When I want to log in I get an immediate short dump saying: DBIF_RSQL_INVALID_REQUEST. Invalid call of database interface. In this thread: SAP NetWeaver 04 Testdrive SR1 with MaxDB they talk about the solution being in the hosts file. I have tried that but to no avail.
    Here is what I have configured:
    hostname = localhost.localdomain
    string to connect = conn=/H/localhost/S/3200
    my hosts file looks like:
    127.0.0.1               localhost
    10.0.0.14               localhost localdomain
    195.155.155.1   nw4host
    I have played around with the hostname by changing it to: localhost, NW4HOST and localhost.localdomain
    Further I checked if everything is running, it is.
    Anybody knows where I need to look?
    Regards,
    RolandD

    Hello all,
    well, i have installed SAP netweaver testdrive sr1 on linux Fedora Core 3. On server, everything works fine but I can't connect from my local server.
    I'm using SAPgui 4.6D on windows and I receive the same message than your first.
    Here is my /etc/hosts file :
    127.0.0.1 localhost     serveur.vileo.localhost serveur
    192.168.0.1 serveur     fredborn.no-ip.org
    192.168.0.1 nw4host
    But that change nothing...
    here is the error message :
    ==========================================================
    Runtime Errors         DBIF_RSQL_INVALID_REQUEST                                   
           Occurred on     18.06.2005 at   17:27:16                                                                               
    Invalid call of database interface.                                                                               
    What happened?                                                                               
    The current ABAP/4 program terminated due to                                       
    an internal error in the database interface.                                                                               
    Error analysis                                                                               
    In a statement an invalid request was made to the database interface               
    when accessing table "DOKTL ".                                                                               
    Last error logged in SAP kernel                                                                               
    Component............ "NI (network interface)"                                     
    Place................ "SAP-Server fredborn_NW4_00 on host fredborn.no-ip.org       
    (wp 0)"                                                                           
    Version.............. 37                                                           
    Error code........... "-2"                                                         
    Error text........... "hostname 'fredborn' unknown"                                
    Description.......... "NiPGetHostByName: hostname 'fredborn' not found"            
    System call.......... "gethostbyname"                                              
    Module............... "niuxi.c"                                                    
    Line................. 325                                                          
    The error reported by the operating system is:                                     
    Error number..... " "                                                              
    Error text....... " "                                                                               
    Trigger Location of Runtime Error:                                                                               
    Program Name                     SAPMSYST                                          
    Include                          SAPMSYST                                          
    Row                              2.529                                             
    Module type                      (FORM)                                            
    Module Name                      FILL_INFO_TAB                                                                               
    ==========================================================
    Can someone help me ???
    Regards,
    Fred
    PS : if i have to install MS Loopback, how must i config it ???

  • Runtime Error DBIF_RSQL_INVALID_REQUEST

    Hi,
    I have installed SAPNW trail version, and I get this error when i log on.
    I have installed it on a Windows XP Professional.
    Here is the log on error.
    <b>Runtime Errors         DBIF_RSQL_INVALID_REQUEST                                                      
    Date and Time          24.08.2006 15:25:28                                                                               
    Short text                                                                               
    Invalid request.                                                                               
    What happened?                                                                               
    The current ABAP/4 program had to be terminated because the                                      
         ABAP/4 processor detected an internal system error.                                                                               
    Error analysis                                                                               
    An invalid request was made to the database interface                                            
         when accessing table "DOKTL ".                                                                   
         Last error logged in SAP kernel                                                                               
    Component............ "NI (network interface)"                                                   
         Place................ "SAP-Server hema_NSP_00 on host hema (wp 0)"                               
         Version.............. 38                                                                               
    Error code........... "-16"                                                                      
         Error text........... "verify own hostname '172.16.0.101:0' failed"                              
         Description.......... "NiIBindSocket"                                                            
         System call.......... "bind"                                                                     
         Module............... "nixxi.cpp"                                                                
         Line................. 3144                                                                               
    The error reported by the operating system is:                                                   
         Error number..... 10049                                                                               
    Error text....... "WSAEADDRNOTAVAIL: Can't assign requested address"                                                                               
    Trigger Location of Runtime Error                                                                    
         Program                                 SAPMSYST                                                 
         Include                                 SAPMSYST                                                 
         Row                                     2.555                                                    
         Module type                             (FORM)                                                   
         Module Name                             FILL_INFO_TAB </b>
    can anyone help me with this please. How to solve this problem.I referred to the forum but not helpful I checkeed the host file etc, but still not helpful.
    Thanks,
    Prashant.
    Message was edited by: Prashant Kumar

    Hi Prashant,
    Set the profile parameter abap/buffersize value to maximum.Get the virtual memory increased.
    If it doesn't work, see in transaction db02 if there is sufficient tablespace.
    Let me knoe the status of tablespaces.
    Regards,
    Sabita

  • BAPI Runtime Error DBIF_RSQL_INVALID_REQUEST with module "KONV_BEARBEITEN"

    Hi Experts
    I am trying to create a sales order using BAPI FM BAPI_SALESORDER_CREATEFROMDAT1. After executing the program it shows in output screen that the sales order created and also displays the newly created sales order number. But when I want to check the order from VA03 it shows Express document "Update was terminated" received by author AAA, where AAA is login name.
    I also analysis the sort dump for which the update process was terminated. I give the error details
    Runtime Errors         DBIF_RSQL_INVALID_REQUES
    Error analysis
        An invalid request was made to the SAP database interface in a statement
         in which the table "KONV " was accessed.
    Below are the module name and report from where the error is coming.
    Function Module name  RV_SALES_DOCUMENT_ADD
    Program Name  SAPLV45U
    Include  LV45UF0K
    Row  26
    Source code from Rruntime Error
      Line  SourceCde
    1 *****************************************************************
        2 *  Unterroutinen RV-Auftragsabwicklung alphabetisch sortiert:
        3 *  ----------------------------------------------------------
        4 *  Buchstabe K:
        5 *
        6 *****************************************************************
        7
        8 *----------------------------------------------------------------
        9 *       FORM KONV_BEARBEITEN
       10 *----------------------------------------------------------------
       11 FORM KONV_BEARBEITEN.
       12
       13   CHECK: FKONV_GEAENDERT NE SPACE OR
       14          VORGANG = CHARH.
       15
       16   IF VORGANG NE 'H'.
       17     DELETE FROM KONV WHERE KNUMV = VBAK-KNUMV.
       18 ENHANCEMENT-POINT KONV_BEARBEITEN_10 SPOTS ES_SAPLV45U.
       19   ENDIF.
       20
       21   LOOP AT FXKOMV.
       22     FXKOMV-MANDT = VBAK-MANDT.
       23     FXKOMV-KNUMV = VBAK-KNUMV.
       24     MODIFY FXKOMV.
       25   ENDLOOP.
    >>>>>   INSERT KONV FROM TABLE FXKOMV.
       27   IF SY-SUBRC NE 0.
       28     MESSAGE A100 WITH
       29   ENDIF.
       30
       31 ENHANCEMENT-POINT KONV
       32 ENDFORM.
       33 *eject
    Below is my source code.
    *& Report  Z_BAPI_SALESORDER
    REPORT  z_bapi_salesorder.
    * Sales document type
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
    PARAMETERS: p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Sales organization
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
    PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Distribution channel
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
    PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Division.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
    PARAMETERS: p_spart TYPE spart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    * Sold-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
    PARAMETERS: p_sold  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Ship-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
    PARAMETERS: p_ship  TYPE kunnr.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    * Material
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
    PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Quantity.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
    PARAMETERS: p_menge TYPE dzmengc  OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Plant
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
    PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    * Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapiitemin  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapireturn1    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapisdhedu
                             WITH HEADER LINE.
    * Initialization.
    INITIALIZATION.
      v_text   = 'Order type'.
      v_text1  = 'Sales Org'.
      v_text2  = 'Distribution channel'.
      v_text3  = 'Division'.
      v_text4  = 'Sold-to'.
      v_text5  = 'Ship-to'.
      v_text6  = 'Material'.
      v_text7  = 'Quantity'.
      v_text9  = 'Plant'.
    * Start-of-selection.
    START-OF-SELECTION.
    * Header data
    * Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    * Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    * Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    * Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    * Partner data
    * Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    * Ship to
      partner-partn_role = 'WB'.
      partner-partn_numb = p_ship.
      APPEND partner.
    * ITEM DATA
      itemx-updateflag = 'I'.
    * Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    * Material
      item-material = p_matnr.
      itemx-material = 'X'.
    * Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    * Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
    *   Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
    *   Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
      CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
        EXPORTING
          order_header_in           = header
    *     WITHOUT_COMMIT            = ' '
    *     CONVERT_PARVW_AUART       = ' '
       IMPORTING
         salesdocument              = v_vbeln
    *     SOLD_TO_PARTY             =
    *     SHIP_TO_PARTY             =
    *     BILLING_PARTY             =
    *     RETURN                    =
        TABLES
          order_items_in            = item
          order_partners            = partner
    *     ORDER_ITEMS_OUT           =
    *     ORDER_CFGS_REF            =
    *     ORDER_CFGS_INST           =
    *     ORDER_CFGS_PART_OF        =
    *     ORDER_CFGS_VALUE          =
    *     ORDER_CCARD               =
    *     ORDER_CFGS_BLOB           =
         order_schedule_ex          = lt_schedules_in
    * Check the return table.
      IF v_vbeln <> space.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
        WRITE: / 'Document ', v_vbeln, ' created'.
      ELSE.
        WRITE: / 'Error in creating document'.
      ENDIF.
    I am unable to trace the exact reason. Please help and thanks in advance.
    Edited by: Joy Banerjee on Oct 12, 2009 7:47 AM

    Hi Prashant,
    Set the profile parameter abap/buffersize value to maximum.Get the virtual memory increased.
    If it doesn't work, see in transaction db02 if there is sufficient tablespace.
    Let me knoe the status of tablespaces.
    Regards,
    Sabita

  • Error while Scheduling InfoPackage

    When i am scheduling a full load in the infopackage to load data to PSA but am getting an DBIF_RSQL_INVALID_REQUEST error. The desciption is "An invalid request was made to the SAP database interface in a statement  in which the table "EDID4 " was accessed".
    Can anyone help me overcome this and resolve the issue, please.
    Thanks
    Neha

    check OSS Note 89384 if it is relevant to ur issue.

  • Error while copying profile...

    Error while copying profile from the default profile...
    runtime error- DBIF_RSQL_INVALID_REQUEST
    pls help..

    Irfan,
                You check weather new role name is in Z,Y name space or not?, check the same thing in other clients as well. If you are in windows , then your server mey need reboot because i faced similar problem but sorted after reboot.
    Regards,
    Hari.
    PS: Points are welcome.

  • DBIF_RSQL_INVALID_REQUEST

    when loggind on using SAP GUI, an abap runtime error is appearing at the beginning  DBIF_RSQL_INVALID_REQUEST whose details are
    Runtime Error          DBIF_RSQL_INVALID_REQUEST
    Date and Time          13.06.2008 09:57:13
    ShrtText
    Invalid call of database interface.
    What happened?
    The current ABAP/4 program terminated due to
    an internal error in the database interface.
    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
    In a statement an invalid request was made to the database interface
    when accessing table "DOKTL ".
    Last error logged in SAP kernel
    Component............ "NI (network interface)"
    Place................ "SAP-Server sapgrp_R3P_00 on host prdbpl2 (wp 0)"
    Version.............. 37
    Error code........... "-16"
    Error text........... "verify own hostname (sapgrp) failed"
    Description.......... "NiIMyAdrVerify"
    System call.......... " "
    Module............... "nixxi.cpp"
    Line................. 3161
    How to correct the error
    Start the work process affected and repeat the action that lead to the
    error.
    If the error is occurring in a program that you can make changes to,
    you should try to solve the problem yourself: Reformulate the database
    command by varying its attributes. Single record accesses can be
    replaced by input/output using internal tables and vice versa, selection
    criteria (WHERE clause) can be restructured, and nested SELECT loops can
    be replaced by FOR ALL ENTRIES and similar formulations.
    Please check the entries in the system log (Transaction SM21).
    Also check the entires in the developers trace for the correspond
    corresponding work process (transaction ST11).
    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_INVALID_REQUEST" C
    "SAPLSDOC" or "LSDOCU09"
    "DOCU_GET"
    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.
    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_INVALID_REQUEST" C
    "SAPLSDOC" or "LSDOCU09"
    "DOCU_GET"
    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.
    System environment
    SAP Release.............. "640"
    Application server....... "sapgrp"
    Network address.......... "192.168.4.14"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "8x Intel 801586"
    Character length......... 8 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "PRDBPL2"
    Database type............ "ORACLE"
    Database name............ "R3P"
    Database owner........... "SAPR3P"
    Character set............ "English_United State"
    SAP kernel............... "640"
    Created on............... "Nov 4 2004 23:26:03"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "OCI_920_SHARE "
    Patch level.............. "43"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory usage.............
    Roll..................... 8112
    EM....................... 2090592
    Heap..................... 0
    Page..................... 0
    MM Used.................. 942232
    MM Free.................. 1146912
    SAP Release.............. "640"
    User and Transaction
    Client.............. 100
    User................ "ADMIN"
    Language key........ "E"
    Transaction......... "SESSION_MANAGER "
    Program............. "SAPLSDOC"
    Screen.............. "SAPMSYST 0020"
    Screen line......... 87
    Information on where terminated
    The termination occurred in the ABAP program "SAPLSDOC" in "DOCU_GET".
    The main program was "SAPMSYST ".
    The termination occurred in line 249 of the source code of the (Include)
    program "LSDOCU09"
    of the source code of program "LSDOCU09" (when calling the editor 2490).
    Source Code Extract
    Line
    SourceCde
    219
    head-tdobject = 'DOKU'.
    220
    ENDCASE.
    221
    HEAD-TDNAME     = DOKHL-OBJECT.
    222
    HEAD-TDID       = DOKHL-ID.
    223
    HEAD-TDSPRAS    = DOKHL-LANGU.
    224
                HEAD-TDFORM     = DOKHL-DOKFORM.         "geä. hb 30/06/93
    225
    IF DOKHL-DOKFORM EQ 'HELP'.              "geä. hb 30/06/93
    226
    MOVE 'S_DOCU_SHOW' TO HEAD-TDFORM.     "geä. hb 30/06/93
    227
    ELSE.                                    "geä. hb 30/06/93
    228
    HEAD-TDFORM     = DOKHL-DOKFORM.       "geä. hb 30/06/93
    229
    ENDIF.                                   "geä. hb 30/06/93
    230
                HEAD-TDSTYLE    = DOKHL-DOKSTYLE.        "geä. hb 30/06/93
    231
    IF DOKHL-DOKSTYLE EQ 'DOKU'.             "geä. hb 30/06/93
    232
    MOVE 'S_DOCUS1' TO HEAD-TDSTYLE.       "geä. hb 30/06/93
    233
    ELSE.                                    "geä. hb 30/06/93
    234
    HEAD-TDSTYLE    = DOKHL-DOKSTYLE.      "geä. hb 30/06/93
    235
    ENDIF.                                   "geä. hb 30/06/93
    236
    HEAD-TDVERSION  = DOKHL-DOKVERSION.
    237
    HEAD-TDFUSER    = DOKHL-DOKFUSER.
    238
    HEAD-TDFRELES   = DOKHL-DOKFRELES.
    239
    HEAD-TDFDATE    = DOKHL-DOKFDATE.
    240
    HEAD-TDFTIME    = DOKHL-DOKFTIME.
    241
    HEAD-TDLUSER    = DOKHL-DOKLUSER.
    242
    HEAD-TDLRELES   = DOKHL-DOKLRELES.
    243
    HEAD-TDLDATE    = DOKHL-DOKLDATE.
    244
    HEAD-TDLTIME    = DOKHL-DOKLTIME.
    245
    HEAD-TDLINESIZE = '072'.
    246
    247
    DOKSTATE = DOKHL-DOKSTATE.
    248
    >>>>>
    SELECT *
    250
    FROM  DOKTL
    251
    INTO  TABLE IDOKTL
    252
    WHERE LANGU      =  LANGU
    253
    AND   ID         =  ID
    254
    AND   OBJECT     =  OBJECT
    255
    AND   TYP        =  TYP
    256
    AND   DOKVERSION =  DOKIL-VERSION
    257
    ORDER BY PRIMARY KEY.
    258
    259
    CLEAR IDOKTL.
    260
    READ TABLE IDOKTL INDEX 1.
    261
    262
    IF IDOKTL-DOKTEXT(5) NE '{
    tf'.
    263
    LOOP AT IDOKTL.
    264
    PERFORM LINE_APPEND.
    265
    ENDLOOP.
    266
    ELSE.
    267
    LOOP AT IDOKTL.
    268
    MOVE IDOKTL-DOKFORMAT TO ILINE-TDFORMAT.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    40
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    0020
    SY-UCOMM
    SY-TITLE
    System Program
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    3 FUNCTION     SAPLSDOC                            LSDOCU09                              249
    DOCU_GET
    2 FORM         SAPMSYST                            SAPMSYST                              699
    GET_COPYRIGHT_TEXT
    1 MODULE (PAI) SAPMSYST                            SAPMSYST                              180
    D020_COPYRIGHT
    Chosen variables
    Name
    Val.
    No.       3 Ty.          FUNCTION
    Name  DOCU_GET
    EXTEND_EXCEPT
    2
    0
    ID
    TX
    55
    48
    LANGU
    E
    4
    5
    OBJECT
    COPYRIGHT_SAP
    445554445554522222222222222222222222222222222222222222222222
    3F0929784F31000000000000000000000000000000000000000000000000
    PRINT_PARAM_GET
    X
    5
    8
    TYP
    E
    4
    5
    VERSION
    0000
    3333
    0000
    VERSION_ACTIVE_OR_LAST
    L
    4
    C
    DOKSTATE
    A
    4
    1
    DOKTITLE
    222222222222222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000000000000
    DOKTYP
    2
    0
    HEAD
    DOKU      COPYRIGHT_SAP                                                         TX  E
    4445222222445554445554522222222222222222222222222222222222222222222222222222222255224222222222
    4FB50000003F0929784F31000000000000000000000000000000000000000000000000000000000048005000000000
    LINE[]
    Table IT_19[0x134]
    PROGRAM=SAPMSYSTDATA=SAP_COPYRIGHT[]
    Table reference: 10
    TABH+  0(20) = 000000009049EB3C000000000A00000013000000
    TABH+ 20(20) = 0000000086000000FFFFFFFF04000000B8060000
    TABH+ 40( 8) = 14000000C1048000
    store        = 0x00000000
    ext1         = 0x9049EB3C
    shmId        = 0     (0x00000000)
    id           = 10    (0x0A000000)
    label        = 19    (0x13000000)
    fill         = 0     (0x00000000)
    leng         = 134   (0x86000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000021
    occu         = 20    (0x14000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    hsdir        = 0x00000000
    ext2         = 0x4849EB3C
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xA068EE3C
    delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    SY-REPID
    SAPLSDOC
    5454544422222222222222222222222222222222
    310C34F300000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    SYST-REPID
    SAPLSDOC
    5454544422222222222222222222222222222222
    310C34F300000000000000000000000000000000
    %_SPACE
    2
    0
    MASTERNEW
    N
    4
    E
    DOKIL-VERSION
    0004
    3333
    0004
    <O>
    ID_HEAD
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    IDOKTL[]
    Table IT_20[0x148]
    FUNCTION-POOL=SDOCDATA=IDOKTL[]
    Table reference: 13
    TABH+  0(20) = 0000000000000000000000000D00000014000000
    TABH+ 20(20) = 0000000094000000FFFFFFFF042B0000D82F0000
    TABH+ 40( 8) = 40000000C1048000
    store        = 0x00000000
    ext1         = 0x00000000
    shmId        = 0     (0x00000000)
    id           = 13    (0x0D000000)
    label        = 20    (0x14000000)
    fill         = 0     (0x00000000)
    leng         = 148   (0x94000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000209
    occu         = 64    (0x40000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    IDOKTL
    0000000000
    2222222222222222222222222222222222222222222222222222222222222222333333333322222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    IDOKTL-DOKTEXT+0(5)
    22222
    00000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LCLASS
    0.0.0.1.                                                                  ##
    0000222222222222222222222222222222222222222222222222222222222222222222002222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.       2 Ty.          FORM
    Name  GET_COPYRIGHT_TEXT
    %_SPACE
    2
    0
    USR02-USTYP
    2
    0
    SY-LANGU
    E
    4
    5
    SY-XFORM
    %_CONTROL_EXIT_DYNPRO
    254445544545455454554222222222
    5F3FE42FCF5894F49E02F000000000
    STATE
    2
    0
    TEXT3
    222222222222222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000000000000
    HEAD
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    NRTEXT-ENTRY+0(25)
    2222222222222222222222222
    0000000000000000000000000
    SAP_COPYRIGHT[]
    Table IT_19[0x134]
    %_DUMMY$$
    2222
    0000
    SY-REPID
    SAPMSYST
    5454555522222222222222222222222222222222
    310D393400000000000000000000000000000000
    SYST-REPID
    SAPMSYST
    5454555522222222222222222222222222222222
    310D393400000000000000000000000000000000
    NRTEXT-ENTRY+0(60)
    222222222222222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000000000000
    SY-SUBRC
    0
    0000
    0000
    SAP_COPYRIGHT
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    COPYRIGHT_DOCU
    222222222222222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000000000000
    No.       1 Ty.          MODULE (PAI)
    Name  D020_COPYRIGHT
    LOGON
    2008061221143020080613095713
    3333333333333333333333333333
    2008061221143020080613095713
    SAP_COPYRIGHT[]
    Table IT_19[0x134]
    SAP_COPYRIGHT
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    DB_COPYRIGHT[]
    Table[initial]
    DB_COPYRIGHT
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    RSYST-MANDT
    100
    333
    100
    RSYST-BNAME
    ADMIN
    444442222222
    14D9E0000000
    ALREADY_SHOWN
    2
    0
    SPACE
    2
    0
    SY
    0000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000
    0000000010000000000000000000000000000000100080001000000010000000000000000000C00000000000000000
    RSJOBINFO
    00000000000000                                  ####
    222222222222222222222222222222223333333333333322222222222222222222222222222222220000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SCREEN
    IUSRACL-BNAME
    4555444244444222222222222222222222222222222222222222222222222222222222222222222222222222222222
    953213CD2E1D5000000000000000000000000000000000000000000000000000000000000000000000000000000000
    Internal notes
    The termination occurred in the function "HandleRsqlErrors" of the SAP
    Basis System, specifically in line 755 of the module
    "//bas/640_REL/src/krn/runt/absapsql.c#10".
    The internal operation just processed is "SQLS".
    The internal session was started at 20080613095659.
    Internal call code.........: "[RSQL/OPEN/DOKTL ]"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=5524)
    When      : 6/13/2008 9:57:13.466
    Threads   : 2
    Computer Name       : PRDBPL2
    User Name           : SAPServiceR3P
    Number of Processors: 8
    Processor Type: x86 Family 15 Model 4 Stepping 8
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id 14e0
    eax=000230c8 ebx=00000000 ecx=3cd0f7c8 edx=00000000 esi=00395fd4 edi=00395fa8
    eip=7c82ed54 esp=0312dff0 ebp=0312e000 iopl=0         nv up ei pl nz ac pe nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000212
    function : KiFastSystemCallRet
    7c82ed54 c3               ret
    7c82ed55 8da42400000000   lea     esp,[esp]              ss:0312dff0=7c82ed5c
    7c82ed5c 8d642400         lea     esp,[esp]              ss:0625b53f=00000000
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    0312e000 00395fa8 00000000 00000001 01a41b6c 000014e0 ntdll!KiFastSystemCallRet
    00000000 00000000 00000000 00000000 00000000 00000000 <nosymbols>
    State Dump for Thread Id 1560
    eax=04a9feac ebx=00000103 ecx=d12b92c9 edx=04a9febb esi=00000000 edi=00000000
    eip=7c82ed54 esp=04a9feb0 ebp=04a9fef4 iopl=0         nv up ei pl zr na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    function : KiFastSystemCallRet
    7c82ed54 c3               ret
    7c82ed55 8da42400000000   lea     esp,[esp]              ss:04a9feb0=7c821514
    7c82ed5c 8d642400         lea     esp,[esp]              ss:07bcd3ff=004c0600
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    04a9fef4 00fc64ac 00000688 00000000 00000000 03892010 ntdll!KiFastSystemCallRet
    04a9ff84 7c36b381 00000000 00000000 00000000 038920a8 disp+work!SigIMsgFunc
    04a9ffb8 77e66063 038920a8 00000000 00000000 038920a8 MSVCR71!endthreadex
    04a9ffec 00000000 7c36b312 038920a8 00000000 00000000 kernel32!GetModuleFileNameA
    List of ABAP programs affected
    Index
    Ty.
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    SAPMSYST
    0
    11.08.2006
    12:12:09
    91136
    E
    1
    Prg
    SAPMSSYD
    0
    11.08.2006
    12:12:08
    17408
    E
    2
    Prg
    SAPFSYSCALLS
    0
    06.11.2003
    20:52:59
    6144
    E
    3
    Typ
    DOKIL
    0
    12.05.1997
    16:46:17
    3072
    4
    Typ
    TLINE
    0
    08.03.1992
    00:19:59
    2048
    5
    Prg
    %_CCXTAB
    0
    06.11.2003
    21:51:14
    5120
    E
    6
    Typ
    SCXTAB_CONTROL
    0
    06.11.2003
    20:31:00
    5120
    7
    Prg
    SAPLSNCA
    7
    06.11.2003
    21:55:16
    27648
    E
    8
    Typ
    SCXTAB_CONTROL
    0
    06.11.2003
    20:31:00
    5120
    9
    Prg
    SAPCNVE
    9
    06.11.2003
    20:52:58
    6144
    E
    10
    Prg
    SAPLLANG
    10
    06.11.2003
    20:53:03
    8192
    E
    11
    Prg
    SAPFSPOR
    0
    16.12.2003
    20:52:12
    12288
    E
    12
    Prg
    SAPLSCNT
    12
    06.11.2003
    20:53:04
    24576
    E
    13
    Typ
    DYCBOX
    0
    20.08.1998
    11:16:53
    2048
    14
    Prg
    SAPLSVSM
    14
    11.08.2006
    11:45:30
    25600
    E
    15
    Prg
    SAPLSGUI
    15
    12.11.2004
    13:59:56
    61440
    E
    16
    Prg
    SAPLSTTM
    16
    11.08.2006
    10:06:38
    75776
    E
    17
    Prg
    SAPLSBDC
    17
    11.08.2006
    10:34:54
    38912
    E
    18
    Prg
    CL_DATAPROVIDER===============CP
    18
    06.11.2003
    20:52:43
    43008
    E
    19
    Prg
    %_CCNTL
    18
    06.11.2003
    20:52:41
    13312
    E
    20
    Typ
    OBJ_RECORD
    0
    14.02.1998
    08:30:43
    2048
    21
    Prg
    SAPLSTUP
    21
    11.08.2006
    11:27:23
    65536
    E
    22
    Prg
    SAPLCNDP
    22
    11.08.2006
    12:10:16
    190464
    E
    23
    Prg
    SAPLSFES
    23
    11.08.2006
    12:11:48
    248832
    E
    24
    Prg
    SAPSHDTV
    12
    06.11.2003
    20:57:23
    27648
    E
    25
    Prg
    SAPFGUICNTL
    0
    06.11.2003
    20:57:18
    20480
    E
    26
    Prg
    SAPLOLEA
    26
    11.08.2006
    10:34:49
    82944
    E
    27
    Prg
    SAPLTHFB
    27
    11.08.2006
    12:11:17
    312320
    E
    28
    Typ
    WPINFO
    0
    26.02.1999
    14:49:01
    5120
    29
    Prg
    SAPLSDEB
    29
    11.08.2006
    11:47:31
    204800
    E
    30
    Prg
    SAPLURFC
    30
    27.01.2004
    13:50:57
    16384
    E
    31
    Prg
    SAPLSPLUGIN
    31
    06.11.2003
    21:28:25
    6144
    E
    32
    Typ
    SWCBCONT
    0
    15.11.2000
    17:55:11
    3072
    33
    Typ
    OLE_VERBS
    0
    04.04.1995
    16:02:20
    2048
    34
    Typ
    OLE_PA
    0
    04.04.1995
    16:02:19
    2048
    35
    Prg
    CL_GUI_PROPS_CONSUMER=========CP
    35
    06.11.2003
    20:52:43
    26624
    E
    36
    Prg
    CL_DYNAMIC_GUI_EXTENSIONS=====CP
    36
    06.11.2003
    20:52:43
    33792
    E
    37
    Prg
    CL_GUI_DATAMANAGER============CP
    37
    11.08.2006
    12:11:38
    71680
    E
    38
    Prg
    CL_ABAP_CHAR_UTILITIES========CP
    38
    12.11.2004
    14:02:13
    11264
    E
    39
    Typ
    USR41
    0
    07.12.2000
    13:35:06
    3072
    40
    Typ
    ARFCRDATA
    0
    09.11.2000
    14:04:16
    6144
    41
    Prg
    SAPLGRFC
    41
    06.11.2003
    20:53:02
    13312
    E
    42
    Prg
    CL_GUI_DYNPRO_COMPANION=======CP
    42
    06.11.2003
    20:52:43
    14336
    E
    43
    Prg
    SAPLSDOC
    43
    11.08.2006
    12:11:46
    634880
    E
    44
    Prg
    SAPMSDCU
    43
    11.08.2006
    12:12:02
    295936
    E
    45
    Typ
    DOKHL
    0
    12.05.1997
    16:46:16
    4096
    46
    Typ
    DOKTL
    0
    12.05.1997
    16:46:17
    3072
    47
    Typ
    TLINE
    0
    08.03.1992
    00:19:59
    2048
    48
    Typ
    DOKTL
    0
    12.05.1997
    16:46:17
    3072
    49
    Typ
    USR02
    0
    06.11.2003
    20:38:33
    7168
    50
    Typ
    SYST
    0
    04.12.2000
    14:54:51
    27648
    51
    Typ
    TEXTPOOL
    0
    10.07.1997
    00:11:35
    2048
    52
    Typ
    RSYST
    0
    10.07.1997
    00:07:55

    Hi,
    If this problem is while logging in  then contact basis person.
    Reward if useful.
    Regards
    Susheel

  • DUMP CRITICAL ERROR - SAP R/3 Enterprise

    Hello Guys,
    I am with the following error in my environment DEV, with the QAS environments and PRD does not happen the same mistake.
    The error occurs when I try to access the table BSEG through transacão SE16. The Dump what happens is:
    DBIF_RSQL_INVALID_REQUEST
    shot dump DBIF_RSQL_INVALID_REQUEST when acessing in cluster table BSEG
    Watching this error in the archives of trace dev_w1, I have the following log of error:
    B Mon Aug 11 10:13:06 2008
    B  dbmyclu : c2_decompress (9.6740) : damaged 0. cluster record (pgs_total 0, bitem_total 0, max_cachecnt 32700)
    B  ***LOG BZW=> error BITT       on compression/decompression using c2_decompr
    B  **LOG BY0=> myCluster: RFBLG      myKey: 11028  37002303432008
    B  dbmyclu : c3_process_cluster (9.14819): received return code 2 from c2_decompress.
    B  dbmyclu : c3_fetch_next_pages_on_db (9.12297): received return code 2 from c3_process_cluster/c3_reread_single_cluster_on_db.
    B  dbmyclu : c3_get_next_multiple_cluster (9.13489): received return code 2 from c3_fetch_next_pages_on_db/c3_get_single_cluster (cid 0, lockstate 0, readmode 1, repeat 0).
    B  dbmyclu : c3_fetch_cluster_cursor (9.13711): received return code 2 out of getloop (cid 0, lockstate 0, readmode 1, readclu -10490, nextclu 0, clucheck 0).
    B  dbmyclu : c2_seqcount (9.10006): received return code 2 from c3_fetch_cluster_cursor (cid 0, readclu -10490).
    B  dbmyclu : c2_count (9.4512): received return code 2 from c2_seqcount (table BSEG      , upto 0, mod_cnt 5691071).
    B  dbmyclu : db_rclu2 (9.2761): received return code 2 from cluster access for fcode 257, table BSEG      , cluster RFBLG     .
    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_VMIT_CLEANUP entered.
    A  ** RABAX: level LEV_RX_VMIT_CLEANUP completed.
    A  ** RABAX: level LEV_RX_ROLLBACK entered.
    M  ***LOG R68=> ThIRollBack, roll back ()
    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_C_STACK entered.
    A  ** RABAX: level LEV_RX_C_STACK completed.
    A  ** RABAX: level LEV_RX_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_INTERFACES entered.
    A  ** RABAX: level LEV_RX_INTERFACES completed.
    A  ** RABAX: level LEV_RX_GET_MESS entered.
    A  ** RABAX: level LEV_RX_GET_MESS completed.
    A  ** RABAX: level LEV_RX_INIT_SNAP entered.
    A  ** RABAX: level LEV_RX_INIT_SNAP completed.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP entered.
    A  ** RABAX: level LEV_SN_END completed.
    A  ** RABAX: level LEV_RX_SET_ALERT entered.
    A  ** RABAX: level LEV_RX_SET_ALERT completed.
    A  ** RABAX: level LEV_RX_COMMIT entered.
    A  ** RABAX: level LEV_RX_COMMIT completed.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
    A  ** RABAX: level LEV_RX_RESET_PROGS entered.
    A  ** RABAX: level LEV_RX_RESET_PROGS completed.
    A  ** RABAX: level LEV_RX_STDERR entered.
    A  Mon Aug 11 10:13:06 2008
    A 
    A  ABAP Program /1BCDWB/DBBSEG                          .
    A  Source /1BCDWB/DBBSEG                           Line 692.
    A  Error Code DBIF_RSQL_INVALID_REQUEST.
    A  Module  $Id: //bas/640_REL/src/krn/runt/absapsql.c#17 $ SAP.
    A  Function HandleRsqlErrors Line 779.
    A  ** RABAX: level LEV_RX_STDERR completed.
    A  ** RABAX: level LEV_RX_RFC_ERROR entered.
    A  ** RABAX: level LEV_RX_RFC_ERROR completed.
    A  ** RABAX: level LEV_RX_RFC_CLOSE entered.
    A  ** RABAX: level LEV_RX_RFC_CLOSE completed.
    A  ** RABAX: level LEV_RX_IMC_ERROR entered.
    A  ** RABAX: level LEV_RX_IMC_ERROR completed.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
    A  ** RABAX: level LEV_RX_ERROR_SAVE entered.
    A  ** RABAX: level LEV_RX_ERROR_SAVE completed.
    A  ** RABAX: level LEV_RX_ERROR_TPDA entered.
    A  ** RABAX: level LEV_RX_ERROR_TPDA completed.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    A  ** RABAX: level LEV_RX_END entered.
    A  ** RABAX: level LEV_RX_END completed.
    A  ** RABAX: end no http/smtp
    A  ** RABAX: end RX_GOTO_RABAX
    A  Invalid request. accessed..
    Someone could help me with this error?
    My environment is as follows:
    Product Version SAP R / 3 Enterprise 47X110
    AIX Operating System
    Database DB2/UDB
    kernel release 640 / patch 155
    Someone could help me with this error?
    Thanks

    please check if this OSS .946659
    I am also looking for a note as we got the same error message.
    See if it helps or let me know your solution if you fix it.
    Good luck..
    Amit Asthana

  • ERROR IN STARTING APPLICATION

    Hi gurus...
    when i start sap , after initializing all the servers ,come WAIT mode...i click on sap logon ...then its giving me an error ..."RUN TIME ERROR - DBIF_RSQL_INVALID_REQUEST.
    ERROR ANALYSIS :
    IN A STATEMENT AN INVALID REQUEST WAS MADE TO THE DATABASE INTERFACE WHEN ACCESSING TABLE "DOTKL".
    CAN ANYBODY PLZ GIVE ME THE SOLUTION.
    REGARDS...AND POINTS WILL BE AWARDED ...
    SURIYA.

    what can you do?
    make a note of the actions and input which caused the error.
    to resolve the problem, contact sap system admin.
    you can use trasaction st22 (abap dump analysis) to view the administer termination messages,especially those beyond their normal deletion date.
    what happened?
    the current abap/4 program terminated due to an internal error in the database interface.
    error analysis
    in a statement an invalid request was made to the database interface when accessing table "DOTKL"
    LAST ERROR LOGGED IN SAP KERNEL
    COMPONENT --N I NETWORK INTERFACE
    VERSION -36
    ERROR CODE - "-16"
    ERROR TEXT - "VERIFY OWN HOSTNAME (SIVA-SAP) FAILED"
    DESCRIPTION - "NiIMyAdrVerify"
    SYSTEM CALL- " "
    MODULE - "nixxi.c"
    line 2859
    how to correct the error
    start the work process affected and repeat the action that lead to the error.if the error is occuring in a program that you can make changees to ,you should try to solve the problem yourself.reformulate the database command by varying its attributes.single record accesses can be replaced by input/output using internal tables and vice versa,selection criteria (WHERE clause) can be restructured,and nested SELECT loopscan be replaced by FOR ALL ENTRIES and similar formulations.
    Please check the entries in the system log (transaction sm21). also check entries in the developers trace for the correspond corresponding work process(transaction st11).
    you may be able to find an interim solution to the problem in the sap note system.if u have access to the note system urself,use the following search criteria:
    "DBIF_RSQL_INVALID_REQUEST" C
    "SAPLSDOC" or "LSDOCU01"
    "DOCU_READ".
    so now pls gve me the solution gurus.
    SURIYA.

  • Runtime error while log in to SP12 help.

    Hi SDN,
    I have installed ABAP Trail SP12 several time each & every time after 2 - 3 days i am getting one dump then i have to again format my whole system to get it work again.
    Since the registry cleanning tool is also not working.
    following is the DUMP
    Runtime Errors         DBIF_RSQL_INVALID_REQUEST                                                         
    Date and Time          2008-03-27 08:38:50                                                                               
    Short text                                                                               
    Invalid request.                                                                               
    What happened?                                                                               
    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.                                                                               
    The situation points to an internal error in the SAP software                                       
         or to an incorrect status of the respective work process.                                           
         For further analysis the SAP system log should be examined                                          
         (transaction SM21).                                                                               
    For a precise analysis of the error, you should supply                                              
         documents with as many details as possible.                                                                               
    Trigger Location of Runtime Error                                                                       
         Program                                 SAPMSYST                                                    
         Include                                 SAPMSYST                                                    
         Row                                     2,556                                                       
         Module type                             (FORM)                                                                               
    Please Help,
    Regards,
    Rahul

    There's another thread here about the same problem and I noticed that it's exactly the same error message.
    Just for fun I did a search on Row 2,556 and found: SAPNW70 Runtime Error BDIF_RSQL_INVALID_REQUEST

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

  • ABAP Run time error in SD

    Hi
    I am Belongs to SD. In my home PC i am getting following ABAP Runtime error.
    Plaese help me ABAP Guys.
    <b>DBIF_RSQL_INVALID_REQUEST</b>
    This error i am getting in most transanctions.
    Please give me the solution for this.
    Regards,
    Ravi Chandra

    Hello Ravi,
    I was talking about the details of the dump, there is much more than just the header line. It tells you what happened and where it happened. Could you please post that information?
    Also do you only get that error when connecting remotely with your home PC or also when you are directly connected to the R/3 system?
    Regards,
    Michael

  • Dump when logging onto NW7.0 ABAP/Java trial - DBIF_RSQL_INVALID_REQUEST

    Hello all,
    I downloaded and installed the NW 7.0 Java & ABAP trial on Linux/VMware.
    Everything went smoothly, until I logged on, when I got a short dump DBIF_RSQL_INVALID_REQUEST. I can continue working with it - I could even install the SAP license - but I keep getting the same dump every now and again.
    I found [this thread|Short Dump: Before Login in SAP Netweaver 7 ABAP Trial; and a few others describing the same issue, however it's not going away. The firewall is completely disabled. I get the error logging in via sapgui for windows SP4 and also when using PlatinGUI on the server itself. The machine has plenty of resources and there are no errors starting up.
    I did have a problem where there was a message about not finding "virtuell host in ifconfig" on startup, so I changed my hostname to n4shost and pointed it to 127.0.0.1 in the hosts file - the error went away.
    Any ideas?
    Cheers,
    Mike

    OK, that makes sense in your setup. I run SAP inside a VM, in a non-networked scenario VMWare creates a local network between the host laptop and the virtual machine and assigns addresses to both using DHCP. Interestingly I also found an easier workaround can be done just by using VMWare: add another network card, make it a static IP and don't connect it.
    Actually now that you mention it, in a past life as a techie I remember we set up servers in exactly that way: Static IPs for an internal server network and DHCP to the outside on a separate network card. I guess even at interprocess level the system doesn't rely on everything being local (otherwise it would just use localhost).
    Cheers,
    Mike

Maybe you are looking for