Skip to main content
Question

[4700] [55000] ERROR: Sequence tablename_columnname_seq has not been accessed in the session

  • April 16, 2020
  • 3 replies
  • 11 views

sreeblr
Forum|alt.badge.img+2

Any idea why this error occurs and how to fix.?

3 replies

deepikaym
Forum|alt.badge.img
  • Participating Frequently
  • July 8, 2020

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?


sreeblr
Forum|alt.badge.img+2
  • Author
  • Participating Frequently
  • July 22, 2020

Yes after we had reset permission the error went away.


Jim_Knicely
Forum|alt.badge.img+2
  • Participating Frequently
  • July 22, 2020

Note that you also get this error when calling CURRVAL but not first calling NEXTVAL:

Example:

dbadmin=> CREATE SEQUENCE s;
CREATE SEQUENCE

dbadmin=> SELECT s.CURRVAL;
ERROR 4700:  Sequence s has not been accessed in the session