cancel
Showing results for 
Search instead for 
Did you mean: 

Migration Error during import(Solution Manager)

Former Member
0 Kudos

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) [IBM][CLI Driver][DB2/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....

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

Apparently you did not execute SMIGR_CREATE_DDL on the source system and copied the resulting SQL files over...

Markus

Former Member
0 Kudos

Hello Markus,

I had executed the report "SMIGR_CREATE_DDL " before the import.

But the 2nd step i.e ., Coping the SQL files to the ABAP/DB/DB6 directory was not done.

Now i have copied the files to this location and tried to rerun the R3load.But the same error.

Please suggest

Regards

Anthony

markus_doehr2
Active Contributor
0 Kudos

Do you see in the logfile that the SQL files are picked?

Markus

Former Member
0 Kudos

Hello Markus

I have checked the SAPDFACT.LOG . But no were it specifies that the DODS.SQL and DFACT.SQL files are picked.

Please find the output of the SAPDFACT.LOG after i had rerun after moving the files to the DB/DB6 folder

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

/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20090603142537

/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 21:47:44

/usr/sap/SOL/SYS/exe/run/R3load -i SAPDFACT.cmd -dbcodepage 4102 -k 1G5fdEM50TIIrBzjt6TE5Pae -l SAPDFACT.log -stop_on_error -loadprocedure fast LOAD

(DB) INFO: connected to DB

(GSI) INFO: dbname = "SOL "

(GSI) INFO: vname = "DB6 "

(GSI) INFO: hostname = "UNKNOWN "

(GSI) INFO: sysname = "AIX"

(GSI) INFO: nodename = "dewall30"

(GSI) INFO: release = "1"

(GSI) INFO: version = "6"

(GSI) INFO: machine = "00C335F44C00"

(DB) INFO: /BI0/F0SMD_CA01 deleted/truncated #20090603142538

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

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

(DB6) [IBM][CLI Driver][DB2/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

/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20090603142538

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

Do i need to check any other log.

Regards

markus_doehr2
Active Contributor
0 Kudos

Usually R3load gives the SQL filename that it opened:

(SQL) INFO: Trying to open /migration/SOP_EXPORT/ABAP/DB/DB6/APPL0.SQL
(SQL) INFO: /migration/SOP_EXPORT/ABAP/DB/DB6/APPL0.SQL opened
(DB) INFO: /1CN/C3DSAP00002 created#20080705215557

It seems that the reason is because the initial creation of the .TSK files did not find that file.

Markus

Former Member
0 Kudos

Hello Markus

Any solution of how i can start for the whole package again then.?

Since i can see in the SAPDFACT.TSK file that many tables have been created.

Extracted output

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

grep "T /B" SAPDFACT.TSK

T /BI0/E0CCMARCDH C ok

T /BI0/E0CCMARCH C ok

T /BI0/E0CCMARSDH C ok

T /BI0/E0CCMARSH C ok

T /BI0/E0CCMSARC C ok

T /BI0/E0CCMSARCD C ok

T /BI0/E0CCMSARS C ok

T /BI0/E0CCMSARSD C ok

T /BI0/E0CCMSATIM C ok

T /BI0/E0CCMSATPH C ok

T /BI0/E0PPM_VC1 C ok

T /BI0/E0RSTT_C01 C ok

T /BI0/E0RSTT_C02 C ok

T /BI0/E0RSTT_C03 C ok

T /BI0/E0RSTT_C04 C ok

T /BI0/E0RSTT_C05 C ok

T /BI0/E0RSTT_C06 C ok

T /BI0/E0SMD_CA01 C ok

T /BI0/E0SMD_CA02 C ok

T /BI0/E0SMD_EA1D C ok

T /BI0/E0SMD_EA1H C ok

T /BI0/E0SMD_EA2D C ok

T /BI0/E0SMD_EA2H C ok

T /BI0/E0SMD_EA3D C ok

T /BI0/E0SMD_EA3H C ok

T /BI0/E0SMD_EA4D C ok

T /BI0/E0SMD_EA4H C ok

T /BI0/E0SMD_EA5D C ok

T /BI0/E0SMD_EA5H C ok

T /BI0/E0SMD_PE2D C ok

T /BI0/E0SMD_PE2H C ok

T /BI0/E0SMD_PERH C ok

T /BI0/E0SMD_PI2D C ok

T /BI0/E0SMD_SB1S C ok

T /BI0/F0CCMARCDH C ok

T /BI0/F0CCMARCH C ok

T /BI0/F0CCMARSDH C ok

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

Regards

Anthony

Edited by: Anthony D'souza on Jun 3, 2009 6:40 PM

markus_doehr2
Active Contributor
0 Kudos

> Any solution of how i can start for the whole package again then.?

If you check the .TSK files you'll see that the "P" entry is wrong (err).

The clean way would be to start over with the installation.

Can you check if those entries with "err" are listed in the SQL file?

Markus

Former Member
0 Kudos

>>>If you check the .TSK files you'll see that the "P" entry is wrong (err).

No my "P" (i.e Primary index---i feel) is not in error.

Its the "D" (i.e Data) entry which is in error.

Just the extract of the file "SAPDFACT.TSK"

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

T /BI0/F0SMD_CA01 C ok

P /BI0/F0SMD_CA01~0 C ok

I /BI0/F0SMD_CA01~01 C ok

I /BI0/F0SMD_CA01~02 C ok

I /BI0/F0SMD_CA01~04 C ok

I /BI0/F0SMD_CA01~05 C ok

I /BI0/F0SMD_CA01~06 C ok

I /BI0/F0SMD_CA01~07 C ok

I /BI0/F0SMD_CA01~08 C ok

I /BI0/F0SMD_CA01~09 C ok

I /BI0/F0SMD_CA01~10 C ok

I /BI0/F0SMD_CA01~11 C ok

I /BI0/F0SMD_CA01~12 C ok

I /BI0/F0SMD_CA01~13 C ok

D /BI0/F0SMD_CA01 I err

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

Regards

Anthony

markus_doehr2
Active Contributor
0 Kudos

Ok...

Since the affected table is a BI cube which is handled differently on the different databases the SQL scripts are necessary to avoid such problems.

I would, in your case, start over with the installation to be clean.

You could, however, delete/drop all the "ok" tables on database level manually, set all "ok" to "xeq" in the .TSK file and recreate the .cmd file by using the first R3load call in SAPDFACT.log.

I think though that it's less work to start again from scratch.

Markus

Former Member
0 Kudos

Hello Markus,

I have deleted all the table from the database and now when i re-run the R3load , i get the following error in the "SAPDFACT.log"

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

/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20090603170050

/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 21:47:44

/usr/sap/SOL/SYS/exe/run/R3load -i SAPDFACT.cmd -dbcodepage 4102 -k 1G5fdEM50TIIrBzjt6TE5Pae -l SAPDFACT.log -stop_on_error -loadprocedure fast LOAD

(DB) INFO: connected to DB

(GSI) INFO: dbname = "SOL "

(GSI) INFO: vname = "DB6 "

(GSI) INFO: hostname = "UNKNOWN "

(GSI) INFO: sysname = "AIX"

(GSI) INFO: nodename = "dewall30"

(GSI) INFO: release = "1"

(GSI) INFO: version = "6"

(GSI) INFO: machine = "00C335F44C00"

(SQL) INFO: Trying to open DFACT.SQL

(SQL) ERROR: Unable to open DFACT.SQL

(SQL) ERROR: OS error message: Permission denied

(SQL) ERROR: SQL list was not built successfully

(DDL) ERROR: check_sql_list() failed for /BI0/E0CCMARCDH

(DB) INFO: disconnected from DB

/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20090603170051

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

Now from this at leat it is trying to read the file , but its giving error.

I dont know from where exactly its trying to read the SQL files.Since i have copied it in the /DB/DB6 folder of the export diretory with all permission.

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

-rwxrwxrwx 1 soladm sapsys 42844 Jun 03 14:43 DODS.SQL

-rwxrwxrwx 1 soladm sapsys 133919 Jun 03 14:43 DFACT.SQL

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

Can you please guide me as to where the SQL files it is reading.

Regards

Anthony

Former Member
0 Kudos

Hello Markus,

Its done!!!

I copied the files in the installation folder and the R3load found it.

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

/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20090603172558

/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 21:47:44

/usr/sap/SOL/SYS/exe/run/R3load -i SAPDFACT.cmd -dbcodepage 4102 -k 1G5fdEM50TIIrBzjt6TE5Pae -l SAPDFACT.log -stop_on_error -loadprocedure fast LOAD

(DB) INFO: connected to DB

(GSI) INFO: dbname = "SOL "

(GSI) INFO: vname = "DB6 "

(GSI) INFO: hostname = "UNKNOWN "

(GSI) INFO: sysname = "AIX"

(GSI) INFO: nodename = "dewall30"

(GSI) INFO: release = "1"

(GSI) INFO: version = "6"

(GSI) INFO: machine = "00C335F44C00"

(SQL) INFO: Trying to open DFACT.SQL

(SQL) INFO: DFACT.SQL opened

(DB) INFO: /BI0/E0CCMARCDH created #20090603172559

(DB) INFO: /BI0/E0CCMARCDH~0 created #20090603172559

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

Thanks for you wonderfull support..

Thankyou

Regards

Anthony

markus_doehr2
Active Contributor
0 Kudos

> Its done!!!

>

> I copied the files in the installation folder and the R3load found it.

I was just about to write that )

Great to hear it's working!

Markus

Answers (0)