Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

dbcc checkstorage

8 posts in General Discussion Last posting was on 2012-07-26 08:40:24.0Z
RobertW Posted on 2012-07-25 11:30:38.0Z
From: RobertW <rkratsch@hotmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: dbcc checkstorage
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <500fd8de$1@forums-1-dub>
Date: 25 Jul 2012 04:30:38 -0700
X-Trace: forums-1-dub 1343215838 172.20.134.152 (25 Jul 2012 04:30:38 -0700)
X-Original-Trace: 25 Jul 2012 04:30:38 -0700, vip152.sybase.com
Lines: 29
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31270
Article PK: 74159

Hi,

I have an ASE 15.0.3 ESD#1 Linux x64 database wich will report allways
for dbcc checkstorage and checkverfiy:

Checking ally: Logical pagesize is 2048 bytes
DBCC CHECKSTORAGE for database 'ally' sequence 2 completed at Jul 25
2012 10:20AM. 1 faults and 13 suspect conditions were located. 0 checks
were aborted. You should investigate the recorded faults, and plan a
course of action that will correct them.
Suspect conditions are to be treated as faults if the same suspect
condition persists in subsequent CHECKSTORAGE operations, or if they are
also detected by other DBCC functions.

Verifying faults for 'ally'.
DBCC CHECKVERIFY for database 'ally' sequence 2 completed at Jul 25 2012
10:20AM. 0 suspect conditions considered, 0 identified as faults, 0
identified as harmless, and 0 could not be checked. 0 objects could not
be checked.

Normally checkstorage shows conditions because of user activity. It is
interesting that it shows allways EXACT the same number of conditions. I
have droped & reinstalled the dbccdb but I allways get the same number
of 1 fault and 13 suspect conditions. Any ideas why this happens?

Thanks

Robert


Rob V Posted on 2012-07-25 11:54:10.0Z
From: Rob V <rob@sypron.nl>
Reply-To: rob@sypron.nl
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: dbcc checkstorage
References: <500fd8de$1@forums-1-dub>
In-Reply-To: <500fd8de$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <500fde62$1@forums-1-dub>
Date: 25 Jul 2012 04:54:10 -0700
X-Trace: forums-1-dub 1343217250 172.20.134.152 (25 Jul 2012 04:54:10 -0700)
X-Original-Trace: 25 Jul 2012 04:54:10 -0700, vip152.sybase.com
Lines: 51
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31271
Article PK: 74160


On 25-Jul-2012 13:30, RobertW wrote:
> Hi,
>
> I have an ASE 15.0.3 ESD#1 Linux x64 database wich will report allways
> for dbcc checkstorage and checkverfiy:
>
> Checking ally: Logical pagesize is 2048 bytes
> DBCC CHECKSTORAGE for database 'ally' sequence 2 completed at Jul 25
> 2012 10:20AM. 1 faults and 13 suspect conditions were located. 0 checks
> were aborted. You should investigate the recorded faults, and plan a
> course of action that will correct them.
> Suspect conditions are to be treated as faults if the same suspect
> condition persists in subsequent CHECKSTORAGE operations, or if they are
> also detected by other DBCC functions.
>
> Verifying faults for 'ally'.
> DBCC CHECKVERIFY for database 'ally' sequence 2 completed at Jul 25 2012
> 10:20AM. 0 suspect conditions considered, 0 identified as faults, 0
> identified as harmless, and 0 could not be checked. 0 objects could not
> be checked.
>
> Normally checkstorage shows conditions because of user activity. It is
> interesting that it shows allways EXACT the same number of conditions. I
> have droped & reinstalled the dbccdb but I allways get the same number
> of 1 fault and 13 suspect conditions. Any ideas why this happens?
>
> Thanks
>
> Robert
>

You should get details on those errors first. Run sp_dbcc_faultreport to
display what was actually found by dbcc checkstorage.

HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Professional DBA for Sybase ASE, IQ, Replication Server

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks & Recipes for Sybase ASE"
"The Complete Sybase IQ Quick Reference Guide"
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter: @rob_verschoor
Sypron B.V., The Netherlands | Chamber of Commerce 27138666
-----------------------------------------------------------------


RobertW Posted on 2012-07-25 12:17:14.0Z
From: RobertW <rkratsch@hotmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: dbcc checkstorage
References: <500fd8de$1@forums-1-dub> <500fde62$1@forums-1-dub>
In-Reply-To: <500fde62$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <500fe3ca@forums-1-dub>
Date: 25 Jul 2012 05:17:14 -0700
X-Trace: forums-1-dub 1343218634 172.20.134.152 (25 Jul 2012 05:17:14 -0700)
X-Original-Trace: 25 Jul 2012 05:17:14 -0700, vip152.sybase.com
Lines: 134
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31272
Article PK: 74161

Am 25.07.2012 13:54, schrieb Rob V:

> On 25-Jul-2012 13:30, RobertW wrote:
>> Hi,
>>
>> I have an ASE 15.0.3 ESD#1 Linux x64 database wich will report allways
>> for dbcc checkstorage and checkverfiy:
>>
>> Checking ally: Logical pagesize is 2048 bytes
>> DBCC CHECKSTORAGE for database 'ally' sequence 2 completed at Jul 25
>> 2012 10:20AM. 1 faults and 13 suspect conditions were located. 0 checks
>> were aborted. You should investigate the recorded faults, and plan a
>> course of action that will correct them.
>> Suspect conditions are to be treated as faults if the same suspect
>> condition persists in subsequent CHECKSTORAGE operations, or if they are
>> also detected by other DBCC functions.
>>
>> Verifying faults for 'ally'.
>> DBCC CHECKVERIFY for database 'ally' sequence 2 completed at Jul 25 2012
>> 10:20AM. 0 suspect conditions considered, 0 identified as faults, 0
>> identified as harmless, and 0 could not be checked. 0 objects could not
>> be checked.
>>
>> Normally checkstorage shows conditions because of user activity. It is
>> interesting that it shows allways EXACT the same number of conditions. I
>> have droped & reinstalled the dbccdb but I allways get the same number
>> of 1 fault and 13 suspect conditions. Any ideas why this happens?
>>
>> Thanks
>>
>> Robert
>>
>
> You should get details on those errors first. Run sp_dbcc_faultreport to
> display what was actually found by dbcc checkstorage.
>
> HTH,
>
> Rob V.
> -----------------------------------------------------------------
> Rob Verschoor
>
> Certified Professional DBA for Sybase ASE, IQ, Replication Server
>
> Author of Sybase books (order online at www.sypron.nl/shop):
> "Tips, Tricks & Recipes for Sybase ASE"
> "The Complete Sybase IQ Quick Reference Guide"
> "The Complete Sybase ASE Quick Reference Guide"
> "The Complete Sybase Replication Server Quick Reference Guide"
>
> rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter: @rob_verschoor
> Sypron B.V., The Netherlands | Chamber of Commerce 27138666
> -----------------------------------------------------------------

Hi Rob,

it says nothing:

sp_dbcc_faultreport long,ally
--Msg 18491, Level 16, State 1:
--Server 'ALLYSRV', Procedure 'sp_dbcc_run_faultreport', Line 316:
--No fault report on DBCC operations available.

The dbcc_faults table is empty:
dbid id indid partitionid devid opid faultid
type_code status
------ ----------- ------ ----------- ----------- ------ -----------
----------- -----------
(0 Zeilen)


sp_dbcc_runcheck ally additionaly gives:

DBCC Operation : checkstorage
================================================================================
Database Name Start time End Time Operation
ID Hard Faults Soft Faults Text Columns Abort Count User Name




-------------------------------- -------------------- ----------
------------ ----------- ----------- ------------ -----------
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ally 07/25/2012 10:02:51 10:03:47 1
1 13 63975 0 sa




ally 07/25/2012 10:19:21 10:20:14 2
1 13 63975 0 sa




================================================================================
DBCC Operation : checkverify
================================================================================
Database Name Start time End Time Operation
ID Run Srl Table Name


Table Id Hard
Faults Soft Faults User Name



------------------------------ -------------------- ----------
------------ -------
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------- ----------- -----------
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ally 07/25/2012 10:05:00 10:05:00 1
1 (NULL)


(NULL) 0
0 sa



ally 07/25/2012 10:20:14 10:20:14 2
1 (NULL)


(NULL) 0
0 sa



================================================================================

Robert


Rob V Posted on 2012-07-25 12:34:23.0Z
From: Rob V <rob@sypron.nl>
Reply-To: rob@sypron.nl
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: dbcc checkstorage
References: <500fd8de$1@forums-1-dub> <500fde62$1@forums-1-dub> <500fe3ca@forums-1-dub>
In-Reply-To: <500fe3ca@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <500fe7cf@forums-1-dub>
Date: 25 Jul 2012 05:34:23 -0700
X-Trace: forums-1-dub 1343219663 172.20.134.152 (25 Jul 2012 05:34:23 -0700)
X-Original-Trace: 25 Jul 2012 05:34:23 -0700, vip152.sybase.com
Lines: 141
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31273
Article PK: 74162

Did you run it after checkstorage but before checkverify?
Also, try displaying only the faults for the run ID in question (which
seems to be 1 in your case); specify as "@opid=<number>" (without quotes).
This can report the detals of the faults, both when specifying long and
short format. You may need to paly around a bit with the parameters.

R.

On 25-Jul-2012 14:17, RobertW wrote:
> Am 25.07.2012 13:54, schrieb Rob V:
>> On 25-Jul-2012 13:30, RobertW wrote:
>>> Hi,
>>>
>>> I have an ASE 15.0.3 ESD#1 Linux x64 database wich will report allways
>>> for dbcc checkstorage and checkverfiy:
>>>
>>> Checking ally: Logical pagesize is 2048 bytes
>>> DBCC CHECKSTORAGE for database 'ally' sequence 2 completed at Jul 25
>>> 2012 10:20AM. 1 faults and 13 suspect conditions were located. 0 checks
>>> were aborted. You should investigate the recorded faults, and plan a
>>> course of action that will correct them.
>>> Suspect conditions are to be treated as faults if the same suspect
>>> condition persists in subsequent CHECKSTORAGE operations, or if they are
>>> also detected by other DBCC functions.
>>>
>>> Verifying faults for 'ally'.
>>> DBCC CHECKVERIFY for database 'ally' sequence 2 completed at Jul 25 2012
>>> 10:20AM. 0 suspect conditions considered, 0 identified as faults, 0
>>> identified as harmless, and 0 could not be checked. 0 objects could not
>>> be checked.
>>>
>>> Normally checkstorage shows conditions because of user activity. It is
>>> interesting that it shows allways EXACT the same number of conditions. I
>>> have droped & reinstalled the dbccdb but I allways get the same number
>>> of 1 fault and 13 suspect conditions. Any ideas why this happens?
>>>
>>> Thanks
>>>
>>> Robert
>>>
>>
>> You should get details on those errors first. Run sp_dbcc_faultreport to
>> display what was actually found by dbcc checkstorage.
>>
>> HTH,
>>
>> Rob V.
>> -----------------------------------------------------------------
>> Rob Verschoor
>>
>> Certified Professional DBA for Sybase ASE, IQ, Replication Server
>>
>> Author of Sybase books (order online at www.sypron.nl/shop):
>> "Tips, Tricks & Recipes for Sybase ASE"
>> "The Complete Sybase IQ Quick Reference Guide"
>> "The Complete Sybase ASE Quick Reference Guide"
>> "The Complete Sybase Replication Server Quick Reference Guide"
>>
>> rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter: @rob_verschoor
>> Sypron B.V., The Netherlands | Chamber of Commerce 27138666
>> -----------------------------------------------------------------
> Hi Rob,
>
> it says nothing:
>
> sp_dbcc_faultreport long,ally
> --Msg 18491, Level 16, State 1:
> --Server 'ALLYSRV', Procedure 'sp_dbcc_run_faultreport', Line 316:
> --No fault report on DBCC operations available.
>
> The dbcc_faults table is empty:
> dbid id indid partitionid devid opid faultid
> type_code status
> ------ ----------- ------ ----------- ----------- ------ -----------
> ----------- -----------
> (0 Zeilen)
>
>
> sp_dbcc_runcheck ally additionaly gives:
>
> DBCC Operation : checkstorage
> ================================================================================
>
> Database Name Start time End Time Operation
> ID Hard Faults Soft Faults Text Columns Abort Count User Name
>
>
>
> -------------------------------- -------------------- ----------
> ------------ ----------- ----------- ------------ -----------
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> ally 07/25/2012 10:02:51 10:03:47 1
> 1 13 63975 0 sa
>
>
>
> ally 07/25/2012 10:19:21 10:20:14 2
> 1 13 63975 0 sa
>
>
>
> ================================================================================
>
> DBCC Operation : checkverify
> ================================================================================
>
> Database Name Start time End Time Operation
> ID Run Srl Table Name
>
> Table Id Hard
> Faults Soft Faults User Name
>
>
> ------------------------------ -------------------- ----------
> ------------ -------
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ----------- ----------- -----------
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> ally 07/25/2012 10:05:00 10:05:00 1
> 1 (NULL)
>
> (NULL) 0
> 0 sa
>
>
> ally 07/25/2012 10:20:14 10:20:14 2
> 1 (NULL)
>
> (NULL) 0
> 0 sa
>
>
> ================================================================================
>
>
> Robert


RobertW Posted on 2012-07-25 13:19:48.0Z
From: RobertW <rkratsch@hotmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: dbcc checkstorage
References: <500fd8de$1@forums-1-dub> <500fde62$1@forums-1-dub> <500fe3ca@forums-1-dub> <500fe7cf@forums-1-dub>
In-Reply-To: <500fe7cf@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <500ff274@forums-1-dub>
Date: 25 Jul 2012 06:19:48 -0700
X-Trace: forums-1-dub 1343222388 172.20.134.152 (25 Jul 2012 06:19:48 -0700)
X-Original-Trace: 25 Jul 2012 06:19:48 -0700, vip152.sybase.com
Lines: 344
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31274
Article PK: 74164

I did it - but I has the same effect:

1> dbcc checkstorage (ally)
2> go
Checking ally: Logical pagesize is 2048 bytes
DBCC CHECKSTORAGE for database 'ally' sequence 4 completed at Jul 25 2012
2:54PM. 1 faults and 13 suspect conditions were located. 0 checks were
aborted.
You should investigate the recorded faults, and plan a course of action that
will correct them.
Suspect conditions are to be treated as faults if the same suspect condition
persists in subsequent CHECKSTORAGE operations, or if they are also
detected by
other DBCC functions.
1> sp_dbcc_faultreport long,ally
2> go
Msg 18491, Leve l 16, State 1:
Server 'ALLYSRV', Procedure 'sp_dbcc_run_faultreport', Line 316:
No fault report on DBCC operations available.
(return status = 1)
1> sp_dbcc_faultreport long,ally,@opid=1
2> go
Msg 18491, Level 16, State 1:
Server 'ALLYSRV', Procedure 'sp_dbcc_run_faultreport', Line 316:
No fault report on DBCC operations available.
(return status = 1)
1> sp_dbcc_summaryreport ally
2> go
DBCC Operation : checkstorage
================================================================================
Database Name
Start time End Time
Operation ID Hard Faults Soft Faults Text Columns Abort Count
User Name





------------------------------------------------------------
---------------------------------------- --------------------
------------ ----------- ----------- ------------ -----------

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ally
07/25/2012 10:02:51 10:03:47
1 1 13 63975 0
sa





ally
07/25/2012 10:19:21 10:20:14
2 1 13 63975 0
sa





ally
07/25/2012 13:07:04 13:07:56
3 1 13 63975 0
sa





ally
07/25/2012 14:54:03 14:54:56
4 1 13 63975 0
sa






(1 row affected)

================================================================================
DBCC Operation : checkverify
================================================================================
Database Name
Start time End Time
Operation ID Run Srl
Table Name





Table Id Hard Faults Soft Faults
User Name





------------------------------------------------------------
---------------------------------------- --------------------
------------ -------

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------- ----------- -----------

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ally
07/25/2012 10:05:00 10:05:00
1 1
NULL





NULL 0 0
sa





ally
07/25/2012 10:20:14 10:20:14
2 1
NULL





NULL 0 0
sa






================================================================================
(return status = 0)
1> sp_dbcc_faultreport long,ally,@opid=3
2> go
Msg 18491, Level 16, State 1:
Server 'ALLYSRV', Procedure 'sp_dbcc_run_faultreport', Line 316:
No fault report on DBCC operations available.
(return status = 1)
1> sp_dbcc_faultreport long,ally,@opid=4
2> go
Msg 18491, Level 16, State 1:
Server 'ALLYSRV', Procedure 'sp_dbcc_run_faultreport', Line 316:
No fault report on DBCC operations available.
(return status = 1)

The only data I found beside from dbcc_operation_log was in
dbcc_operation_results (only the first five columns):

dbid opid optype type_code intvalue
------ ------ ------ ----------- -----------
4 1 2 1000 1
4 1 2 1001 13
4 1 2 1002 0
4 1 2 1007 63975
4 1 3 1000 0
4 1 3 1001 0
4 1 3 1002 0
4 2 2 1000 1
4 2 2 1001 13
4 2 2 1002 0
4 2 2 1007 63975
4 2 3 1000 0
4 2 3 1001 0
4 2 3 1002 0
4 3 2 1000 1
4 3 2 1001 13
4 3 2 1002 0
4 3 2 1007 63975
4 4 2 1000 1
4 4 2 1001 13
4 4 2 1002 0
4 4 2 1007 63975

dbcc checkdb, checkalloc and checkcatalog outputs are clean

Robert


Am 25.07.2012 14:34, schrieb Rob V:

