I have a table whose primary key alway picks up the sequence number. But somehow, rightnow my primary key has value even bigger than the current sequence number. I want to know how it could be possible. Any reasons it can make this happen. I need to find the resaons ASAP. Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Guess that you mean "at the time of creating the sequence, not the index", right.
Also what you mean by "seems some app design prob" and also can you list the ways which could cause the number greater than currval?
Actually excluding other reasons, even you used NOCACHE option and it may have few intervals between the numbers, but should not cause the number greater than currval. Thanks.
A Sequence can be put into a column of an inserted row either through a Before Insert Trigger or directly by an application by referring to the sequence.nextval in the insert statement.
If you are using the second method then anyone not going through the application can directly insert records with whatever values in that column.
You have not mentioned how > "primary key alway picks up the sequence number".
If the design is already good, To avoid the problem in production , you can drop the sequence and create another sequence with the same name while the starting value of the sequence is greater than the largest value in your table. this helps you to pick up the primary key from the sequence for new records being entered without changing the application code.
Hope this helps.
Business Accounts
Answer for Membership
by: orageniusPosted on 2004-09-27 at 10:10:43ID: 12162230
if you havnt used NOCACHE option at the time of creating the index then it may have few intervals between the numbers but there should be any way the number can be greater than currval. seems some app designe prob.