cancel
Showing results for 
Search instead for 
Did you mean: 

Program "Migration Monitor" exists with error code 103

Former Member
0 Kudos

Hi All,

Im currently doing a dual stack install of NW 7.3 incl. EHP 1. At the "Import ABAP" step in the following error --> Program "Migration Monitor" exists with error code 103.

I have update all versions of java.

Checked the swap sizes

Increased the RAM (16GB)

Still no resolution.

Import_monitor.log: (last couple of lines)

ERROR: 2012-10-17 09:20:33 com.sap.inst.migmon.LoadTask run

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

Process 'C:\usr\sap\V02\SYS\exe\uc\NTAMD64\R3load.exe -ctf I "C:\Install\51043228_ InstExp\DATA_UNITS\EXP3\DATA\SAPNTAB.STR" "C:\Program Files\sapinst_instdir\NW731\INSTALL\NW73\MSS\STD\AS\DDLMSS.TPL" SAPNTAB.TSK MSS -l SAPNTAB.log' exited with return code 2.

For mode details see 'SAPNTAB.log' file.

Standard error output:

sapparam: sapargv(argc, argv) has not been called!

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

WARNING: 2012-10-17 09:21:01

Cannot continue import because not all import packages with data conversion tables are loaded successfully.

WARNING: 2012-10-17 09:21:01

1 error(s) during processing of packages.

INFO: 2012-10-17 09:21:01

Import Monitor is stopped.

___________________________________________________________________

Import_monitor_java.log

java version "1.6.0_29"

Java(TM) SE Runtime Environment (build 6.1.037)

SAP Java Server VM (build 6.1.037 1.6-b11, Jan  4 2012 01:06:07 - 61_REL - optU - windows amd64 - 6 - bas2:164951 (mixed mode))

Import Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29.

Loading of 'SAPNTAB' import package: ERROR

Import Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29.



Please help!

Thanks

Nish


Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Nish,

Check the SAPNTAB.TSK file and verify any table in marked with "ok" exist in the database.

Did you see any error in database log file ( you did not mention about your DB and OS ).

Error :

sapparam: sapargv(argc, argv) has not been called!

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

This is a warning you can ignore it.

Regards,

Dipam

Former Member
0 Kudos

Hi Dipam,

Thanks for the reply.

This is the content of the SAPNTAB.TSK:

T SVERS C ok

P SVERS~0 C ok

D SVERS I ok

T DDNTF C ok

P DDNTF~0 C ok

D DDNTF I ok

T DDNTF_CONV_UC C ok

P DDNTF_CONV_UC~0 C ok

D DDNTF_CONV_UC I ok

T DDNTT C ok

P DDNTT~0 C ok

D DDNTT I ok

T DDNTT_CONV_UC C ok

P DDNTT_CONV_UC~0 C ok

D DDNTT_CONV_UC I ok

-----------------------------------------------------

Sorry for not mentioning other details.

OS: Win Server 2008 R2

DB: MS SQL Server 2008 R2.

Unfortunately Im still getting the error when trying to install.

All feed back is appreciated.

Thanks

Nish

Former Member
0 Kudos

Hi Nish,

Could you please check any .bck file exist for SAPNTAB package and compare both .bck and .TSK file for this package. Basic idea is to find out which table is causing issue for import. If you get the table name - you may create manually ( table creation statement can be found from SAPNTAB.log ) and set the status of that particular table to "OK" in the .TSK file and proceed with installation.

Also you can try with R3load --merge_only for the package SAPNTAB and continue with installation.

Check the syxtax for the merge option using R3load -help.

Even though your log file did not say any thing about generic error, check file system, database log too.

Regards,

Dipam