RZ20 Service "<SID>\Background\...\BackgroundService" missing

[Private_Member_19084]

Hello experts,

we are facing the issue, that in rz20 the service "<SID>\Background\...\BackgroundService" is missing, which gives information about the Background-Job environment.

I already tried the reset via RZ21 a few times, but didn't help.

Any other ideas for this?

Kind regards

[alwina_enns · Accepted solution]

Hello Christian,

how many instances has the system? Could you please check in "RZ21 --> Topology --> Context Overview", on which instance the background context is located and if this instance has background work processes available? Does this instance have enough space in CCMS shared memory segment?

Regards, Alwina

[Private_Member_19084 · Accepted solution]

Hello Alwina,

we have 4 instances.

It runs one of the instances were we have background-processes available.

How can I check the shared-memory?

[alwina_enns · Accepted solution]

Hello Christian,

please check it under:

RZ20 --> SAP CCMS Technical Expert Monitors
               -->  CCMS Selfmonitoring
                     --> <SID> --> MoniInfra_<instance>
                             --> Space
                       double click on "FreeAlertSlots"

are enough slots available here?

Please check also the selfmonitoring structure for open alerts related to the data collectors for the background monitor, if you see alerts about data collector termination.

If you cannot find a reason in selfmonitoring structure, then you should delete and recreate the background monitor.

Regards, Alwina

[Private_Member_19084 · Accepted solution]

Hello Alwina,

thank you very much, very good information - didn't know this.

So I have 0% availalbe "FreeAlertSlots".

However, in screen most percentage are by around 95%.

so should I increase alert/MONI_SEGM_SIZE?

[Private_Member_19084 · Accepted solution]

Or is there another possibility to free some memory?

Because it is only on one system, sure, it is the most used sytem, however I think for monitoring values it should not make a difference.

[alwina_enns · Accepted solution]

Hello Christian,

for which slots there is no more space? You have several possibilities:

1. Increase the value for alert/MONI_SEGM_SIZE on the affected instance --> disadvantage is, that after a while the space will be consumed again, if you did not find the causeer

2. If you can identify the monitor consuming the space, then you can check, what creates this monitor (log attributes lines? alerts?) and if this monitor is OK, or if this monitor has a  problem. If you are not using this monitor then you can disable it and delete its structure in RZ20.

Is this a BW system? In a BW system the process chains monitor can consume to much space.

3. You could move the background context in RZ21 to the instance, which has enough space in monitoring segment --> disadvantage is, that the context will be fixed to a segment of one instance, and if this instance is not available, the monitor will not be available too.

Regards, Alwina

[Private_Member_19084 · Accepted solution]

Hello Alwina,

sorry I read it the wrong way.

That 95% around are free space sorry.

However, I've moved now to another instance and at the moment it works.

Thank you very much for your help.

Kind regards

[alwina_enns · Accepted solution]

Hello Christian,

you are welcome 🙂

Regards, Alwina