Skip to Content
0
Former Member
Nov 05, 2011 at 01:47 PM

Unicode import - Migration key error

101 Views

Hi

As per the documentation we left the migration key blank when starting the unicode import phase.

The import hit an error with the migration key .....

ERROR 2011-11-04 22:11:43.275

FCO-00011 The step testMigrationKey with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|testMigrationKey was executed with status ERROR ( Last error reported by the step :Process call '\usr\sap\T03\SYS\exe\run\R3load -dbcodepage 4102 -i test_MIGKEY.cmd -l test_MIGKEY.log -K' exits with error code 2. For details see log file(s) test_MIGKEY.log.).

test_MIGKEY.log reads

***********Beginning of data*************

C64U0377/R3LOADDB4: START OF LOG: 20111104221150

C64U0377/R3LOADDB4: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP

C64U0377/R3LOADDB4: version R6.40/V1.4 [UNICODE]

Compiled Jul 16 2011 02:10:27

C64U0377/R3LOADDB4 -dbcodepage 4102 -i test_MIGKEY.cmd -l test_MIGKEY.log -K

(DB) INFO: connected to DB

(RFF) ERROR: file SAPSSEXC.001 not found

C64U0377/R3LOADDB4: job finished with 1 error(s)

C64U0377/R3LOADDB4: END OF LOG: 20111104221152

***********End of Data*******************

We can not find SAPSSEXC.001 but do have a SAPSSEXC.010

Not sure if we lost something and need to re-run the export.

Thanks