Recovery from Corrupted ODB

From MidasWiki
Revision as of 15:49, 10 November 2015 by Suz (talk | contribs) (Created page with "{{Pagelinks}} = Links = <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> * ODB Access and Use * Odbedit </div> === How to recover from a corru...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


How to recover from a corrupted ODB

  • Stop your front-ends, mlogger, mhttpd, etc.
  • Remove the shared memory associated to ODB buffer. Find the shared memory segment by doing
ls -l /dev/shm

then remove the segment that will be something like /dev/shm/*_test_ODB_SHM

  • Move the old ODB files. These will be in the location given by Exptab, e.g. ~/online
cd online
  • Restart ODB with larger size using odbedit e.g.
odbedit -s 100000000
  • Reload the last saved ODB dump you have (see save and reload the ODB). These dumps are typically called something like 'online/history/*.xml'.

So from odbedit you do something like

odbedit> load history/run00071.xml
  • Your ODB should now be fixed.