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
>
Showing posts with label build. Show all posts
Showing posts with label build. Show all posts
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
CDTime 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
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0043_01C4BB41.E7258280
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
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 =3D (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 =3D
> (55:939524096).
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object =ID
> 2005582183, index ID 7, page (1:948329). Test (sorted [i].offset =>=3D
> 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 >=3D =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 =>=3D
> 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 =>=3D 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
>
>
--=_NextPart_000_0043_01C4BB41.E7258280
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
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" wrote in message news:ehsYVw1uEHA.4028=@.TK2MSFTNGP15.phx.gbl...Time to open a call to Microsoft PSS.. It costs $249 I think... If the =datais important, don't risk it..Also, do not overwrite any backups =until you get this resolved..-- Wayne Snyder, MCDBA, SQL Server MVPMariner, Charlotte, NChttp://www.mariner-usa.com">www.mariner-usa.com(Please =respond only to the newsgroups.)I support the Professional Association =of SQL Server (PASS) and it'scommunity of SQL Server professionals.http://www.sqlpass.org">www.sqlpass.org"CD" 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 andreturned> 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][ODBCSQL> Server Driver][SQL = Server]Table error: Object ID 10944512, index ID 0,page> ID = (1:948331). The PageId in the page header =3D (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 =3D> (55:939524096).>> [Microsoft][ODBC SQL Server =Driver][SQL Server]Table error: Object ID> 2005582183, index ID 7, page =(1:948329). Test (sorted [i].offset >=3D> 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 >=3D 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 fordetails.> [Microsoft][ODBC =SQL Server Driver][SQL Server]Object ID 2005582183, index> ID 7: =Page (1:948331) could not be processed. See other errors =fordetails.> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index> ID 7: Page (1:948332) could not be processed. See other =errors fordetails.> [Microsoft][ODBC SQL Server Driver][SQL =Server]Object ID 2005582183, index> ID 7: Page (1:948333) could not be =processed. See other errors fordetails.> [Microsoft][ODBC SQL Server =Driver][SQL Server]Object ID 2005582183, index> ID 7: Page (1:948334) could =not be processed. See other errors fordetails.> [Microsoft][ODBC =SQL Server Driver][SQL Server]Object ID 2005582183, index> ID 7: =Page (1:948335) could not be processed. See other errors =fordetails.> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582183, index> ID 7: Page (1:948336) could not be processed. See other =errors fordetails.> [Microsoft][ODBC SQL Server Driver][SQL =Server]Object ID 2005582183, index> ID 7: Page (1:948337) could not be =processed. See other errors fordetails.> [Microsoft][ODBC SQL Server =Driver][SQL Server]Table error: Object ID> 2031398356, index ID 14, page (1:948330). Test (sorted [i].offset >=3D> 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 >=3D 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 isthe> minimum =repair level for the errors found by DBCC CHECKDB (XXDB ).> ** Execution Time: 0 hrs, 33 mins, =26 secs **>> TIA> CD>>
--=_NextPart_000_0043_01C4BB41.E7258280--
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
CDTime 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
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0043_01C4BB41.E7258280
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
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 =3D (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 =3D
> (55:939524096).
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object =ID
> 2005582183, index ID 7, page (1:948329). Test (sorted [i].offset =>=3D
> 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 >=3D =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 =>=3D
> 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 =>=3D 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
>
>
--=_NextPart_000_0043_01C4BB41.E7258280
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
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"
--=_NextPart_000_0043_01C4BB41.E7258280--
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]&#
91;ODBC SQL
Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0, p
age
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: Obje
ct 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: Obje
ct 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: Obje
ct 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 2005582
183, index
ID 7: Page (1:948330) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948331) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948332) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948333) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948334) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948335) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948336) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948337) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Obje
ct 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: Obje
ct 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 a
llocation
errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 a
llocation
errors and 2 consistency errors in table 'TblPhoneNote' (object ID
2031398356).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 a
llocation
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
CDTime 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][ODB
C
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: Ob
ject 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: Ob
ject 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: Ob
ject 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 20055
82183, index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject 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: Ob
ject ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= ma
x)
> 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 is
sues 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 a
s 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 diag
nostics 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:e
hsYVw1uEHA.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][ODB
C
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: Ob
ject 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: Ob
ject 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: Ob
ject 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 20055
82183, index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject 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: Ob
ject ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= ma
x)
> 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
>sql
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]&#
91;ODBC SQL
Server Driver][SQL Server]Table error: Object ID 10944512, index ID 0, p
age
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: Obje
ct 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: Obje
ct 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: Obje
ct 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 2005582
183, index
ID 7: Page (1:948330) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948331) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948332) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948333) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948334) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948335) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948336) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2005582
183, index
ID 7: Page (1:948337) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Obje
ct 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: Obje
ct 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 a
llocation
errors and 11 consistency errors in table 'TblLab' (object ID 2005582183).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 a
llocation
errors and 2 consistency errors in table 'TblPhoneNote' (object ID
2031398356).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 a
llocation
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
CDTime 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][ODB
C
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: Ob
ject 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: Ob
ject 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: Ob
ject 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 20055
82183, index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject 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: Ob
ject ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= ma
x)
> 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 is
sues 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 a
s 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 diag
nostics 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:e
hsYVw1uEHA.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][ODB
C
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: Ob
ject 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: Ob
ject 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: Ob
ject 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 20055
82183, index
> ID 7: Page (1:948330) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948331) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948332) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948333) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948334) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948335) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948336) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 20055
82183, index
> ID 7: Page (1:948337) could not be processed. See other errors for
details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Ob
ject 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: Ob
ject ID
> 2031398356, index ID 14, page (1:948330). Test (sorted[i].offset >= ma
x)
> 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
>sql
Monday, March 26, 2012
Error 823 that I cant fix
Hi,
I am running SQL 2000 server for datawarehousing and I am getting the following error in the application log when I build large tables:
Error: 823, Severity: 24, State: 3
I/O error 33(The process cannot access the file because another process has locked a portion of the file.) detected during write at offset 0x00000829618000 in file '<file name.mdf>'
I have run through MS Support and really haven't found helpful info on this. I don't know what process is locking the mdf file, but I don't beleive there are any server or even client side programs running against this datafile.
Any thoughts?
joeNot come across that error before, but I would try looking under the Managment section of your server in Enterprise Manager then Locks/Objects and see if you can spot an offending process. If there is one it may be worth trying to kill it.
I am running SQL 2000 server for datawarehousing and I am getting the following error in the application log when I build large tables:
Error: 823, Severity: 24, State: 3
I/O error 33(The process cannot access the file because another process has locked a portion of the file.) detected during write at offset 0x00000829618000 in file '<file name.mdf>'
I have run through MS Support and really haven't found helpful info on this. I don't know what process is locking the mdf file, but I don't beleive there are any server or even client side programs running against this datafile.
Any thoughts?
joeNot come across that error before, but I would try looking under the Managment section of your server in Enterprise Manager then Locks/Objects and see if you can spot an offending process. If there is one it may be worth trying to kill it.
Sunday, March 11, 2012
Error 5172
Hello,
I hava an sql server 2000 sp3a on a win2k sp4 machine running all ok. I tried to build a raid 1 using the hdd where sqlserver was and a new one, but i failed to build it and consecuently i lost all data bases.
Using some programs, i recover the mdf, ldf and ndf files from my old sql server 2000.
I reinstalled all the system exactly the same, win2k sp4 and sql server 2000 with sp3a ( i know sp4 is out ), installed all the apps and overwrites mdf,nfs and ldf files with the old data, and when i tried to put databse online i get this error:
error 5172: header not valid on file "C:\dbtest.mdf". Pageaudit property is not valid.
Any one can help me?http://www.dbforums.com/t749523.html
http://www.lazydba.com/sql/1__728.html
There's lots of stuff out there...just google it...|||well, i've tried this before post with no result. i just ask here becouse i'm very lost.|||I tried command:
exec sp_attach_db @.dbname ... with so meny variation and i get the same error. Can anyone help me?
Thanks.
I hava an sql server 2000 sp3a on a win2k sp4 machine running all ok. I tried to build a raid 1 using the hdd where sqlserver was and a new one, but i failed to build it and consecuently i lost all data bases.
Using some programs, i recover the mdf, ldf and ndf files from my old sql server 2000.
I reinstalled all the system exactly the same, win2k sp4 and sql server 2000 with sp3a ( i know sp4 is out ), installed all the apps and overwrites mdf,nfs and ldf files with the old data, and when i tried to put databse online i get this error:
error 5172: header not valid on file "C:\dbtest.mdf". Pageaudit property is not valid.
Any one can help me?http://www.dbforums.com/t749523.html
http://www.lazydba.com/sql/1__728.html
There's lots of stuff out there...just google it...|||well, i've tried this before post with no result. i just ask here becouse i'm very lost.|||I tried command:
exec sp_attach_db @.dbname ... with so meny variation and i get the same error. Can anyone help me?
Thanks.
Friday, February 24, 2012
Error 28055 when creating mirroring endpoint.
I tried to build a certifictae based endpoint to mirror databases.
However all the time I try to create the endpoint I got the Message:
"The certificta e'MyCert' is not valid fer endpoint authentication. The
certificate must have a privare key encrypted with the database master key
and current UTC date has to be between the certificate start date end
expiration date."
I used the sripts like shown in the example at the help file:
use master
create master key encryption by password ='MyPassword'
go
create certificate 'MyCert' with subject ='Mirroring Certificate',
Expiry_date = '12/31/2020'
go
create Endpoint EPSorry to fast fingers :-)
create Endpoint EP
state=started
as tcp (listener_port=5022, listener_ID=ALL)
for database_mirroring(
Authentication=certificate MyCert,
encryption=required Algorithm AES,
Role=all)
and this create statement will fail all the time
Regards
Michael|||If you live in the eastern hemisphere the newly created cert start date is
not yet valid for a number of hours equal to the difference of hours between
your zone and GMT. So simply specify a start date for the certificate as
well:
create certificate 'MyCert' with subject ='Mirroring Certificate',
Expiry_date = '12/31/2020',
start_date = '02/21/2007';
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Michael W. Schneider" <MichaelWSchneider@.discussions.microsoft.com> wrote
in message news:346EF8CB-35F7-4CEF-8DD0-7A38DBCC87C8@.microsoft.com...
> Sorry to fast fingers :-)
> create Endpoint EP
> state=started
> as tcp (listener_port=5022, listener_ID=ALL)
> for database_mirroring(
> Authentication=certificate MyCert,
> encryption=required Algorithm AES,
> Role=all)
> and this create statement will fail all the time
> Regards
> Michael
>
However all the time I try to create the endpoint I got the Message:
"The certificta e'MyCert' is not valid fer endpoint authentication. The
certificate must have a privare key encrypted with the database master key
and current UTC date has to be between the certificate start date end
expiration date."
I used the sripts like shown in the example at the help file:
use master
create master key encryption by password ='MyPassword'
go
create certificate 'MyCert' with subject ='Mirroring Certificate',
Expiry_date = '12/31/2020'
go
create Endpoint EPSorry to fast fingers :-)
create Endpoint EP
state=started
as tcp (listener_port=5022, listener_ID=ALL)
for database_mirroring(
Authentication=certificate MyCert,
encryption=required Algorithm AES,
Role=all)
and this create statement will fail all the time
Regards
Michael|||If you live in the eastern hemisphere the newly created cert start date is
not yet valid for a number of hours equal to the difference of hours between
your zone and GMT. So simply specify a start date for the certificate as
well:
create certificate 'MyCert' with subject ='Mirroring Certificate',
Expiry_date = '12/31/2020',
start_date = '02/21/2007';
This posting is provided "AS IS" with no warranties, and confers no rights.
HTH,
~ Remus Rusanu
SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"Michael W. Schneider" <MichaelWSchneider@.discussions.microsoft.com> wrote
in message news:346EF8CB-35F7-4CEF-8DD0-7A38DBCC87C8@.microsoft.com...
> Sorry to fast fingers :-)
> create Endpoint EP
> state=started
> as tcp (listener_port=5022, listener_ID=ALL)
> for database_mirroring(
> Authentication=certificate MyCert,
> encryption=required Algorithm AES,
> Role=all)
> and this create statement will fail all the time
> Regards
> Michael
>
Subscribe to:
Posts (Atom)