1
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle. Release timing for Oracle Database 12c is planned for Calendar Year 2013. 2
Active Oracle Database 12c Heat Map, Automatic Data Optimization & In-Database Archiving Penny Avril Senior Director Oracle Database Server Technologies Frequent Access Occasional Access Dormant 3
Heat Map, Automatic Data Optimization & In- Database Archiving Challenges Heat Map Automatic ti Data Optimization i ADO In-Database Archiving 4
Data Growth Challenges Opposing forces - Managing growing volumes of data cost-effectively - Process data real-time, interactively 5
Active Frequent Access Occasional Access Dormant Heat Map What it tracks A Heat Map of the Database Database level Heat Map shows which tables and partitions are being used Block level Heat Map shows last modification at the block level Comprehensive Segment level shows both reads and writes Distinguishes index lookups from full scans Automatically excludes stats gathering, DDLs or table redefinitions 6
Heat Map for Table and Partitions segment level tracking ORDER S 7
Heat Map for Blocks row level tracking ORDER S 8
Heat Map How to enable Active Syntax for production.. SQL> alter system set parameter heat_map= ON ; Frequent Access Occasional Access Dormant Syntax for shiphome 121022.. SQL> alter table employee ilm enable activity tracking segment access 9
Heat Map Enterprise Manager screens Work In Progress, expected GA + 6 months 10
Automatic Data Optimization Compress rows based on usage background row compression ORDER S SQL> ALTER TABLE EMPLOYEE ILM ADD POLICY ROW STORE COMPRESS ADVANCED ROW AFTER 1 DAY OF NO MODIFICATION 11
Automatic Data Optimization Compress partitions based on usage columnar Exadata only ORDER S SQL> ALTER TABLE ORDERS ILM ADD POLICY COMPRESS FOR QUERY HIGH SEGMENT AFTER 30 DAYS OF NO MODIFICATION 12
Automatic Data Optimization Optimize data storage based on usage columnar Exadata only ORDER S Optimized use of Row Store & Column Store within a single table Insert / load data as fast as possible row format Fast analytics & reporting data optimized in columnar format for analytics 13
Automatic Data Optimization (ADO) Storage tiering - policy SQL> ALTER TABLE EMPLOYEE ILM ADD POLICY TIER TO LOW_COST_TABLESPACE TABLESPACE 14
Automatic Data Optimization Storage tiering how it works ORDER S 1. Tables grow in size ILM policies compress data 2. Tbl Tablespace containing i partitions reaches ILM tiering threshold 3. Partitions are moved to different tablespace on lower spec disk group 15
Automatic Data Optimization Optimized Backups with Automated READONLY data movement Expected syntax for production.. SQL> ALTER TABLE EMPLOYEE ILM ADD POLICY TIER TO DATA2 READ ONLY AFTER 180 DAYS OF NO MODIFICATION 16
Automatic Data Optimization Optimized p Backups p with Automated READONLY data movement D OR 17 1. Tables grow in size ILM policies compress data 2. Tablespace T bl containing i i partitions reaches ILM tiering threshold 3. Partitions are moved to new read only tablespace on lower spec disk group S ER
Automatic Data Optimization Competitive Oracle Storage Vendors Disk Saving Extensive Partial Performance Speeds Queries Adds Overhead Integration with Database Deep integration excludes maintenance tasks includes memory access Integrated with RMAN and Active Data Guard Zero integration maintenance tasks considered real access 18
Compression New features in Oracle Database 12c Network Compression Faster queries on advanced row (OLTP) compression Wide tables (>255 columns) for advanced row (OLTP) compression 19
In-Database Archiving Speed up upgrade and reports Applications typically work with recent data But often need to retain data for 5 to 10 years In-Database Archiving provides the ability to archive infrequently used data within the database Archived data is invisible by default Works with partition pruning and Exadata storage indexes to eliminate I/O for archived data Archived data remains online for SQL Query & DMLs 20
In-Database Archiving How to enable Easily enabled for a table: alter table row archival Application can marks rows as archived: update SALES_ORDERS set ORA_ARCHIVE_STATE = 1 Sessions can set default visibility to see all data or active data only (default) alter session set row archival visibility = [all active] 21
In-Database Archiving Competitive Application Knowledge Cost Schema Changes Operational Impact Oracle Required No cost for functionality (included in EE) Minimal Minimal IBM Optim, Solix, Informatica, HP Knowledge Packs for all Oracle Apps. Supports custom rules. Consultant cost usually required. Typical deal in $200K range Required (typically shadow table) Access to archive data requires special support, app dev effort 22
Heat Map, Automatic Data Optimization and In- Database Archiving Summary Heat Map Automatically tracks access Database-aware: maintenance jobs, backups, etc don t affect heat map Automatic Data Optimization Declarative easy-to-use syntax to define data compression & movement policies Extensible with business-specific logic In-Database Archiving i Automatically hide archive data from normal users Keep archive data accessible, minimize impact on storage and performance 23
The preceding is intended to outline our general product direction. It is intended for information purposes p only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle. Release timing for Oracle Database 12c is planned for Calendar Year 2013. 24
25