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 "inkb_dataflowscopes" does not exist can be seen in the Cast-MS.log.txt.
INF: 2017-11-07 14:34:10: [SQL] {? = call odh_local.KB_DecodeGuidForDataFlow() }
INF: 2017-11-07 14:34:10: [SQL] 1: IO integer value
ERR: 2017-11-07 14:34:10: [SQL] ERROR: relation "inkb_dataflowscopes" does not exist
Where: PL/pgSQL function odh_local.kb_decodeguidfordataflow() line 8 at SQL statement
Release | Yes/No |
|---|---|
| 8.3.x, x < 2 |  |
| 8.2.x, x < 8 | |
| 8.1.x | |
| 8.0.x | |
| 7.3.x | |
RDBMS | Yes/No |
|---|---|
| Oracle Server | |
| Microsoft SQL Server | |
| CSS2 | |
- Take snapshot (skipping analysis)
- Error observed during Finalize Dataflow Security step
Users should not run queries on the Central Base using "Tools after module generation". Refer to official documentation for details about the tool editor CMS - Tool editor
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,
- Remove any "set search_path = xxx" in the scripts registered as "Tools after module generation"
- Prefer prefixing all involved tables, views and procedures with the name of the local base.
- 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.
Ticket # 10371
