Failed startup BI 7.01 ABAP

[Former Member]

Hi Friends,

I have some issue when starting a centralized NW BI 7.01(EHP1).

Sometimes this system doesn´t start an the dev_w0 log trace shows:

I *** ERROR => ShmGet: Shared Pool Space exhausted. PoolKey=10

M *** ERROR => AlCreateAttachShm_AS: ShmCreate (SHM_CREATE) rtc =

M *** ERROR => CCMS: sAlInit: could not create/attach shared memory key 13 (rtc = 249)

M *** ERROR => AlDpAdmInit: sAlInit rtc = 249

M ***LOG R19=> ThInit, AlThAdmInit` ( ALERTS 000249)

I have reviewed in RZ10 the instance profile parameter abap/buffersize and the value for this was 2097152, because of a review another X BI system we decreese this value to 400000 but the problem still happening. The temporal solution we´ve taken is to start manually DB and after run sapstart script, so in this case system starup Ok!

I don´t have a lot experince in parameters tunning, and I would like you to give me an opinion of this problem. The system is installed on AIX 6.1 plataform and it has around of 10 GB of memory. The most important relevant parameters are:

abap/buffersize 400000

gw/max_sys 2000

rdisp/tm_max_no 2000

rdisp/appc_ca_blk_no 2000

rdisp/wp_ca_blk_no 1000

ES/SHM_SEGS_VERSION 2

ztta/roll_area 6500000

em/global_area_MB 256

sap/bufdir_entries 10000

zcsa/presentation_buffer_area 10000000

zcsa/db_max_buftab 10000

zcsa/table_buffer_area 50000000

rsdb/cua/buffersize 5000

rtbb/buffer_length 30000

rtbb/max_tables 2000

rsdb/ntab/entrycount 30000

login/system_client 100

login/no_automatic_user_sapstar 1

SAPSYSTEM 00

rdisp/wp_no_dia 18

rdisp/wp_no_enq 1

rdisp/wp_no_vb 6

rdisp/wp_no_vb2 3

rdisp/wp_no_spo 1

ipc/shm_psize_10 154000000

ipc/shm_psize_40 112000000

Thanks in advance. Enrique.

Edited by: Enrique Sanchez on Nov 9, 2009 8:35 PM

[Former Member]

Please refer to the following SAP Note and make the setting as suggested:

599985

This should sovle your problem.

Edited by: Augustus Cristicini on Nov 9, 2009 10:57 PM

[Former Member]

hi ,

please through this

Increase the size of the shared memory pool in the profile, for example, with

ipc/shm_psize_10 = <size in bytes>

ipc/shm_psize_40 = <size in bytes>

-or-

if the pool cannot or should not be increased, you can extract individual shared memories from the pool, for example, with ipc/shm_psize_06 = 0 Extract ABAP program buffer (key 6) from the pool

ipc/shm_psize_06 = -40, or move it into pool 40

it may help you to resolve the error