Skip Headers
Oracle® Database VLDB and Partitioning Guide
12c Release 1 (12.1)

E17613-20
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

Changes in This Release for Oracle Database VLDB and Partitioning Guide

This chapter describes changes to Oracle Database VLDB and Partitioning Guide for Oracle Database 12c Release 1 (12.1).

See Also:

Oracle Database New Features Guide for a complete description of the new features in Oracle Database 12c Release 1 (12.1)

Changes for Very Large Databases and Partitioning in Oracle Database 12c Release 1 (12.1)

The following are changes in Very Large Databases and Partitioning for Oracle Database 12c Release 1 (12.1).

New Features

These are the new features in Oracle Database 12c Release 1 (12.1) to support very large databases:

Partition Maintenance Operations on Multiple Partitions

This feature enables partition maintenance operations on multiple partitions, providing simplified application development and more efficient partition maintenance.

Multipartition maintenance operations enable adding multiple partitions to a table, dropping multiple partitions, merging multiple partitions into one partition, splitting of a single partition into multiple partitions, and truncating multiple partitions using a single SQL data definition language (DDL) statement. For a summary of maintenance operations that are valid, refer to "Maintenance Operations on Partitions That Can Be Performed"

For more information, refer to "Adding Multiple Partitions", "Dropping Multiple Partitions", "Merging Multiple Partitions", "Splitting into Multiple Partitions", and "Truncating Multiple Partitions".

Heat Map

This feature provides a heat map of hot and cold data, enabling you to specify the archive state for each row in the database as needed and assisting you to implement your Information Lifecycle Management (ILM) strategy. Each row in a database can be managed appropriately based on its archive state, providing fine-grained control over the visibility, compression, and storage tier for all of the data in the database. In combination with other ILM-related features, this feature enables users to automatically optimize their database storage to maximize performance and minimize cost.

You can track both access and modification operations to data at the row, segment, and table levels. You can also implement policy-driven automation based on the information tracked with this feature.

For more information, refer to "Using Heat Map" and "Managing ILM Heat Map and ADO with Oracle Enterprise Manager".

See Also:

Automatic Data Optimization

This feature provides SQL statement options for specifying policies at the row, segment, and tablespace level, assisting you to implement your Information Lifecycle Management (ILM) strategy.

You can use Automatic Data Optimization (ADO) to automate the movement of data between different tiers of storage within the database. This includes the ability to specify different compression levels for each tier, and to control when the data movement takes place. You can specify compression at the row and segment level within each table in a database. The combination of row and segment level compression tiering provides fine-grained control over how the data in the database is stored and managed.

For more information, refer to "Using Automatic Data Optimization" and "Managing ILM Heat Map and ADO with Oracle Enterprise Manager".

See Also:

In-Database Archiving and Temporal Validity

The In-Database Archiving and Temporal Validity features enable you to manage the validity and visibility of data for real world situations.

For more information, refer to "Controlling the Validity and Visibility of Data in Oracle Database".

See Also:

Concurrent Execution of Union All

The main benefit of this feature is to run multiple remote branches of a UNION or UNION ALL concurrently.

For information, refer to "Concurrent Execution of Union All".

Enhancements to Incremental Statistics

Incremental statistics have been enhanced to support partition exchange loading. Data loaded into a nonpartitioned table can be exchanged with a partition from the table and Oracle automatically and accurate computes the global statistics for the partition table, using the statistics from the nonpartitioned table and the existing partition level statistics. For information, refer to "Exchanging Partitions and Subpartitions".

Parallel Statement Queuing Enhancements

This feature adds to existing parallel statement queuing functionality.

