Quantcast
Channel: Forum SQL Server Database Engine
Viewing all articles
Browse latest Browse all 15889

SQL Server not coming up after a patch upgrade

$
0
0

We installed some windows security patches on windows server 2008 failover cluster on each node one by one. After that SQL Service resources were not coming online.
We found below error in errorlog:

2011-11-11 18:08:09.47 spid7s      Error: 3906, Severity: 16, State: 1.
2011-11-11 18:08:09.47 spid7s      Failed to update database "XXX_Snapshot" because the database is read-only.
2011-11-11 18:08:09.47 spid7s      Error: 912, Severity: 21, State: 2.
2011-11-11 18:08:09.47 spid7s      Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 3906, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.

As it was a UAT environment and customer had no issue in deleting database snapshot, We deleted the database snapshot and brought SQL resources online.

I would like to know is there any alternate way to resolve this issue apart from deleting database snapshots?

Regards,
Ravi Agarwal


Viewing all articles
Browse latest Browse all 15889

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>