Tuesday, March 27, 2012

Error 8909 in job...is it?

Microsoft SQL Server 2000 - 8.00.923 (Intel X86)
Enterprise Edition on Windows NT 5.2 (Build 3790: )
I received the following error the last two nights in a row while running
the gui created maintanence job. I just ran DBCC CHECKDB WITH NO_INFOMSGS
and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and returned
no errors. I am alarmed but why the errors one way and not the other. Is
there some switches that I enable prior to running in QA to get more info?
[5] Database XXDB: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: [Microsoft][ODBC SQL
Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0, page
ID (1:948331). The PageId in the page header = (55:939524096).
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
10944512, index ID 0, page ID (1:948331). The PageId in the page header =
(55:939524096).
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2005582183, index ID 7, page (1:948329). Test (sorted [i].offset >=
PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >= max)
failed. Slot 0, offset 0x1ab overlaps with the prior row.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948330) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948331) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948332) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948333) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948334) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948335) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948336) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
ID 7: Page (1:948337) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >=
PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= max)
failed. Slot 0, offset 0xe9 overlaps with the prior row.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 2 consistency errors in table 'TblPhoneNote' (object ID
2031398356).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 20 consistency errors in database 'XXDB'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the
minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
** Execution Time: 0 hrs, 33 mins, 26 secs **
TIA
CD
Time to open a call to Microsoft PSS.. It costs $249 I think... If the data
is important, don't risk it..
Also, do not overwrite any backups until you get this resolved..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CD" <mcdye1@.hotmail.nospam.com> wrote in message
news:OfSshe1uEHA.3872@.TK2MSFTNGP11.phx.gbl...
> Microsoft SQL Server 2000 - 8.00.923 (Intel X86)
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
> I received the following error the last two nights in a row while running
> the gui created maintanence job. I just ran DBCC CHECKDB WITH NO_INFOMSGS
> and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and
returned
> no errors. I am alarmed but why the errors one way and not the other. Is
> there some switches that I enable prior to running in QA to get more info?
> [5] Database XXDB: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0,
page
> ID (1:948331). The PageId in the page header = (55:939524096).
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 10944512, index ID 0, page ID (1:948331). The PageId in the page header =
> (55:939524096).
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2005582183, index ID 7, page (1:948329). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >= max)
> failed. Slot 0, offset 0x1ab overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= max)
> failed. Slot 0, offset 0xe9 overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 2 consistency errors in table 'TblPhoneNote' (object ID
> 2031398356).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 20 consistency errors in database 'XXDB'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is
the
> minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
> ** Execution Time: 0 hrs, 33 mins, 26 secs **
> TIA
> CD
>
|||It is possible for hardware problems to show up as 'transient' corruption issues in DBCC. Issues like caching controllers can cause the buffer pool to read stale data and feed that stale data to DBCC, which detects a corruption. If the page is flushed back out of the cache and then read back in later on, there could be no problem with the read (and thus no corruption as far as DBCC is concerned).
As Wayne correctly suggests, CSS is probabaly your best alternative at this point, but they are probably going to request that you do some hardware diagnostics too. You might be preemptive and have them ready.
Thanks,
Ryan Stonecipher
SQL Server Storage Engine, DBCC
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:ehsYVw1uEHA.4028@.TK2MSFTNGP15.phx.gbl...
Time to open a call to Microsoft PSS.. It costs $249 I think... If the data
is important, don't risk it..
Also, do not overwrite any backups until you get this resolved..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CD" <mcdye1@.hotmail.nospam.com> wrote in message
news:OfSshe1uEHA.3872@.TK2MSFTNGP11.phx.gbl...
> Microsoft SQL Server 2000 - 8.00.923 (Intel X86)
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
> I received the following error the last two nights in a row while running
> the gui created maintanence job. I just ran DBCC CHECKDB WITH NO_INFOMSGS
> and DBCC CHECKTABLE ('TblPhoneNote') on the tables listed in QA and
returned
> no errors. I am alarmed but why the errors one way and not the other. Is
> there some switches that I enable prior to running in QA to get more info?
> [5] Database XXDB: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8909: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0,
page
> ID (1:948331). The PageId in the page header = (55:939524096).
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 10944512, index ID 0, page ID (1:948331). The PageId in the page header =
> (55:939524096).
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2005582183, index ID 7, page (1:948329). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 427, offset 0x2 is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2005582183, index ID 7, page (1:948329). Test (sorted[i].offset >= max)
> failed. Slot 0, offset 0x1ab overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >=
> PAGEHEADSIZE) failed. Slot 233, offset 0x2e is invalid.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= max)
> failed. Slot 0, offset 0xe9 overlaps with the prior row.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 2 consistency errors in table 'TblPhoneNote' (object ID
> 2031398356).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
> errors and 20 consistency errors in database 'XXDB'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is
the
> minimum repair level for the errors found by DBCC CHECKDB (XXDB ).
> ** Execution Time: 0 hrs, 33 mins, 26 secs **
> TIA
> CD
>

No comments:

Post a Comment