Solution Manager 7.1 SPS8 to SPS11 with SUM

[former_member640444]

Hello,

I'm just upgrading SolMan 7.1 to SPS11 (AIX, DB/2). The SUM Initialization and Extraction part is done without any errors. Now in step 5.3 Configuration the ABAP part is also done, but Java brings following error:

I'm wondering, because the SAP-processes shows an DVEBMGS02 and an SCS03 instance - no additional JCxx instane!?

Can anyone help me in that?

Thx a lot!

[former_member185239 · Accepted solution]

Hi Karheinz,

From the host 10.6.2.211 check the connection through telnet.

telnet 10.6.2.211 50204.

And also check whether java is up or not.

Activity to follow.

1. open the SDM and enter the password of j2ee_admin(if you can logon its good)

2. open the JSPM and try to logon with the j2ee_admin(if you can logon its good)

3. Then maintain the same password in secure storage of configtool and take a restart of whole system (ABAP and Java)

4. Retry the SUM Tool.

If you can logon to the SDM , then reset the password of SDM(having the same password of j2ee_admin user) and maintain the same password for j2ee_admin user in secure storage of config tool.

Take a restart of whole system and retry the SUM Tool.

With Regards

Ashutosh Chaturvedi

[former_member640444 · Accepted solution]

Hi Ashutosh,

telnet cannot connect to P4 port and I think there is only the ABAP and SCS instance running (and maybe configured/installed). Because I cannot see any JC-Instance there:

bash-4.1$ ps -ef| grep SOP

  sopadm  5243040  9240682   0 10:05:09      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm  5308630        1   1 10:47:59      -  0:36 /usr/sap/SOP/DVEBMGS02/exe/sapstartsrv pf=/usr/sap/SOP/SYS/profile/START_DVEBMGS02_solutionmgr -D -u sopadm

  sopadm  5898280        1   0 10:04:43      -  0:00 /usr/sap/SOP/SCS03/exe/sapstartsrv pf=/usr/sap/SOP/SYS/profile/START_SCS03_solutionmgr -D

  sopadm  6684718  9240682   0 10:05:11      -  0:01 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm  7078084 14614740   0 10:04:53      -  0:00 en.sapSOP_SCS03 pf=/usr/sap/SOP/SYS/profile/SOP_SCS03_solutionmgr

  sopadm  7471128  9240682   0 10:05:09      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm  7667890  9240682   0 10:05:09      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm  9240682 16253044   0 10:05:07      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 12320814 14614740   0 10:04:53      -  0:00 ms.sapSOP_SCS03 pf=/usr/sap/SOP/SYS/profile/SOP_SCS03_solutionmgr

  sopadm 12583108  9240682   0 10:05:09      -  0:01 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 12714102  9240682   0 10:05:11      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 12779534  9240682   0 10:05:10      -  0:02 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 13041748  9240682   0 10:05:09      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 13434992  9240682   0 10:05:08      -  0:02 gwrd -dp pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 13631660  9240682   0 10:05:08      -  0:00 icman -attach pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 13697132  9240682   0 10:05:11      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 13828162  9240682   0 10:05:09      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 14614740        1   0 10:04:53      -  0:00 sapstart pf=/usr/sap/SOP/SYS/profile/START_SCS03_solutionmgr

  sopadm 15073416  9240682   0 10:05:09      -  0:11 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 15138882  9240682   0 10:05:10      -  0:01 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 15532284 16253044   0 10:05:07      -  0:00 ms.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 15663288  9240682   0 10:05:10      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 16056446  9240682   0 10:05:09      -  0:01 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 16253044        1   0 10:05:06      -  0:00 sapstart pf=/usr/sap/SOP/SYS/profile/START_DVEBMGS02_solutionmgr

  sopadm 17170536  6750438   0 10:06:50  pts/1  0:00 grep SOP

  sopadm 17236076  9240682   0 10:05:09      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 17301728  9240682   0 10:05:10      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

  sopadm 17694856  9240682   0 10:05:09      -  0:00 dw.sapSOP_DVEBMGS02 pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

bash-4.1$ sapcontrol -nr 03 -function GetSystemInstanceList

14.05.2014 10:11:30

