Update DAE-Trouble-Shooting.md

Author: FreddieAkeroyd

doc/specific_iocs/dae/DAE-Trouble-Shooting.md

@@ -468,6 +468,9 @@ For info, the `eventsYYYYY.tmp` file is the NeXus HDF5 file being written as the
 
 If the run number comes back incorrectly (like as `000001`) then it means `c:\data\recovery.run` has been corrupted. There are backup weekday copies in c:\data e.g. `recovery.run_Thu` so you can pick one to copy to `recovery.run` however note that this may include an old run number so after restarting you may need to reset the run number (see on this page) 
 
+If after the above you get SQLite/selogger database errors in the isisicp.log then stop isisdae/icicisp and delete `c:\data\selog.*` (.sq3 .sq3-shm and .sh3-wal files)
+
+
 ## SQLite database is very large 
 
 The `selog.sq3` file in `C:/Data` is used by ISISICP to store log data prior to a run end, it is then purged. It will normally only get very big if a run has not been ended for a long time, which either happens over a shutdown if logging has been left running, or on systems that do not often end runs such as RIKENFE, MUONFE, DETMON, HIFI-CRYOMAG etc. The solution is to begin and end a run, though on HIFI-CRYOMAG the scientist will normally do this themselves once a cycle to keep log data together in the same data file, so consult with them if it needs doing. Ending a run may take a while and will happen in the background, so don't stop ibex as soon as you get back to SETUP as it will likely not have finished saving. If you need to stop ibex, wait until the data file for the run you have saved appears in the archive.