This error is intermittent. The last time it happened it resulted in stuck db - because of errors in this file logs could not be backed up and in combination with some other conditions it almost resulted in loss of db which is very important, that would have significant consequences for me. I repair file manually and unpredictably it get's corrupted again.
I've got support about this error from SAP but not very helpful, what they told me basically was, repair it manually. This makes backup and even maxdb itself unreliable. For sure, such a simple error that is not hard to trace and repair over such a long period of time (from sap notes I saw this error reported since 2012) and that makes maxdb development team look unprofessional.
I have several maxdb 7.9 based system, some of them in the latest version (and patch) and this error still occurs.
As I wrote, we are using SLES 11SP02, specific version for SAP.
This is unacceptable. I wish we could use Oracle in stead.