customscoop
asked on
Warning: Fatal error 7987
We are seeing this problem in our application:
Warning: Fatal error 7987 occurred at Apr 10 2006 9:18AM猠楡 876;ڃ 2;牰 汩&# 26912;S 07;敤 ;楳& #28263; 9793;ā 01;愠 ;⁳&# 24910; 996;ଋ 1;. Note the error and time, and contact your system administrator.
And upon checking the SQL logs we are seeing everytime a specific simple query is run:
A possible database consistency problem has been detected on database 'allscoopdb'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on database 'allscoopdb'..
We had this problem once last week, and a reboot fixed it. The error is coming up everytime we run a specific sql query against the allscoopdb database. We have been running this query for over a year with no problems.
I've run the DBCC CHECKDB and it has returned no errors. Do you think there could be some kind of hardware problem? Or what else can I do to figure out what the problem is?
We are running MSSQL 2k on a big box. It's a quad box with 16 gigs of RAM with a SAN device. We are using managed hosting at RackSpace.
Help!
Warning: Fatal error 7987 occurred at Apr 10 2006 9:18AM猠楡
And upon checking the SQL logs we are seeing everytime a specific simple query is run:
A possible database consistency problem has been detected on database 'allscoopdb'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on database 'allscoopdb'..
We had this problem once last week, and a reboot fixed it. The error is coming up everytime we run a specific sql query against the allscoopdb database. We have been running this query for over a year with no problems.
I've run the DBCC CHECKDB and it has returned no errors. Do you think there could be some kind of hardware problem? Or what else can I do to figure out what the problem is?
We are running MSSQL 2k on a big box. It's a quad box with 16 gigs of RAM with a SAN device. We are using managed hosting at RackSpace.
Help!
This problem migth be because of bad sector in the disk so try running scan disk for windows at a drive containing log file and datafile for the allscoopdb database.
ASKER
Those look great. Will running either:
DBCC CHECKCATALOG ('allscoopdb')
GO
DBCC CHECKDB ('allscoopdb', REPAIR_FAST)
GO
Require single user mode, making the database unavailable in anyway?
DBCC CHECKCATALOG ('allscoopdb')
GO
DBCC CHECKDB ('allscoopdb', REPAIR_FAST)
GO
Require single user mode, making the database unavailable in anyway?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Here is the error I've gotten from the DBCC CHECKDB:
There are 69159732 rows in 280572 pages for object 'KeywordMatches'.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'KeywordMatches' (object ID 693577509).
When I run this:
select keywordid from keywordmatches WITH (INDEX (keywordmatches11))
forcing it to use that index, it blows up. So I suspect this index is having problems. It did take 6 hours to run so I'll give the REPAIR_FAST option a try overnight. I'll update this in the morning.
There are 69159732 rows in 280572 pages for object 'KeywordMatches'.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'KeywordMatches' (object ID 693577509).
When I run this:
select keywordid from keywordmatches WITH (INDEX (keywordmatches11))
forcing it to use that index, it blows up. So I suspect this index is having problems. It did take 6 hours to run so I'll give the REPAIR_FAST option a try overnight. I'll update this in the morning.
<< 2 consistency errors in table 'KeywordMatches' (object ID 693577509).>>
Try dbcc dbreindex(KeywordMatches') with All_indexes
Try dbcc dbreindex(KeywordMatches')
ASKER
Thanks! The DBCC CHECKDB ('allscoopdb', REPAIR_FAST) fixed all my problems!
run this statemnt
DBCC CHECKCATALOG ('allscoopdb')
GO
DBCC CHECKDB ('allscoopdb', REPAIR_FAST)
GO