Recovery from Corrupted ODB: Difference between revisions

From MidasWiki
Jump to navigation Jump to search
(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...")
 
(The midas documentation has moved to https://midas.triumf.ca/docs/)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{Pagelinks}}
The midas documentation has moved. See [https://midas.triumf.ca/docs/develop/features/core_system/odb/configuring/#corruption Corruption] in ODB: configuring for the new documentation about recovering a corrupted ODB.
 
= 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 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
mv .ODB.SHM .ODB.SHM.BAD
* Restart ODB with larger size using [[odbedit]] e.g.
odbedit -s 100000000
* Reload the last saved ODB dump you have (see [[ODB#Save and reload the ODB|save and reload the ODB]]). These dumps are typically called something like 'online/history/*.xml'.
So from  {{Utility|name=odbedit}} you do something like
odbedit> load history/run00071.xml
* Your ODB should now be fixed.
 
[[Category:ODB]]

Latest revision as of 22:01, 30 October 2026

The midas documentation has moved. See Corruption in ODB: configuring for the new documentation about recovering a corrupted ODB.

Retrieved from "https://daq00.triumf.ca/MidasWiki/index.php?title=Recovery_from_Corrupted_ODB&oldid=3800"