Migration - Error During Import - Oracle->MSS

[former_member183872]

Dear Gurus,

I have got error while importing an export from Linux-Oracle to Windows-MSSQL(2008(R2)-SP1).

The error are in 2 packages.

SAPAPPL1

(DB) INFO: <<table>created

(DB) INFO: <table>~0 created

(IMP) INFO: ExeFastLoad failed with <2: BCP Commit failed:[Microsoft][SQL Server Native Client 10.0][SQL Server]Violation of PRIMARY KEY constraint '<table>~0'. Cann>

(IMP) ERROR: ExeFastload: rc = 2

SAPDFACT

(DB) INFO: /BI0/E0CCA_C11 created
(DB) ERROR: DDL statement failed
(ALTER TABLE [/BI0/E0CCA_C11] ADD CONSTRAINT [/BI0/E0CCA_C11~0] PRIMARY KEY CLUSTERED ( [KEY_0CCA_C11P], [KEY_0CCA_C11T], [KEY_0CCA_C11U], [KEY_0CCA_C111], [KEY_0CCA_C112], [KEY_0CCA_C113], [KEY_0CCA_C114], [KEY_0CCA_C115], [KEY_0CCA_C116], [KEY_0CCA_C117], [KEY_0CCA_C118], [KEY_0CCA_C119] ) )
DbSlExecute: rc = 99
  (SQL error 1779)
  error message returned by DbSl:
[Microsoft][SQL Server Native Client 10.0][SQL Server]Table '/BI0/E0CCA_C11' already has a primary key defined on it.
(IMP) INFO: import of /BI0/E0CCA_C11 completed (214757 rows) #20120705083147

(DB) INFO: /BI0/E0CCA_C11~010 created
(DB) INFO: /BI0/E0CCA_C11~020 created
(DB) INFO: /BI0/E0CCA_C11~030 created
(DB) INFO: /BI0/E0CCA_C11~040 created
(DB) INFO: /BI0/E0CCA_C11~050 created
(DB) INFO: /BI0/E0CCA_C11~060 created
(DB) INFO: /BI0/E0CCA_C11~070 created
(DB) INFO: /BI0/E0CCA_C11~080 created
(DB) INFO: /BI0/E0CCA_C11~090 created
(DB) INFO: /BI0/E0CCA_C11~100 created
(DB) INFO: /BI0/E0CCA_C11~110 created
(DB) INFO: /BI0/E0CCA_C11~120 created
(DB) INFO: /BI0/E0CCA_C11~P created

There are around 231 tables with the same error for SAPDFACT.

I have gone through below notes:

Note 888210 - NW 7.**: System copy (supplementary note)

Which says we have to select MSS-2008 while running SMIGR*, but as the export was done by other team, I am not sure this has been done.... and also that this error can be linked to that.

Note 1170869 - Duplicated primary keys during system copy via R3Load:

Note 942540 - System copy fails on SAPDFACT import

I am not sure if this give the same result. As nothing will be changed.

Request you to please help me resolve the mentioned issue.

Do let me know if you require any more details.

Thanks in Advance.

Best Regards

Anuj

[former_member189725 · Accepted solution]

The reason for this error is that ~P is the primary index and ~0 is not the primary index . So when R3load tries to create primary index  ~0 , it is not able to as the the primary index ~P is already created

There is an SAP note

Note 1471193 - SMIGR_CREATE_DDL creates non-unique P-Index on APO facttable

which needs to be implemented before the export and running SMIGR_CREATE_DDL on the source system. The correction in the above note ensures that SMIGR_CREATE_DDL can create files containing ~P as unique index instead of non-unique index.

The best solution would be import this note , then run SMIGR_CREATE_DDL and export again.

Else now , you can ignore the ~0 index creation. Change the entries in SAPDFCAT.TSK  from err to ign for ~0 index for all the affected tables.

For SAPAPPL1 , please check if duplicate entry exists  on the source system for the affected table.

Regards

Ratnajit