Oracle 11 G new features associated with this release:-

Enhanced ILM - Information Lifecycle Management (ILM) has been around for the almost 10 years, but Oracle has made an influencing power to codify the approach in 11G.

File Group Repository - Oracle introduced an exciting new feature in 10gr2 dubbed the File group Repository (FGR).  The FGR allows the database to define a logically-related group of files and build a version control infrastructure.  Oracle file group repository were created to support Oracle Streams, and they mimic the functionality of in mainframe of IBM  generation data group (GDG), in that you can specify relative institutes of the file sets (e.g. generation 0, generation).

Interval partitioning for tables -

This is the process breaking that automatically developes time-based partitions as new data is added. This is a unique one! You can now partition by date, one partition per month for example, with automatic partition creation.

New table Data Type simple integer - A new 11g data type labeled simple integer is initiated. The simple integer data type is always NOT NULL, absorbs instead of overflows and is faster than ever.

Faster DML triggers - DML triggers are up to 25% faster. This especially effects row level triggers doing updates against other tables (think Audit trigger).

Invisible indexes - New 11ginvisible indexes are modern new features.  It comes that the invisible indexes will survive, that they can just be pointed as invisible so that they cannot be acknowledged by the SQL optimizer. With the responsibility of maintaining the index intact, I don't see why this is very effective. 

Optimized RAC cache fusion protocols - Moves on from the general memory fusion protocols in 10G to deal with specially scenarios where the databases could be further optimized.

Data Guard - Standby snapshot - This new feature of oracle 11G that surfaces database developers to encompass a snapshot for their regression testing.  They can accumulate standby snapshots and forward those into their QA databases, making sure that their regression test uses real production data.