cancel
Showing results for 
Search instead for 
Did you mean: 

SOLMAN 4.0(with MaxDB) IMPORT SAP error

Former Member
0 Kudos

Hallo Everyone,

I'm installing <b>SOLMAN 4.0(with MaxDB)</b> on the <u>VMWare</u> with <u>java 1.4.2_09</u>.

I've got many errors that it has been resolved, thanks to your help .

But, when I'm getting close to the end of the installation.

I become on <b>step 4</b> (Execute Service) an error by <b>IMPORT SAP</b>.

I search for solution to it for two days. I try to serialize the Jobs(i.e. from 3 to 1 job) it took many hours with buggy bugs but in the end it didn't work.

How Next??? 'Migration Monitor' exits with error code 103

Best Regards,

Kais

P.s. I'm waiting for your helpful answers.

-


WARNING 2007-04-24 18:01:28

Execution of the command "C:\j2sdk1.4.2_09\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ADA -importDirs C:\Sapinst\SOLMANEXPORT\EXP1;C:\Sapinst\SOLMANEXPORT\EXP2;C:\Sapinst\SOLMANEXPORT\EXP3;C:\Sapinst\SOLMANEXPORT\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -nolog -c 0" -trace all -sapinst" finished with return code 103. Output:

java version "1.4.2_09"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)

Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)

Import Monitor jobs: running 1, waiting 5, completed 12, failed 0, total 18.

Import Monitor jobs: running 2, waiting 4, completed 12, failed 0, total 18.

Import Monitor jobs: running 3, waiting 3, completed 12, failed 0, total 18.

Loading of 'SAPSSEXC' import package: ERROR

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

Loading of 'SAPAPPL1' import package: ERROR

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

Loading of 'SAPAPPL0' import package: ERROR

Import Monitor jobs: running 0, waiting 3, completed 12, failed 3, total 18.

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

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

Loading of 'SAPSSRC' import package: ERROR

Import Monitor jobs: running 1, waiting 1, completed 12, failed 4, total 18.

Loading of 'SAPAPPL2' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 12, failed 5, total 18.

ERROR 2007-04-24 18:01:28

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

ERROR 2007-04-24 18:01:28

FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|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 .<b></b>

Message was edited by:

Kais El Kara

Accepted Solutions (1)

Accepted Solutions (1)

raguraman_c
Active Contributor
0 Kudos

Hi,

The problem would have due to the fact that the database space allocation was insufficient.

The default amount of volumes created by the installer was too low. Also increased the virtual memory

(Run the pre install check).

Also check this link.

http://sap.ittoolbox.com/groups/technical-functional/sap-basis/solution-manager-40-sr1-installation-...

And check the reply of Frank MeertenS in this link.

This should solve your problem.

Feel free to revert back.

--Ragu

Message was edited by:

Raguraman C

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Ragu,

I used the Prerequisites check. The Problem was with the virtual memory.

I told Windows to manage alone the size(System managed size) but it seem's that he manage less memory then the Installation needs(about 1000MB).

As I did select the Option "Custom size" but I could only allocate(Max) 4096MB(because of windows 32bit) and it still less then 4321MB(Prerequisites didn't success).

Also, I tried to fix the other Problem.

I follow the instruction from "Frank Meertens" but I've got another Problem then that he explains.

In the SAPAPPL(0 -> 2).TCK I couldn't find an ERROR it was all OK.

The only thinks that I've found was in the R3load.exe.log.

Could you please tell me what's wrong on this log-file.

Regards,

Kais

P.s. I think it has something to do with Database MaxDB

-


<b>Also A Fragment of SAPAPPL0.log</b>

C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070426162350

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

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

Compiled Sep 1 2006 00:38:35

C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -nolog -c 0

DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:database not running))

(DB) ERROR: db_connect rc = 256

DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:database not running))

(DB) ERROR: DbSlErrorMsg rc = 99

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

C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070426162351

C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070426162502

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

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

Compiled Sep 1 2006 00:38:35

C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -nolog -c 0

DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:database not running))

(DB) ERROR: db_connect rc = 256

DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:database not running))

(DB) ERROR: DbSlErrorMsg rc = 99

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

C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070426162502

-


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

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070425160956

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

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

Compiled Sep 1 2006 00:38:35

