SAP ST22 dump SAPSQL_ARRAY_INSERT_DUPREC

Hi All,
We are getting dump SAPSQL_ARRAY_INSERT_DUPREC in testing system. SAP basis: 701 and Oracle 10.2.0.2
We are getting this dump from yesterday only and the details of the dump are as mentioned below:
============================================================================================
Short text
    The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSBAL_DB_INTERNAL" had to be terminated because it
     has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
     in
    procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", nor was it propagated
     by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
Information on where terminated
    Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in
     "BAL_DB_INTERNAL_NO_UPDATE_TASK".
    The main program was "SWNCCOLL ".
    In the source code you have the termination point in line 64
    of the (Include) program "LSBAL_DB_INTERNALU02".
    The program "SAPLSBAL_DB_INTERNAL" was started as a background job.
    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
    Job Initiator.. "BASIS"
    Job Number..... 08893100
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", but it was neither
     handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLSBAL_DB_INTERNAL "; its source code begins
     line
    1 of the (Include program "LSBAL_DB_INTERNALU02 ".
System environment
    SAP-Release 701
    Application server... "appl543"
    Network address...... "122.99.01.88"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "099DER88BN90000"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 27
    Shortdump setting.... "full"
    Database server... "appl543"
    Database type..... "ORACLE"
    Database name..... "Q22"
    Database user ID.. "SAPSR3"
=====================================================================================================
Also some jobs are cancelled and they are forming the above dump. the detials are:
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 00:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 02:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 03:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 04:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 05:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 06:43:31
**The cancelled job SAP_COLLECTOR_FOR_NONE_R3_STAT generating the above dump at ST22.**
Please suggest us a solution. Thanks in advance!!!
Regards
Veera
Edited by: Veerab on Dec 17, 2010 11:33 AM

>     1 of the (Include program "LSBAL_DB_INTERNALU02 ".
Try the following:
open http://service.sap.com/notes
Search for "LSBAL_DB_INTERNALU02"
Markus

Similar Messages

  • COMPUTE_BCD_OVERFLOW ST22 dump

    Dear All,
    When I run the ECC_PRD_BITX_D_FDM_INVOICE, which is a standard SAP(program FDM_INVOICE_MEMORY).
    I get COMPUTE_BCD_OVERFLOW ST22 dump.
    This short dump occured due to CX_SY_ARITHMETIC_OVERFLOW i.e. Target field size was not able to store the value of source field at the folowing code location while assigning value to l_days_of_delay.
       90       ENDIF.
       91
       92 *     set actual discount and delay in payment
    >>>>>       l_days_of_delay = sy-datlo
       94                       - <open_item>-zfbdt
       95                       - <open_item>-zbd1t.
    Are there SAP Notes that can solve this problem?
    My system details
    S/w Component : SAP_APPL
    Release : 604
    Highest Support : SAPKH60405
    sapnote_0000620532, sapnote_0001239612 , sapnote_0001323002 do not work in my system
    Regards,
    Jack Silverz

    hi jack,
    just check these avalilabe notes for your dump.
    620532
    1323002
    1239612
    hope this will help u.
    thanks

  • ST22 Dumps in ECC pushed to Slution Manager

    Hi,
    We have a ECC6.0 and Solution Manager in our system.
    I wanted to configure that if a ST22 Dump occurs in ECC 6.0, the ST22 dump should be pused to the Solution Manager and i should be able to view it through the Solution Manager.
    Please let me know whether it is possible or anyone has done it

    Dear andreas,
    You will not be able to see ST22 dumps in solution Manager. You can see dumps in Solution Manager Diagonstics.. for that you need to configure SMD agents on satelite system and SMD on solution Manager...
    also if you just want to get alerts .. you can configure.. CCMS RZ20 and use solution manager as central system..
    search in help.sap.com for more info..
    Let me know if you require any furher info..
    Regards,
    akhilesh

  • DS 3.2  u201CDirect Downloadu201D from SAP ECC Dump RFC_ATTACH_GUI_FAILED

    DS 3.2  u201CDirect Downloadu201D from SAP ECC Dump RFC_ATTACH_GUI_FAILED  - Start 'sapgui' failed
    We are running DS 3.2.1 with a data source connected to ECC 6.0 using u201CDirect Downloadu201D.
    DS 3.2 Designer on Windows, DS Job server on Unix, SAP ECC running on Unix (different Unix box than DS).
    We get a dump in the SAP ECC source system, RFC_ATTACH_GUI_FAILED Start 'sapgui' failed.
    DETAILS
    From the DS Designer
    -     We can view the data in the SAP ECC T001 table from the ECC Data Source.
    -     Run the job from the DS designer on the DS Unix server, jobs starts the ABAP Data flow, then gets the error:
    >Cannot connect to SAP Applications datastore <DS_JR_ERD100_TEST> using host <ierpt1>, client <100>, user <G6992JR>, and system number <27: CRFC error: Start 'sapgui' failed.>. Please make sure the SAP server is running and the login information is correct.
    -     In the SAP ECC source system Tran ST22 I see the following dump:
    >Runtime Errors         RFC_ATTACH_GUI_FAILED
    >Start 'sapgui' failed.
    >u2026
    >Call Program........."al_engine"
    >Function Module..... "SYSTEM_RFC_VERSION_3_INIT"
    >u2026
    >Termination occurred in the ABAP program "SAPLSYST" - in "SYSTEM_ATTACH_GUI".
    >The main program was "SAPMSSY1 ".
    -Data Store to SAP ECC  settings:
    o     ABAP Execution Option:     Generate and Execute
    o     Execute in Background:          No
    o     Data Transfer Method:          Direct Download
    o     Working dir on Sap server:     ECC Server, no files show here.
    o     Local Directory:               DS Server,  no files here
    o     Generated ABAP Dir:          DS Unix server, the ABAP program is here.
    Has anyone seen this issue?
    Shouldnu2019t it use WS_DOWNLOAD vs. GUI_DOWNLOAD?

    Thanks for the information on the Direct Download.
    I will check test by running the generated ABAP in the SAP ECC system to see why we get the GUI ERROR.
    I now understand that Direct Download is for testing & small amounts of data & "Old" functionality.
    We were doing a test on a table with only 87 records.
    We wanted to test that we could connect from DS to the SAP ECC system & that the DS Data Flow worked.
    Also, our SAP ECC & our Data Services are on different Unix servers that do NOT have a common directory.
    So if we used Shared Directory, the file would be deposited on the SAP Server, but the DS server would not be able to see it to pick it up. So we may have to look at FTP option.
    Has anyone used DS to extract from an SAP ECC on a Unix server to Data Services on a DIFFERENT Unix server with no common directory?
    We would really prefere NOT to have to create a temporary file, but would rather it worked just like the BW extracts from SAP ECC, it just sends the records over via TRFC's, not temp file, or if it woudl work the same way as when DS pulls from one oracle DB on a Unix server to another oracle DB on a Different Unix server, I don't think that creates temporary files.
    Thanks Again for your help
    Jay Roble

  • St22 Dump in Mail

    Dear All,
    I want to configure the St22 dump in mail , With criteria if Mail is more than 150 in a day it should send a mail.Please Let me know the steps need to be done.
    RK

    Hello Rableen,
    in RZ20 there are several MTEs, where dumps are catched, for example, ABAP dumps are displayed under:
    RZ20 --> SAP CCMS Monitor Templates
                   --> Entire System
                        --> <SID> --> Application Server
                             --> <instance> --> R3Abap
    and here you have these MTEs
    You can configure threshold values in the properties of MTE "Shortdumps Frequency" and assign an autoreaction method.
    But this MTE is only for ABAP dumps. Other type of dumps you can find as described in KBA:
    1942651 - RZ20 does not display shortdumps
    but there is no such monitor in RZ20, which cathes all dumps from ST22 in one MTE.
    Regards,
    Alwina

  • Trigger ST22 Dumps as EMAIL

    Hi Everyone,
                  I want all my ST22 Dumps to be automatically triggered to a particular User mail id (Busines Workplace). so that, if any new Dump comes in a Production system i will come to know that while checking mail and provide solution immediately.How this can be done from Basis side
    Thanks& Regards,
    Siva

    Hai,
    Check the below link.....
    http://help.sap.com/saphelp_nw70/helpdata/en/2c/abb2e7ff6311d194c000a0c93033f7/frameset.htm
    Regards,
    Yoganand.V

  • Short Dump SAPSQL_ARRAY_INSERT_DUPREC

    Hi Experts,
    I am getting a the short dump SAPSQL_ARRAY_INSERT_DUPREC after executing report SDRQCR21 at line 1258
    INSERT VBBE FROM TABLE DA_XVBBE.
    Please help.

    Did you look for OSS notes for your version ?
    33267
    SDRQCR21 cancels with duplicate record
    25444
    SDRQCR21: Recovery of sales and delivery requirements
    1023578
    SDRQCR21 not fixing when wrong plant or material in VBBE
    1562605
    CALL_FUNCTION_REMOTE_ERROR SAPSQL_ARRAY_INSERT_DUPREC
    Regards,
    Raymond

  • After system copy, dump 'SAPSQL_ARRAY_INSERT_DUPREC' per every hour.

    hi experts,
    I did system copy solman 701. but I found short dump 'SAPSQL_ARRAY_INSERT_DUPREC' per every hour.
    I attach part of short dump.
    ===============================================================================
    Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
    Exception CX_SY_OPEN_SQL_DB
    Date and Time 2010.09.02 06:14:16
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "GP4II5O0KKJ13RR6R50N44F7KST" had to be terminated
    because it has
    come across a statement that unfortunately cannot be executed.
    Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
    in
    procedure "WRITE_ICFACT" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
    User and Transaction
    Client.............. 001
    User................ "SMD_RFC"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "D30DB6DF06D7F16BA277005056AD47D2"
    Program............. "GP4II5O0KKJ13RR6R50N44F7KST"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    ================================================================================================
    I think the program GP4II5O0KKJ13RR6R50N44F7KST is related with BW.
    I found information of the program GP4II5O0KKJ13RR6R50N44F7KST
    Generated report : InfoCube Write
    Template......: RSTMPLWIDTP
    RSAUInfoCube......: 0SMD_PE2H
    Author........: SMD_RFC
    Date..........: 16.07.2010 18:56:23
    How can I correct ?
    thanks and regards
    jun

    hi,
    thanks your reply.
    I applied sapnote 1500227 but still error.
    what can I do?
    Regards
    jun

  • How can I read st22 dump in ABAP

    hello,
    i would like to know if st22 dump info could be read via FMs or Classes. I found a class CL_DUMP_INFO_MANAGER, btu well could not find documentation on it usage. Will be glad if someone can tell me how to retrieve St22 info.
    - Harish

    Hi,
    Try the fun module
    RS_ST22_GET_DUMPS
    to get the dump results.
    other related fun modules are:
    RS_ST22_GET_DUMPS_CATEGORIES
    RS_ST22_GET_DUMP_CATEGORY
    RS_ST22_GET_DUMP_CATEGORY_TEXT
    reward if useful
    regards,
    Anji

  • Dump SAPSQL_ARRAY_INSERT_DUPREC when loading a hierarchy

    Hi Guru's,
    I have an error when i try to load a hiearchy on my BI system. I want to load the Cust_sales hierarchy but i ahev a short dump : SAPSQL_ARRAY_INSERT_DUPREC
    Any idea ?
    Cyril

    hi...
    it seems you have tried to insert data fro an internal table to database and in the mean it tried to insert duplicate entry ie records with same key fields.
    way to solve it:::
    way1.
    *sort the internal table in use.
    sort t_table.
    Delete adjecent duplicates.
    DELETE ADJACENT DUPLICATE ENTRIES FROM t_table
    now proceed.
    way2.
    loop at the internal table and now go for insert....
    if duplicte exist in that case it will set sy-subrc but will not give dump....
    regards

  • Dump : SAPSQL_ARRAY_INSERT_DUPREC  in VA42.

    Hi All,
    I got one critical Dump issue,
    I got the issue like dump : SAPSQL_ARRAY_INSERT_DUPREC  in VA42.
    Runtime Error      :    SAPSQL_ARRAY_INSERT_DUPREC
    Except.               :  CX_SY_OPEN_SQL_DB
    The user is trying to add a line item from Contract its going to dump, the dump is saying like  duplicate  object number .
    can any one suggest the how to resolve the issue.
    Regards,
    Jayan.

    Check SM13 for the update termination records.  View the update data and check the data condition causing the issue.  Debug.  Check for bad user exits and/or recent changes to the code.  OSS does have notes regarding the issue but it's unlikely that you'll find the issue there, especially if it just started happening, unless you just implemented support packs or notes.

  • ST22 Dump - Need to find associated proxy XML

    Hi,
    I need to find the inbound proxy call (xml message), which has caused the ST22 dump. Can any of you tell me whether the transaction id or any other values from ST22 can be used to track the message unique?
    Thanks,

    HI Joe,
    for any proxy call either inbound or outbound, you will find all the processed the messages in the SXMB_MONI transaction.
    the messages which are processed successfully has the status and processed successfully but if there is any problem during the processing of message because of program dump then this message remains in the green flagged status. hence try to find out the green flagged status and check the error log for the same. you will find out the exact error message which is appearing in ST22.
    you can also try to check the queue using smq2 transaction , if there is any dump while processing the message the followeing messages are got stuck as long as you are not deleting the first messages. from there also you can see the erroneous XML data.

  • ABAP dump(SAPSQL_ARRAY_INSERT_DUPREC) while creating a delivery

    Hello Friends,
    I am getting the dump while creating the delivery .The error details are as follows.
    The ABAP/4 Open SQL array insert results in duplicate database record
    What happened?
    The current ABAP/4 program "SAPLV05I " had to be terminated because
    one of the statements could not be executed.
    How to correct the error
    Use an ABAP/4 Open SQL array insert only if you are sure that none of
    the records passed already exists in the database.
    If the error occurred in a non-modified SAP program, you may be
    able to find a solution in the SAP note system.
    If you have access to the note system yourself, use the following
    search criteria:
    "SAPSQL_ARRAY_INSERT_DUPREC"
    "SAPLV05I " or "LV05IU15 "
    "SD_PARTNER_UPDATE"
    Source code extract
    004500                                           POSNR = I_XVBPA-POSNR
    004510                                           PARVW = I_XVBPA-PARVW.
    004520               IF I_YVBPA-STCD1 <> I_XVBPA-STCD1 OR
    004530                   I_YVBPA-STCD2 <> I_XVBPA-STCD2 OR
    004540                   I_YVBPA-STCD3 <> I_XVBPA-STCD3 OR
    004550                   I_YVBPA-STCD4 <> I_XVBPA-STCD4 OR
    004560                   I_YVBPA-STCDT <> I_XVBPA-STCDT OR
    004570                   I_YVBPA-STKZN <> I_XVBPA-STKZN OR
    004580                   I_YVBPA-J_1KFREPRE <> I_XVBPA-J_1KFREPRE OR
    004590                   I_YVBPA-J_1KFTBUS <> I_XVBPA-J_1KFTBUS OR
    004600                   I_YVBPA-J_1KFTIND <> I_XVBPA-J_1KFTIND.
    004610                 MOVE-CORRESPONDING I_XVBPA TO WA_XVBPA3I.
    004620                 APPEND WA_XVBPA3I TO DA_XVBPA3I.
    004630               ENDIF.
    004640             ENDIF.
    004650           ENDIF.
    004660         WHEN UPDKZ_OLD.
    004670           IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD   OR
    004680              DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
    004690             YADR-ADRNR = DA_VBPA-ADRNR. COLLECT YADR.
    004700           ENDIF.
    004710           IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD   OR
    004720              DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
    004730             XADR-ADRNR = DA_VBPA-ADRNR. COLLECT XADR.
    004740           ENDIF.
    004750       ENDCASE.
    004760     ENDLOOP.
    004770     UPDATE (OBJECT) FROM TABLE DA_XVBPAU.
    004780     UPDATE VBPA3 FROM TABLE DA_XVBPA3U.
    004790
         >     INSERT (OBJECT) FROM TABLE DA_XVBPAI.
    004810     INSERT VBPA3 FROM TABLE DA_XVBPA3I.
    004820
    004830     IF SY-SUBRC > 0.
    Could you please suggest me ,what could be the reason for dump and how to avoid dump?
    <REMOVED BY MODERATOR>
    Thank you in advance,
    Arvind.
    Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:16 PM
    Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:16 PM

    Hello, I have very same error
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
    Transaction......... "VL01N "                                                                
    Program............. "SAPLV05I"                                                              
    Screen.............. "RSM13000 3000"                                                         
    Screen line......... 2   
    SAP kernel....... 700  
    Patch level. 75 
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"                             
    SAP database version. 700                                                                    
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2" 
    The ABAP/4 Open SQL array insert results in duplicate database records.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught  in procedure "SD_PARTNER_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING clause.
    I use SAP_APPL SAPKH60006 Support Package
    The NUMBER RANGE OBJECT HAS NO ERRORS!
    I went trough the zillions of notes all of them affect the old releases.... Please advice.
    Patiently yours,
    SAP User

  • SAP Short Dumps and PCI Compliance

    We've run into an issue with our PCI Compliance audit around being able to see unencrypted credit cards in short dump messages in SAP.  Has anyone run into this issue?
    Only work around I've got at this point is to restrict all access to short dumps and require many documented signoffs before turning on and off access to a short dump.  This is pretty cumbersome, and still leaves a hole in my overall security.
    We've managed to purge restricted CC data from our XI logging, and done everything right with encryption, but this short dump issue just doesn't seem to have a solution.
    Can anyone help?  We're on 6.0.
    Thanks!

    Hi David,
    This is an interesting situation you have described. ABAP short-dumps or run-time errors as they are also known as, are unhandled exceptions during program execution. The conditions that cause such exceptions is unknown or cannot be handled at run-time. To help analyze what went wrong with the said program during execution, it is necessary for the dump to contain all possible information including data values passed between programs when the error occurs. Encryption of restricted data values is a program step in itself. If the dump were to occur after this step then of course it would contain encrypted CC info. Unfortunately in your case it exposes restricted CC info because the dump occurs BEFORE this step.
    I don't believe there is a way to prevent this from happening -- for the same reason that the program logic does not know at run-time how to "handle" the exception. If occurrences of such dumps is fairly common in your system, you may want to investigate the likely causes -- for example, missing or incorrect customization. Analyzing the short dumps will probably give you a clue. Your customization team may be able to identify a pre-condition that causes this unhandled exception. If this exception can then be handled (via a program change) that returns a meaningful error instead of a short dump you would be able to close the security hole. This however entails modification to SAP standard code. I don't usually recommend such changes, but given the sensitive nature of your data it may be worth consideration.
    I personally advocate restricted access to ST22. The steps you have undertaken to enforce this may be cumbersome despite efforts to keep it simple. I suppose that's the price we pay in administering the system. If you have not already done so, you may also want to ensure that short-dumps that contain restricted CC info are not saved (using the "Keep" feature in ST22) for easy retrieval at a later point in time or they are saved, it be available only to 'restricted eyes'. Short-dumps are normally saved in the system for 7 or 14 days (not sure of exact # of days). The bigger challenge in my opinion is: How do you prevent the restricted info from being viewed by the user who during the course of program/transaction execution encounters the said short dump? No amount of security controls around ST22 will mitigate this risk. The only option that remains is program change (as mentioned above). But to get there you first need to know what causes the exception.
    Regards.
    Ashutosh

  • ST22 Dumps: Shared Objects

    Hi SDN,
    in our SRM System, SRM Server 5.5, WAS700 ABAP, we get ST22 Short Dumps concerning "shared objects".
    This is the Dump Short Analysis:
    Runtime Errors         SYSTEM_NO_SHM_MEMORY                                    
    Date and Time          19.08.2008 12:20:50                                                                               
    Short text                                                                    
         No more memory for 2516576 bytes in the shared objects memory.                                                                               
    What happened?                                                                
         The shared objects memory is full or an area management specified         
         memory limit has be reached.                                              
    In heard, that "shared objects" is part of the new WAS 620, 640, 2004s, 700 ... releases
    What are exactly these shared objects. And how can we avoid the dumps?
    We have an instance profile parameter set:
    abap/shared_objects_size_MB                 100
    Apparently this is not enough... Are there any recommendations?
    thanx, matthias

    Take a look at [Note 972757 - Occurence of the SYSTEM_NO_SHM_MEMORY runtime error|https://service.sap.com/sap/support/notes/972757] for further information. You should investigate what is using the shared objects memory, it may be an error in a application. The note will help to determine this.
    Regards,
    Nelis

Maybe you are looking for