ALTER SEQUENCE on a busy server results in unexpected very high values
708633Jun 24 2009 — edited Jun 24 2009Our sequence was at 782,393,232 or so, when I bumped it up by 30,000. Here's the commands I used:
alter sequence OUR_SEQ increment by 30000;
select OUR_SEQ.nextval from dual;
alter sequence OUR_SEQ increment by 1;
commit;
When I queried the sequence's nextval a few minutes later, it had jumped to over 8 billion !?! I quickly reset down to 783 million or so, and it behaved propertly after that. I've seen a couple of posts on the net that infer that resetting a sequence while it is being heavily used can cause "unpredictable results". Has anyone else experienced this or is there a known bug ?
I'm running :
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit, RAC system.
PL/SQL Release 10.2.0.4.0 - Production
"CORE 10.2.0.4.0 Production"
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production