GetSystemInstanceList

OK

hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus

solutionmgr, 3, 50313, 0, 1, MESSAGESERVER|ENQUE, GREEN

solutionmgr, 2, 50213, 0, 2, ABAP|J2EE|GATEWAY|MESSAGESERVER|ENQUE|ICMAN|IGS, YELLOW

I had to reset j2ee_admin password in SU01 - how can I do this in configtool too?

[former_member185239 · Accepted solution]

Dear Karlheinz,

First of all try to start the java instance and then give a retry with SUM tool

- stop the sap system

- kill all the process related to sap

-start the sap system

With Regards

Ashutosh Chaturvedi

[former_member640444 · Accepted solution]

Dear Ashutosh,

I've tried this already 2 or 3 times - doesnt help. Have now also updated the j2ee_admin password in secstore.

SUM shows the same error as above.

But get an error when changing SDM password:

sdm.sh jstartup mode=standalone

sdm.sh changepassword newpassword=xxxxx

Starting '/usr/java/bin/java' '-Xmx512M' -jar '/usr/sap/SOP/DVEBMGS02/SDM/program/bin/SDM.jar' changepassword 'sdmhome=/usr/sap/SOP/DVEBMGS02/SDM/program' newpassword=verleihnix

Starting SDM - Software Deployment Manager...

tc/SL/SDM/SDM/sap.com/SAP AG/7.0208.20110714090755.0000

Initializing Network Manager (50217)

Checking if another SDM is running on port 50218

Unhandled exception

Type=Segmentation error vmState=0x00000000

J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033

Handler1=09001000A2E6DB80 Handler2=09001000A2E65C68

[former_member185239 · Accepted solution]

Hi Kar,

You need to stop the SDM first

Follow the below steps

1. ./StopServer.sh

2. ./sdm.sh jstartup "mode=standalone"

3. ./sdm.sh changepassword "newpassword=<newpasswor>"

4. ./sdm.sh jstartup "mode=integrated"

5. ./StartServer.sh

With Regards

Ashutosh Chaturvedi

[former_member640444 · Accepted solution]

Hi,

I've stopped the server and there are now SDM processes running. But still get this error when giving the newpassword command:

./sdm.sh changepassword "newpassword=<newpassw>"

P.S.: ulimit -c unlimited and ulimit -d unlimited given before!

[former_member185239 · Accepted solution]

Dear Karlheinz,

Run the command

netstat -tupan |grep 50217

netstat -tupan |grep 50218

Paste the output of the above commands

With Regards

Ashutosh

[former_member640444 · Accepted solution]

Dear Ashutosh,

I'm on AIX therefore i took: netstat -a | grep 502

No output! Ports 50217 and 50218 are free for use!

[former_member185239 · Accepted solution]

Dear Karlheinz ,

is it possible for you to take the reboot of the server.

With Regards

Ashutosh Chaturvedi

[former_member640444 · Accepted solution]

Yes, have rebooted now (Shutdown -Fr) and I get the same error.

Maybe this is a java (jdk) problem?

Is there a way to re-install SDM?

[former_member185239 · Accepted solution]

Dear Karlheinz,

Kindly set the environment variable

export JAVA_COMPILER= NONE

and in that session try to change the password of SDM user.

With Regards

Ashutosh Chaturvedi

[Former Member · Accepted solution]

Have you switched to sapjvm for Solution Manager system? If yes try to use it instead of IBM jvm.

[former_member640444 · Accepted solution]

Hi,

the JAVA_COMPILER=NONE was helpful!

Now the password change for SDM was done in standalone-mode, then changed back to integrated-mode.

Starting SDM with ./StartServer.sh now shows repeatingly:

SDM server not up after 200 seconds. Waiting for another 5 seconds.

Can start it in standalone-mode without any problems!

[former_member185239 · Accepted solution]

Hi Karlheinz,

Kill the repeating phase , and open a new session of putty and take a restart of SAP system.

Also confirm that java has come up properly.

Paste the details of jsmon pf=<instance profile>

With Regards

Ashutosh Chaturvedi

[former_member640444 · Accepted solution]

Hi Ashutosh,

have no again restarted SAP, new putty session. Same problem SDM server not up after... seconds.

