Short Dump Error in deleting the Init request

Hi Gurus,
  i am loading master data from sap r3 by init update.
now due to some requirement i have to delete the init request , but when i try to delete the request
it goes to short dump and gives the error message as
Runtime Errors         MESSAGE_TYPE_X
Date and Time          01/05/2009 01:54:15
Short text
     The current application triggered a termination with a short du
What happened?
     The current application program detected a situation which real
     should not occur. Therefore, a termination with a short dump wa
     triggered on purpose by the key word MESSAGE (type X).
Error analysis
     Short text of error message:
     Error when opening an RFC connection
     Long text of error message:
     Technical information about the message:
     Message class....... "RSAR"
     Number.............. 051
     Variable 1.......... "Error when opening an RFC connection"
     Variable 2.......... " "
     Variable 3.......... " "
     Variable 4.......... " "
     Last error logged in SAP kernel
     Component............ "SAP-Gateway"
     Place................ "SAP-Gateway on host sapdev / sapgw00"
     Version.............. 2
     Error code........... 631
     Error text........... "max no of gateways exceeded (100)"
     Description.......... " "
     System call.......... " "
     Module............... "gwxxrd.c"
     Line................. 8438
     The error reported by the operating system is:
     Error number..... " "
     Error text....... " "
Trigger Location of Runtime Error
    Program                                 SAPLRSSM
    Include                                 LRSSMF03
    Row                                     1,627
    Module type                             (FORM)
    Module Name                             DEL_SOURCE_SYSTEM_INIT
1624           communication_failure = 1  message l_msg_text
1625           system_failure        = 2  message l_msg_text.
1626       if sy-subrc <> 0.
>>>>>         message x051(rsar) with l_msg_text(50) l_msg_text+50(50) '' ''.
1628       endif.
Please help me on this as untill it will not be deleted, I will be unable to load the data.
suitable answer will get Full points.
Thanks.

Hi Saurabh,
PLEase go through these notes:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cst/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383837393039%7d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cst/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383934313030%7d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cst/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393738303738%7d

