R3Load import fails - System Copy

[sheril_sasidharan]

hi,

We are performing a system copy via export/import method. During import it fails during ABAP import with the following errors:

OS - V7R1M0

PTFs are uptodate

The source system is ECC 6.0 Unicode on kernel 721 EXT patch level 600

ERROR: 2016-05-23 00:13:12 com.sap.inst.migmon.LoadTask run                 

Loading of 'SAPAPPL1' import package is interrupted with R3load error.      

Process '/usr/sap/DEA/SYS/exe/run/R3load -i SAPAPPL1.cmd -dbcodepage 4102 -l

SAPAPPL1.log -nojournal' exited with return code 2.                         

For mode details see 'SAPAPPL1.log' file.                                   

Log of SAPAPPL1.log

(DB) ERROR: DDL statement failed

(ALTER TABLE "VBSS" DROP PRIMARY KEY )

DbSlExecute: rc = 99

  (SQL error -539)

  error message returned by DbSl:

SQL0539 - Table VBSS in R3DEADATA does not have a primary or unique key. (253

801/SAPIUSR/QP0ZSPWP)

(DB) ERROR: DDL statement failed

(ALTER TABLE "VBSS" ADD CONSTRAINT "VBSS+0" PRIMARY KEY ( "MANDT", "SAMMG",

"VBELN" ) )

DbSlExecute: rc = 99

  (SQL error -603)

  error message returned by DbSl:

SQL0603 - Unique index cannot be created because of duplicate keys. (253801/S

  APIUSR/QP0ZSPWP)           

(DB) ERROR: DDL statement failed                                            

(ALTER TABLE "VBUK" DROP PRIMARY KEY )                                     

DbSlExecute: rc = 99                                                       

  (SQL error -539)                                                          

  error message returned by DbSl:                                           

SQL0539 - Table VBUK in R3DEADATA does not have a primary or unique key. (253

801/SAPIUSR/QP0ZSPWP)                                                       

(IMP) INFO: a failed DROP attempt is not necessarily a problem              

(DB) ERROR: DDL statement failed                                            

(ALTER TABLE "VBUK" ADD CONSTRAINT "VBUK+0" PRIMARY KEY ( "MANDT", "VBELN" )

)                                                                          

DbSlExecute: rc = 99                                                       

  (SQL error -603)                                                          

  error message returned by DbSl:                                           

SQL0603 - Unique index cannot be created because of duplicate keys. (253801/S

APIUSR/QP0ZSPWP)                                                            

(DB) INFO: disconnected from DB                                             

/usr/sap/DEA/SYS/exe/run/R3load: job finished with 2 error(s)               

/usr/sap/DEA/SYS/exe/run/R3load: END OF LOG: 20160522212707                 

Spool of R3Load

Attached

Any idea on how this can be resolved ?

OS is V7R1M0

PTFs are uptodate

The source system is ECC 6.0 Unicode on kernel 721 EXT patch level 600

Thanks

Sheril

QPJOBLOG254348.txt.zip

[Former Member]

Hi Sheril,

I would start by checking if there are actually dup key rows in both the target and/or the source system.

Something like this should help you find out:

select MANDT,VBELN, count(*) from R3<sid>DATA/VBUK group by MANDT,VBELN order by 3 desc

You should be able to determine if the problem really exists in the target library and if it is already an issue at the source system.

If no dup keys exist in the source table, you should try to find out how the source and target table contents differ from each other and if the problem is that the data has change (ie truncation) or if there are row that were imported multiple times.

Regards,

Luis Gonzalez

[sheril_sasidharan]

hi Luis,

I check the duplicate entry in source and target and i could see duplicate entries in the target mainly for one of the client (300) in the system. 9545 duplicate entries.

Any ideas on how to move forward ?

Thanks

[volker_gldenpfennig]

Hi Sheril,

I have never had an issue like this, that was NOT caused in the source DB.

Did you do the COUNT(*) as Luis suggested. If this should be lower in the source, I would use CPYF in the source to a different library and try again the count.

If you just want to get over this error message, I would copy the data to a different table on the target system and use CLRPFM - then it can create the key - BUT: then the system is no longer consistent - even when you do copy the data back with ERRLVL(*NOMAX).

Regards,

Volker Gueldenpfennig, consolut international ag

[sheril_sasidharan]

Hi Volker,

I did exactly like Luis suggested. Source is clean and target is the one which has duplicates.

Can we just drop these table VBSS and VBUK from the target, edit the TSK file for R3Load and then retry the import from SWPM ?

Thanks

Sheril

[volker_gldenpfennig]

Hi Sheril,

yes, as I said: there can be done ugly hacks - editing the TSK file is one of them ... then it will be "successful" ...

good luck!

Regards,

Volker Gueldenpfennig, consolut international ag