First I created a sequence with any name. I ran the nextval and currval command and it's working perfectly, but...
the problem starts when I try to create another sequence with the same name. As expected it won't create a new sequence, as the object already exists, but what it does is give junk values to the already created sequence. Ideally it shouldn't touch the previous sequence but here it does.
If anybody has any idea why it does, I would like to hear it. Thanks.
Are you using the "cache" option for the sequence definition? If so, there are known issues:
In any case, getting a "sequence already exists" message should not corrupt the existing sequence. I would log an iTar on Oracle MetaLink and see if there is a bug.
Dig Deeper on Oracle database design and architecture
Related Q&A from Don Burleson
Suppose you have a table which has only two columns, namely locid (not primary) and place. In Oracle, which query should I run to get the output as ...continue reading
I have created a table, Party, and in it there are two main fields, party_code and party_name, and around 2,500 records are available in it. I passed...continue reading
I have a query that retrieves around 10 records. I have a task to concatenate the values separated with ','. I would like to know if Oracle has any ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.