Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Vice Admiral Vice Admiral
Vice Admiral

/var/opt/OV/log/pvhibernate.log => Relation "pg_class" does not exist

This is showing up more than a few times.  Anyone know what this means and make it go away ?


May 14 14:48:03 - ERROR - could not get database metadata
java.sql.SQLException: [Vertica][VJDBC](4566) ERROR: Relation "pg_class" does not exist
at com.vertica.util.ServerErrorData.buildException(Unknown Source)
at com.vertica.dataengine.VQueryExecutor.executeSimpleProtocol(Unknown Source)
at com.vertica.dataengine.VQueryExecutor.execute(Unknown Source)
at com.vertica.jdbc.SStatement.executeNoParams(Unknown Source)
at com.vertica.jdbc.SStatement.executeQuery(Unknown Source)
at org.hibernate.tool.hbm2ddl.DatabaseMetadata.initSequences(
at org.hibernate.tool.hbm2ddl.DatabaseMetadata.<init>(
at org.hibernate.tool.hbm2ddl.DatabaseMetadata.<init>(
at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(
at com.hp.reporter.db.HibernateManager.updateSchema(Unknown Source)
at com.hp.reporter.db.HibernateManager.<init>(Unknown Source)
at com.hp.reporter.db.HibernateManager.getInstance(Unknown Source)
at com.hp.reporter.db.HibernateHelper.executeSQLListQuery(Unknown Source)
at Source)
at Source)
at com.hp.pv.alerts.AlertAdapter.getLatestAlerts(Unknown Source)
at Source)
at java.util.concurrent.Executors$
at java.util.concurrent.FutureTask.runAndReset(
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(
at java.util.concurrent.ScheduledThreadPoolExecutor$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
Caused by: com.vertica.util.ServerException: [Vertica][VJDBC](4566) ERROR: Relation "pg_class" does not exist
... 24 more

Labels (1)
Tags (1)
2 Replies
Captain Captain



We have vPV installed on RHEL 6.2 and we're facing this same problem.

Did you get to fix this issue?


Thanks and best regards,


Paulo Ferreira

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor



I guess this error is not resulting in any funcationality impact and you can safely ignore the exception in log file.


Currently there is no support for Vertica dialect from Hiberanate.  This request is still in open state.

Using postgresql dialect works for Vertica as well with exception logged in log file.


Note: Postgres dialet is compatible with Vertica.   Dialect is a Hibernate feature that generate the appropriate SQL for a chosesn database for Java applications.  Since vPV uses Vertica DB resulting exception in log file.




The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.