1.Issue Description:
The SAP Central Instance cann't start when reboot the Instance.
The dev_disp log as below:
*** ERROR =>
[esnti.c 2661]
*** ERROR => EgInit: EsCreateShared() failed. info='EG_GLOBAL_AREA',
blocks=8005, rc=11 [egxx.c 307]
*** ERROR => DpEmInit: EmInit (1) [dpxxdisp.c 10250]
*** ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c 10175]
*** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit
*** DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs.
2.Root Case Analyse:
Check Note 841944 - EgInit: EsCreateShared() failed. info='EG_GLOBAL_AREA'...;
With the 6.40 kernel, the ABAP Shared Object are added again and require additional address space in the EG.
The size for shared objects is determined by the abap/shared_object_size_MB parameter (the default is 20 MB).
If em/global_area_MB is set too high, then the entire EG exceeds 256 MB.
That is, the following applies in particular for AIX:
em/global_area_MB + abap/shared_object_size_MB < ES/SHM_SEG_SIZE;
This is still the case in Realse 700.
Use T-code RZ11 to check in SAP system that
the parameter 'em/global_area_MB' value is 32000
and the parameter 'abap/shared_object_size_MB' value is 20,
but the parameter 'ES/SHM_SEG_SIZE' value is 4096, the first two values is greater than the latter value,so the instance can not start.
3.Solution:
Configure the instance profile accordingly, reduce the parameter 'em/global_area_MB' value from 32000 to 4000,
then the instance can start successfully.
4.The experience gained:
We need to find the Root Case by checking the Error log(dev_disp/dev_w0), and try to find the Solution with
the Key word of Error log.
5.Key Word:
"EG_GLOBAL_AREA" & "em/global_area_MB"
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/23006853/viewspace-681808/ ,如需转载,请注明出处,否则将追究法律责任。