SAP not starting with VMC parameters. SAP_ES2_03_000 file exists

[Former Member]

Hi All,

I have a problem in starting the system. If I disable the following instance parameters, I am able to start SAP, however we need VMC as well.

vmcj/option/ps = 128M

vmcj/enable = on

vmcj/option/maxJavaHeap = 200M

It was working with above parameters, so we are sure the parameter values are correct. Eventhough some sapnote says that, we need to set the vmcj/option/ps value to higher value.

After some abrupt sapstop, we are not able to start SAP again. It is always failing with the reason /SAP_ES2_03_000 file exists. I am not able to get this file in /tmp or /proc filesystem. Is there any way to check where SAP_ES2_03_000 file is located ?

Here is dev_disp log file. we are on AIX os. Please guide me.

Fri May 22 11:00:06 2009

MBUF state OFF

DpCommInitTable: init table for 1000 entries

DpFileInitTable: init table for 3200 entries

DpSesCreateTable: created session table at 0x700000030000000 (len=1418392)

ThTaskStatus: rdisp/reset_online_during_debug 0

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 4096 kByte.

Using implementation std

<ES> Info: use normal pages (no huge table support available)

EsStdUnamFileMapInit: ES base = 0x0x700000040000000

EsStdInit: Extended Memory 5116 MB allocated

<ES> 1278 blocks reserved for free list.

ES initialized.

• ERROR => Es2IResCreate: open /SAP_ES2_03_000 failed. File already exists. If no SAP processes are running any more, you can cl

ean up stale resources with cleanipc. (17: File exists) [es2ux.c 198]

• ERROR => Es2ResCreateFiles: Es2IResCreate failed [es2xx.c 1265]

• ERROR => Es2ResCreate: Es2ResCreateFiles failed [es2xx.c 1443]

• ERROR => DpEmInit: Es2ResCreate (1) [dpxxdisp.c 9659]

• ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c 9561]

• DP_FATAL_ERROR => DpSapEnvInit: DpMemInit

• DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

[arkadius_sobkow]

Hello,

we have the same problem on our Linux x86_64 PI 7.10 system. when I try to start the instance, I get the following message:<BR><BR>

<ES> client 0 initializing ....<BR>

<ES> InitFreeList<BR>

<ES> block size is 4096 kByte.<BR>

Using implementation std<BR>

EsStdUnamFileMapInit: ES base = 0x2b21eedc7000<BR>

EsStdInit: Extended Memory 4096 MB allocated<BR>

Linux: Kernel supports shared memory disclaiming<BR>

Linux: using madvise(<pointer>, <size>, 9).<BR>

Linux: disclaiming for shared memory enabled<BR>

<ES> 1023 blocks reserved for free list.<BR>

ES initialized.

<BR>

• ERROR => Es2IResCreate: open /SAP_ES2_12_000 failed. File already exists. If no SAP processes are running any more, you can clean up stale resources with cleanipc. (17: File exists) [es2ux.c 193]<BR>

• ERROR => Es2ResCreateFiles: Es2IResCreate failed [es2xx.c 1283]<BR>

• ERROR => Es2ResCreate: Es2ResCreateFiles failed [es2xx.c 1461]<BR>

• ERROR => DpEmInit: Es2ResCreate (1) [dpxxdisp.c 10125]<BR>

• ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c 9993]<BR>

• DP_FATAL_ERROR => DpSapEnvInit: DpMemInit<BR>

• DISPATCHER EMERGENCY SHUTDOWN ***<BR>

increase tracelevel of WPs<BR>

NiWait: sleep (10000ms) ...<BR>

NiISelect: timeout 10000ms<BR>

NiISelect: maximum fd=1<BR>

NiISelect: read-mask is NULL<BR>

NiISelect: write-mask is NULL<BR>

When i try to clean / delete this files with cleanipc 12 remove, I get the following message:<BR><BR>

Show/Cleanup SAP-IPC-Objects V2.3, 94/01/20<BR>

===========================================<BR><BR>

Running SAP-Systems (Nr)...:<BR><BR>

-

---

Clear IPC-Objects of Sap-System 12 -

---

<BR><BR>

OsKey: 21238 0x000052f6 Semaphore Key: 38 removed<BR>

OsKey: 21260 0x0000530c Semaphore Key: 60 removed<BR>

OsKey: 58900112 0x0382be90 SCSA Shared Memory Key: 58900000 removed<BR><BR>

Number of IPC-Objects...........: 3<BR>

Number of removed IPC-Objects...: 3<BR>

Summary of all Shared Memory....: 4659.0 MB (may be incomplete when not in superuser mode)<BR>

SAP_ES file: /dev/shm/SAP_ES2_12_004 remove failed **** - errno = 13 (Permission denied)<BR>

SAP_ES file: /dev/shm/SAP_ES2_12_003 remove failed **** - errno = 13 (Permission denied)<BR>

SAP_ES file: /dev/shm/SAP_ES2_12_002 remove failed **** - errno = 13 (Permission denied)<BR>

SAP_ES file: /dev/shm/SAP_ES2_12_001 remove failed **** - errno = 13 (Permission denied)<BR>

SAP_ES file: /dev/shm/SAP_ES2_12_000 remove failed **** - errno = 13 (Permission denied)<BR><BR>

Number of SAP_ES files found:.............: 5<BR>

Number of SAP_ES files removed:...........: 0<BR><BR>

So, to start this instance we have to reboot the server. VCM is not active on this system.<BR>

Any Idea to solve this problem?<BR><BR>

Regards<BR><BR>

Arkadius Sobkow

Edited by: Arkadius Sobkow on May 28, 2009 1:49 PM

Edited by: Arkadius Sobkow on May 28, 2009 1:50 PM

[Former Member]

hi,

Try to delete the files from root.

[former_member838162]

Hello Rajeev,

from the error message I assume you use Solaris.

The file SAP_ES2_03_000 is a memory mapped file. Solaris changes the file name to .SHMDSAP_ES2_03_000 and stores it in the /tmp file system.

cleanipc 03 remove

should delete it.

Regards,

Klaus

[Former Member]

Hi All,

Just forgot to mention that we did cleanipc and ipcrm before starting SAP instances. Still we are getting the same error.

[Former Member]

Hi,

Have a look at note 854170

Narsi

[Former Member]

Hi,

Thanks for the response.

As I said in the last thread, VMC parameters were never an issue and all was working fine. The referred note explains on VMC parameters value and not on the issue we were facing.

Anyway, the problem was resolved after rebooting the entire server from OS level. We still could not identify in which filesystem SAP_ES2_03_000 file exists.

Thanks & Regards

Rajeev

[Former Member]

The problem is resolved after reboot from OS.