alert/MONI_SEGM_SIZE Maximum value

[Former Member]

Hi All,

Our system has this parameter value as

alert/MONI_SEGM_SIZE =   60000000

Can this parameter be increased further?

If yes, to what value it can be extended?

Our server is 701 release.

[srinivasan_vinayagam · Accepted solution]

Dear Yadoji,

Refere below note:

135503 - CCMS monitor architecture: Meaning of profile parameters

731165 - RZ20: CCMS parameters for segment control

[Former Member · Accepted solution]

Hi Srinivasan,

Thanks for the info,

I have gone through the notes but i didn't get my answer yet.

Can you please tell me the max value that the parameter can be extended to?

Regards,

Vishnu

[srinivasan_vinayagam · Accepted solution]

Dear Yadoji,

The values are set by reference of that two notes only.

Not required to increase the value(my guess).

SAP CCMS Installation and Registration - Basis Corner - SCN Wiki

Regards,

V Srinivasan

[Former Member · Accepted solution]

As per the note, It says the parameter can be increased by whole number multiples of 2

Currently value is : 30 * 2,000,000 = 60000000

so can we increase it to : 35 * 2,000,000 = 70000000

Please suggest ..

Actually issue is we are getting error while processing the BI Loads and the reason is like "The shared memory space for the log attributes is completely exhausted"

So thought of increasing this parameter so that we can get rid of this issue.

Regards,

Vishnu

[alwina_enns · Accepted solution]

Hello Vishnu,

you can set it to 100000000, it will not be a problem for RZ20. In a BW system it could be required to have a higher value for alert/MONI_SEGM_SIZE.

Please check also the methods:

RSPC_CCMS_AGENT
RSPC_CCMS_STARTUP

in RZ21 --> Methods --> Method definitions

and set the parameter

DAYS_TO_KEEP_LOGS

in the both methods to a small value.

Regards,
Alwina

[Former Member]

Hi,

Thanks Alwina and Srinivasan for your valuable suggestions,

We did a cleanup of the log attributes for the process chains from BWCCMS transaction manually and that resolved the issue.

Regards,

Vishnu

[alwina_enns]

Hello Vishnu,

if you need to increase the value, then you should do it step by steps. I have seen systems with really high value for this parameter (about 400 000 000), but a high value means a huge CCMS shared memory segment with many MTEs. The CCMS dispatchers (autoabap and background dispatcher) can process only a certain number of MTEs at each run. If you have more MTEs than can be processed by the dispatcher at one run, then the dispatchers will need several runs to update all MTEs and the whole CCMS infrastructure will be unstable. Before increasing the value for alert/MONI_SEGM_SIZE you have to check what consumes space in CCMS shared memory segment, if a data supplier creates wrongly too many MTEs (logs, alerts...) and if this is an error situation.

Why do you need to increase alert/MONI_SEGM_SIZE? Which slots in monitoring segment are consumed?

Regards,
Alwina