ITAB_DUPLICATE_KEY

[Former Member]

Hi ,

We have received around 1000 dumps, most of them "ITAB_DUPLICATE_KEY" (PROGRAM : /PSYNG/SAPLSW_UTLS ) and "ASSERTION FAILED" (PROGRAM :   /SIE/SRM_AVOID_PARALLEL_RUN).

Please find the logs.

Category               ABAP Programming Error

Runtime Errors         ASSERTION_FAILED

ABAP Program           /SIE/SRM_AVOID_PARALLEL_RUN

Application Component  Not Assigned

Date and Time          03.07.2014 13:20:27

Operating system..... "Linux"

Release.............. "3.0.93-0.8-default"

Hardware type........ "x86_64"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 142

Shortdump setting.... "full"

Database server...

Database type..... "ORACLE"

Database name.....

Database user ID.. "SAPDAT"

SAP kernel....... 720

Patch level. 525

Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"

SAP database version. 720

Operating system..... "Linux 2.6, Linux 3"

2.) ITAB_DUPLICATE_KEY

Category               ABAP Programming Error

Runtime Errors         ITAB_DUPLICATE_KEY

ABAP Program           /PSYNG/SAPLSW_UTLS

Application Component  BC

Date and Time          03.07.2014 13:22:02

[former_member182657]

Hi,

Kindly share the complete dump details.

Regards,

Gaurav

[Former Member]

Hello Gaurav,

Category               ABAP Programming Error

Runtime Errors         ITAB_DUPLICATE_KEY

ABAP Program           /PSYNG/SAPLSW_UTLS

Application Component  BC

Date and Time          03.07.2014 16:01:56

Short text

     There is already a line with the same key.

What happened?

     Error in the ABAP Application Program

     The current ABAP program "/PSYNG/SAPLSW_UTLS" 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

     You tried to insert an entry into table

      "\PROGRAM=/PSYNG/SAPLSW_UTLS\DATA=IFAOBJ[]". However, updating

     the unique table key "PRIMARY_KEY" resulted in a duplicate entry. The key

     concerned may be either the primary key or a secondary key.

     The key components of the duplicate entry have the values

"{SE21;/SIE/SRM_REP;S_PROGRAM;001;P_ACTION;SUBMIT;}"

" " " " " ".

With primary keys, the system may terminate while processing

block insert operations. The statements concerned are

(1) MOVE

(2) INSERT/APPEND ... LINES OF ... INTO/TO

(3) SELECT ... INTO/APPENDING ...

With secondary keys, the system may also terminate while processing

a single record insert operation. In particular, the following

modifying statements may cause the system to terminate due to

duplicate key values:

(1) "<fs> = ..." or "<fs>-comp = ...", if the assignment to

a field symbol or to a component of a field symbol modifies a

component of a unique secondary key.

(2) "ref->* = ..." or "ref->comp = ...", if the assignment to a field

symbol or to a component of a field symbol modifies a component of

a unique secondary key.

(3) "MODIFY ... [TRANSPORTING comp_1 ... comp_n] ...", if transporting

the components to be changed modifies a component of a unique secondary

key.

(4) "COLLECT ... INTO ...", if adding up the columns of a numeric type

modifies a component of a unique secondary key.

(5) "READ TABLE ... INTO <fs> ...[TRANSPORTING comp_1 ... comp_n] ...",

if the field symbol points to a row of a table with unique secondary

keys and transporting the values read modifies a component of a unique

secondary key.

System environment

    SAP Release..... 702

    SAP Basis Level. 0013

    Application server...

    Network address......

    Operating system..... "Linux"

    Release.............. "3.0.93-0.8-default"

    Hardware type........ "x86_64"

    Character length.... 16 Bits

    Pointer length....... 64 Bits

    Work process number.

    Shortdump setting.... "full"

    Database server...

    Database type..... "ORACLE"

    Database name.....

    Database user ID.. "SAPDAT"

    Terminal.......... " "

    Char.set.... "C"

    SAP kernel....... 720

    created (date)... "Feb 10 2014 20:06:13"

    create on........ "Linux GNU SLES-9 x86_64 cc4.1.2 use-pr130820"

    Database version. "OCI_102, 11.2.0.2.0, V1, default"

    Patch level. 525

    Patch text.. " "

