Error 207: following

Showing posts with label following. Show all posts

Thursday, March 29, 2012

Error accessing database

When I launch a client program that reads the database, I
get the following error message
Error while reading information from database
Error Code Login failed for user 'sa'
Reason Not associated with a trusted SQL Server Connection.
Has anyone got ideas on how to Fix this?
Thanks in advance
DarrinHave a look at the server properties. You should see that the server is set
up to use Windows Authentication only. sa is not a windows account. You
are using sa in a client app. Most people would advise against this.
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Darrin" <darrin.adams@.eei.ericsson.se> wrote in message
news:0a6801c3510d$b546da10$a501280a@.phx.gbl...
> When I launch a client program that reads the database, I
> get the following error message
> Error while reading information from database
> Error Code Login failed for user 'sa'
> Reason Not associated with a trusted SQL Server Connection.
> Has anyone got ideas on how to Fix this?
> Thanks in advance
> Darrin

Tuesday, March 27, 2012

Error 9002 tempdb log file is full

Hi,
I've the following error message, which doesn't make sense to me.
The log file is not full, it has autogrow set to on and the disk drive on
which it
resides has 256GB free space. I hope i'm missing something and welcome
any suggestions on what to do or what to look at.
"Server: Msg 9002, Level 17, State 6, Line 1
The log file for database 'tempdb' is full. Back up the
transaction log for the database to free up some log space."If the application is requesting space in TempDB and the request interval is
faster than the disk can allocate the space then you will see this message
whilst the Autogrow is happening.
If you have this much space then try pre allocating a larger TempDB
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Stressed" <k@.c.co.uk> wrote in message
news:ufQ6UCJlDHA.2536@.tk2msftngp13.phx.gbl...
> Hi,
>
> I've the following error message, which doesn't make sense to me.
> The log file is not full, it has autogrow set to on and the disk drive on
> which it
> resides has 256GB free space. I hope i'm missing something and welcome
> any suggestions on what to do or what to look at.
>
> "Server: Msg 9002, Level 17, State 6, Line 1
>
> The log file for database 'tempdb' is full. Back up the
> transaction log for the database to free up some log space."
>|||Thanks for that, it all makes sense now.
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:O$FlXLJlDHA.1084@.tk2msftngp13.phx.gbl...
> If the application is requesting space in TempDB and the request interval
is
> faster than the disk can allocate the space then you will see this message
> whilst the Autogrow is happening.
> If you have this much space then try pre allocating a larger TempDB
>
> --
> --
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
> www.SQLDTS.com
> I support PASS - the definitive, global community
> for SQL Server professionals - http://www.sqlpass.org
> "Stressed" <k@.c.co.uk> wrote in message
> news:ufQ6UCJlDHA.2536@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> >
> >
> > I've the following error message, which doesn't make sense to me.
> >
> > The log file is not full, it has autogrow set to on and the disk drive
on
> > which it
> >
> > resides has 256GB free space. I hope i'm missing something and welcome
> >
> > any suggestions on what to do or what to look at.
> >
> >
> >
> > "Server: Msg 9002, Level 17, State 6, Line 1
> >
> >
> >
> > The log file for database 'tempdb' is full. Back up the
> >
> > transaction log for the database to free up some log space."
> >
> >
>|||Just to add - check with Profiler what is going on. TempDb could be a target
of a DoS attack.
--
Dejan Sarka, SQL Server MVP
Please reply only to the newsgroups.
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:O$FlXLJlDHA.1084@.tk2msftngp13.phx.gbl...
> If the application is requesting space in TempDB and the request interval
is
> faster than the disk can allocate the space then you will see this message
> whilst the Autogrow is happening.
> If you have this much space then try pre allocating a larger TempDB
>
> --
> --
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
> www.SQLDTS.com
> I support PASS - the definitive, global community
> for SQL Server professionals - http://www.sqlpass.org
> "Stressed" <k@.c.co.uk> wrote in message
> news:ufQ6UCJlDHA.2536@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> >
> >
> > I've the following error message, which doesn't make sense to me.
> >
> > The log file is not full, it has autogrow set to on and the disk drive
on
> > which it
> >
> > resides has 256GB free space. I hope i'm missing something and welcome
> >
> > any suggestions on what to do or what to look at.
> >
> >
> >
> > "Server: Msg 9002, Level 17, State 6, Line 1
> >
> >
> >
> > The log file for database 'tempdb' is full. Back up the
> >
> > transaction log for the database to free up some log space."
> >
> >
>|||The server isn't exposed to the outside world, although the point has been
taken
on board for future occurences of the same.
Thanks.
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:OPFEUOJlDHA.3024@.tk2msftngp13.phx.gbl...
> Just to add - check with Profiler what is going on. TempDb could be a
target
> of a DoS attack.
> --
> Dejan Sarka, SQL Server MVP
> Please reply only to the newsgroups.
> "Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
> news:O$FlXLJlDHA.1084@.tk2msftngp13.phx.gbl...
> > If the application is requesting space in TempDB and the request
interval
> is
> > faster than the disk can allocate the space then you will see this
message
> > whilst the Autogrow is happening.
> >
> > If you have this much space then try pre allocating a larger TempDB
> >
> >
> >
> > --
> > --
> >
> > Allan Mitchell (Microsoft SQL Server MVP)
> > MCSE,MCDBA
> > www.SQLDTS.com
> > I support PASS - the definitive, global community
> > for SQL Server professionals - http://www.sqlpass.org
> >
> > "Stressed" <k@.c.co.uk> wrote in message
> > news:ufQ6UCJlDHA.2536@.tk2msftngp13.phx.gbl...
> > > Hi,
> > >
> > >
> > >
> > > I've the following error message, which doesn't make sense to me.
> > >
> > > The log file is not full, it has autogrow set to on and the disk drive
> on
> > > which it
> > >
> > > resides has 256GB free space. I hope i'm missing something and welcome
> > >
> > > any suggestions on what to do or what to look at.
> > >
> > >
> > >
> > > "Server: Msg 9002, Level 17, State 6, Line 1
> > >
> > >
> > >
> > > The log file for database 'tempdb' is full. Back up the
> > >
> > > transaction log for the database to free up some log space."
> > >
> > >
> >
> >
>sql

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,
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on TechNet and find the following article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e não encontrei informações sobre este FLAG.
Does someone know any information about this error or about this flag?I found several KB's associated with that error such as this one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;841404&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on TechNet and find the following article
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e não encontrei informações sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>

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 26, 2012

error 823, severity 24, state2

The following messages seems happen every two weeks. it may cause by hardware
error, but HP Array Utility hasn't detected any error. Any ideas, does it
make sense to move database to the local hard drive?
Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
Data:Words
0000: 00000337 00000018 00000009 00550053
0010: 0044004e 00540041 00310041 00070000
0020: 00530000 004e0055 00440035 00000042
SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA 1000,
the database is on SAN disks.
Sounds like you may have some corruption in the database.
Try running the DBCC CHECKCATALOG and see what you get back. BOL has some
great suggestions on the usage as well as some others like DBCC CHECKTABLE
and DBCC CHECKxxxxxx
Rick Sawtell
MCT, MCSD, MCDBA
"Joshua" <Joshua@.discussions.microsoft.com> wrote in message
news:A1DF380C-CB99-4125-A713-7E14303C6125@.microsoft.com...
> The following messages seems happen every two weeks. it may cause by
> hardware
> error, but HP Array Utility hasn't detected any error. Any ideas, does it
> make sense to move database to the local hard drive?
> Error: 823, Severity: 24, State: 2
> I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
> file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
> Data:Words
> 0000: 00000337 00000018 00000009 00550053
> 0010: 0044004e 00540041 00310041 00070000
> 0020: 00530000 004e0055 00440035 00000042
> SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA
> 1000,
> the database is on SAN disks.
|||Generally the first thing you do is look up the error number in Books On
line... Here is the info from BOL
Error 823
Severity Level 24
Message Text
I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'.
Explanation
Microsoft SQL ServerT encountered an I/O error on a read or write request
made to a device. This error usually indicates disk problems. However,
additional kernel messages in the error log, recorded before error 823,
should indicate which device is involved.
Action
Check the accessibility and condition of the device in question.
Run hardware diagnostics and correct problems, if possible.
Restore damaged files from the latest database backup. Restoring from a
database backup should always be considered the primary means of fixing a
damaged database.
If you don't have a backup or if the errors detected are very isolated, the
repair functionality of DBCC CHECKDB may be useful. However, using DBCC
CHECKDB can be more time consuming than restoring the damaged files from a
backup, and you may not be able to recover all your data .
Caution If running DBCC CHECKDB with one of the repair clauses does not
correct the problem or if you are unsure how this process may affect your
data, contact your primary support provider.
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
"Joshua" <Joshua@.discussions.microsoft.com> wrote in message
news:A1DF380C-CB99-4125-A713-7E14303C6125@.microsoft.com...
> The following messages seems happen every two weeks. it may cause by
hardware
> error, but HP Array Utility hasn't detected any error. Any ideas, does it
> make sense to move database to the local hard drive?
> Error: 823, Severity: 24, State: 2
> I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
> file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
> Data:Words
> 0000: 00000337 00000018 00000009 00550053
> 0010: 0044004e 00540041 00310041 00070000
> 0020: 00530000 004e0055 00440035 00000042
> SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA
1000,
> the database is on SAN disks.
begin 666 caution.gif
M1TE&.#EA# `+`/<``````#,``&8``)D``,P``/\````S`#,S`&8S`)DS`,PS
M`/\S``!F`#-F`&9F`)EF`,QF`/]F``"9`#.9`&:9`)F9`,R9`/^9``#,`#/,
M`&;,`)G,`,S,`/_,``#_`#/_`&;_`)G_`,S_`/__````,S,`,V8`,YD`,\P`
M,_\`,P`S,S,S,V8S,YDS,\PS,_\S,P!F,S-F,V9F,YEF,\QF,_]F,P"9,S.9
M,V:9,YF9,\R9,_^9,P#,,S/,,V;,,YG,,\S,,__,,P#_,S/_,V;_,YG_,\S_
M,___,P``9C,`9F8`9ID`9LP`9O\`9@.`S9C,S9F8S9IDS9LPS9 O\S9@.!F9C-F
M9F9F9IEF9LQF9O]F9@."99C.99F:99IF99LR99O^99@.#,9C/,9F;,9IG,9LS,
M9O_,9@.#_9C/_9F;_9IG_9LS_9O__9@.``F3,`F68`F9D`F<P`F?\`F0`SF3,S
MF68SF9DSF<PSF?\SF0!FF3-FF69FF9EFF<QFF?]FF0"9F3.9F6:9F9F9F<R9
MF?^9F0#,F3/,F6;,F9G,F<S,F?_,F0#_F3/_F6;_F9G_F<S_F?__F0``S#,`
MS&8`S)D`S,P`S/\`S `SS#,SS&8SS)DSS,PSS/\SS !FS#-FS&9FS)EFS,QF
MS/]FS "9S#.9S&:9S)F9S,R9S/^9S #,S#/,S&;,S)G,S,S,S/_,S #_S#/_
MS&;_S)G_S,S_S/__S ``_S,`_V8`_YD`_\P`__\`_P`S_S,S_V8S_YDS_\PS
M__\S_P!F_S-F_V9F_YEF_\QF__]F_P"9_S.9_V:9_YF9_\R9__^9_P#,_S/,
M_V;,_YG,_\S,___,_P#__S/__V;__YG__\S______P``````````````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M`````````````````````"'Y! $``*P`+ `````,``L`0 @.B`%D)'$BPH,&#
;K HH1)AP(4*%!1A"9$A1X,2'#BMBC#@.P( `[
`
end

error 823, severity 24, state2

Error 823 with msdb

Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the followin
g
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage

But if you are
thinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should no
t
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msd
b
> is fixed, I am dead in the water (the existing plans still run fine). And
I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas
"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens

Error 823 with msdb

Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the following
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>
|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens
|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage

But if you are
thinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should not
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msdb
> is fixed, I am dead in the water (the existing plans still run fine). And I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>
|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens
|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas

"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens

Error 823 with msdb

When I try to create a new Maintenance Plan or revise an existing one I
get the following error:
Error: 823, Severity: 24, State: 2
Microsoft SQL-DMO (ODBC SQL State:HY000)
Error 823: I/O error (torn page) detected during read at offsett
0x000000000f0000 in file 'd:\sqldata\MSSQL\data\msdbdata.mdf'.
There are no known disk problems that I can detect. The existing
Maintenance Plans run fine. I do not have a backup of msdb prior to when
this problem started (I have no idea of when it started, it only appears
when I try to modify the maintenance plan).
I can easily recreate the maintenance plans but I need to fix the problem
with msdb first. Can msdb be repaired, can I empty it to start fresh, can I
use the msdb from an original install'
Any suggestions are greatly appreciated.
Thanks
Russ StevensI just tried to repair msdb
DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
It fixed 6 errors - I now have a bigger mess <g> - am getting the following
error (and other strange errors) when I try to modify a Maintenance Plan;
Error 170: Line 1: Incorrect syntax near ','.
I need a clean working msdb - appreciate any help.
Thanks
Russ Stevens|||Anytime you run a dbcc checkdb with repair_allow_data_loss you risk data
integrity. there is no way to know what kind of data is lost etc. In
your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.
Alternatively you can always restore from backup :)
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the following
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage :) But if you are
thinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should not
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msdb
> is fixed, I am dead in the water (the existing plans still run fine). And I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas
"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevenssql

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.

Error 823

I'm running W2000 server with SQL 7.0 SP2. we get the following error

Error 823, severity 24, state 1 , i/o error (bad page 10) detected
during read of BUF pointer= 0x11959fc80, page ptr=0x45724000, page id=
(0x3:0x777f), dbid=7, status= 0x 801, file=D:\masdata\monitordb.ndf

We continued restoring a backup, but after a few day, the database crash again.Microsoft has reported to fix this error in service pack 3,

FIX: Error 823 or 8966 Reported by SQL Server with Insufficient System Resources

Knowledge base article Q274310sql

Error 823

I am attempting to add a windows login to be able to access a database. Whe
n
I try to do this I receive the following error.
Error 823: I/O Error (bad page id) detected during read at offset
0x00000000ae6000 in file e:\program files\microsoft sql
server\mssql\master.mdf
I also receive the following when I run dbcc checkdb on the master database
Server: Msg 8928, Level 16, State 6, Line 1
Object ID 0, index ID 0: Page (1:1331) could not be processed. See other
errors for details.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:1395). The PageId in the
page header = (0:0).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2, index ID 255: Page (1:1332) could not be processed. See other
errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 6, index ID 0: Page (1:1395) could not be processed. See other
errors for details.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:1331) is pointed to by the next pointer of IAM page (0:0) object
ID 40 index ID 2 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 40, index ID 2 due to invalid
allocation (IAM) page(s).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:1331) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1),
but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED
0_PCT_FULL'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 3407872, index ID 512, page ID (1:1331). The PageId
in the page header = (1:3126).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:1330) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1),
but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED
0_PCT_FULL'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1111693545, index ID 0, page ID (1:1332). The PageId
in the page header = (0:0).
DBCC results for 'master'.
CHECKDB found 1 allocation errors and 1 consistency errors not associated
with any single object.
DBCC results for 'sysobjects'.
There are 1278 rows in 23 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 103 rows in 4 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 4958 rows in 94 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 2232 rows in 1213 pages for object 'syscomments'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'syscomments' (object ID 6).
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 789 rows in 4 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 16 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 5445 rows in 31 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 0 rows in 0 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysdatabases'.
There are 14 rows in 1 pages for object 'sysdatabases'.
DBCC results for 'sysxlogins'.
There are 46 rows in 1 pages for object 'sysxlogins'.
DBCC results for 'sysdevices'.
There are 6 rows in 1 pages for object 'sysdevices'.
DBCC results for 'sysmessages'.
There are 3883 rows in 166 pages for object 'sysmessages'.
DBCC results for 'sysconfigures'.
There are 38 rows in 1 pages for object 'sysconfigures'.
DBCC results for 'sysservers'.
There are 3 rows in 1 pages for object 'sysservers'.
CHECKDB found 1 allocation errors and 1 consistency errors in table
'sysservers' (object ID 40).
DBCC results for 'syslanguages'.
There are 33 rows in 3 pages for object 'syslanguages'.
DBCC results for 'syscharsets'.
There are 114 rows in 33 pages for object 'syscharsets'.
DBCC results for 'sysaltfiles'.
There are 28 rows in 6 pages for object 'sysaltfiles'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
CHECKDB found 1 allocation errors and 1 consistency errors in table '(Object
ID 3407872)' (object ID 3407872).
DBCC results for 'spt_monitor'.
There are 1 rows in 1 pages for object 'spt_monitor'.
DBCC results for 'spt_values'.
There are 730 rows in 7 pages for object 'spt_values'.
DBCC results for 'spt_fallback_db'.
There are 0 rows in 0 pages for object 'spt_fallback_db'.
DBCC results for 'spt_fallback_dev'.
There are 0 rows in 0 pages for object 'spt_fallback_dev'.
DBCC results for 'spt_fallback_usg'.
There are 0 rows in 0 pages for object 'spt_fallback_usg'.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 538976288)' (object ID 538976288).
DBCC results for 'spt_provider_types'.
There are 25 rows in 1 pages for object 'spt_provider_types'.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object
ID 1111693545)' (object ID 1111693545).
DBCC results for 'spt_datatype_info_ext'.
There are 10 rows in 1 pages for object 'spt_datatype_info_ext'.
DBCC results for 'MSreplication_options'.
There are 2 rows in 1 pages for object 'MSreplication_options'.
DBCC results for 'spt_datatype_info'.
There are 36 rows in 1 pages for object 'spt_datatype_info'.
DBCC results for 'spt_server_info'.
There are 29 rows in 1 pages for object 'spt_server_info'.
CHECKDB found 4 allocation errors and 6 consistency errors in database
'master'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKDB (master ).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
How can I correct these errors?Before fixing it, you should check your hardware and look
for issues with your disk subsystem. Check the event logs on
the server and look for any other system errors that may
have occurred around the same time.
After fixing any hardware issues, then you would need to
restore the last known good backup of the master database.
-Sue
On Wed, 29 Mar 2006 10:08:01 -0800, rleamey
<rleamey@.discussions.microsoft.com> wrote:

>I am attempting to add a windows login to be able to access a database. Wh
en
>I try to do this I receive the following error.
>Error 823: I/O Error (bad page id) detected during read at offset
>0x00000000ae6000 in file e:\program files\microsoft sql
>server\mssql\master.mdf
>I also receive the following when I run dbcc checkdb on the master database
>Server: Msg 8928, Level 16, State 6, Line 1
>Object ID 0, index ID 0: Page (1:1331) could not be processed. See other
>errors for details.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 0, index ID 0, page ID (1:1395). The PageId in the
>page header = (0:0).
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 2, index ID 255: Page (1:1332) could not be processed. See other
>errors for details.
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 6, index ID 0: Page (1:1395) could not be processed. See other
>errors for details.
>Server: Msg 2575, Level 16, State 1, Line 1
>IAM page (1:1331) is pointed to by the next pointer of IAM page (0:0) objec
t
>ID 40 index ID 2 but was not detected in the scan.
>Server: Msg 7965, Level 16, State 1, Line 1
>Table error: Could not check object ID 40, index ID 2 due to invalid
>allocation (IAM) page(s).
>Server: Msg 8906, Level 16, State 1, Line 1
>Page (1:1331) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1)
,
>but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED
>0_PCT_FULL'.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 3407872, index ID 512, page ID (1:1331). The PageId
>in the page header = (1:3126).
>Server: Msg 8906, Level 16, State 1, Line 1
>Page (1:1330) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1)
,
>but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED
>0_PCT_FULL'.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 1111693545, index ID 0, page ID (1:1332). The PageId
>in the page header = (0:0).
>DBCC results for 'master'.
>CHECKDB found 1 allocation errors and 1 consistency errors not associated
>with any single object.
>DBCC results for 'sysobjects'.
>There are 1278 rows in 23 pages for object 'sysobjects'.
>DBCC results for 'sysindexes'.
>There are 103 rows in 4 pages for object 'sysindexes'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table
>'sysindexes' (object ID 2).
>DBCC results for 'syscolumns'.
>There are 4958 rows in 94 pages for object 'syscolumns'.
>DBCC results for 'systypes'.
>There are 26 rows in 1 pages for object 'systypes'.
>DBCC results for 'syscomments'.
>There are 2232 rows in 1213 pages for object 'syscomments'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table
>'syscomments' (object ID 6).
>DBCC results for 'sysfiles1'.
>There are 2 rows in 1 pages for object 'sysfiles1'.
>DBCC results for 'syspermissions'.
>There are 789 rows in 4 pages for object 'syspermissions'.
>DBCC results for 'sysusers'.
>There are 16 rows in 1 pages for object 'sysusers'.
>DBCC results for 'sysproperties'.
>There are 0 rows in 0 pages for object 'sysproperties'.
>DBCC results for 'sysdepends'.
>There are 5445 rows in 31 pages for object 'sysdepends'.
>DBCC results for 'sysreferences'.
>There are 0 rows in 0 pages for object 'sysreferences'.
>DBCC results for 'sysfulltextcatalogs'.
>There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
>DBCC results for 'sysfulltextnotify'.
>There are 0 rows in 0 pages for object 'sysfulltextnotify'.
>DBCC results for 'sysdatabases'.
>There are 14 rows in 1 pages for object 'sysdatabases'.
>DBCC results for 'sysxlogins'.
>There are 46 rows in 1 pages for object 'sysxlogins'.
>DBCC results for 'sysdevices'.
>There are 6 rows in 1 pages for object 'sysdevices'.
>DBCC results for 'sysmessages'.
>There are 3883 rows in 166 pages for object 'sysmessages'.
>DBCC results for 'sysconfigures'.
>There are 38 rows in 1 pages for object 'sysconfigures'.
>DBCC results for 'sysservers'.
>There are 3 rows in 1 pages for object 'sysservers'.
>CHECKDB found 1 allocation errors and 1 consistency errors in table
>'sysservers' (object ID 40).
>DBCC results for 'syslanguages'.
>There are 33 rows in 3 pages for object 'syslanguages'.
>DBCC results for 'syscharsets'.
>There are 114 rows in 33 pages for object 'syscharsets'.
>DBCC results for 'sysaltfiles'.
>There are 28 rows in 6 pages for object 'sysaltfiles'.
>DBCC results for 'sysfilegroups'.
>There are 1 rows in 1 pages for object 'sysfilegroups'.
>CHECKDB found 1 allocation errors and 1 consistency errors in table '(Objec
t
>ID 3407872)' (object ID 3407872).
>DBCC results for 'spt_monitor'.
>There are 1 rows in 1 pages for object 'spt_monitor'.
>DBCC results for 'spt_values'.
>There are 730 rows in 7 pages for object 'spt_values'.
>DBCC results for 'spt_fallback_db'.
>There are 0 rows in 0 pages for object 'spt_fallback_db'.
>DBCC results for 'spt_fallback_dev'.
>There are 0 rows in 0 pages for object 'spt_fallback_dev'.
>DBCC results for 'spt_fallback_usg'.
>There are 0 rows in 0 pages for object 'spt_fallback_usg'.
>CHECKDB found 1 allocation errors and 0 consistency errors in table '(Objec
t
>ID 538976288)' (object ID 538976288).
>DBCC results for 'spt_provider_types'.
>There are 25 rows in 1 pages for object 'spt_provider_types'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table '(Objec
t
>ID 1111693545)' (object ID 1111693545).
>DBCC results for 'spt_datatype_info_ext'.
>There are 10 rows in 1 pages for object 'spt_datatype_info_ext'.
>DBCC results for 'MSreplication_options'.
>There are 2 rows in 1 pages for object 'MSreplication_options'.
>DBCC results for 'spt_datatype_info'.
>There are 36 rows in 1 pages for object 'spt_datatype_info'.
>DBCC results for 'spt_server_info'.
>There are 29 rows in 1 pages for object 'spt_server_info'.
>CHECKDB found 4 allocation errors and 6 consistency errors in database
>'master'.
>repair_allow_data_loss is the minimum repair level for the errors found by
>DBCC CHECKDB (master ).
>DBCC execution completed. If DBCC printed error messages, contact your
>system administrator.
>How can I correct these errors?|||Would there be anyway to fix it if we did not have a good copy of the backup
?
"Sue Hoegemeier" wrote:

> Before fixing it, you should check your hardware and look
> for issues with your disk subsystem. Check the event logs on
> the server and look for any other system errors that may
> have occurred around the same time.
> After fixing any hardware issues, then you would need to
> restore the last known good backup of the master database.
> -Sue
> On Wed, 29 Mar 2006 10:08:01 -0800, rleamey
> <rleamey@.discussions.microsoft.com> wrote:
>
>|||Restoring is the best option. If that's not an option, you
can rebuild master using the rebuildm.exe
You can find more information on how to do this in the books
online topic: Rebuilding the master Database
-Sue
On Thu, 30 Mar 2006 05:09:02 -0800, rleamey
<rleamey@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Would there be anyway to fix it if we did not have a good copy of the backu
p?
>"Sue Hoegemeier" wrote:
>

Thursday, March 29, 2012

Error accessing database

Tuesday, March 27, 2012

Error 9002 tempdb log file is full

Error 8909 in job...is it?

Error 8909 in job...is it?

Error 8909 in job...is it?

Error 8623

Error 8623

Error 8623

Error 8623

Monday, March 26, 2012

error 823, severity 24, state2

error 823, severity 24, state2

error 823, severity 24, state2

Error 823 with msdb

Error 823 with msdb

Error 823 with msdb

Error 823 that I cant fix

Error 823

Error 823

Error 207

Blog Archive

About Me