declare
sqlstmt varchar2(200);
begin
for x in (select sequence_name from user_sequences) loop
sqlstmt := ‘alter sequence ‘||x.sequence_name||’ increment by 10′;
execute immediate sqlstmt;
sqlstmt := ‘declare retval number(10); begin select ‘||x.sequence_name||’.nextval into retval from dual; commit; end;’;
execute immediate sqlstmt;
sqlstmt := ‘alter sequence ‘||x.sequence_name||’ increment by 1′;
execute immediate sqlstmt;
end loop;
end;

I know this is not very clean code, but it seems that a nextval does not work in a pure select statement in execute immediate function.

We have development databases for all of our developers. Each developer gets a sandbox to play in. Some of them play with more sand than others, so their sequence numbers are higher. We have a base data set that gets updated periodically that the developers use to refresh their data periodically to a known, good state. This, unfortunately, results in occasional tromping of sequence numbers. I have tried to build a procedure to step them, but it still does not work.

declare
sqlstmt varchar2(200);
begin
for x in (select sequence_name from user_sequences) loop
sqlstmt := ‘alter sequence ‘||x.sequence_name||’ increment by 100′;
execute immediate (sqlstmt);
sqlstmt := ’select ‘||x.sequence_name||’.nextval from dual’;
execute immediate (sqlstmt);
sqlstmt := ‘alter sequence ‘||x.sequence_name||’ increment by 1′;
execute immediate (sqlstmt);
end loop;
end;

This doesn’t do anything to the sequences, so I am relegated to running the scripts individually.

alter sequence id_sequence increment by -142900;

More info:
http://www.jlcomp.demon.co.uk/faq/resetseq.html