February 18, 2009 at 3:51 pm
I have an issue with the Check DB Integrity Task failing in a maintenance plan. The problem is described exactly at http://support.microsoft.com/kb/945067. That is literally the exact problem I am having, but there is a disconnect. The solution is to use sp_configure and change 'allow updates' to 0. Well, it is already 0. I ran the suggested script anyway:
sp_configure 'allow updates', 0
reconfigure with override
Then kicked off the maintenance plan, but as I assumed, it didn't work, same error. This instance is version 9.0.3239 and it will be going to 9.0.4207 this Sunday 2/22. I don't think that will solve anything because I had our test instance at 3239 before going to 4207 and it didn't have this issue.
I am at wit's end, but before I descend into the Microsoft Support abyss I thought I'd give this Forum a shot...any help appreciated...:)
February 18, 2009 at 4:09 pm
Couple things, are you logging the output of the maint plan? Anythign in there? not SQL Agent, but the text file the plan creates.
Are the server and tools at the same version? Can you open the plan using SSMS on the server and save it there?
February 19, 2009 at 1:22 pm
Thx for the reply...
Yes, the mx plan log has info in there just as the KB article describes, here it is:
***************************************************
NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3239
Report was generated on "XXXXXXXX\XXX".
Maintenance Plan: All Databases
Duration: 00:00:01
Status: Warning: One or more tasks failed..
Details:
Check Database Integrity Task (XXXXXXXX\XXX)
Check Database integrity on Local server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All databases
Include indexes
Task start: 2009-02-15T01:00:05.
Task end: 2009-02-15T01:00:06.
Failed:(0) Alter failed for Server 'XXXXXXXX\\XXX'.
************************************************
I logged onto the server and opened SSMS, was able to save changes to the mx plan. SSMS is version 9.00.3042.00, the server is vesion 9.0.3239. Hope that helps answer your questions...thx! :ermm:
July 28, 2009 at 3:28 pm
I know this is an old post, but I'm having the same problem. Based on research I've already changed:
allow updates to 0
CPU and I/O affinity set to Automatic
Seems others have just gone to using either the AITScripts or some other home grown solution (like the ones here on the site).
I'm on SQL Server 2005 SP 3, haven't applied the cumulative update yet, though.
9.00.4035.00
----------------------------------------------------------------------------
Sacramento SQL Server users group - http://sac.sqlpass.org
Follow me on Twitter - @SQLDCH
----------------------------------------------------------------------------
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply