Quantcast
Channel: SCN: Message List - SAP MaxDB
Viewing all articles
Browse latest Browse all 2539

Re: Log is full DBCRASH each time log backup is done

$
0
0

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


Viewing all articles
Browse latest Browse all 2539

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>