Skip to content

Latest commit

 

History

History
60 lines (43 loc) · 3.02 KB

mssqlserver-7995-database-engine-error.md

File metadata and controls

60 lines (43 loc) · 3.02 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic helpviewer_keywords
MSSQLSERVER_7995
MSSQLSERVER_7995
MashaMSFT
mathoma
04/04/2017
sql
supportability
reference
7995 (Database Engine error)

MSSQLSERVER_7995

[!INCLUDE SQL Server]

Details

Attribute Value
Product Name SQL Server
Event ID 7995
Event Source MSSQLSERVER
Component SQLEngine
Symbolic Name DBCC2_SYSTEM_CATALOGS_CORRUPT
Message Text Database 'DBNAME': consistency errors in system catalogs prevent further DBCC CHECKNAME processing.

Explanation

The DBCC CHECKDB process consists of the following three stages:

  1. Allocation checks. This is equivalent to running DBCC CHECKALLOC.

  2. System tables consistency checks. This is equivalent to running DBCC CHECKTABLE on a small list of necessary system base tables.

  3. Complete database consistency checks.

MSSQLEngine_7995 is raised in stage 2 to indicate that DBCC CHECKDB has found errors that the command cannot repair or that REPAIR has not been specified. DBCC CHECKDB cannot continue with stage 3 because either the system base tables in question store the metadata for all objects in the database or the system base tables are corrupted.

User Action

Look for Hardware Failure

Run hardware diagnostics and correct any problems. Also examine the [!INCLUDEmsCoName] Windows system and application logs and the [!INCLUDEssNoVersion] error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs.

If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor.

Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system.

Restore from Backup

If the problem is not hardware related and a known clean backup is available, restore the database from the backup.

Run DBCC CHECKDB

If no clean backup is available, run DBCC CHECKDB without a REPAIR clause to determine the extent of the corruption. DBCC CHECKDB will recommend a REPAIR clause to use. Then, run DBCC CHECKDB with the appropriate REPAIR clause to repair the corruption.

Caution

If you are not sure what effect DBCC CHECKDB with a REPAIR clause has on your data, contact your primary support provider before running this statement.

If running DBCC CHECKDB with one of the REPAIR clauses does not correct the problem, contact your primary support provider.

Results of Running REPAIR Options

Examine the list of errors to see what REPAIR will do for each.