When you use Cumulative Update 9 (CU9) for SQL Server 2017 on Linux, you may notice that SQL Server instance can't start and gets hung in script upgrade mode for the database SSISDB with the following error:
Database 'master' is upgrading script 'ISServer_upgrade.sql' from level 0 to level 500.
Starting execution of ISServer_upgrade.SQL
Taking SSISDB to single user mode
Setting database option SINGLE_USER to ON for database 'SSISDB'.
CREATE NONCLUSTERED INDEX [index_tasks_ReadyForDispatchTime] ON [internal].[tasks] ([ReadyForDispatchTime] ASC) INCLUDE ([CreatedTime], [CreateWorkerAgentId], [ExecutedCount], [ExpiredTime], [InputData], [IsCritical], [JobId], [LastUpdatedTime], [MaxExecutedCount], [Priority], [Status], [TaskType]) WITH (ONLINE = ON)
CREATE NONCLUSTERED INDEX [index_tasks_Status] ON [internal].[tasks] ([Status]) INCLUDE ([ExecutedCount], [ExpiredTime], [IsCancelled], [MaxExecutedCount], [WorkerAgentId]) WITH (ONLINE = ON)
The module 'enable_scaleout' depends on the missing object 'internal.update_logdb_info'. The module will still be created; however, it cannot run successfully until the object exists.
CLR version v4.0.30319 loaded.
Common language runtime (CLR) functionality initialized.
AppDomain 2 (SSISDB.dbo[runtime].1) created.
Error: 10342, Severity: 16, State: 100.
Assembly 'Microsoft.SqlServer.IntegrationServices.Server' cannot be loaded because this edition of SQL Server only supports SAFE assemblies.
Error: 912, Severity: 21, State: 2.
Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 10342, state 100, severity 25. 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.
SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: