ORDER or NOORDER? If the sequence is not cached then Oracle has to find
the last number generated and generate the next one. If the sequence is
ordered (default) then Oracle must satisfy the first request for NEXTVAL
before it can go on to the next request. If order is not important try
Title: RE: Problem with sequence and row cache lock
Thanks for the reply, but it seems to be the problem you're describing is exactly
what sequences are there for - to prevent serialization and eliminate this type
of waiting.
The sequences is ORDERED, BTW.
-Original Message-
From
