Error 7987: A possible database consistency problem has been detected on database 'master'.

Last Post 03 Apr 2008 12:30 PM by ufohj. 7 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
ufohj
New Member
New Member

--
03 Apr 2008 06:12 AM
I got the error today while trying to create new database in SQL 2000 EM.
There is no error reported while running CHECKDB and DBCC CHECKCATALOG.

Error:
Error 7987: A possible database consistency problem has been detected on database 'master'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on database 'master'.

Result:
DBCC results for 'master'.
DBCC results for 'sysobjects'.
There are 1329 rows in 23 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 105 rows in 4 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 5060 rows in 87 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 2282 rows in 1085 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 838 rows in 4 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 13 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 5551 rows in 28 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 0 rows in 0 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysdatabases'.
There are 34 rows in 1 pages for object 'sysdatabases'.
DBCC results for 'sysxlogins'.
There are 3549 rows in 82 pages for object 'sysxlogins'.
DBCC results for 'sysdevices'.
There are 6 rows in 1 pages for object 'sysdevices'.
DBCC results for 'sysmessages'.
There are 3853 rows in 165 pages for object 'sysmessages'.
DBCC results for 'sysconfigures'.
There are 38 rows in 1 pages for object 'sysconfigures'.
DBCC results for 'sysservers'.
There are 2 rows in 1 pages for object 'sysservers'.
DBCC results for 'syslanguages'.
There are 33 rows in 3 pages for object 'syslanguages'.
DBCC results for 'syscharsets'.
There are 114 rows in 33 pages for object 'syscharsets'.
DBCC results for 'sysaltfiles'.
There are 80 rows in 15 pages for object 'sysaltfiles'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 'spt_monitor'.
There are 1 rows in 1 pages for object 'spt_monitor'.
DBCC results for 'spt_values'.
There are 730 rows in 7 pages for object 'spt_values'.
DBCC results for 'spt_fallback_db'.
There are 0 rows in 0 pages for object 'spt_fallback_db'.
DBCC results for 'spt_fallback_dev'.
There are 0 rows in 0 pages for object 'spt_fallback_dev'.
DBCC results for 'spt_fallback_usg'.
There are 0 rows in 0 pages for object 'spt_fallback_usg'.
DBCC results for 'dtproperties'.
There are 0 rows in 0 pages for object 'dtproperties'.
DBCC results for 'spt_provider_types'.
There are 25 rows in 1 pages for object 'spt_provider_types'.
DBCC results for 'spt_datatype_info_ext'.
There are 10 rows in 1 pages for object 'spt_datatype_info_ext'.
DBCC results for 'MSreplication_options'.
There are 2 rows in 1 pages for object 'MSreplication_options'.
DBCC results for 'spt_datatype_info'.
There are 36 rows in 1 pages for object 'spt_datatype_info'.
DBCC results for 'spt_server_info'.
There are 29 rows in 1 pages for object 'spt_server_info'.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'master'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
DBCC results for 'master'.
DBCC execution completed. If DBCC
ufohj
New Member
New Member

--
03 Apr 2008 09:31 AM
Thanks rm.

It is SQL2000 SP4.

I also tried DBCC-repair in single mode and still has the warning message.
It generated lots of warning messages in SQL error log, such as 'Stack Signature for the dump is 0x66E17712'.

All user databases are fine.

I'm thinking to restore it from tape backup of two days ago.

What's you opinion?

Thanks again.
ufohj
New Member
New Member

--
03 Apr 2008 11:07 AM
quote:

Originally posted by: russellb
i'll get the backups handy. then try a reboot after hours, though unlikely to fix (and possible to make worse). Did server have abnormal shutdown recently? Get same error if u execute CREATE DATABASE in query analyzer? what is status in sysdatabases ( select status from sysdatabases where dbid = 1 ) ?

-- Russell --
------------------------------------------
SQL Server Magazine Forum Pro



Thanks russellb.

1. Did server have abnormal shutdown recently? No.
2. Get same error if u execute CREATE DATABASE in query analyzer? No error in SQL Query Analyer.
3. What is status in sysdatabases ( select status from sysdatabases where dbid = 1 ) ?
DB: master
dbid:1
mode:0
status:24
status2:1090519040
category:0
version:539


Should I ignore it or restore master from tape backup(2 days ago)?

Someone had similar issue on VM.
My server is physical server and has multiple instances.

Thanks.

ufohj
New Member
New Member

--
03 Apr 2008 12:30 PM
quote:

Originally posted by: russellb
i don't think master is corrupt. tried from EM directly on server? or from other machine? maybe error is EM on client machine...by the way, don't ignore it, but seems u can try to exhaust other possibilities b4 restoring master.

that said, make sure you save a copy of the backup old enough to not be a backup of the corrupt db if it is indeed corrupt.

-- Russell --
------------------------------------------
SQL Server Magazine Forum Pro




Thanks Russell.
I got same error from other server or PC.
I'll backup it and try to restore it from tape tomorrow.

Thanks again.
ufohj
New Member
New Member

--
03 Apr 2008 12:43 PM
quote:

Originally posted by: russellb
definitely back it up, but you have an older, presumably clean, backup right?

-- Russell --
------------------------------------------
SQL Server Magazine Forum Pro



Thanks Russell.
I think so. The warning starts yesterday.
I got backup of two days ago.
ufohj
New Member
New Member

--
04 Apr 2008 12:31 PM
quote:

Originally posted by: rm
I'll restart sql first like Russell said, restore master only if restarting doesn't fix the issue.


Thanks rm.

SQLUSA
New Member
New Member

--
06 Apr 2008 11:27 PM
Knowledge bank article on the topic:

http://support.microsoft.com/kb/828337

Kalman Toth - Database, Data Warehouse & Business Intelligence Architect
BI Workshop NYC SSAS, SSIS, SSRS - April 21-24: http://www.sqlusa.com/
ufohj
New Member
New Member

--
07 Apr 2008 05:48 AM
quote:

Originally posted by: SQLUSA
Knowledge bank article on the topic:

http://support.microsoft.com/kb/828337

Kalman Toth - Database, Data Warehouse & Business Intelligence Architect
BI Workshop NYC SSAS, SSIS, SSRS - April 21-24: http://www.sqlusa.com/



Thanks SQLUSA.
I tried it before and it didn't work.

Restore solved the issue without rebooting.
You are not authorized to post a reply.

Acceptable Use Policy