cancel
Showing results for 
Search instead for 
Did you mean: 

Table duplicate keys at import step - CU&UC

0 Kudos

Hi all,

We are experiencing a serious problem in our SAP Combined Upgrade and Unicode Conversion.

We are upgrading SAP R/3 4.7 systems to ECC6 EHP7 SPS07.

And in the meantime, we convert the database in UNICODE.

- The UNICODE preparation steps are all OK (SPUMG and so on).

- The upgrades steps are all ok (shadow and offline upgrade steps).

But when we export/import the database to convert it in UNICODE, we get duplicate keys in EKPO table at import step, which make the SWPM unable to create the primary index.

The fact is that EKPO table does not seem to get any problems in the source system.

We tried SAP Notes 2007272 and 2144285 without any result.

Any ideas please ?

Best regards,

Stéphan

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi all,

Sorry, I didn't come back here to give the solution.

So, after about 10 exports/imports with different tests, we found the solution !

This problem is due to an Oracle bug because of table compression.

The SAP note which indicate this problem is :

SAP Note 1970224 - Missing or wrong data in OLTP compressed tables after expanding columns to be > 255.

The fact is that upgrading in ECC6, some tables are modified and get more than 255 fields.

And when we export the DB to convert it unicode, it generates duplicate keys because of this bug.

We only get the bug for table EKPO at our side.

So, we proceeded in the following exact order :

- SAP Upgrade from 4.7 to ECC6 Ehp7

- SAP SBP installation (SBP201505 in our case), containing the necesary bug fix

- Database export

- SAP installation and DB import

We ran the production migration at the beginning ot november and all was ok.

Do not hesitate to ask me more information if necesary. It would be a pleaseure to help if I can.

Regards,

Stéphan

Answers (2)

Answers (2)

mirra_yin
Explorer
0 Kudos

Hello Stéphan

The duplicated keys could be already there in the source system.

In the source system, you should goto SE14 and click the "Check" button for EKPO. Make sure no inconsistency especially on the index.

Best Regards

Mirra

Former Member
0 Kudos

Hi Stéphan

i think you may receive more help if you upload the log with the error and the command of the import (just to refresh my memory about that activity)

let me know

a