Skip to main content

Knowledge Document: [Vertica] SELECT SYNC_CATALOG does not sync secondary subcluster catalog

  • September 24, 2025
  • 0 replies
  • 1 view

coest_opentext_com
Forum|alt.badge.img

Environment

Vertica Version 12.0.x-x and higher

Situation

After running SELECT SYNC_CATALOG(); the subcluster "sub-cluster1" catalog is not in sync (below), The "default_subcluster" however looks ok.

SELECT * from CATALOG_SYNC_STATE;

node_name sync_catalog_version earliest_checkpoint_version sync_trailing_interval last_sync_at

v_vmart_node0001 25374670 25303451 1 2025-09-22 14:26:56
v_vmart_node0002 25374670 25303451 1 2025-09-22 14:26:56
v_vmart_node0003 25374670 25303451 1 2025-09-22 14:26:59
v_vmart_node0007 25374670 25303451 1 2025-09-22 14:26:57
v_vmart_node0008 25374670 25303451 1 2025-09-22 14:26:56
v_vmart_node0009 25374670 25303451 1 2025-09-22 14:26:56
v_vmart_node0010 -1 -1 25374672 1999-12-31 19:00:00
v_vmart_node0011 -1 -1 25374672 1999-12-31 19:00:00
v_vmart_node0012 -1 -1 25374672 1999-12-31 19:00:00
v_vmart_node0013 -1 -1 25374672 1999-12-31 19:00:00
v_vmart_node0014 -1 -1 25374672 1999-12-31 19:00:00
v_vmart_node0015 -1 -1 25374672 1999-12-31 19:00:00

Find complete article on support portal