Showing posts with label corrupt. Show all posts
Showing posts with label corrupt. Show all posts

Wednesday, March 21, 2012

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:

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

sql

Friday, February 24, 2012

dbcc checktable(syslogs)

In SQL Server 6.5, after I run the following command, it has error in the
result. How can I fix the Table Corrupt problem ?
Thanks a lot !
Query :
dbcc checktable(syslogs)
go
checkpoint
go
Result :
Checking syslogs
Msg 2578, Level 16, State 1
The first page 764720 in Sysindexes for table 'syslogs' has previous page #
764721 in its page header. The previous page # should be NULL. Please check
Sysindexes.
Msg 2503, Level 16, State 1
Table Corrupt: Page linkage is not consistent; check the following pages:
(current page#=764720; page# pointing to this page=0; previous page#
indicated in this page=764721)
DBCC execution completed. If DBCC printed error messages, see your System
Administrator.You could try just emptying the log (but please consider your backup strategy when doing this).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Danny" <.> wrote in message news:ughx2LS0EHA.3596@.TK2MSFTNGP12.phx.gbl...
> In SQL Server 6.5, after I run the following command, it has error in the
> result. How can I fix the Table Corrupt problem ?
> Thanks a lot !
> Query :
> dbcc checktable(syslogs)
> go
> checkpoint
> go
> Result :
> Checking syslogs
> Msg 2578, Level 16, State 1
> The first page 764720 in Sysindexes for table 'syslogs' has previous page #
> 764721 in its page header. The previous page # should be NULL. Please check
> Sysindexes.
> Msg 2503, Level 16, State 1
> Table Corrupt: Page linkage is not consistent; check the following pages:
> (current page#=764720; page# pointing to this page=0; previous page#
> indicated in this page=764721)
> DBCC execution completed. If DBCC printed error messages, see your System
> Administrator.
>

dbcc checktable(syslogs)

In SQL Server 6.5, after I run the following command, it has error in the
result. How can I fix the Table Corrupt problem ?
Thanks a lot !
Query :
dbcc checktable(syslogs)
go
checkpoint
go
Result :
Checking syslogs
Msg 2578, Level 16, State 1
The first page 764720 in Sysindexes for table 'syslogs' has previous page #
764721 in its page header. The previous page # should be NULL. Please check
Sysindexes.
Msg 2503, Level 16, State 1
Table Corrupt: Page linkage is not consistent; check the following pages:
(current page#=764720; page# pointing to this page=0; previous page#
indicated in this page=764721)
DBCC execution completed. If DBCC printed error messages, see your System
Administrator.
You could try just emptying the log (but please consider your backup strategy when doing this).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Danny" <.> wrote in message news:ughx2LS0EHA.3596@.TK2MSFTNGP12.phx.gbl...
> In SQL Server 6.5, after I run the following command, it has error in the
> result. How can I fix the Table Corrupt problem ?
> Thanks a lot !
> Query :
> dbcc checktable(syslogs)
> go
> checkpoint
> go
> Result :
> Checking syslogs
> Msg 2578, Level 16, State 1
> The first page 764720 in Sysindexes for table 'syslogs' has previous page #
> 764721 in its page header. The previous page # should be NULL. Please check
> Sysindexes.
> Msg 2503, Level 16, State 1
> Table Corrupt: Page linkage is not consistent; check the following pages:
> (current page#=764720; page# pointing to this page=0; previous page#
> indicated in this page=764721)
> DBCC execution completed. If DBCC printed error messages, see your System
> Administrator.
>

dbcc checktable(syslogs)

In SQL Server 6.5, after I run the following command, it has error in the
result. How can I fix the Table Corrupt problem ?
Thanks a lot !
Query :
dbcc checktable(syslogs)
go
checkpoint
go
Result :
Checking syslogs
Msg 2578, Level 16, State 1
The first page 764720 in Sysindexes for table 'syslogs' has previous page #
764721 in its page header. The previous page # should be NULL. Please check
Sysindexes.
Msg 2503, Level 16, State 1
Table Corrupt: Page linkage is not consistent; check the following pages:
(current page#=764720; page# pointing to this page=0; previous page#
indicated in this page=764721)
DBCC execution completed. If DBCC printed error messages, see your System
Administrator.You could try just emptying the log (but please consider your backup strateg
y when doing this).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Danny" <.> wrote in message news:ughx2LS0EHA.3596@.TK2MSFTNGP12.phx.gbl...
> In SQL Server 6.5, after I run the following command, it has error in the
> result. How can I fix the Table Corrupt problem ?
> Thanks a lot !
> Query :
> dbcc checktable(syslogs)
> go
> checkpoint
> go
> Result :
> Checking syslogs
> Msg 2578, Level 16, State 1
> The first page 764720 in Sysindexes for table 'syslogs' has previous page
#
> 764721 in its page header. The previous page # should be NULL. Please chec
k
> Sysindexes.
> Msg 2503, Level 16, State 1
> Table Corrupt: Page linkage is not consistent; check the following pages:
> (current page#=764720; page# pointing to this page=0; previous page#
> indicated in this page=764721)
> DBCC execution completed. If DBCC printed error messages, see your System
> Administrator.
>