DBCC checks that are correct in replication environment

jimhub@gmail.com · *nix forums beginner Joined: 04 Jul 2006 Posts: 2

I am running. sp_dbcc_runcheck. Below is a sample of the output. If I
rerun it after suspending replication, I will only see the suggestions
for syslogs and space bits. While I'm at it, is there a way to keep
from constantly getting space bit errors. As soon as we clear them up,
new errors pop up.

Thanks!
Jim

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

Database level recommendations:

Run dbcc checkalloc with the 'fix' option.

Reload the database from a clean backup.

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

Suggested corrective actions for object syslogs, objid 8, listed in
recommended
order:

Run dbcc tablealloc with the 'fix' option.
Run dbcc checktable.

Recommended corrective action for object at_product_delete, objid
157959639:

Run dbcc checktable.

Recommended corrective action for object at_product_fix, objid
317960209:

Run dbcc checktable.

Suggested corrective actions for object MEMBER_STAT, objid 352004285,
listed in recommended order:

Run dbcc tablealloc with the 'fix' option.
Drop the object and recreate it.

Recommended corrective action for object PRODUCT_ATTRIBUTE, objid
432056625:

Run dbcc checktable.

Recommended corrective action for object PAYMENT, objid 508528845:

Run dbcc checktable.

Recommended corrective action for object PRODUCT_PAGE_SECTION, objid
704057594:

Run dbcc checktable.

Suggested corrective actions for object MEMBER, objid 848006052, listed
in recommended order:

Run dbcc indexalloc with the 'fix' option.
Run dbcc tablealloc with the 'fix' option.
Run dbcc checktable.

Recommended corrective action for object rater2rated, objid 883534231:

Run dbcc checktable.

Suggested corrective actions for object TEXT_BLOB, objid 976006508,
listed in recommended order:

Run dbcc checktable.
Drop the object and recreate it.

Recommended corrective action for object TRIGGER_ALERT, objid
1307867726:

Run dbcc checktable.

Recommended corrective action for object MEMBER_MEMBER_COMMENT, objid
1432392172:

Drop the object and recreate it.

Recommended corrective action for object member_member_comment_arch,
objid
1536060558:

Run dbcc checktable.

Recommended corrective action for object PRODUCT, objid 1568008617:

Run dbcc checktable.

Recommended corrective action for object Customer2product_data, objid
1626488873:

Run dbcc checktable with the 'fix_spacebits' option.

Recommended corrective action for object OPINION, objid 1760009301:

Run dbcc checktable.

Recommended corrective action for object login_log, objid 1811537537:

Run dbcc checktable.

Recommended corrective action for object MEMBER2TRUSTEDMEMBER, objid
1856009643:

Run dbcc checktable.

Recommended corrective action for object image_content2object, objid
1884585802:

Run dbcc checktable.

Suggested corrective actions for object READLOG, objid 1888009757,
listed in recommended order:

Run dbcc indexalloc with the 'fix' option.
Run dbcc tablealloc with the 'fix' option.
Drop the object and recreate it.

Suggested corrective actions for object OPINION_RATING, objid
1920009871, listed in recommended order:

Run dbcc checktable.
Drop the object and recreate it.

Suggested corrective actions for object OPINION_DATA, objid 2016010213,
listed in recommended order:

Run dbcc checktable with the 'fix_spacebits' option.
Run dbcc checktable.

Suggested corrective actions for object MEMBER_DATA, objid 2048010327,
listed in recommended order:

Run dbcc indexalloc with the 'fix' option.
Run dbcc tablealloc with the 'fix' option.
Drop the object and recreate it.

bret@sybase.com wrote:

bret@sybase.com · *nix forums addict Joined: 24 May 2005 Posts: 66

jimhub@gmail.com wrote:

jimhub@gmail.com · *nix forums beginner Joined: 04 Jul 2006 Posts: 2

I tried talking to Sybase and they don't have a resolution. Perhaps
someone in the group can offer up what they do.

I am running nightly dbcc checks on my primary and replicated
databases. With the new and improved dbcc checks, I often get
indications of potential failure when I run sp_dbcc_recommendations. If
I suspend replication and then DBCC on the replicated databases, there
are no errors reported.

So I understand that when the server is busy, it doesn't do such a
great job of checking... I would guess it is that the checks don't go
back to verify the potential errors that it has found.

What I would like is an automated process that alerts me when I have
corruption, and quietly does it's job when no problems exist. What are
you doing to get good results from your DBCC checks? Does anyone have
code, scripts, snippets that are working for them?

Thanks very much in advance for any help you may be able to offer!

Google