June 11, 2012 at 10:19 am
Problem:
I got the error message -
Check Database Integrity Task (MANNASQL2) Check Database integrity on Local server connection
Databases: |database list here|
Include indexes
Task start: 2012-06-09T03:28:56.
Task end: 2012-06-09T03:55:11.
Failed:(-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS " failed with the following error: "Process ID 55 attempted to unlock a resource it does not own: PAGE: 29:1:25771460. Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator.
During undoing of a logged operation in database 'TheDatabase', an error occurred at log record ID (6729214:1576:425). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
A database snapshot cannot be created because it failed to start.
A database snapshot cannot be created because it failed to start.
The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.
The database could not be exclusively locked to perform the operation.
Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
I located the MSDN article:
http://msdn.microsoft.com/en-us/library/aa337285(v=sql.105).aspx
I am running DBCC on the DR machine, a restore from a few days ago on our staging machine, and our Net Admin is copying the backups from last night to the Stage server so I can do a restore and test. I will be doing DBCC later tonight on the production server, off business hours.
Background:
2005 SP4 Standard.
DBCC runs once weekly.
No previous error from previous weeks.
Windows system and application logs gave no additional information.
Anyone seen this error message WITHOUT any notification of a suspect database?
I will try to rerun DBCC on the production as stated, off normal hours of operation, but I am curious what I might see when I do as a heads up. Just trying to get a game plan. I have looked over the beautiful interwebs knowledge base but am lacking anything that is spot on and tells of resolution. All other testing has completed without problems and the system has been up for two days without any reported errors seen. All other logs look clean, all backup directories look clean and plenty of space allocations ready to dump files. Database that failed is only about 235GB size, on Raid 10, transferring to Raid 0. Have not seen this in the year of being here. New datamart/warehouse snapshots were recently added, though did not affect the checkdb process last weekend.
June 22, 2012 at 9:37 pm
Do you get this error everytime you run it on that database or just the one time? What edition of SQL? If using Enterprise Edition, can you create a snapshot manually? If so, run DBCC CheckDB on the snapshot and see if it works.
June 23, 2012 at 4:13 pm
I lost the fought on the maintenance window from business and waited until the weekly production check. Everything is good, no errors recurring after the weekend audits. Thanks!
July 9, 2012 at 10:21 am
Dang, happened again one month later after weeks of success. Unfortunately, from what I learned last time I spent time investigating; I really have no control to get any files for this to a test environment nor to execute dbcc on production outside my weekend window.
2005 SP4, Standard - with all primary databases on the same RAID 10, 8 disk volume. A DBCC even from snapshot would slow the IO down too far during weekday operations, even in maintenance periods, to allow for good normal operation on data input and output. Only time I really can run the DBCC stuff due to IO stress is on the weekend, when it is scheduled to run.
I checked for auto growth thinking maybe the files where in a growth, but saw nothing for that particular database.
Related found content:
July 9, 2012 at 12:26 pm
You may need to contact PSS to see if it's possible to get a hotfix for this.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply