46C Migration Oracle/HP-UX to MAXDB/SLE10 error: Duplicate value QCMT066

Question

To migrate a productive system from 46C to ECC600 I got an system copy export from our business partner.
The source system is running on HPUX/Oracle. The target system should be MAXDB/SLE10.
I run the import with R3setup and got error: Duplicate value QCMT066.
To try to continue the import I set in DBMIG.R3S:
[DBR3LOADEXEC_IND_ADA]
from STATUS=ERROR to STATUS=OK
[DBR3LOADVIEW_IND_ADA]
from STATUS=ERROR to STATUS=OK
[DBR3LICENSECREATE_IND_ADA]
STATUS=ERROR to STATUS=OK
[DBR3START_IND_ADA]
from STATUS=ERROR to STATUS=OK
Tthe system is coming up, but get: in SAPGUI: GEN_TABLE_NOT_EXISTS .. Table VSEOPARENT does not exist.
I believe that I have to run the import again. How can I solve the duplicate value QCMT066 problem?
Edited by: Trieu Chi Phung on Aug 4, 2009 4:01 PM

Answer 1

Answer of SAP:
Did you skip the error? because there errors in both SAPVIEW.log and
SAPAPPL1.log
The SAPVIEW is having error because the table VBKD was not imported yet, and this table belongs to package SAPAPPL1, so, you have to finish
import the SAPAPPL1 in the first place.
You have the error "Duplicate key in index" for table QCMT066
One of the most important things to do before a migration starts is to
look at the consistency between Database and ABAP DDIC (/DB02 > checks>
button Database<> ABAP/4 DDIC) and to look after QCM-Tables from pre-
viously failed table-conversions These temporary objects are used duringconversion (see attached note # 9385 this note is for 3.0F but explains
the situation).
I would like you to proceed as follows:
1. In the source-system check SE14 > Extras > Invalid Temp.
Tables and remove all entries from there
2. Switch to use sidadm create a new temp-directory and run 'R3ldct
without any parameters
3. Check the STR-files created and grep for entries starting with
QCM
4. For those objects use function module 'DD_NAMETAB_DELETE' and
remove them from the nametab
5. repeat the export from scratch
If you want a workaround on this, you can modify the <package>.STR file
and remove the entry QCMT066 and restart the import to continue.
However, this maybe tedious if you and lots of this kind of object.