I supppose it’s inevitable that there will be a flurry of 11gR2 posts in the next few days – so here’s mine. A really useful new feature (and it’s corollary) that caught my eye:
18.104.22.168 Segment Creation on Demand
The initial segment creation for nonpartitioned tables and indexes can be delayed until data is first inserted into an object.
Several prepackaged applications are delivered with large schemas containing many tables and indexes. Depending on the module usage, only a subset of these objects are really being used. With delayed segment creation, empty database objects do not consume any space, reducing the installation footprint and speeding up the installation.
22.214.171.124 Zero-Size Unusable Indexes and Index Partitions
Unusable indexes and index partitions no longer consume space in the database because they become segmentless.
Unusable indexes and index segments are not usable for any data access. Any space allocated by this unusable (dead) object is freed as soon as an object is marked unusable.
While we’re on the topic of 11.2 – here’s an interesting set of results published on the comp.databases.oracle.server newsgroup by Charles Hooper.
Update 7th Sept: And here’s another interesting post, from the Optimizer Development Group, on a new feature for comparing execution plans. It looks like a nice idea, but it looks a little clunky at present so I’m not sure it will be of much to many people.
Update 11th Sept: I see that Greg Rahn has listed his top 10 – the parallel stuff looks as if it might be interesting, and “instance caging” could be very useful.