I have a very high transaction database I have multiple sequences to unique generate numbers for different outlets.

One of the outlets started receiving errors because i have a unique constraint on a table to prevent duplicates. The sequence that generates the numbers rolled back more than 10 numbers.

I can afford for this to happen again because it stops sales and I currently have over 70 sequences and going to added more as the months go by.

Has anyone ever experienced this before and how can i stop this from happening in the future ?

any help would be appreciated .. thanks


There is a known issue in some circumstances.

As far as I can see, you need to use NO CACHE so numbers cannot be reused

| improve this answer | |
  • Thank you but I am concerned that using No CACHE may affect performance. I will do more research on this. Thanks again – Yugz Dec 12 '14 at 7:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.