The issue with databases that live in an Always-On Availability Group is that they can’t be “Altered”. The patching script is trying to alter the database and set the log to simple. This causes an error. The work around is below but causes us to add extra steps to the patching process. Can you find a way to patch and stop alter the database log method?

Fix:
So the solution for this particular problem scenario is to remove the Usage Logging database from the Availability Group while you are patching. You can do this safely, assuming that you have all your service applications configured to point to the availability group listener so that you can continue to access the databases while patching. The other important points are that you must remove the database from the primary replica and that you make a backup of the primary replica just in case something goes wrong. Once your patching has been successful across all nodes in the farm, you must then re-add the Usage Logging database back to the Availability Group.