Netweaver Installation, error "import ABAP"

[Former Member]

Hello Everyone,

After finally installing the Solution Manager 4.0 and Generating the SAP Solution Manager Key.

I have started to install Netweaver 2004s, after some steps of configuration.

I finally got stucked as phase 18 "import ABAP".

So, this error isn't new at all. I had to deal with it at Solman 4.0 installation, but I thought it has something to do with the java version(j2se1.4_09).

But it wasn't the only reason.

Now, I really don't know which action should I made, to ensure that the Netweaver Installation finally end.

This's the best actions that I made:

- I copied all the DVDs to the local directory.

- I used the J2SE1.4_09

- I even parallelized the jobs from 3 to 1(by the configuration steps), which has contributed to end the installation of Solman4.0.

Now, I hope soon that I find a solution.

Ps. Thanks for your help,

Best Regards,

Kais

[markus_doehr2 · Accepted solution]

If you have installation errors, it's always advised to post logfiles and system environment (Operating system (version), Database (version))

If you have an error on ABAP import, those errors will be logged in your installation directory as

packetname.log

If you look at the logfile of sapinst, it will tell you in which logfile to look for the error.

Post that error here and we may help you.

--

Markus

[Former Member · Accepted solution]

Hello Markus,

Thank you for responding.

This is how the log file look like.

--

Kais

-

---

INFO 2007-07-25 22:22:03

Creating file C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS\import_monitor.java.log.

INFO 2007-07-25 22:22:03

Working directory changed to C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS.

INFO 2007-07-25 22:22:03

Output of C:\j2sdk1.4.2_09\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ADA -importDirs "C:\Sapinst\Netweaver 2004s Export\EXP1;C:\Sapinst\Netweaver 2004s Export\EXP2;C:\Sapinst\Netweaver 2004s Export\EXP3" -installDir "C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 2 -monitorTimeout 30 -loadArgs " -nolog -c 0" -trace all -sapinst is written to the logfile import_monitor.java.log.

WARNING 2007-07-25 22:22:33

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\Netweaver 2004s Export\EXP1;C:\Sapinst\Netweaver 2004s Export\EXP2;C:\Sapinst\Netweaver 2004s Export\EXP3" -installDir "C:\Program Files\sapinst_instdir\NW04S\SYSTEM\ADA\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\S01\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 2 -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 17, completed 0, failed 0, total 18.

Loading of 'SAPSDIC' import package: ERROR

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

ERROR 2007-07-25 22:22:33

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-07-25 22:22:33

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|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 2007-07-25 22:22:37

An error occured and the user decide to stop.\n Current step "|NW_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|runMigrationMonitor".

-

---

SAPSDIC.log

This is another error part of the SAPSDIC log file

-

---

(IMP) INFO: a failed DROP attempt is not necessarily a problem

ERROR : Prepare/modify for GetPages failed(dbrc=26).

(SQL error 0)

error message returned by DbSl:

(DB) ERROR: DDL statement failed

(DROP INDEX "VRSX2~1" ON "VRSX2")

DbSlExecute: rc = 103

(SQL error -4011)

error message returned by DbSl:

(IMP) INFO: a failed DROP attempt is not necessarily a problem

ERROR : Prepare/modify for GetPages failed(dbrc=26).

(SQL error 0)

error message returned by DbSl:

(DB) ERROR: DDL statement failed

(DROP INDEX "VRSX3~1" ON "VRSX3")

DbSlExecute: rc = 103

(SQL error -4011)

error message returned by DbSl:

(IMP) INFO: a failed DROP attempt is not necessarily a problem

ERROR : Prepare/modify for GetPages failed(dbrc=26).

(SQL error 0)

error message returned by DbSl:

(DB) ERROR: DDL statement failed

(DROP INDEX "VRSX4~1" ON "VRSX4")

DbSlExecute: rc = 103

(SQL error -4011)

error message returned by DbSl:

(IMP) INFO: a failed DROP attempt is not necessarily a problem

ERROR : Prepare/modify for GetPages failed(dbrc=26).

(SQL error 0)

error message returned by DbSl:

(DB) INFO: disconnected from DB

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

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

[markus_doehr2 · Accepted solution]

Those are not the main errors - as the import states, a failed "drop" doesn´t mean an error. Check more above for errors...

--

Markus

[raguraman_c · Accepted solution]

Hi,

One of these would solve your problem.

