CMS Snapshot Analysis - Run Path Builder - Fatal Error - Relation inkb dia expensivepath does not exist

Purpose

This page provides information regarding a fatal error that comes up during Run Path Builder step while taking a snapshot.
The following message can be seen in the Cast-MS.log.txt

INF: 2017-11-07 17:16:27: [SQL] {? = call xxx_local.DDL_TRUNCATETABLE(?) }
INF: 2017-11-07 17:16:27: [SQL] 1: IO integer value
INF: 2017-11-07 17:16:27: [SQL] 2: InKB_DIA_ExpensivePath
ERR: 2017-11-07 17:16:27: [SQL] ERROR: relation "inkb_dia_expensivepath" does not exist
 Where: SQL statement "TRUNCATE TABLE InKB_DIA_ExpensivePath"
PL/pgSQL function xxx_local.ddl_truncatetable(character varying) line 10 at EXECUTE statement
WRN: 2017-11-07 17:16:27: Cleanup for "Run Path builder on "xxx_local"" skipped

Applicable in CAST Version

Applicable RDBMS

Step by Step Scenario

1. Take snapshot (skipping analysis)
2. Error observed during Run Path Builder

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 #10371

Related Pages