DB error...please help!

Hi
I have a DB running in SQLServer 2000 that has worked fine for ages.
However, a recent data load failed. We check the DB using 'dbcc checkdb'
and it reported errors. We fixed the DB using 'dbcc checkdb
(REPAIR_ALLOW_DATA_LOSS )' and this appeared to fix the problem. However,
the DB has since corrupted twice more within a week. CheckDB run on the
master DB shows no problems.
Error messages:
These have been fairly varied. The error we recieve when doing an update
is:
--
Error -2147467259 - I/O error (bad page ID) detected during read at offset
0x0000001f220000 in file 'd:\mssql\data\[myDBName].mdf'
(This is followed by a whole series of connection failure errors for each
connection attempted during the data upload.)
--
Other error messages include:
--
Server: Msg 3624, Level 20, State 1, Line 1
Location: S:\sql\ntdbms\storeng\drs\include\record.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 75
Process ID: 824
Connection Broken
--
When we correct the errors using CheckDB, we get the following example
messages (should you wish to read):
Table error: Object ID -1291825152, index ID 12336, page ID (1:74256). The
PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 33792, page ID (1:74258). The PageId in
the page header = (0:0).
The error has been repaired.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object
ID -1291825152)' (object ID -1291825152).
CHECKDB fixed 0 allocation errors and 1 consistency errors in table '(Object
ID -1291825152)' (object ID -1291825152).
DBCC results for '[myDataBaseName]'.
The error has been repaired.
CHECKDB found 0 allocation errors and 1 consistency errors not associated
with any single object.
CHECKDB fixed 0 allocation errors and 1 consistency errors not associated
with any single object.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 606625204, index ID 0: Page (1:74256) could not be processed. See
other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 606625204, index ID 0: Page (1:74257) could not be processed. See
other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 606625204, index ID 0: Page (1:74258) could not be processed. See
other errors for details.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 606625204, index ID 1. Page (1:74256) was not seen in
the scan although its parent (1:74322) and previous (1:74271) refer to it.
Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 606625204, index ID 1. Index node page (1:74322),
slot 32 refers to child page (1:74257) and previous child (1:74256), but
they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 606625204, index ID 1. Index node page (1:74322)
DBCC results for 'accountProducts'.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 606625204, index ID 1. Page (1:74259) is missing a
reference from previous page (1:74258). Possible chain linkage problem.
The error has been repaired.
The error has been repaired.
Repair: Page (1:74256) has been deallocated from object ID 606625204, index
ID 0.
Repair: Page (1:74257) has been deallocated from object ID 606625204, index
ID 0.
Repair: Page (1:74258) has been deallocated from object ID 606625204, index
ID 0.
There are 3930517 rows in 64635 pages for object 'accountProducts'.
CHECKDB found 0 allocation errors and 7 consistency errors in table
'accountProducts' (object ID 606625204).
CHECKDB fixed 0 allocation errors and 7 consistency errors in table
'accountProducts' (object ID 606625204).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1312043077, index ID 12341, page ID (1:74257). The
PageId in the page header = (0:1205993552).
There are 7602 rows in 54 pages for object 'crossSellingProducts'.
The error has been repaired.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object
ID 1312043077)' (object ID 1312043077).
CHECKDB fixed 0 allocation errors and 1 consistency errors in table '(Object
ID 1312043077)' (object ID 1312043077).
CHECKDB found 0 allocation errors and 10 consistency errors in database
'[myDBName]'.
CHECKDB fixed 0 allocation errors and 10 consistency errors in database
'[myDBName]'.
--
Any ideas what may be the problem? More importantly, what to do about it?
Many thanks in advance!
GriffHello,
After looking at your problem I think its somehow one or
more of your updates is currupting one of your clusters,
in turn its effecting your pages.
Personally I would examine the data closely and try the
50/50 approach, i.e. load in 50% of the data see if there
is an error of not 50% of the remaining data and so on.
I wish I could give you some more help, but please feel
free to email me on (in reverse order)
ku.oc.elcannip@.nalon.retep.
Peter
>--Original Message--
>Hi
>I have a DB running in SQLServer 2000 that has worked
fine for ages.
>However, a recent data load failed. We check the DB
using 'dbcc checkdb'
>and it reported errors. We fixed the DB using 'dbcc
checkdb
>(REPAIR_ALLOW_DATA_LOSS )' and this appeared to fix the
problem. However,
>the DB has since corrupted twice more within a week.
CheckDB run on the
>master DB shows no problems.
>Error messages:
>These have been fairly varied. The error we recieve when
doing an update
>is:
>--
>Error -2147467259 - I/O error (bad page ID) detected
during read at offset
>0x0000001f220000 in file 'd:\mssql\data\[myDBName].mdf'
>(This is followed by a whole series of connection failure
errors for each
>connection attempted during the data upload.)
>--
>Other error messages include:
>--
>Server: Msg 3624, Level 20, State 1, Line 1
>Location:
S:\sql\ntdbms\storeng\drs\include\record.inl:1447
>Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
>SPID: 75
>Process ID: 824
>Connection Broken
>--
>When we correct the errors using CheckDB, we get the
following example
>messages (should you wish to read):
>Table error: Object ID -1291825152, index ID 12336, page
ID (1:74256). The
>PageId in the page header = (0:0).
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 0, index ID 33792, page ID
(1:74258). The PageId in
>the page header = (0:0).
> The error has been repaired.
>CHECKDB found 0 allocation errors and 1 consistency
errors in table '(Object
>ID -1291825152)' (object ID -1291825152).
>CHECKDB fixed 0 allocation errors and 1 consistency
errors in table '(Object
>ID -1291825152)' (object ID -1291825152).
>DBCC results for '[myDataBaseName]'.
> The error has been repaired.
>CHECKDB found 0 allocation errors and 1 consistency
errors not associated
>with any single object.
>CHECKDB fixed 0 allocation errors and 1 consistency
errors not associated
>with any single object.
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 606625204, index ID 0: Page (1:74256) could not
be processed. See
>other errors for details.
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 606625204, index ID 0: Page (1:74257) could not
be processed. See
>other errors for details.
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 606625204, index ID 0: Page (1:74258) could not
be processed. See
>other errors for details.
>Server: Msg 8976, Level 16, State 1, Line 1
>Table error: Object ID 606625204, index ID 1. Page
(1:74256) was not seen in
>the scan although its parent (1:74322) and previous
(1:74271) refer to it.
>Check any previous errors.
>Server: Msg 8980, Level 16, State 1, Line 1
>Table error: Object ID 606625204, index ID 1. Index node
page (1:74322),
>slot 32 refers to child page (1:74257) and previous child
(1:74256), but
>they were not encountered.
>Server: Msg 8980, Level 16, State 1, Line 1
>Table error: Object ID 606625204, index ID 1. Index node
page (1:74322)
>
>DBCC results for 'accountProducts'.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
>Server: Msg 8978, Level 16, State 1, Line 1
>Table error: Object ID 606625204, index ID 1. Page
(1:74259) is missing a
>reference from previous page (1:74258). Possible chain
linkage problem.
> The error has been repaired.
> The error has been repaired.
>Repair: Page (1:74256) has been deallocated from object
ID 606625204, index
>ID 0.
>Repair: Page (1:74257) has been deallocated from object
ID 606625204, index
>ID 0.
>Repair: Page (1:74258) has been deallocated from object
ID 606625204, index
>ID 0.
>
>There are 3930517 rows in 64635 pages for
object 'accountProducts'.
>CHECKDB found 0 allocation errors and 7 consistency
errors in table
>'accountProducts' (object ID 606625204).
>CHECKDB fixed 0 allocation errors and 7 consistency
errors in table
>'accountProducts' (object ID 606625204).
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 1312043077, index ID 12341, page
ID (1:74257). The
>PageId in the page header = (0:1205993552).
>There are 7602 rows in 54 pages for
object 'crossSellingProducts'.
> The error has been repaired.
>CHECKDB found 0 allocation errors and 1 consistency
errors in table '(Object
>ID 1312043077)' (object ID 1312043077).
>CHECKDB fixed 0 allocation errors and 1 consistency
errors in table '(Object
>ID 1312043077)' (object ID 1312043077).
>CHECKDB found 0 allocation errors and 10 consistency
errors in database
>'[myDBName]'.
>CHECKDB fixed 0 allocation errors and 10 consistency
errors in database
>'[myDBName]'.
>--
>Any ideas what may be the problem? More importantly,
what to do about it?
>Many thanks in advance!
>Griff
>
>.
>