May 17, 2017 at 2:23 pm
I installed SP1 CU3 on the non-active node which was successful. When I attempted to fail over SQL Server, the SQL Server service would not come online and instead fail back to the original node. Here are the error messages that I noticed:
Event Viewer:
Event ID: 912
Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 3930, 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.
Event ID: 3417
Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
SQL Server Logs:
Error: 3930, Severity: 16, State: 1
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
Error: 912, Severity: 21, State: 2
Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 3930, 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.
Error: 3417, Severity: 21, State: 3
Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
I finally got it to work by applying -T902 in the startup parameters for the SQL Server service. I highly doubt that is the fix.
Has anyone experienced this before? I'm afraid to apply SP1 CU3 on the prod active nodes...
Thank you.
May 18, 2017 at 7:33 am
I wonder if the issue is because I moved the System databases onto the SAN?
Or is it because the system databases aren't in the "MSSQL10_50.MSSQLSERVER/MSSQL/Data" folder structure. I placed my system databases on "SystemDBs/SystemDBs"...
This issue is completely baffling to me. The CU upgrade works on standalone SQL Servers, but not the clustered SQL Servers with AGs.
If I SQL failover the databases onto the SQL Server 13.0.4435.0 instances, do I have to attempt an CU upgrade on the former SQL instances which are 13.0.4411.0?
May 18, 2017 at 8:30 am
have you moved the databases post the sql server installation?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply