NSX Flow statistics and Rule hit statistics fail to load with the error: "Unknown Error Occurred. Please look into tech support logs"

Products

• VMware NSX

Issue/Introduction

Symptoms:
After restoring NSX Manager from backup, flow statistics and rule hit statistics fail to load with an error "Unknown Error Occured. Please look into tech support logs".



In vsm.log, you see entries similar to:
 

2020-03-31 14:58:56.778 GMT ERROR http-nio-127.0.0.1-7441-exec-980 SqlExceptionHelper:131 - ERROR: materialized view "firewall_rule_stats_mv" has not been populated

  Hint: Use the REFRESH MATERIALIZED VIEW command.

2020-03-31 14:58:56.779 GMT ERROR http-nio-127.0.0.1-7441-exec-980 FirewallFacadeImpl:1124 - - [nsxv@6876 comp="nsx-manager" errorCode="MP100046" subcomp="manager"] Exception :

org.springframework.orm.jpa.JpaSystemException: org.hibernate.exception.GenericJDBCException: could not extract ResultSet; nested exception is javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could no

t extract ResultSet

        at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:418) ~[spring-orm-4.3.17.RELEASE.jar:4.3.17.RELEASE]

        at org.springframework.orm.jpa.aspectj.JpaExceptionTranslatorAspect.ajc$afterThrowing$org_springframework_orm_jpa_aspectj_JpaExceptionTranslatorAspect$1$18a1ac9(JpaExceptionTranslatorAspect.aj:37) ~[spring-aspects-4.3.17.RELEASE.

jar:4.3.17.RELEASE]

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

After a restore of NSX Manager, materialized view become unscannable. When a pg_restore occurs, which is a part of NSX restore operation, materialized view is refreshed with no data. A manual refresh of the table fixes the issue.

Resolution

This issue is resolved in VMware NSX for vSphere 6.4.5

Workaround:
To work around this issue if you do not want to upgrade, contact Broadcom Support and note this Knowledge Base article ID-317725 in the problem description.