June 10, 2011 at 2:32 am
Hi
i am getting below issue while selecting data from one table particularly.
i have ran the dbcc checkdb but no errors found
Msg 829, Level 21, State 1, Line 1
Database ID 6, Page (1:1324) is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
June 10, 2011 at 3:11 am
Have you verified that there are no page restores currently happening on the database?
What version of SQL 2k5 are you running? (SP3 or above?) Because if you're running a service pack less than that, I advise running DBCC CheckDB with ALL_ERRORMSGS to make sure you're getting the full list of errors.
If not, then I suggest you do as the error message states and restore the database, or at least the page if you have the db set up for page-level restores.
I'm sure Gail has more to add. She's the expert on database corruption. But first, please verify that the database in question isn't actually restoring pages or anything else.
June 10, 2011 at 3:53 am
That's exactly the message you'd get if someone's run a page restore and not completed the operation.
Ask your colleagues, see if any are playing around.
What version and edition are you running? What recovery model is the DB in?
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
June 22, 2011 at 6:42 am
sorry for late reply , i went for conference and came back today itself
so i ran
DBCC CheckDB with ALL_ERRORMSGS
and got below error
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 829, Level 21, State 1, Line 1
Database ID 32, Page (1:1270) is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
there is no shortage for tempdb space
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
June 22, 2011 at 6:49 am
i am using sql 2005 sp3 and database is in simple recovery model
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
June 22, 2011 at 6:50 am
Bhuvnesh (6/22/2011)
sorry for late reply , i went for conference and came back today itselfso i ran
DBCC CheckDB with ALL_ERRORMSGSand got below error
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 829, Level 21, State 1, Line 1
Database ID 32, Page (1:1270) is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
there is no shortage for tempdb space
Did you actually check the properties of tempdb to verify this? Remember that if you have a Max File Size for this DB, that counts for the "out of space" error.
Did you run CheckDB WITH ALL_ErrorMsgs against the system databases to see if there are issues with one of your system dbs?
What do your log files say around the time that you ran it against your user db?
June 22, 2011 at 6:56 am
i ran the above query against all system db nit no luck
and
below is the figures of tempdb in (MB)
USED (%)26.90 (7.68 %)
FREE (%)323.55 (92.32 %)
TOTAL(MB)350.45
DATA (used, %) 301.07 (5.07, 1.68%)
LOG (used, %) 49.38 (21.83, 44.21%)
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
June 22, 2011 at 11:30 am
Restore from a clean backup.
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 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply