As Java does not start: "Can't create static shared memory "

[Former Member]

Dears,

we are at the end of the Solution Manager 71 upgrade, and the JAVA instance does not come up in phase Evaluation; the upgrade on the Abap side in ended successfully.

Here some logs:

std_server0.out

--------------------------------------------------------------------------------
stdout/stderr redirect
--------------------------------------------------------------------------------
node name   : server0
pid         : 4718646
system name : ABC
system nr.  : 00
started at  : Wed Apr  4 10:19:31 2012

Critical Error
Can't initialize JControl Administration
-> Unknown error code (rc = 3)

std_sdm.out

--------------------------------------------------------------------------------
stdout/stderr redirect
--------------------------------------------------------------------------------
node name   : SDM
pid         : 4718646
system name : ABC
system nr.  : 00
started at  : Wed Apr  4 10:19:31 2012

Critical Error
Can't initialize JControl Administration
-> Unknown error code (rc = 3)

dev_jcontrol

.......

[Thr 01] *** ERROR => SfCreateShm: Shm in use by process 4718646. [jsfxxshm_mt. 1277]

[Thr 01] *** ERROR => Can't create static shared memory (rc = 13 already in use) [jcntrxx_mt.c 2119]

[Thr 01] *** ERROR => Can't initialize JControl Administration [jcntrxx_mt.c 295]

[Thr 01] JControlCloseProgram: started (exitcode = -1)

[Thr 01] *** ERROR => SfDestroyDynShm: Dynamic shared memory is not opened. [jsfxxshm_mt. 2369]

[Thr 01] *** ERROR => SfDestroyShm: Static shared memory is not opened. [jsfxxshm_mt. 1389]

[Thr 01] JControlCloseProgram: good bye... (exitcode = -1)

....

Any advise ?

regards

[Former Member]

Dear Roberto,

can you send us the relevant content of the trace file dev_server0, dev_jcontrol, jvm_sdm.out and std_sdm.out ?

Try to upgrade your kernel if doesn't yet done; stop all instance, run slibclean a try to restart.

Thanks

[Former Member]

Hi,

Check the SAP knowledge Base Article 1606123 - AS JAVA can't
start to resolve this.

The best solution would be to reboot the machine on OS level first (this
will very likely to release shared memory)  then restart the java
instance.

Regrds,

Vipin

[Former Member]

unfortunately note 1606123 is not released.

Is it the right number ?

Regards

[Former Member]

Sorry SAP note is still not released

In order to solve it, please kill the proc.ess with PID 4718646 and then try

to restart your instance.

[Former Member]

We read note 723909 but it's only for 640/700, while our TSM is NW 71, based on Sap_Basis 702 pl 9, and  the kernel in use it's rel 720_REL, pl 201.

We check note 1248926 but we are unable to find out on sapnet any ZeroAdmin template for the Solution Manager product.

In any case we try to put with Configtool the parameter -xmx equal to -xms to 2048M and restarted the instance cleaning the memory as for :

http://help.sap.com/saphelp_nw04/helpdata/en/12/bb0a412a06f023e10000000a155106/frameset.htm

but it does not start anyway.

Any advise ?

regards

[Former Member]

rebooting the server the number of the proces holding the memory change.

Anyway it's always the process:

jc.sapABC_DVEBMGS00 pf=/usr/sap/ABC/SYS/profile/ABC_DVEBMGS00_saphost -DSAPSTART=1

I think it's not usefull to kill this process; if you do that and then restart the Sap instance, obviously a new jc process is started

any advise

[Former Member]

Please, could you paste at least a partial copy of the content of this note, even if is not officially released  ?

regards

[Former Member]

Please find the content of note:

Cause

The SHM is used by another process. You need to check if the PID is changing.

If the PID remains the same, there is a stucked jcontrol or jlaunch process on the OS.

If the PID is different at every restart, the process (identified by <PID>) is getting started through the startsap script independently from the Java Startup Framework.

Resolution

If the PID remains the same you have to kill the process on the OS or restart the SAP service.

If the PID is changing at every restart you need to check the start profiles. The profiles may contain extra entries which start the processes through startsap and not through the Java Startup framework.

Regards,

Vipin

[Former Member]

Thanks , infact I found the jc  started two times:

into the START_DVEBMGS00_saphost

and

into the ABC_DVEBMGS00_saphost

I removed it from the START_DVEBMGS00_saphost and restarted and finally it works...

Best regards

[Former Member]

Hi,

Can suggest a restart of the server as it would clean up the shared memory.

Did you also try a cleanipc and restart? Check this thread for more tips:

http://scn.sap.com/thread/1473067

Regards,

Srikishan

[Former Member]

We restarted the whole server , the error still exist.