Similar Messages

  • Short Dump Error while executing the DTP

    Hello Experts,
    I am facing an issue with DTP.
    Data has been loaded to PSA successfully but while executing the DTP for loading from PSA to DSO (WO) throwing a short dump RAISE_EXCEPTION.
    Short text
        Exception condition "NO_DS_LG_FOUND" raised.
    "RAISE_EXCEPTION" " "
    "SAPLRSSTATMAN" or "LRSSTATMANU1
    "RSSTATMAN_GET_PARTTAB_PSA"
    or
    "SAPLRSSTATMAN" "NO_DS_LG_FOUND"
    or
    "RSAWBN_START " "NO_DS_LG_FOUND"
    We are on BI support pack 14 SAPKW70014, searched for OSS notes but there are few for SP 12/ 13.
    Did any body faced the simlliar issues,,,, please help
    Appreicate your quick response.

    You may wish to check this
    Note 1083305 - P16:STATMAN:Dump in function module RSM_INFOCUBE_WRITE_CHECK
    Hope it Helps
    Chetan
    @CP..

  • Short dump error when using count(*)

    Hi Experts
    I am getting a short dump error when selecting the records >= current date - 30 see the coding and comment please correct the coding I want to know the ztable records it is important for command interface.
    I have 1402345 records available after deleting the records but as the memory is not enough it is giving short dump error
    select count(*) from ZINT_TABLE
    select count(*) from ZINT_MSGS
       select * from zint_data
                 nto table izint_d2 . "PACKAGE SIZE 20000
       where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
    endselect.**
    report z_eslp_command_records.
    data: cnt type i.
    data: cnt2 type i.
    data: cnt3 type i.
    data: cnt4 type i.
    DATA:
         w_date1 like sy-datum .
    DATA:
         w_date2 like sy-datum.
    data: izint_msgs type table of zint_msgs.
    data: izint_data type table of zint_data.
    data: izint_m2 type table of zint_msgs.
    data: izint_d2 type table of zint_data.
    INITIALIZATION.
    w_date1 = sy-datum -  30.
    w_date2 = sy-datum -  30.
    select * from zint_data
                 into table izint_data PACKAGE SIZE 3000
                 where STATUS = 'OK' AND CREATED_ON <= w_date1.   " ZERO
    endselect.
    select * from zint_msgs
                 into table izint_msgs  PACKAGE SIZE 3000
                  where  CREATED_ON <= w_date2.              " ZERO
    endselect.
      select * from zint_data
                 into table izint_d2 PACKAGE SIZE 20000
       where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
    endselect.
    select * from zint_msgs
                 into table izint_m2 PACKAGE SIZE 20000
      where CREATED_ON >= w_date2.                            " VALUE
      endselect.
    select * from zint_data
                into table izint_data2
    where STATUS = 'OK' AND CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
    ENDSELECT.
      select * from zint_msgs
                into table izint_msgs2
    where CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
    ENDSELECT.
    sort izint_data by created_on ascending.
    sort izint_msgs by created_on ascending.
    sort izint_d2 by created_on ascending.
    sort izint_m2 by created_on ascending.
    describe table izint_data lines cnt.
    describe table izint_msgs lines cnt2.
    describe table izint_d2 lines cnt3.
    describe table izint_m2 lines cnt4.
    write:/ ' Note: THE RECORDS COUNTED SHOULD SHOW ZERO ELSE THE SCRIPT FAILED TO RUN' color 3.
    skip.
    write:/ '1. Records counted in ZINT_DATA   <=current date - 30                   :' color 2,                        cnt color 4.
    write:/ '2. Records available in ZINT_DATA >=current date - 30                   'color 4,                   cnt3 color 4 .
    skip.
    write:/ '2. Records counted in ZINT_MSGS   <=current date - 30                   :' color 2                 ,                      cnt2 color 4.
    write:/ '4. Records available in ZINT_MSGS >=current date - 30                   'color 4  ,            cnt4 color 4 .
    TOP-OF-PAGE.
    WRITE:/55(60) ' WAGNERS INVESTMENT LIMITED  '.
    WRITE:/50(40) ' Command Interface Data' CENTERED .
      WRITE:/50(40) '----
    ' CENTERED .
      FORMAT INTENSIFIED ON.
      SKIP.
      "FORMAT COLOR COL_HEADING.
      ULINE.
      FORMAT COLOR 1.
    END-OF-PAGE.

    Answer

  • Short dump error DBIF_RSQL_TABLE_UNKNOWN

    Hi Experts,
    We are using a job having program "ATPBD001" to Refresh the buffer. Yesterday this job failed with the short dump error
    DBIF_RSQL_TABLE_UNKNOWN.
    The message is coming like " One of the tables in the statement accessing table "ATP_RESB " is unknown ".
    Today the same job run successfully. what could be the possible root cause of the error ?
    Here is the source code for reference :
    004370                     atp_resb-sobkz = sobkzk
    004380   *}   INSERT
    004390               CLEAR atp_resb-sobkz.
    004400   *           checks
    004410               resb_check atp_resb
    004420                          p_atpmex.
    004430             ENDSELECT.
    004440           ENDIF. " IF  NOT g_t441v-skbdp IS
    004450
    004460         ENDIF. " IF  s_index_flg = swoff.
    004470       ELSE.
    004480         SELECT *
    004490         FROM   atp_resb
    004500         INTO   atp_resb
    004510         WHERE  matnr = atpmat-matnr
    004520         AND    werks = atpmat-werks
    004530         AND    xloek = space
    004540         AND    kzear = space
    004550   *{   REPLACE        PA8K040916
    004560   *\      AND    sobkz IN (space, sobkzk)
    004570   *XFO 16.12.2005 H908220 wrong ATP for spe
    004580   *(del)      AND    sobkz IN (space, sobkz
    004590   *}   REPLACE
    004600         AND    bdmng > atp_resb~enmng
    004610         AND    txtps = space
    004620         AND    schgt = space
    004630         AND    dbskz = space
    004640         AND  ( vorab IS NULL
    >             OR vorab = space ).
    004660   *{   INSERT         PA8K040916

    Check noe 950317.
    rob

  • Short dump error DBIF_RSQL_INVALID_CURSOR

    Hi
    From Past few days, I am facing a peculiar issue
    I am getting a short dump when the batch run to load to the Infocubes(Full Load). The load runs fine ones I deletes the failed request and load again.
    The short dump and the exception are as below
    Name of runtime error     DBIF_RSQL_INVALID_CURSOR
    Exception     CX_SY_OPEN_SQL_DB
    I have also checked with the basis team and no indication of a failure within SAP (no errors suggesting time-outs, buffers filling, tables filling etc)
    Kindly let me know what could be root cause

    Hi Pavan,
    Are you trying to load the infocube from a DSO.We had the same issue whlle loading a cube from DSO and OSS note 339080 solved our issue.In case you are not able to access the note,find below the cause and solution provided in the note for this issue.
    Cause and prerequisites
    Customizing: the number of parallel processes for sending data was set to 0 in the ROIDOCPRMS table. For this reason, the system uses the process, in which the extraction takes place, for sending the data. A 'commit work' is performed in the sending process which causes an interruption of the running database selection in the extraction process.
    Solution
    Set the parameter 'maximum processes' in the ROIDOCPRMS table (or of the ROIDOCPRMS maintenance view) to a value> 0 for its connection with the BW.
    Regards,
    Bhagyarekha.

  • Short Dump Error While Data load

    Hi Experts,
    Data load to an ODS in production server has been failed because of Short dump error. The error message shows " OBJECTS_OBJREF_NOT_ASSIGNED ".
    Request you to please help me out with a solution ..
    Regards,
    Vijay

    Hi Vijay,
    follow the steps below (May Help you)
    Goto Monitor screen>Status Tab> using the wizard or the menu path >Environment -> Short dump> In the warehouse
    Select the Error and double click
    Analyse the error from the message.
    1.-->Go to Monitor
    -->Transactional RFC
    -->In the Warehouse
    -->Execute
    -->EDIT
    -->Execute LUW
    Refresh the Transactional RFC screen and go to the Data Target(s) which have failed and see the status of the Request-->Now it should be green.
    2.In some cases the above process will not work (where the Bad requests still exists after the above procedure).
    In that case we need to go to the Data Targets and need to delete the bad requests and do the update again
    Regards,
    BH

  • 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

  • Short Dump Error

    Hi Everyone,
    I'm loading 690k odd records to cube
    I am facing short dump error while data request is processed to cube.
    In ST22 i'm getting Timeout Error.
    Buffer time is set for 10mins to process
    Can  anyone guide me in this issue.
    Thanks in advance

    Hi,
    Due to data volume your load took more than 7hrs. in general time out time is 7hrs. so in your case its may exceeded.
    Try to increase time out time for your info package.
    Go to your info pack--> menu scheduler --> time out time--> increase 7 hrs to 14hrs and trigger your load again. if its full load delete failed load and retrigger.
    Thanks

  • Short dump error when extracting delta records from R/3

    I am working on BW 3.5 and I am facing some short dump error when extracting delta records from the r/3 to BW.
    Below is the error message
    Kindly do the needful ASAP.
    Job started
    Step 001 started (program SBIE0001, variant &0000000024277, user ID BWREMOTE)
    Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
    DATASOURCE = 0ISCM_PAYMENT_01
             Current Values for Selected Profile Parameters               *
    abap/heap_area_nondia......... 2000000000                              *
    abap/heap_area_total.......... 2000000000                              *
    abap/heaplimit................ 40000000                                *
    zcsa/installed_languages...... DE                                      *
    zcsa/system_language.......... E                                       *
    ztta/max_memreq_MB............ 2047                                    *
    ztta/roll_area................ 6500000                                 *
    ztta/roll_extension........... 2000000000                              *
    2,454 LUWs confirmed and 2,454 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DAT
    ABAP/4 processor: MESSAGE_TYPE_X
    Job cancelled

    Hi,
    I look at the transaction ST22 to see which type of error has given you. Take a look at the notes to correct the error.
    Another option is to look at OSS notes, because the error is giving you a standard extractor.
    Greetings,

  • 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

  • How to delete the open requests in the LBWQ

    Hi guys ... Can any one let me know how to delete / update the open requests in the queue . I need to delete the Open requests in the LBWQ...we are applying patches and for that we need to delete from LBWQ and RSA7...I guess there is an ABAP report which will deletes the open requests...Can any one let me know that report name please
    Thanks in advance...
    regards
    Edited by: sam on Dec 17, 2007 6:15 PM

    If your job control runs fine then best thing is to transfer the records from LBWQ to RSA7 and pull it to BW. If you do this all your delta data is intact and you do not loose any delta data. But if you delete the LBWQ you potentially loose all youre delta data. You can go to LBWE and start the job control and move data to RSA7 and then pull it to BW.
    But i am not very clear why you wish to delete this data ? If you do this then better you reinitialize all your delta data by following your normal procedure of filling up the setup tables and then initalizing in BW.

  • How to delete the compressed Request ID in the info cube... ?

    Hi BW Gurus,
    one of the info package will upload the request in to three data targets and failed due to error with duplicate records.  I am able to delete the bad request in two data targets and facing problem with one data target due to the request is available in green and got compressed. 
    The reasons why i am unable to delete the request in that data target is it is already got compressed and rolledup.
    I tried with selective deletion based on same request ID  i have done that successfully but the request still presents in the data target.  I have checked in listcube and found no data for the request id.
    now i have one more question like the request has bring down to status not ok in the monitor and done selective deletion will it be a problem on the data missing please advise me if any data missing will occur for the particular data target.
    can any one help on this. Thanks in Advance.
    Venkat.

    Hi Venkat
    You have one way to delete the compressed request
    But this is possible only if u have the request in PSA
    If the request is in PSA, do reverse posting
    This will nullify the particular bad request by changing the press sign into - and - sign into + for all the records went in the cube for that particular request
    Regards
    N Ganesh

  • How to delete the Transport Request?

    Hi all,
       I want to delete the Transoport Request from Production Box( we have 2 request number... one child another one parent). I released the Child Request. Now i want to delete that request. we don't have setup in our production Box i think(in order to release that we don't have setup in Production Box).
    Any Idea? I know how to delete that Transport Request. If i try to release that i'm getting TP(Transport Profile error) <b>with return Code 12</b>. it suppose to handle by Basis. My basis consultant is not aware of how to work on this?
    Regards,
    Nagesh Ganisetti.

    I am not sure I understand.
    You release the request in the system you created, not in another system (in your case production). It will then go to the import queue of the target system.
    Transports will be configured in all the systems in your landscape (including production).
    Just by releasing a request, it will not go to the target (unless it is configured so, not likely if the target is production), someone has to import it into the target. I assume you do not want this request to go to target. In this case, release it, then go to STMS, import queue, and delete it from there.
    Added -
    I now see that the request is in production.
    Igore the above in that case.
    If you are not able to release it, let it be. If you are doing an upgrade/support pack, you will need to release it.
    When you try to delete, what message do you get?
    Message was edited by: Ajay Das

  • Short Dump error while loading data from R/3 to ODS

    Hello,
    while trying to load data into the ODS from R/3 I get the following short dump error message. How do I carry out step 1 in the below procedure. Where do i find the Activate Function. And idea?
    Thanks,
    SD
                                                                                    Diagnosis                                                                               
    Form routine CONVERT_ITAB_RFC is incorrect in transfer program         
         GP4C0LOLZ6OQ70V8JR365GWNW3K .                                                                               
    System Response                                                                               
    The IDoc processing was terminated and indicated as incorrect. The IDoc
         can be reimported at any time.                                                                               
    Procedure                                                                               
    1.  Go to the transfer rule maintenance for your InfoSource               
             ZFIN_TR_FLQITEM_FI and the source system DA_M_10 and regenerate the   
             transfer program using the function Activate. Remove possible syntax  
             errors on the basis of your conversion routines.                                                                               
    2.  Restart the processing of this IDoc.                                                                               
    3. If the error occurs again search for SAPNet R/3 notes, and create a 
            problem message if necessary.
    Edited by: Sebastian D'Souza on Jan 13, 2009 3:22 PM

    Hi.......
    Goto RSA1>> then to source system tab (on left side) >>  double click on the desired source system...........Then on the right side you have the Datasource tree..........there search the datasource and activate.......Also u can Replicate the datasource again.......and activate the Transfer rules using the program : RS_TRANSTRU_ACTIVATE_ALL
    After this operation when come back to source system (R/3).........I think  the error log line will be disappeared from SM58......... Then repeat the load.........
    Also u can try to Activate the infosource once...........in RSA1.........before repeating the load....
    Hope this helps......
    Regards,
    Debjani....

Maybe you are looking for