1 Automatic Data Optimization with Oracle Database 12c O R A C L E W H I T E P A P E R S E P T E M B E R
2 Table of Contents Disclaimer 1 Introduction 2 Storage Tiering and Compression Tiering 3 Heat Map -- Fine Grained Data Usage Tracking 4 Automatic Data Optimization 4 Conclusion 9 Disclaimer 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.
3 Introduction The amount of data that enterprises are storing and managing is growing rapidly - various industry estimates indicate that data volume is doubling every 2-3 years. The rapid growth of data presents daunting challenges for IT, both in cost and performance. Although the cost of storage keeps declining, fast-growing data volumes make storage one of the costliest elements of most IT budgets. In addition, the accelerating growth of data makes it difficult to meet performance requirements while staying within budget. Information Lifecycle Management (ILM) is intended to address these challenges by storing data in different storage and compression tiers, according to the enterprise s current business and performance needs. This approach offers the possibility of optimizing storage for both cost savings and maximum performance. In Oracle Database 12c, Heat Map and Automatic Data Optimization were introduced as features of Oracle Advanced Compression. Heat Map automatically tracks modification and query timestamps at the row and segment levels, providing detailed insights into how data is being accessed. Automatic Data Optimization (ADO) automatically moves and compresses data according to user-defined policies based on the information collected by Heat Map. Heat Map and ADO make it easy to use existing innovations in Oracle Database compression and partitioning technologies, which help reduce the cost of managing large amounts of data, while also improving application and database performance. Together these capabilities help to implement first-class Information Lifecycle Management in Oracle Database. Oracle Database 12c Release 2 (12.2) is available in the cloud, with Oracle Cloud at Customer, and on-premises. 2
4 Storage Tiering and Compression Tiering An enterprise (or even a single application) does not access all its data equally: the most critical or frequently accessed data will need the best available performance and availability. To provide this best access quality to all the data would be costly, inefficient and is often architecturally impossible. Instead, IT organizations implement storage tiering. With storage tiering, organizations can deploy their data on different tiers of storage so that less-accessed ( colder ) data is migrated away from the costliest and fastest storage. The colder data is still available, but at slower speeds the effect on the overall application performance is minimal, due to the rarity of accessing colder data. Colder data may also be compressed to a greater level (compared to active data) in storage. We use the term Information Lifecycle Management (ILM) 1 to name the managing of data from creation/acquisition to archival or deletion. Figure 1 indicates that the most active data located on a high performance tier and the less active data/historical data on lower-cost tiers. In this scenario, the business is meeting all of its performance, reliability, and security requirements, but at a significantly lower cost than in a configuration where all data is located on high performance (tier 1) storage. The illustration shows that a higher level of compression can be applied to the less active and historical storage tiers, further improving the cost savings while also improving performance for queries that scan the less active data. Different portions of the data are assigned to different tiers based on the cost, performance, availability, and security requirements for each portion. Data is compressed with Advanced Compression and/or Hybrid Columnar Compression across storage tiers 3X to 15X compression ratios are typical. Figure 1 - Partitioning, Advanced Compression and Hybrid Columnar Compression. In addition to storage tiering, it is also possible to use different types of compression to suit different access patterns. For example, colder data can be compressed at a higher level at the cost of slower access. Oracle Database provides several types of compression that can be utilized as data moves through its lifecycle - from hot/active to warm/less active to cold/historical while meeting the performance and availability requirements for the application. We call this compression tiering. 1 See for example Gartner s definition of ILM. Storage tiering, the practice of allocating different data to different levels of storage service, is one of the tools used for ILM. 3
5 Even with the right storage and compression capabilities, deciding which data should reside where and when to migrate data from one tier to another remains a serious challenge. Oracle Database 12c addresses this challenge with functionality that automatically discovers data access patterns Heat Map and uses Heat Map information to automatically optimize data organization Automatic Data Optimization. The rest of this document explains the Oracle Database technologies that enable storage and compression tiering, and how to use them to support Information Lifecycle Management. Heat Map -- Fine Grained Data Usage Tracking Heat Map, a feature in Oracle Advanced Compression, automatically tracks table/partition usage information at the row and segment levels. 2 Data modification times are tracked at the row level and aggregated to the block level, and modification times, full table scan times, and index lookup times are tracked at the segment level. Heat Map gives you a detailed view of how your data is being accessed, and how access patterns are changing over time. Programmatic access to Heat Map data is available through a set of PL/SQL table functions, as well as through data dictionary views. Figure 2 shows one way to depict Heat Map data. Each box represents one partition of a table. The size of the box is the relative size of the partition, and the color represents how hot (i.e., frequently accessed) the partition is based on the most recent access to any row in the partition. Figure 2 - Heat Map data for access patterns to a partitioned table Automatic Data Optimization Automatic Data Optimization (ADO) allows you to create policies for data compression (Smart Compression) and data movement, to implement storage and compression tiering. Smart Compression refers to the ability to utilize Heat Map information to associate compression policies, and compression levels, with actual data usage. Oracle Database periodically evaluates ADO policies, and uses the information collected by Heat Map to determine when to move and / or compress data. All ADO operations are executed automatically and in the background, without user intervention. 2 Database rows are stored in database blocks, which are grouped in extents. A segment is a set of extents that contains all the data for a logical storage structure within a tablespace, i.e. a table or partition. 4
6 ADO policies can be specified at the segment or row level for tables and/or partitions. Policies will be evaluated and executed automatically in the background during the maintenance window. ADO policies can also be evaluated and executed anytime by a DBA, manually or via a script. ADO policies specify what conditions (of data access) will initiate an ADO operation such as no access, or no modification, or creation time and when the policy will take effect for example, after n days or months or years. It is important to note that ADO conditions cannot be mixed. For example, if the first ADO condition, on a table/partition, uses the condition no modification, then the other conditions used for the same table/partition must use the same condition type. Conditions in ADO policies are not limited to Heat Map data: you can also create custom conditions using PL/SQL functions, extending the flexibility of ADO to use your own data and logic to determine when to move or compress data. The next examples use the best practice approach of compressing using both Advanced Row Compression and Hybrid Columnar Compression. While compression tiering best practice does include the use of HCC, if an organization doesn t have access to HCC, then they would use only Advanced Row Compression in their ADO policies. Automatic Data Optimization Examples The following examples assume there is an orders table containing sales orders, and the table is range partitioned by order date. In the first example, a segment-level ADO policy is created to automatically compress partitions using Advanced Row Compression after there have been no modifications for 30 days. This will automatically reduce storage used by older sales data, as well as improve performance of queries that scan through large numbers of rows in the older partitions of the table. ROW STORE COMPRESS ADVANCED SEGMENT AFTER 30 DAYS OF NO MODIFICATION; In the following example, a segment-level ADO policy is created to automatically compress the partition, to a higher compression level, using Hybrid Columnar Compression after there have been no modifications for 90 days. This makes sense when HCC is available, and when the data will no longer be updated, but will continue to be queried; moving to HCC will save a lot of storage AND give a big boost to query performance. COLUMN STORE COMPRESS FOR QUERY HIGH SEGMENT AFTER 90 DAYS OF NO MODIFICATION; Sometimes it is necessary to load data at the highest possible speed, which requires creating the partition without any compression enabled. This allows the post-load activity to subside on the table before compression is implemented. For organizations with SLA s around the load times, this allows the table to be created and populated as quickly as possible, before implementing compression. In the next example, an organization wants the benefits of compression, but also needs to ensure SLA requirements are met. It would be beneficial to compress the data, in the partition, on a more granular basis (block by block instead of the entire segment). You can create row-level ADO policies to automatically 5
7 compress blocks in the partition after no row, in a given block, has been modified for at least 3 days. With rowlevel policies, all rows in the block must meet the policy conditions before the block is compressed. Below is an example ADO policy where rows are inserted uncompressed, and then later moved to Advanced Row Compression (row-level policies can also be specified for Hybrid Columnar Compression) on a per-block basis. Note that this policy uses the ROW keyword instead of the SEGMENT keyword. ROW STORE COMPRESS ADVANCED ROW AFTER 3 DAYS OF NO MODIFICATION; With the above policy in place, Oracle Database will evaluate blocks during the maintenance window, and any blocks that qualify will be compressed, freeing up space for new rows as they are inserted. This allows you to achieve the highest possible performance for data loads, but also get the storage savings and performance benefits of compression without having to wait for an entire partition to be ready for compression. In addition to Smart Compression, ADO policy actions include data movement to other storage tiers, including lower cost storage tiers or storage tiers with other compression capabilities such as Oracle s Hybrid Columnar Compression (HCC). 3 ADO-based storage tiering (Tier To) is not based upon the ADO condition clause (i.e. after x days of NO MODIFICATION) as is compression tiering and instead, is based upon tablespace space pressure. The justification for making storage tiering dependent on "space pressure" is exactly as you might imagine, the belief that organizations will want to keep as much data as possible on their high performance (and most expensive) storage tier, and not move data to a lower performance storage tier until it is absolutely required. The exception to the storage pressure requirement are storage tiering policies with the 'READ ONLY' option, these are triggered by a heat-map based condition clause. The value for the ADO parameter TBS_PERCENT_USED specifies the percentage of the tablespace quota when a tablespace is considered full. The value for TBS_PERCENT_FREE specifies the targeted free percentage for the tablespace. When the percentage of the tablespace quota reaches the value of TBS_PERCENT_USED, ADO begins to move segments so that percent free of the tablespace quota approaches the value of TBS_PERCENT_FREE. This action by ADO is a best effort and not a guarantee. You can set ILM ADO parameters with the CUSTOMIZE_ILM procedure in the DBMS_ILM_ADMIN PL/SQL package, for example: BEGIN DBMS_ILM_ADMIN.CUSTOMIZE_ILM(DBMS_ILM_ADMIN.TBS_PERCENT_USED, 85): DBMS_ILM_ADMIN.CUSTOMIZE_ILM(DBMS_ILM_ADMIN.TBS_PERCENT_FREE, 25): END; In the example above, when a tablespace reaches the fullness threshold (85%) defined by the user, the database will automatically move the coldest table/partition(s) in the tablespace to the target tablespace until the tablespace quota has at least 25 percent free. This only applies to tables and partitions that have a "TIER TO" ADO policy defined. This frees up space on your tier 1 storage for the segments that would truly benefit 3 HCC requires the use of Exadata, SuperCluster, Pillar Axiom, Sun ZFS Storage Appliance or FS1 6
8 from the performance while moving colder segments, that don t need Tier 1 performance, to lower cost Tier 2 storage. In the following example, a tablespace-level ADO policy automatically moves the partition to a different tablespace when the current tablespace runs low on space. The tier to keywords indicate that data will be moved to a new tablespace when the current tablespace becomes too full. The low_cost_store tablespace was created on a lower cost storage tier. tier to low_cost_store; ADO storage tiering operates at the segment level, so when an ADO policy implements storage tiering the entire segment is moved and this movement is one direction, meaning that ADO storage tiering is meant to move colder segments from high performance storage to slower, lower cost storage. If an ADO compression policy AND a storage tiering policy both qualify, the database will execute both in a single segment reorganization step. All of this storage tiering behavior can be overridden with custom conditions on "TIER TO" policies: the DBA can write their own conditions using PL/SQL, and implement segment movement based on any conditions they want to encode. Another option when moving a segment to another tablespace is to set the target tablespace to READ ONLY after the object is moved. This is beneficial for historical data and during backups, since subsequent RMAN full database backups will skip READ ONLY tablespaces. Automatic Data Optimization for OLTP The previous examples show individual ADO policies that implement one action compression tiering (Smart Compression) or storage tiering. The following example shows how to combing multiple ADO policies for an OLTP application. In OLTP applications, you should use Advanced Row Compression for the most active tables/partitions, to ensure that newly added or updated data will be compressed as DML operations are performed against the active tables/partitions. For cold or historic data within the OLTP tables, use either Warehouse or Archive Hybrid Columnar Compression. This ensures that data which is infrequently or never updated is compressed to the highest levels compression ratios of 6x to 15x are typical with Hybrid Columnar Compression, whereas 2x to 4x compression ratios are typical with Advanced Row Compression. For example, see Figure 3: Figure 3 - Advanced Row Compression, Hybrid Columnar Compression and tiering. 7
9 To implement this approach with ADO, use the following policies: COLUMN STORE COMPRESS FOR QUERY HIGH SEGMENT AFTER 30 DAYS OF NO MODIFICATION; COLUMN STORE COMPRESS FOR ARCHIVE HIGH SEGMENT AFTER 90 DAYS OF NO MODIFICATION; tier to low_cost_store; In this example of Smart Compression and storage tiering, we assume that the orders partition is defined with Advanced Row Compression enabled, so that rows are compressed at that level when they are first inserted. Oracle Database will automatically evaluate the ADO policies to determine if the partition is eligible to be moved to a higher compression level, and if the partition is eligible to be moved to a lower cost storage tier. As discussed earlier, storage tiering is primarily triggered when the current tablespace becomes too full, but can be customized to occur based on user-defined conditions. The capabilities of Heat Map and ADO in Oracle Database 12c make it easy for DBAs to implement ILM for OLTP applications, and enable the use of HCC with OLTP data. With HCC, DBAs can significantly reduce the amount of storage space used by colder OLTP data, while increasing the performance of reports and analytics. Automatic Data Optimization for Data Warehousing In data warehousing applications on Exadata storage, or on Oracle Storage that supports HCC, HCC Warehouse Compression should be used for heavily queried tables/partitions. For cold or historic data within the data warehousing application, using Archive Compression ensures that data which is infrequently accessed is compressed to the highest level compression ratios of 15x to 50x are typical with Archive Compression. For example, see Figure 4: Figure 4 - Partitioning and Hybrid Columnar Compression. To implement this approach with ADO, use the following statements: COLUMN STORE COMPRESS FOR ARCHIVE HIGH SEGMENT AFTER 90 DAYS OF NO MODIFICATION; tier to lessactivetbs; 8
10 In this example, we assume that the orders table is defined with Warehouse Compression enabled, so that rows are compressed at that level when they are first inserted. Although this example implemented HCC compression at the segment-level, it should be noted that Automatic Data Optimization also supports Hybrid Columnar Compression (HCC) for row-level policies. Rows from cold blocks can be HCC-compressed even if there is DML insert activity on other parts of the table or partition. Hybrid Columnar Compression (HCC) can be used during array inserts into tables. This means that the SQL INSERT statement, without the APPEND hint, can use HCC (without degrading the compression level), and array inserts from programmatic interfaces such as PL/SQL and the Oracle Call Interface (OCI) can use HCC. ADO policies for HCC are now effective even if changes are constantly being made to a small subset of the table or partition (updates will still be performed uncompressed and could impact the HCC compression level). Oracle Database will automatically evaluate the ADO policies to determine if the partition is eligible to be moved to a higher compression level, and if the partition is eligible to be moved to a different tablespace. As with the previous Smart Compression example for OLTP, the automatic capabilities of ADO in Oracle Database 12c make it simple and easy for DBAs to implement ILM for Data Warehousing, and significantly reduce the amount of time and effort DBAs need to spend optimizing storage usage and storage performance. Conclusion Information Lifecycle Management enables organizations to understand how their data is accessed over time, and manage the data accordingly. However, most ILM solutions for databases lack two key capabilities automatic classification of data, and automatic data compression and movement across storage tiers. The Heat Map and Automatic Data Optimization features of Oracle Advanced Compression support comprehensive and automated ILM solutions that minimize costs while maximizing performance. In combination with the comprehensive compression features in Oracle Database 12c, Oracle Database 12c provides an ideal platform for implementing ILM. For more information about Automatic Data Optimization, please see the Storage Optimization blog here: https://blogs.oracle.com/dbstorage/ 9
11 Oracle Corporation, World Headquarters Worldwide Inquiries 500 Oracle Parkway Phone: Redwood Shores, CA 94065, USA Fax: C O N N E C T W I T H U S blogs.oracle.com/oracle facebook.com/oracle twitter.com/oracle oracle.com Copyright 2017, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group
Implementing Information Lifecycle Management (ILM) with Oracle Database 18c O R A C L E W H I T E P A P E R F E B R U A R Y 2 0 1 8 Disclaimer 1 Introduction 2 Information Lifecycle Management 3 Automating
Hybrid Columnar Compression (HCC) on Oracle Database 18c O R A C L E W H IT E P A P E R FE B R U A R Y 2 0 1 8 Disclaimer The following is intended to outline our general product direction. It is intended
Oracle Exadata Statement of Direction NOVEMBER 2017 Disclaimer The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated
Automating Information Lifecycle Management with Oracle Database 2c The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated
Oracle Advanced Compression with Oracle Database 12c Release 2 O R A C L E W H I T E P A P E R M A R C H 2 0 1 7 Disclaimer The following is intended to outline our general product direction. It is intended
Oracle Data Provider for.net Microsoft.NET Core and Entity Framework Core O R A C L E S T A T E M E N T O F D I R E C T I O N F E B R U A R Y 2 0 1 8 Disclaimer The following is intended to outline our
Information Lifecycle Management for Business Data An Oracle White Paper September 2005 Information Lifecycle Management for Business Data Introduction... 3 Regulatory Requirements... 3 What is ILM?...
An Oracle White Paper September 2012 Security and the Oracle Database Cloud Service 1 Table of Contents Overview... 3 Security architecture... 4 User areas... 4 Accounts... 4 Identity Domains... 4 Database
Oracle Data Masking and Subsetting Frequently Asked Questions (FAQ) S E P T E M B E R 2 0 1 6 Product Overview Q: What is Data Masking and Subsetting? A: Data Masking or Static Data Masking is the process
DATA INTEGRATION PLATFORM CLOUD Experience Powerful Integration in the Want a unified, powerful, data-driven solution for all your data integration needs? Oracle Integration simplifies your data integration
SecureFiles Migration O R A C L E W H I T E P A P E R F E B R U A R Y 2 0 1 8 Table of Contents Disclaimer 1 Introduction 2 Using SecureFiles 2 Migration Techniques 3 Migration with Online Redefinition
RAC Database on Oracle Ravello Cloud Service O R A C L E W H I T E P A P E R A U G U S T 2017 Oracle Ravello is an overlay cloud that enables enterprises to run their VMware and KVM applications with data-center-like
Oracle Big Data SQL Release 3.2 The unprecedented explosion in data that can be made useful to enterprises from the Internet of Things, to the social streams of global customer bases has created a tremendous
Siebel CRM Applications on Oracle Ravello Cloud Service ORACLE WHITE PAPER AUGUST 2017 Oracle Ravello is an overlay cloud that enables enterprises to run their VMware and KVM applications with data-center-like
Oracle Advanced Compression with Oracle Database 12c Release 2 O R A C L E W H I T E P A P E R S E P T E MB E R 2 0 1 7 Disclaimer The following is intended to outline our general product direction. It
An Oracle White Paper: November 2011 Installation Instructions: Oracle XML DB XFILES Demonstration Table of Contents Installation Instructions: Oracle XML DB XFILES Demonstration... 1 Executive Overview...
April 2013 Understanding Federated Single Sign-On (SSO) Process Understanding Federated Single Sign-On Process (SSO) Disclaimer The following is intended to outline our general product direction. It is
Oracle Database 12c: JMS Sharded Queues For high performance, scalable Advanced Queuing ORACLE WHITE PAPER MARCH 2015 Table of Contents Introduction 2 Architecture 3 PERFORMANCE OF AQ-JMS QUEUES 4 PERFORMANCE
MySQL CLOUD SERVICE Propel Innovation and Time-to-Market The #1 open source database in Oracle. Looking to drive digital transformation initiatives and deliver new modern applications? Oracle MySQL Service
An Oracle White Paper January 2013 Oracle Hyperion Planning on the Oracle Database Appliance using Oracle Transparent Data Encryption Executive Overview... 3 Introduction... 3 Hyperion Planning... 3 Oracle
Oracle Partitioning in Oracle Database 12c Release 2 Extreme Data Management and Performance for every System O R A C L E W H I T E P A P E R M A R C H 2 0 1 7 Disclaimer The following is intended to outline
October 2017 Oracle Application Express Statement of Direction Disclaimer This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle.
Insider s Guide on Using ADO with Database In-Memory & Storage-Based Tiering Andy Rivenes Gregg Christman Oracle Product Management 16 November 2016 Safe Harbor Statement The following is intended to outline
An Oracle White Paper February 2012 Benefits of an Exclusive Multimaster Deployment of Oracle Directory Server Enterprise Edition Disclaimer The following is intended to outline our general product direction.
An Oracle White Paper September 2011 Oracle Utilities Meter Data Management 2.0.1 Demonstrates Extreme Performance on Oracle Exadata/Exalogic Introduction New utilities technologies are bringing with them
Oracle Database Vault DBA Administrative Best Practices ORACLE WHITE PAPER MAY 2015 Table of Contents Introduction 2 Database Administration Tasks Summary 3 General Database Administration Tasks 4 Managing
An Oracle White Paper May 2014 Integrating Oracle SuperCluster Engineered Systems with a Data Center s 1 GbE and 10 GbE s Using Oracle Switch ES1-24 Introduction... 1 Integrating Oracle SuperCluster T5-8
Migrating VMs from VMware vsphere to Oracle Private Cloud Appliance 2.3.1 O R A C L E W H I T E P A P E R O C T O B E R 2 0 1 7 Table of Contents Introduction 2 Environment 3 Install Coriolis VM on Oracle
APPLICATION CONTAINER CLOUD Application Container Cloud with Java SE and Node The Best Java SE and Node Cloud. Get the choice of either Oracle Java SE Advanced, including Flight Recorder for production
Oracle Diagnostics Pack For Oracle Database ORACLE DIAGNOSTICS PACK FOR ORACLE DATABASE Oracle Enterprise Manager is Oracle s integrated enterprise IT management product line, and provides the industry
An Oracle White Paper October 2013 Deploying and Developing Oracle Application Express with Oracle Database 12c Disclaimer The following is intended to outline our general product direction. It is intended
Oracle Grid Infrastructure 12c Release 2 Cluster Domains O R A C L E W H I T E P A P E R N O V E M B E R 2 0 1 7 Table of Contents Introduction 2 Clustering with Oracle Clusterware 12c Release 2 3 Oracle
Deploy VPN IPSec Tunnels on Oracle Cloud Infrastructure White Paper September 2017 Version 1.0 Disclaimer The following is intended to outline our general product direction. It is intended for information
New Oracle NoSQL Database APIs that Speed Insertion and Retrieval O R A C L E W H I T E P A P E R F E B R U A R Y 2 0 1 6 1 NEW ORACLE NoSQL DATABASE APIs that SPEED INSERTION AND RETRIEVAL Introduction
An Oracle White Paper December, 3 rd 2014 Oracle Metadata Management v184.108.40.206.1 Oracle Metadata Management version 220.127.116.11.1 - December, 3 rd 2014 Disclaimer This document is for informational purposes.
An Oracle White Paper September, 2011 Oracle Real User Experience Insight Server Requirements Executive Overview Oracle Enterprise Manager is Oracle s integrated enterprise IT management product line and
An Oracle White Paper September 2010 Handling Memory Ordering in Multithreaded Applications with Oracle Solaris Studio 12 Update 2: Part 2, Memory Introduction... 1 What Is Memory Ordering?... 2 More About
Oracle Database Appliance X7-2 Model Family MANAGING ORACLE DATABASE WITH A PURPOSE BUILT SYSTEM ORACLE WHITE PAPER OCTOBER 2017 Introduction The Oracle Database Appliance, introduced in 2011, is an Oracle
Oracle Cloud Infrastructure Virtual Cloud Network Overview and Deployment Guide ORACLE WHITEPAPER JANUARY 2018 VERSION 1.0 Table of Contents Purpose of this Whitepaper 1 Scope & Assumptions 1 Virtual Cloud
Oracle Database Security Assessment Tool With data breaches growing every day along with the evolving set of data protection and privacy regulations, protecting business sensitive and regulated data is
An Oracle White Paper September 2010 Upgrade Methods for Upgrading to Oracle Database 11g Release 2 Introduction... 1 Database Upgrade Methods... 2 Database Upgrade Assistant (DBUA)... 2 Manual Upgrade...
Oracle Database 12c Release 2 for Data Warehousing and Big Data O R A C L E W H I T E P A P E R N O V E M B E R 2 0 1 6 Disclaimer The following is intended to outline our general product direction. It
Oracle Communications Interactive Session Recorder and Broadsoft Broadworks Interoperability Testing Technical Application Note Disclaimer The following is intended to outline our general product direction.
An Oracle White Paper August 2010 Building Highly Scalable Web Applications with XStream Disclaimer The following is intended to outline our general product direction. It is intended for information purposes
An Oracle Technical White Paper September 2012 Detecting and Resolving Oracle Solaris LUN Alignment Problems Overview... 1 LUN Alignment Challenges with Advanced Storage Devices... 2 Detecting and Resolving
An Oracle Technical White Paper October 2011 Sizing Guide for Single Click Configurations of Oracle s MySQL on Sun Fire x86 Servers Introduction... 1 Foundation for an Enterprise Infrastructure... 2 Sun
TABLE OF CONTENTS DOCUMENT HISTORY 3 UPDATE 18A 3 Revision History 3 Overview 3 Order Management 4 Test to Production Rule Migration 4 Pricing 4 Improve Price List Import 4 Manage Pricing Rules and Pricing
Implementing Fibre Channel SAN Boot with the Oracle ZFS Storage Appliance January 2014 By Tom Hanvey; update by Peter Brouwer Version: 2.0 This paper describes how to implement a Fibre Channel (FC) SAN
Differentiate Your Business with Oracle PartnerNetwork Specialized. Recognized by Oracle. Preferred by Customers. Joining Oracle PartnerNetwork differentiates your business, connects you with customers,
An Oracle White Paper June 2011 Oracle Service Registry - Oracle Enterprise Gateway Integration Guide 1 / 19 Disclaimer The following is intended to outline our general product direction. It is intended
Oracle Fusion Middleware Getting Started with Oracle Data Integrator 12c Virtual Machine Installation Guide July 2017 Oracle Fusion Middleware Getting Started with Oracle Data Integrator, 12c Copyright
PeopleSoft Fluid Navigation Standards Fluid User Experience ORACLE WHITE PAPER OCTOBER 2015 Disclaimer The following is intended to outline our general product direction. It is intended for information
Oracle ZFS Storage Appliance: Ideal Storage for Virtualization and Private Clouds O R A C L E W H I T E P A P E R M A R C H 2 0 1 7 Table of Contents Introduction 1 The Value of Having the Right Storage
Oracle WebLogic Server Multitenant: The World s First Cloud-Native Enterprise Java Platform KEY BENEFITS Enable container-like DevOps and 12-factor application management and delivery Accelerate application
Was ist dran an einer spezialisierten Data Warehousing platform? Hermann Bär Oracle USA Redwood Shores, CA Schlüsselworte Data warehousing, Exadata, specialized hardware proprietary hardware Introduction
An Oracle White Paper February 2010 Benefits of Using the Solaris 10 OS with Oracle Directory Server Enterprise Edition Benefits of using Solaris TM 10 OS with Oracle Directory Server Enterprise Edition
Oracle Service Cloud Agent Browser UI November 2017 What s New TABLE OF CONTENTS REVISION HISTORY... 3 OVERVIEW... 3 WORKSPACES... 3 Rowspan Workspace Designer Configuration Option... 3 Best Answer Incident
Implementing Oracle database12c s Heat Map and Automatic Data Optimization to Optimize the Database Storage Cost and Performance Kai Yu Oracle Solutions Engineering Dell Inc Agenda Database Storage Challenges
INTEGRATION CLOUD SERVICE Accelerate Your Application Across the Cloud and On Premises With Oracle Cloud Service you can innovate at a faster pace. Oracle Cloud Service gives you a powerful and intuitive
CONTAINER CLOUD SERVICE Managing on Why Container Service? The cloud application development and deployment paradigm is changing. Docker containers make your operations teams and development teams more
An Oracle White Paper September, 2009 Oracle Database 11g for Data Warehousing and Business Intelligence Introduction Oracle Database 11g is a comprehensive database platform for data warehousing and business
An Oracle Technical White Paper March 2014; v2.1 Best Practice Guide for Implementing VMware vcenter Site Recovery Manager 4.x with Oracle ZFS Storage Appliance Introduction... 1 Overview... 2 Prerequisites...
An Oracle White Paper October 2010 Minimizing Planned Downtime of SAP Systems with the Virtualization Technologies in Oracle Solaris 10 Introduction When business-critical systems are down for a variety
Oracle Financial Consolidation and Close Cloud What s New in the March Update (17.03) February 2017 TABLE OF CONTENTS REVISION HISTORY... 3 ORACLE FINANCIAL CONSOLIDATION AND CLOSE CLOUD, MARCH UPDATE...
Oracle Enterprise Data Quality 18.104.22.168 New Features Overview Integrated Profiling, New Data Services, New Processors O R A C L E W H I T E P A P E R J U L Y 2 0 1 6 Table of Contents Executive Overview
Oracle Privileged Account Manager Disaster Recovery Deployment Considerations O R A C L E W H I T E P A P E R A U G U S T 2 0 1 5 Disclaimer The following is intended to outline our general product direction.
Oracle Database 12c Product Family O R A C L E W H I T E P A P E R M A R C H 2 0 1 7 Disclaimer The following is intended to outline our general product direction. It is intended for information purposes
An Oracle White Paper March 2012 How to Define an Importer Returning Error Messages to the Oracle Web Applications Desktop Integrator Document Disclaimer The following is intended to outline our general
Oracle Mobile Application Framework Oracle Mobile Application Framework (Oracle MAF) is a hybrid-mobile development framework that enables development teams to rapidly develop single-source applications
Oracle Java SE Advanced for ISVs Oracle Java SE Advanced for ISVs is designed to enhance the Java based solutions that ISVs are providing to their enterprise customers. It brings together industry leading
An Oracle White Paper June 2011 Oracle Virtual Directory 11g Oracle Enterprise Gateway Integration Guide 1 / 25 Disclaimer The following is intended to outline our general product direction. It is intended
Oracle Warehouse Builder 10g Release 2 Integrating Packaged Applications Data June 2006 Note: This document is for informational purposes. It is not a commitment to deliver any material, code, or functionality,
Oracle Database Vault with Oracle Database 12c ORACLE WHITE PAPER MAY 2015 Table of Contents Introduction 1 Controls for Privileged Accounts 2 Privilege User Access Controls on Application Data with Realms
APPLICATION BUILDER CLOUD Application Creation Made Easy Today s environment demands that your business... be able to adjust quickly to evolving requirements from the market, from your customers, as well
Oracle Developer Studio 12.6 Oracle Developer Studio is the #1 development environment for building C, C++, Fortran and Java applications for Oracle Solaris and Linux operating systems running on premises
Oracle GoldenGate for Big Data The Oracle GoldenGate for Big Data 12c product streams transactional data into big data systems in real time, without impacting the performance of source systems. It streamlines
Oracle Financial Consolidation and Close Cloud What s New in the December Update (16.12) December 2016 TABLE OF CONTENTS REVISION HISTORY... 3 ORACLE FINANCIAL CONSOLIDATION AND CLOSE CLOUD, DECEMBER UPDATE...
StorageTek ACSLS Manager Software Management of distributed tape libraries is both time-consuming and costly involving multiple libraries, multiple backup applications, multiple administrators, and poor
An Oracle White Paper July 2011 Oracle WebCenter Portal: Copying a Runtime-Created Skin to a Portlet Producer Introduction This white paper describes a method for copying runtime-created skins from a WebCenter
An Oracle Technical White Paper September 2010 Oracle VM Templates for PeopleSoft 1 Disclaimer The following is intended to outline our general product direction. It is intended for information purposes
Oracle Financial Consolidation and Close Cloud What s New in the February Update (17.02) February 2017 TABLE OF CONTENTS REVISION HISTORY... 3 ORACLE FINANCIAL CONSOLIDATION AND CLOSE CLOUD, FEBRUARY UPDATE...
An Oracle Technical Article August 2017 Certification with Oracle Linux 7 Oracle Technical Article Certification with Oracle Linux 7 Introduction... 1 Comparing Oracle Linux 7 and Red Hat Enterprise Linux
Implementing Oracle Database 12c s Heat Map and Automatic Data Optimization to optimize the database storage cost and performance Kai Yu, Senior Principal Engineer, Oracle Solutions Engineering, Dell Inc
Your consent to our cookies if you continue to use this website.