C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe -testconnect

DbSl Trace: prepare() of C_0000, rc=1, rcSQL=-942 (POS(28) Unknown table name:SVERS)

DbSl Trace: SQL PREPARE on connection 0, rc=-942 (POS(28) Unknown table name:SVERS)

(DB) INFO: connected to DB

(DB) INFO: The MaxDB logwriter is switched off#20070425160956

(DB) INFO: disconnected from DB

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

C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070425160956

Message was edited by:

Kais El Kara

Message was edited by:

Kais El Kara

roland_mallmann
Advisor
Advisor
0 Kudos

Hi,

from a MaxDB perspective, are you sure that the MaxDB is online at that time? Please take a look into the MaxDB knldiag and/or knldiag.err file at the exact same timeinterval to see if you can find any related error messages. If you find any, please post them here.

Addionally, could you please post which exact MaxDB version you are using (incl. Buildnr.)?

Thanks & regards,

Roland

Former Member
0 Kudos

Hi Roland,

-


MaxDB 7.6.00 Build 037-121-149-748

-


The DBMCLI from MaxDB is running. But the SQLCLI is not.

I have an error like that * -10709: Connection failed (RTE:database not running).

I haven't found any error on knldiag.err.

Thanks for Help.

Regards,

Kais

<b>knldiag.err</b>

-


Date Time TID(hex) Typ MsgID Label Message-Text

-


2007-04-25 15:57:29 --- Starting GMT 2007-04-25 13:57:29 7.6.00 Build 035-123-139-084

2007-04-25 16:09:41 ___ Stopping GMT 2007-04-25 14:09:41 7.6.00 Build 035-123-139-084

2007-04-25 16:09:43 --- Starting GMT 2007-04-25 14:09:43 7.6.00 Build 035-123-139-084

2007-04-27 14:49:41 --- Starting GMT 2007-04-27 12:49:41 7.6.00 Build 037-121-149-748

Message was edited by:

Kais El Kara

roland_mallmann
Advisor
Advisor
0 Kudos

Hi,

please make sure:

a) the DB is in ONLINE state, by issueing (from the commandline):

dbmcli -d D01 -u <DBM-user>,<password> db_state

b) the Xserver (it's a service on the Windows platform) is running:

x_server start

Regards,

Roland

Former Member
0 Kudos

Hi Roland,

The SQLCLI works know. Thanks to your help.

I've just switch to user <SAPID>adm and followed your instructions.

But the SOLMAN 4.0 Installation doesn't want to be fixed.

I don't really knows how to solve this Problem.

Best Regards,

Kais

P.s. I hope finding a solution at the weekend

roland_mallmann
Advisor
Advisor
0 Kudos

Hi,

can you try a 'R3trans -d' and tell me the result (i.e. copy the output of the command AND the contents of the then created 'trans.log' file)?

Regards,

Roland

Edit: sry, meant R3trans instead of R3Load

Message was edited by:

Roland Mallmann

Former Member
0 Kudos

Hi Roland,

I'm sorry to reply you late. But, because I'haven't worked this later days.

I wish that you find the solution for this Problem.

Thanks for your help.

Best Regards,

Kais

-


The command's contains.

This is R3trans version 6.14 (release 700 - 18.09.06 - 09:35:00).

unicode enabled version

R3trans finished (0000).

Message was edited by:

Kais El Kara

roland_mallmann
Advisor
Advisor
0 Kudos

Hi,

'R3trans -d' seems to work fine, as it shows the returncode 0000.

With which user are you installing the SOLMAN 4.0?

Regards,

Roland

murray_lahn
Participant
0 Kudos

Silly question, but are the MaxDB database logs full? I got caught on that a couple times.

roland_mallmann
Advisor
Advisor
0 Kudos

Hi,

can you please remove the trans.log file content? It's no longer needed and blows the size of the thread out of proportions.

Thanks & regards,

Roland

Former Member
0 Kudos

Hi,

I've installed SOLMAN 4.0 with the Administrator user.

The MaxDB is running on the user <SAPID>adm

Regards,

Kais

Message was edited by:

Kais El Kara

roland_mallmann
Advisor
Advisor
0 Kudos

Hi again,

btw. did you open an official OSS message for your issue, as it seems you're an official SAP customer?

Regards,

Roland