Error 207: received

Showing posts with label received. 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
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
>

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--

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

Error 8623

Hi,
After some changes in my database when I try to execute following statement:
delete from dbo.PrzychodH
i received this error:
Server: Msg 8623, Level 16, State 1, Line 1
Internal Query Processor Error:
The query processor could not produce a query plan.
Contact your primary support provider for more information.
When I dropped all changes this error does NOT disappeared.
Sql2000 SP4 on WinServ2003 SP1.
Is this SQL2k SP4 new bug?
MarekMarek,
Not sure what you're doing but might take a look at:
http://support.microsoft.com/search...>
ast=3&mode=a
There are quite a few references to the error code in here.
Also, might perform a DBCC CHECKTABLE on przychodH just to rule that out as
a possible cause.
HTH
Jerry
"Marek" <marlie@.wp.pl> wrote in message
news:OcbJYr2wFHA.3124@.TK2MSFTNGP12.phx.gbl...
> Hi,
>
> After some changes in my database when I try to execute following
> statement:
>
> delete from dbo.PrzychodH
>
> i received this error:
>
> Server: Msg 8623, Level 16, State 1, Line 1
> Internal Query Processor Error:
> The query processor could not produce a query plan.
> Contact your primary support provider for more information.
>
> When I dropped all changes this error does NOT disappeared.
>
> Sql2000 SP4 on WinServ2003 SP1.
>
> Is this SQL2k SP4 new bug?
>
> Marek
>
>sql

Error 8623

Hi,
After some changes in my database when I try to execute following statement:
delete from dbo.PrzychodH
i received this error:
Server: Msg 8623, Level 16, State 1, Line 1
Internal Query Processor Error:
The query processor could not produce a query plan.
Contact your primary support provider for more information.
When I dropped all changes this error does NOT disappeared.
Sql2000 SP4 on WinServ2003 SP1.
Is this SQL2k SP4 new bug?
Marek
Marek,
Not sure what you're doing but might take a look at:
http://support.microsoft.com/search/...2&ast=3&mode=a
There are quite a few references to the error code in here.
Also, might perform a DBCC CHECKTABLE on przychodH just to rule that out as
a possible cause.
HTH
Jerry
"Marek" <marlie@.wp.pl> wrote in message
news:OcbJYr2wFHA.3124@.TK2MSFTNGP12.phx.gbl...
> Hi,
>
> After some changes in my database when I try to execute following
> statement:
>
> delete from dbo.PrzychodH
>
> i received this error:
>
> Server: Msg 8623, Level 16, State 1, Line 1
> Internal Query Processor Error:
> The query processor could not produce a query plan.
> Contact your primary support provider for more information.
>
> When I dropped all changes this error does NOT disappeared.
>
> Sql2000 SP4 on WinServ2003 SP1.
>
> Is this SQL2k SP4 new bug?
>
> Marek
>
>

Error 8623

Hi,
After some changes in my database when I try to execute following statement:
delete from dbo.PrzychodH
i received this error:
Server: Msg 8623, Level 16, State 1, Line 1
Internal Query Processor Error:
The query processor could not produce a query plan.
Contact your primary support provider for more information.
When I dropped all changes this error does NOT disappeared.
Sql2000 SP4 on WinServ2003 SP1.
Is this SQL2k SP4 new bug?
MarekMarek,
Not sure what you're doing but might take a look at:
http://support.microsoft.com/search/default.aspx?spid=2852&query=not+produce+a+query+plan&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a
There are quite a few references to the error code in here.
Also, might perform a DBCC CHECKTABLE on przychodH just to rule that out as
a possible cause.
HTH
Jerry
"Marek" <marlie@.wp.pl> wrote in message
news:OcbJYr2wFHA.3124@.TK2MSFTNGP12.phx.gbl...
> Hi,
>
> After some changes in my database when I try to execute following
> statement:
>
> delete from dbo.PrzychodH
>
> i received this error:
>
> Server: Msg 8623, Level 16, State 1, Line 1
> Internal Query Processor Error:
> The query processor could not produce a query plan.
> Contact your primary support provider for more information.
>
> When I dropped all changes this error does NOT disappeared.
>
> Sql2000 SP4 on WinServ2003 SP1.
>
> Is this SQL2k SP4 new bug?
>
> Marek
>
>

Monday, March 19, 2012

Error 7102, Severity Level 20, State 7

We have received the following error in the production. It is a SQL
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.?^E^@.?^F^@.?^G^@.?^@.?.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.
Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegr oups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.?^E^@.?^F^@.?^G^@.?^@.?.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>
|||Thnx for the post.

Error 7102, Severity Level 20, State 7

We have received the following error in the production. It is a SQL
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
--
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegroups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>|||Thnx for the post.

Error 7102, Severity Level 20, State 7

We have received the following error in the production. It is a SQL
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknow
n
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
--
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegroups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unkn
own
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>|||Thnx for the post.

Friday, February 24, 2012

Error 29506. SQL Server Setup failed to modify security permissions

Received the following error while installing SP2

MSI (s) (D8!A0) [21:07:09:062]: Product: Microsoft SQL Server 2005 -- Error 29506. SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user Administrator. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.

Tried running install with a domain account and local account with same results.

Based on the error message, I checked permission on the drive and still received the same error.

Followed resolution based on KB 916766, this did not resolve the error.

Only possible resolution I found was to disable UAP, reboot and retry the install. This will be done as a last resort, but any other suggestion will be appreciated.

Many Thanks

http://support.microsoft.com/kb/916766
This was the solution. Pays to read the resolution carefully
Went through ALL the files and finally found the ones without proper permissions

|||Check whether the account(admin ID) u r using to install SP2 has sysadmin privilege in SQL

Error 29506. SQL Server Setup failed to modify security permissions

Received the following error while installing SP2

Tried running install with a domain account and local account with same results.

Based on the error message, I checked permission on the drive and still received the same error.

Followed resolution based on KB 916766, this did not resolve the error.

Only possible resolution I found was to disable UAP, reboot and retry the install. This will be done as a last resort, but any other suggestion will be appreciated.

Many Thanks

http://support.microsoft.com/kb/916766
This was the solution. Pays to read the resolution carefully
Went through ALL the files and finally found the ones without proper permissions

|||Check whether the account(admin ID) u r using to install SP2 has sysadmin privilege in SQL

Sunday, February 19, 2012

error 2501 performing dbcc reindex

To answer you questions, I'm able to select the data in the AssignGOP table
just fine. It all looks accurate. I did a DBCC checkcatalog and checkdb and
there are no errors.
I do know there are no indexes on this table to defrag, so could this be
causing my issue?
I read through that article awhile back. If I recall, to reindex, you have
to be in single-user mode, which we can't do so in our enviroment, we've
chosen defragging indexes over reindexing. I'm sorry for the confusion in my
wording.
"Paul S Randal [MS]" wrote:

> I recognize that code - I wrote that BOL example :-)
> One thing to be aware of - you're not using doing a reindex using this
> script, you're doing a defrag. They're different operations. You should read
> the whitepaper
> http://www.microsoft.com/technet/pro.../ss2kidbp.mspx
> to see if you really need to be doing this.
> It looks like a call to DBCC SHOWCONTIG is failing for some reason - I
> suspect there may be something wrong with your system catalogs. Can you run
> DBCC CHECKCATALOG and DBCC CHECKDB on the Hopping database? What happens if
> you try a select from the AssignGOP table?
> Thanks
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Josephine" <Josephine@.discussions.microsoft.com> wrote in message
> news:D896B2C3-2834-4C60-A7D5-5F9045E5F753@.microsoft.com...
> the
> rights.
> and
> exist
> other
>
>
|||No need to apologize for being unclear - I'm happy to help.
You don't have to be in single-user mode to reindex. I think you're getting
confused with the concurrency possible while rebuilding an index. When
rebuilding a non-clustered index, the table is read-only and when rebuilding
a clustered index, the table is not even readable.
The lack of indexes does mean it won't be defragged but the cursor to select
indexes should skip the heap:
[vbcol=seagreen]
- the IndexDepth property for a heap is always zero.
Can you post the results from the following query? I believe you that you
have no indexes but I'd like to see what data is there for the heap.
select * from sysindexes where id=object_id('AssignGOP')
Thanks.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Josephine" <Josephine@.discussions.microsoft.com> wrote in message
news:30B5C3B8-58E2-4CF4-B9D6-A4D82A01C9F7@.microsoft.com...
> Ha,ha! Yes, the BOL examples have helped me a bunch!

> To answer you questions, I'm able to select the data in the AssignGOP
table
> just fine. It all looks accurate. I did a DBCC checkcatalog and checkdb
and
> there are no errors.
> I do know there are no indexes on this table to defrag, so could this be
> causing my issue?
> I read through that article awhile back. If I recall, to reindex, you have
> to be in single-user mode, which we can't do so in our enviroment, we've
> chosen defragging indexes over reindexing. I'm sorry for the confusion in
my[vbcol=seagreen]
> wording.
> "Paul S Randal [MS]" wrote:
read[vbcol=seagreen]
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx[vbcol=seagreen]
run[vbcol=seagreen]
if[vbcol=seagreen]
rights.[vbcol=seagreen]
run[vbcol=seagreen]
named[vbcol=seagreen]
step[vbcol=seagreen]
the[vbcol=seagreen]
checktable,[vbcol=seagreen]
to[vbcol=seagreen]

error 2501 performing dbcc reindex

To answer you questions, I'm able to select the data in the AssignGOP table
just fine. It all looks accurate. I did a DBCC checkcatalog and checkdb and
there are no errors.
I do know there are no indexes on this table to defrag, so could this be
causing my issue?
I read through that article awhile back. If I recall, to reindex, you have
to be in single-user mode, which we can't do so in our enviroment, we've
chosen defragging indexes over reindexing. I'm sorry for the confusion in my
wording.
"Paul S Randal [MS]" wrote:

> I recognize that code - I wrote that BOL example :-)
> One thing to be aware of - you're not using doing a reindex using this
> script, you're doing a defrag. They're different operations. You should re
ad
> the whitepaper
> [url]http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx[/ur
l]
> to see if you really need to be doing this.
> It looks like a call to DBCC SHOWCONTIG is failing for some reason - I
> suspect there may be something wrong with your system catalogs. Can you ru
n
> DBCC CHECKCATALOG and DBCC CHECKDB on the Hopping database? What happens i
f
> you try a select from the AssignGOP table?
> Thanks
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Josephine" <Josephine@.discussions.microsoft.com> wrote in message
> news:D896B2C3-2834-4C60-A7D5-5F9045E5F753@.microsoft.com...
> the
> rights.
> and
> exist
> other
>
>|||No need to apologize for being unclear - I'm happy to help.
You don't have to be in single-user mode to reindex. I think you're getting
confused with the concurrency possible while rebuilding an index. When
rebuilding a non-clustered index, the table is read-only and when rebuilding
a clustered index, the table is not even readable.
The lack of indexes does mean it won't be defragged but the cursor to select
indexes should skip the heap:

- the IndexDepth property for a heap is always zero.
Can you post the results from the following query? I believe you that you
have no indexes but I'd like to see what data is there for the heap.
select * from sysindexes where id=object_id('AssignGOP')
Thanks.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Josephine" <Josephine@.discussions.microsoft.com> wrote in message
news:30B5C3B8-58E2-4CF4-B9D6-A4D82A01C9F7@.microsoft.com...[vbcol=seagreen]
> Ha,ha! Yes, the BOL examples have helped me a bunch!

> To answer you questions, I'm able to select the data in the AssignGOP
table
> just fine. It all looks accurate. I did a DBCC checkcatalog and checkdb
and
> there are no errors.
> I do know there are no indexes on this table to defrag, so could this be
> causing my issue?
> I read through that article awhile back. If I recall, to reindex, you have
> to be in single-user mode, which we can't do so in our enviroment, we've
> chosen defragging indexes over reindexing. I'm sorry for the confusion in
my[vbcol=seagreen]
> wording.
> "Paul S Randal [MS]" wrote:
>
read[vbcol=seagreen]
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx[vbcol=seagreen]
run[vbcol=seagreen]
if[vbcol=seagreen]
rights.[vbcol=seagreen]
run[vbcol=seagreen]
named[vbcol=seagreen]
step[vbcol=seagreen]
the[vbcol=seagreen]
checktable,[vbcol=seagreen]
to[vbcol=seagreen]

error 2501 performing dbcc reindex

