I noticed that if there is "assertion failed"-error, then restore the database from backup copy and current log (for example, using -a database option) incorrectly restores the currval/nextval of sequence.
asked 09 Aug '16, 10:10
If your sequence definition is not declared with a NO CACHE clause there is a possibility this can happen. Fatal errors, assertions, power outages, unhandled systems exceptions could all cause the server to stop without a clean checkpoint.
If your 'gap' is less than the default 100 values (or whatever you have your CACHE setting set to) then the above could be your issue.
If your 'gap' is larger I would suspect an incomplete (-a) recovery.
answered 09 Aug '16, 12:50
Nick Elson S...