This parameter was introduced in 11.2.0.1 especially for Exadata Database Machine because the Allocation Unit Size (AU_SIZE) for Diskgroups built upon Exadata Cells is recommended with 4 MB. Large Segments should therefore use a multiple of 4 MB already for their initial extents. Although the parameter was made obsolete, the effect that was achievable with it is still present:

Conclusion: With 11.2.0.2, partitioned tables get initial extents of 8 MB in size, which is particular useful in Exadata Environments where the ASM AU_SIZE will be 4 MB. But also ordinary Databases are affected – which is probably a good thing if we assume that partitioned tables will be large in size anyway and will therefore benefit from a large initial extent size as well.

Sure it is. But they don’t mention CELL_PARTITION_LARGE_EXTENTS nor the new hidden parameter, although we have still some whitepapers – and courseware – out there that recommend setting the obsolete parameter. So my hope is that this post is not completely useless :-)

Oh, sorry, didn’t mean to imply that… I wasn’t even aware that _partition_large_extents existed, so it was quite interesting!
I just don’t think many people are aware that Oracle tried to document the new features of 11.2.0.2. It is a bit unusual to have so many small enhancements in a patchset.

Ofir,
thank you for pointing to our very informative New Features Guides :-)
11.2.0.2 is indeed extraordinary. Can’t remember that we could ever download a patchset from MOS/Metalink that was an autonomous installation, for example.