system copy error during import abap phase

[Former Member]

Hi ,

We  are performing system copy from PRD to sand box. We have successfully  exported dump from source system( Production server). While importing in  target system ( Sand Box) we are getting error at Import ABAP phase.   Please find the attached sapinst log file and help us to resolve,.

Thank you.

SURYA

log.txt.zip

[former_member192421]

Hi Surya,

Are the Production and QA systems on same release and patch level?

Regards,

Rajkumar

[former_member192421]

Hi Surya,

Also from the log it was found that

WARNING 2013-10-29 10:17:55.552

Execution of the command "C:\j2sdk1.4.2_17\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103

It seems some problem with Migration Monitor. Please check below notes.

SAP Note 1454575

SAP Note 1454576

SAP Note 1595840

SAP Note 784118

Hope this helps....Anyways HAPPY DIWALI.

Regards,

Rajkumar

[former_member192421]

Hi Surya,

Could you please attach the import_monitor.log log?

Also you can refer to the below thread.

http://scn.sap.com/thread/1764236

Regards,

Rajkumar

[Sriram2009]

Hi Surya

1.Install a newer DBSL patch  and then restart SAPinst

2. could you share the SAP version?

Regards

Sriram

[Former Member]

Hi Sriram,

SAP Version : ECC6.0 SR3

Thanks,

SURYA

[Sriram2009]

Hi Surya

What is the kernel version on NW07 SR3?it should be kernel 353 or 333 along with DBSL patch

Regards

Sriram

Wish you happy Diwali

[former_member196492]

Hi,

Kindly check the log import_monitor.java.log and apply/update the latest R3load and retry again.

Thanks

[Former Member]

Hi,

I'm attaching the import_monitor.java.log file here kindly look into that and suggest us some solution.

Thanks,

SURYA

importjava.txt.zip

[Jörg_Brockmann]

Hello,

the 'imort_monitor_java.log' file is only an 'result list' for the imported packages.

Each listed package in this file has an single import log file.

Please check the individual log files for the packages with the status 'error'.

There you will find the cause of the problem(s).

best regards

Jörg