> Did you run it after checkstorage but before checkverify?
> Also, try displaying only the faults for the run ID in question (which
> seems to be 1 in your case); specify as "@opid=<number>" (without quotes).
> This can report the detals of the faults, both when specifying long and
> short format. You may need to paly around a bit with the parameters.
>
> R.
>
>
> On 25-Jul-2012 14:17, RobertW wrote:
>> Am 25.07.2012 13:54, schrieb Rob V:
>>> On 25-Jul-2012 13:30, RobertW wrote:
>>>> Hi,
>>>>
>>>> I have an ASE 15.0.3 ESD#1 Linux x64 database wich will report allways
>>>> for dbcc checkstorage and checkverfiy:
>>>>
>>>> Checking ally: Logical pagesize is 2048 bytes
>>>> DBCC CHECKSTORAGE for database 'ally' sequence 2 completed at Jul 25
>>>> 2012 10:20AM. 1 faults and 13 suspect conditions were located. 0 checks
>>>> were aborted. You should investigate the recorded faults, and plan a
>>>> course of action that will correct them.
>>>> Suspect conditions are to be treated as faults if the same suspect
>>>> condition persists in subsequent CHECKSTORAGE operations, or if they
>>>> are
>>>> also detected by other DBCC functions.
>>>>
>>>> Verifying faults for 'ally'.
>>>> DBCC CHECKVERIFY for database 'ally' sequence 2 completed at Jul 25
>>>> 2012
>>>> 10:20AM. 0 suspect conditions considered, 0 identified as faults, 0
>>>> identified as harmless, and 0 could not be checked. 0 objects could not
>>>> be checked.
>>>>
>>>> Normally checkstorage shows conditions because of user activity. It is
>>>> interesting that it shows allways EXACT the same number of
>>>> conditions. I
>>>> have droped & reinstalled the dbccdb but I allways get the same number
>>>> of 1 fault and 13 suspect conditions. Any ideas why this happens?
>>>>
>>>> Thanks
>>>>
>>>> Robert
>>>>
>>>
>>> You should get details on those errors first. Run sp_dbcc_faultreport to
>>> display what was actually found by dbcc checkstorage.
>>>
>>> HTH,
>>>
>>> Rob V.
>>> -----------------------------------------------------------------
>>> Rob Verschoor
>>>
>>> Certified Professional DBA for Sybase ASE, IQ, Replication Server
>>>
>>> Author of Sybase books (order online at www.sypron.nl/shop):
>>> "Tips, Tricks & Recipes for Sybase ASE"
>>> "The Complete Sybase IQ Quick Reference Guide"
>>> "The Complete Sybase ASE Quick Reference Guide"
>>> "The Complete Sybase Replication Server Quick Reference Guide"
>>>
>>> rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter: @rob_verschoor
>>> Sypron B.V., The Netherlands | Chamber of Commerce 27138666
>>> -----------------------------------------------------------------
>> Hi Rob,
>>
>> it says nothing:
>>
>> sp_dbcc_faultreport long,ally
>> --Msg 18491, Level 16, State 1:
>> --Server 'ALLYSRV', Procedure 'sp_dbcc_run_faultreport', Line 316:
>> --No fault report on DBCC operations available.
>>
>> The dbcc_faults table is empty:
>> dbid id indid partitionid devid opid faultid
>> type_code status
>> ------ ----------- ------ ----------- ----------- ------ -----------
>> ----------- -----------
>> (0 Zeilen)
>>
>>
>> sp_dbcc_runcheck ally additionaly gives:
>>
>> DBCC Operation : checkstorage
>> ================================================================================
>>
>>
>> Database Name Start time End Time Operation
>> ID Hard Faults Soft Faults Text Columns Abort Count User Name
>>
>>
>>
>> -------------------------------- -------------------- ----------
>> ------------ ----------- ----------- ------------ -----------
>> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>>
>> ally 07/25/2012 10:02:51 10:03:47 1
>> 1 13 63975 0 sa
>>
>>
>>
>> ally 07/25/2012 10:19:21 10:20:14 2
>> 1 13 63975 0 sa
>>
>>
>>
>> ================================================================================
>>
>>
>> DBCC Operation : checkverify
>> ================================================================================
>>
>>
>> Database Name Start time End Time Operation
>> ID Run Srl Table Name
>>
>> Table Id Hard
>> Faults Soft Faults User Name
>>
>>
>> ------------------------------ -------------------- ----------
>> ------------ -------
>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> ----------- ----------- -----------
>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>>
>> ally 07/25/2012 10:05:00 10:05:00 1
>> 1 (NULL)
>>
>> (NULL) 0
>> 0 sa
>>
>>
>> ally 07/25/2012 10:20:14 10:20:14 2
>> 1 (NULL)
>>
>> (NULL) 0
>> 0 sa
>>
>>
>> ================================================================================
>>
>>
>>
>> Robert
>
>


Bret Halford Posted on 2012-07-25 15:20:39.0Z
From: Bret Halford <bret@sybase.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: dbcc checkstorage
References: <500fd8de$1@forums-1-dub> <500fde62$1@forums-1-dub> <500fe3ca@forums-1-dub> <500fe7cf@forums-1-dub> <500ff274@forums-1-dub>
In-Reply-To: <500ff274@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <50100ec7$1@forums-1-dub>
Date: 25 Jul 2012 08:20:39 -0700
X-Trace: forums-1-dub 1343229639 172.20.134.152 (25 Jul 2012 08:20:39 -0700)
X-Original-Trace: 25 Jul 2012 08:20:39 -0700, vip152.sybase.com
Lines: 18
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31275
Article PK: 74163


On 7/25/2012 7:19 AM, RobertW wrote:
> I did it - but I has the same effect:

Perhaps the faults dbcc checkstorage are
reporting have been registered as faults
to exclude from sp_dbcc_faultreport and
checkverify processing?


Check
a) if the dbcc_exclusions table has any entries
b) if selecting directly from dbcc_faults shows rows
matching the number of faults and suspect conditions
(presumably with object or fault ids that are in
dbcc_exclusions)


RobertW Posted on 2012-07-26 06:05:55.0Z
From: RobertW <rkratsch@hotmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: dbcc checkstorage
References: <500fd8de$1@forums-1-dub> <500fde62$1@forums-1-dub> <500fe3ca@forums-1-dub> <500fe7cf@forums-1-dub> <500ff274@forums-1-dub> <50100ec7$1@forums-1-dub>
In-Reply-To: <50100ec7$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <5010de43$1@forums-1-dub>
Date: 25 Jul 2012 23:05:55 -0700
X-Trace: forums-1-dub 1343282755 172.20.134.152 (25 Jul 2012 23:05:55 -0700)
X-Original-Trace: 25 Jul 2012 23:05:55 -0700, vip152.sybase.com
Lines: 35
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31276
Article PK: 74165

Hi,

dbcc_exclusions includes only

dbid type fault_type table_name
------ ---- ----------- ---------------------------------------------
0 1 100035 (NULL)
0 1 100037 (NULL)
0 1 100040 (NULL)

the checked database has an db_id=4.
dbcc_faults is empty it contains no row.

Robert

Am 25.07.2012 17:20, schrieb Bret Halford:

> On 7/25/2012 7:19 AM, RobertW wrote:
>> I did it - but I has the same effect:
>
> Perhaps the faults dbcc checkstorage are
> reporting have been registered as faults
> to exclude from sp_dbcc_faultreport and
> checkverify processing?
>
>
> Check
> a) if the dbcc_exclusions table has any entries
> b) if selecting directly from dbcc_faults shows rows
> matching the number of faults and suspect conditions
> (presumably with object or fault ids that are in
> dbcc_exclusions)
>
>
>


RobertW Posted on 2012-07-26 08:40:24.0Z
From: RobertW <rkratsch@hotmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: dbcc checkstorage
References: <500fd8de$1@forums-1-dub> <500fde62$1@forums-1-dub> <500fe3ca@forums-1-dub> <500fe7cf@forums-1-dub> <500ff274@forums-1-dub> <50100ec7$1@forums-1-dub> <5010de43$1@forums-1-dub>
In-Reply-To: <5010de43$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <50110278@forums-1-dub>
Date: 26 Jul 2012 01:40:24 -0700
X-Trace: forums-1-dub 1343292024 172.20.134.152 (26 Jul 2012 01:40:24 -0700)
X-Original-Trace: 26 Jul 2012 01:40:24 -0700, vip152.sybase.com
Lines: 43
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31277
Article PK: 74166

If found the problem, after upgrading from 15.0.3 ESD#1 to ESD#4.1 the
problem is gone.

Thanks

Robert

> Hi,
>
> dbcc_exclusions includes only
>
> dbid type fault_type table_name
> ------ ---- ----------- ---------------------------------------------
> 0 1 100035 (NULL)
> 0 1 100037 (NULL)
> 0 1 100040 (NULL)
>
> the checked database has an db_id=4.
> dbcc_faults is empty it contains no row.
>
> Robert
>
> Am 25.07.2012 17:20, schrieb Bret Halford:
>> On 7/25/2012 7:19 AM, RobertW wrote:
>>> I did it - but I has the same effect:
>>
>> Perhaps the faults dbcc checkstorage are
>> reporting have been registered as faults
>> to exclude from sp_dbcc_faultreport and
>> checkverify processing?
>>
>>
>> Check
>> a) if the dbcc_exclusions table has any entries
>> b) if selecting directly from dbcc_faults shows rows
>> matching the number of faults and suspect conditions
>> (presumably with object or fault ids that are in
>> dbcc_exclusions)
>>
>>
>>
>