Home > database >  Oracle sequence set the cache size lead to jump?
Oracle sequence set the cache size lead to jump?

Time:02-04

Cache is cached rushed out, convert into set to '1' can thoroughly solve the problem, and what is wrong???

CodePudding user response:

This cache resize to 1, just reduce the number of scenarios,

Is it common has the following several:
1, after the cache is not used for a long time, or restart the instance, and coincided basically with the description of the building Lord,
2, the implementation of the insert into the t () values (seq. Nextval) later, did the transaction rollback,
3, multiple tables (or more) using the same sequence,
4, deleted already submitted data in the table,

PS: since this increases the number of actual business have any effect, or just look nice (ocd)
If is business requirements must be continuous, it can't use sequence to generate the serial number,
  • Related