Update and insert sequence failed due to conflicting unique indexes on table /IWFND/I_MED_SRH (please read OSS note 626915 for details)

[former_member147856]

Hi  Friends,

we are facing an issue in TABIM Execution phase during an SP upgrade with SUM.

Update and insert sequence failed due to conflicting unique indexes on table /IWFND/I_MED_SRH (please read OSS note 626915 for details)

While trying to delete it from SE14 its getting dumped. due to syntax error.

please help use , already tried changing kernel version from 741 to 742.

OS HP-UX 11.31

DB Sybase ASE 15.7 sp 122

Attaching logs .

Thanks,

logs.txt.zip

TABIM.txt.zip

[james_wong · Accepted solution]

Hello Saurav Bisht,

Regarding your issue, during the import, the target system must contain a unique index where the source system doesn't have. As per SAP note 626915, you will have to bring the tables on both

systems in sync. So now you have to delete the unique index in the target system.

SE11 <tablename> -> display -> indices

Best regards,

James

[former_member778080]

Dear All ,

Please follow note 3056869 - Handling /IWFND/I_MED_SRH table index issue during system upgrade in HANA

Login to your hana console using schema user id and password . execute below sql queries in my case SAPHANADB is the schema username .

DROP INDEX "SAPHANADB" . "/IWFND/I_MED_SRH~1" ;

DROP INDEX "SAPHANADB" . "/IWFND/I_MED_SRH~~1 ";

And repeat your upgrade from the point where it stopped .

Thanks and Regards

Pavan Kumar

[Former Member]

Hi Saurabh,

Were you able to fix this issue, we are facing the same issue now?

[anandkarthik_raja]

Hi San,

Could you please attach the error log.

Regards,
Anand.

[Reagan]

Have you tried to drop the index from the DB level ?

Connect to the shadow system and call Tx SE16 - TATAF and enter /IWFND/I_MED_SRH in the TABNAME field and provide the output.

Regards

Reagan

[former_member147856]

After dropping the index from the DB level its still giving same error.

And SE16 is giving dump as SAP_BASIS patch upgrade is not yet complete.

Thanks,

[Reagan]

If you are unable to use Tx SE16 then could you query the table from the DB level ?

Reagan