FMS not starting due to SQL Server Fatal error 824 listed in FMS log (4302369)

A FMS would not start due to connection issue to with SQL Server repository database.

We confirmed that the database could be pinged and telnet worked to the DB port.

The following message appears in the FMS log

YYYY-MM-DD HH:MM:SS.SSS DEBUG [main] com.quest.nitro.service.topology.provider.wcfsdo.TopologyLoader - Caught unimportant exception; safe to ignore: Error loading types: com.quest.nitro.service.sl.interfaces.topology.OptimisticLockException: Warning: Fatal error 824 occurred at MMM DD YYYY HH:SSAM. Note the error and time, and contact your system administrator.. Resyncing with database before retry...
YYYY-MM-DD HH:MM:SS.SSS  ERROR [main] com.quest.nitro.service.topology.persistence.TopologyPersistence - An unexpected error occurred which may cause undesired behavior. You may want to contact Quest Software customer support if you see this error again: The connection is closed. com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed

This issue was caused by an I/O error in the SQL Server repository database. The following message was found in both the SQL Server error log and in the Event Viewer in association with a Fatal Error 824.

SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:2110898; actual 0:0).
It occurred during a read of page (1:2110898) in database ID 6 at offset 0x00000406b64000 in file 'G:\MSSQL\FoglightMSLP\Data01\foglight.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

It was determined that the transaction log for the repository database had been full for at least ten days prior to the I/O error occuring. The repeated action of the full transaction log appears to have cause the I/O error to occur.

Resolution

The customer restored a backup copy of their repository database from prior to the beginning of the Fatal Error 824 and then restarted the FMS.