WARNING: Do
not run the
DBCC CheckDB command with the
repair_allow_data_loss option. This command is destructive, and you have no control over what data is lost.
The data lost could be critical data that leaves the ePO database either:
- Inoperable
Or
- In a broken state with symptoms that are not immediately apparent.
Running the
repair_allow_data_loss command is
not supported.
Use the following non-destructive instructions to try a repair on the database:
- Back up the ePO database.
- Click Start, Run, type services.msc and click OK.
- Stop all ePO services and all remote Agent Handler services (if any).
- Run the attached script (DBCorruptionFix.txt), which runs the DBCC CheckDB command with the repair_rebuild command.
NOTE: This script can take several hours to complete. The repair_rebuild command is a non-destructive command that does not result in any data loss. It might repair the consistency or allocation errors. Even if the DBCC CheckDB command indicated that the repair_allow_data_loss option was needed.
- Review the output of the script when it completes.
- When the output indicates that the ePO database has consistency or allocation errors. The database must be restored from a good backup that does not have any corruption.
- If the issue was repaired, the output looks like the following:
CHECKDB found 0 allocation errors and 0 consistency errors in database.
