Why TIBCO Data Virtualization's users get the error 'duplicate key value violates unique constraint "system_tables_pkey"' and how to resolve it?

Why TIBCO Data Virtualization's users get the error 'duplicate key value violates unique constraint "system_tables_pkey"' and how to resolve it?

book

Article ID: KB0070048

calendar_today

Updated On:

Products Versions
TIBCO Data Virtualization All supported versions

Description

This error typically occurs when adding a node to a cluster. Although the node may be added successfully, attempting to create a view in the cluster results in the following error message


User-added image

 ERROR [WorkerThread-Low-10697] 2024-04-01 10:15:46.652 +0800 NewClusterNode - FAILED TO APPLY CHANGE: {-1385247125:9346}(false) - Cause: ERROR: duplicate key value violates unique constraint "system_tables_pkey" Detail: Key (table_id)=(1200194) already exists. ... Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "system_tables_pkey" Detail: Key (table_id)=(1200194) already exists.
 
This issue arises due to discrepancies between the metadata repository of the particular node and the rest of the cluster. Normally, when a node is added to the cluster, the current schema of node is automatically dropped, and metadata is imported from the timekeeper. However, if this process does not occur automatically, it must be done manually.

Issue/Introduction

This KB explains why TDV users encounter the issue 'duplicate key value violates unique constraint "system_tables_pkey"' and provides the solution to resolve this error.

Environment

All supported environments

Resolution

TDV users can follow the steps outlined in the KB article below to drop and recreate the TDV repository, which will resolve the issue: https://support.tibco.com/s/article/000040942