Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

sysobjects corruption Expand / Collapse
Author
Message
Posted Tuesday, June 25, 2013 9:44 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, February 12, 2014 7:00 AM
Points: 6, Visits: 104
i get the following error when selecting:

sysobjects: I/O error (torn page) detected during read at offset 0*0000000000000 in file ‘D:\XXX.mdf’
tbl_a: Could not continue scan with NOLOCK due to data movement.

any idea? someone?
Post #1467432
Posted Wednesday, June 26, 2013 2:15 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:19 AM
Points: 40,208, Visits: 36,617
Please run the following and post the full and unedited output

DBCC CheckDB(<database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS




Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1467504
Posted Wednesday, June 26, 2013 2:49 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, February 12, 2014 7:00 AM
Points: 6, Visits: 104
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1610) with latch type SH. sysobjects failed.
Post #1467516
Posted Wednesday, June 26, 2013 2:58 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:19 AM
Points: 40,208, Visits: 36,617
Restore from a clean backup, your database is irreparably corrupt.

Once done, check your IO subsystem for errors.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1467518
Posted Wednesday, June 26, 2013 4:47 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, February 12, 2014 7:00 AM
Points: 6, Visits: 104
thank you very much!!!!
Post #1467556
Posted Wednesday, June 26, 2013 5:03 AM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Tuesday, October 21, 2014 1:36 AM
Points: 608, Visits: 1,050
If it is a very big database then you can restore only page (1:1610) to save restoration time

Pramod
SQL Server DBA | MCSA SQL Server 2012

in.linkedin.com/in/pramodsingla/
http://pramodsingla.wordpress.com/
Post #1467562
Posted Wednesday, June 26, 2013 8:28 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:19 AM
Points: 40,208, Visits: 36,617
psingla (6/26/2013)
If it is a very big database then you can restore only page (1:1610) to save restoration time


No, he can't.

Firstly because it's a SQL 2000 database and page restore didn't exist in SQL 2000, second because you can't do a page restore of the critical system tables, which is where the corruption is in this case.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1467703
Posted Wednesday, June 26, 2013 8:36 AM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Tuesday, October 21, 2014 1:36 AM
Points: 608, Visits: 1,050
GilaMonster (6/26/2013)

No, he can't.

Firstly because it's a SQL 2000 database and page restore didn't exist in SQL 2000, second because you can't do a page restore of the critical system tables, which is where the corruption is in this case.


Thanks Gail,I was not aware that page restore doesn't work for critical system tables
but how you came to know this is SQL 2000?I haven't worked on 2000...


Pramod
SQL Server DBA | MCSA SQL Server 2012

in.linkedin.com/in/pramodsingla/
http://pramodsingla.wordpress.com/
Post #1467708
Posted Wednesday, June 26, 2013 12:45 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:19 AM
Points: 40,208, Visits: 36,617
psingla (6/26/2013)
but how you came to know this is SQL 2000?I haven't worked on 2000...


Because it's posted in the SQL 2000 forum, because the error messages are in the SQL 2000 form (they were all rewritten for SQL 2005) and because the corruption message references sysobjects, a table that does not exist in SQL 2005+

It could be SQL 7 too, but it's definitely not SQL 2005 or higher.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1467816
Posted Wednesday, June 26, 2013 7:58 PM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Tuesday, October 21, 2014 1:36 AM
Points: 608, Visits: 1,050
GilaMonster (6/26/2013)

corruption message references sysobjects, a table that does not exist in SQL 2005+
It could be SQL 7 too, but it's definitely not SQL 2005 or higher.


Thanks again,I missed that point it's posted in the SQL 2000 forum.
BTW sysobjects view exists in 2005+ versions also.So if somebody is trying to select data from sysobjects in later 2005+ then he can get the same error that is listed here.


Pramod
SQL Server DBA | MCSA SQL Server 2012

in.linkedin.com/in/pramodsingla/
http://pramodsingla.wordpress.com/
Post #1467926
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse