Which two statements about Automatic Data Optimization (ADO) are true?

Question

Options

• AADO policies can automatically compress data when it qualifies.
• BADO policies can automatically move segments when necessary.
• CADO is not dependent on Heat Map, and works even if Heat Map is disabled.
• DYou cannot compress at block level, but you can compress at segment level.
• EYou can compress at row level only for QUERY LOW.

• A
  75% (21)
• C
  4% (1)
• D
  7% (2)
• E
  14% (4)

Explanation

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. This exponential growth of data presents daunting challenges for IT. First and foremost are storage costs: even though the cost of storage has been declining dramatically, the enormous growth in the volume of data makes storage one of the biggest cost elements of most IT budgets. In addition, as databases grow at accelerating rates, it is difficult to continue to meet performance requirements while staying within budget. In Oracle Database 12c, several new features have been added to the Oracle Advanced Compression option which enhances the storage management capabilities of Oracle Database. Heat Map automatically tracks modification and query timestamps, providing detailed insights into how data is being accessed. Automatic Data Optimization (ADO) automatically moves and compresses data based on the information collected by Heat Map. Together, these capabilities help to implement Information Lifecycle Management (ILM) strategies. Heat Map and ADO make it easy to use existing innovations in Oracle Database compression technologies, which can help reduce the cost of managing large amounts of data, while also improving application and database performance. The Oracle Advanced Compression option includes a comprehensive set of compression features designed to reduce costs and improve performance by enabling compression for structured data, unstructured data, database backups, network traffic and for Data Guard Redo. In addition to Heat Map and ADO, other new features in the Oracle Advanced Compression option include Advanced Network Compression, Advanced Index Compression, Optimization of Flashback Data Archive History Tables, Storage Snapshot Optimization and Online Move Partition to compressed formats. Oracle Advanced Compression The Oracle Advanced Compression option provides a comprehensive set of compression capabilities to help customers improve performance while reducing storage costs. It allows IT administrators to significantly reduce their overall database storage footprint by enabling compression for all types of data -relational (table), unstructured (file), index, network and backup Although storage cost savings and optimization across servers (production, development, QA, Test, Backup and etc...) are often seen as the most tangible benefits, all of the features in the Oracle Advanced Compression option are designed to improve performance for all components of your IT infrastructure, including memory, network bandwidth and storage. Business requirements are not the same for all data in a database. Data goes through various stages in its lifecycle: It starts out as active data, when the data is first inserted and then frequently queried and modified; this data is an ideal candidate for Advanced Row Compression. After some period of time, data typically becomes less active - a time period when it is queried often, for example for report generation, however it is modified rarely; this data is an ideal candidate for Hybrid Columnar Warehouse Compression. In the final stage, data becomes more or less dormant - it is no longer updated and is queried very infrequently, if at all, but it must be kept for compliance and regulatory purposes; this data can be compressed using Hybrid Columnar Archive Compression. Heat Map is a new Oracle Database feature that collects usage information at the block and segment levels. By using Heat Map in conjunction with Automatic Data Optimization - see the Automatic Data Optimization section below - Oracle Database 12c can automate compression and storage policies based on the usage of the data, reducing storage costs, improving performance and optimizing storage. At the segment level, Heat Map tracks the timestamps of the most recent modification and query of each table and partition in the database. At the block level, Heat Map tracks the most recent modification timestamp. These timestamps are used by Automatic Data Optimization to define compression and storage policies which will be automatically maintained throughout the lifecycle of the data. Heat Map skips internal operations done for system tasks -- automatically excluding Stats Gathering, DDLs, Table Redefinitions and similar operations. In addition, Heat Map can be disabled at the session level, allowing DBA's to exclude manual maintenance, avoiding pollution of Heat Map data. With the data collected by Heat Map, Oracle Database can automatically compress each partition of a table independently based on Heat Map data, implementing compression tiering. This compression tiering can use all forms of Oracle table compression, including: Advanced Row Compression and all levels of Hybrid Columnar Compression (HCC) if the underlying storage supports HCC. Oracle Database can also compress individual database blocks with Advanced Row Compression based on Heat Map data.

No community discussion yet for this question.