Recovery from Corrupted ODB: Difference between revisions

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.

@@ 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.
-Note that sometimes it seems that you also need to remove the buffers associated with the system messages (called SYSMSG) as well as the buffers associated with the ODB.
-[[Category:ODB]]