SolMan Installation Errors

[Former Member]

Hi Experts,

I am installing SAP Solution Manager on Windows2003 SR2+Oracle 10G.

My server is: HP DL360 32bit (RAM:2GB, HD:150GB)

But it was prevent at the Phase 35 of 44, the 'Start Jave engine'.

It popuped error logs like below:

Part One:

ERROR 2009-03-09 09:43:05.781

CJS-30149 ABAP processes of instance SLM/DVEBMGS00 [ABAP: UNKNOWN, Java: UNKNOWN] did not start after 10:00 minutes. Giving up.

Part Two:

ERROR 2009-03-09 09:43:05.796

FCO-00011 The step startJava with step key

|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava was executed with status ERROR .

I try many times but still can't install successfully.

Hope you cuould guide me.

Thank in advance!

Jason

[Former Member · Accepted solution]

Hi

The Steps what you are following for installing Solman are right.I think you have problem with JDK

"With 1.4.2_18 and 1.4.2_19 we are currently having massive stack overflow and also access violation problems on Windows x86 (64bit) with our default parameter set. The issue is still under investigation. Additionally we see a performance regression"with Java Systemcopy on 1.4.2_18

This applies for only 64 bit

Just give a try changing the JDK version but iam not sure it will resolve but we can give a try once

Regards

Uday

[Former Member · Accepted solution]

Hi Uday,

Thank you very much. You gave me an important clew. I will focus on JDK.

Pls note:

-

---

I am installing SAP Solution Manager on Windows2003 SR2+Oracle 10G.

My server is: HP DL360 32bit (RAM:2GB, HD:150GB)

-

---

It's 32bit.

Do you have any further suggestions?

Regards!

Jason

[markus_doehr2 · Accepted solution]

http://service.sap.com/solutionmanager

--> FAQ

There is a sizing section, if you read that, you will find out, that 2 GB memory is too less for a SolMan and that a 64bit platform is recommended.

Markus

[Former Member · Accepted solution]

Hi Markus,Uday

I just want to get download approvals via SolMan.(We will but a new server in June.)

So I want to install SolMan4.0 on HP DL360 now.

Could you tell me the avaliable JDK version and download link?

Thank you very much!

Jason

[markus_doehr2 · Accepted solution]

> Could you tell me the avaliable JDK version and download link?

Did you check the installation guide? It contains a bunch of notes and also notes that tell you where to get the appropriate JDK.

Note: Installation a SolMan and configuring it for download confirmation is not something that can be done "quick and easy".

You were already as far as you did load the database with the data but it did not come up. Using a different JDK won't solve that problem. Your main issue is memory - which can only be solved by adding more of it or increasing the swap space.

Post dev_disp and dev_w0 of the failed attempt to start the system and let's see, if we can figure out, what can be done.

Markus

[Former Member · Accepted solution]

Hi Markus,Uday

Today I am very happy. Because I installed the SolMan successfully.

But I still don't know where/which step I were wrong.

Today I uninstalled the unsuccessful systems installed before(Oracle,JDK,SolMan) and deleted the directories:

c:\program files\oracle

C:\Program Files\sapinst_instdir

After that, I re-installed JDK,Oracle and SolMan.

I noticed that I met a new parameter configration interface at the second phase 'Define Parameters' during SolMan installation.

The content of configration listed below(I didn't see it before.):

-

---

SAP Sytem>Central and SCS Instance

Central Instance Parameters

ABAP Message Service Posrt: 3600

Internal ABAP Message Service Port: 3900

HOST with Transport Directory: WXJSLM

SCS Instance Parametes

Internal SCS Messaing Service Port: 3901

-

---

I'm not sure I can install SolMan4.0(32bit) successfully once again on the same platform.

I still do't know which step/reason caused the unbelievable success today.

I will re-install it again until I assure I can install it successfully every time.

I will write a guide that describe every details of installing SolMan4.0 on windows2003.

Thank you very much again! Markus,Uday!

Jason

[Former Member]

Dear Jason Xu.

Congratulations fisrt.

Now, could you provide the installation guide with your steps?

I very appreciate it.

Edited by: Jachael Huang on Mar 16, 2009 3:55 PM

[markus_doehr2]

> Now, could you provide the installation guide with your steps?

Did you check the official guides at

http://service.sap.com/instguides?

Really everything you need to know to sucessfully install a system is in it...

Markus

[Former Member]

Hi Markus.

I have read the offical installation guide and setup the environment variable.

But it still occurs exception at the phase Import ABAP...

O.S: Windows 2003 Server Standard Edition x64

JDK: 1.4.2_17

The log file is below

============================================

import_monitor.java.log

java version "1.4.2_17"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)

Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, 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 'ATAB' import package: ERROR

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