User and Transaction

    Client.............. 111

    User................ "RFC_P_R0P011"

    Language key........ "E"

    Transaction......... " "

    Transaction ID...... "53B53C1B15651CDDE10000009DA38A64"

    EPP Whole Context ID.... " "

    EPP Connection ID....... " "

    EPP Caller Counter...... 0

    Program............. "/PSYNG/SAPLSW_UTLS"

    Screen.............. "SAPMSSY1 3004"

    Screen Line......... 2

    Debugger Active..... "none"

Server-Side Connection Information

    Information on caller of Remote Function Call (RFC):

    System.............. "R0P"

    Installation Number. " "

    Database Release.... 700

    Kernel Release...... 721

    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

    Call Type........... "asynchronous with reply and non-transactional (emode 0,

     imode 0)"

    Inbound TID.........." "

    Inbound Queue Name..." "

    Outbound TID........." "

    Outbound Queue Name.." "

    Client.............. 011

    User................ "CPIC_ZAV"

    Transaction......... " "

    Call Program........."/PSYNG/SAPLSW_UTLS_3A"

    Function Module..... "/PSYNG/SW_FUNC_SCAN"

    Call Destination.... "XXXCLNT111"

    Source Server....... ""

    Source IP Address... ""

    Additional information on RFC logon:

    Trusted Relationship " "

    Logon Return Code... 0

    Trusted Return Code. 0

    Note:

    - For Releases < 4.0, information on the RFC caller not available.

    - The installation number is available from caller Release > 700

    Additional information on RFC logon:

    Trusted Relationship " "

    Logon Return Code... 0

Server-Side Connection Information

    Information on caller of Remote Function Call (RFC):

    System.............. "R0P"

    Installation Number. " "

    Database Release.... 700

    Kernel Release...... 721

    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

    Call Type........... "asynchronous with reply and non-transactional (emode 0,

     imode 0)"

    Inbound TID.........." "

    Inbound Queue Name..." "

    Outbound TID........." "

    Outbound Queue Name.." "

    Client.............. 011

    User................ "CPIC_ZAV"

    Transaction......... " "

    Call Program........."/PSYNG/SAPLSW_UTLS_3A"

    Function Module..... "/PSYNG/SW_FUNC_SCAN"

    Call Destination.... "POSCLNT111"

    Source Server....... "pkgr0p0d_R0P_00"

    Source IP Address... "157.163.137.112"

    Additional information on RFC logon:

    Trusted Relationship " "

    Logon Return Code... 0

    Trusted Return Code. 0

    Note:

    - For Releases < 4.0, information on the RFC caller not available.

    - The installation number is available from caller Release > 700

    Additional information on RFC logon:

    Trusted Relationship " "

    Logon Return Code... 0

Information on where terminated

    Termination occurred in the ABAP program "/PSYNG/SAPLSW_UTLS" - in

     "/PSYNG/SW_GET_TCODE_AUTH_DATA".

    The main program was "SAPMSSY1 ".

    In the source code you have the termination point in line 46

    of the (Include) program "/PSYNG/LSW_UTLSU09".

[Former Member]

Hi Udaya,

Please check with your database team regarding this error "

Error analysis

     You tried to insert an entry into table

      "\PROGRAM=/PSYNG/SAPLSW_UTLS\DATA=IFAOBJ[]". However, updating

     the unique table key "PRIMARY_KEY" resulted in a duplicate entry. The key

     concerned may be either the primary key or a secondary key.

Also, you can check this note

1674895 - View maintenance function group cannot be generated

Thanks

Adil

[Reagan]

Were there some changes done to the system prior to this like a kernel upgrade or so ?

Regards

RB

[Former Member]

Hello Reagan,

Thanks for the reply.

Storage migration was performed on the system last week.Also,some parameter changes done on the system.

Regards,

uday.