April 8, 2009 at 7:58 am
Good morning,
Can someone explain this error message to me and what needs to be done?
I tried a google search, but found this error associated with tempdb. The advice was to stop and start SQL Server.
However, this is not my tempdb. This is one of my production databases.
Thank you.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:5242
Date:4/8/2009
Time:8:05:47 AM
User:N/A
Computer:MYSERVER
Description:
An inconsistency was detected during an internal operation in database 'MYDATABASE'(ID:10) on page (1:779255). Please contact technical support. Reference number 7.
Tony
Things will work out. Get back up, change some parameters and recode.
April 8, 2009 at 8:05 am
Please run checkDB on that database and post any errors here.
DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS
You may also want to take a look at this article. http://www.sqlservercentral.com/articles/65804/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 8, 2009 at 8:27 am
Thank you.
I read the article and will still do some more studying. I am running DBCC CHECKDB now.
Tony
Things will work out. Get back up, change some parameters and recode.
April 8, 2009 at 9:06 am
Ok now I am really confused.
DBCC CHECKDB return a bunch rows results of course. But at the end, it returned this message.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'Mydatabase'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Then what was with the error? What do I do now. The event log is showing me an error, but this command says there isn't one?!
Thank you.
Tony
Things will work out. Get back up, change some parameters and recode.
April 8, 2009 at 10:16 am
Ok, so no database corruption. That's good. Just to be sure, you ran that on the database that has an ID of 10?
This may be a transient condition that doesn't reoccur. I hope it is. If it does reoccur, you may have to contact Microsoft's Customer Support
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply