cancel
Showing results for 
Search instead for 
Did you mean: 

CRM Upgrade Error During SHADOW_IMPORT_INC

former_member183872
Participant
0 Kudos

Dear Gurus,

We are in process of upgrading our EHP1 FOR SAP CRM 7.0 (SAP EHP2 FOR SAP NETWEAVER 7.0) to EHP2 FOR SAP CRM 7.0 (SAP EHP3 FOR SAP NETWEAVER 7.0).

We are getting below error in the phase SHADOW_IMPORT_INC:

ERROR: Detected the following errors due to error summary in E:\usr\sap\CR1\SUM\abap\log\SHDALLIMP.ELG:

# E:\usr\sap\CR1\SUM\abap\log\SAPK-702BRINBBPCRM.CR1:

4 ETW000  [     dev trc,00000]  Tue Aug 07 09:43:08 2012                                             68485403  68.485403

4 ETW000  [    dbrsbuf ,00000]  ***LOG BBC=>nametab inconsistency for table TADIR~     regarding view buffering

4 ETW000                                                                                                  50  68.485453

4 ETW000   1 entry for TADIR~ updated  (R3TRATTR80215ADE55241DDF8CE636D957DE4033        ).

4 ETW000  [     dev trc,00000]  table logging switched off for all clients                             36467  68.521920

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

4 ETW000  [     dev trc,00000]  Tue Aug 07 09:45:16 2012                                             62566284  62.566284

4 ETW000  [    dbrsbuf ,00000]  ***LOG BBC=>nametab inconsistency for table TADIR~     regarding view buffering

4 ETW000                                                                                                  50  62.566334

4 ETW000   1 entry for TADIR~ updated  (R3TRATTR80215ADE55241DDF8CE636D957DE4033        ).

4 ETW000  [     dev trc,00000]  table logging switched off for all clients                               714  62.567048

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

I have gone through below SAP notes and links, but issue comes again when i rerun it after making changes:

601757 - Error upgrading from Release 2.0C, 3.0, 3.1, 3.5 to CRM 4.0

1591102 - Error in comc_attribute during the import of CRM 701 - We are already at patch level 8

http://scn.sap.com/message/13295580

Request your help to resolve the issue.

Please let us know if you require any details.

Thank you in advance.

Best Regards,

Anuj

Accepted Solutions (1)

Accepted Solutions (1)

former_member189725
Active Contributor
0 Kudos

As per the SAP note Note 626915 - Transport problems with tables with a unique index

please change the unique index to non-unique index for the table COMC_ATTRIBUTE

Login to the main instance and change it.

Regards

Ratnajit

former_member183872
Participant
0 Kudos

Thanks for your reply Ratnajit.

I have already made the changes as mentioned in your reply.

And as per one of the sdn link i have also dropped the index as well.

But when i re-run the upgrade with both the options i.e. Initialize and Repeat it gives the same error.

former_member189725
Active Contributor
0 Kudos

Go to se11 , display the table COMC_ATTRIBUTE , then click on indexes . Select the index , go to change mode . Select the option non-unique index (index on all database systems).

Once the listed unique index is defined as non-unique in the ABAP dictionary , the upgrade should go through .

Regards

Ratnajit

former_member183872
Participant
0 Kudos

Same result.

former_member189725
Active Contributor
0 Kudos

I believe the index COMC_ATTRIBUTE~UNI is the index which is affected. In SE11 , once you save the change after setting the index as non-unique , activate the index (in the menu bar index -->activate)

Then go to se14 , enter the table name , Edit , select indexes , select the index , then adjust and activate . This would recreate the index . Then check the object log.

Regards

Ratnajit

former_member183872
Participant
0 Kudos

Did the same ... but it got the same error again.

former_member189725
Active Contributor
0 Kudos

Did you resolve the issue?

Did you try to change the index on the database level .?

What is the underlying database you have ??

Regards

Ratnajit

former_member183872
Participant
0 Kudos

Hello Ratnajit,

Thank you for asking.

I was able to complete the upgrade today.

I feel i missed out activating both i.e. table and index during my 1st run.

I reset the upgrade and started all over again.

It went through with very less issues this time :-).

Thank you very much for your help.

Best Regards,

Anuj

Answers (0)