DBfile usage: errors

Showing posts with label errors. Show all posts

Tuesday, March 27, 2012

DBCC SHRINKDATABASE Errors Running SQL Server 2000 , SP3a

I am running SQL Server 2000 SP3a on Windows 2003
I get the following error when I run DBCC SHRINKDATABASE
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
If I shrink the database using Enterprise Manager, I can shrink all the
files, including the log, except the MDF (PRIMARY) file.
I get the following error when I try to shrink this file:
Error 0 : This server has been connected.You must reconnect to perform this
operation.
I have re-booted the server , but get the same error messages.
I have run DBCC CHECKDB and DBCC CHECKFILEGROUP , and 0 errors are reported
Has anyone any ideas how to resolve this problem?
--
DuncanJTry setting single-user mode.
DuncanJ wrote:
> I am running SQL Server 2000 SP3a on Windows 2003
> I get the following error when I run DBCC SHRINKDATABASE
> [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> If I shrink the database using Enterprise Manager, I can shrink all the
> files, including the log, except the MDF (PRIMARY) file.
> I get the following error when I try to shrink this file:
> Error 0 : This server has been connected.You must reconnect to perform this
> operation.
> I have re-booted the server , but get the same error messages.
> I have run DBCC CHECKDB and DBCC CHECKFILEGROUP , and 0 errors are reported
> Has anyone any ideas how to resolve this problem?
> --
> DuncanJ

DBCC Shrinkdatabase errors

When DBCC ShrinkDatabase ('db-name') is run; the following error is returned.

File ID 1 of database ID 5 cannot be shrunk as it is either being shrunk by another process or is empty.

File ID 3 of database ID 5 cannot be shrunk as it is either being shrunk by another process or is empty.

Cannot shrink log file 2 (logmentusnet) because all logical log files are in use.

The files 1-3 are not empty so I'm assuming that another shrink is already running.

Questions:

1. If I restart the database will the errent database shrink stop?

2. How can I find and stop the errent database shrink process?

3. What's going on, and how can I recover the empty space in the database?

I am also facing the same issue.

Any workaround for this.

Regards

kokila

|||

Hy,

I am with the same problem… somebody can help?

File ID 9 of database ID 6 cannot be shrunk as it is either being shrunk by another process or is empty.

Thursday, March 22, 2012

DBCC Results into a Table Brings Errors!

If you run the script below, it will cause an error. However, if you
run the select portion after the error, it will have accomplished the
desired result. Unfortunately, the table has to be manually dropped
after the proc is run. Any ideas why'? USing the GO keyword is not
an option as it will blow the rest of the script.
CREATE TABLE #db_file_information(
fileid integer,
theFileGroup integer,
Total_Extents integer,
Used_Extents integer,
db varchar(30),
file_Path_name varchar(300)--,
-- File_Free_space decimal(15,2),
-- Percent_Free decimal(15,2)
)
-- Get the size of the datafiles
insert into #db_file_information exec('DBCC showfilestats')
-- add two columns to the temp table
alter table #db_file_information add dude as
((Total_Extents-Used_Extents)/(Total_extents*1.0))
select * from #db_file_information
drop table #db_file_informationTry,
use northwind
go
CREATE TABLE #db_file_information(
Fileid bigint,
[FileGroup] bigint,
TotalExtents bigint,
UsedExtents bigint,
[Name] sysname,
[FileName] varchar(260)
)
go
-- Get the size of the datafiles
insert into #db_file_information
exec('DBCC showfilestats with NO_INFOMSGS')
-- add two columns to the temp table
alter table #db_file_information
add dude as ((TotalExtents - UsedExtents) / nullif((TotalExtents * 1.0), 0))
go
select * from #db_file_information
go
drop table #db_file_information
go
AMB
"dpaskiet@.comcast.net" wrote:

> If you run the script below, it will cause an error. However, if you
> run the select portion after the error, it will have accomplished the
> desired result. Unfortunately, the table has to be manually dropped
> after the proc is run. Any ideas why'? USing the GO keyword is not
> an option as it will blow the rest of the script.
>
> CREATE TABLE #db_file_information(
> fileid integer,
> theFileGroup integer,
> Total_Extents integer,
> Used_Extents integer,
> db varchar(30),
> file_Path_name varchar(300)--,
> -- File_Free_space decimal(15,2),
> -- Percent_Free decimal(15,2)
> )
> -- Get the size of the datafiles
> insert into #db_file_information exec('DBCC showfilestats')
> -- add two columns to the temp table
> alter table #db_file_information add dude as
> ((Total_Extents-Used_Extents)/(Total_extents*1.0))
>
> select * from #db_file_information
>
> drop table #db_file_information
>

Wednesday, March 21, 2012

DBCC Question

We are trying to do some automated weekly optimization processes on a SQL
2000 Server and have had some errors returned when we do a DBCC CheckDB.
I've posted those below. We then tried DBCC CHECKDB repair_allow_data_loss
which returns a message that says that it found 9 errors and repaired 0.
Can anyone help me determine what kind of errors these are and how they
might be fixed?
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 231654031360 owned by data record
identified by RID = (1:2026:23) id = 194502355 and indid = 3.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 234646667264 owned by data record
identified by RID = (1:2026:24) id = 194502355 and indid = 4.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 246486007808 owned by data record
identified by RID = (1:2028:23) id = 469576711 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 246504488960 owned by data record
identified by RID = (1:7431:20) id = 805577908 and indid = 30.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:14296),
slot 3, text ID 246486007808 does not match its reference from page
(1:8421), slot 2.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or
image node page (1:14296), slot 3, text ID 246486007808 is pointed to by
page (1:2028), slot 23 and by page (1:8421), slot 2.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:14378),
slot 1, text ID 234646863872 is not referenced.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:22060),
slot 4, text ID 246504488960 does not match its reference from page
(1:2531), slot 5.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or
image node page (1:22060), slot 4, text ID 246504488960 is pointed to by
page (1:2531), slot 5 and by page (1:7431), slot 20.
DBCC results for 'sunrise'.
DBCC results for 'sysobjects'.
There are 24482 rows in 435 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 2652 rows in 155 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 9 consistency errors in table
'sysindexes' (object ID 2).At a guess, if sql server is unable to repair the database (even with data
loss,
if that is acceptable to you), you will need to restore from your latest
backup.
Verify this before taking any action though
"Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com> wrote
in message news:eBh7qp9lDHA.2732@.TK2MSFTNGP11.phx.gbl...
> We are trying to do some automated weekly optimization processes on a SQL
> 2000 Server and have had some errors returned when we do a DBCC CheckDB.
> I've posted those below. We then tried DBCC CHECKDB
repair_allow_data_loss
> which returns a message that says that it found 9 errors and repaired 0.
> Can anyone help me determine what kind of errors these are and how they
> might be fixed?
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 231654031360 owned by data record
> identified by RID = (1:2026:23) id = 194502355 and indid = 3.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 234646667264 owned by data record
> identified by RID = (1:2026:24) id = 194502355 and indid = 4.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 246486007808 owned by data record
> identified by RID = (1:2028:23) id = 469576711 and indid = 7.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 246504488960 owned by data record
> identified by RID = (1:7431:20) id = 805577908 and indid = 30.
> Server: Msg 8961, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
(1:14296),
> slot 3, text ID 246486007808 does not match its reference from page
> (1:8421), slot 2.
> Server: Msg 8974, Level 16, State 1, Line 1
> Text node referenced by more than one node. Object ID 2, text, ntext, or
> image node page (1:14296), slot 3, text ID 246486007808 is pointed to by
> page (1:2028), slot 23 and by page (1:8421), slot 2.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
(1:14378),
> slot 1, text ID 234646863872 is not referenced.
> Server: Msg 8961, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
(1:22060),
> slot 4, text ID 246504488960 does not match its reference from page
> (1:2531), slot 5.
> Server: Msg 8974, Level 16, State 1, Line 1
> Text node referenced by more than one node. Object ID 2, text, ntext, or
> image node page (1:22060), slot 4, text ID 246504488960 is pointed to by
> page (1:2531), slot 5 and by page (1:7431), slot 20.
> DBCC results for 'sunrise'.
> DBCC results for 'sysobjects'.
> There are 24482 rows in 435 pages for object 'sysobjects'.
> DBCC results for 'sysindexes'.
> There are 2652 rows in 155 pages for object 'sysindexes'.
> CHECKDB found 0 allocation errors and 9 consistency errors in table
> 'sysindexes' (object ID 2).
>|||The latest backup was made after these messages were created. Wouldn't
these errors still exist after restoring?
"Stressed" <k@.c.co.uk> wrote in message
news:Odykkb%23lDHA.988@.TK2MSFTNGP10.phx.gbl...
> At a guess, if sql server is unable to repair the database (even with data
> loss,
> if that is acceptable to you), you will need to restore from your latest
> backup.
> Verify this before taking any action though
>
> "Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com> wrote
> in message news:eBh7qp9lDHA.2732@.TK2MSFTNGP11.phx.gbl...
> > We are trying to do some automated weekly optimization processes on a
SQL
> > 2000 Server and have had some errors returned when we do a DBCC CheckDB.
> > I've posted those below. We then tried DBCC CHECKDB
> repair_allow_data_loss
> > which returns a message that says that it found 9 errors and repaired 0.
> >
> > Can anyone help me determine what kind of errors these are and how they
> > might be fixed?
> >
> > Server: Msg 8929, Level 16, State 1, Line 1
> >
> > Object ID 2: Errors found in text ID 231654031360 owned by data record
> > identified by RID = (1:2026:23) id = 194502355 and indid = 3.
> >
> > Server: Msg 8929, Level 16, State 1, Line 1
> >
> > Object ID 2: Errors found in text ID 234646667264 owned by data record
> > identified by RID = (1:2026:24) id = 194502355 and indid = 4.
> >
> > Server: Msg 8929, Level 16, State 1, Line 1
> >
> > Object ID 2: Errors found in text ID 246486007808 owned by data record
> > identified by RID = (1:2028:23) id = 469576711 and indid = 7.
> >
> > Server: Msg 8929, Level 16, State 1, Line 1
> >
> > Object ID 2: Errors found in text ID 246504488960 owned by data record
> > identified by RID = (1:7431:20) id = 805577908 and indid = 30.
> >
> > Server: Msg 8961, Level 16, State 1, Line 1
> >
> > Table error: Object ID 2. The text, ntext, or image node at page
> (1:14296),
> > slot 3, text ID 246486007808 does not match its reference from page
> > (1:8421), slot 2.
> >
> > Server: Msg 8974, Level 16, State 1, Line 1
> >
> > Text node referenced by more than one node. Object ID 2, text, ntext, or
> > image node page (1:14296), slot 3, text ID 246486007808 is pointed to by
> > page (1:2028), slot 23 and by page (1:8421), slot 2.
> >
> > Server: Msg 8964, Level 16, State 1, Line 1
> >
> > Table error: Object ID 2. The text, ntext, or image node at page
> (1:14378),
> > slot 1, text ID 234646863872 is not referenced.
> >
> > Server: Msg 8961, Level 16, State 1, Line 1
> >
> > Table error: Object ID 2. The text, ntext, or image node at page
> (1:22060),
> > slot 4, text ID 246504488960 does not match its reference from page
> > (1:2531), slot 5.
> >
> > Server: Msg 8974, Level 16, State 1, Line 1
> >
> > Text node referenced by more than one node. Object ID 2, text, ntext, or
> > image node page (1:22060), slot 4, text ID 246504488960 is pointed to by
> > page (1:2531), slot 5 and by page (1:7431), slot 20.
> >
> > DBCC results for 'sunrise'.
> >
> > DBCC results for 'sysobjects'.
> >
> > There are 24482 rows in 435 pages for object 'sysobjects'.
> >
> > DBCC results for 'sysindexes'.
> >
> > There are 2652 rows in 155 pages for object 'sysindexes'.
> >
> > CHECKDB found 0 allocation errors and 9 consistency errors in table
> > 'sysindexes' (object ID 2).
> >
> >
>|||This database has over 900 tables. Is there any way to know which table's
indexes are the problem? Or to rebuild all of the indexes in the database?
"harvinder" <hs@.metratech.com> wrote in message
news:0c6301c397eb$fcfeeda0$a501280a@.phx.gbl...
> most of the appear to belong to index...so better way
> will be to recreate the corrupted indexes and run dbcc
> checkdb again
> Thanks
> --Harvinder
> >--Original Message--
> >We are trying to do some automated weekly optimization
> processes on a SQL
> >2000 Server and have had some errors returned when we do
> a DBCC CheckDB.
> >I've posted those below. We then tried DBCC CHECKDB
> repair_allow_data_loss
> >which returns a message that says that it found 9 errors
> and repaired 0.
> >
> >Can anyone help me determine what kind of errors these
> are and how they
> >might be fixed?
> >
> >Server: Msg 8929, Level 16, State 1, Line 1
> >
> >Object ID 2: Errors found in text ID 231654031360 owned
> by data record
> >identified by RID = (1:2026:23) id = 194502355 and indid
> = 3.
> >
> >Server: Msg 8929, Level 16, State 1, Line 1
> >
> >Object ID 2: Errors found in text ID 234646667264 owned
> by data record
> >identified by RID = (1:2026:24) id = 194502355 and indid
> = 4.
> >
> >Server: Msg 8929, Level 16, State 1, Line 1
> >
> >Object ID 2: Errors found in text ID 246486007808 owned
> by data record
> >identified by RID = (1:2028:23) id = 469576711 and indid
> = 7.
> >
> >Server: Msg 8929, Level 16, State 1, Line 1
> >
> >Object ID 2: Errors found in text ID 246504488960 owned
> by data record
> >identified by RID = (1:7431:20) id = 805577908 and indid
> = 30.
> >
> >Server: Msg 8961, Level 16, State 1, Line 1
> >
> >Table error: Object ID 2. The text, ntext, or image node
> at page (1:14296),
> >slot 3, text ID 246486007808 does not match its reference
> from page
> >(1:8421), slot 2.
> >
> >Server: Msg 8974, Level 16, State 1, Line 1
> >
> >Text node referenced by more than one node. Object ID 2,
> text, ntext, or
> >image node page (1:14296), slot 3, text ID 246486007808
> is pointed to by
> >page (1:2028), slot 23 and by page (1:8421), slot 2.
> >
> >Server: Msg 8964, Level 16, State 1, Line 1
> >
> >Table error: Object ID 2. The text, ntext, or image node
> at page (1:14378),
> >slot 1, text ID 234646863872 is not referenced.
> >
> >Server: Msg 8961, Level 16, State 1, Line 1
> >
> >Table error: Object ID 2. The text, ntext, or image node
> at page (1:22060),
> >slot 4, text ID 246504488960 does not match its reference
> from page
> >(1:2531), slot 5.
> >
> >Server: Msg 8974, Level 16, State 1, Line 1
> >
> >Text node referenced by more than one node. Object ID 2,
> text, ntext, or
> >image node page (1:22060), slot 4, text ID 246504488960
> is pointed to by
> >page (1:2531), slot 5 and by page (1:7431), slot 20.
> >
> >DBCC results for 'sunrise'.
> >
> >DBCC results for 'sysobjects'.
> >
> >There are 24482 rows in 435 pages for object 'sysobjects'.
> >
> >DBCC results for 'sysindexes'.
> >
> >There are 2652 rows in 155 pages for object 'sysindexes'.
> >
> >CHECKDB found 0 allocation errors and 9 consistency
> errors in table
> >'sysindexes' (object ID 2).
> >
> >
> >.
> >|||To find the index name use the following query in you database.
select name from dbo.sysindexes
where id = 194502355 and indid = 3
The example above will find the index in the first error.
HTH
--
Barry McAuslin
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com> wrote
in message news:uRhM7g$lDHA.2000@.TK2MSFTNGP12.phx.gbl...
> This database has over 900 tables. Is there any way to know which table's
> indexes are the problem? Or to rebuild all of the indexes in the
database?
>
> "harvinder" <hs@.metratech.com> wrote in message
> news:0c6301c397eb$fcfeeda0$a501280a@.phx.gbl...
> > most of the appear to belong to index...so better way
> > will be to recreate the corrupted indexes and run dbcc
> > checkdb again
> >
> > Thanks
> > --Harvinder
> >
> > >--Original Message--
> > >We are trying to do some automated weekly optimization
> > processes on a SQL
> > >2000 Server and have had some errors returned when we do
> > a DBCC CheckDB.
> > >I've posted those below. We then tried DBCC CHECKDB
> > repair_allow_data_loss
> > >which returns a message that says that it found 9 errors
> > and repaired 0.
> > >
> > >Can anyone help me determine what kind of errors these
> > are and how they
> > >might be fixed?
> > >
> > >Server: Msg 8929, Level 16, State 1, Line 1
> > >
> > >Object ID 2: Errors found in text ID 231654031360 owned
> > by data record
> > >identified by RID = (1:2026:23) id = 194502355 and indid
> > = 3.
> > >
> > >Server: Msg 8929, Level 16, State 1, Line 1
> > >
> > >Object ID 2: Errors found in text ID 234646667264 owned
> > by data record
> > >identified by RID = (1:2026:24) id = 194502355 and indid
> > = 4.
> > >
> > >Server: Msg 8929, Level 16, State 1, Line 1
> > >
> > >Object ID 2: Errors found in text ID 246486007808 owned
> > by data record
> > >identified by RID = (1:2028:23) id = 469576711 and indid
> > = 7.
> > >
> > >Server: Msg 8929, Level 16, State 1, Line 1
> > >
> > >Object ID 2: Errors found in text ID 246504488960 owned
> > by data record
> > >identified by RID = (1:7431:20) id = 805577908 and indid
> > = 30.
> > >
> > >Server: Msg 8961, Level 16, State 1, Line 1
> > >
> > >Table error: Object ID 2. The text, ntext, or image node
> > at page (1:14296),
> > >slot 3, text ID 246486007808 does not match its reference
> > from page
> > >(1:8421), slot 2.
> > >
> > >Server: Msg 8974, Level 16, State 1, Line 1
> > >
> > >Text node referenced by more than one node. Object ID 2,
> > text, ntext, or
> > >image node page (1:14296), slot 3, text ID 246486007808
> > is pointed to by
> > >page (1:2028), slot 23 and by page (1:8421), slot 2.
> > >
> > >Server: Msg 8964, Level 16, State 1, Line 1
> > >
> > >Table error: Object ID 2. The text, ntext, or image node
> > at page (1:14378),
> > >slot 1, text ID 234646863872 is not referenced.
> > >
> > >Server: Msg 8961, Level 16, State 1, Line 1
> > >
> > >Table error: Object ID 2. The text, ntext, or image node
> > at page (1:22060),
> > >slot 4, text ID 246504488960 does not match its reference
> > from page
> > >(1:2531), slot 5.
> > >
> > >Server: Msg 8974, Level 16, State 1, Line 1
> > >
> > >Text node referenced by more than one node. Object ID 2,
> > text, ntext, or
> > >image node page (1:22060), slot 4, text ID 246504488960
> > is pointed to by
> > >page (1:2531), slot 5 and by page (1:7431), slot 20.
> > >
> > >DBCC results for 'sunrise'.
> > >
> > >DBCC results for 'sysobjects'.
> > >
> > >There are 24482 rows in 435 pages for object 'sysobjects'.
> > >
> > >DBCC results for 'sysindexes'.
> > >
> > >There are 2652 rows in 155 pages for object 'sysindexes'.
> > >
> > >CHECKDB found 0 allocation errors and 9 consistency
> > errors in table
> > >'sysindexes' (object ID 2).
> > >
> > >
> > >.
> > >
>|||Thank you very much. Can you tell me what this means? I have never seen
errors like this on a table.
Table error: Object ID 2. The text, ntext, or image node at page (1:22060),
slot 4, text ID 246504488960 does not match its reference from page
(1:2531), slot 5.
"Barry McAuslin" <barry_mcauslin@.yahoo.com.nospam> wrote in message
news:eipens$lDHA.1676@.TK2MSFTNGP09.phx.gbl...
> To find the index name use the following query in you database.
> select name from dbo.sysindexes
> where id = 194502355 and indid = 3
> The example above will find the index in the first error.
> HTH
> --
> Barry McAuslin
> Look inside your SQL Server files with SQL File Explorer.
> Go to http://www.sqlfe.com for more information.
> "Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com> wrote
> in message news:uRhM7g$lDHA.2000@.TK2MSFTNGP12.phx.gbl...
> > This database has over 900 tables. Is there any way to know which
table's
> > indexes are the problem? Or to rebuild all of the indexes in the
> database?
> >
> >
> > "harvinder" <hs@.metratech.com> wrote in message
> > news:0c6301c397eb$fcfeeda0$a501280a@.phx.gbl...
> > > most of the appear to belong to index...so better way
> > > will be to recreate the corrupted indexes and run dbcc
> > > checkdb again
> > >
> > > Thanks
> > > --Harvinder
> > >
> > > >--Original Message--
> > > >We are trying to do some automated weekly optimization
> > > processes on a SQL
> > > >2000 Server and have had some errors returned when we do
> > > a DBCC CheckDB.
> > > >I've posted those below. We then tried DBCC CHECKDB
> > > repair_allow_data_loss
> > > >which returns a message that says that it found 9 errors
> > > and repaired 0.
> > > >
> > > >Can anyone help me determine what kind of errors these
> > > are and how they
> > > >might be fixed?
> > > >
> > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > >
> > > >Object ID 2: Errors found in text ID 231654031360 owned
> > > by data record
> > > >identified by RID = (1:2026:23) id = 194502355 and indid
> > > = 3.
> > > >
> > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > >
> > > >Object ID 2: Errors found in text ID 234646667264 owned
> > > by data record
> > > >identified by RID = (1:2026:24) id = 194502355 and indid
> > > = 4.
> > > >
> > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > >
> > > >Object ID 2: Errors found in text ID 246486007808 owned
> > > by data record
> > > >identified by RID = (1:2028:23) id = 469576711 and indid
> > > = 7.
> > > >
> > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > >
> > > >Object ID 2: Errors found in text ID 246504488960 owned
> > > by data record
> > > >identified by RID = (1:7431:20) id = 805577908 and indid
> > > = 30.
> > > >
> > > >Server: Msg 8961, Level 16, State 1, Line 1
> > > >
> > > >Table error: Object ID 2. The text, ntext, or image node
> > > at page (1:14296),
> > > >slot 3, text ID 246486007808 does not match its reference
> > > from page
> > > >(1:8421), slot 2.
> > > >
> > > >Server: Msg 8974, Level 16, State 1, Line 1
> > > >
> > > >Text node referenced by more than one node. Object ID 2,
> > > text, ntext, or
> > > >image node page (1:14296), slot 3, text ID 246486007808
> > > is pointed to by
> > > >page (1:2028), slot 23 and by page (1:8421), slot 2.
> > > >
> > > >Server: Msg 8964, Level 16, State 1, Line 1
> > > >
> > > >Table error: Object ID 2. The text, ntext, or image node
> > > at page (1:14378),
> > > >slot 1, text ID 234646863872 is not referenced.
> > > >
> > > >Server: Msg 8961, Level 16, State 1, Line 1
> > > >
> > > >Table error: Object ID 2. The text, ntext, or image node
> > > at page (1:22060),
> > > >slot 4, text ID 246504488960 does not match its reference
> > > from page
> > > >(1:2531), slot 5.
> > > >
> > > >Server: Msg 8974, Level 16, State 1, Line 1
> > > >
> > > >Text node referenced by more than one node. Object ID 2,
> > > text, ntext, or
> > > >image node page (1:22060), slot 4, text ID 246504488960
> > > is pointed to by
> > > >page (1:2531), slot 5 and by page (1:7431), slot 20.
> > > >
> > > >DBCC results for 'sunrise'.
> > > >
> > > >DBCC results for 'sysobjects'.
> > > >
> > > >There are 24482 rows in 435 pages for object 'sysobjects'.
> > > >
> > > >DBCC results for 'sysindexes'.
> > > >
> > > >There are 2652 rows in 155 pages for object 'sysindexes'.
> > > >
> > > >CHECKDB found 0 allocation errors and 9 consistency
> > > errors in table
> > > >'sysindexes' (object ID 2).
> > > >
> > > >
> > > >.
> > > >
> >
> >
>|||Basically you have some kind of database corruption.
A table with an image column in it (sysindexes in this case) which has a
reference to an image blob (in this case the column statblob, which is for
index statistics). The location it is pointing to is owned by another
object.
I would first try
DBCC CHECKDB ( 'database_name' REPAIR_ALLOW_DATA_LOSS )
I would not worry about the data loss as all you problems a with the
statblob column in the sysindexs table. This data can be recreated by the
DB maintenance wizard.
Then run the DB maintenance plan for updating your statistics and see what
happens.
If this does not fix the problem then I guess your only solution is to
create a new database, script all objects, and copy all data.
Hope this helps
--
Barry McAuslin
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com> wrote
in message news:OuDI3WAmDHA.2732@.TK2MSFTNGP11.phx.gbl...
> Thank you very much. Can you tell me what this means? I have never seen
> errors like this on a table.
> Table error: Object ID 2. The text, ntext, or image node at page
(1:22060),
> slot 4, text ID 246504488960 does not match its reference from page
> (1:2531), slot 5.
> "Barry McAuslin" <barry_mcauslin@.yahoo.com.nospam> wrote in message
> news:eipens$lDHA.1676@.TK2MSFTNGP09.phx.gbl...
> > To find the index name use the following query in you database.
> >
> > select name from dbo.sysindexes
> > where id = 194502355 and indid = 3
> >
> > The example above will find the index in the first error.
> >
> > HTH
> >
> > --
> >
> > Barry McAuslin
> >
> > Look inside your SQL Server files with SQL File Explorer.
> > Go to http://www.sqlfe.com for more information.
> >
> > "Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com>
wrote
> > in message news:uRhM7g$lDHA.2000@.TK2MSFTNGP12.phx.gbl...
> > > This database has over 900 tables. Is there any way to know which
> table's
> > > indexes are the problem? Or to rebuild all of the indexes in the
> > database?
> > >
> > >
> > > "harvinder" <hs@.metratech.com> wrote in message
> > > news:0c6301c397eb$fcfeeda0$a501280a@.phx.gbl...
> > > > most of the appear to belong to index...so better way
> > > > will be to recreate the corrupted indexes and run dbcc
> > > > checkdb again
> > > >
> > > > Thanks
> > > > --Harvinder
> > > >
> > > > >--Original Message--
> > > > >We are trying to do some automated weekly optimization
> > > > processes on a SQL
> > > > >2000 Server and have had some errors returned when we do
> > > > a DBCC CheckDB.
> > > > >I've posted those below. We then tried DBCC CHECKDB
> > > > repair_allow_data_loss
> > > > >which returns a message that says that it found 9 errors
> > > > and repaired 0.
> > > > >
> > > > >Can anyone help me determine what kind of errors these
> > > > are and how they
> > > > >might be fixed?
> > > > >
> > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > >
> > > > >Object ID 2: Errors found in text ID 231654031360 owned
> > > > by data record
> > > > >identified by RID = (1:2026:23) id = 194502355 and indid
> > > > = 3.
> > > > >
> > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > >
> > > > >Object ID 2: Errors found in text ID 234646667264 owned
> > > > by data record
> > > > >identified by RID = (1:2026:24) id = 194502355 and indid
> > > > = 4.
> > > > >
> > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > >
> > > > >Object ID 2: Errors found in text ID 246486007808 owned
> > > > by data record
> > > > >identified by RID = (1:2028:23) id = 469576711 and indid
> > > > = 7.
> > > > >
> > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > >
> > > > >Object ID 2: Errors found in text ID 246504488960 owned
> > > > by data record
> > > > >identified by RID = (1:7431:20) id = 805577908 and indid
> > > > = 30.
> > > > >
> > > > >Server: Msg 8961, Level 16, State 1, Line 1
> > > > >
> > > > >Table error: Object ID 2. The text, ntext, or image node
> > > > at page (1:14296),
> > > > >slot 3, text ID 246486007808 does not match its reference
> > > > from page
> > > > >(1:8421), slot 2.
> > > > >
> > > > >Server: Msg 8974, Level 16, State 1, Line 1
> > > > >
> > > > >Text node referenced by more than one node. Object ID 2,
> > > > text, ntext, or
> > > > >image node page (1:14296), slot 3, text ID 246486007808
> > > > is pointed to by
> > > > >page (1:2028), slot 23 and by page (1:8421), slot 2.
> > > > >
> > > > >Server: Msg 8964, Level 16, State 1, Line 1
> > > > >
> > > > >Table error: Object ID 2. The text, ntext, or image node
> > > > at page (1:14378),
> > > > >slot 1, text ID 234646863872 is not referenced.
> > > > >
> > > > >Server: Msg 8961, Level 16, State 1, Line 1
> > > > >
> > > > >Table error: Object ID 2. The text, ntext, or image node
> > > > at page (1:22060),
> > > > >slot 4, text ID 246504488960 does not match its reference
> > > > from page
> > > > >(1:2531), slot 5.
> > > > >
> > > > >Server: Msg 8974, Level 16, State 1, Line 1
> > > > >
> > > > >Text node referenced by more than one node. Object ID 2,
> > > > text, ntext, or
> > > > >image node page (1:22060), slot 4, text ID 246504488960
> > > > is pointed to by
> > > > >page (1:2531), slot 5 and by page (1:7431), slot 20.
> > > > >
> > > > >DBCC results for 'sunrise'.
> > > > >
> > > > >DBCC results for 'sysobjects'.
> > > > >
> > > > >There are 24482 rows in 435 pages for object 'sysobjects'.
> > > > >
> > > > >DBCC results for 'sysindexes'.
> > > > >
> > > > >There are 2652 rows in 155 pages for object 'sysindexes'.
> > > > >
> > > > >CHECKDB found 0 allocation errors and 9 consistency
> > > > errors in table
> > > > >'sysindexes' (object ID 2).
> > > > >
> > > > >
> > > > >.
> > > > >
> > >
> > >
> >
> >
>|||Yes.
--
Barry McAuslin
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com> wrote
in message news:uZHO3k%23lDHA.744@.tk2msftngp13.phx.gbl...
> The latest backup was made after these messages were created. Wouldn't
> these errors still exist after restoring?
>
> "Stressed" <k@.c.co.uk> wrote in message
> news:Odykkb%23lDHA.988@.TK2MSFTNGP10.phx.gbl...
> > At a guess, if sql server is unable to repair the database (even with
data
> > loss,
> > if that is acceptable to you), you will need to restore from your latest
> > backup.
> >
> > Verify this before taking any action though
> >
> >
> > "Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com>
wrote
> > in message news:eBh7qp9lDHA.2732@.TK2MSFTNGP11.phx.gbl...
> > > We are trying to do some automated weekly optimization processes on a
> SQL
> > > 2000 Server and have had some errors returned when we do a DBCC
CheckDB.
> > > I've posted those below. We then tried DBCC CHECKDB
> > repair_allow_data_loss
> > > which returns a message that says that it found 9 errors and repaired
0.
> > >
> > > Can anyone help me determine what kind of errors these are and how
they
> > > might be fixed?
> > >
> > > Server: Msg 8929, Level 16, State 1, Line 1
> > >
> > > Object ID 2: Errors found in text ID 231654031360 owned by data record
> > > identified by RID = (1:2026:23) id = 194502355 and indid = 3.
> > >
> > > Server: Msg 8929, Level 16, State 1, Line 1
> > >
> > > Object ID 2: Errors found in text ID 234646667264 owned by data record
> > > identified by RID = (1:2026:24) id = 194502355 and indid = 4.
> > >
> > > Server: Msg 8929, Level 16, State 1, Line 1
> > >
> > > Object ID 2: Errors found in text ID 246486007808 owned by data record
> > > identified by RID = (1:2028:23) id = 469576711 and indid = 7.
> > >
> > > Server: Msg 8929, Level 16, State 1, Line 1
> > >
> > > Object ID 2: Errors found in text ID 246504488960 owned by data record
> > > identified by RID = (1:7431:20) id = 805577908 and indid = 30.
> > >
> > > Server: Msg 8961, Level 16, State 1, Line 1
> > >
> > > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:14296),
> > > slot 3, text ID 246486007808 does not match its reference from page
> > > (1:8421), slot 2.
> > >
> > > Server: Msg 8974, Level 16, State 1, Line 1
> > >
> > > Text node referenced by more than one node. Object ID 2, text, ntext,
or
> > > image node page (1:14296), slot 3, text ID 246486007808 is pointed to
by
> > > page (1:2028), slot 23 and by page (1:8421), slot 2.
> > >
> > > Server: Msg 8964, Level 16, State 1, Line 1
> > >
> > > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:14378),
> > > slot 1, text ID 234646863872 is not referenced.
> > >
> > > Server: Msg 8961, Level 16, State 1, Line 1
> > >
> > > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:22060),
> > > slot 4, text ID 246504488960 does not match its reference from page
> > > (1:2531), slot 5.
> > >
> > > Server: Msg 8974, Level 16, State 1, Line 1
> > >
> > > Text node referenced by more than one node. Object ID 2, text, ntext,
or
> > > image node page (1:22060), slot 4, text ID 246504488960 is pointed to
by
> > > page (1:2531), slot 5 and by page (1:7431), slot 20.
> > >
> > > DBCC results for 'sunrise'.
> > >
> > > DBCC results for 'sysobjects'.
> > >
> > > There are 24482 rows in 435 pages for object 'sysobjects'.
> > >
> > > DBCC results for 'sysindexes'.
> > >
> > > There are 2652 rows in 155 pages for object 'sysindexes'.
> > >
> > > CHECKDB found 0 allocation errors and 9 consistency errors in table
> > > 'sysindexes' (object ID 2).
> > >
> > >
> >
> >
>|||... so that should be restated as "the latest clean backup". However, you can re-apply your
transaction log backups. The corruption will likely not re-appear when you apply a transaction log
backup taken after the corruption occurred in the original db.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Barry McAuslin" <barry_mcauslin@.yahoo.com.nospam> wrote in message
news:uznbxyFmDHA.2772@.TK2MSFTNGP10.phx.gbl...
> Yes.
> --
> Barry McAuslin
> Look inside your SQL Server files with SQL File Explorer.
> Go to http://www.sqlfe.com for more information.
> "Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com> wrote
> in message news:uZHO3k%23lDHA.744@.tk2msftngp13.phx.gbl...
> > The latest backup was made after these messages were created. Wouldn't
> > these errors still exist after restoring?
> >
> >
> > "Stressed" <k@.c.co.uk> wrote in message
> > news:Odykkb%23lDHA.988@.TK2MSFTNGP10.phx.gbl...
> > > At a guess, if sql server is unable to repair the database (even with
> data
> > > loss,
> > > if that is acceptable to you), you will need to restore from your latest
> > > backup.
> > >
> > > Verify this before taking any action though
> > >
> > >
> > > "Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com>
> wrote
> > > in message news:eBh7qp9lDHA.2732@.TK2MSFTNGP11.phx.gbl...
> > > > We are trying to do some automated weekly optimization processes on a
> > SQL
> > > > 2000 Server and have had some errors returned when we do a DBCC
> CheckDB.
> > > > I've posted those below. We then tried DBCC CHECKDB
> > > repair_allow_data_loss
> > > > which returns a message that says that it found 9 errors and repaired
> 0.
> > > >
> > > > Can anyone help me determine what kind of errors these are and how
> they
> > > > might be fixed?
> > > >
> > > > Server: Msg 8929, Level 16, State 1, Line 1
> > > >
> > > > Object ID 2: Errors found in text ID 231654031360 owned by data record
> > > > identified by RID = (1:2026:23) id = 194502355 and indid = 3.
> > > >
> > > > Server: Msg 8929, Level 16, State 1, Line 1
> > > >
> > > > Object ID 2: Errors found in text ID 234646667264 owned by data record
> > > > identified by RID = (1:2026:24) id = 194502355 and indid = 4.
> > > >
> > > > Server: Msg 8929, Level 16, State 1, Line 1
> > > >
> > > > Object ID 2: Errors found in text ID 246486007808 owned by data record
> > > > identified by RID = (1:2028:23) id = 469576711 and indid = 7.
> > > >
> > > > Server: Msg 8929, Level 16, State 1, Line 1
> > > >
> > > > Object ID 2: Errors found in text ID 246504488960 owned by data record
> > > > identified by RID = (1:7431:20) id = 805577908 and indid = 30.
> > > >
> > > > Server: Msg 8961, Level 16, State 1, Line 1
> > > >
> > > > Table error: Object ID 2. The text, ntext, or image node at page
> > > (1:14296),
> > > > slot 3, text ID 246486007808 does not match its reference from page
> > > > (1:8421), slot 2.
> > > >
> > > > Server: Msg 8974, Level 16, State 1, Line 1
> > > >
> > > > Text node referenced by more than one node. Object ID 2, text, ntext,
> or
> > > > image node page (1:14296), slot 3, text ID 246486007808 is pointed to
> by
> > > > page (1:2028), slot 23 and by page (1:8421), slot 2.
> > > >
> > > > Server: Msg 8964, Level 16, State 1, Line 1
> > > >
> > > > Table error: Object ID 2. The text, ntext, or image node at page
> > > (1:14378),
> > > > slot 1, text ID 234646863872 is not referenced.
> > > >
> > > > Server: Msg 8961, Level 16, State 1, Line 1
> > > >
> > > > Table error: Object ID 2. The text, ntext, or image node at page
> > > (1:22060),
> > > > slot 4, text ID 246504488960 does not match its reference from page
> > > > (1:2531), slot 5.
> > > >
> > > > Server: Msg 8974, Level 16, State 1, Line 1
> > > >
> > > > Text node referenced by more than one node. Object ID 2, text, ntext,
> or
> > > > image node page (1:22060), slot 4, text ID 246504488960 is pointed to
> by
> > > > page (1:2531), slot 5 and by page (1:7431), slot 20.
> > > >
> > > > DBCC results for 'sunrise'.
> > > >
> > > > DBCC results for 'sysobjects'.
> > > >
> > > > There are 24482 rows in 435 pages for object 'sysobjects'.
> > > >
> > > > DBCC results for 'sysindexes'.
> > > >
> > > > There are 2652 rows in 155 pages for object 'sysindexes'.
> > > >
> > > > CHECKDB found 0 allocation errors and 9 consistency errors in table
> > > > 'sysindexes' (object ID 2).
> > > >
> > > >
> > >
> > >
> >
> >
>|||Barry,
The OP stated that allow_data_loss was already tried :-(...
Deborah,
I'd go for the restore route. See my other post regarding restoring transaction log backups.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Barry McAuslin" <barry_mcauslin@.yahoo.com.nospam> wrote in message
news:%23JOayyFmDHA.2772@.TK2MSFTNGP10.phx.gbl...
> Basically you have some kind of database corruption.
> A table with an image column in it (sysindexes in this case) which has a
> reference to an image blob (in this case the column statblob, which is for
> index statistics). The location it is pointing to is owned by another
> object.
> I would first try
> DBCC CHECKDB ( 'database_name' REPAIR_ALLOW_DATA_LOSS )
> I would not worry about the data loss as all you problems a with the
> statblob column in the sysindexs table. This data can be recreated by the
> DB maintenance wizard.
> Then run the DB maintenance plan for updating your statistics and see what
> happens.
> If this does not fix the problem then I guess your only solution is to
> create a new database, script all objects, and copy all data.
> Hope this helps
> --
> Barry McAuslin
> Look inside your SQL Server files with SQL File Explorer.
> Go to http://www.sqlfe.com for more information.
> "Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com> wrote
> in message news:OuDI3WAmDHA.2732@.TK2MSFTNGP11.phx.gbl...
> > Thank you very much. Can you tell me what this means? I have never seen
> > errors like this on a table.
> >
> > Table error: Object ID 2. The text, ntext, or image node at page
> (1:22060),
> > slot 4, text ID 246504488960 does not match its reference from page
> > (1:2531), slot 5.
> >
> > "Barry McAuslin" <barry_mcauslin@.yahoo.com.nospam> wrote in message
> > news:eipens$lDHA.1676@.TK2MSFTNGP09.phx.gbl...
> > > To find the index name use the following query in you database.
> > >
> > > select name from dbo.sysindexes
> > > where id = 194502355 and indid = 3
> > >
> > > The example above will find the index in the first error.
> > >
> > > HTH
> > >
> > > --
> > >
> > > Barry McAuslin
> > >
> > > Look inside your SQL Server files with SQL File Explorer.
> > > Go to http://www.sqlfe.com for more information.
> > >
> > > "Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com>
> wrote
> > > in message news:uRhM7g$lDHA.2000@.TK2MSFTNGP12.phx.gbl...
> > > > This database has over 900 tables. Is there any way to know which
> > table's
> > > > indexes are the problem? Or to rebuild all of the indexes in the
> > > database?
> > > >
> > > >
> > > > "harvinder" <hs@.metratech.com> wrote in message
> > > > news:0c6301c397eb$fcfeeda0$a501280a@.phx.gbl...
> > > > > most of the appear to belong to index...so better way
> > > > > will be to recreate the corrupted indexes and run dbcc
> > > > > checkdb again
> > > > >
> > > > > Thanks
> > > > > --Harvinder
> > > > >
> > > > > >--Original Message--
> > > > > >We are trying to do some automated weekly optimization
> > > > > processes on a SQL
> > > > > >2000 Server and have had some errors returned when we do
> > > > > a DBCC CheckDB.
> > > > > >I've posted those below. We then tried DBCC CHECKDB
> > > > > repair_allow_data_loss
> > > > > >which returns a message that says that it found 9 errors
> > > > > and repaired 0.
> > > > > >
> > > > > >Can anyone help me determine what kind of errors these
> > > > > are and how they
> > > > > >might be fixed?
> > > > > >
> > > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > > >
> > > > > >Object ID 2: Errors found in text ID 231654031360 owned
> > > > > by data record
> > > > > >identified by RID = (1:2026:23) id = 194502355 and indid
> > > > > = 3.
> > > > > >
> > > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > > >
> > > > > >Object ID 2: Errors found in text ID 234646667264 owned
> > > > > by data record
> > > > > >identified by RID = (1:2026:24) id = 194502355 and indid
> > > > > = 4.
> > > > > >
> > > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > > >
> > > > > >Object ID 2: Errors found in text ID 246486007808 owned
> > > > > by data record
> > > > > >identified by RID = (1:2028:23) id = 469576711 and indid
> > > > > = 7.
> > > > > >
> > > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > > >
> > > > > >Object ID 2: Errors found in text ID 246504488960 owned
> > > > > by data record
> > > > > >identified by RID = (1:7431:20) id = 805577908 and indid
> > > > > = 30.
> > > > > >
> > > > > >Server: Msg 8961, Level 16, State 1, Line 1
> > > > > >
> > > > > >Table error: Object ID 2. The text, ntext, or image node
> > > > > at page (1:14296),
> > > > > >slot 3, text ID 246486007808 does not match its reference
> > > > > from page
> > > > > >(1:8421), slot 2.
> > > > > >
> > > > > >Server: Msg 8974, Level 16, State 1, Line 1
> > > > > >
> > > > > >Text node referenced by more than one node. Object ID 2,
> > > > > text, ntext, or
> > > > > >image node page (1:14296), slot 3, text ID 246486007808
> > > > > is pointed to by
> > > > > >page (1:2028), slot 23 and by page (1:8421), slot 2.
> > > > > >
> > > > > >Server: Msg 8964, Level 16, State 1, Line 1
> > > > > >
> > > > > >Table error: Object ID 2. The text, ntext, or image node
> > > > > at page (1:14378),
> > > > > >slot 1, text ID 234646863872 is not referenced.
> > > > > >
> > > > > >Server: Msg 8961, Level 16, State 1, Line 1
> > > > > >
> > > > > >Table error: Object ID 2. The text, ntext, or image node
> > > > > at page (1:22060),
> > > > > >slot 4, text ID 246504488960 does not match its reference
> > > > > from page
> > > > > >(1:2531), slot 5.
> > > > > >
> > > > > >Server: Msg 8974, Level 16, State 1, Line 1
> > > > > >
> > > > > >Text node referenced by more than one node. Object ID 2,
> > > > > text, ntext, or
> > > > > >image node page (1:22060), slot 4, text ID 246504488960
> > > > > is pointed to by
> > > > > >page (1:2531), slot 5 and by page (1:7431), slot 20.
> > > > > >
> > > > > >DBCC results for 'sunrise'.
> > > > > >
> > > > > >DBCC results for 'sysobjects'.
> > > > > >
> > > > > >There are 24482 rows in 435 pages for object 'sysobjects'.
> > > > > >
> > > > > >DBCC results for 'sysindexes'.
> > > > > >
> > > > > >There are 2652 rows in 155 pages for object 'sysindexes'.
> > > > > >
> > > > > >CHECKDB found 0 allocation errors and 9 consistency
> > > > > errors in table
> > > > > >'sysindexes' (object ID 2).
> > > > > >
> > > > > >
> > > > > >.
> > > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Thank you Tibor. I appreciate all the responses.
I've been told that a couple of weeks ago, there was some corruption to the
RAID array and a new one was installed. I believe that some of these
problems began then. I also found out that the version of SQL on the box
was the RTM version, no service packs. (This is not one of my servers; I
provide support as needed to their support people.)
I've passed on the advice given here. They've already tried scripting the
objects in the database for possible data export. However, the script
process runs about 20 minutes and then just hangs without finishing. I
believe that they are going to go with restoring the last known clean backup
and then applying all the transaction logs since then. I will post here
with an update on the results.
Thanks again,
Deborah
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:eZksgTGmDHA.372@.TK2MSFTNGP11.phx.gbl...
> Barry,
> The OP stated that allow_data_loss was already tried :-(...
>
> Deborah,
> I'd go for the restore route. See my other post regarding restoring
transaction log backups.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Barry McAuslin" <barry_mcauslin@.yahoo.com.nospam> wrote in message
> news:%23JOayyFmDHA.2772@.TK2MSFTNGP10.phx.gbl...
> > Basically you have some kind of database corruption.
> >
> > A table with an image column in it (sysindexes in this case) which has a
> > reference to an image blob (in this case the column statblob, which is
for
> > index statistics). The location it is pointing to is owned by another
> > object.
> >
> > I would first try
> >
> > DBCC CHECKDB ( 'database_name' REPAIR_ALLOW_DATA_LOSS )
> >
> > I would not worry about the data loss as all you problems a with the
> > statblob column in the sysindexs table. This data can be recreated by
the
> > DB maintenance wizard.
> >
> > Then run the DB maintenance plan for updating your statistics and see
what
> > happens.
> >
> > If this does not fix the problem then I guess your only solution is to
> > create a new database, script all objects, and copy all data.
> >
> > Hope this helps
> >
> > --
> >
> > Barry McAuslin
> >
> > Look inside your SQL Server files with SQL File Explorer.
> > Go to http://www.sqlfe.com for more information.
> >
> > "Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com>
wrote
> > in message news:OuDI3WAmDHA.2732@.TK2MSFTNGP11.phx.gbl...
> > > Thank you very much. Can you tell me what this means? I have never
seen
> > > errors like this on a table.
> > >
> > > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:22060),
> > > slot 4, text ID 246504488960 does not match its reference from page
> > > (1:2531), slot 5.
> > >
> > > "Barry McAuslin" <barry_mcauslin@.yahoo.com.nospam> wrote in message
> > > news:eipens$lDHA.1676@.TK2MSFTNGP09.phx.gbl...
> > > > To find the index name use the following query in you database.
> > > >
> > > > select name from dbo.sysindexes
> > > > where id = 194502355 and indid = 3
> > > >
> > > > The example above will find the index in the first error.
> > > >
> > > > HTH
> > > >
> > > > --
> > > >
> > > > Barry McAuslin
> > > >
> > > > Look inside your SQL Server files with SQL File Explorer.
> > > > Go to http://www.sqlfe.com for more information.
> > > >
> > > > "Deborah Bohannon" <dbohannon@.nationalDONOTSENDHEREcareanetwork.com>
> > wrote
> > > > in message news:uRhM7g$lDHA.2000@.TK2MSFTNGP12.phx.gbl...
> > > > > This database has over 900 tables. Is there any way to know which
> > > table's
> > > > > indexes are the problem? Or to rebuild all of the indexes in the
> > > > database?
> > > > >
> > > > >
> > > > > "harvinder" <hs@.metratech.com> wrote in message
> > > > > news:0c6301c397eb$fcfeeda0$a501280a@.phx.gbl...
> > > > > > most of the appear to belong to index...so better way
> > > > > > will be to recreate the corrupted indexes and run dbcc
> > > > > > checkdb again
> > > > > >
> > > > > > Thanks
> > > > > > --Harvinder
> > > > > >
> > > > > > >--Original Message--
> > > > > > >We are trying to do some automated weekly optimization
> > > > > > processes on a SQL
> > > > > > >2000 Server and have had some errors returned when we do
> > > > > > a DBCC CheckDB.
> > > > > > >I've posted those below. We then tried DBCC CHECKDB
> > > > > > repair_allow_data_loss
> > > > > > >which returns a message that says that it found 9 errors
> > > > > > and repaired 0.
> > > > > > >
> > > > > > >Can anyone help me determine what kind of errors these
> > > > > > are and how they
> > > > > > >might be fixed?
> > > > > > >
> > > > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > > > >
> > > > > > >Object ID 2: Errors found in text ID 231654031360 owned
> > > > > > by data record
> > > > > > >identified by RID = (1:2026:23) id = 194502355 and indid
> > > > > > = 3.
> > > > > > >
> > > > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > > > >
> > > > > > >Object ID 2: Errors found in text ID 234646667264 owned
> > > > > > by data record
> > > > > > >identified by RID = (1:2026:24) id = 194502355 and indid
> > > > > > = 4.
> > > > > > >
> > > > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > > > >
> > > > > > >Object ID 2: Errors found in text ID 246486007808 owned
> > > > > > by data record
> > > > > > >identified by RID = (1:2028:23) id = 469576711 and indid
> > > > > > = 7.
> > > > > > >
> > > > > > >Server: Msg 8929, Level 16, State 1, Line 1
> > > > > > >
> > > > > > >Object ID 2: Errors found in text ID 246504488960 owned
> > > > > > by data record
> > > > > > >identified by RID = (1:7431:20) id = 805577908 and indid
> > > > > > = 30.
> > > > > > >
> > > > > > >Server: Msg 8961, Level 16, State 1, Line 1
> > > > > > >
> > > > > > >Table error: Object ID 2. The text, ntext, or image node
> > > > > > at page (1:14296),
> > > > > > >slot 3, text ID 246486007808 does not match its reference
> > > > > > from page
> > > > > > >(1:8421), slot 2.
> > > > > > >
> > > > > > >Server: Msg 8974, Level 16, State 1, Line 1
> > > > > > >
> > > > > > >Text node referenced by more than one node. Object ID 2,
> > > > > > text, ntext, or
> > > > > > >image node page (1:14296), slot 3, text ID 246486007808
> > > > > > is pointed to by
> > > > > > >page (1:2028), slot 23 and by page (1:8421), slot 2.
> > > > > > >
> > > > > > >Server: Msg 8964, Level 16, State 1, Line 1
> > > > > > >
> > > > > > >Table error: Object ID 2. The text, ntext, or image node
> > > > > > at page (1:14378),
> > > > > > >slot 1, text ID 234646863872 is not referenced.
> > > > > > >
> > > > > > >Server: Msg 8961, Level 16, State 1, Line 1
> > > > > > >
> > > > > > >Table error: Object ID 2. The text, ntext, or image node
> > > > > > at page (1:22060),
> > > > > > >slot 4, text ID 246504488960 does not match its reference
> > > > > > from page
> > > > > > >(1:2531), slot 5.
> > > > > > >
> > > > > > >Server: Msg 8974, Level 16, State 1, Line 1
> > > > > > >
> > > > > > >Text node referenced by more than one node. Object ID 2,
> > > > > > text, ntext, or
> > > > > > >image node page (1:22060), slot 4, text ID 246504488960
> > > > > > is pointed to by
> > > > > > >page (1:2531), slot 5 and by page (1:7431), slot 20.
> > > > > > >
> > > > > > >DBCC results for 'sunrise'.
> > > > > > >
> > > > > > >DBCC results for 'sysobjects'.
> > > > > > >
> > > > > > >There are 24482 rows in 435 pages for object 'sysobjects'.
> > > > > > >
> > > > > > >DBCC results for 'sysindexes'.
> > > > > > >
> > > > > > >There are 2652 rows in 155 pages for object 'sysindexes'.
> > > > > > >
> > > > > > >CHECKDB found 0 allocation errors and 9 consistency
> > > > > > errors in table
> > > > > > >'sysindexes' (object ID 2).
> > > > > > >
> > > > > > >
> > > > > > >.
> > > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>

DBCC Problems with syscolumns

Hi, I have run a DBCC CHECKDB and it found 2 Errors in syscolumns. I
have run a CHECKTABLE and found the following Error:
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 3, index ID 2: Page (1:266) could not be processed. See other
errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 3, index ID 2, page (1:266), row 12. Test
(VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <=
(nextRec - pRec)) failed. Values are 178 and 72.
DBCC results for 'syscolumns'.
There are 6963 rows in 144 pages for object 'syscolumns'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table
'syscolumns' (object ID 3).
repair_allow_data_loss is the minimum repair level for the errors found
by DBCC CHECKTABLE (EMIS.dbo.syscolumns ).
Can anyone suggest the best way to proceed with this problem. I am a
little dubious about running REPAIR_ALLOW_DATALOSS on syscolumns, I am
unsure of what will happen if sections of syscolumns go missing. I have
run DBCC PAGE ('EMIS',1,266,1) but this has given me nothing to work
with.
Thanks in Advance,
Dave Shaw.Normally i would suggest DBREINDEX but as this is a system table you're not
allowed.
Give SP_FixIndex a try. You will need the DB in single user mode 1st.
"Dave Shaw" <Dave.Shaw1584@.NTLWorld.com> wrote in message
news:1134990883.398840.145620@.z14g2000cwz.googlegroups.com...
> Hi, I have run a DBCC CHECKDB and it found 2 Errors in syscolumns. I
> have run a CHECKTABLE and found the following Error:
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 3, index ID 2: Page (1:266) could not be processed. See other
> errors for details.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 3, index ID 2, page (1:266), row 12. Test
> (VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <=
> (nextRec - pRec)) failed. Values are 178 and 72.
> DBCC results for 'syscolumns'.
> There are 6963 rows in 144 pages for object 'syscolumns'.
> CHECKTABLE found 0 allocation errors and 2 consistency errors in table
> 'syscolumns' (object ID 3).
> repair_allow_data_loss is the minimum repair level for the errors found
> by DBCC CHECKTABLE (EMIS.dbo.syscolumns ).
> Can anyone suggest the best way to proceed with this problem. I am a
> little dubious about running REPAIR_ALLOW_DATALOSS on syscolumns, I am
> unsure of what will happen if sections of syscolumns go missing. I have
> run DBCC PAGE ('EMIS',1,266,1) but this has given me nothing to work
> with.
> Thanks in Advance,
> Dave Shaw.
>|||This article may help ...
http://www.windows2000faq.com/Artic...ArticleID=14051
"John Smith" <fsfsdf@.microsoft.com> wrote in message
news:enUNTKJBGHA.3872@.TK2MSFTNGP12.phx.gbl...
> Normally i would suggest DBREINDEX but as this is a system table you're
not
> allowed.
> Give SP_FixIndex a try. You will need the DB in single user mode 1st.
>
> "Dave Shaw" <Dave.Shaw1584@.NTLWorld.com> wrote in message
> news:1134990883.398840.145620@.z14g2000cwz.googlegroups.com...
>|||Thanks John Smith.
I shall give this a try.
Dave.

DBCC Problems with syscolumns

Hi, I have run a DBCC CHECKDB and it found 2 Errors in syscolumns. I
have run a CHECKTABLE and found the following Error:
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 3, index ID 2: Page (1:266) could not be processed. See other
errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 3, index ID 2, page (1:266), row 12. Test
(VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <=
(nextRec - pRec)) failed. Values are 178 and 72.
DBCC results for 'syscolumns'.
There are 6963 rows in 144 pages for object 'syscolumns'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table
'syscolumns' (object ID 3).
repair_allow_data_loss is the minimum repair level for the errors found
by DBCC CHECKTABLE (EMIS.dbo.syscolumns ).
Can anyone suggest the best way to proceed with this problem. I am a
little dubious about running REPAIR_ALLOW_DATALOSS on syscolumns, I am
unsure of what will happen if sections of syscolumns go missing. I have
run DBCC PAGE ('EMIS',1,266,1) but this has given me nothing to work
with.
Thanks in Advance,
Dave Shaw.
Normally i would suggest DBREINDEX but as this is a system table you're not
allowed.
Give SP_FixIndex a try. You will need the DB in single user mode 1st.
"Dave Shaw" <Dave.Shaw1584@.NTLWorld.com> wrote in message
news:1134990883.398840.145620@.z14g2000cwz.googlegr oups.com...
> Hi, I have run a DBCC CHECKDB and it found 2 Errors in syscolumns. I
> have run a CHECKTABLE and found the following Error:
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 3, index ID 2: Page (1:266) could not be processed. See other
> errors for details.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 3, index ID 2, page (1:266), row 12. Test
> (VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <=
> (nextRec - pRec)) failed. Values are 178 and 72.
> DBCC results for 'syscolumns'.
> There are 6963 rows in 144 pages for object 'syscolumns'.
> CHECKTABLE found 0 allocation errors and 2 consistency errors in table
> 'syscolumns' (object ID 3).
> repair_allow_data_loss is the minimum repair level for the errors found
> by DBCC CHECKTABLE (EMIS.dbo.syscolumns ).
> Can anyone suggest the best way to proceed with this problem. I am a
> little dubious about running REPAIR_ALLOW_DATALOSS on syscolumns, I am
> unsure of what will happen if sections of syscolumns go missing. I have
> run DBCC PAGE ('EMIS',1,266,1) but this has given me nothing to work
> with.
> Thanks in Advance,
> Dave Shaw.
>
|||This article may help ...
http://www.windows2000faq.com/Articl...rticleID=14051
"John Smith" <fsfsdf@.microsoft.com> wrote in message
news:enUNTKJBGHA.3872@.TK2MSFTNGP12.phx.gbl...
> Normally i would suggest DBREINDEX but as this is a system table you're
not
> allowed.
> Give SP_FixIndex a try. You will need the DB in single user mode 1st.
>
> "Dave Shaw" <Dave.Shaw1584@.NTLWorld.com> wrote in message
> news:1134990883.398840.145620@.z14g2000cwz.googlegr oups.com...
>
|||Thanks John Smith.
I shall give this a try.
Dave.

DBCC Problems with syscolumns

Hi, I have run a DBCC CHECKDB and it found 2 Errors in syscolumns. I
have run a CHECKTABLE and found the following Error:
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 3, index ID 2: Page (1:266) could not be processed. See other
errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 3, index ID 2, page (1:266), row 12. Test
(VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <= (nextRec - pRec)) failed. Values are 178 and 72.
DBCC results for 'syscolumns'.
There are 6963 rows in 144 pages for object 'syscolumns'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table
'syscolumns' (object ID 3).
repair_allow_data_loss is the minimum repair level for the errors found
by DBCC CHECKTABLE (EMIS.dbo.syscolumns ).
Can anyone suggest the best way to proceed with this problem. I am a
little dubious about running REPAIR_ALLOW_DATALOSS on syscolumns, I am
unsure of what will happen if sections of syscolumns go missing. I have
run DBCC PAGE ('EMIS',1,266,1) but this has given me nothing to work
with.
Thanks in Advance,
Dave Shaw.Normally i would suggest DBREINDEX but as this is a system table you're not
allowed.
Give SP_FixIndex a try. You will need the DB in single user mode 1st.
"Dave Shaw" <Dave.Shaw1584@.NTLWorld.com> wrote in message
news:1134990883.398840.145620@.z14g2000cwz.googlegroups.com...
> Hi, I have run a DBCC CHECKDB and it found 2 Errors in syscolumns. I
> have run a CHECKTABLE and found the following Error:
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 3, index ID 2: Page (1:266) could not be processed. See other
> errors for details.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 3, index ID 2, page (1:266), row 12. Test
> (VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <=> (nextRec - pRec)) failed. Values are 178 and 72.
> DBCC results for 'syscolumns'.
> There are 6963 rows in 144 pages for object 'syscolumns'.
> CHECKTABLE found 0 allocation errors and 2 consistency errors in table
> 'syscolumns' (object ID 3).
> repair_allow_data_loss is the minimum repair level for the errors found
> by DBCC CHECKTABLE (EMIS.dbo.syscolumns ).
> Can anyone suggest the best way to proceed with this problem. I am a
> little dubious about running REPAIR_ALLOW_DATALOSS on syscolumns, I am
> unsure of what will happen if sections of syscolumns go missing. I have
> run DBCC PAGE ('EMIS',1,266,1) but this has given me nothing to work
> with.
> Thanks in Advance,
> Dave Shaw.
>|||This article may help ...
http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14051
"John Smith" <fsfsdf@.microsoft.com> wrote in message
news:enUNTKJBGHA.3872@.TK2MSFTNGP12.phx.gbl...
> Normally i would suggest DBREINDEX but as this is a system table you're
not
> allowed.
> Give SP_FixIndex a try. You will need the DB in single user mode 1st.
>
> "Dave Shaw" <Dave.Shaw1584@.NTLWorld.com> wrote in message
> news:1134990883.398840.145620@.z14g2000cwz.googlegroups.com...
> > Hi, I have run a DBCC CHECKDB and it found 2 Errors in syscolumns. I
> > have run a CHECKTABLE and found the following Error:
> >
> > Server: Msg 8928, Level 16, State 1, Line 1
> > Object ID 3, index ID 2: Page (1:266) could not be processed. See other
> > errors for details.
> > Server: Msg 8944, Level 16, State 1, Line 1
> > Table Corrupt: Object ID 3, index ID 2, page (1:266), row 12. Test
> > (VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <=> > (nextRec - pRec)) failed. Values are 178 and 72.
> > DBCC results for 'syscolumns'.
> > There are 6963 rows in 144 pages for object 'syscolumns'.
> > CHECKTABLE found 0 allocation errors and 2 consistency errors in table
> > 'syscolumns' (object ID 3).
> > repair_allow_data_loss is the minimum repair level for the errors found
> > by DBCC CHECKTABLE (EMIS.dbo.syscolumns ).
> >
> > Can anyone suggest the best way to proceed with this problem. I am a
> > little dubious about running REPAIR_ALLOW_DATALOSS on syscolumns, I am
> > unsure of what will happen if sections of syscolumns go missing. I have
> > run DBCC PAGE ('EMIS',1,266,1) but this has given me nothing to work
> > with.
> >
> > Thanks in Advance,
> >
> > Dave Shaw.
> >
>|||Thanks John Smith.
I shall give this a try.
Dave.

DBCC Page does not appear to functon?

I have a corrupt sql server 2000 database table, dbcc checktable yields:

Server: Msg 8929, Level 16, State 1, Line 1

Object ID 738101670: Errors found in text ID 1922475229184 owned by data record identified by RID = (1:5663655:28) PageId = 53918671.

Server: Msg 8965, Level 16, State 1, Line 1

Table error: Object ID 738101670. The text, ntext, or image node at page (1:5663737), slot 0, text ID 1922475229184 is referenced by page (1:4527446), slot 9, but was not seen in the scan.

When I try to use dbcc page( testdb, page#,1 ) where I plug in any of the reported page#'s above I always get the following:

"Server: Msg 8968, Level 16, State 1, Line 2
Table error: DBCC PAGE page (41728:1) (object ID 0, index ID 0) is out of the range of this database.
DBCC execution completed. If DBCC printed error messages, contact your system administrator."

The only page value which does not yield this error is page 1, which is the only pageno I found on any examples on the web. I guess this is because this is the only page it works on?

Can you post the exact command your using?

Also, can you tell me the result of 'SELECT DB_ID()'?

Thanks,|||Looks like you've got your parameters swapped. It should be dbcc page(testdb, 1, page#). The second parameter is the file number (which will always be 1 if your database has no secondary data files).
|||

You are correct! The format I originally found on the internet was either for a prior version or something else unexplained. I found the correct format in one of Ken Henderson's books.

Thanks!

DBCC Page does not appear to function?

I have a corrupt sql server 2000 database table, dbcc checktable yields:

Server: Msg 8929, Level 16, State 1, Line 1

Object ID 738101670: Errors found in text ID 1922475229184 owned by data record identified by RID = (1:5663655:28) PageId = 53918671.

Server: Msg 8965, Level 16, State 1, Line 1

Table error: Object ID 738101670. The text, ntext, or image node at page (1:5663737), slot 0, text ID 1922475229184 is referenced by page (1:4527446), slot 9, but was not seen in the scan.

When I try to use dbcc page( testdb, page#,1 ) where I plug in any of the reported page#'s above I always get the following:

The only page value which does not yield this error is page 1, which is the only pageno I found on any examples on the web. I guess this is because this is the only page it works on?

Can you post the exact command your using?

Also, can you tell me the result of 'SELECT DB_ID()'?

You are correct! The format I originally found on the internet was either for a prior version or something else unexplained. I found the correct format in one of Ken Henderson's books.

Thanks!

sql

Monday, March 19, 2012

dbcc memusage

when I issued "dbcc memusage",
I got the errors:
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (1:929) with latch type SH. VerifyPageId failed.
but when I issued: "dbcc checkdb", it is working ok...
I have searched on the net, couldn't find any solution for it..
Would you please advise?Well if you look in BooksOnLine it will tell you that it is no longer
supported and I believe there were even reports of it being dangerous to
run. What is it you are trying to look for?
--
Andrew J. Kelly SQL MVP
"renhai" <renhai@.discussions.microsoft.com> wrote in message
news:8764FA14-93CF-4AC8-8165-3AEDEF7C4B93@.microsoft.com...
> when I issued "dbcc memusage",
> I got the errors:
> Server: Msg 8966, Level 16, State 4, Line 1
> Could not read and latch page (1:929) with latch type SH. VerifyPageId
> failed.
> but when I issued: "dbcc checkdb", it is working ok...
> I have searched on the net, couldn't find any solution for it..
> Would you please advise?|||Andrew,
I was looking for why this 'dbcc memusage' is not working on this server
only, but working on other servers...Is something wroing with this server?
If not, how can I approve to the manager? What is not supported? it is in SQL
Server 2000 SP4. Thanks in advance.
"Andrew J. Kelly" wrote:
> Well if you look in BooksOnLine it will tell you that it is no longer
> supported and I believe there were even reports of it being dangerous to
> run. What is it you are trying to look for?
> --
> Andrew J. Kelly SQL MVP
>
> "renhai" <renhai@.discussions.microsoft.com> wrote in message
> news:8764FA14-93CF-4AC8-8165-3AEDEF7C4B93@.microsoft.com...
> > when I issued "dbcc memusage",
> > I got the errors:
> > Server: Msg 8966, Level 16, State 4, Line 1
> > Could not read and latch page (1:929) with latch type SH. VerifyPageId
> > failed.
> >
> > but when I issued: "dbcc checkdb", it is working ok...
> >
> > I have searched on the net, couldn't find any solution for it..
> >
> > Would you please advise?
>
>|||I hope you got my reply I just sent to you...
"Andrew J. Kelly" wrote:
> Well if you look in BooksOnLine it will tell you that it is no longer
> supported and I believe there were even reports of it being dangerous to
> run. What is it you are trying to look for?
> --
> Andrew J. Kelly SQL MVP
>
> "renhai" <renhai@.discussions.microsoft.com> wrote in message
> news:8764FA14-93CF-4AC8-8165-3AEDEF7C4B93@.microsoft.com...
> > when I issued "dbcc memusage",
> > I got the errors:
> > Server: Msg 8966, Level 16, State 4, Line 1
> > Could not read and latch page (1:929) with latch type SH. VerifyPageId
> > failed.
> >
> > but when I issued: "dbcc checkdb", it is working ok...
> >
> > I have searched on the net, couldn't find any solution for it..
> >
> > Would you please advise?
>
>|||This is directly from BOL:
Removed; no longer supported or available. Remove all references of DBCC
MEMUSAGE and replace with references to these Performance Monitor counters.
Just because a command can be executed it does not mean in any way that it
is supported. If it is not in BOL then all bets are off and you run it at
your own risk. Who knows why it fails on that one machine since it is
unsupported in the first place. Use on of the supported commands to get the
information you require.
Andrew J. Kelly SQL MVP
"renhai" <renhai@.discussions.microsoft.com> wrote in message
news:2A28A250-24D7-4059-BD72-047C71EE4106@.microsoft.com...
> Andrew,
> I was looking for why this 'dbcc memusage' is not working on this server
> only, but working on other servers...Is something wroing with this
> server?
> If not, how can I approve to the manager? What is not supported? it is in
> SQL
> Server 2000 SP4. Thanks in advance.
> "Andrew J. Kelly" wrote:
>> Well if you look in BooksOnLine it will tell you that it is no longer
>> supported and I believe there were even reports of it being dangerous to
>> run. What is it you are trying to look for?
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "renhai" <renhai@.discussions.microsoft.com> wrote in message
>> news:8764FA14-93CF-4AC8-8165-3AEDEF7C4B93@.microsoft.com...
>> > when I issued "dbcc memusage",
>> > I got the errors:
>> > Server: Msg 8966, Level 16, State 4, Line 1
>> > Could not read and latch page (1:929) with latch type SH. VerifyPageId
>> > failed.
>> >
>> > but when I issued: "dbcc checkdb", it is working ok...
>> >
>> > I have searched on the net, couldn't find any solution for it..
>> >
>> > Would you please advise?
>>

Tuesday, March 27, 2012

DBCC SHRINKDATABASE Errors Running SQL Server 2000 , SP3a

DBCC Shrinkdatabase errors

Thursday, March 22, 2012

DBCC Results into a Table Brings Errors!

Wednesday, March 21, 2012

DBCC Question

DBCC Problems with syscolumns

DBCC Problems with syscolumns

DBCC Problems with syscolumns

DBCC Problems with syscolumns

DBCC Problems with syscolumns

DBCC Problems with syscolumns

DBCC Page does not appear to functon?

DBCC Page does not appear to function?

Monday, March 19, 2012

dbcc memusage

DBfile usage

Blog Archive

About Me