Hi there, we ran into the above issue over the weekend when installing SP3 on a instance and it seems like the work around is the steps below while you have the failure and master db is corrupt ...
- Start SQL Server service with Trace Flag 902:
- >Net Start MSSQL$InstanceName /T902
- Open SQL Server Management Studio, go to Availability Group and remove SSISDB from the availability databases
- Open New Query, execute the SSIS_hotfix_install.sql script which can be found inInstall folder under \Program Files\Microsoft SQL Server\MSSQL11.MSSQL$InstanceName \MSSQL
-
Stop SQL Server services:
- >Net Stop MSSQL$InstanceName
- Start SQL server service from SQL Server configuration manager
- Add SSISDB back to Availability Group
My question is will it also not work to remove SSISDB from Availability Group and detaching it, before you start installing SP3 ?
With this approach you wont have any issues during your SP3 install.