sapstart error

[Former Member]

Hi

I am installing ECC 6.0 on RedHat and Maxdb. Everything was going fine,

but the phase NW_CI_Instance_Start fails.

So, I am trying to start manually with startsap. Workprocess don't

start and in work directory dev_disp shows the following error:

• ERROR => EsPMapCreateResource: open /SAP_ES_00_000 failed (13:

Permission denied) [esuxmap.c 20

9]

• ERROR => <EsMap> EsPMapCreateResource failed (1) [esxxmap.c 531]

• Error 1 while initializing OS dependent part.

• ERROR => DpEmInit: EmInit (1) [dpxxdisp.c 9584]

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

• DP_FATAL_ERROR => DpSapEnvInit: DpMemInit

• DISPATCHER EMERGENCY SHUTDOWN ***

There aren't dev_w* files in work dir.

I downloaded and installed newest kernel patch level.

Any hint?

Thanks

[Former Member]

Hannes,

I don't have 'es/implementation' key in SAP profile, so I can't understand the 'permission denied' message. However, I think this is a good start point.

Did you have any idea to identify this "/SAP_ES_00_000 permission denied"?

Thanks

[hannes_kuehnemund]

Dear Raffaele,

then the default value, 'es/implementation = map' is used by the kernel. If this key is set to map, it uses the /dev/shm shared memory. Have you already checked, if the user <sid>adm is allowed to write to /dev/shm, e.g. by executing

su - <sidadm> -c 'touch /dev/shm/1

? Anyway, another possibility is to set es/implementation = std, which tells the SAP system, not to use /dev/shm (but SysV shared memory).

Thanks,

Hannes

[Former Member]

Hallo Hannes

your hints are very useful.

Executing "su - <sidadm> -c 'touch /dev/shm/1' " I discovered that sidadm is not allowed to write. System replies with "permission denied". I will investigate on this furthermore.

However, setting es/implementation = std, the system starts. So, the problem was fixed.

Thanks a lot for your precious help.

Bye

Raffaele

[g_awater]

I had the same thing trying to install solman 7 sr3 on Ubuntu 64bits in VMware (just for testing purposes, I know it's not a supported OS).

Since es/implementation = std is the way to go for 64bits OS, I wonder why it is not default in the profile?

[joo_migueldimas]

I had the same problem... with ECC 6.0, Red Hat with Oracle 11.2 and this was the solution... I create the parameter es/implementation in instance profile with value std instead map... so I ask the same questions as you why this parameter is not set at default in the profile of any system that runs on Linux/Unix platform!? I don´t understand why!!!!

Kind regards,

João Dimas - Portugal

[markus_doehr2]

> Since es/implementation = std is the way to go for 64bits OS, I wonder why it is not default in the profile?

If SAP would just change that in the middle of the kernel as new default tons of customers would run into problems if they upgrade their kernel.

It is the default for newer kernels (7.20).

Markus

[joo_migueldimas]

Ok Markus... I understood that point! This question has the objective to come to know actualy if we have to change the value of this parameter so that we can avoid this error in others systems!

Can you tell me in which that parameter is related ? I heared it is related with shared memory... I would like to understand better what does it do?...

There are some sap notes or documents that explain more better what does it do?

Thank you Markus,

Kind regards,

João Dimas - Portugal

[markus_doehr2]

But why that problem doesn´t happen in others sap systems that we have? Because they are running with exactly same kernel and platform (Red Hat and Oracle 11.2g) and that parameter, it have the default value = map..?! This question has the objective to come to know actualy if we have to change the value of this parameter so that we can avoid this error in others systems!

Because their memory configuration is different? They may have /dev/shm mapped up properly (different OS patchlevel) etc. - there can be a number of reasons.

There are some sap notes or documents that explain more better what does it do?

Well - I'd open a browser at http://service.sap.com/notes, enter

es/implementation

as search term and component

BC-OP-LNX*

and check yourself

--

Markus

[joo_migueldimas]

LOL... Ok Markus

As I read in note 941735 it is recomended change the value of es/implementation to std.

STD implementation (es/implementation=std)

           With this variant, the memory management of an SAP system on Linux is the same as
on standard UNIX systems. This means that all user contexts are displayed in the address space
at the same time, which means that this variant is only available for 64 bit systems.

While the MAP implementation should be used exclusively on 32-bit Linux in more cases, both variants
can be used on 64-bit systems. However, since there are no longer any 32-bit restrictions, there is no
longer any need to use the special MAP implementation on 64-bit Linux systems .

For this reason, the STD implementation for SAP systems on 64-bit Linux is activated by default as of
SAP Kernel 7.10.

Thank you,

Best regards,

João Dimas - Portugal

[Former Member]

stderr1

(5171) New Child Process created.

(5171) Starting local Command:

Command: dw.sapUPV_DVEBMGS00

pf=/usr/sap/UPV/SYS/profile/UPV_DVEBMGS00_camellia

***

• DISPATCHER EMERGENCY SHUTDOWN => DpSapEnvInit: DpMemInit

[Former Member]

start profile

SAPSYSTEMNAME = UPV

SAPSYSTEM = 00

INSTANCE_NAME = DVEBMGS00

DIR_CT_RUN = $(DIR_EXE_ROOT)/run

DIR_EXECUTABLE = $(DIR_INSTANCE)/exe

DIR_PROFILE = $(DIR_INSTALL)/profile

PF = $(DIRPROFILE)/UPV_DVEBMGS00_xxxxxx

SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)

SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)

SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)

#----

---

1. Copy SAP Executables

#----

---

Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF)

#----

---

1. Start SCSA administration

#----

---

Execute_01 = local $(DIR_EXECUTABLE)/sapmscsa pf=$(_PF) -n

#----

---

1. Start SAP messaging service

#----

---

MS = ms.sap$(SAPSYSTEMNAME)$(INSTANCE_NAME)

Execute_02 = local rm -f $(_MS)

Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/msg_server$(FT_EXE) $(_MS)

Start_Program_00 = local $(_MS) pf=$(_PF)

#----

---

1. Start application server

#----

---

DW = dw.sap$(SAPSYSTEMNAME)$(INSTANCE_NAME)

Execute_04 = local rm -f $(_DW)

Execute_05 = local ln -s -f $(DIR_EXECUTABLE)/disp+work$(FT_EXE) $(_DW)

Start_Program_01 = local $(_DW) pf=$(_PF)

#----

---

1. Start syslog collector daemon

#----

---

CO = co.sap$(SAPSYSTEMNAME)$(INSTANCE_NAME)

Execute_06 = local rm -f $(_CO)

Execute_07 = local ln -s -f $(DIR_EXECUTABLE)/rslgcoll $(_CO)

Start_Program_02 = local $(_CO) pf=$(_PF) -F

#----

---

1. Start syslog send daemon

#----

---

SE = se.sap$(SAPSYSTEMNAME)$(INSTANCE_NAME)

Execute_08 = local rm -f $(_SE)

Execute_09 = local ln -s -f $(DIR_EXECUTABLE)/rslgsend $(_SE)

Start_Program_03 = local $(_SE) pf=$(_PF) -F

#----

---

1. Start internet graphics server

#----

---

IG = ig.sap$(SAPSYSTEMNAME)$(INSTANCE_NAME)

Execute_10 = local rm -f $(_IG)

Execute_11 = local ln -s -f $(DIR_EXECUTABLE)/igswd_mt $(_IG)

Start_Program_04 = local $(_IG) -mode=profile pf=$(_PF)

rsdb/dbid = UPV

dbs/ada/schema = SAPUPV

[Former Member]

I tried with reboot but the problem wasn't fixed.

dev_disp shows the same error.

[hannes_kuehnemund]

Dear Raffaele,

which shared memory implemenation of SAP are you using? Could you please check your SAP profile for the 'es/implementation' key? If it is set to map, please check if the <sid>adm user is allowed to write to /dev/shm (because of permission denied).

Thanks,

Hannes

[markus_doehr2]

Was the system shutdown cleanly or did you kill the workprocesses before? It seems, that some shared memory (and the ´tmpfs´) filesystem was not correctly cleaned. A reboot will solve that problem but the cause of that is unknown then...

--

Markus

[former_member204746]

please post the contents of your start profile. also check if you can find any stderr* files.

[Former Member]

If you can reboot your system? Try it.

regards

tamilboy