10 new features to the oracle dataabse 10g

Question

Hi all.
Recently, I have been interivewed and I have been asked to list 10 new features of Oracle 10g.
I told him about:
1) Here, stats have been collected automatically, in oracle 9i it was manual
2) AWR
3) RULE based optimizer is not there only in oracle 9i
4) ASM
Anything else which you want to mentioned:

Answer 1

The Automatic Database Diagnostic Monitor (ADDM) analyzes data in the Automatic Workload Repository (AWR) to identify potential performance bottlenecks. For each of the identified issues it locates the root cause and provides recommendations for correcting the problem. An ADDM analysis task is performed and its findings and recommendations stored in the database every time an AWR snapshot is taken provided the STATISTICS_LEVEL parameter is set to TYPICAL or ALL. The ADDM analysis includes:
•     CPU load
•     Memory usage
•     I/O usage
•     Resource intensive SQL
•     Resource intensive PL/SQL and Java
•     RAC issues
•     Application issues
•     Database configuration issues
•     Concurrency issues
•     Object contention
ASM
Automatic Storage Management (ASM) simplifies administration of Oracle related files by allowing the administrator to reference disk groups rather than individual disks and files, which are managed by ASM
DBMS_FILE_TRANSFER Package in Oracle Database 10g•     Common Usage Notes
•     COPY_FILE
•     GET_FILE
•     PUT_FILE
Flashback New Features and Enhancements in Oracle Database 10g•     Flashback Query
•     Flashback Version Query
•     Flashback Transaction Query
•     Flashback Table
•     Flashback Drop (Recycle Bin)
•     Flashback Database
•     Flashback Query Functions
Oracle Data Pump
STARTUP UPGRADE
The is a new startup mode associated with the upgrade procedure in Oracle 10g.
SQL> STARTUP UPGRADE
Automatic Shared Memory ManagementAutomatic Shared Memory Management puts Oracle in control of allocating memory within the SGA. The SGA_TARGET parameter sets the amount of memory available to the SGA. This parameter can be altered dynamically up to a maximum of the SGA_MAX_SIZE parameter value. Provided the STATISTICS_LEVEL is set to TYPICAL or ALL and the SGA_TARGET is set to a value other than "0" Oracle will control the memory pools which would otherwise be controlled by the following parameters:
•     DB_CACHE_SIZE (default block size)
•     SHARED_POOL_SIZE
•     LARGE_POOL_SIZE
•     JAVA_POOL_SIZE
If these parameters are set to a non-zero value they represent the minimum size for the pool. These minimum values may be necessary if you experience application errors when certain pool sizes drop below a specific threshold.
The following parameters must be set manually and take memory from the quota allocated by the SGA_TARGET parameter:
•     DB_KEEP_CACHE_SIZE
•     DB_RECYCLE_CACHE_SIZE
•     DB_nK_CACHE_SIZE (non-default block size)
•     STREAMS_POOL_SIZE
•     LOG_BUFFER