Loading of 'SEOSUBCODF' import package: ERROR

Loading of 'STERM_TEXT' import package: ERROR

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

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

===========================================================

ATAB.log

D:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20090317053717

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

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

Compiled Jan 24 2008 01:41:44

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

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

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

D:\usr\sap\S01\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20090317053721

============================================================

There is the same error code at 'SEOSUBCODF' and 'STERM_TEXT' files

Please help thank you very much.

[Former Member]

Cheers!!!!

Regards

Uday

[Former Member]

Hi

"My server is: HP DL360 32bit (RAM:2GB, HD:150GB)" is not sufficient for solman SR2 when it is for production operations, just try increasing the RAM and upgrade it to 64 bit.

For Test purpose i have installed solman SR2 on my desktop with 1GB of RAM and 250 HD i havn't faced any problem during installation and its working fine.

The problem you have with " Phase 35 of 44, the 'Start Jave engine' i think IMPORT ABAP phase is completed.Just try logging to ABAP instance and check users J2EE_ADMIN,SAPJSF and J2EE_GUEST users are created,If not just created them manually through SU01 client 001 and assign appropiate role to them and try the installation again.

Hope this should work

Regards

Uday

[Former Member]

HI Uday,

Thanks for your reply.

Could tell me the main steps of SolMan4.0 installation?

Here is the main steps I carried out:

(1)Install the JDK version: j2sdk1.4.2_18.

(2)Set 'JAVA_HOME' and 'PATH' for JDK.

(3)Install Oracle 10.2.0.1.0. (It's SID: SLM)

(4)Stop the Oracle Service manually.

(5)Apply the Oracle patches. Update Oracle to a new version: 10.2.0.2.0.

(6)Start the Oracle service manually.

(7)Install SolMan via sapinst.

(8)Select the DB(SLM) during the SolMan installation.

(9)Waiting and waiting,but I was prevent at the 35 step. (Total: 44 steps.)

Thank you!

Jason

[markus_doehr2]

2 GB is FAR TOO LESS memory.

OS will need some memory, Java will allocated exclusively 1 GB for the server process and another 250+ MB for the dispatcher and SDM. The database will also need memory so there is nothing less for the data. You may, however, compensate that using a lot of swap but you may not able to work with the system since it's constantly swapping.

Markus

[Former Member]

Hi Markus,

Thank you very much!

You let me know the needs of every components.

I've created a message on SMP.

I am waiting for SAP's reply.

And I will post their suggestions here.

Regards!

Jason

[markus_doehr2]

> You let me know the needs of every components.

Those are just average numbers, I would not install a Solman under 6 GB of physical memory and I also would not try to install it 32bit. You may not be able to run certain components (the BI stuff) because of the 32bit limitation.

Markus

[Former Member]

Hi Markus,

Here below was the reply from SAP support:

I will try to find out the reason.

===================================================

Thank you for contacting SAP Active Global Support Center.

I recommend you to use the lastest sapinst downloaded from marketplace.

Then for the upper errors would you please refer to check

to see if the application was using the port 3901 in your system if

so please refer to install by a different port for this problem

furtherly please also refer to SAP attached Note 52959 to check to sure

if there is no extra white spaces in service file.

Note 52959: sapms..., sapdp.., sapgw.. unknown (or not found)

Could you check, if on windows system the address spase is

fragmented, which I think it is related.

Please check SAP attached notes 723909 and 716604 about jvm settings andSAP attached Note 736462 about address

space fragmentation.

There is better way to avoid address space fragmentation - please

see SAP attached Note 853696.

Hope this information helps you.

[markus_doehr2]

I see.

Maintaining a 32bit installation on Windows, especially if it's ABAP + Java and Unicode can be pretty cumbersome.

Markus