Oracle don’t guarantee sequence numbers are generated in order of request. Which means the sequence order is not the same as data insert request order. So you see some small id number but inserted on later time, older id number was inserted on earlier time. However, It can sure that sequences to automatically generate sequential unique integers.
Oracle 中的sequence 并不保证与插入数据的先后顺序保持一致. 在并发的情形下,当某个线程中的数据先提交, oracle 已经分配的序列就会先入库, 造成数据插入顺序与序列顺序不一致。或者线程被rollback ,则序列就会出现skip情况, 将不连续。
https://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_6015.htm#SQLRF01314
ORDER Specify ORDER
to guarantee that sequence numbers are generated in order of request. This clause is useful if you are using the sequence numbers as timestamps. Guaranteeing order is usually not important for sequences used to generate primary keys.
ORDER
is necessary only to guarantee ordered generation if you are using Oracle Database with Real Application Clusters. If you are using exclusive mode, sequence numbers are always generated in order.
NOORDER Specify NOORDER
if you do not want to guarantee sequence numbers are generated in order of request. This is the default.