Solution Manager Installation Error

[Former Member]

Hi All,

I am facing some problem while installing Solution Manager 4.0 with win 2003 and oracle 10 and j2sdk1.4.2_13 java.

I am getting the error in Start Java Engine...

The Log is ERROR 2007-03-07 17:19:02

CJS-30149 ABAP processes of instance SMH/DVEBMGS01 [ABAP: UNKNOWN, Java: UNKNOWN] did not start after 10:30 minutes. Giving up.

ERROR 2007-03-07 17:19:02

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|4|0|startJava was executed with status ERROR .

<b>Please help me to get out it....</b>

Thanks in Advance

Kamal Bhargava

kamalb@hcl.in

[Former Member]

goto configtool and decrease the heap memory to 512 and rerun the installation

Samrat

[Former Member]

Hi ,

In configtool I have already 512 and I have total memory 512 in my system.

and I am seeing the config tool config in

D:\usr\sap\SMH\DVEBMGS01\j2ee\configtool

Is there any step by step installation guide for it...

The same error is coming please let me know the file name in which I had to make changes for heap memory.

Thanks

Kamal

[Former Member]

can you send me dev trace of server process

what i assumed is abap stack is up and i feel your java server processs is down

what is your ram size?

also check

valu of these parameters

-XX:MaxPermSize=?

-XX:PermSize=?

Xms?

go to D:\usr\sap\SMH\DVEBMGS01\j2ee\configtool

and click on configtool.bat

and select yes for the popup

the in the cluster

goto ->instance_id....

then select server_id..

ckeck the value in the right side against the max heap size

and also for the above parameters

Samrat

[Former Member]

Hi Samrat,

The values are , and I have 512 MB total memory in my server.

-Djava.security.policy=./java.policy

-Djava.security.egd=file:/dev/urandom

-Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

-Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

-Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser

-Djco.jarm=1

-Dsun.io.useCanonCaches=false

-XX:NewSize=85m

-XX:MaxNewSize=85m

-XX:MaxPermSize=192m

-Djava.awt.headless=true

-XX:PermSize=192m

-XX:SurvivorRatio=2

-XX:TargetSurvivorRatio=90

-XX:SoftRefLRUPolicyMSPerMB=1

-Xms512m

-verbose:gc

-XX:+DisableExplicitGC

-XX:+PrintGCDetails

-XX:+PrintGCTimeStamps

-XX:+UseParNewGC

Thanks

Kamal

[Former Member]

then you need to check the dev trace of server process

[Former Member]

Hi Samrat,

How to do this can you please let me know and max hep size is 512 MB.

Thanks

Kamal

[Former Member]

Hello,

Please change the value for -Xms512m, you have to change this for server and dispatcher node.

Adjust the JVM parameters of the node which is not starting manually using the configtool as follows:

1. Start the configtool from /usr/sap/<SID>/JC<instance-nr>/j2ee/ configtool directory

2. Browse the tree in the left pane cluster-data -> instance_ID<num> -> <node>_ID<num>

3. Select the Java parameters Text field in the right pane

4. Adjust the parameters of the node.

5. Make sure value of -Xms option is lower or equal than -Xmx

6. Press the apply changes button

7. Confirm all popups.

8. Close the configtool

9. Stop the J2EE instance

10. Start the J2EE instance

11. Continue with the installation process

Cheers,

-Sunil