The above process is how Oracle allocates extents for empty tablespaces. For tablespaces that have segments allocated, Oracle tries to allocate extents where it can find space. And the extent is not allowed to cross a datafile. So if you drop segments and leave holes of free space, Oracle will attempt to fill in those holes. So you may not notice the same behavior.
There are other issues which may affect this behavior as well. A high setting for PCTINCREASE may cause Oracle to behave differently. Or, if you have extents that are larger than your free space fragments, Oracle may exhibit other behavior as well. It all depends on the tablespace's allocation strategy, i.e. locally or dictionary managed.
Dig Deeper on Oracle database administration
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.