1. When the installation fails, check if DB is running, if not restart the DB services and continue with the installation.

2. It might be due to the fact that the database space allocation was insufficient. The default amount of volumes created by the installer would be low.

3. Also increase the virtual memory (Run the pre install check). Give sufficient virtual memory.

Feel free to revert back.

--Ragu

[Former Member · Accepted solution]

Hi Raguraman,

My MaxDB Database is running, the service DB is running as fast and not as slow.

The Database space allocation is sufficient.

I allocated the default value + some other space using the MaxDB tool manager.

I have also a sufficient virtual memory about 11GB.

Using this below command. I tried to finish some processes and I have succeded.

<b>R3Load -i SAPSDIC.cmd -dbcodepage 4103 -log SAPSDIC.log -continue_on_error</b>

By changing all the <b>"ok"</b> on the e.g. <b>SAPSDIC.tsk</b> to <b>"err"</b>.

But some other processes like <b>SAPSSEXC, SAPAPPL0, SAPAPPL1,SAPAPPL2</b> didn't end.

At the end I got some 5 processes finished and the other 13 as failed.

When looking to the tsk files. I have some file with only "ok", which are the finished processes.

And the other are like before with some table "error", because the fact that the sql database isn't running.

Also by running the r3load command in the console, I have a message like:

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

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

Ps. I am so close to the solution.

Please respond,

Kais

Message was edited by:

Kais El Kara

[markus_doehr2 · Accepted solution]

Since you never posted the logfile with the "real" error it's impossible to help you here...

--

Markus

[Former Member · Accepted solution]

Hello Kais ,

Open your SAPSDIC.tsk file

1 ) You will notice object name and status for eg VRSX1 ok

2 ) Same status you will get for the object VRSX2 err

3 ) Edit SAPSDIC.tsk file ( make manually err to ok )

repeat same for VRSX2 ,VRSX3 & VRSX4.

And resume the installation .

Take the action accordingly in your case reindex VRSX1,2,3,4 after competion of instalaltion .

Revert back to me if you need further assistance .

Regards ,

Santosh

[Former Member · Accepted solution]

Hallo Markus,

I have the same problem with the one at this following link.

Sorry, for the log files but I am not working jet and I don't have access to the SAP System.

I can't provide you with the needed log files.

I hope I will post it to you today at night.

Regards,

Kais

[markus_doehr2 · Accepted solution]

> Hello Kais ,

>

> Open your SAPSDIC.tsk file

> 1 ) You will notice object name and status for eg

> VRSX1 ok

> 2 ) Same status you will get for the object VRSX2 err

>

> 3 ) Edit SAPSDIC.tsk file ( make manually err to ok )

>

>

> repeat same for VRSX2 ,VRSX3 & VRSX4.

If you do that, some tables will not be created and you will run sooner or later into subsequent errors (on creating views).

The root cause can (only) be found by looking at the logfiles.

--

Markus

[Former Member · Accepted solution]

Hello Markus ,

My advice was to escape index only not table .

That was only example .

[markus_doehr2 · Accepted solution]

Yes - but this may cause other errors (performance) lateron.

Don't you think it makes more sense to find out the real cause of the error?

--

Markus

[Former Member · Accepted solution]

Hello Markus ,

I do agree with you .

Creating index is manageable .

If you are exporting Data and there is only issue with specific object ->Cause may be the export may not consistent .

Regards ,

Santosh

[markus_doehr2 · Accepted solution]

An Index create statement is nothing more than a DDL statement, an index is not "imported" but created on the database, R3load generates just the DDL statement and sends it to the database.

If an index creation fails, the cause is ALWAYS local and should be investigated.

--

Markus

[Former Member · Accepted solution]

Ok !

What will happen if activate and adjust index in R/3.

Regards ,

Santosh Karadkar

[markus_doehr2 · Accepted solution]

If you remember the indexes you set manually to "OK" you can do it of course later in the R/3 - if you know the fields

--

Markus

[Former Member · Accepted solution]

Yes , Markus that’s very true .

Thank you!

[markus_doehr2 · Accepted solution]

I have had in 12 years ONE export CD, that was corrupted - and not because of the CD itself being corrupt but after copying data from CD to the disk it got somehow some defect.

It's always advised to search for the root cause, if e. g. your database crashed, setting the status manually to 'OK' won't help

--

Markus

[Former Member · Accepted solution]

That`s the reason you should always ensure Database statistics competed without single error before exporting data.