August 19, 2013 at 3:05 am
Hi ,
On one of the production box , I am facing the below error while running the weekly maintenance job :
ERROR :
Msg 5030, Level 16, State 12, Server XXX , Line 1
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Server XXX , Line 1
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.
Outcome: Failed
Duration: 00:00:20
COMMAND which is getting execute on the back end :
Command: DBCC CHECKDB ([DB Name]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY
This error is coming for MSDB Database and couple of user databases as well . For some of the databases the maintenance job is running fine , only for few databases the error is coming.
I grantd the SQL SERVER& AGENT account full permissions in the MDF/LDF file path but this doesn't seems to be permission issue. There is no error log entry which is getting generated while the job fails.
Also the job is running on SQL 2005 Standard edition (9.0.5057) , hence manually taking snapshots is not possible.
Please help !!!!!!!!!!!
August 19, 2013 at 3:16 am
Can you check and see if the commands are being blocked by other (long-)running queries?
August 19, 2013 at 3:24 am
There is no blocking traced on the back end. Its a Share point instance and around 200 sleeping connections are present as of now.
August 19, 2013 at 6:14 am
August 19, 2013 at 6:20 am
What's in the SQL Server error log?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 19, 2013 at 6:47 am
The solution explained in the Link cannot be implemented in this case as SQL Standard edition is running and hence no snapshots can be taken .
August 19, 2013 at 7:01 am
Still we are having the same issue..Job failing..Please help us to fix the issue.
August 19, 2013 at 7:25 am
GilaMonster (8/19/2013)
What's in the SQL Server error log?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 19, 2013 at 7:28 am
Job completed successfully after giving the Full rights to Sql server account..Thanks every one for your instant help
🙂
August 20, 2013 at 4:34 am
Are you using different account for SQL server and agent? why?
Regards
Durai Nagarajan
August 20, 2013 at 6:18 am
Yes Durai,
We are using the different account for both server and agent..
August 20, 2013 at 7:53 am
but what is the reason behind that
Regards
Durai Nagarajan
August 20, 2013 at 9:10 am
Well, different accounts for different services is the standard recommendation. I know most people just ignore the recommendation though.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2013 at 12:45 am
Gail,
Just a thought, both services are managed by DBA and all SQL service account will be with DBA what wrong in giving the same account.
Regards
Durai Nagarajan
August 21, 2013 at 1:12 am
Potentially quite a lot, but as I said, most people ignore this recommendation and use one account for every single SQL Server service they have.
http://msdn.microsoft.com/en-us/library/ms144228%28SQL.105%29.aspx#isolated_services
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply