dbcc check verify....

[Suresh]

Hi,
i run the dbcc cmd in production server for one database , that shows
0 faults and 2 suspect conditions were located. How can i generate
for checking suspect condition of that database.

this is o/p for that command,

DBCC CHECKSTORAGE for database 'DBSglep' sequence 2044 completed at
Aug 22 2010 8:11PM. 0 faults and 2 suspect conditions were located. 0
Suspect conditions are to be treated as faults if the same suspect
condition persists in subsequent CHECKSTORAGE operations, or if they
are
DBCC CHECKSTORAGE for database 'DBSpscb' sequence 2043 completed at
Aug 22 2010 8:19PM. 0 faults and 2 suspect conditions were located. 0
Suspect conditions are to be treated as faults if the same suspect
condition persists in subsequent CHECKSTORAGE operations, or if they
are

2010-08-22 20:47:50 >>> Error or suspect conditions detected M-^V
Please check the database presenting the problem

DBCC CHECKVERIFY for database 'DB_name ' sequence 2044 completed at
Aug 22 2010 9:14PM. 2 suspect conditions considered, 0 identified as
faults, 2 identified as harmless, and 0 could not be checked. 0
objects could not be checked.

[Suresh]

Hi,
 i run the dbcc cmd in production server for one database , that shows
0 faults and 2 suspect conditions were located.  How can i generate
for checking suspect condition of that database.
this is o/p for that command,
DBCC CHECKSTORAGE for database 'DB_' sequence 2044 completed at
Aug 22 2010  8:11PM. 0 faults and 2 suspect conditions were located. 0
Suspect conditions are to be treated as faults if the same suspect
condition persists in subsequent CHECKSTORAGE operations, or if they
are
DBCC CHECKSTORAGE for database 'DBSpscb' sequence 2043 completed at
Aug 22 2010  8:19PM. 0 faults and 2 suspect conditions were located. 0
Suspect conditions are to be treated as faults if the same suspect
condition persists in subsequent CHECKSTORAGE operations, or if they
are
2010-08-22 20:47:50 >>> Error or suspect conditions detected M-^V
Please check the database presenting the problem
DBCC CHECKVERIFY for database 'DB_name ' sequence 2044 completed at
Aug 22 2010  9:14PM. 2 suspect conditions considered, 0 identified as
faults, 2 identified as harmless, and 0 could not be checked. 0
objects could not be checked.

for this i did as follows steps..

1> select * from dbcc_faults where dbid = 29
2> go
dbid id indid partitionid devid opid faultid
type_code status
------ ----------- ------ ----------- ------ ------ -----------
----------- -----------
29 221240812 0 1 38 2044 2
100025 2
29 969051457 0 1 38 2044 1
100025 2

(2 rows affected)
1> select * from dbcc_faults where dbid = 38
2> go
dbid id indid partitionid devid opid faultid
type_code status
------ ----------- ------ ----------- ------ ------ -----------
----------- -----------
38 432001539 0 1 54 2043 1
100035 0
38 432001539 0 1 54 2043 2
100035 0


1> use DBSglep
2> go
1> select name from sysobjects where id = 221240812
2> go
name
------------------------------
unposted_jrnl_line

(1 row affected)
1> select name from sysobjects where id = 969051457
2> go
name
------------------------------
unposted_jrnl_ctrl

(1 row affected)
1> use DBSpscb
2> go
1> select name from sysobjects where id = 432001539
2> go
name
------------------------------
psc_log


***********************************************************

1> use DBSglep
2> go

1> select name from sysobjects where id = 221240812
2> go
name
------------------------------
unposted_jrnl_line

(1 row affected)
1> dbcc checktable (221240812)
2> go
Checking unposted_jrnl_line: Logical pagesize is 16384 bytes
The total number of data pages in this table is 560.
The total number of empty pages (with all deleted rows) in this table
is 1.
The total number of pages which could be garbage collected to free up
some space is 241.
Table has 17477 data rows.
DBCC execution completed. If DBCC printed error messages, contact a
user with System Administrator (SA) role.
1> dbcc checktable (969051457)
2> go
Checking unposted_jrnl_ctrl: Logical pagesize is 16384 bytes
The total number of data pages in this table is 62.
Table has 538 data rows.
DBCC execution completed. If DBCC printed error messages, contact a
user with System Administrator (SA) role.
1> use DBSpscb
2> go

1> dbcc checktable (432001539, fix_spacebits)
2> go
Checking psc_log: Logical pagesize is 16384 bytes
Msg 12916, Level 16, State 1:
Server 'COMPT_PR2', Line 1:
Fixed spacebits (on allocation page) for DOL datapage 2155, with insfs
279 and expected row length 0. Were expected to be 0x8, but were found
to be 0x0.
Msg 12916, Level 16, State 1:
Server 'COMPT_PR2', Line 1:
Fixed spacebits (on allocation page) for DOL datapage 2156, with insfs
6295 and expected row length 0. Were expected to be 0x8, but were
found to be 0x0.
The total number of data pages in this table is 608.
The total number of pages which could be garbage collected to free up
some space is 4.
Table has 31727 data rows.
DBCC execution completed. If DBCC printed error messages, contact a
user with System Administrator (SA) role.

[Sathesh]

Hi,

You can try these follwing options:
run sp_dbcc_summaryreport for that database
sp_dbcc_faultreport (with opid of the checkstorage)
sp_dbcc_help_fault

This will help you

Thanks,
Sathesh.S

[Suresh]

Post by Sathesh
Hi,
run sp_dbcc_summaryreport for that database
sp_dbcc_faultreport (with opid of the checkstorage)
sp_dbcc_help_fault
This will help you
Thanks,
Sathesh.S

thanks you sathesh, i have fauilt code 100035 in perticular
table(table1) when i run dbcc_checktable table1, is this stored
procedure solve that fault issue or how i can solve 100035 fault
error..

1> dbcc checktable (table1)
2> go


The logical page size of this table is 2048 bytes.
The total number of data pages in partition
'tblFeeCalculationMonthlyDataHistory_279773123' (partition ID
279773123) is 91300.
Partition 'tblFeeCalculationMonthlyDataHistory_279773123' (partition
ID 279773123) has 582531 data rows.
The total number of empty pages (with all deleted rows) in partition
'tblFeeCalculationMonthlyDataHistory_279773123' (partition ID
279773123) is 0.
The total number of pages in partition
'tblFeeCalculationMonthlyDataHistory_279773123' (partition ID
279773123) which could be garbage collected to free up some space is
29.
The total number of deleted rows in partition
'tblFeeCalculationMonthlyDataHistory_279773123' (partition ID
279773123) is 8.
The total number of pages in partition
'tblFeeCalculationMonthlyDataHistory_279773123' (partition ID
279773123) with more than 50 percent garbage is 2.
The total number of pages in partition
'tblFeeCalculationMonthlyDataHistory_279773123' (partition ID
279773123) with more than 50 percent insert free space is 15.

The total number of data pages in this table is 91300.
The total number of pages which could be garbage collected to free up
some space is 29.
The total number of deleted rows in the table is 8.
The total number of pages with more than 50 percent garbage is 2.
The total number of pages with more than 50 percent insert free space
is 15.
Table has 582531 data rows.
DBCC execution completed. If DBCC printed error messages, contact a
user with System Administrator (SA) role.

[Sathesh]

Hi Suresh,

You can run the following command to fix the spacebits error:

dbcc checktable (table_name, fix_spacebits)

Note: Make sutre that no processes are holding any lock on the table
when you run this.


Thanks,
Sathesh.S