Can't connect to PI instance - No space left on device

[Former Member]

Hi all,

we have installed two instances on one host that share one Oracle DB. One SRM system and one NW 7.0 double stack with PI. The problem is that we can't connect to the PI system. SAP Logon says "connection refused" as if the server wasn't there.

sapstart finishes without any error message, R3trans -d doesn't give an error either.

dev_disp contains these lines:

• ERROR => e=28 semget(28602,1,2047) (28: No space left on device) [semux.c 924]

• ERROR => DpRqQInit: SemInit SEM_REQ_QUEUE_DIA_KEY [dpxxqueu.c 321]

• DP_FATAL_ERROR => DpSapEnvInit: DpRqQInit

• DISPATCHER EMERGENCY SHUTDOWN ***

No directory on the file system seems to be full though and there's about 10 gig of free RAM.

The OS is Solaris 10.

Thanks for any hints,

Paul

[Former Member]

Hi,

Kindly try R3trans -x and check the logs.

Apart from that it seems to be a memory allocation issue. Hence please check with the memory parameters of your SAP system.

Regards,

Prem

[Former Member]

Prem,

thanks for your reply.

R3trans -x finishes without error. Also, trans.log doesn't contain an error message.

How do I check the memory parameters, and which ones?

Paul

[Former Member]

Hi paul,

Please check the database free area (and not the only the File system free area on UNIX systems).

Please logon to the OS level using ora<sid> user and check the datafiles free space using brtools utility. Also check for the space on / , /tmp and /usr/sap/trans

Regards,

Prem

[Former Member]

Problem solved. The reason for the trouble was the fact that for some reason the setting for

project.max-sem-ids

was not effective although it was set correctly in /etc/project. By logging in again via

su - <sid>adm

it worked. Don't ask me why, but it helped.

Paul

[Former Member]

By the way, the /etc/project file contains the line

<sid>:200:SAP System <SID>:<orasid>,<sid>adm::process.max-sem-nsems=(priv,2048,deny);project.max-sem-ids=(priv,1024,deny);project.max-shm-ids=(priv,256,deny);project.max-shm-memory=(priv,18446744073709551615,deny)

for both instances.

Maybe an issue with the shared memory?

Please advise,

Paul