jsmon pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

shows:

unknown section: -pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

Regards, Karlheinz

[former_member185239 · Accepted solution]

Dear Karlheinz,

Is your java stack is coming up apart from SDM?

Paste the logs from /usr/sap/SID/DVEBMGS<nr>/SDM/program/log

With Regards

Ashutosh Chaturvedi

[former_member640444]

Hi @all,

have no installed SAPJVM 4.1 with Switch-Tool (also adapted to DAA). SAP stopped, server rebooted, SAP started.

After that again:

1. ./StopServer.sh

2. ./sdm.sh jstartup "mode=standalone"

3. ./sdm.sh changepassword "newpassword=<newpasswor>"

4. ./sdm.sh jstartup "mode=integrated"

5. ./StartServer.sh

Sorry, but have the same problem again: Every 5 seconds message: SDM server not up after 5 seconds. Waiting for another 5 seconds.

[former_member185239]

Hi Karlheinz,

Is your java stack is coming up.

With Regards

Ashutosh Chaturvedi

[former_member640444]

Hi,

no did not came up. Have changed jstartup/vm/home to new SAPJVM-directory and SDM started together with SAP system and SUM continues!

Thx a lot to all!

[Matt_Fraser]

Karlheinz,

For a dual-stack system like Solution Manager, it is correct that there is no JCxx instance.  You should have SCS03 and DVEBMGS02 only, unless you added additional dialog instances.  So, the lack of JC0x is not an error, although it's interesting that you have chosen instance numbers 02 and 03 instead of 00 and 01.  Still, that's not a problem.

I'm not an expert with AIX/DB2, unfortunately, so I'm not sure about some of the methods, but if your Java instance is running, you should be able to point a browser at http://<server>:50200/monitoring/SystemInfo.  In the output of that page, you should be able to see any running dispatcher, server, and SDM processes within the DVEBMGS02 instance, and whether their status is 'green' or not.

With regard to the substituted D02 instance name you're seeing, you can check that further by logging onto your ABAP instance and running RSPARAM via SE38.  Find jstartup/instance_properties and see if you still see that in the User-Defined Value column.  What you see in this column is what really matters.  If the column is blank, then the System Default Value is what's in play.  So, you might be seeing D02 in system default, but as long as user-defined shows DVEBMGS02 instead, you're ok on this score.

Regards,

Matt

[former_member640444]

Hi Matt,

rsparam shows in user defined value the right instance DVEBMGS02. I cannot browse to http://<server>:50200/monitoring/SystemInfo - there is no output. So I think the java instance is not up.

[former_member185239]

Hi Kartlheinz,

Can you paste the below logs from directory /usr/sap/SOP/DVEBMGS02/work

1. jvm_bootstrap.log

2. dev_server0

3. std_server0

With Regards

Ashutosh Chaturvedi

[former_member640444]

Hi, in dev_bootstrap you can find an Java VM abort:

---------------------------------------------------

trc file: "dev_bootstrap", trc level: 1, release: "721"

---------------------------------------------------

node name   : bootstrap

pid         : 8126588

system name : SOP

system nr.  : 02

started at  : Thu May 15 17:54:13 2014

arguments  :

   arg[00] : /usr/sap/SOP/DVEBMGS02/uc/jlaunch

   arg[01] : pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

   arg[02] : -DSAPINFO=SOP_02_bootstrap

   arg[03] : pf=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

   arg[04] : -DSAPSTART=1

   arg[05] : -DCONNECT_PORT=60093

   arg[06] : -DSAPSYSTEM=02

   arg[07] : -DSAPSYSTEMNAME=SOP

   arg[08] : -DSAPMYNAME=solutionmgr_SOP_02

   arg[09] : -DSAPPROFILE=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

   arg[10] : -DFRFC_FALLBACK=ON

   arg[11] : -DFRFC_FALLBACK_HOST=localhost

**********************************************************************

Used property files

-> files [00] : /usr/sap/SOP/DVEBMGS02/j2ee/cluster/instance.properties

**********************************************************************

**********************************************************************

Bootstrap nodes

-> [00] bootstrap            : /usr/sap/SOP/DVEBMGS02/j2ee/cluster/instance.properties

-> [01] bootstrap_ID25948100 : /usr/sap/SOP/DVEBMGS02/j2ee/cluster/instance.properties

-> [02] bootstrap_ID25948150 : /usr/sap/SOP/DVEBMGS02/j2ee/cluster/instance.properties

**********************************************************************

**********************************************************************

Worker nodes

-> [00] ID25948100           : /usr/sap/SOP/DVEBMGS02/j2ee/cluster/instance.properties

-> [01] ID25948150           : /usr/sap/SOP/DVEBMGS02/j2ee/cluster/instance.properties

**********************************************************************

**********************************************************************

JStartupReadInstanceProperties: read instance properties [/usr/sap/SOP/DVEBMGS02/j2ee/cluster/instance.properties]

-> ms host    : solutionmgr

-> ms port    : 3903

-> OS libs    : /usr/sap/SOP/DVEBMGS02/j2ee/os_libs

-> Admin URL  :

-> run mode   : normal

-> run action : NONE

-> enabled    : yes

**********************************************************************

[Thr 01] Thu May 15 17:54:13 2014

[Thr 01] [Node: bootstrap] java home is set by profile parameter

[Thr 01] Java Home: /usr/java14_64

**********************************************************************

JStartupIReadSection: read node properties [bootstrap]

-> node name          : bootstrap

-> node type          : bootstrap

-> node execute       : yes

-> java path          : /usr/java14_64

-> java parameters    : -Djco.jarm=1 -Djava.security.policy=./java.policy -Xj9

-> java vm version    : J2RE 1.4.2 IBM J9 2.3 AIX ppc64-64 j9ap64142ifx-20070920 (JIT enabled)

-> java vm vendor     : IBM J9 VM (IBM Corporation)

-> java vm type       : server

-> java vm cpu        : ppc64

-> heap size          : 512M

-> root path          : /usr/sap/SOP/DVEBMGS02/j2ee/cluster

-> class path         : ./bootstrap/launcher.jar

-> OS libs path       : /usr/sap/SOP/DVEBMGS02/j2ee/os_libs

-> main class         : com.sap.engine.offline.OfflineToolStart

-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path     : /usr/sap/SOP/DVEBMGS02/uc/jstartup.jar:/usr/sap/SOP/DVEBMGS02/uc/jvmx.jar

-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0259481

-> debuggable         : yes

-> debug mode         : no

-> debug port         : 60000

-> shutdown timeout   : 120 sec.

**********************************************************************

[Thr 01] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 01] JLaunchRequestQueueInit: create pipe listener thread

[Thr 258] JLaunchRequestFunc: Thread 258 started as listener thread for np messages.

[Thr 515] WaitSyncSemThread: Thread 515 started as semaphore monitor thread.

[Thr 01] SigISetDefaultAction : default handling for signal SIGCHLD

[Thr 01] Thu May 15 17:54:14 2014

[Thr 01] NiInit3: NI already initialized; param 'maxHandles' ignored (init=1;par=32768;cur=2048)

[Thr 01] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)

[Thr 01] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.

[Thr 01] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.

[Thr 01] CCMS: CCMS Monitoring Initialization finished, rc=0.

[Thr 01] [Node: bootstrap] java home is set by profile parameter

[Thr 01] Java Home: /usr/java14_64

**********************************************************************

JStartupIReadSection: read node properties [bootstrap]

-> node name          : bootstrap

-> node type          : bootstrap

-> node execute       : yes

-> java path          : /usr/java14_64

-> java parameters    : -Djco.jarm=1 -Djava.security.policy=./java.policy -Xj9

-> java vm version    : J2RE 1.4.2 IBM J9 2.3 AIX ppc64-64 j9ap64142ifx-20070920 (JIT enabled)

-> java vm vendor     : IBM J9 VM (IBM Corporation)

-> java vm type       : server

-> java vm cpu        : ppc64

-> heap size          : 512M

-> root path          : /usr/sap/SOP/DVEBMGS02/j2ee/cluster

-> class path         : ./bootstrap/launcher.jar

-> OS libs path       : /usr/sap/SOP/DVEBMGS02/j2ee/os_libs

-> main class         : com.sap.engine.offline.OfflineToolStart

-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path     : /usr/sap/SOP/DVEBMGS02/uc/jstartup.jar:/usr/sap/SOP/DVEBMGS02/uc/jvmx.jar

-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0259481

-> debuggable         : yes

-> debug mode         : no

-> debug port         : 60000

-> shutdown timeout   : 120 sec.

**********************************************************************

[Thr 772] JLaunchIStartFunc: Thread 772 started as Java VM thread.

**********************************************************************

JHVM_LoadJavaVM: VM Arguments of node [bootstrap]

-> stack   : 1048576 Bytes

-> arg[  0]: exit

-> arg[  1]: abort

-> arg[  2]: vfprintf

-> arg[  3]: -Denv.class.path=:/db2/db2sop/sqllib/java/db2java.zip:/db2/db2sop/sqllib/java/runtime.zip:.:/db2/db2sop/sqllib/java/db2java.zip:/db2/db2sop/sqllib/java/runtime.zip:.

-> arg[  4]: -Djco.jarm=1

-> arg[  5]: -Djava.security.policy=./java.policy

-> arg[  6]: -Xj9

-> arg[  7]: -Dsys.global.dir=/usr/sap/SOP/SYS/global

-> arg[  8]: -Dapplication.home=/usr/sap/SOP/DVEBMGS02/uc

-> arg[  9]: -Djava.class.path=/usr/sap/SOP/DVEBMGS02/uc/jstartup.jar:/usr/sap/SOP/DVEBMGS02/uc/jvmx.jar:./bootstrap/launcher.jar

-> arg[ 10]: -Djava.library.path=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/SOP/DVEBMGS02/exe:/usr/sap/SOP/DVEBMGS02/exe:/usr/sap/SOP/DVEBMGS02/exe:/usr/sap/SOP/SYS/exe/run:/usr/sap/SOP/SYS/exe/uc/rs6000_64:/usr/java14_64/jre/bin/j9vm:/usr/sap/SOP/DVEBMGS02/exe::/usr/lib:/usr/sap/SOP/DVEBMGS02/j2ee/os_libs:/usr/sap/SOP/DVEBMGS02/uc:/usr/sap/SOP/DVEBMGS02/uc:/usr/sap/SOP/DVEBMGS02/exe:/usr/sap/SOP/SYS/exe/run:/usr/sap/SOP/SYS/exe/uc/rs6000_64

-> arg[ 11]: -Dmemory.manager=512M

-> arg[ 12]: -Xmx512M

-> arg[ 13]: -DLoadBalanceRestricted=no

-> arg[ 14]: -Djstartup.mode=BOOTSTRAP

-> arg[ 15]: -Djstartup.ownProcessId=8126588

-> arg[ 16]: -Djstartup.ownHardwareId=T1167630990

-> arg[ 17]: -Djstartup.whoami=bootstrap

-> arg[ 18]: -Djstartup.debuggable=yes

-> arg[ 19]: -DSAPINFO=SOP_02_bootstrap

-> arg[ 20]: -DSAPSTART=1

-> arg[ 21]: -DCONNECT_PORT=60093

-> arg[ 22]: -DSAPSYSTEM=02

-> arg[ 23]: -DSAPSYSTEMNAME=SOP

-> arg[ 24]: -DSAPMYNAME=solutionmgr_SOP_02

-> arg[ 25]: -DSAPPROFILE=/usr/sap/SOP/SYS/profile/SOP_DVEBMGS02_solutionmgr

-> arg[ 26]: -DFRFC_FALLBACK=ON

-> arg[ 27]: -DFRFC_FALLBACK_HOST=localhost

-> arg[ 28]: -DSAPSTARTUP=1

-> arg[ 29]: -DSAPSYSTEM=02

-> arg[ 30]: -DSAPSYSTEMNAME=SOP

-> arg[ 31]: -DSAPMYNAME=solutionmgr_SOP_02

-> arg[ 32]: -DSAPDBHOST=solutionmgr

-> arg[ 33]: -Dj2ee.dbhost=solutionmgr

**********************************************************************

[Thr 772] JHVM_LoadJavaVM: Java VM created OK.

**********************************************************************

JHVM_BuildArgumentList: main method arguments of node [bootstrap]

