Relation "NRM_PARTITIONS_rate" does not exist
search cancel

Relation "NRM_PARTITIONS_rate" does not exist

book

Article ID: 192867

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management Network Observability

Issue/Introduction

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

Environment

All supported DX NetOps Performance Management releases

Cause

The Metric Family “Partition” needs to have a Collection associated

 

Resolution

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?

Check to ensure the default "All Servers" Collection Group has members.

Additional Information

If all expected connections between devices in that Collection and the affected Certifications are in place, the errors observed are benign.

Upgrade to r20.2.8 or newer to resolve the errors. They are cleaned up as part of work for defects resolved in 20.2.5 and 20.2.7 releases.