Conflicting Unique indexes - CRM upgrade stopped

[Former Member]

Hi Friends,

We are getting the below error in pre-processing step of CRM upgrade from CRM 5.2 to CRM 7.0 EHP 2.0

"Checks after phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_UPG2 were negative!

Last error code set: Detected 128 errors summarized in 'SHDUPGIMP2.ELG'<br/> Calling '/dataexport/SUM/abap/exe/tp' failed with return code 8, check /dataexport/SUM/abap/log/SAPup.ECO for details"

Detail from SHDUPGIMP2.ELG:

"2EETW000 Update and insert sequence failed due to conflicting unique indexes on table COMC_ATTRIBUTE (please read OSS note 626915 for details)"

I have dropped the index at DB level.

Any suggestion on how to proceed further..

I have attached the below files

    SHDUPGIMP2.ELG

    SAPup.log

    Error screenshot & Table details at DB level

System details:

CRM 7.0 EHP2.0 , Oracle 11g

I have referred the below,

http://scn.sap.com/thread/3293015

SAP Note : 626915

Thanks in Advance

Thanks, Ganesh

SHDUPGIMP2_ELG.txt.zip

SAPup.txt.zip

[former_member188883 · Accepted solution]

Hi Ganesh,

As per SAP Note 689574 - Add. info. on upgrading to SAP ERP Central Component 5.00

Similar issue has been addressed.

Solution is :

delete the primary index of the respective table and recreate it. Repeat the upgrade phase

Hope this helps.

Regards,

Deepak Kori

[Former Member · Accepted solution]

Hi Deepak,

Thanks,

This note is not applicable to us as we are in SAP Basis 700

Thanks, Ganesh

[former_member188883 · Accepted solution]

Hi Ganesh,

I understand that SAP note is for ECC 5.0 and your environment is CRM 7.0.

Objective of giving reference to that note is for the issue and solution described.

Solution is to drop the index and recreate it and proceed with upgrade.

As you have already dropped the index, re-create it and then continue with upgrade.

Hope this helps.

Regards,

Deepak Kori

[Former Member · Accepted solution]

Hi Deepak,

No luck , Error remains same.

Thanks, Ganesh

[stefan_koehler · Accepted solution]

Hi Ganesh,

> No luck , Error remains same.

What a surprise ... why should dropping and recreating an unique index solve the problem like Deepak mentioned? This is the main task of such an index - keeping the uniqueness (in combination with a NOT NULL constraint). If you have some duplicates - it will always fail. I am so tired of such "Google & Copy & Paste" recommendations without a profound analysis or any clue about the root cause.

Please run the following query and post your index definitions on table "COMC_ATTRIBUTE". SAP is usually aware of that unique key requirements and such errors could be caused by customized index definitions.

SQL> select INDEX_NAME, COLUMN_NAME, COLUMN_POSITION 
           from DBA_IND_COLUMNS where INDEX_NAME 
           IN (select INDEX_NAME 
                 from DBA_INDEXES 
                  where TABLE_NAME = 'COMC_ATTRIBUTE' and UNIQUENESS = 'UNIQUE');

Regards

Stefan

[Former Member · Accepted solution]

Hi All,

The issue is solved,  below are the steps. Thank you all for the suggestions.

Solution :

1. Created the unique index "COMC_ATTIBUTE~UNI"at SAP level in SE14

2. Renamed  the unique index from "COMC_ATTIBUTE~UNI" to "ZDROPINDEX" at DB level instead of deleting it.

3. Retried the main import phase in SUM.

Thanks, Ganesh