So far we haven't gotten into a problem of locking, there are about 15-20
users of the system.
-Original Message-
Sent: Thursday, July 18, 2002 8:28 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Sequence number generation
I really don't see where t
trigger in which you fetch from
sequence you select from table. To keep it synchronized with the
transaction, we make counter table block
HTH!
Aleem
-Original Message-
Sent: Thursday, July 18, 2002 11:48 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Sequence number
additional coding, the trigger in which you fetch from
> sequence you select from table. To keep it synchronized with the
> transaction, we make counter table block
>
> HTH!
>
> Aleem
> -Original Message-
> Sent: Thursday, July 18, 2002 11:48 AM
> To: Multiple re
h you fetch from
> sequence you select from table. To keep it synchronized with the
> transaction, we make counter table block
>
> HTH!
>
> Aleem
> -Original Message-
> Sent: Thursday, July 18, 2002 11:48 AM
> To: Multiple recipients of list ORACLE-L
> Subject:
from table. To keep it synchronized with the
transaction, we make counter table block
HTH!
Aleem
-Original Message-
Sent: Thursday, July 18, 2002 11:48 AM
To: Multiple recipients of list ORACLE-L
Subject:RE: Sequence number generation
It is not possible to avoid sequence
It is not possible to avoid sequence number loss .
If a user requests a sequence number, then ultimately rolls back that
transaction,
that sequence number is lost .
However you can catch such lost sequence numbers programatically and reuse
then.
that would require a bit of extra coding.
-Ori
Generate the sequence with option NOCAHCE
The cached values of the sequences are lost if the shared pool is flushed.
Sanjay
-Original Message-
Sent: 18 July, 2002 1:13 PM
To: Multiple recipients of list ORACLE-L
Hi
Is it possible to avoid sequence number loss in the sequence number
gen
