Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

dbcc checkdb part failed in maintenance plan Expand / Collapse
Author
Message
Posted Tuesday, April 10, 2007 8:17 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, May 16, 2014 11:57 AM
Points: 178, Visits: 508

Hi, not sure if this is an issue with sql 2005 service pack 2 (installed last week). Part of my maintenance plan checks database integrity. The sql shows:

USE [master]
GO
DBCC CHECKDB WITH NO_INFOMSGS
GO
USE [model]
GO
DBCC CHECKDB WITH NO_INFOMSGS
GO
USE [msdb]
GO
DBCC CHECKDB WITH NO_INFOMSGS

This part fails everyday. The error says:

Check Database Integrity

Check Database integrity on Local server connection
Databases: All system databases
Include indexes
Task start: 2007-04-10T05:00:39.
Task end: 2007-04-10T05:00:39.
Failed0) Alter failed for Server 'XYZ'.

It seems to me like its trying to alter database by changing to to single user mode, like it would do if you have repair_rebuild argument there, but the code does not show. Does anyone have any clue?

Thanks,

Kathleen

 

 

 

 

Post #357190
Posted Tuesday, April 10, 2007 8:30 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 5:51 AM
Points: 6,266, Visits: 2,028

http://support.microsoft.com/kb/934459

 




* Noel
Post #357359
Posted Wednesday, April 11, 2007 7:34 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, May 16, 2014 11:57 AM
Points: 178, Visits: 508
Thanks much!
Post #357479
Posted Thursday, January 29, 2009 7:17 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, May 19, 2014 2:43 AM
Points: 21, Visits: 152
I got a later version than that kb specifies and still have a problem with checkdb and same error.

Microsoft SQL Server 2005 - 9.00.3282.00 (X64) Aug 5 2008 00:48:00 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
Post #645891
Posted Thursday, January 29, 2009 7:49 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, May 16, 2014 11:57 AM
Points: 178, Visits: 508
I have:
Microsoft SQL Server 2005 - 9.00.3233.00 (X64) Mar 6 2008 21:58:47 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

The error cleared out a while ago, I forget when. Might have been after installing the patch Noel specified.
Post #645934
Posted Sunday, March 29, 2009 9:17 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, July 13, 2014 5:42 PM
Points: 2, Visits: 39
Check the "Automatically set I/O affinity mask for all processors" in your server properties. We had unselected this to reduce processors for licensing, and the maintenance plan failed the following weekend and since. I reselected thsi and the plan started working. Still sounds like a bug Microsoft should fix as a plan shouldn't fail for this reason.
Post #685850
Posted Monday, June 21, 2010 7:59 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, May 1, 2014 7:12 AM
Points: 10, Visits: 348
I had the same problem and checked every conceivable log and even did profiler traces to no avail.
I finally stumbled onto a solution that at least worked for me. It had to do with enabling AWE (Address Windowing Extensions allow 32-bit operating systems to access large amounts of memory. One first has to enable the lock pages in memory option. See links below. Hope this helps.
http://msdn2.microsoft.com/en-US/library/ms190730.aspx
http://msdn.microsoft.com/en-us/library/ms190673%28SQL.90%29.aspx
Post #940334
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse