How to solve an SSIS Deployment Error

Tags:
Oracle,
Technical Track
Problem:
You are deploying a SQL Server Integration Services Package to the SSIS Catalog and it keeps on failing with the following error:
Cause:
You receive the main error when either your server is actually running out of resources and the external assemblies or modules (like CLRs and external stored procedures) could not run because there is no more memory/cpu available. But more often than not, it is because those external calls were not registered properly or marked as safe. SSIS package deployment calls a number of external assemblies during deployment of packages. Since these packages are saved inside the SSISDB database, the database must be set to "Trustworthy" or else external calls will fail. The Trustworthy property of the database lets SQL Server know whether it can trust the contents of the databases and its calls. By default, the property is off for any databases except msdb. You can understand more about this property here.Fix:
To address this specific error, you'll need to set the Trustworthy property of SSISDB to ON:select name,is_trustworthy_on from sys.databases where name= 'SSISDB' ALTER DATABASE SSISDB SET TRUSTWORTHY ON; select name,is_trustworthy_on from sys.databases where name= 'SSISDB'