Shadow instance not starting in Preprocessing phase

[erugu_suresh]

Dear all,

While in Preprocessing phase, shadow system is not able to start.

In JAVA MMC message server is runnning but dispatched stopped status. In trace file we are getting below error message.

"*** ERROR => shmget(10203,208896000,2016) (28: No space left on device) [shmux.c      1530]

Tue Oct  6 15:01:39 2015

*** ERROR => DpShMCreate: ShmCreate SHM_DP_CA_KEY(rc=1) [dpxxca.c     143]

*** ERROR => DpIPCInit2: DpShMCreate [dpxxtool2.c  579]

*** DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit2

*** DISPATCHER EMERGENCY SHUTDOWN *** "

FYI we have removed all shared memory and semaphores. Another point when I stop main instance, shadow instance up and running.

But when shadow instance require main instance, main instance will not be getting up and throwing same error of shadow instance

Could you please suggest on this.

Thanks in advance.

Regards

Suresh

[former_member264034 · Accepted solution]

Hi,

For Linux systems please ensure your system is properly configured as per note 941735.

Regards,
Aidan

[erugu_suresh · Accepted solution]

Hi Aidan,

Thanks for the note I will check and get back to you.

Regards

Suresh

[Former Member]

What is the OS you are using? For Linux pay attention to kernel.shmall, kernel.shmmni and kernel.shmmax parameters.

[erugu_suresh]

Hi Roman,

OS: Linux, below are the kernel parameters, do i need to change any parameter?

kernel.shmmax = 53136829430

kernel.shmall = 5242880

kernel.shmmni = 4096

Regards

Suresh

[Former Member]

What is the exact version of your Linux? Have you specified/changed any of them manually? Please increase shmall twice and try again.

[Mofizur]

Hi Suresh,

Please go through following wiki..

ERROR shmget ... (28: No space left on device), ERROR semget ... (28: No space left on device) - Bas...

A: When starting the SAP system following error appears in dev_wxx trace:

• ERROR => e=28 shmget(...) (28: No space left on device)
• ERROR => shmget(...) (28: No space left on device)

Check the OS configuration:

Linux

kernel.shmmax in /etc/sysctl.conf. Activate changes by 'sysctl -p'.
If the parameter apprer more than once there comment out the lower one by #, like:

> cat /etc/sysctl.conf | grep shm
kernel.shmmax = 68719476736
kernel.shmall = 41943040
#kernel.shmmax=23136829430   <<<--- this
#kernel.shmall=5242880   <<<--- and this

Thanks,

Mofizur

[Mofizur]

Hi,

Your trace file says...

28: No space left on device

Please check the space availability at OS level.

Thanks,

Mofizur

[erugu_suresh]

Hi Mofizur,

please find the below space details

Filesystem                 Size  Used Avail Use% Mounted on

/dev/sda2                  193G   94G   90G  52% /

tmpfs                      7.9G  144K  7.9G   1% /dev/shm

/dev/sda1                  985M   46M  889M   5% /boot

/dev/sdb12                  44G  2.8G   39G   7% /sapmnt

/dev/sdb9                   58G  3.0G   52G   6% /sybase/SID

/dev/sdb1                  337G  101G  220G  32% /sybase/SID/sapdata_1

/dev/sdb2                  337G  101G  220G  32% /sybase/SID/sapdata_2

/dev/sdb3                  337G  101G  220G  32% /sybase/SID/sapdata_3

/dev/sdb4                  337G  101G  220G  32% /sybase/SID/sapdata_4

/dev/sdb5                  337G  101G  220G  32% /sybase/SID/sapdata_5

/dev/sdb10                  53G   11G   41G  21% /sybase/SID/sapdiag

/dev/sdb6                  337G   26G  295G   8% /sybase/SID/saplog_1

/dev/sdb11                  49G   13G   34G  27% /sybase/SID/saptemp

/dev/sdb14                  20G   11G  8.1G  56% /sybase/SID/sybsecurity

/dev/sdb15                  20G  946M   18G   6% /sybase/SID/sybsystem

/dev/sdb13                  25G  2.2G   21G  10% /sybase/SID/sybtemp

/dev/sda5                   31G  177M   30G   1% /tmp

/dev/sdb8                   63G  3.7G   56G   7% /usr/sap

/dev/sdb7                  116G   33G   77G  30% /usr/sap/trans

Thanks

Suresh