Our SQL Server 2000 database had an error last week:
Table error: Database ID 12, object ID 1909581841, index
ID 0. Chain linkage mismatch. (1:154654)->next = (1:228873), but (1:228873)->prev = (1:228872).
We sort of fixed the problem by running dbcc checkdb with
repair_rebuild clause.
It was fine for a week, then yesterday sql server gave us
an error 605:
Server: Msg 605, Level 21, State 1, Line 1
Attempt to fetch logical page (1:123632) in
database 'afsa_ecaps' belongs to object 'employer', not to
object 'consolidation_activity_log'.
Connection Broken
We ran dbcc checkdb again to fix the problem.
My concern is, why does this keep happening? Any thing I
can do to prevent these totally? Any input will appreciate.
Thanks.
PeterI dealt with this problem for a while. Error 605 is still
on my favorites page in BOL because of the frequency.
Finally I noticed this paragraph:
Finally, be sure that your system does not have write
caching enabled on the disk controller. If you suspect
this to be the problem, contact your hardware vendor.
That fixed it for me. Havent had it since.
>--Original Message--
>Our SQL Server 2000 database had an error last week:
>Table error: Database ID 12, object ID 1909581841, index
>ID 0. Chain linkage mismatch. (1:154654)->next =>(1:228873), but (1:228873)->prev = (1:228872).
>We sort of fixed the problem by running dbcc checkdb with
>repair_rebuild clause.
>It was fine for a week, then yesterday sql server gave us
>an error 605:
>Server: Msg 605, Level 21, State 1, Line 1
>Attempt to fetch logical page (1:123632) in
>database 'afsa_ecaps' belongs to object 'employer', not
to
>object 'consolidation_activity_log'.
>Connection Broken
>We ran dbcc checkdb again to fix the problem.
>My concern is, why does this keep happening? Any thing I
>can do to prevent these totally? Any input will
appreciate.
>Thanks.
>Peter
>.
>|||... Also, make sure you don't compress the database files.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:001401c3c0d3$5dee8110$a401280a@.phx.gbl...
> I dealt with this problem for a while. Error 605 is still
> on my favorites page in BOL because of the frequency.
> Finally I noticed this paragraph:
> Finally, be sure that your system does not have write
> caching enabled on the disk controller. If you suspect
> this to be the problem, contact your hardware vendor.
>
> That fixed it for me. Havent had it since.
>
> >--Original Message--
> >Our SQL Server 2000 database had an error last week:
> >
> >Table error: Database ID 12, object ID 1909581841, index
> >ID 0. Chain linkage mismatch. (1:154654)->next => >(1:228873), but (1:228873)->prev = (1:228872).
> >We sort of fixed the problem by running dbcc checkdb with
> >repair_rebuild clause.
> >
> >It was fine for a week, then yesterday sql server gave us
> >an error 605:
> >Server: Msg 605, Level 21, State 1, Line 1
> >Attempt to fetch logical page (1:123632) in
> >database 'afsa_ecaps' belongs to object 'employer', not
> to
> >object 'consolidation_activity_log'.
> >Connection Broken
> >
> >We ran dbcc checkdb again to fix the problem.
> >
> >My concern is, why does this keep happening? Any thing I
> >can do to prevent these totally? Any input will
> appreciate.
> >
> >Thanks.
> >Peter
> >
> >.
> >
