Trust me on this one -- there is exactly ONE way to sort of get the last row inserted.
You MUST have some column that you can order by.
Rowid - won't work. Its based on flie/block/slot. We reuse rowids, we can even
change them (partitioned tables, IOTS). You might have extent #1 in file 55 and
extent #2 in file 2. Extent 4 might start on block 555 of file 3, Extent 5
might start on block 2 of file 3. Rowids are NOT sortable.
Even so, I had expected that when inserting rows into a NEW, EMPTY table they would physically go in starting at the first block, first record and so on - apparently not!