Re: sequence #'s skipping

Related question...when doing replication, I need to use offsetting sequences (location 1 uses 11/21/31/41..., 2 uses 12/22/32/43...).

Can I use caching and not loose my interval setting? Sounds like caching subjects the interval to being reset to start on next highest 10 rounded. If this is true, this could really foul up a replicated table where the primary key must have offsetting numbers.

Steve Lehrfeld wrote:
>
> we found that Oracle 7 skips sequence #'s after it has been reset. It
> always rounds to the nearest twenty, i.e. 10001, 10002, <reset>, 10020,
> 10021, 10022, <reset>, 10040, etc.
>
> Does anyone know why it does this and how to prevent it?
>
> -steve
 

-- 
Gary Melhaff
Senior Database Analyst
Weyerhauser Corporation