-> arg[  0]: com.sap.engine.bootstrap.Bootstrap

-> arg[  1]: ./bootstrap

-> arg[  2]: ID0259481

**********************************************************************

Thu May 15 17:54:15 2014

Unhandled exception

Type=Segmentation error vmState=0x00000000

Target=2_30_20070919_13979_BHdSMr (AIX 6.1)

CPU=ppc64 (8 logical CPUs) (0x500000000 RAM)

[Thr 772] Thu May 15 17:54:18 2014

[Thr 772] JLaunchIAbortJava: abort hook is called

[Thr 772] **********************************************************************

[Thr 772] *** ERROR => The Java VM aborted unexpectedly.

[Thr 772] *** Please see SAP Note 943602 , section 'Java VM crashes'

[Thr 772] *** for additional information and trouble shooting.

[Thr 772] **********************************************************************

[Thr 772] SigISetIgnoreAction : SIG_IGN for signal SIGCHLD

[Thr 772] JLaunchCloseProgram: good bye (exitcode = -2)

[Matt_Fraser]

Ok, try connecting to the instance with SAPMC.  I don't know if you're already familiar with this tool or not, through probably you are since you're managing in AIX and not Windows.  You may be able to connect to it by pointing your browser at http://<host>:50213.  However, you may get Java security warnings and your JRE might block the applet from running, depending on which version of the sapmc executables are installed in your kernel.  If that happens, you can try reducing your Java security level from High to Medium temporarily.  If that still doesn't work (for instance, you get past the security warnings but you get null pointer errors or control exceptions), then set your Java security back to high and install the SAPMC locally on your workstation instead and run it from there.  You can download it from http://service.sap.com/swdc -> Browse our Download Catalog -> Additional Components -> SAP Kernel -> SAP KERNEL <32-bit or 64-bit> -> SAP KERNEL 7.41 <32/64-BIT> -> <platform> -> #Database independent -> sapmc_xx-xxxxxxxx.sar.  Download the version appropriate for your workstation, not your server, if you want to install it on your workstation.  Unpack the SAR file, and then run \servicehttp\sapmc\sapmc.html from the location you unpacked it to.  This should open it as a standalone application in your browser.  You'll see a connect button, and you should be able to just enter the instance hostname and instance number (02) and connect.

If that works, you should see your DVEBMGS02 and SCS03 instances running, hopefully with green lights.  Expand DVEBMGS02 and you'll see AS Java within it.  Select that and you'll see the status, running or not.  Expand it, and you can see the process table, where you can see the status of the SDM, dispatcher, and any serverx processes.

[Matt_Fraser]

Per Note 1703496, segmentation errors in the Java VM are usually due to using very old or unsupported JVMs.  You are using the IBM JVM, and really you should be switching to the SAPJVM.  This is most likely the cause of the problem.  Someone else earlier in this thread also called out that you were using IBM JVM instead of SAPJVM.

[former_member185239]

Hi Karlheinz,

The error is related to the ibm jvm as it is using JIT Compiler.

"

Unhandled exception

Type=Segmentation error vmState=0x00000000

Target=2_30_20070919_13979_BHdSMr (AIX 6.1)

CPU=ppc64 (8 logical CPUs) (0x500000000 RAM)"

Set the environment variable JAVA_COMPILER=NONE

export JAVA_COMPILER=NONE and in the same putty session you need to start the system.

After starting the system , also checked the same log dev_bootstrap.

If it does not resolve the error then you need to switch from ibm to sapjvm with the help of sapjvm switch tool.

With Regards

Ashutosh Chaturvedi

[former_member640444]

Hi Matt,

Firefox can connect to 50213 via http and with errors. The system state I had already checked with sapcontrol - see output below:

bash-4.1$ sapcontrol -nr 02 -function GetSystemInstanceList

15.05.2014 18:23:25

GetSystemInstanceList

OK

hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus

solutionmgr, 3, 50313, 0, 1, MESSAGESERVER|ENQUE, GREEN

solutionmgr, 2, 50213, 0, 2, ABAP|J2EE|GATEWAY|MESSAGESERVER|ENQUE|ICMAN|IGS, YELLOW

