Log is full DBCRASH each time log backup is done

[Former Member]

Log is full in our DEV server.  Everytime I do a log backup, the DB turns offline.

How do I resolve this.

Thanks.

[MichaelTe · Accepted solution]

Hello,

please attach the database error file and/or the database messages file..

Regards, Michael

[Former Member · Accepted solution]

Attached portion of knldiag.err when the crash happened..

knldiag-err.txt.zip

[MichaelTe · Accepted solution]

Hello,

it seems that somethings wrong with your log, obviously.

With the following commands you could clear the log and hopefully the DB will start again.

But if you do this, be aware that you will lose data!

dbmcli -d <SID> -u control,<xxx>                                                 

>db_admin                                                                   

>db_connect                                                    

>db_execute clear log

>db_offline

>db_online

Regards,

Michael

[yashwanthkumar_kethineed]

Hello Rizza,

What is version of MaxDB Software ?

Please attach the logs KnlMsg / Knldiag & dbm.prt from the database RUNDIRECTORY.

Regards,

Yashwanth

[Former Member]

MaxDB 7.6.00   Build 018-123-119-055

[yashwanthkumar_kethineed]

Hello Rizza,

From the attached Knldiag log, I see you run into a log IOSequence mismatch problem.

2013-05-04 11:20:17    21 ERR 20048 Log      Log_VolumeIterator.cpp:309

2013-05-04 11:20:18    21 ERR 20048 Log      2013-05-04 11:20:17 Log Error 20048

2013-05-04 11:20:18    21 ERR 20048 Log      read: offset 79934 expected iosequence 58621234 found 58621235

ioseq + 1 found ...

How large is your log volume ??

Workaround for this issue:

-> Perform a complete data backup in the admin state (db_admin)

-> As a backup, just copy the LogVolumes to another location

-> Run "db_execute clear log" in admin state

-> Restart the database online

-> I would recommend to switch the autolog backup on to avoid the log full situtaion in furture.

Also the version of databsae you are using is quiet old one. I would recommend you to upgrade to the latest possible versions to avoid any known issues.

Regards,

Yashwanth