469,082 Members | 1,108 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Share your developer knowledge by writing an article on Bytes.

Oracle 11g New Features-I

8,127 Expert 4TB
Interval Partitioning: A new partitioning strategy in Oracle Database 11g
================================================== ======
One more features which really look interesting and I will be looking forward to implement it is, A new partitioning strategy in Oracle Database 11g, Interval partitioning extends the capabilities of the range method to define equipartitioned ranges using an interval definition. Rather than specifying individual ranges explicitly, Oracle will create any partition automatically as-needed whenever data for a partition is inserted for the very first time. Interval partitioning greatly improves the manageability of a partitioned table.

For example:
An interval partitioned table could be defined so that Oracle creates a new partition for every month in a calendar year; a partition is then automatically created for new month as soon as the first record for that month is inserted into the database.

PL/SQL: Fine Grained Dependency Tracking
In previous releases, metadata recorded mutual dependencies between objects with the granularity of the whole object.

For example:
PL/SQL unit P depends on PL/SQL unit Q or that view V depends on table T. This means that dependent objects were sometimes invalidated when there was no logical requirement to do so. For example, if view V depends only on columns C1, C2, and C3 in table T and a new column, C99, is added, the validity of view V is not logically affected. Nevertheless, in earlier releases, V was invalidated by the addition of column C99.

Oracle Database 11g records dependency metatdata at a finer level of granularity so that the addition of C99 does not invalidate view V. Similarly, if procedure P depends only on elements E1 and E2 in package PKG, then if element E99 is added to PKG, procedure P is not invalidated. (In Oracle Database 10g, this change to PKG would invalidate procedure P.)

By reducing the consequential invalidation of dependent objects in response to changes in the objects they depend upon, application availability is dramatically increased. The benefit is felt both in the development environment and when a deployed application is patched or upgraded. The benefit occurs when an Oracle Database patchset is applied because changes to schema objects are required to be compatible and, therefore, will not now cause consequential invalidations.

Source:Extracted from Oracle White Paper

Oracle 11g New Features.-II
Aug 8 '07 #1
0 3866

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

10 posts views Thread by michael newport | last post: by
7 posts views Thread by Murtix Van Basten | last post: by
42 posts views Thread by Paul | last post: by
56 posts views Thread by Ashish Patankar | last post: by
1 post views Thread by CARIGAR | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.