Included in this feature:

  • Parallel server limit directive for pluggable database (PDB) plans

    The parallel_server_limit directive replaces the parallel_target_percentage directive. This directive specifies the percentage of the available parallel servers that the consumer group can use when this directive is set.

    For multitenant container database (CDB) resource plans, this limit applies to pluggable databases. For PDB resource plans or non-CDB resource plans, this limit applies to consumer groups.

    For more information, refer to "Managing Parallel Statement Queuing with Oracle Database Resource Manager".

    See Also:

  • Automatic Parallel Queuing Enhancements

    • Queued statement monitoring and analysis

      To facilitate the analysis of queued parallel statements, the V$RSRC_SESSION_INFO view provides the PQ_SERVERS and PQ_STATUS columns.

      V$RSRC_SESSION_INFO.PQ_SERVERS specifies the number of parallel servers used by this parallel operation.

      V$RSRC_SESSION_INFO.PQ_STATUS specifies the reason why the parallel operation is queued.

      For more information, refer to "V$RSRC_SESSION_INFO".

      See Also:

      Oracle Database Reference for information about the V$RSRC_SESSION_INFO view
    • Historical statistics for parallel statement queuing

      Statistics related to parallel statement queuing are added to the resource manager metrics that takes statistics for a given one-minute window and retains them for approximately one hour.

      These statistics enable a DBA to monitor parallel statement queuing over time.

      For more information, refer to "V$RSRCMGRMETRIC".

      See Also:

      Oracle Database Reference for information about the V$RSRCMGRMETRIC view
    • Critical parallel statement prioritization

      The parallel_stmt_critical parameter enables you to mark specific consumer groups as critical in respect to parallel statements in the plan directive.

      This parameter specifies that parallel operations from a particular consumer group should not be queued; instead these statements should be run immediately.

      For more information, refer to "Critical Parallel Statement Prioritization".

      See Also:

For information about parallel statement queuing, refer to "Parallel Statement Queuing".

Partial Indexes for Partitioned Tables

Local and global indexes can be created on a subset of the partitions of a table, enabling more flexibility in index creation. This operation is supported using a default table indexing property. When a table is created or altered, a default indexing property can be specified for the table or its partitions.

For information about creating partial indexes for partitioned tables, refer to "Partial Indexes for Partitioned Tables".

Asynchronous Global Index Maintenance for DROP and TRUNCATE PARTITION

This feature enables global index maintenance to be delayed and decoupled from a DROP and TRUNCATE partition without making a global index unusable. Enhancements include faster DROP and TRUNCATE partition operations and the ability to delay index maintenance to off-peak time.

For more information, refer to "Asynchronous Global Index Maintenance for Dropping and Truncating Partitions".

Interval-Reference Partitioning

This feature enables reference-partitioned table to use interval partitioning as a top partitioning strategy, which provides a better partitioning modeling. Interval partitioned tables can be used as parent tables for reference partitioning. Partitions in the reference partitioned table corresponding to interval partitions in the parent table are created upon insert into the reference partitioned table.

For more information, refer to "Creating Interval-Reference Partitioned Tables".

Cascade Functionality for TRUNCATE PARTITION and EXCHANGE PARTITION

This feature provides a CASCADE option for TRUNCATE PARTITION and EXCHANGE PARTITION operations for reference and interval-reference partitioned tables, which cascades the operation to reference partitioned child tables. This functionality enables simplified application development by enabling the inheritance of the partition maintenance operation from the parent to the child tables. The cascade options are off by default so they do not affect compatibility.

For more information, refer to "Exchanging a Partition with the Cascade Option" and "Truncating a Partition with the Cascade Option".

Oracle XML DB and Domain Index Support of Hash and Interval Partitioned Tables, Including XMLIndex

Oracle XML DB and other applications that use domain indexes can use hash or interval partitioned methods. Hash partitioning is an effective approach to balancing I/O evenly over a series of partitions. Interval partitioning is an automatic and low overhead approach to defining partitions in advance that are created only as needed. The advantages of these partitioning methods are now available to users of XML DB and other applications that use domain indexes. For more information, refer to "Hash Partitioning" and "Interval Partitioning".

This feature also supports the use of hash partitioning for XMLIndex. For more information, refer to "Partitioning of XMLIndex for Binary XML Tables".

See Also:

Online Move Partition

This feature provides an ALTER TABLE .. MOVE PARTITION option, where DML operations can continue to run uninterrupted on the partition that is being moved. In addition, global indexes are maintained during the move partition, so a manual index rebuild is no longer required. This feature eliminates the need for any special downtime for the ALTER TABLE MOVE PARTITION ONLINE command.

For more information, refer to "Moving Partitions and Subpartitions".

See Also:

Oracle Database SQL Language Reference for information about online move partition, including any limitations of this feature