This section describes the new features of Oracle Database 11g Release 1 (11.1) and provides pointers to additional information. New features information from previous releases is also retained to help those users migrating to the current release.
Pivot and Unpivot Operators
PIVOT operator makes it easy to create aggregated cross-tabular output that condenses many rows into a compact result set useful for reports. For instance, input data holding sales of one month in each row can be pivoted into output holding twelve months in each row, with each month in its own column. By combining multiple input rows into each output row,
PIVOT also enables inter-row comparison without a table self-join. The
UNPIVOT operator reshapes data into a format useful for further relational operations. For example, if a source data set presents twelve months of sales values in each row,
UNPIVOT can reshape each source row into twelve output rows, each holding one month of sales data. The unpivoted results are in a more normalized relational form than the source data, and they can be manipulated with simpler and more efficient SQL.
See Also:Chapter 20, "SQL for Aggregation in Data Warehouses" for more information
The SQL Access Advisor has been enhanced to include partition advice. It recommends the right strategy to partition tables, indexes, and materialized views to get best performance from an application.
See Also:Chapter 5, "Partitioning in Data Warehouses" for more information
Change Data Capture (CDC) Enhancements
CDC is now aware of direct-path load operations and implicit data changes as the result of partition-maintenance operations. Users can now turn synchronous CDC on and off as needed. Also, the flexibility of purging change data from change tables has been improved, so you can specify a date range for which data should be purged.
Another improvement is that it is easier to maintain a subscription window to change data. You now have control over the definition of the change subscription, so the window can be moved forward and backward.
See Also:Chapter 16, "Change Data Capture" for more information
Query Rewrite Enhancements
Query rewrite has been enhanced to support queries containing inline views. Prior to this release, queries containing inline views could rewrite only if there was an exact text match with the inline views in the materialized views. Because inline views no longer need to textually match between the query and the materialized view, a larger number of queries with inline views can be rewritten. Another significant query rewrite improvement is the ability to rewrite queries that reference remote tables.
See Also:Chapter 17, "Basic Query Rewrite" for more information
Refresh has been enhanced to support automatic index creation for
ALL materialized views, the use of query rewrite during a materialized view's atomic refresh, and materialized view refresh with set operators. Also, partition change tracking refresh of
ALL materialized views is now possible. Finally, catalog views have been enhanced to contain information on the staleness of partitioned materialized views. These improvements will lead to faster refresh performance.
See Also:Chapter 15, "Maintaining the Data Warehouse" for more information
Administrators can now specify with a single parameter (
MEMORY_TARGET) the total amount of memory (shared memory and SQL execution memory) that can be used by the Oracle Database, leaving to the server the responsibility to determine the optimal distribution of memory across the various memory components of the database instance.
See Also:Chapter 25, "Using Parallel Execution" for more information
Oracle OLAP Option Data Warehousing Features
The OLAP Option of the Oracle Database has been enhanced with several features designed to make OLAP cubes attractive alternatives to tables for managing and querying aggregate data in the data warehouse. These include:
Further integration of cubes into the SQL query engine. Advancements include integration of cubes with the Oracle query optimizer and a cube row source. These features dramatically increase the efficiency of SQL queries that select from OLAP cubes and dimensions by pushing joins directly into the Oracle Database's multidimensional engine, allowing efficient joins between tables and cubes and by improving overall row/second throughput when selecting from cubes.
Automatic query rewrite to cube organized materialized views. Cube-organized materialized views access data from OLAP cubes rather than tables. Like table-based materialized views, application can write queries to detail tables or views and let the database automatically rewrite the query to pre-aggregated data in the cube.
Database-managed automatic refresh of cubes. In this release, cubes can be refreshed using the
DBMS_MVIEW.REFRESH program, just like table-based materialized views. Cubes provide excellent support for
FAST (incremental) refresh.
Cost-based aggregation. In many situations, cubes are much more efficient at managing aggregate data as compared to tables. Cost-based aggregation improves upon these advantages by improving the efficiency of pre-aggregating and querying aggregate data, and by simplifying the process of managing aggregate data.
Database administrators who support dimensionally modeled data sets (for example, star/snowflake schema) for query by business intelligence tools and applications should consider using OLAP cubes as a summary management solution because they may offer significant performance advantages.
SQL Model Calculations
MODEL clause enables you to specify complex formulas while avoiding multiple joins and
UNION clauses. This clause supports analytical queries such as share of ancestor and prior period comparisons, as well as calculations typically done in large spreadsheets. The
MODEL clause provides building blocks for budgeting, forecasting, and statistical applications.
See Also:Chapter 22, "SQL for Modeling"
Materialized View Refresh Enhancements
Materialized view fast refresh involving multiple tables, whether partitioned or non-partitioned, no longer requires that a materialized view log be present.
Query Rewrite Enhancements
Query rewrite performance has been improved because query rewrite is now able to use multiple materialized views to rewrite a query.
See Also:Chapter 17, "Basic Query Rewrite"
You can now use partitioning with index-organized tables. Also, materialized views in OLAP are able to use partitioning. You can now use hash-partitioned global indexes.
Change Data Capture
Oracle now supports asynchronous change data capture as well as synchronous change data capture.
See Also:Chapter 16, "Change Data Capture"
Oracle's extraction, transformation, and loading capabilities have been improved with several
MERGE improvements and better external table capabilities.