FI_GL LOAD GETTING INTO SHORTDUMP "SAPSQL_ARRAY_INSERT_DUPREC"

Question

Hi Experts,
    We have FI_GL  DTP load from datasource PSA to  DSO, this was loading sucessfully till 25 of JUNE. From 28 th of June this load is getting into short dump "SAPSQL_ARRAY_INSERT_DUPREC"but surprisingly when i repeat this step the load getting successfull.  please let me know how can i stop this Shortdump in future.
thanks in advance
please see the below deatiled shortdump message.
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
Date and Time          07.07.2010 04:15:51
     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 "SAPLSDDO" had to be terminated because it has
          come across a statement that unfortunately cannot be executed.
     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 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 "DD_DTEL_SET_PUT" "(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.)
     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 occures in a non-modified SAP program, you may be able to
          find an interim solution in an SAP Note.
          If you have access to SAP Notes, carry out a search with the following
          keywords:
          "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
          "SAPLSDDO" or "LSDDOU08"
          "DD_DTEL_SET_PUT"
          If you cannot solve the problem yourself and want to send an error
          notification to SAP, include the following information:
          1. The description of the current problem (short dump)
             To save the description, choose "System->List->Save->Local File
          (Unconverted)".
          2. Corresponding system log
             Display the system log by calling transaction SM21.
             Restrict the time interval to 10 minutes before and five minutes
          after the short dump. Then choose "System->List->Save->Local File
          (Unconverted)".
          3. If the problem occurs in a problem of your own or a modified SAP
          program: The source code of the program
             In the editor, choose "Utilities->More
          Utilities->Upload/Download->Download".
          4. Details about the conditions under which the error occurred or which
          actions and input led to the error.
          The exception must either be prevented, caught within proedure
          "DD_DTEL_SET_PUT" "(FUNCTION)", or its possible occurrence must be declared in
           the
          RAISING clause of the procedure.
          To prevent the exception, note the following:
     System environment
          SAP-Release 701
          Application server... "EUAX418-ZEP"
          Network address...... "10.129.6.97"
          Operating system..... "AIX"
          Release.............. "5.3"
          Hardware type........ "00C13D524C00"
          Character length.... 16 Bits
          Pointer length....... 64 Bits
          Work process number.. 18
          Shortdump setting.... "full"
          Database server... "EUAX418-ZEP"
          Database type..... "DB6"
          Database name..... "BWP"
          Database user ID.. "SAPBWP"
          Terminal.......... " "
          Char.set.... "C"
          SAP kernel....... 701
          created (date)... "Feb 15 2010 21:28:06"
          create on........ "AIX 2 5 00CB5A5B4C00"
          Database version. "DB6_81 "
          Patch level. 81
          Patch text.. " "
          Database............. "DB6 08.02., DB6 09."
          SAP database version. 701
          Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
          Memory consumption
          Roll.... 16192
          EM...... 16759392
          Heap.... 0
          Page.... 24576
          MM Used. 6041768
          MM Free. 2335128
     User and Transaction
          Client.............. 100
          User................ "ALEREMOTE"
          Language key........ "E"
          Transaction......... " "
          Transactions ID..... "4C27AEF624350086E10080000A810661"
          Program............. "SAPLSDDO"
          Screen.............. "SAPMSSY0 1000"
          Screen line......... 6
     Information on where terminated
          Termination occurred in the ABAP program "SAPLSDDO" - in "DD_DTEL_SET_PUT".
          The main program was "RSBATCH_EXECUTE_PROZESS ".
          In the source code you have the termination point in line 54
          of the (Include) program "LSDDOU08".
          The program "SAPLSDDO" was started as a background job.
          Job Name....... "BIDTPR_207115_1"
          Job Initiator.. "ALEREMOTE"
          Job Number..... 04140400
          The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
          procedure "DD_DTEL_SET_PUT" "(FUNCTION)", but it was neither handled locally
           nor declared
          in the RAISING clause of its signature.
          The procedure is in program "SAPLSDDO "; its source code begins in line
          1 of the (Include program "LSDDOU08 ".
             leng         = 4     (0x00000004)
             loop         = -1    (0xFFFFFFFF)
             xtyp         = TYPE#000126
             occu         = 25    (0x00000019)
             access       = 1     (ItAccessStandard)
             idxKind      = 0     (ItIndexNone)
             uniKind      = 2     (ItUniqueNon)
             keyKind      = 1     (default)
             cmpMode      = 0     (cmpAllDynamic)
             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         = 0x07000000606AC9E8
             pgHook       = 0x0000000000000000
             idxPtr       = 0x0000000000000000
             shmTabhSet   = 0x0000000000000000
             id           = 2095  (0x0000082F)
             refCount     = 0     (0x00000000)
             tstRefCount  = 0     (0x00000000)
             lineAdmin    = 25    (0x00000019)
             lineAlloc    = 25    (0x00000019)
             shmVersId    = 0     (0x00000000)
             shmRefCount  = 1     (0x00000001)
             >>>>> 1st level extension part <<<<<
             regHook      = Not allocated
             collHook     = Not allocated
             ext2         = Not allocated
             >>>>> 2nd level extension part <<<<<
             tabhBack     = Not allocated
             delta_head   = Not allocated
             pb_func      = Not allocated
             pb_handle    = Not allocated
     I

Answer 1

Hi,
This error due to that you are inserting duplicate records into DSO Key fields.
Check your record in PSA and remove duplicate reocrds from PSA and try to run transformation again or you need to change primary key of your DSO to fit PSA data.
Thank you,
Regards,
Govind.