Thanks for the question, Eric.
Asked: April 05, 2017 - 2:05 pm UTC
Last updated: April 06, 2017 - 4:36 am UTC
Version: 12.1.0.2
Viewed 1000+ times
You Asked
We recently ran into an issue where altering a sequence resulted in an invalid number, a negative number. Working with Oracle Support, we came across this, Bug 5881343: ALTERING "INCREMENT BY" VALUE FOR A SEQUENCE CORRUPTS LAST_NUMBER
This bug was last updated over 10 years ago, published for a version of the database that is 2 major revisions behind and for a version of the OS that is 32-bit. So, needless to say, is quite old.
The workaround is a bit odd, "Don't ever alter a sequence."
Curious your thoughts on this bug. If we are never supposed to alter sequences, then why are these commands still allowed?
Regards,
Eric
and Connor said...
Is this answer out of date? If it is, please let us know via a Comment