1

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

asked Dec 11, 2014 at 10:35
0

1 Answer 1

1

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

answered Dec 11, 2014 at 12:17
1
  • Thank you but I am concerned that using No CACHE may affect performance. I will do more research on this. Thanks again Commented Dec 12, 2014 at 7:23

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.