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 ««123»»

Torn page issue Expand / Collapse
Author
Message
Posted Tuesday, January 15, 2013 2:35 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 1, 2014 12:43 AM
Points: 208, Visits: 563
Ohh.. Is there any way to know how much data lost? Or how to find what table affected by that ?
Post #1407112
Posted Tuesday, January 15, 2013 2:49 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 @ 12:11 PM
Points: 42,470, Visits: 35,541
jitendra.padhiyar (1/15/2013)
Ohh.. Is there any way to know how much data lost? Or how to find what table affected by that ?


How much, no, not after the fact. Which table, yes. The tables PTJOBOPHISTORY and PTJOBLOGS



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 #1407116
Posted Tuesday, January 15, 2013 3:05 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Today @ 5:22 AM
Points: 709, Visits: 1,412
Before you go further down this rabbit hole, do you have backups of this database? It may be better to restore from full/logs before proceeding.

I hope those backups you removed to clear up space on the drive were not from the database you are working on. If they were I hope they were moved and not deleted...


Joie Andrew
"Since 1982"
Post #1407121
Posted Tuesday, January 15, 2013 4:11 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 1, 2014 12:43 AM
Points: 208, Visits: 563
Thanks a lot GilaMonster and Joe !

I just checked with client end, and found they are ok with the performance of sql server but... they got one error while performing Delete operation with PTJOBLOGS.. (:

The were trying to perform below delete operation:

DELETE FROM PTPortalUser.PTJOBLOGS WHERE INSTANCEID < 614469

and got error message:

Msg 8908, Level 22, State 6, Line 1
Table error: Database ID 23, object ID 901578250, index ID 0. Chain linkage mismatch. (1:753306)->next = (1:753307), but (1:753307)->prev = (1:706408).

It seems its consistency error that Checkdb was not able to repair. Should I run checkdb again with All_ErrorMSGS ? to know whts going on ? OR any other way to cope with this error ? Indexid=0 seems cluster index issue..

Post #1407147
Posted Tuesday, January 15, 2013 4:23 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 1, 2014 12:43 AM
Points: 208, Visits: 563
Just googled error message and found this issue occurs because the SHRINK operation cannot remove a page from the SYSFILES1 system table on the primary data file of the database. And we can fix it by applying latest service pack of SQL Server 2000!!

Is it advisable ?? Please help me masters...!
Post #1407154
Posted Tuesday, January 15, 2013 4:27 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, June 12, 2014 2:04 PM
Points: 1,789, Visits: 1,014
index id 0 is heap , just to get a better idea for future use. did u get this error after a power failure ?
Did you try running a checkdsk on the disk drives?

@Gail , would it make sense now to add a clustered index or rebuild the clustered index ?


Jayanth Kurup
Post #1407158
Posted Tuesday, January 15, 2013 4:30 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, June 12, 2014 2:04 PM
Points: 1,789, Visits: 1,014
I wouldnt start adding service packs ( sql 2000 and still ahve serice packs you need to add??) to fix a issue your facing now. Applying service packs need to be thought out properly.

Are you able to access the table , can you create a copy of the table ?


Jayanth Kurup
Post #1407160
Posted Tuesday, January 15, 2013 5:45 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 @ 12:11 PM
Points: 42,470, Visits: 35,541
jitendra.padhiyar (1/15/2013)

The were trying to perform below delete operation:

DELETE FROM PTPortalUser.PTJOBLOGS WHERE INSTANCEID < 614469

and got error message:

Msg 8908, Level 22, State 6, Line 1
Table error: Database ID 23, object ID 901578250, index ID 0. Chain linkage mismatch. (1:753306)->next = (1:753307), but (1:753307)->prev = (1:706408).

It seems its consistency error that Checkdb was not able to repair. Should I run checkdb again with All_ErrorMSGS ? to know whts going on ? OR any other way to cope with this error ? Indexid=0 seems cluster index issue..


As I asked earlier...

Now, please run this so I can see if there are any remaining errors
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 #1407200
Posted Tuesday, January 15, 2013 5:47 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 @ 12:11 PM
Points: 42,470, Visits: 35,541
jitendra.padhiyar (1/15/2013)
Just googled error message and found this issue occurs because the SHRINK operation cannot remove a page from the SYSFILES1 system table on the primary data file of the database. And we can fix it by applying latest service pack of SQL Server 2000!!


Err, no it is not caused by shrink trying to remove a page from sysfiles1 and no you cannot fix it by applying a service pack.



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 #1407201
Posted Tuesday, January 15, 2013 5:47 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 @ 12:11 PM
Points: 42,470, Visits: 35,541
Jayanth_Kurup (1/15/2013)
@Gail , would it make sense now to add a clustered index or rebuild the clustered index ?


No, it will fail.

Are you able to access the table , can you create a copy of the table ?


No, it will fail.



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 #1407203
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse