CMS Snapshot Analysis - Create Snapshot Definition - Fatal Error - Relation dss central selection does not exist

Purpose

This page provides information regarding a fatal error that comes up during the step “Finalize Dataflow Security” while taking a snapshot.
The following error message ERROR: relation “dss_central_selection” does not exist can be seen in the Cast-MS.log.txt.

ERROR: relation "dss_central_selection" does not exist
                              Where: SQL statement "truncate table DSS_CENTRAL_SELECTION"
                              PL/pgSQL function dss_definesnapshot(timestamp without time zone,character varying,character varying) line 18 at SQL statement
                              org.postgresql.util.PSQLException:ERROR: relation "dss_central_selection" does not exist
  Where: SQL statement "truncate table DSS_CENTRAL_SELECTION"

Observed in CAST AIP

Observed on RDBMS

Step by Step Scenario

1. Take snapshot (skipping analysis)
2. Error observed during Create Snapshot Definition step

Action Plan

If the SQL error is related to a non-existing table or non-existing column (example : “Relation xxxx does not exist” ot “Column xxx does not exist”), the root cause is likely to be a known vulnerability in Cast-MS that will be fixed in Service Pack 8.2.9

If user defines a Tool after module generation and sets the search path to the Central Base instead of the Local Base, then all the SQL queries and procedures in the further steps may be affected.

To remedy the situation,

1. Remove any “set search_path = xxx” in the scripts registered as “Tools after module generation”
2. Prefer prefixing all involved tables, views and procedures with the name of the local base.
3. Relaunch snapshot

Relevant Input

Sherlock (CAST Support Tool (CST) - alias Sherlock) : Option to select are Export Logs and Export Database (MB only). Since issue occurs during the snapshot computation, source code is not requested because analysis is already done.

Notes/comments

Ticket # 10372

Related Pages