July 16, 2014 at 7:54 am
Hello,
I have just install the SP2 for SQL2012 on a server with AlwaysOn and Availability Group.
After the update on the replica, in the server log, there is the following message for all databases that are in an availability group :
System objects Could not be updated in database 'X' Because it is read-only.
...
Did I do something wrong?
How to be sure that all update scripts have been successfully applied?
Is there special scripts in the SP2?
thx
July 17, 2014 at 1:03 am
Can you please elaborate ?
Cheers,
- Win
"Dont Judge a Book by its Cover"
July 17, 2014 at 2:23 am
... after applying the SP2 "SQLServer2012SP2-KB2958429-x64-ENU", there is the above message in the SQL Server log !!!
what do you want more?
July 18, 2014 at 7:19 am
I believe service packs cannot be applied on read only databases. Maybe someone knows 100% for sure. I know this was the case in much older versions of SQL Server.
if you run a select @@version you can tell of the brains of SQL Server were upgraded to SP2.. .but as far as all of the databases look at the .log file for the SP2 apply.. which you might be looking at now anyway.
July 18, 2014 at 8:10 am
The problem is that as Microsoft said, (http://msdn.microsoft.com/en-us/library/dn178483(v=sql.110).aspx), I must apply the SP to the secondary replica first, but on this server, databases are in read-only mode !!!
July 19, 2014 at 6:33 am
My guess is that when you installed the service pack on the secondary, the databases involved in AG were not updated as the message said. If they were then the AG would be out of sync(primary would not match secondary). Your system databases and any non-AG databases should have been upgraded. When you upgrade you primary instance, I would think secondary AG databases will be upgraded at that point. That is why Microsoft says you have to secondary first. If you did it in the reverse order that the secondary DB would try to update on an instance that doesnt support it.
*Full disclosure: I don't have any production experience with AG but this is how it would work with log shipping where the secondary database is non writable.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply