Fetch Next Cursor Short Dumps

Hello All,
   I have the following code which short dumps after losing its cursor position. 
OPEN CURSOR WITH HOLD dbcur FOR
      select * from ekpo where bukrs in s_bukrs2.
      do.
          FETCH NEXT CURSOR dbcur INTO table iekpo package size pkgsize.
          if sy-subrc <> 0.
             close cursor dbcur.
             exit.
          else.
              perform ouput_to_text_file.
              refresh: iekpo.
           endif.
      enddo.
I have millions of records to be extracted and  simple select to an internal table causes memory problems.  Thus I need to extract a chunk of records write them to a text file, then get the next chunk. 
Any suggestions?
Thank you,
Jerry

GUI Download probably causes problem, writing to a dataset on app server might not cause the problem, maybe you want to try.
Regarding the select, here is some pseudo code outlining what I mean:
clear wa_ekpo.
do.
  select * from ekpo into table lt_ekpo up to 10,000 rows
      where ebeln > wa_ekpo-ebeln or ( ebeln = wa_ekpo-ebeln and ebelp > wa_ekpo-ebelp )
      order by primary key.
  if sy-subrc ne 0.
    exit.
  endif.
  download lt_ekpo (appending to existing file)
  l_lines = lines( lt_ekpo ).
  read table lt_ekpo into wa_ekpo index l_lines.
enddo.
Will run for a while, but should not dump out
Thomas

Similar Messages

  • Fetch next cursor/ invalid database interruption

    Hi Experts,
    I would appreciate your help for the following problem:
    I am trying to develope something like that:
    OPEN CURSOR ... WITH HOLD
    loop at ...
             FETCH ... PACKAGE SIZE ... into lt_names
             insert table ZZ_XXXX ... from lt_names
             commit work
    endloop.
    in the second loop, the FETCH dumps raising the runtime error "Invalid interruption of a database selection"
    Runtime Error          DBIF_RSQL_INVALID_CURSOR
    Exception              CX_SY_OPEN_SQL_DB      
    The cursor is opened "with hold".
    Does anybody know, why does it dump?
    Cheers
    marmsg

    Hi Thomas,
    I have four entires in a custom z-table. During FETCH Statements, I use, PACKET SIZE, of 2.
    Rough code is as follows:
    OPEN CURSOR WITH HOLD w_dbcur1 FOR
    SELECT * FROM ztable.
    WHILE sy-subrc = 0.
    FETCH NEXT CURSOR w_dbcur1 INTO TABLE i_notes PACKAGE SIZE p_pack. "Here packet size is of 2
    IF sy-subrc = 0.
    Calling some X BAPI Function module.
    Calling BAPI_TRANSACTION_COMMIT Function module.
    ENDIF.
    ENDWHILE.
    CLOSE CURSOR w_dbcur1.
    Here the problem is, if I give packet size as 30,000, then program is working fine. If I am giving packet size as 2, which less than 4 entries in the table, The program dumps either at first execution of FETCH NEXT CURSOR statement or at the second time of FETCH NEXT CURSOR. Can you provide exact solution for this, and not the links please. Rewards will be provided.
    Thanks,
    Vijayanand.

  • Short Dump with Fetch in ECC 6.0

    Hello Friends,
    I have a query sth like this.
    <b>fetch next cursor wc_cursor
             into table it_bdi_entry
             package size s_pkg.</b>
    it_bdi_entry is a internal table of type bdi_entry.
    When i use this fetch statement in ECC 6.0 and the fetching row is not all char (like bdi_entry) then i see a short dump saying sth like the source and target are not of same types. How do i overcome this error. please suggest. Thanks in advance.

    HI Ramu
    I doubt the dump is due to UNICODE compliancy.
    In UNICODE systems, we can transfer data between structures only when the structure are similar or having only character fields.
    To avoid the dump, we might need to handle field by field.
    Hope this helps.
    Kind Regards
    Eswar

  • Short dump in SAP R/3: SQL statement buffer overflow?

    Hello,
    I hope someone can help us with the following problem:
    A short dump in SAP R/3 (DBIF_RSQL_INVALID_RSQL, CX_SY_OPEN_SQL_DB)
    occurred during a delta load, which worked fine for several month.
    The custom code crashes at a FETCH NEXT CURSOR statement.
    I assume, it might be a SQL statement buffer overflow in SAP R/3?
    The problem can be reproduced by RSA3, and is therefore not time-dependent.
    The problem did not occur before or on the quality assurance system.
    Cursor code:
          Read all entries since last transfer (delta mechanism)
            OPEN CURSOR WITH HOLD s_cursor FOR
              SELECT * FROM ekko
                WHERE ebeln IN t_selopt_ekko.
    t_selopt_ekko has up to 60.000 data sets, which worked fine in the past.
    It is very likely that the amount of data during the first crash did not exceed this.
    SQL-Trace of RSA3 call:
    It seems that 25150 data set can be processed via fetch before the short dump occurs
    After that object SNAP is written:
    "...DBIF_RSQL_INVALID_RSQL...dynpen00 + 0xab0 at dymain.c:1645 dw.sapP82_D82
    Thdyn...Report für den Extraktoraufruf...I_T_FIELDS...Table IT_43[16x60]TH058FUNCTION=
    RSA3_GET_DATA_SIMPLEDATA=S_S_IF_SIMPLE-T_FIELDSTH100...shmRefCount  = 1...
    ...> 1st level extension part <...isUsed       = 1...isCtfyAble   = 1...> Shareable Table Header Data
    <...tabi         = Not allo......S_CURSORL...SAPLRSA3...LRSA3U06...SAPLRSA3...
    During dump creation the following occurs:
    "...SAPLSPIAGENTCW...CX_DYNAMIC_CHECK=...CRSFH...BALMSGHNDL...
    DBIF_RSQL_INVALID_RSQL...DBIF_RSQL_INVALID_RSQL...DB_ERR_RSQL_00013...
    INCL_ABAP_ERROR...DBIF_INCL_INTERNAL_ERROR...INCL_INTERNAL_ERROR...
    GENERAL_EXC_WITHOUT_RAISING...INCL_SEND_TO_ABAP...INCL_SEARCH_HINTS...
    INCL_SEND_TO_SAP...GENERAL_EXC_WITHOUT_RAISING...GENERAL_ENVIRONMENT...
    GENERAL_TRANSACTION...GENERAL_INFO...GENERAL_INFO_INTERNAL...
    DBIF_INCL_INTERNAL_CALL_CODE..."
    Basis says, that the Oracle data base works fine. The problem seems to be a SAP R/3 buffer.
    Does anyone had a similar problem or knows where such a buffer might be or how it can be enlarged?
    Best regards
    Thomas
    P.S.
    Found a thread that contains part of the dump message "dynpen00 + 0xab0 at dymain.c:1645":
    Thread: dump giving by std prg contains -> seems not to be helpful
    Found a similar thread:
    Thread: Short dump in RSA3 --Z Data Source -> table space or somting else?
    Edited by: Thomas Köpp on Apr 1, 2009 11:39 AM

    Hi Thomas,
          Its due to different field length.
    Just check it out in code after FETCH NEXT CURSOR what internal table you have mention.
    that internal table shoul deffined by taking refrence of ekko, because your code is
    OPEN CURSOR WITH HOLD s_cursor FOR
    SELECT * FROM ekko
    WHERE ebeln IN t_selopt_ekko.
    hope you got solution.
    Regards,

  • Short dump in RSA3 --Z Data Source

    Hi,
    I created a Z data source based on view and i appended extract structure to insert ZZ fields.
    When i execute the data source it is showing me short dump how shall i proceed
    I checked the view conditions and it is extracting data and showing now error and i checked the enhancements i have written in CMOD and checked the program it is displaying No syntax errors
    Please advise me on how to correct the errors....
    If need further info of short dump please ask
    Runtime Error          DBIF_RSQL_INVALID_RSQL
    Exception              CX_SY_OPEN_SQL_DB                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLRSA3" had to be terminated because one of the
    Statements could not be executed. 
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail belo.The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', waS neither                                                           caught nor passed along using a RAISING clause, in the procedure "RSA3_GEN_GET_DATA" "(FUNCTION)"                                                                               
    Since the caller of the procedure could not have expected this exceptio to occur, the running program was terminated.           
    The reason for the exception is:                                      
    The data read during a SELECT access could not be inserted into the target field.                                                         
    Either conversion is not supported for the target field's type or the target field is too short to accept the value or the data are not in a form that the target field can accept.
    Information on where terminated                                                                               
    The termination occurred in the ABAP program "SAPLRSA3" in "RSA3_GEN_GET_DATA".   
    The main program was "RSFHGEN2 ".                                                                               
    The termination occurred in line 226 of the source code of the (Include)          
    program "LRSA3U03"                                                               
    of the source code of program "LRSA3U03" (when calling the editor 2260).          
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in   
    the                                                                               
    procedure "RSA3_GEN_GET_DATA" "(FUNCTION)" but was not handled locally, not       
    declared in the                                                                  
    RAISING clause of the procedure.                                                  
    The procedure is in the program "SAPLRSA3 ". Its source code starts in line 5     
    of the (Include) program "LRSA3$03 ".                                             
    Program
    002150                                                                            
    002160       CASE G_S_INTERFACE-UPDMODE.                                          
    002170         WHEN 'F' OR 'C' OR 'I'.                                            
    002180   * First data package -> OPEN CURSOR                                      
    002190           IF G_COUNTER_DATAPAKID = 0.                                      
    002200   * Open Cursor for dynamical SELECT                                       
    002210             OPEN CURSOR WITH HOLD G_CURSOR FOR                             
    002220             SELECT * FROM (G_S_OLTPSOURCE-EXTRACTOR)                       
    002230                    WHERE (L_T_DYNAMIC_SELECT).                             
    002240           ENDIF.                                                           
    002250   * Fetch first data package                                               
    >           FETCH NEXT CURSOR G_CURSOR                                       
    002270                        APPENDING CORRESPONDING FIELDS OF TABLE E_T_DATA    
    002280                        PACKAGE SIZE G_S_INTERFACE-MAXSIZE.                 
    002290           IF SY-SUBRC <> 0.                                                
    002300             RAISE NO_MORE_DATA.                                            
    002310           ENDIF.                                                           
    002320           G_COUNTER_DATAPAKID = G_COUNTER_DATAPAKID + 1.                   
    002330         WHEN 'D'.                                                          
    002340           PERFORM FETCH_GEN_DELTA IN PROGRAM (L_GEN_PROGID)                
    002350                           TABLES E_T_DATA                                  
    002360                                  L_T_DYNAMIC_SELECT                        
    002370                                  G_T_FIELDS                                
    002380                           USING  G_S_INTERFACE-MAXSIZE                     
    002390                           CHANGING L_FLG_NO_MORE_DATA.                     
    002400           IF L_FLG_NO_MORE_DATA = 'X'.                                     
    002410             IF NOT L_T_BDCPS[] IS INITIAL.                                 
    002420               L_T_BDCPS-PROCESS = SBIWA_C_FLAG_ON.                         
    002430               MODIFY L_T_BDCPS                                             
    002440                    TRANSPORTING PROCESS WHERE PROCESS = SBIWA_C_FLAG_OFF.

    Hello,
    This thread is answered. Was it the table space or something else?
    We may have a similar issue as recently posted in thread:
    "Short dump in SAP R/3: SQL statement buffer overflow?"
    Best regards
    Thomas

  • Short dump when executing report.

    Dear all,
    I’m running a web template report which is calling a multiprovider and within the multiprovider are 9 cubes. All cubes have aggregates and are optimize for performance. Lately, for the past 2 days, users have been complaining that they keep getting error 500, a time out error. This happens only to certain users and not all. Some users are able to query for data more the 5 years where as some not even 1 day. Below is the error which BW is throwing back to us. Can you please help me analyze the error?
    Error analysis
        After a certain length of time, the program is terminated. In the case
        of a work area, this means that
        - endless loops (DO, WHILE, ...),
        - database accesses producing an excessively large result set,
        - database accesses without a suitable index (full table scan)
        do not block the processing for too long.
    Trigger Location of Runtime Error
        Program                                 SAPLRSDRS
        Include                                 LRSDRSF04
        Row                                     116
        Module type                             (FORM)
        Module Name                             FETCH_DATA_OPENSQL
      103
      104     IF <l_s_data>      IS NOT ASSIGNED OR
      105        <l_s_data>      IS NOT ASSIGNED OR
      106        <l_s_data_olap> IS NOT ASSIGNED .
      107       RAISE EXCEPTION TYPE cx_rs_program_error
      108          EXPORTING
      109            method = 'FETCH_DATA_OPEN_SQL-2-'.
      110     ENDIF.
      111   ENDIF.
      112
      113
      114   IF i_pkgsize <= 0.
      115 *   Reading all data with one single fetch
    >>>>>     FETCH NEXT CURSOR i_cursor
      117       INTO CORRESPONDING FIELDS OF TABLE <l_t_data>.
      118     e_eof = rs_c_true.
      119   ELSE.
      120 *   Reading only one package
      121     FETCH NEXT CURSOR i_cursor
      122       INTO CORRESPONDING FIELDS OF TABLE <l_t_data>
      123       PACKAGE SIZE i_pkgsize.
      124
      125 *   If less than 'i_pkgsize' many tuples are read
      126 *   => end-of-data is reached
      127     DESCRIBE TABLE <l_t_data> LINES l_count.
      128     IF l_count <> i_pkgsize.
      129       e_eof = rs_c_true.
      130     ENDIF.
      131   ENDIF.

    Hi SCHT.
    Error itself says that
    <i>"database accesses producing an excessively large result set,
    - database accesses without a suitable index (full table scan)
    do not block the processing for too long."</i>
    I believe there should be some change in query which causes aggregates to be excluded from selection.
    Try running query from RSRT with option Execute + Debut ->Aggergates section select "Display aggregates found" and see the out put ..and watch whether aggregates are actually used.
    Also some time this error happens because of network traffic , try running query in Bex Analyzer and see the run time.
    Hope that helps.
    Regards
    Mr Kapadia
    Assigning points is the way to say thanks in SDN.

  • Short dump error report

    What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?

    hi please look through this:
    Whenever any transaction or any process is executed it hits an ABAP code.
    If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
    Transaction ST22 is used to check any ABAP Dump within a given duration.
    U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
    you can select back to the last 14 days if you are
    running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
    old ABAP dumps every day, possibly further if you run it weekly or
    monthly.
    sap-basis   sap-basisAll Groups  Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
    SAP Groups > Technical-functional > sap-basis > Message
    About This Group | Invite peers to join this group 
    << Prev thread  < Prev msg  Next msg >  Next thread >> 
    short dump----urgent
    Reply from Keith Lewis on 5/2/2003 3:22:00 AM 
    Good explanation Joy, but it is not only limited to the current day and
    yesterday. If you click on the Selection button you can select previous
    days as well. In fact you can select back to the last 14 days if you are
    running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
    old ABAP dumps every day, possibly further if you run it weekly or
    monthly.
    Cheers
    Keith
    SAP R/3 Support Specialist
    Information Services International
    Tel +44 1664 41 6178 Mobile +44 7887 627818
    E-mail email@removed
    Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
    Dear sreenivas
    If you receive an error message in the R/3 System log (SM21), or if you
    see
    a terminated update in the update service analysis transaction (SM13), or
    DB
    realated error ,check for dumps using the dump analysis transaction
    (transaction ST22), or choose Tools -> Administration -> Monitoring ->
    Dump
    analysis.
    Transaction ST22 enables you to analyze short dumps from the current and
    previous day.
    The dump analysis function shows you:
    What happened
    What you can do
    How to correct the error
    The dump analysis function also provides an error ID and keywords that you
    can use to search in SAPNet, as well as information about:
    The system environment
    Users and transactions
    Transaction ST22 enables you to analyze the following data:
    Date, time, user, client
    Contents of system and data fields
    Contents of internal tables and application tables
    ST22 is a very nice feature in SAP. This is where all the system errors
    and users mistakes showed up. If there is a problem that you cannot
    solve and you contact SAP support, they look at this area to analyze it.
    This gives us lead where to handle the problems.
    Error analysis
    How to correct the error
    System environment
    User, transaction...
    Information on where termination occurred
    Contents of system fields
    Chosen variables
    Active calls / events
    Internal notes
    Active calls in SAP kernel
    List of ABAP programs affected
    List of internal tables
    Directory of application tables (contents)
    Directory of data areas (administration information)
    Directory of data areas (contents)
    ABAP control blocks CONT
    End of runtime analysis
    i think this would be helpful
    regards
    sravani

  • How to fetch n records at a time from a FM and then fetch next n records

    I have a report program which is calling a function module . This function module returns all the records from a table. As the table has millions of records, it cant be returned at a time. How can we return N records from a function module and then return Next n records .The Function module and the report program are in different system .
    Thanks in Advance.

    Use open cursor and fetch cursor.
    Check the program as in SAP Help.
    DATA: BEGIN OF count_line,
            carrid TYPE spfli-carrid,
            count  TYPE i,
          END OF count_line,
          spfli_tab TYPE TABLE OF spfli.
    DATA: dbcur1 TYPE cursor,
          dbcur2 TYPE cursor.
    OPEN CURSOR dbcur1 FOR
      SELECT carrid count(*) AS count
             FROM spfli
             GROUP BY carrid
             ORDER BY carrid.
    OPEN CURSOR dbcur2 FOR
      SELECT *
             FROM spfli
             ORDER BY carrid.
    DO.
      FETCH NEXT CURSOR dbcur1 INTO count_line.
      IF sy-subrc <> 0.
        EXIT.
      ENDIF.
      FETCH NEXT CURSOR dbcur2
        INTO TABLE spfli_tab PACKAGE SIZE count_line-count.
    ENDDO.
    CLOSE CURSOR: dbcur1,
                  dbcur2.
    Regards
    Kannaiah

  • Short dump when trying to Select date in Field

    Hi,
    I created generic data source based on Function Module. I went to RSA3 to test the extraction and I got this error message when I tried to enter a date as input selection in date field or any other selection field
    If I test the extraction without any input I get correct results.
    Whats the reason for this error?
    *Error analysis
       The current ABAP/4 program attempted to execute an ABAP/4 Open SQL
       statement in which the WHERE condition contains an IN itab operator.
       The IN itab operator is used with internal tables which
       have the following structure:
          SIGN(1)   OPTION(2)   LOW LIKE db_field   HIGH LIKE db_field
       The OPTION column should contain only one of the following values:
          "EQ LE GE CP BT NE LT GT NP NB"
    Function module code
    of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
          LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'COMPID'.
            MOVE-CORRESPONDING L_S_SELECT TO rd.
            APPEND rd.
          ENDLOOP.
          LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'SUBSCRIBERS'.
            MOVE-CORRESPONDING L_S_SELECT TO rs.
            APPEND rd.
          ENDLOOP.
          LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'TURNOVER'.
            MOVE-CORRESPONDING L_S_SELECT TO rt.
            APPEND rd.
          ENDLOOP.
          LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'ENTRYDATE'.
            MOVE-CORRESPONDING L_S_SELECT TO re.
            APPEND rd.
          ENDLOOP.
    Determine number of database records to be read per FETCH statement
    from input parameter I_MAXSIZE. If there is a one to one relation
    between DataSource table lines and database entries, this is trivial.
    In other cases, it may be impossible and some estimated value has to
    be determined.
          OPEN CURSOR WITH HOLD S_CURSOR FOR
          SELECT (S_S_IF-T_FIELDS) FROM ZMOBILEDATA
                                   WHERE COMPID  IN rd AND
                                         SUBSCRIBERS  IN rs AND
                                         TURNOVER IN rt AND
                                         ENTRYDATE IN re.
        ENDIF.                             "First data package ?
    Fetch records into interface table.
      named E_T_'Name of extract structure'.
        FETCH NEXT CURSOR S_CURSOR
                   APPENDING CORRESPONDING FIELDS
                   OF TABLE E_T_DATA
                   PACKAGE SIZE S_S_IF-MAXSIZE.
        IF SY-SUBRC <> 0.
          CLOSE CURSOR S_CURSOR.
          RAISE NO_MORE_DATA.
        ENDIF.
    Thanks

    Hi,
    thanks for your input
    Rd, rt,re and rs are ranges.
    Select ranges
      RANGES: rd FOR ZMOBILEDATA-COMPID,
              rs FOR ZMOBILEDATA-SUBSCRIBERS,
              rt FOR ZMOBILEDATA-TURNOVER,
              re FOR ZMOBILEDATA-ENTRYDATE.
    thanks'

  • How to Fetch Cancelled Jobs info along with the Short Dump Text

    Hi Gurus,
    I need to develop a report to fetch the cancelled jobs information for the given period. I also need to display the "Error Analysis" part of the Short Dump if it exists.
    I am able to fetch the Failed Jobs information and the Job log details using the FM "BP_JOBLOG_READ". But I need to show the "Error Analysis Text" on the report , if there is any Short Dump Exists for the Dump.
    Please give me your ideas to fetch the Error Analysis part of the short dump for a given Batch Job Name.
    Thanks in Advance.
    Best Regards,
    Sumalatha

    The dump information is in table SNAP. You could identify which dump you want by the date & time of the failed job - let's hope you don't have more than one dump with the same time. If it is ambiguous you could also compare the program name of the failed step with the program name in the SNAP data.
    The error analysis texts are in table SNAPT keyed according to which error occurred (which is data element code FC right at the start of the first record in the SNAP data). You will have to expand out the includes, and substitute the variable codes using values from the SNAP data. There is standard code to do this that you could copy - see program SAPMS380.
    To find out the details of the SAP process you could run transaction ST22 via the debugger and use the same mechanism.
    best wishes
    Ed
    PS Note these details apply to recent systems I think there may be differences if you go back to before ?2004, but I don't have such a system so can't check. You didn't say what release you have.

  • Short Dump while fetching values from a Database view

    Hi ALL,
    Here is the code that is giving short dump
    SELECT * FROM ZVMATLMOVE INTO TABLE I_MATLMOVE
        WHERE BUDAT >= V_LASTRUN_DATE
        AND   WERKS IN S_WERKS
        AND   LIFNR IN S_LIFNR
        AND   EBELN IN S_EBELN
        AND   MATNR IN S_MATNR
        AND   BWART IN S_BWART
    (Please don't say that I am using * in the select query,
    I knew that it is not a good way of fetching values)
    Declaration of the internal table is:
    DATA  I_MATLMOVE LIKE ZVMATLMOVE OCCURS 0 WITH HEADER LINE.
    The variable V_LASTRUN_DATE is:
    DATA  V_LASTRUN_DATE LIKE SY-DATUM.
    We will be getting the lastrundate value from another table. And it is passing correct value (ex. 20060731)
    ZVMATLMOVE is a database view created for MKPF and MSEG table. And I checked both table were consistent.
    Dump Analysis:
    Runtime errors         DBIF_RSQL_SQL_ERROR          
    Exception              CX_SY_OPEN_SQL_DB
    Every thing is fine. But I don't know how it is going to dump. Any suggestions?

    Hi !
    It seams that your table is not correct / fully activated.
    To check it out you should try the following:
    - Go to the SE11
    - Give it your table name and go to "Display"
    - Check if the table is "active"
    - Choose "Utilities->Database Object->Check" and see
      if there are any errors
    - go back and choose "Utilities->Runtime Object->Check"
      and see if there are any errors
    If there are any errors - try to activate the table again. You may need the "Utilities->Database Utiliy" for that.
    After there are no more errors by checking all these your program should work.
    Regards
    Rainer
    Some points would be nice if thate helped a bit.

  • Short Dump Error DBIF_DSQL2_SQL_ERROR

    Hi All,
    I am getting a Short dump error DBIF_DSQL2_SQL_ERROR when I try to selectively delete the contents of an infocube. Now, we have a custom program that does this selective deletion. I had no problem when I ran this program in Development system. But when I try to do the same in Testing system, I get a short dump error.
    Additional info: We have DB2 for database.
    Thanks,
    Ashmith Roy

    Hi All,
    Thanks for your input. The exact error I am getting is in as follows:
    Runtime Error          DBIF_DSQL2_SQL_ERROR
    Except.                CX_SY_NATIVE_SQL_ERROR
    An SQL error occurred when executing Native SQL.
    Error "-199" occurred in the current database connection "DEFAULT".
    How to correct the error
         Database error text........: "[IBM][CLI Driver][DB2] DSNT408I SQLCODE = -199,
          ERROR: ILLEGAL USE OF KEYWORD FETCH. TOKEN WAS EXPECTED DSNT418I SQLSTATE =
          42601 SQLSTATE RETURN CODE "
         Database error code .......: "-199"
         Triggering SQL statement...: "FETCH NEXT "
         Internal call code.........: "[DBDS/NEW DSQL]"
         Please check the entries in the system log (Transaction SM21).
    Information on where terminated
    The termination occurred in the ABAP program "GP41YKV36E6C2VFC36AKSJQXCD3" in
          "COUNT".
    The termination occurred in line 0 of the source code of the (Include)
    program " "
    of the source code of program " " (when calling the editor 00).
    Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
    occurred in the
    procedure "COUNT" "(FORM)" but was not handled locally, not declared in the
    RAISING clause of the procedure.
    The procedure is in the program "GP41YKV36E6C2VFC36AKSJQXCD3 ". Its source code
    starts in line 0
    of the (Include) program "???".
    So could you please advise as to how to correct the error?
    Ashmith Roy

  • Short dump errors desc--how to resolve

    I would like to know the short dump errors meaning and how to resolve it. i have the following errors
    1. TSV_TNEW_PAGE_ALLOC_FAILE----
    for this the description for ERROR ANALYSIS is : The internal table "IT_24" could not  be enlarged further. To allow error handling, the table has to be deleted before this log was created.HOW TO CORRECT THE ERROR is : the amount of storage space was  (in bytes) filled at termination time was:
    Roll area..........1708928
    Extended memory (EM).........440057520
    Assigned memory (HEAP).......465813648
    short area.........." "
    Paging area.....33857536
    Maximum address space....." "
    2. DBIF_DSQL2_SQL_ERROR----
    HOW TO CORRECT THE ERROR is:
    Database error text......."ORA-01555: snapshot too old: rollback segment number 2 with name "PRS_0" too small"
    Database error code - 1555
    Triggering SQL statement......."FETCH NEXT"
    Internal call code................"[DBDS / NEW DSQL]"               
    Please check the entries in the system log (Trasaction SM21)
    3. TSV_LIN_ALLOC_FAILED----
    this error analysis which also gives HOW TO CORRECT THE ERROR is almost the same like the first error description which i have written like memory space and so on
    i would appreciate if u could clarify these errors and how to resolve it. Thanks in advance.

    Hi,
    TSV_TNEW_* error are the memory problems in BI, you need to wait untill the system load is reduced...check the TA: SM37 and then repeat the failed steps, it will be successful.
    DBIF_* are database releated errors....oracle backend error, u need to find out where the error has occured in the SQL statement and fix the error.
    Usually these errors will the locks.
    Oracle 8i error message says:
    <u><b>ORA-01555</b></u>
    snapshot too old: rollback segment number string with name "string"
    too small
    Cause: Rollback records needed by a reader for consistent read are overwritten
    by other writers.
    Action: Use larger rollback segments.
    Regards,
    Vijay
    Message was edited by:
            Vijaya Kumar Malyavantham

  • Short Dump when deleting CMR/DMR

    Hi,
    When I delete a CMR or DMR the system hangs and I get a Short Dump.  I have traced the line where the dump is occuring, but cannot figure why the error/short dump occurs.
    INCLUDE FV45KFKD_VBKD_FUELLEN_TEIL_2
    FORM VBKD_FUELLEN_TEIL_2 USING VALUE(US_POSNR)
      IF NOT DA_WARNUNG IS INITIAL AND
         SVBKD-TABIX > 0.
        CLEAR DA_WARNUNG.
        IF VBKD-FKDAT EQ DA_FKDAT.
          SET CURSOR FIELD 'VBKD-FKDAT'.
          WRITE VBKD-FKDAT TO DA_DATUMC DD/MM/YYYY.
          MESSAGE W221 WITH DA_DATUMC.  <== The error is occuring when this statement is exceuted.
        ENDIF.
      ENDIF.
    Although the short dump thing the error occurs when trying do the next ste PERFORM VBKD_FUELLEN_IAOM USING US_POSNR.
    Thanks in advance
    Naing

    I would check if you have any code in userexit_check_vbkd for example.
    NOTE: sapmv45a processes not only sales orders but contracts, CMR/DMR,... so please be careful with your code in userexits and make sure you restrict it to proper document types/transactions.
    Ideally you need to write your userexits in such a way that they all can be switched-off easily (like put all code in each userexit between if sy-uname = 'SAPLOOK' ... endif. for example) in this case when you are logged on with SAPLOOK ID - userexits are off.
    The bottom line is - if you are able to perform any action (delete DMR/CMR) when your exits are OFF -> the problem is somewhere in your exits.
    The problem may NOT be in the code where dump occurs, it can be well in advance
    One small flag or incorrect read statement which re-sets workarea of internal table in one of your userexits may cause problems down the line.

  • Short Dump on BAPI_TRANSACTION_COMMIT with destination NONE

    Hi All
    I am using SAP-PM with Compatible Unit(CU) functionality in ECC6 environment.
    After we release the CU design to Generate order we get SHORT DUMP.
    Any help will be of great help.
    I am pasting the details from the dump file here.
    Please let me know.
    Appretaite your help.
    Thanks
    Meghana
    Runtime Errors         CALL_FUNCTION_REMOTE_ERROR
    Date and Time          27.08.2007 18:01:10
    Short text
    "The current application triggered a termination with a short dump."
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "/***/SAPLCUORDER_N" had to be terminated because it
    has
    come across a statement that unfortunately cannot be executed.
    The error occurred during an RFC call to another system.
    In the target system, a short dump has been written as well.
    More detailed information on the error cause can be found there.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An error occurred when executing a REMOTE FUNCTION CALL.
    It was logged under the name "MESSAGE_TYPE_X"
    on the called page.
    How to correct the error
    Please refer to the notes described in the
    short dump.
    System environment
    SAP-Release 700
    Application server... "MB1ES1005"
    Network address...... "10.191.97.206"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x Intel 801586"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 3
    Shortdump setting.... "full"
    Database server... "MB1ES1005"
    Database type..... "ORACLE"
    Database name..... "EC6"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Jul 25 2007 00:57:05"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10201_SHARE (10.2.0.1.0) "
    Patch level. 121
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0"
    Memory consumption
    Roll.... 8176
    EM...... 14633136
    Heap.... 0
    Page.... 131072
    MM Used. 5005432
    MM Free. 1263944
    User and Transaction
    Client.............. 200
    User................ 10086330
    Language key........ "E"
    Transaction......... "/***/DESIGN "
    Transactions ID..... "409954DC5D77F1C58E2D0013725D3B3B"
    Program............. "/***/SAPLCUORDER_N"
    Screen.............. "/***/SAPLCUORDER_N 2000"
    Screen line......... 34
    Information on where terminated
    Termination occurred in the ABAP program "/***/SAPLCUORDER_N" - in
    "SAVE_DESIGN".
    The main program was "/***/SAPLCUORDER_N ".
    In the source code you have the termination point in line 594
    of the (Include) program "/***/LCUORDER_NF07".
    Source Code Extract
    Line
    SourceCde
    564
    ENDIF .
    565
    ENDLOOP .
    566
    IF l_ret-type = 'E' OR
    567
    l_ret-type = 'A' .
    568
    CLEAR: save_okcode .
    569
    570
    Show Messages
    571
    CALL FUNCTION '/***/N_LOG_ADD_MSG'
    572
    EXPORTING
    573
    i_log_type = 'G'
    574
    TABLES
    575
    t_ret      = t_ret.
    576
    PERFORM log_order_create_show  .
    577
    Show first Message
    578
         MESSAGE ID l_ret-id TYPE l_ret-type NUMBER l_ret-number
    579
         WITH
    580
           l_ret-message_v1 l_ret-message_v2
    581
           l_ret-message_v3 l_ret-message_v4.
    582
    CALL FUNCTION '/***/N_DESIGN_INIT' .
    583
    ELSE .
    584
    IF g_design_mode = con_mode_crea.
    585
    Need to update DMS documents with real design number
    586
    PERFORM document_prepare_002 USING con_desnum_tmp_1
    587
    lv_desnum.
    588
    ENDIF.
    589
    Commit design BAPI's
    590
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
    591
    592
    IF save_okcode = con_order.
    593
    Commit order BAPI's
    >>>>>
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    595
    DESTINATION 'NONE'.
    596
    597
    call of fct. RFC_CONNECTION_CLOSE is important to get a new
    598
    initial roll area with initial internal tables next time
    599
    CALL FUNCTION 'RFC_CONNECTION_CLOSE'
    600
    EXPORTING
    601
    destination          = 'NONE'
    602
    EXCEPTIONS
    603
    destination_not_open = 1
    604
    OTHERS               = 2.
    605
    ENDIF.
    606
    607
    IF lv_desnum IS INITIAL .
    608
    lv_desnum = /***/cudesign-desnum .
    609
    ENDIF .
    610
    SET PARAMETER ID '/***/DESNUM' FIELD lv_desnum .
    611
        Changes saved
    612
    MESSAGE ID '/***/MSG' TYPE 'S' NUMBER '529' WITH lv_desnum .
    613
    ENDIF .
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    2000
    SY-UCOMM
    CU01
    SY-TITLE
    Change Design: 50000109
    SY-MSGTY
    X
    SY-MSGID
    00
    SY-MSGNO
    341
    SY-MSGV1
    MESSAGE_TYPE_X
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20070827
    SY-UZEIT
    180110
    SY-XPROG
    SAPMSSY1
    SY-XFORM
    XAB_READ
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    4 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                    594
    SAVE_DESIGN
    3 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                   2616
    CHECK_AND_SAVE_F07
    2 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF04                    311
    USER_COMMAND_D2000
    1 MODULE (PAI) /***/SAPLCUORDER_N                  /***/LCUORDER_NI05                     28
    USER_COMMAND_2000
    Chosen variables
    Name
    Val.
    No.       4 Ty.          FORM
    Name  SAVE_DESIGN
    %_DUMMY$$
    2222
    0000
    0000
    0000
    CL_GUI_RESOURCES=>COL_TEXTAREA
    31
    1000
    F000
    G_DESIGN_MODE
    R
    5
    2
    0
    0
    CON_MODE_CREA
    I
    4
    9
    0
    0
    GT_NODE_CUI
    Table[initial]
    SY-REPID
    /***/SAPLCUORDER_N
    2454254544545445542222222222222222222222
    F35DF310C35F2452FE0000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    CON_DESNUM_TMP_1
    TM00000001CY
    543333333345
    4D0000000139
    000000000000
    000000000000
    LV_DESNUM
    222222222222
    000000000000
    000000000000
    000000000000
    SAVE_OKCODE
    CU01
    4533222222222222222222222222222222222222222222222222222222222222222222
    3501000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    CON_ORDER
    CU01
    4533222222222222222222222222222222222222222222222222222222222222222222
    3501000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    SY-XPROG
    SAPMSSY1
    5454555322222222222222222222222222222222
    310D339100000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    CON_DELETE
    LVMS
    4545222222222222222222222222222222222222222222222222222222222222222222
    C6D3000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    No.       3 Ty.          FORM
    Name  CHECK_AND_SAVE_F07
    CL_GUI_ALV_GRID=>MC_MB_VIEW
    &MB_VIEW
    2445544522222222222222222222222222222222222222222222222222222222222222
    6D2F695700000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    GT_OP
    Table IT_303[2x1320]
    PROGRAM=/***/SAPLCUORDER_NDATA=GT_OP
    Table reference: 118
    TABH+  0(20) = 7039FC3C5824DB3C00000000760000002F010000
    TABH+ 20(20) = 0200000028050000FFFFFFFF0400000030140000
    TABH+ 40( 8) = 08000000C1308001
    store        = 0x7039FC3C
    ext1         = 0x5824DB3C
    shmId        = 0     (0x00000000)
    id           = 118   (0x76000000)
    label        = 303   (0x2F010000)
    fill         = 2     (0x02000000)
    leng         = 1320  (0x28050000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000093
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x2010FC3C
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 234   (0xEA000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 8     (0x08000000)
    lineAlloc    = 8     (0x08000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x60B7153D
    collHook     = 0x00000000
    ext2         = 0x1024DB3C
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xE00FFC3C
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    G_BADI_PROGRAM
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    LOG_ERROR
    2
    0
    0
    0
    CON_BUTT_DELETED
    @11QDelete@
    43355466676422222222222222222222222222222222
    011C145C545000000000000000000000000000000000
    00000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000
    G_CU_EXIT_CU_EXPLODE
    F0000000
    F0000000
    /***/CUDESIGN-OBJNR
    CY00000000000000008835
    4533333333333333333333
    3900000000000000008835
    0000000000000000000000
    0000000000000000000000
    CL_GUI_RESOURCES=>COL_TEXTAREA
    31
    1000
    F000
    G_SEC_COUNT
    0
    0000
    0000
    LV_UPD
    X
    5
    8
    0
    0
    %_SPACE
    2
    0
    0
    0
    GS_ROW_NO
    0.0.0.1.
    0000
    1000
    0000
    0000
    SCREEN
    /***/CUDESIGN-GLTRP
    2454245445444244555222222222222222222222222222222222222222222222222222222222222222222222222222
    F35DF3545397ED7C420000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY-MSGID
    00
    33222222222222222222
    00000000000000000000
    00000000000000000000
    00000000000000000000
    SWO_%CONTAINER
    000000000
    2222222222222222222222222222222233333333322222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SPACE
    2
    0
    0
    0
    SY-MSGNO
    341
    333
    341
    000
    000
    /***/CVCUI-CUTYP
    2
    0
    0
    0
    SY-MSGV1
    MESSAGE_TYPE_X
    44554445555455222222222222222222222222222222222222
    D533175F4905F8000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    No.       2 Ty.          FORM
    Name  USER_COMMAND_D2000
    /***/CVCUI
    0.0.0.0.0.0.0.1.                                                                         000000
    2220000000022222222222222222222222222222222222222222222222222222222222222222222222223333332222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST-REPID
    /***/SAPLCUORDER_N
    2454254544545445542222222222222222222222
    F35DF310C35F2452FE0000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    CON_MODE_COPY
    C
    4
    3
    0
    0
    LT_BAPI_RETURN
    Table IT_1778[2x1088]
    PROGRAM=/***/SAPLCUORDER_NFORM=USER_COMMAND_D2000DATA=LT_BAPI_RETURN
    Table reference: 310
    TABH+  0(20) = 8837083D407E1C3D0000000036010000F2060000
    TABH+ 20(20) = 0200000040040000FFFFFFFF04000000F0170000
    TABH+ 40( 8) = 08000000C1308101
    store        = 0x8837083D
    ext1         = 0x407E1C3D
    shmId        = 0     (0x00000000)
    id           = 310   (0x36010000)
    label        = 1778  (0xF2060000)
    fill         = 2     (0x02000000)
    leng         = 1088  (0x40040000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000113
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 1
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x50C6073D
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 1534  (0xFE050000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 8     (0x08000000)
    lineAlloc    = 8     (0x08000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0x6067033D
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xE82F063D
    delta_head   = 0000000000000000CF000000000000000400000020180000000000004D00430055004F000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    CON_MODE_ORDE
    O
    4
    F
    0
    0
    TGSBT
    22222222222222222222222222222222222222
    00000000000000000000000000000000000000
    00000000000000000000000000000000000000
    00000000000000000000000000000000000000
    CL_GUI_RESOURCES=>COL_TEXTAREA
    31
    1000
    F000
    LS_NUMBERS-AUFNR_NEW
    000001000677
    333333333333
    000001000677
    000000000000
    000000000000
    T024I
    200UT10100PG for Term & Comp
    33355333335426672567622246672222222222222222
    20054101000706F20452D0603FD00000000000000000
    00000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000
    LS_T399X
    200UT10UM01                  X    INST  30UT01UT01
    3335533543322222222222222222252222445522335533553322222222222222222222222222222222222222222222
    20054105D01000000000000000000800009E3400305401540100000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    CON_VBKZ_U
    U
    5
    5
    0
    0
    /***/CU_ORDER_IO-DISP_FACTOR
    2097152
    0
    0
    LS_DESIGN
    200########000050000109DDCY00000000000000008835PROFILE1  0001UT10UM0100220100MWH001
    333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
    200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
    000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
    /***/CUDESIGN
    200########000050000109DDCY00000000000000008835PROFILE1  0001UT10UM0100220100MWH001
    333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
    200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
    000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
    G_DROP_COUNT
    0
    0000
    0000
    LS_DESIGN-DESNUM
    000050000109
    333333333333
    000050000109
    000000000000
    000000000000
    No.       1 Ty.          MODULE (PAI)
    Name  USER_COMMAND_2000
    GT_SELTAB_INIT
    Table[initial]
    Internal notes
    The termination was triggered in function "RfcExtendedReceive"
    of the SAP kernel, in line 422 of the module
    "//bas/700_REL/src/krn/rfc/abrfcrcv.c#4".
    The internal operation just processed is "FUNC".
    Internal mode was started at 20070827180011.
    Status of connection:
    RFC state: " "
    RFC error text: "RFC_ERROR_SYSTEM_FAILURE"
    CPI-C error text: "The current application triggered a termination with a short
    dump."
    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=26488)
    When      : 8/27/2007 18:1:10.942
    Threads   : 2
    Computer Name       : MB1ES1005
    User Name           : ec6adm
    Number of Processors: 2
    Processor Type: x86 Family 15 Model 4 Stepping 10
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id 5e10
    eax=000f93c0 ebx=0000042c ecx=00003118 edx=00000000 esi=0000042c edi=00000000
    eip=7c82ed54 esp=056d71f0 ebp=056d7260 iopl=0         nv up ei ng nz ac po cy
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00200297
    function : KiFastSystemCallRet
    7c82ed54 c3               ret
    7c82ed55 8da42400000000   lea     esp,[esp]              ss:056d71f0=7c822124
    7c82ed5c 8d642400         lea     esp,[esp]              ss:62bd5803=00000000
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    056d7260 77e6ba42 0000042c 0001d4c0 00000000 056d7298 ntdll!KiFastSystemCallRet
    056d7274 0109504d 0000042c 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
    056d7298 00582118 00582151 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess  (ntstcdbg.c (501))
    056d729c 00582151 7c38b5c8 7c38b5c8 7c38b5c8 01e9b1b8 disp+work!NTStack  (dptstack.c (1367))
    056d72b8 00582185 7c38b5c8 00000000 008b7ec8 7c38b5c8 disp+work!CTrcStack2  (dptstack.c (352))
    056d72c4 008b7ec8 7c38b5c8 00000000 005f0059 00330030 disp+work!CTrcStack  (dptstack.c (182))
    056d72e8 008bb39f 00711076 056d8018 056d7be8 00200020 disp+work!rabax_CStackSave [abrabax.c (7063)
    056d7b90 009eca8b 020b9e4c 020b9e14 000001a6 5d88acf0 disp+work!ab_rabax  (abrabax.c (1243))
    056d7bcc 009ed19e 00000003 00711076 00000020 00000000 disp+work!rcv_message  (abrfcrcv.c (422))
    056d8068 009ed29d 00000003 00000000 00710c47 056d80c0 disp+work!RfcExtendedReceive [abrfcrcv.c (14
    056d808c 00714873 00000003 00710c47 056d80c0 00711076 disp+work!ab_rfcreceive  (abrfcrcv.c (59))
    056d80e4 0071886b 2694a7c8 2694a7cc 2694a7cc 2694a7cc disp+work!jfunc_get  (abfunc.c (5103))
    056d89f4 007191d0 00000003 000000b4 00000000 05e8b7c0 disp+work!jfunc_nonstandard [abfunc.c (1655)
    056dcfb0 006e3e2d 00000003 3ced8f90 00000000 056dd018 disp+work!ab_jfunc  (abfunc.c (554))
    056dd018 0081cb5e 00000000 3ced8f90 056dd164 3cedb514 disp+work!ab_extri  (abextri.c (552))
    056dd02c 00897dbd 00000000 3cedae46 005bf4cd 3ceda13c disp+work!ab_xevent  (abrunt1.c (281))
    056dd038 005bf4cd 3ceda13c 000000ea 3cedae46 00000000 disp+work!ab_dstep  (abdynpro.c (492))
    056dd164 005c25be 3ced8f90 3ced8f90 056dfc78 00000000 disp+work!dynpmcal  (dymainstp.c (2398))
    056dd178 005c1def 00000001 3ced8f90 00000003 056dfc78 disp+work!dynppai0  (dymainstp.c (1004))
    056dd194 00595e69 3ced8f90 00000001 00000001 00000001 disp+work!dynprctl  (dymainstp.c (360))
    056dfcec 00490e06 00000004 0049d15f 00000004 01dadd00 disp+work!dynpen00  (dymain.c (1628))
    056dfcf4 0049d15f 00000004 01dadd00 00000003 00000002 disp+work!Thdynpen00  (thxxhead.c (4773))
    056dfee0 0049d6d6 00000001 00000000 00000000 00430000 disp+work!TskhLoop  (thxxhead.c (4455))
    056dff00 00421c36 00000000 00000000 7ffde000 056dff60 disp+work!ThStart  (thxxhead.c (1173))
    056dff14 00401080 00000003 05876980 00000001 00000000 disp+work!DpMain  (dpxxdisp.c (1121))
    056dff60 01242970 00000003 05876980 05877a10 01cce000 disp+work!nlsui_main  (thxxanf.c (82))
    056dffc0 77e523e5 00000000 00000000 7ffde000 8967f020 disp+work!wmainCRTStartup  (crtexe.c (395))
    056dfff0 00000000 0124282d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
    State Dump for Thread Id 61fc
    eax=00000000 ebx=00000103 ecx=0587a700 edx=02714360 esi=00000000 edi=00000000
    eip=7c82ed54 esp=0799fec0 ebp=0799ff04 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:0799fec0=7c821514
    7c82ed5c 8d642400         lea     esp,[esp]              ss:64e9e4d3=00000000
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    0799ff04 0119030a 000006e0 00000000 00000000 0587a798 ntdll!KiFastSystemCallRet
    0799ff84 7c349565 00000000 00000000 00000000 0587a700 disp+work!SigIMsgFunc  (signt.c (610))
    0799ffb8 77e6608b 0587a700 00000000 00000000 0587a700 MSVCR71!endthreadex
    0799ffec 00000000 7c3494f6 0587a700 00000000 00000000 kernel32!GetModuleFileNameA
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    /***/SAPLCUORDER_N
    0
    10.08.2007
    10:12:44
    541696
    E
    1
    Typ
    /***/CUDESIGN
    0
    10.08.2007
    10:05:19
    7168
    2
    Typ
    /***/CU_ORDER_IO
    0
    10.08.2007
    09:53:38
    4096
    3
    Typ
    /***/DESTYPE
    0
    10.08.2007
    10:05:21
    2048
    4
    Typ
    /***/PRF_ORD
    0
    10.08.2007
    10:05:21
    4096
    5
    Prg
    SAPMSSYD
    0
    04.04.2007
    10:28:36
    21504
    E
    6
    Prg
    SAPFSYSCALLS
    0
    09.09.2004
    14:18:32
    8192
    E
    7
    Typ
    /***/G_CUST
    0
    10.08.2007
    09:53:39
    3072
    8
    Prg
    /***/SAPLTABLES
    8
    10.08.2007
    10:13:00
    19456
    E
    9
    Typ
    /***/G_CHAR
    0
    10.08.2007
    10:05:21
    3072
    10
    Prg
    SAPLCTCE
    10
    09.09.2004
    14:18:34
    9216
    E
    11
    Typ
    CABN
    0
    18.09.2001
    10:02:26
    12288
    12
    Prg
    SAPLICON
    12
    04.04.2007
    10:10:28
    27648
    E
    13
    Prg
    %_CICON
    12
    07.02.2006
    10:40:00
    104448
    E
    14
    Typ
    ICONT
    0
    04.04.2007
    10:10:08
    2048
    15
    Typ
    NRIV
    0
    02.04.1998
    08:14:54
    3072
    16
    Prg
    SAPLBSVA
    16
    04.04.2007
    14:47:00
    296960
    E
    17
    Typ
    /***/CU_ORDER_S_OP_N
    0
    10.08.2007
    09:53:39
    14336
    18
    Prg
    CL_GUI_CONTROL================CP
    18
    28.02.2005
    21:03:09
    112640
    E
    19
    Prg
    %_CCNTL
    18
    18.02.2005
    14:15:08
    15360
    E
    20
    Typ
    OBJ_RECORD
    0
    14.02.1998
    08:30:43
    2048
    21
    Prg
    CL_GUI_OBJECT=================CP
    21
    05.07.2005
    13:10:15
    375808
    E
    22
    Prg
    CL_GUI_CFW====================CP
    22
    28.02.2005
    21:03:09
    172032
    E
    23
    Prg
    CL_GUI_PROPS_CONSUMER=========CP
    23
    18.02.2005
    14:15:08
    30720
    E
    24
    Prg
    SAPLTHFB
    24
    04.04.2007
    13:24:38
    390144
    E
    25
    Typ
    EUDB
    0
    06.11.2003
    20:28:08
    8192
    26
    Prg
    SAPLSFES
    26
    08.08.2007
    16:46:17
    259072
    E
    27
    Prg
    SAPLSPLUGIN
    27
    09.09.2004
    14:18:36
    8192
    E
    28
    Prg
    SAPLSTTM

    Yes even i find it strange. But there is no syntax error and the fact is that it was working 2 days back.  Suddenly it has started giving us this dump.
    The code is as follows.
    Commit design BAPI's
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
          IF save_okcode = con_order.
    Commit order BAPI's
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
              DESTINATION 'NONE'.
    Here con_order is CU01.
    Please let me know if anybody has faced this problem earlier.
    Thanks in Advance
    Meghana

Maybe you are looking for

  • Can't Open System Preferences...

    Hello, I have had my Macbook since early Sept. and so far I'm a big supporter! Everything runs great and I haven't had any trouble until now. Recently though, I noticed that I can't open the 'System Preferences' on this machine. When I click on it un

  • How to make my iTunes Library use the music which is already on my NAS?

    Hi there, I know there have already been some posts around the forum about having the iTunes library on external harddrives or NAS's. Though my question is different to that question and the solution for those can't seem to cater for my issue. In the

  • How to transfer GB music file from iPad to iMac?

    Hello to all! Have created a music file on my iPad Mini and am unable to transfer it to my iMac through AirDrop. With WiFi and Bluetooth on for both, the iMac first shows being connected and then shows not connected to the iPad...stating that it is n

  • Connecting the Touch to my Element???

    I connect my Touch to my Element's stereo using a cord that plugs into the AUX on the car, and the headphone jack on the Touch. When I'm listening to it, I set the volume on the Touch to almost all the way up, and then have to turn the volume on the

  • Java 1.5 on Mac G5, Leopard 10.5.8

    Just installed Britannica Ultimate Reference Suite 2010 DVD (encyclopedia), but it won't start apparently due a Java issue. I have the latest MacOS which is able to run on PowerPC machines (Leopard 10.5.8) I have the latest Apple software upgrade ins