Testing confirmed that we are seeing this error on two different domains and two different database files, both of which were working fine this morning, and both went out at the same time, so it cannot be a corrupt DB file causing this problem as you suggest.
Moreover, both of these domains...