Data360 Analyze

I am baffled...

I have a stored proc, that the first thing it does is insert a row into a table (which creates an ID from a sequence)

When I run it from D360 the sequence jumps by 20... 

When I run it in SQL Dev it increases by 1 as it supposed to do.

I cannot determine why?? anyone have ANY clue?

If this is Oracle, then there are some strange cache behavior, even when you have nocache set in the sequence definition, especially when different users are used to insert rows. The default sequence cache for oracle is 20.

In a developer session, you will probably always have the sequences cached and then you will see mostly incremental behavior. If its really bothering you, you can implement your own sequence allocation on a trigger, but there are pitfalls in doing this. Another thing to try would be to use identity columns instead. It works mostly the same but means that you have less objects to manage, and might have different cache behaviors. 

Good luck.

I am baffled...

I have a stored proc, that the first thing it does is insert a row into a table (which creates an ID from a sequence)

When I run it from D360 the sequence jumps by 20... 

When I run it in SQL Dev it increases by 1 as it supposed to do.

I cannot determine why?? anyone have ANY clue?

I am baffled...

I have a stored proc, that the first thing it does is insert a row into a table (which creates an ID from a sequence)

When I run it from D360 the sequence jumps by 20... 

When I run it in SQL Dev it increases by 1 as it supposed to do.

I cannot determine why?? anyone have ANY clue?

Hi Geoff, how do you call the stored proc in D360?

I am baffled...

I have a stored proc, that the first thing it does is insert a row into a table (which creates an ID from a sequence)

When I run it from D360 the sequence jumps by 20... 

When I run it in SQL Dev it increases by 1 as it supposed to do.

I cannot determine why?? anyone have ANY clue?