Message error in Vertica log file:
2020-06-09 10:41:55.055 Init Session:7f523ffff700-a0000001b92e9c <ERROR> @v_datarepository_node0001: 42V01/4566: Relation "NRM_PARTITIONS_rate" does not exist
LOCATION: throwRelationDoesNotExist, /scratch_a/release/svrtar14870/vbuild/vertica/Catalog/CatalogLookup.cpp:3673
DA message error:
ERROR | 53395527-1520856 | 2020-06-09 10:41:55,061 | ExceptionLog | .ca.im.core.util.ExceptionLogger 99 | m.ca.im.common.core.util | | A NEW application exception occurred
PreparedStatementCallback; bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: [Vertica][VJDBC](4566) ERROR: Relation "NRM_PARTITIONS_rate" does not exist
org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: [Vertica][VJDBC](4566) ERROR: Relation "NRM_PARTITIONS_rate" does not exist
…
Caused by: java.sql.SQLSyntaxErrorException: [Vertica][VJDBC](4566) ERROR: Relation "NRM_PARTITIONS_rate" does not exist
…
Caused by: com.vertica.support.exceptions.SyntaxErrorException: [Vertica][VJDBC](4566) ERROR: Relation "NRM_PARTITIONS_rate" does not exist
... 72 more
The Metric Family “Partition” needs to have a Collection associated
Release : 3.7
Component : IM Reporting / Admin / Configuration
Check if the Metric Family “Partition” has the one Monitor Profile associated?
And if the Monitor Profile (in this example is the Physical Server) has a Collection associated?