Oracle 11G New features detailed

One, the database Management Section

1. Database replay (DB replay)

This feature captures the load of the entire data and passes it on to a test database created from a backup or standby database, and then repeats the load to test the effect of the system tuning.

2. SQL Replay (Sqlreplay)

Similar to the previous feature. But just capture the portion of the SQL payload, not the full load.

3. Planning Management (Plan Management)

This feature allows you to fix the query plan for a particular statement, regardless of whether the changes in the statistical data or the database version will change its query plan.

4. Automatic diagnostic Knowledge Base (Automatic diagnostic Repositoryadr)

When Oracle detects a critical error, it automatically creates an event (incident), captures the information associated with the event, and automatically checks the database for health and notifies the DBA. In addition, this information can be packaged and sent to the Oracle support team.

5, Event Packaging Services (Incident packaging service)

If you need to test further or retain relevant information, this feature can package information related to an event. And you can also send packaged information to the Oracle support team.

6, based on the characteristics of the patch (Feature Based patching)

This feature makes it easy to distinguish between the features in a patch package that you are using and that you have to play. Enterprise Manager (EM) enables you to subscribe to a feature-based patch service, so Enterprise Manager can automatically scan those features you are using with patches that can be hit.

7, Automatic SQL optimization (auto sqltuning)

The 10g automatic optimizer can write tuning recommendations in SQL profile. In 11g, you can have Oracle automatically apply a profile with 3 times times the original performance to the SQL statement. Performance comparisons are performed by a new administrative task in the Maintenance window.

8, access to the recommendations (access Advisor)

11G's access advice can give zoning advice, including recommendations for new interval partitions (interval partitioning). An interval partition is equivalent to an automated version of a range partition (Rangepartitioning) that automatically creates a partition of the same size, if necessary. range partitions and interval partitions can exist in a single table, and the range partition can be converted to an interval partition.

9, Automatic memory optimization (Auto Memory tuning)

In 9i, automatic PGA optimization was introduced, and automatic SGA optimization was introduced in 10g. To 11g, all memory can be automatically optimized by setting only one parameter for the entire table. As long as you tell Oracle how much memory is available, it can automatically specify how much memory is allocated to the PGA, how much memory is allocated to the SGA, and how much memory is allocated to the operating system process. Of course, you can set the maximum and minimum threshold values.

10. Resource Manager (Resource Manager)

The 11G resource Manager can manage not only the CPU but also IO. You can set the priority, file type, and ASM disk group for specific files.

11, ADDM

ADDM was introduced in 10g. In 11g, ADDM can recommend not only a single instance, but also the entire RAC (that is, the database level). In addition, some instructions (Directive) can be added to the ADDM to ignore information that you don't care about.

12, AWR Baseline (Awrbaselines)

The AWR baseline has been expanded. You can automatically create baselines for some other features that you use. The Dian Cun Zhang Line is created by default.

Second, Plsql part

1, result set cache (results set Caching)

This feature can greatly improve the performance of many programs. In some MIS systems or OLAP systems, you need to use many queries such as SELECT COUNT (*). Before, if we wanted to improve the performance of such queries, we might need to use materialized views or query rewriting techniques. In 11g, we just need to add a/*+result_cache*/hint to cache the result set, which can greatly improve query performance. Of course, in this case, we may have another problem: completeness. Because the integrity of the data is guaranteed through consistent reading in Oracle. Obviously, under this new feature, in order to improve performance, the data is read from the result set in the cache without reading the data from the rollback segment. The answer to this question is complete assurance of completeness. Because the result set is cached independently, any other DML statements will not affect the contents of the result set during the query, thus guaranteeing the integrity of the data.

2. Object-dependent improvement

Before 11g, if a function or view depended on a table, once the table had a structural change, the function or view would become invalid, whether it involved a function or a view-dependent property. In 11g, this situation is adjusted: if the properties of the table change are independent of the related function or view, the related object state does not change.

3. Improvement of Regular expression

In 10g, regular expressions are introduced. This feature greatly facilitates the developer. 11g,oracle has again improved this feature. Among them, a function called Regexp_count is added. In addition, other regular expression functions have been improved.

4. New SQL Syntax =>

When we call a function, we can specify the data for a particular function parameter by =>. In the 11g, this syntax can also appear in the SQL statement. For example, you can write a statement like this:

Select F (x=>6) from dual;

5, the TCP packet (UTL_TCP, UTL_SMTP ... ) supports FGAC (Fine grained AccessControl) security control

6, added read-only table (read-only table)

Previously, we implemented read-only control of a table through triggers or constraints. 11g does not need this much trouble, you can directly specify the table as a read-only table.

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/database/Oracle/