Updating nextval in sequence in oracle

Instance 2 has sequence values 21 through 40 in its cache.

Normally, concurrent sessions might generate sequence values in this order: 1, 2, 21, 3, 22, 4, 23, and 24.

Which has the higher priority in your organization: Deploying a new database or securing the ones you already have?

Looking for a website, and resources, dedicated solely to securing Oracle databases? The alternative to sequences used in other RDBMS products is autonumbering and keeping the current number in a table.

' and v_bno= '

Search for updating nextval in sequence in oracle:

updating nextval in sequence in oracle-40updating nextval in sequence in oracle-18

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “updating nextval in sequence in oracle”