MAIN_SHDIMP/PARMVNT_SHD SQL-error "1505-The CREATE UNIQUE INDEX statement terminated because 2EETP345 a duplicate key was found

[Former Member]

Hello

We are in the process of an upgrade this weekend and are recieving the following error during the "Preprocessing" phase in SUM (13 Patch 1), which is an error we did not recieve in the mock upgrades from the same source, which is a bit odd.

Hoping someone can help out in steps on resolving and moving past this MSSQL error, as there doesnt seem to be any specific SAP notes related to this issue with the EHP7 upgrade on ECC?

Your help and expertise would be greatly appreciated.  Thanks in advance.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MVNTABS ERRORS: ddlntabs and RETURN CODE in PD000718.ECD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3 ETP000 [LGART] ,
3 ETP000 [TABNA] ,
3 ETP000 [LFDNR] )
3 ETP000 
2WETP000 14:24:30: Retcode 1: error in DDL statement for "T512E                         " - repeat
2EETP345 14:24:46: Retcode 1: SQL-error "1505-The CREATE UNIQUE INDEX statement terminated because
2EETP345 a duplicate key was found for the object name 'ecd.T512E~' and the index name 'T512E^0'. T
2EETP345 he duplicate key value is (000, 07, KK01, /101, RT, 00)." in DDL statement for "T512E    
2EETP345                     "
2 ETP000  --------------- DB-ROLLBACK() ---------------
2EETP334 14:24:46: error in DDL, nametab for "T512E" not activated

3 ETP000 [LEV2NAME] ,
3 ETP000 [REFCOUNT] )
3 ETP000 ON [PRIMARY]
3 ETP000 
2WETP000 14:24:46: Retcode 1: error in DDL statement for "THEXS                         " - repeat
2EETP345 14:24:58: Retcode 1: SQL-error "1505-The CREATE UNIQUE INDEX statement terminated because
2EETP345 a duplicate key was found for the object name 'ecd.THEXS~' and the index name 'THEXS~0'. T
2EETP345 he duplicate key value is ( ,  ,  ,  , 00)." in DDL statement for "THEXS                 
2EETP345        "
2 ETP000  --------------- DB-ROLLBACK() ---------------
2EETP334 14:24:58: error in DDL, nametab for "THEXS" not activated
1 ETP111 exit code           : "8"

[Reagan · Accepted solution]

The best would be to modify the TATAF table and change the create statement by removing UNIQUE to let the tool create a non-unique index and continue.

[Former Member · Accepted solution]

This could definitely be an answer, could you explain specifically what you mean.

I assume you speak of the TATAF~ from the shadow instance, as the TATAF has 0 entries?

Do you recommend deleting an entry from the TATAF~ table based on the specific tables I am reciving the errors on, as this 'TABNAME' doesnt seeem to exist in this table?

[Reagan · Accepted solution]

Correct. The TATAF on the shadow is the one. You should modify the index creation statement by removing UNIQUE from it for the failed table and repeat the phase.

[Former Member · Accepted solution]

We have resolved the issue in TATAF but unfortunastely with this release it does not have any entries that specify "UNIQUE" on the create. We will recreate the indexes required in DB02 upon completion of upgrade.

Thanks for your help!