I run dbcc reindex at night and received error 2501 on several of the
databases.
Based on what Books Online recommends, I have ran a dbcc checktable, and
checkdb for that matter...no errors. I also verified the table(s) to exist in
the database and are also in the sysobjects. Does anyone have any other ideas
as to why this job is failing and how I fix it?
Thank youCan you post the error output, exact DBCC command, and output from
sysobjects?
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Josephine" <Josephine@.discussions.microsoft.com> wrote in message
news:3582C3AB-FE6A-45C5-9536-918962706A50@.microsoft.com...
> I run dbcc reindex at night and received error 2501 on several of the
> databases.
> Based on what Books Online recommends, I have ran a dbcc checktable, and
> checkdb for that matter...no errors. I also verified the table(s) to exist
in
> the database and are also in the sysobjects. Does anyone have any other
ideas
> as to why this job is failing and how I fix it?
> Thank you|||Thank you Paul, below is the information I'm dealing with.
Josie.
DBCC Command
*Perform a 'USE <database name>' to select the database in which to run the
script.*/
-- Declare variables
USE Hopping
SET NOCOUNT ON
DECLARE @.tablename VARCHAR (128)
DECLARE @.execstr VARCHAR (255)
DECLARE @.objectid INT
DECLARE @.indexid INT
DECLARE @.frag DECIMAL
DECLARE @.maxfrag DECIMAL
-- Decide on the maximum fragmentation to allow
SELECT @.maxfrag = 30.0
-- Declare cursor
DECLARE tables CURSOR FOR
SELECT TABLE_NAME
FROM INFORMATION_SCHEMA.TABLES
WHERE TABLE_TYPE = 'BASE TABLE'
-- Create the table
CREATE TABLE #fraglist (
ObjectName CHAR (255),
ObjectId INT,
IndexName CHAR (255),
IndexId INT,
Lvl INT,
CountPages INT,
CountRows INT,
MinRecSize INT,
MaxRecSize INT,
AvgRecSize INT,
ForRecCount INT,
Extents INT,
ExtentSwitches INT,
AvgFreeBytes INT,
AvgPageDensity INT,
ScanDensity DECIMAL,
BestCount INT,
ActualCount INT,
LogicalFrag DECIMAL,
ExtentFrag DECIMAL)
-- Open the cursor
OPEN tables
-- Loop through all the tables in the database
FETCH NEXT
FROM tables
INTO @.tablename
WHILE @.@.FETCH_STATUS = 0
BEGIN
-- Do the showcontig of all indexes of the table
INSERT INTO #fraglist
EXEC ('DBCC SHOWCONTIG (''' + @.tablename + ''')
WITH FAST, TABLERESULTS, ALL_INDEXES, NO_INFOMSGS')
FETCH NEXT
FROM tables
INTO @.tablename
END
-- Close and deallocate the cursor
CLOSE tables
DEALLOCATE tables
-- Declare cursor for list of indexes to be defragged
DECLARE indexes CURSOR FOR
SELECT ObjectName, ObjectId, IndexId, LogicalFrag
FROM #fraglist
WHERE LogicalFrag >= @.maxfrag
AND INDEXPROPERTY (ObjectId, IndexName, 'IndexDepth') > 0
-- Open the cursor
OPEN indexes
-- loop through the indexes
FETCH NEXT
FROM indexes
INTO @.tablename, @.objectid, @.indexid, @.frag
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'Executing DBCC INDEXDEFRAG (0, ' + RTRIM(@.tablename) + ',
' + RTRIM(@.indexid) + ') - fragmentation currently '
+ RTRIM(CONVERT(varchar(15),@.frag)) + '%'
SELECT @.execstr = 'DBCC INDEXDEFRAG (0, ' + RTRIM(@.objectid) + ',
' + RTRIM(@.indexid) + ')'
EXEC (@.execstr)
FETCH NEXT
FROM indexes
INTO @.tablename, @.objectid, @.indexid, @.frag
END
-- Close and deallocate the cursor
CLOSE indexes
DEALLOCATE indexes
-- Delete the temporary table
DROP TABLE #fraglist
GO
From Job History
Executed as user: DOMAIN\username. Could not find a table or object named
'AssignGOP'. Check sysobjects. [SQLSTATE 42S02] (Error 2501). The step
failed.
From Sysobjects
AssignGOP 1860201677 U 6 3 1619001347 592 0 0 2004-02-21
11:25:49.007 0 592 0 U 1 115 0 2004-02-21 11:25:49.007 0 0 0 0 0 0 0
"Paul S Randal [MS]" wrote:
> Can you post the error output, exact DBCC command, and output from
> sysobjects?
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Josephine" <Josephine@.discussions.microsoft.com> wrote in message
> news:3582C3AB-FE6A-45C5-9536-918962706A50@.microsoft.com...
> > I run dbcc reindex at night and received error 2501 on several of the
> > databases.
> > Based on what Books Online recommends, I have ran a dbcc checktable, and
> > checkdb for that matter...no errors. I also verified the table(s) to exist
> in
> > the database and are also in the sysobjects. Does anyone have any other
> ideas
> > as to why this job is failing and how I fix it?
> > Thank you
>
>|||I recognize that code - I wrote that BOL example :-)
One thing to be aware of - you're not using doing a reindex using this
script, you're doing a defrag. They're different operations. You should read
the whitepaper
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
to see if you really need to be doing this.
It looks like a call to DBCC SHOWCONTIG is failing for some reason - I
suspect there may be something wrong with your system catalogs. Can you run
DBCC CHECKCATALOG and DBCC CHECKDB on the Hopping database? What happens if
you try a select from the AssignGOP table?
Thanks
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Josephine" <Josephine@.discussions.microsoft.com> wrote in message
news:D896B2C3-2834-4C60-A7D5-5F9045E5F753@.microsoft.com...
> Thank you Paul, below is the information I'm dealing with.
> Josie.
> DBCC Command
> *Perform a 'USE <database name>' to select the database in which to run
the
> script.*/
> -- Declare variables
> USE Hopping
> SET NOCOUNT ON
> DECLARE @.tablename VARCHAR (128)
> DECLARE @.execstr VARCHAR (255)
> DECLARE @.objectid INT
> DECLARE @.indexid INT
> DECLARE @.frag DECIMAL
> DECLARE @.maxfrag DECIMAL
> -- Decide on the maximum fragmentation to allow
> SELECT @.maxfrag = 30.0
> -- Declare cursor
> DECLARE tables CURSOR FOR
> SELECT TABLE_NAME
> FROM INFORMATION_SCHEMA.TABLES
> WHERE TABLE_TYPE = 'BASE TABLE'
> -- Create the table
> CREATE TABLE #fraglist (
> ObjectName CHAR (255),
> ObjectId INT,
> IndexName CHAR (255),
> IndexId INT,
> Lvl INT,
> CountPages INT,
> CountRows INT,
> MinRecSize INT,
> MaxRecSize INT,
> AvgRecSize INT,
> ForRecCount INT,
> Extents INT,
> ExtentSwitches INT,
> AvgFreeBytes INT,
> AvgPageDensity INT,
> ScanDensity DECIMAL,
> BestCount INT,
> ActualCount INT,
> LogicalFrag DECIMAL,
> ExtentFrag DECIMAL)
> -- Open the cursor
> OPEN tables
> -- Loop through all the tables in the database
> FETCH NEXT
> FROM tables
> INTO @.tablename
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> -- Do the showcontig of all indexes of the table
> INSERT INTO #fraglist
> EXEC ('DBCC SHOWCONTIG (''' + @.tablename + ''')
> WITH FAST, TABLERESULTS, ALL_INDEXES, NO_INFOMSGS')
> FETCH NEXT
> FROM tables
> INTO @.tablename
> END
> -- Close and deallocate the cursor
> CLOSE tables
> DEALLOCATE tables
> -- Declare cursor for list of indexes to be defragged
> DECLARE indexes CURSOR FOR
> SELECT ObjectName, ObjectId, IndexId, LogicalFrag
> FROM #fraglist
> WHERE LogicalFrag >= @.maxfrag
> AND INDEXPROPERTY (ObjectId, IndexName, 'IndexDepth') > 0
> -- Open the cursor
> OPEN indexes
> -- loop through the indexes
> FETCH NEXT
> FROM indexes
> INTO @.tablename, @.objectid, @.indexid, @.frag
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> PRINT 'Executing DBCC INDEXDEFRAG (0, ' + RTRIM(@.tablename) + ',
> ' + RTRIM(@.indexid) + ') - fragmentation currently '
> + RTRIM(CONVERT(varchar(15),@.frag)) + '%'
> SELECT @.execstr = 'DBCC INDEXDEFRAG (0, ' + RTRIM(@.objectid) + ',
> ' + RTRIM(@.indexid) + ')'
> EXEC (@.execstr)
> FETCH NEXT
> FROM indexes
> INTO @.tablename, @.objectid, @.indexid, @.frag
> END
> -- Close and deallocate the cursor
> CLOSE indexes
> DEALLOCATE indexes
> -- Delete the temporary table
> DROP TABLE #fraglist
> GO
>
> From Job History
> Executed as user: DOMAIN\username. Could not find a table or object named
> 'AssignGOP'. Check sysobjects. [SQLSTATE 42S02] (Error 2501). The step
> failed.
> From Sysobjects
> AssignGOP 1860201677 U 6 3 1619001347 592 0 0 2004-02-21
> 11:25:49.007 0 592 0 U 1 115 0 2004-02-21 11:25:49.007 0 0 0 0 0 0 0
>
> "Paul S Randal [MS]" wrote:
> > Can you post the error output, exact DBCC command, and output from
> > sysobjects?
> >
> > --
> > Paul Randal
> > Dev Lead, Microsoft SQL Server Storage Engine
> >
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> > "Josephine" <Josephine@.discussions.microsoft.com> wrote in message
> > news:3582C3AB-FE6A-45C5-9536-918962706A50@.microsoft.com...
> > > I run dbcc reindex at night and received error 2501 on several of the
> > > databases.
> > > Based on what Books Online recommends, I have ran a dbcc checktable,
and
> > > checkdb for that matter...no errors. I also verified the table(s) to
exist
> > in
> > > the database and are also in the sysobjects. Does anyone have any
other
> > ideas
> > > as to why this job is failing and how I fix it?
> > > Thank you
> >
> >
> >|||Ha,ha! Yes, the BOL examples have helped me a bunch! :)
To answer you questions, I'm able to select the data in the AssignGOP table
just fine. It all looks accurate. I did a DBCC checkcatalog and checkdb and
there are no errors.
I do know there are no indexes on this table to defrag, so could this be
causing my issue?
I read through that article awhile back. If I recall, to reindex, you have
to be in single-user mode, which we can't do so in our enviroment, we've
chosen defragging indexes over reindexing. I'm sorry for the confusion in my
wording.
"Paul S Randal [MS]" wrote:
> I recognize that code - I wrote that BOL example :-)
> One thing to be aware of - you're not using doing a reindex using this
> script, you're doing a defrag. They're different operations. You should read
> the whitepaper
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
> to see if you really need to be doing this.
> It looks like a call to DBCC SHOWCONTIG is failing for some reason - I
> suspect there may be something wrong with your system catalogs. Can you run
> DBCC CHECKCATALOG and DBCC CHECKDB on the Hopping database? What happens if
> you try a select from the AssignGOP table?
> Thanks
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Josephine" <Josephine@.discussions.microsoft.com> wrote in message
> news:D896B2C3-2834-4C60-A7D5-5F9045E5F753@.microsoft.com...
> > Thank you Paul, below is the information I'm dealing with.
> > Josie.
> >
> > DBCC Command
> >
> > *Perform a 'USE <database name>' to select the database in which to run
> the
> > script.*/
> > -- Declare variables
> > USE Hopping
> > SET NOCOUNT ON
> > DECLARE @.tablename VARCHAR (128)
> > DECLARE @.execstr VARCHAR (255)
> > DECLARE @.objectid INT
> > DECLARE @.indexid INT
> > DECLARE @.frag DECIMAL
> > DECLARE @.maxfrag DECIMAL
> >
> > -- Decide on the maximum fragmentation to allow
> > SELECT @.maxfrag = 30.0
> >
> > -- Declare cursor
> > DECLARE tables CURSOR FOR
> > SELECT TABLE_NAME
> > FROM INFORMATION_SCHEMA.TABLES
> > WHERE TABLE_TYPE = 'BASE TABLE'
> >
> > -- Create the table
> > CREATE TABLE #fraglist (
> > ObjectName CHAR (255),
> > ObjectId INT,
> > IndexName CHAR (255),
> > IndexId INT,
> > Lvl INT,
> > CountPages INT,
> > CountRows INT,
> > MinRecSize INT,
> > MaxRecSize INT,
> > AvgRecSize INT,
> > ForRecCount INT,
> > Extents INT,
> > ExtentSwitches INT,
> > AvgFreeBytes INT,
> > AvgPageDensity INT,
> > ScanDensity DECIMAL,
> > BestCount INT,
> > ActualCount INT,
> > LogicalFrag DECIMAL,
> > ExtentFrag DECIMAL)
> >
> > -- Open the cursor
> > OPEN tables
> >
> > -- Loop through all the tables in the database
> > FETCH NEXT
> > FROM tables
> > INTO @.tablename
> >
> > WHILE @.@.FETCH_STATUS = 0
> > BEGIN
> > -- Do the showcontig of all indexes of the table
> > INSERT INTO #fraglist
> > EXEC ('DBCC SHOWCONTIG (''' + @.tablename + ''')
> > WITH FAST, TABLERESULTS, ALL_INDEXES, NO_INFOMSGS')
> > FETCH NEXT
> > FROM tables
> > INTO @.tablename
> > END
> >
> > -- Close and deallocate the cursor
> > CLOSE tables
> > DEALLOCATE tables
> >
> > -- Declare cursor for list of indexes to be defragged
> > DECLARE indexes CURSOR FOR
> > SELECT ObjectName, ObjectId, IndexId, LogicalFrag
> > FROM #fraglist
> > WHERE LogicalFrag >= @.maxfrag
> > AND INDEXPROPERTY (ObjectId, IndexName, 'IndexDepth') > 0
> >
> > -- Open the cursor
> > OPEN indexes
> >
> > -- loop through the indexes
> > FETCH NEXT
> > FROM indexes
> > INTO @.tablename, @.objectid, @.indexid, @.frag
> >
> > WHILE @.@.FETCH_STATUS = 0
> > BEGIN
> > PRINT 'Executing DBCC INDEXDEFRAG (0, ' + RTRIM(@.tablename) + ',
> > ' + RTRIM(@.indexid) + ') - fragmentation currently '
> > + RTRIM(CONVERT(varchar(15),@.frag)) + '%'
> > SELECT @.execstr = 'DBCC INDEXDEFRAG (0, ' + RTRIM(@.objectid) + ',
> > ' + RTRIM(@.indexid) + ')'
> > EXEC (@.execstr)
> >
> > FETCH NEXT
> > FROM indexes
> > INTO @.tablename, @.objectid, @.indexid, @.frag
> > END
> >
> > -- Close and deallocate the cursor
> > CLOSE indexes
> > DEALLOCATE indexes
> >
> > -- Delete the temporary table
> > DROP TABLE #fraglist
> > GO
> >
> >
> > From Job History
> > Executed as user: DOMAIN\username. Could not find a table or object named
> > 'AssignGOP'. Check sysobjects. [SQLSTATE 42S02] (Error 2501). The step
> > failed.
> >
> > From Sysobjects
> > AssignGOP 1860201677 U 6 3 1619001347 592 0 0 2004-02-21
> > 11:25:49.007 0 592 0 U 1 115 0 2004-02-21 11:25:49.007 0 0 0 0 0 0 0
> >
> >
> > "Paul S Randal [MS]" wrote:
> >
> > > Can you post the error output, exact DBCC command, and output from
> > > sysobjects?
> > >
> > > --
> > > Paul Randal
> > > Dev Lead, Microsoft SQL Server Storage Engine
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > > "Josephine" <Josephine@.discussions.microsoft.com> wrote in message
> > > news:3582C3AB-FE6A-45C5-9536-918962706A50@.microsoft.com...
> > > > I run dbcc reindex at night and received error 2501 on several of the
> > > > databases.
> > > > Based on what Books Online recommends, I have ran a dbcc checktable,
> and
> > > > checkdb for that matter...no errors. I also verified the table(s) to
> exist
> > > in
> > > > the database and are also in the sysobjects. Does anyone have any
> other
> > > ideas
> > > > as to why this job is failing and how I fix it?
> > > > Thank you
> > >
> > >
> > >
>
>|||No need to apologize for being unclear - I'm happy to help.
You don't have to be in single-user mode to reindex. I think you're getting
confused with the concurrency possible while rebuilding an index. When
rebuilding a non-clustered index, the table is read-only and when rebuilding
a clustered index, the table is not even readable.
The lack of indexes does mean it won't be defragged but the cursor to select
indexes should skip the heap:
> > > DECLARE indexes CURSOR FOR
> > > SELECT ObjectName, ObjectId, IndexId, LogicalFrag
> > > FROM #fraglist
> > > WHERE LogicalFrag >= @.maxfrag
> > > AND INDEXPROPERTY (ObjectId, IndexName, 'IndexDepth') > 0
- the IndexDepth property for a heap is always zero.
Can you post the results from the following query? I believe you that you
have no indexes but I'd like to see what data is there for the heap.
select * from sysindexes where id=object_id('AssignGOP')
Thanks.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Josephine" <Josephine@.discussions.microsoft.com> wrote in message
news:30B5C3B8-58E2-4CF4-B9D6-A4D82A01C9F7@.microsoft.com...
> Ha,ha! Yes, the BOL examples have helped me a bunch! :)
> To answer you questions, I'm able to select the data in the AssignGOP
table
> just fine. It all looks accurate. I did a DBCC checkcatalog and checkdb
and
> there are no errors.
> I do know there are no indexes on this table to defrag, so could this be
> causing my issue?
> I read through that article awhile back. If I recall, to reindex, you have
> to be in single-user mode, which we can't do so in our enviroment, we've
> chosen defragging indexes over reindexing. I'm sorry for the confusion in
my
> wording.
> "Paul S Randal [MS]" wrote:
> > I recognize that code - I wrote that BOL example :-)
> >
> > One thing to be aware of - you're not using doing a reindex using this
> > script, you're doing a defrag. They're different operations. You should
read
> > the whitepaper
> >
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
> > to see if you really need to be doing this.
> >
> > It looks like a call to DBCC SHOWCONTIG is failing for some reason - I
> > suspect there may be something wrong with your system catalogs. Can you
run
> > DBCC CHECKCATALOG and DBCC CHECKDB on the Hopping database? What happens
if
> > you try a select from the AssignGOP table?
> >
> > Thanks
> >
> > --
> > Paul Randal
> > Dev Lead, Microsoft SQL Server Storage Engine
> >
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> > "Josephine" <Josephine@.discussions.microsoft.com> wrote in message
> > news:D896B2C3-2834-4C60-A7D5-5F9045E5F753@.microsoft.com...
> > > Thank you Paul, below is the information I'm dealing with.
> > > Josie.
> > >
> > > DBCC Command
> > >
> > > *Perform a 'USE <database name>' to select the database in which to
run
> > the
> > > script.*/
> > > -- Declare variables
> > > USE Hopping
> > > SET NOCOUNT ON
> > > DECLARE @.tablename VARCHAR (128)
> > > DECLARE @.execstr VARCHAR (255)
> > > DECLARE @.objectid INT
> > > DECLARE @.indexid INT
> > > DECLARE @.frag DECIMAL
> > > DECLARE @.maxfrag DECIMAL
> > >
> > > -- Decide on the maximum fragmentation to allow
> > > SELECT @.maxfrag = 30.0
> > >
> > > -- Declare cursor
> > > DECLARE tables CURSOR FOR
> > > SELECT TABLE_NAME
> > > FROM INFORMATION_SCHEMA.TABLES
> > > WHERE TABLE_TYPE = 'BASE TABLE'
> > >
> > > -- Create the table
> > > CREATE TABLE #fraglist (
> > > ObjectName CHAR (255),
> > > ObjectId INT,
> > > IndexName CHAR (255),
> > > IndexId INT,
> > > Lvl INT,
> > > CountPages INT,
> > > CountRows INT,
> > > MinRecSize INT,
> > > MaxRecSize INT,
> > > AvgRecSize INT,
> > > ForRecCount INT,
> > > Extents INT,
> > > ExtentSwitches INT,
> > > AvgFreeBytes INT,
> > > AvgPageDensity INT,
> > > ScanDensity DECIMAL,
> > > BestCount INT,
> > > ActualCount INT,
> > > LogicalFrag DECIMAL,
> > > ExtentFrag DECIMAL)
> > >
> > > -- Open the cursor
> > > OPEN tables
> > >
> > > -- Loop through all the tables in the database
> > > FETCH NEXT
> > > FROM tables
> > > INTO @.tablename
> > >
> > > WHILE @.@.FETCH_STATUS = 0
> > > BEGIN
> > > -- Do the showcontig of all indexes of the table
> > > INSERT INTO #fraglist
> > > EXEC ('DBCC SHOWCONTIG (''' + @.tablename + ''')
> > > WITH FAST, TABLERESULTS, ALL_INDEXES, NO_INFOMSGS')
> > > FETCH NEXT
> > > FROM tables
> > > INTO @.tablename
> > > END
> > >
> > > -- Close and deallocate the cursor
> > > CLOSE tables
> > > DEALLOCATE tables
> > >
> > > -- Declare cursor for list of indexes to be defragged
> > > DECLARE indexes CURSOR FOR
> > > SELECT ObjectName, ObjectId, IndexId, LogicalFrag
> > > FROM #fraglist
> > > WHERE LogicalFrag >= @.maxfrag
> > > AND INDEXPROPERTY (ObjectId, IndexName, 'IndexDepth') > 0
> > >
> > > -- Open the cursor
> > > OPEN indexes
> > >
> > > -- loop through the indexes
> > > FETCH NEXT
> > > FROM indexes
> > > INTO @.tablename, @.objectid, @.indexid, @.frag
> > >
> > > WHILE @.@.FETCH_STATUS = 0
> > > BEGIN
> > > PRINT 'Executing DBCC INDEXDEFRAG (0, ' + RTRIM(@.tablename) + ',
> > > ' + RTRIM(@.indexid) + ') - fragmentation currently '
> > > + RTRIM(CONVERT(varchar(15),@.frag)) + '%'
> > > SELECT @.execstr = 'DBCC INDEXDEFRAG (0, ' + RTRIM(@.objectid) + ',
> > > ' + RTRIM(@.indexid) + ')'
> > > EXEC (@.execstr)
> > >
> > > FETCH NEXT
> > > FROM indexes
> > > INTO @.tablename, @.objectid, @.indexid, @.frag
> > > END
> > >
> > > -- Close and deallocate the cursor
> > > CLOSE indexes
> > > DEALLOCATE indexes
> > >
> > > -- Delete the temporary table
> > > DROP TABLE #fraglist
> > > GO
> > >
> > >
> > > From Job History
> > > Executed as user: DOMAIN\username. Could not find a table or object
named
> > > 'AssignGOP'. Check sysobjects. [SQLSTATE 42S02] (Error 2501). The
step
> > > failed.
> > >
> > > From Sysobjects
> > > AssignGOP 1860201677 U 6 3 1619001347 592 0 0 2004-02-21
> > > 11:25:49.007 0 592 0 U 1 115 0 2004-02-21 11:25:49.007 0 0 0 0 0 0 0
> > >
> > >
> > > "Paul S Randal [MS]" wrote:
> > >
> > > > Can you post the error output, exact DBCC command, and output from
> > > > sysobjects?
> > > >
> > > > --
> > > > Paul Randal
> > > > Dev Lead, Microsoft SQL Server Storage Engine
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > > "Josephine" <Josephine@.discussions.microsoft.com> wrote in message
> > > > news:3582C3AB-FE6A-45C5-9536-918962706A50@.microsoft.com...
> > > > > I run dbcc reindex at night and received error 2501 on several of
the
> > > > > databases.
> > > > > Based on what Books Online recommends, I have ran a dbcc
checktable,
> > and
> > > > > checkdb for that matter...no errors. I also verified the table(s)
to
> > exist
> > > > in
> > > > > the database and are also in the sysobjects. Does anyone have any
> > other
> > > > ideas
> > > > > as to why this job is failing and how I fix it?
> > > > > Thank you
> > > >
> > > >
> > > >
> >
> >
> >

Tuesday, March 27, 2012

Error 8909 in job...is it?

Error 8909 in job...is it?

Error 8909 in job...is it?

Error 8623

Error 8623

Error 8623

Monday, March 19, 2012

Error 7102, Severity Level 20, State 7

Error 7102, Severity Level 20, State 7

Error 7102, Severity Level 20, State 7

Friday, February 24, 2012

Error 29506. SQL Server Setup failed to modify security permissions

Error 29506. SQL Server Setup failed to modify security permissions

Sunday, February 19, 2012

error 2501 performing dbcc reindex

error 2501 performing dbcc reindex

error 2501 performing dbcc reindex

Error 207

Blog Archive

About Me