After you apply Hot Fix 4, if your deployment configuration is schemaPerTenant, the svi-alert service does not start. It fails because some views that are expected by the svi-alert service have not been created. They are created when your deployment configuration is databasePerTenant.

In the svi-alert log, you see the following error information:

To work around the problem, run the script on the Full Code tab.

For more information about Hot Fix 4, see the release notes.

Operating System and Release Information

DO
$$
DECLARE alert_schema text;
        view_name text;
        dummy_views text[] := '{tdc_assignment_view,tdc_extended_scenario_fired_event}';
BEGIN
  FOR alert_schema IN SELECT schema_name FROM information_schema.schemata WHERE schema_name LIKE 'svi_alert%'
  LOOP
    FOREACH view_name IN ARRAY dummy_views
    LOOP
      IF NOT EXISTS (SELECT * FROM information_schema.tables 
        WHERE table_type = 'VIEW' AND table_name = view_name 
        AND table_schema = alert_schema) THEN 
          EXECUTE 'CREATE VIEW ' || alert_schema || '.' || view_name || ' AS SELECT 1;';
          RAISE NOTICE USING MESSAGE = 'Creating dummy view ' || view_name || ' in schema ' || alert_schema;
      END IF;
    END LOOP;
  END LOOP;
END;
$$;

Viya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at

An update for this issue is available for SAS Visual Investigator 10.7. For instructions on how to access and apply these software updates, see the documentation links at the top of