[Matt_Fraser]

See Note 1367498 for SAP JVM installation prerequisites (including minimum versions of AIX libraries), Note 1665953 for composite notes about SAP JVM Switch Tool, and http://service.sap.com/instguides -> SAP JVM Switch Tool for the documentation.

[former_member640444]

Thx Matt,

I´ll install JVM 5.1 for AIX 6.1 latest version (I think tomorrow or monday) and let you know if this was the solution.

[former_member640444]

Hi Ashutosh,

I've tried with the JAVA_COMPILER=NONE and restarted SAP system. Doesn't work - therefore I will switch to sapjvm tomorrow or next monday. Thx.

[Matt_Fraser]

Be aware that for Solution Manager 7.1, per the PAM you must use SAPJVM 4.1.  This is because SolMan 7.1 runs on a NetWeaver 7.02 platform, and NW 7.02 only uses SAPJVM 4.1.  I think JVM 5.1 was only for the NW 7.1 platform (NW 7.3 and 7.4 use JVM 6.1).

[former_member185239]

Hi Karlheinz,

You are using a very old JVM which was build in 20070920.

"J2RE 1.4.2 IBM J9 2.3 AIX ppc64-64 j9ap64142ifx-20070920"

Either you use the latest ibm jre or switch over to sapjvm

Check the below threads for sapjvm switch

http://scn.sap.com/community/netweaver-administrator/blog/2012/06/06/sap-jvm-switch-guide-with-scree...

http://scn.sap.com/docs/DOC-33488

http://scn.sap.com/docs/DOC-35652

http://wiki.scn.sap.com/wiki/display/SL/SAPJVM+Switch+Tool

If you want to analyze the error deeply.

then run the below command

java -version

it will give a error as below , as a result your java system is not coming up.

Unhandled exception

Type=Segmentation error vmState=0x00000000

J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033

Handler1=09001000A2E6DB80 Handler2=09001000A2E65C68

With Regards

Ashutosh Chaturvedi

[former_member640444]

Hello all,

in the last sdmlog20140515.log you find only:

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[1.5.3.7185 - 630]/-->

<!--NAME[/usr/sap/SOP/DVEBMGS02/SDM/program/log/sdmlog20140515.log]/-->

<!--PATTERN[sdmlog20140515.log]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

May 15, 2014 12:09:10... Info:

May 15, 2014 12:09:10... Info: ============================================

May 15, 2014 12:09:10... Info: =   Starting to execute command 'server'   =

May 15, 2014 12:09:10... Info: ============================================

May 15, 2014 12:09:10... Info: Starting SDM - Software Deployment Manager...

May 15, 2014 12:09:11... Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0208.20110714090755.0000

May 15, 2014 12:09:19... Info: SDM operation mode successfully set to: Integrated

May 15, 2014 12:09:19... Info: JStartupFramework is active

May 15, 2014 12:09:19... Info: Operation mode of SDM in JStartupFramework is "Integrated".

May 15, 2014 12:09:19... Info: Check if Server is running already.

May 15, 2014 12:09:20... Info: OK server is not running. Enable SDM Process in JStartupFramework.

May 15, 2014 12:09:20... Info: enabling SDM Process with JStartupFramework

May 15, 2014 12:09:20... Info: enabled SDM Process with JStartupFramework

May 15, 2014 12:09:20... Info: Successfully enabled SDM Process in JStartupFramework.

[former_member185239]

Hi Karlheinz,

Checked the Sapnote 741289 - Profile parameters of the J2EE Engine are lost

As per 6.40/6.30

1. jstartup/instance_properties = $(INSTANCE_PROPERTIES);$(SDM_PROPERTIES)

2. INSTANCE_PROPERTIES = $(DIR_INSTANCE)/j2ee/cluster/instance.properties SDM_PROPERTIES = $(DIR_INSTANCE)/SDM/program/config/sdm_jstartup.properties

As per 2004s:

jstartup/instance_properties = $(jstartup/j2ee_properties);$(jstartup/sdm_properties)

Also paste the logs std_sdm.out, dev_sdm, jvm_sdm.out from the work directory.

With Regards

Ashutosh Chaturvedi

[former_member640444]

Hi Ashutosh,

checked the jstartup/instance_properties entry in the instance profile - is: $(jstartup/j2ee_properties):$(jstartup/sdm_properties)

But interesting is the substituted value:

/usr/sap/SOP/SYS/exe/run/icmext.properties:/usr/sap/SOP/D02/

There is no D02 instance only a DVEBGMS02.

[former_member185239]

Dear Karlheinz,

Kindly paste the content of Instance profile and also std_sdm.out, dev_sdm, jvm_sdm.out logs file

from /usr/sap/SOP/DVEBMGS02/work directory

With Regards

Ashutosh Chaturvedi

[former_member640444]

Hi,

there ar no such out-files in work-directory! Instance profile:

service/protectedwebmethods = NONE

jstartup/recorder = java -classpath ../j2ee/cluster/bootstrap/launcher.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node %nodeID% %startTime% -bz $(DIR_GLOBAL) –exitcode %exitcode%

login/min_password_lng = 5

zcsa/system_language = D

sap/bufdir_entries = 10000

zcsa/presentation_buffer_area = 20000000

zcsa/db_max_buftab = 10000

zcsa/table_buffer_area = 100000000

rsdb/cua/buffersize = 10000

rdisp/max_wprun_time = 3600

abap/buffersize = 500000

login/no_automatic_user_sapstar = 1

rsdb/ntab/ftabsize = 60000

SAPSYSTEMNAME = SOP

SAPSYSTEM = 02

INSTANCE_NAME = DVEBMGS02

DIR_CT_RUN = /usr/sap/SOP/SYS/exe/run

DIR_EXECUTABLE = /usr/sap/SOP/DVEBMGS02/uc

rsdb/ntab/entrycount = 30000

FN_JSTART = jcontrol$(FT_EXE)

jstartup/trimming_properties = off

jstartup/protocol = on

jstartup/vm/home = /usr/java14_64

jstartup/max_caches = 500

jstartup/release = 700

jstartup/instance_properties = $(jstartup/j2ee_properties):$(jstartup/sdm_properties)

j2ee/dbdriver = $(DIR_EXECUTABLE)/db2jcc.jar:$(DIR_EXECUTABLE)/db2jcc_license_cu.jar

exe/saposcol = $(DIR_CT_RUN)/saposcol

rdisp/wp_no_dia = 10

rdisp/wp_no_btc = 3

exe/icmbnd = $(DIR_CT_RUN)/icmbnd

rdisp/j2ee_start_control = 1

rdisp/j2ee_start = 1

rdisp/j2ee_libpath = $(DIR_EXECUTABLE)

exe/j2ee = $(DIR_EXECUTABLE)/jcontrol$(FT_EXE)

rdisp/j2ee_timeout = 600

rdisp/frfc_fallback = on

icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00

icm/server_port_0 = PROT=HTTP,PORT=80$$,TIMEOUT=240,PROCTIMEOUT=600

#-----------------------------------------------------------------------

# SAP Message Server parameters are set in the DEFAULT.PFL

#-----------------------------------------------------------------------

ms/server_port_0 = PROT=HTTP,PORT=81$$

rdisp/wp_no_enq = 1

rdisp/wp_no_vb = 1

rdisp/wp_no_vb2 = 1

rdisp/wp_no_spo = 1

icm/server_port_1 = PROT=SMTP,PORT= 25000

rdisp/elem_per_queue = 4000

csi/enable = 0

rsdb/obj/buffersize = 50000

abap/shared_objects_size_MB = 100

ssl/ssl_lib = $(DIR_EXECUTABLE)$(DIR_SEP)$(FT_DLL_PREFIX)sapcrypto$(FT_DLL)

sec/libsapsecu = $(ssl/ssl_lib)

ssf/ssfapi_lib = $(ssl/ssl_lib)

ipc/shm_psize_10 = 238000000

ipc/shm_psize_40 = 112000000

rsdb/ntab/irbdsize = 15000

rtbb/buffer_length = 60000

rsdb/obj/max_objects = 20000

[v_veeramalla]

can you paste the logs

sdm logs -(/usr/sap/SID/DVEBMGS<nr>/SDM/program/log)

dev_jcontrol (work directory)

//Venkat V