Any idea why this error occurs and how to fix.?
Hi, did you check the table and Cloumn's permission which is seeing this?
Is the transaction run using dbadmin ort another user who is not having access to the table?
Yes after we had reset permission the error went away.
Note that you also get this error when calling CURRVAL but not first calling NEXTVAL:
dbadmin=> CREATE SEQUENCE s;
dbadmin=> SELECT s.CURRVAL;
ERROR 4700: Sequence s has not been accessed in the session
Can't find what you're looking for? Search the Vertica Documentation, Knowledge Base, or Blog for more information.