Solution Manager rises an MAXDB Log fill level error

[AlessandroBuech]

Hello all, 

this might be a bit of a specific Error, however i wasn't able to find a true solution so i want to ask here. 

We get Alerts from our Solution manager at random times from two Content Server Databases with the following text:

Activated (Log fill level > 1.5 * Log segment size)

I am not really sure what that actually means and even more importantly, how to solve the issue. We do not seem to have any issues that the log runs full, or the System is not able to write down logs. So asking the AI, it states that the log Segment size would need to be increased. That however would mean i would need to recrate the DB as Log Segments cannot easily be recreated as Disk Segments. 

Has anyone encountered this?

Thank you very much!

Alessandro Büch

[aka204]

Hello Alessandro,

AI was right ;0)

The reason for alert is, it was concerning that having log filling at 1.5*LogSegmentSize your system is at danger, because normally the log is filled about LogSegment level and afterwards ideally it must be saved with the log backup. If autolog backup is activated in your system, it will always trigger after filling of the LogSegment size on the log volume. So alert is concerning about that either autolog backup is out of function or you backup infrastructure is too slow. Getting LOG FULL situation means stand still.

However in many customer environments we could see, that log segment size compared to the size of the log volume is too low, therefore reaching the log volume filling of 1.5 of log segment size means no danger. But alerting is hard coding and hard meaning.

The log segment size is defined by the MaxDB parameter AutologBackupSize and expressed in the 8k pages. If it is too low and you are saving the backups not by autolog , but for example timely scheduled, it can easy happen that you reach 1.5 of log segment size filling. If the sum size of the log volumes is much higher as AutoLogBackupSize, in this case you can probably increase the AutologBackupSize parameter. However if you run log backups with autolog, it will increase the size of log backups and also increase the time gap between auto log backups, what impact the availability of data in case of restore.

If you schedule log backups and not use autolog backup, the AutoLogBackupSize will have only ´CCMS alerting effect.

Regards, Alexander