Hemant,
I would guess that this is true if you are caching values for the sequence.
Each database instance might cache the same set of values.
Turn sequence caching off, and I would think that the problem goes away.
Havn't tried this in awhile, but it makes sense.
Tom Mercadante
Oracle
me don't think so.
Raj
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts, having an opinion is an art !
-Original Message-
In the Oracle9i Real Application Clusters Administration manual, there is a chapter
about sequence numbers generator. Before believing to the snake oil sellers, read
the fine manual. Sequence numbers are guaranteed to be unique PER DATABASE. What
they're
not guaranteed is to come in ordered
Sequences are mastered by the single SYS.SEQ$ table in each
database. Cached or uncached, RAC or non-RAC, OPS or
non-OPS, sequence numbers generated by this mechanism are
unique across a database, not by instance. Each instance
updates SEQ$ as individual numbers (noncached) or ranges of
numbers
Yes, I've been aware of the difference between ORDERED and CACHED.
However, the Builder.Com article quite explicity asserts
Sequence generator numbers are guaranteed to be unique only for a single
instance, which is unsuitable for use as a primary key in parallel or
remote environments, where a
