Error: 605, Severity: 21, State: 1

Question

Post reply

Error: 605, Severity: 21, State: 1

franco

SSCommitted

Points: 1642
More actions
March 3, 2005 at 4:10 am

#87665

SQL Server 2K sp3a
WS2K3 on 2 nodes cluster.
This Morning I notify this error on Event Log:
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:6368) in database 'AJL_Credi_PROD01' belongs to object '3670073', not to object 'FATTURA'.
Next I run - dbcc checktable ('fattura') - and this is the result:
Server: Msg 8909, Level 16, State 1, Line 3
Table error: Object ID 3670073, index ID 0, page ID (1:6368). The PageId in the page header = (48:4390960).
Server: Msg 8928, Level 16, State 1, Line 3
Object ID 1538104520, index ID 0: Page (1:6368) could not be processed. See other errors for details.
CHECKTABLE found 0 allocation errors and 1 consistency errors in table '(Object ID 3670073)' (object ID 3670073).
DBCC results for 'FATTURA'.
There are 68027 rows in 2458 pages for object 'FATTURA'.
CHECKTABLE found 0 allocation errors and 1 consistency errors in table 'FATTURA' (object ID 1538104520).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (AJL_Credi_PROD01.dbo.FATTURA ).
Any idea why this happen and how to solve it?
Do I really have to try, as suggested, to use 'repair_allow_data_loss'?
Please advise.
Franco

Franco

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

sa24 SSCrazy Eights Points: 8027 More actions · Answer 1

Do I really have to try, as suggested, to use 'repair_allow_data_loss'?

I guess so but please make sure you have a good backup of the database before you run that.

Frank Kalis SSC Guru Points: 111183 More actions · Answer 2

Even if you can repair it for now, check your hardware closely to make sure it won't happen again.

If it doesn't help, I would call MS PSS.

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

franco SSCommitted Points: 1642 More actions · Answer 3

Thanks for your suggestion.

I run dbcc checktable repair_fast and dbcc checktable repair_rebuild without success.

So I decide to run dbcc checktable repair_allow_data_loss and SQL Server tells me that he found errors and he was able to repair these errors.

From HW point of view everything in our SAN seems to be in a state of OPTIMAL, so I have no issue on that side.

Thanks again for yout time.

Franco

noeld SSC Guru Points: 96590 More actions · Answer 4

Because my life has tought me not to trust one opinion (HW manufacturer) I would schedule a CHKDSK on the SAN Disk you had problems when the next maintenance window shows up!

HTH

* Noel