Thanks for the question, Roberto.
Asked: May 18, 2017 - 9:24 pm UTC
Last updated: May 19, 2017 - 8:24 pm UTC
Version: 12.1.0.2
Viewed 1000+ times
You Asked
We are in the process of reorganizing a large table: 6+ billion rows, almost 500 gigs of space, 126k extents.
This table is an audit record so it would rarely --if ever-- get updated or deleted.
My question has to do with extent sizing: What would you recommend for objects like these? Is AUTOALLOCATE a good option or would it be better to use UNIFORM extent sizing?
If UNIFORM is the way to go, is there a guideline for determining extent sizing?
Thank you,
Roberto.
and Connor said...
I cant think of a time when I've had an issue with autoallocate - it tends to keep extent numbers to a manageable level.
But if you want to opt for uniform, thats fine too. I'd pick a size that ensures less than (say) 1000 extents simply to keep queries against DBA_EXTENTS nice and efficient. If you exceed that, it is not a problem in any way - your queries against DBA_EXTENTS (not your table) might be a little slower.
Is this answer out of date? If it is, please let us know via a Comment