Migration Error during import(Solution Manager)

[Former Member]

Hello All,

I am migrating my current system from oracle/IBM to DB2/IBM .The export was successfull.

Now during the import only one package has gone into error.

Following are the details:

In the "import_state.properties" file one package is in error

***********************************************

"SAPDFACT=-"

************************************************

In the SAPDFACT.TSK file the following Table has error

***********************************************************

"D /BI0/F0SMD_CA01 I err"

***********************************************************

In the SAPDFACT.LOG follwing is the error.

***************************************************************

(DB6) LOAD API is not used for table with small buffer

(DB6) Using ARRAY INSERT for table /BI0/F0SMD_CA01

(DB6) IBMCLI DriverDB2/AIX64 SQL0803N One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement

are not valid because the primary key, unique constraint or unique index identified by "1" constrains table "SAPSOL./BI0/F0SMD_CA01" from having duplicate val

ues for the index key. SQLSTATE=01661

(IMP) ERROR: ExeFastload: rc = 2

(DB) INFO: disconnected from DB

*******************************************************************

Please suggest....

[Former Member]

Please refer to this post.

[Former Member]

Dont duplicate the posts, And atleast have a courtesy in saying "Thanks" when someone reply to your issue.

Thanks,

Surendra

[Former Member]

Hi Surendra,

My Apology...

Thanks for your help....

Yes... made a mistake of dublicating the post.

Actually was confused of which session you have to post!!!!

Will take care next time....

Thanks for the solution , i had done the same but had not copied the .SQL to DB/DB6 folder before the import started.And i didnt knew how to make the R3load re-read the .SQL files for that perticular package.

Yes , re-doing the import was the solution . But since it was the longest way.

Regards

Anthony

[markus_doehr2]

Don't duplicate posts:

Markus

[Former Member]

Hi Anthony,

You have to rerun the export after running the SMIGR_CREATE_DDL job in source system. You miss the prerequasite step in migration process.

As a prerequsite we must run "SMIGR_CREATE_DDL" job in the source system.

It does Generating <TABART>.SQL files containing DDL statements for non-standard database objects of ABAP Dictonary (Mainly bw objects).

Note 771209 - NetWeaver 04: System copy (supplementary note)

Exapmle Process step by step in source system:

Run this job using transaction SE38, run ABAP program SMIGR_CREATE_DDL

Use the following options as a example, if the database is oracle and version 10g

Target Database: "Oracle"

Version: "10"

Point to Nfs mount:<location where you want to copy the <TABART>.sql files>

Run the program in the background so it doesn't time out. It will run longer than 3 hours depends on the database size.

(This will create *SQL files that create the ODS and FACT tables that need partitions when they are called by R3load).

Copy this *.SQL files under before start actual EXPORT- /data/exports/ABAP/DB/<DBTYPE>/

>> Once this is done run u201CSAP_DROP_TMPTABLESu201D report for dropping temp tables

And copy the same export content to the target location for import. While import R3load will check the *.SQL files for creaiting non standard objects in ABAP dictonary.

This solves your issue.

Let me know if you have any questions.

Thanks,

Surendra