instance profile : system not started

[Former Member]

Dear SAP Guru,

After modifing the following parameters in SAP instance profile SAP system is not being started.

The parameter are:

abap/heap_area_dia

abap/heap_area_nondia

abap/heap_area_total

The initial size of the parameter was maintained the default value and I have changed to 4 GB.

After modifing the parameter, I have checked the sappfpar check and already applied the reccomendation. Still the SAP instance is not starting.

When I revert back with the old profile system starts properly.

Please let me know what could be the reason.

Regards,

[mercedes_fernandez]

Hello,

you'd need to have a look in the trace files (dev_ms, dev_disp, sapstart.log, stderr*. etc) in the work directory to check the error causing the instance not starting.

kind regards,

Mercedes

[Former Member]

Hi Mr. Mercedes,

I have checked in the "dev_disp" log file the following errors has seen.

• ERROR => ESSHM: ====================> ERROR <====================

[esuxshm.c 832]

• ERROR => ESSHM: Error during Initialization for Work Process 0 in

SHM_EsInit [esuxshm.c 833]

• ERROR => ESSHM: Configuration variable ES/SHM_MAX_PRIV_SEGS

[esuxshm.c 834]

• ERROR => ESSHM: Value Provided 15 [esuxshm.c 835]

• ERROR => ESSHM: Should be between 0 and value provided for

ES/SHM_PROC_SEG_COUNT 2 [esuxshm.c 836]

• ERROR => ESSHM: ====================> ERROR <====================

Kinldy guide me what should I do?? There is no other error in other log files you have mentioned.

Regards,

[Former Member]

The error is show in dev_dis is

MBUF state OFF

DpCommInitTable: init table for 500 entries

DpFileInitTable: init table for 7600 entries

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

DpRqQInit: Parameter rdisp/queue_lock_level = 2

• WARN Shm 31 in Pool 10 4107 KB estimated 5636 KB real ( +1528 KB +37 %)

rdisp/queue_size_check_value : -> on,50,30,40,500,50,500,80

ThTaskStatus: rdisp/reset_online_during_debug 0

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

• WARN Shm 51 in Pool 10 3125 KB estimated 7578 KB real ( +4453 KB +142 %)

EM/TOTAL_SIZE_MB = 10240

• ERROR => ESSHM: ====================> ERROR <==================== [esuxshm.c 832]

• ERROR => ESSHM: Error during Initialization for Work Process 0 in SHM_EsInit [esuxshm.c 833]

• ERROR => ESSHM: Configuration variable ES/SHM_MAX_PRIV_SEGS [esuxshm.c 834]

• ERROR => ESSHM: Value Provided 15 [esuxshm.c 835]

• ERROR => ESSHM: Should be between 0 and value provided for ES/SHM_PROC_SEG_COUNT 2 [esuxshm.c 836]

• ERROR => ESSHM: ====================> ERROR <==================== [esuxshm.c 837]

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

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

• DP_FATAL_ERROR => DpSapEnvInit: DpMemInit

• DISPATCHER EMERGENCY SHUTDOWN ***

Please let me know what to be done next??

[Former Member]

The error is show in dev_dis is

MBUF state OFF

DpCommInitTable: init table for 500 entries

DpFileInitTable: init table for 7600 entries

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

DpRqQInit: Parameter rdisp/queue_lock_level = 2

• WARN Shm 31 in Pool 10 4107 KB estimated 5636 KB real ( +1528 KB +37 %)

rdisp/queue_size_check_value : -> on,50,30,40,500,50,500,80

ThTaskStatus: rdisp/reset_online_during_debug 0

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

• WARN Shm 51 in Pool 10 3125 KB estimated 7578 KB real ( +4453 KB +142 %)

EM/TOTAL_SIZE_MB = 10240

• ERROR => ESSHM: ====================> ERROR <==================== [esuxshm.c 832]

• ERROR => ESSHM: Error during Initialization for Work Process 0 in SHM_EsInit [esuxshm.c 833]

• ERROR => ESSHM: Configuration variable ES/SHM_MAX_PRIV_SEGS [esuxshm.c 834]

• ERROR => ESSHM: Value Provided 15 [esuxshm.c 835]

• ERROR => ESSHM: Should be between 0 and value provided for ES/SHM_PROC_SEG_COUNT 2 [esuxshm.c 836]

• ERROR => ESSHM: ====================> ERROR <==================== [esuxshm.c 837]

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

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

• DP_FATAL_ERROR => DpSapEnvInit: DpMemInit

• DISPATCHER EMERGENCY SHUTDOWN ***

Please let me know what to be done next??

[mercedes_fernandez]

Hello,

in SAP Note 352604 describes which parameter ES/SHM_SEG_COUNT or ES/SHM_USER_COUNT you need to increase depending of the specific return code.

kind regards,

Mercedes

[Former Member]

Dear Mercedes

Thanks for your reply. I will update you once I will apply the notes which you have mentioned.

Thanks and Thanks for your time.

Regards,