October 22, 2007 at 2:37 pm
I think it may have something to do with the fact that I forgot to exclude the data and log folders and the mdf and ndf and ldf extensions from symantec, given the errors below, can anyone tell me if this is a likely cause?
the error I get in the event log is:
Error: 7105, Severity: 22, State: 6
Page (1:2256), slot 3 for text, ntext, or image node does not exist.
and when I tried to do a dbcc checkalloc it came back with the following first line error
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:371024) in database ID 5 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
DBCC results for 'my_database'.
CHECKALLOC found 1 allocation errors and 0 consistency errors not associated with any single object.
this has only happened the one time. I have detached the non-functioning database and restored a backup without issue. I have also added the exclusions to the symantec client and haven't seen this anymore, but this has only happened once after 2 weeks of use. No queries or stored procedures were being run against the database when this happened, Luckily this machine is not yet in production, so we can work with it until we are confident it will be sucessful.
I did a full diagnostic on the hardware of the machine and everything, including the DAS and controller are seem fine.
any suggestions you may have would be great.
October 22, 2007 at 2:52 pm
It could be your AV software - I've seen it do weird things before.
Can you post the output from "dbcc checkdb (yourdb) with all_errormsgs, no_infomsgs"?
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
October 22, 2007 at 2:58 pm
I'll do it for you tomorrow. I have to reattach the db and I am about to head out for the night. thanks for the reply.
October 23, 2007 at 1:41 pm
So when I tried to run dbcc checkdb
it gave me this
Server: Msg 7995, Level 16, State 3, Line 1
Database 'mydatabase' consistency errors in sysobjects, sysindexes, syscolumns, or systypes prevent further CHECK processing.
I can run the REPAIR_ALLOW_DATA_LOSS
but I would rather not do that.
October 23, 2007 at 1:49 pm
ok - so you're running SQL Server 2000 (from the error message you posted).
Is that the only output from CHECKDB? There should be some more specific errors too?
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
October 23, 2007 at 1:53 pm
that was it.
October 23, 2007 at 2:00 pm
Can you try doing a select * from each of the named tables? My guess is that the text error you previously had is from a row in sysindexes - specifically the statistics blog for an index - in which case the select * will fail with a similar error.
If so, you should be able to work around the problem without running repair (details once we determine whether that's the problem)
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
November 16, 2007 at 4:05 pm
Just wanted to pass this on. We ran into this same error and in the end it was caused by symantec live update crashing the services exe and causing window to reboot. This seems to only be an issue on sql boxes. So I would recommend removing live update from add and remove programs on sql server boxes.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply