Hi Gurus,

I'm installing with SAPinst Solman on windows server 2003. I got the following error message "

runMigrationMonitor was executed with status ERROR"

I made a ticket for that on the forum but my question was closed and assumed answered.

Before that John Feely (thanks for that) suggested me te following method

Make sure you have latest R3load version check sapsystemname is set correctly

and restart the process from the begining.

regards,

John Feely

Can somebody please explain to me the procedure to set SAPSYSTEMNAME=SID in SID environment?

Second issue: I have downloaded R3load last version on the service marketplace. But I have any clue how to use it?

Thanks for the help

SAP Managed Tags:
Windows Server

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

Hello Patrick,

to set variable on windows you need to go to System properties, tab Advanced, Environment Variables button in the bottom. Anyway from the information you've provided, environment variables and R3load would be OK as import of 27 packages completed successfully and only import of package SACONT01 is failing. Detailed error description will be in SACONT01.log file in inst_dir location (C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\). If you are still not sure what is causing problem after reading SACONT01.log paste it here.

Best regards

Igor

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello Igor,

Thanks for the response. Here is the log:

WARNING 2012-03-09 18:52:45.267

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

java version "1.4.2_36"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_36-b03)

Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_36-b03, mixed mode)

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

Loading of 'SAPNTAB' import package: OK

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

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

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

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

Loading of 'DSVASREPODOCS' import package: OK

Import Monitor jobs: running 2, waiting 25, completed 2, failed 0, total 29.

Import Monitor jobs: running 3, waiting 24, completed 2, failed 0, total 29.

Loading of 'SASACONT1' import package: OK

Import Monitor jobs: running 2, waiting 24, completed 3, failed 0, total 29.

Import Monitor jobs: running 3, waiting 23, completed 3, failed 0, total 29.

Loading of 'SAPSSEXC' import package: ERROR

Import Monitor jobs: running 2, waiting 23, completed 3, failed 1, total 29.

Import Monitor jobs: running 3, waiting 22, completed 3, failed 1, total 29.

Loading of 'REPOSRC' import package: OK

Import Monitor jobs: running 2, waiting 22, completed 4, failed 1, total 29.

Import Monitor jobs: running 3, waiting 21, completed 4, failed 1, total 29.

Loading of 'SAPAPPL1' import package: OK

Import Monitor jobs: running 2, waiting 21, completed 5, failed 1, total 29.

Import Monitor jobs: running 3, waiting 20, completed 5, failed 1, total 29.

Loading of 'DOKCLU' import package: OK

Import Monitor jobs: running 2, waiting 20, completed 6, failed 1, total 29.

Import Monitor jobs: running 3, waiting 19, completed 6, failed 1, total 29.

Loading of 'SAPAPPL0' import package: ERROR

Import Monitor jobs: running 2, waiting 19, completed 6, failed 2, total 29.

Import Monitor jobs: running 3, waiting 18, completed 6, failed 2, total 29.

Loading of 'SAPSSRC' import package: OK

Import Monitor jobs: running 2, waiting 18, completed 7, failed 2, total 29.

Import Monitor jobs: running 3, waiting 17, completed 7, failed 2, total 29.

Loading of 'SAPAPPL2' import package: OK

Import Monitor jobs: running 2, waiting 17, completed 8, failed 2, total 29.

Import Monitor jobs: running 3, waiting 16, completed 8, failed 2, total 29.

Loading of 'STERM_TEXT' import package: OK

Import Monitor jobs: running 2, waiting 16, completed 9, failed 2, total 29.

Import Monitor jobs: running 3, waiting 15, completed 9, failed 2, total 29.

Loading of 'DD03L' import package: OK

Import Monitor jobs: running 2, waiting 15, completed 10, failed 2, total 29.

Loading of 'E071K' import package: OK

Import Monitor jobs: running 1, waiting 15, completed 11, failed 2, total 29.

Import Monitor jobs: running 2, waiting 14, completed 11, failed 2, total 29.

Import Monitor jobs: running 3, waiting 13, completed 11, failed 2, total 29.

Loading of 'SAPSDIC' import package: OK

Import Monitor jobs: running 2, waiting 13, completed 12, failed 2, total 29.

Import Monitor jobs: running 3, waiting 12, completed 12, failed 2, total 29.

Loading of 'SAPSPROT' import package: OK

Import Monitor jobs: running 2, waiting 12, completed 13, failed 2, total 29.

Loading of 'ATAB' import package: OK

Import Monitor jobs: running 1, waiting 12, completed 14, failed 2, total 29.

Import Monitor jobs: running 2, waiting 11, completed 14, failed 2, total 29.

Import Monitor jobs: running 3, waiting 10, completed 14, failed 2, total 29.

Loading of 'SAPSDOCU' import package: OK

Import Monitor jobs: running 2, waiting 10, completed 15, failed 2, total 29.

Loading of 'SAPSLEXC' import package: OK

Import Monitor jobs: running 1, waiting 10, completed 16, failed 2, total 29.

Loading of 'SEOSUBCODF' import package: OK

Import Monitor jobs: running 0, waiting 10, completed 17, failed 2, total 29.

Import Monitor jobs: running 1, waiting 9, completed 17, failed 2, total 29.

Import Monitor jobs: running 2, waiting 8, completed 17, failed 2, total 29.

Import Monitor jobs: running 3, waiting 7, completed 17, failed 2, total 29.

Loading of 'SAPSLOAD' import package: OK

Loading of 'SAPPOOL' import package: OK

Import Monitor jobs: running 1, waiting 7, completed 19, failed 2, total 29.

Loading of 'SAPCLUST' import package: OK

Import Monitor jobs: running 0, waiting 7, completed 20, failed 2, total 29.

Import Monitor jobs: running 1, waiting 6, completed 20, failed 2, total 29.

Import Monitor jobs: running 2, waiting 5, completed 20, failed 2, total 29.

Import Monitor jobs: running 3, waiting 4, completed 20, failed 2, total 29.

Loading of 'SAPDDIM' import package: OK

Import Monitor jobs: running 2, waiting 4, completed 21, failed 2, total 29.

Loading of 'SAPDODS' import package: OK

Import Monitor jobs: running 1, waiting 4, completed 22, failed 2, total 29.

Loading of 'SAPDFACT' import package: OK

Import Monitor jobs: running 0, waiting 4, completed 23, failed 2, total 29.

Import Monitor jobs: running 1, waiting 3, completed 23, failed 2, total 29.

Import Monitor jobs: running 2, waiting 2, completed 23, failed 2, total 29.

Import Monitor jobs: running 3, waiting 1, completed 23, failed 2, total 29.

Loading of 'SACONT01' import package: ERROR

Import Monitor jobs: running 2, waiting 1, completed 23, failed 3, total 29.

Loading of 'SAP0000' import package: OK

Import Monitor jobs: running 1, waiting 1, completed 24, failed 3, total 29.

Loading of 'SAPUSER' import package: OK

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

WARNING[E] 2012-03-09 18:52:45.736

CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR 2012-03-09 18:52:46.564

FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|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|runMigrationMonitor was executed with status ERROR .

INFO 2012-03-10 14:33:32.375

An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|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|runMigrationMonitor".

INFO 2012-03-10 14:34:11.203

Switched to user: s01adm.

INFO 2012-03-10 14:34:12.515

Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\import_monitor.java.log.

INFO 2012-03-10 14:34:12.671

Switched to user: s01adm.

INFO 2012-03-10 14:34:12.718

Working directory changed to C:\PROGRA~1\SAPINS~1\SOLMAN\SYSTEM\ORA\CENTRAL\AS.

INFO 2012-03-10 14:34:12.734

Output of C:\j2sdk1.4.2_36-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.

WARNING 2012-03-10 14:59:02.671

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

java version "1.4.2_36"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_36-b03)

Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_36-b03, mixed mode)

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

Import Monitor jobs: running 2, waiting 2, completed 25, failed 0, total 29.

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

Loading of 'SACONT01' import package: ERROR

Import Monitor jobs: running 2, waiting 1, completed 25, failed 1, total 29.

Loading of 'SAPAPPL0' import package: OK

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

Loading of 'SAPSSEXC' import package: OK

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

WARNING[E] 2012-03-10 14:59:02.734

CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR 2012-03-10 14:59:03.265

INFO 2012-03-10 15:04:48.500

INFO 2012-03-10 15:04:50.328

Switched to user: s01adm.

INFO 2012-03-10 15:04:50.546

Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\import_monitor.java.log.

INFO 2012-03-10 15:04:50.562

Switched to user: s01adm.

INFO 2012-03-10 15:04:50.562

Working directory changed to C:\PROGRA~1\SAPINS~1\SOLMAN\SYSTEM\ORA\CENTRAL\AS.

INFO 2012-03-10 15:04:50.562

Output of C:\j2sdk1.4.2_36-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.

WARNING 2012-03-10 15:05:21.312

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

java version "1.4.2_36"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_36-b03)

Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_36-b03, mixed mode)

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

Loading of 'SACONT01' import package: ERROR

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

WARNING[E] 2012-03-10 15:05:21.328

CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR 2012-03-10 15:05:21.671

Thank for your advice

Hello Igor,

I paste also the SAPCONT001.log here:

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20120309185214

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]

Compiled Jan 24 2008 01:41:44

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe -ctf I E:\SAP Install\SAPCD\51033518_EXP_SOLMAN\51033518_2\EXP3\DATA\SACONT01.STR C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\DDLORA_LRG.TPL SACONT01.TSK ORA -l SACONT01.log

(RTF) ########## WARNING ###########

Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: job completed

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20120309185214

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20120309185214

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]

Compiled Jan 24 2008 01:41:44

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe -i SACONT01.cmd -dbcodepage 4103 -l SACONT01.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(RFF) ERROR: file SACONT01.001 not found

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20120309185215

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20120310143422

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]

Compiled Jan 24 2008 01:41:44

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe -i SACONT01.cmd -dbcodepage 4103 -l SACONT01.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(RFF) ERROR: file SACONT01.001 not found

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20120310143433

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20120310150454

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]

Compiled Jan 24 2008 01:41:44

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe -i SACONT01.cmd -dbcodepage 4103 -l SACONT01.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(RFF) ERROR: file SACONT01.001 not found

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)

C:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20120310150455

Hope it will help

Hi,

The main cause of ORA-01403 is that the table SAPUSER does not contain any entries. Therefore, proceed as follows:

Use the following BRCONNECT call (BRCONNECT 6.10 or higher) to set the password consistently in SAPUSER and in the Oracle DDIC:

brconnect -u system/<password> -f chpass -o <sapowner> -p <password>

Alternatively, you can insert it in SAPUSER manually.

INSERT INTO "OPS$<sid>ADM".SAPUSER VALUES ('<sapowner>', '<password>');

Another possible cause is that SAPUSER contains incorrect entries. The system always uses the user name to select from SAPUSER. Therefore, you must ensure that the user name is always uppercase (SAPR3 or SAP<sid>) and that it corresponds exactly to the value of the environment variable dbs_ora_schema if SAP<sid> is used.

Regards,

Venkata S Pagolu

Hello Venkata,

Thanks for the response. I found brconnect.exe in c:\usr\<sid>\SYS\exe\uc\OS. What do I have to do. i double click but nothing is happening. Do I have to perform it in comman prompt?

Can you give me an example.

Thanks

Hi,

you need to do it in command prompt.

This is the command to change password of Oracle Database User :

From BRTOOLS= BRTOOLS -> 8 – Additional functions -> 4 – Change password of database user -> continue, then you can type your new password as below (ex, SID = DEV):

BR0801I BRCONNECT 7.00 (18)

BR0280I BRCONNECT time stamp: 2009-07-14 01.52.04

BR0263I Enter password for database user ‘SAPCR2′ (maximum 30 characters):

BR0801I BRCONNECT 7.00 (18)
BR0280I BRCONNECT time stamp: 2009-07-14 01.52.04
BR0263I Enter password for database user ‘SAPDEV’ (maximum 30 characters):_

or you can type quick brconnect command :

brconnect [-u system/<system_password>] –f chpass –u <user_name>

or you can go through SQL commands :

sqlplus “/as sysdba”
alter user ‘username’ identified by ‘password’;

Hello,

I went throuh SQL command but I got the following error:

alter user '<sid>adm' identified by 'password'

ORA-01935: missing user or role name

I've also tried the followinf syntax in command prompt:

c:\>brconnect [-u system/<systempassword>] -f chpass -u SAPs00

error : 'brconnect' is not recognized as an internal or external command, operable program or batch file.

Hi,

Did you tried with first option

From BRTOOLS= BRTOOLS -> 8 – Additional functions -> 4 – Change password of database user -> continue, then you can type your new password as below (ex, SID = DEV):

BR0801I BRCONNECT 7.00 (18)

BR0280I BRCONNECT time stamp: 2009-07-14 01.52.04

BR0263I Enter password for database user ‘SAPCR2′ (maximum 30 characters):

BR0801I BRCONNECT 7.00 (18)
BR0280I BRCONNECT time stamp: 2009-07-14 01.52.04
BR0263I Enter password for database user ‘SAPDEV’ (maximum 30 characters):_
Regards,
Venkata S Pagolu

Hello Patrick,

issue with the import is that dump file SACONT01.001 is missing. It should be located in here in your case:

E:\SAP Install\SAPCD\51033518_EXP_SOLMAN\51033518_2\EXP3\DATA

If it's really missing there, try to download 51033518 dvd again and unpack to different location and compare content (I have now checked content of dvd and file is present there).

regards

Igor

Hi Patrick,

Can you follow below and check ORACLE is up and you can able to connect.

click on start

click on run

enter CMD and press enter

type sqlplus "/nolog"

connect sys as sysdba

enter password ( same which you given for <sapsid>adm user during installation steps )

Let me know are you able to connect successfully ?

Regards,

Nikunj Thaker

Hi Igor,

The file is effectively missing, I'v just checked that out. I will try to download again.Can you give the exact version for the DVD.

Meanwhile I will try others gurus solutions.

Regards

Hi Patrick,

DVD number is 51033518.

About the other suggestions, for this error in log file:

DbSl Trace: ORA-1403 when accessing table SAPUSER

if you will check, this error is followed by

(DB) INFO: connected to DB

This is caused by the fact that SAPUSER data are not loaded yet, you can see this error in all other import logs as well (C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\SAPAPPL0.log for instance). So R3trans can not see SAPUSER table in DB but connects sucessfully anyway.

regards

Igor

Hello Igor,

I tried three times to download the export solman software (51033518). I downloaded the six parts. Now i want to unrar al the 6 files. I selected all of the rar files, then try to unpack them. But i have problems always that i try to do it : “Packed data CRC failed in directory, the volume is corrupt”.

I don't know what else I can do.

PS: Sorry for the late reaction.

Regards

Hello Patrick,

downloaded DVD files would be 5 of *.rar type and one *.exe type. You need to run the *.exe self-extracting file (which will extract all).

Best regards

Igor

Ask a Question

Top Q&A Solution Author

User

Count

How to set variable SAPSYSTEMNAME=SID

runMigrationMonitor was executed with status ERROR"

Accepted Solutions (0)

Answers (1)

Answers (1)

Re: Object store secret default-object-store-secre...

odata Metadata issue for standard service

Re: Dynamic SemanticObject for Intent Based Naviga...

Lookup logic in Integration suite

Re: Dynamic SemanticObject for Intent Based Naviga...