Safe Harbor Statement - DOAG

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |

Safe Harbor Statement

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.

Oracle Confidential – Internal/Restricted/Highly Restricted 2


Agenda

Oracle Database In-Memory Overview

Oracle Database In-Memory Advisor

ORACLE ZDLRA & Backup?

3

1

2

3


Oracle Database In-Memory


Until Now Must Choose One Format and Suffer Tradeoffs

Row Format Databases vs. Column Format Databases

Row

Transactions run faster on row format

– Example: Insert or query a sales order – Fast processing few rows, many columns

Column

Analytics run faster on column format

– Example : Report on sales totals by region – Fast accessing few columns, many rows

SALES

SALES

5


• BOTH row and column formats for same table

• Simultaneously active and transactionally consistent

• Analytics & reporting use new in-memory Column format

• OLTP uses proven row format

6

Normal Buffer Cache

New In-Memory Format

SALES SALES

Row Format

Column Format

SALES

*

Breakthrough: Dual Format Database


• Pure in-memory column format Not persistent, and no logging Quick to change data: fast OLTP

• 2x to 20x compression typical

• Enabled at table or partition level Not all columns need to be populated Just active data in-memory

• Data populated into memory in In-Memory Compression Units

7

SALES

In-Memory Columnar

IMCU IMCU

IMCU IMCU

IMCU IMCU

Oracle Database In-Memory Columnar Technology


Why is an IM scan faster than the buffer cache?

SELECT COL4 FROM MYTABLE;

8

X X X X X

RESULT

Row Format

Buffer Cache


Why is an IM scan faster than the buffer cache?

SELECT COL4 FROM MYTABLE;

9

RESULT

Column Format

IM Column Store

RESULT

X X X X X


• Each CPU core scans local in-memory columns

• Scans use super fast SIMD vector instructions

Originally designed for graphics & science

• Billions of rows/sec scan rate per CPU core

Row format is millions/sec

10

Vec

tor

Reg

iste

r

Load multiple region values

Vector Compare all values an 1 cycle

CPU

Memory

REG

ION

CA

CA

CA

CA

Example: Find sales in region of CA

> 100x Faster

Orders of Magnitude Faster Analytic Data Scans


New SGA Component: In-Memory Area

In-Memory Area

Buffer Cache Shared Pool Large Pool

Redo Log Flashback Java Pool

Fixed SGA

SQL> sho sga

Total System Global Area 2415919104 bytes

Fixed Size 2927240 bytes

Variable Size 436209016 bytes

Database Buffers 889192448 bytes

Redo Buffers 13848576 bytes

In-Memory Area 1073741824 bytes


Populating : In-Memory Column Store

• New INMEMORY ATTRIBUTE

• Following segment types are eligible Tables Partitions Subpartition Materialized views

• Following segment types not eligible IOTs Hash clusters Out of line LOBs

CREATE TABLE customers ……

PARTITION BY LIST

(PARTITION p1 …… INMEMORY,

(PARTITION p2 …… NO INMEMORY);

ALTER TABLE sales INMEMORY;

ALTER TABLE sales NO INMEMORY;

ALTER TABLE lineorder INMEMORY MEMCOMPRESS FOR QUERY LOW

PRIORITY CRITICAL;

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 13

Populating : In-Memory Column Store


SELECT owner, segment_name, bytes orig_size, inmemory_size in_mem_size,

bytes / inmemory_size comp_ratio, bytes_not_populated not_populated,

FROM v$im_segments;

How to : In-Memory Column Store


select count(*) from sales where quantity_sold>30 or (quantity_sold<10 and prod_id=5000);

Plan hash value:672559287

-------------------------------------------------------------------

| Id | Operation | Name | Pstart| Pstop |

-------------------------------------------------------------------

| 0 | SELECT STATEMENT | | | |

| 1 | SORT AGGREGATE | | | |

| 2 | PARTITION RANGE ALL | | 1 | 16 |

|* 3 | TABLE ACCESS INMEMORY FULL| SALES | 1 | 16 |

-------------------------------------------------------------------

Predicate Information (identified by operation id):

---------------------------------------------------

3 - inmemory(("QUANTITY_SOLD">30 OR "QUANTITY_SOLD"<10) AND

("QUANTITY_SOLD">30 OR "PROD_ID"=5000 AND "QUANTITY_SOLD"<10))

filter("QUANTITY_SOLD">30 OR "PROD_ID"=5000 AND

"QUANTITY_SOLD"<10)

Execution Plan Display


Monitoring im Cloud Control


New In-Memory Central Screen in EM

In-Memory Area (GB) :4.00

In-Memory Area Used (GB) :1.79

Object mapping in 12c Heatmap integriert


• Extremely fast data processing

• Extremely fast features for Data Warehousing (vector technologies)

• Fully transparent to applications – no change for software development

• Fully transparent to operations – no change for administration, B&R, HA concepts

• Runs together with all other options, e.g. partitioning, pluggable database, data guard, etc.

• Cost effective storage of data. Best of memory, flash, disk, cloud

In-Memory DB Option Summary

20


Oracle Database In-Memory Advisor


Why In-Memory Advisor?

• How to optimize database In-Memory Column Store for maximum analytics performance

• How to size In-Memory Column Store?

• What database objects to place In-Memory?

In-Memory Advisor


Features

• Assists with IM Column Store size selection

• Recommends tables, partitions and sub partitions for a given IM Column Store size

• Uses workload and performance data to prioritize objects

• Takes into account differences in disk and memory footprint, as well as compression ratios

• Recommendation based on cost/benefit calculations

• Cost: Estimated memory size with various compression options

• Benefit: Estimated DB time reduction of processing analytic workload

In-Memory Advisor


• Analyzes existing workload via AWR & ASH repositories

• Provides list of objects that would benefit most from being populated into IM column store

• Works on database versions 11.2.0.3 and above

• Recommendations can be implemented on database 12.1.0.2

24

Object Type

Object Estimated In-

Memory Size

Estimated Analytic

Performance Improvement

Table SALES.ORDERS 2.19 GB 9.3X

Table SALES.LINEITEM 1.03 GB 5.2X

Partition SALES.PRODUCTS.201404 415 MB 4.3X

Sub-partition SALES.PRODUCTS.20140330 200 MB 2.7X

In-Memory Advisor Output


• In addition to html reports, In-Memory Advisor produces a SQL script to configure your objects In-Memory:

ALTER TABLE SALES.H_CUSTOMER INMEMORY MEMCOMPRESS FOR QUERY LOW; ALTER TABLE SALES.H_ORDER INMEMORY MEMCOMPRESS FOR QUERY HIGH; ALTER TABLE SALES.H_PART INMEMORY MEMCOMPRESS FOR QUERY HIGH; ALTER TABLE SALES.H_PARTSUPP INMEMORY MEMCOMPRESS FOR QUERY LOW; ALTER TABLE SALES.H_SUPPLIER INMEMORY MEMCOMPRESS FOR QUERY LOW;

25

In-Memory Advisor Output—SQL Script


In-Memory Advisor – General Info

• Download from My Oracle Support (MOS) note 1965343.1 – imadvisor.zip

– Whitepaper on how to install and run the Advisor

• Licensing – In-Memory Advisor is part of the Tuning Pack

• Supported versions – Database 11.2.0.3 and above

– Recommendations can be implemented on Database 12.1.0.2



Installing the Advisor

• Advisor installation is a SQL script – instimadv.sql

• Creates IMADVISOR user

• Installs package – DBMS_INMEMORY_ADVISOR



Running the Advisor - 1

• Advisor ships with script imadvisor_analyze_and_report.sql

• Input – task_name: identifier for the analysis

– Time range: time period for workload ASH and AWR to be analyzed

• Output: – imadvisor_task_name.html – report of findings

– imadvisor_task_name.sql – SQL script to implement the recommendations in database 12.1.0.2




• You can also write your own Advisor script

• Why? – Adjust Advisor defaults settings

• Available parameters described in Appendix 3 of whitepaper

• GET_PARAMETER, SET_PARAMETER, RESET_PARAMETER procedures

– Specify a SQL Tuning Set as an input

• Example script in Appendix 1 of the whitepaper




• Advisor also can be run on a separate test database

• Export performance data from production database: – $ORACLE_HOME/rdbms/admin/awrextr.sql

– imadvisor_awr_augment_export.sql

• Import that data in your test database: – $ORACLE_HOME/rdbms/admin/awrload.sql

– imadvisor_awr_augment_import.sql

• Run the Advisor – Use procedure on previous slide - need to specify DBID



Best Practices

• Run the Advisor on a substantial, real workload – Database In-Memory improves ‘analytic’ workloads – long running

queries that do large table scans

– If the workload you run the Advisor on is not analytic, the results will be trivial / not interesting

– Minimum analysis time of 2 hours or (4 x elapsed time of longest running query) recommended

• Use SPA to validate the performance improvements of Advisor recommendations



Resources

• My Oracle Support (MOS) note 1965343.1.

• Database In-Memory OTN page

• In-Memory Advisor OTN page

• In-Memory Advisor Best Practices Whitepaper

• Trouble Free Upgrade to Database 12c with Real Application Testing


http://www.oracle.com/technetwork/database/in-memory/overview/index.html



http://www.oracle.com/technetwork/database/manageability/inmemory-advisor-2412222.html



http://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdf



http://www.oracle.com/technetwork/oem/db-mgmt/con8248-upgrade-with-rat-2332583.pdf


Oracle ZDLRA


Zero Data Loss Recovery Appliance

35

Brauchen Sie einen grundsätzlich anderen Ansatz zum Schutz von Geschäftsdaten kritische Datenbank...


Recovery-Appliance einzigartige Vorteile für Business und IT

Minimale Backups

Produktionsdatenbanken senden nur Änderungen.

Vermeiden von Datenverlusten

Echtzeit-Redo-Transport bietet sofortigen Schutz der laufenden Geschäftsvorfälle

Skalierbarkeit in der Cloud

Einfache Sicherung aller Datenbanken im Rechenzentrum mit massiver Skalierung

Database Level Recoverability

End-to-end Sicherheit, Sichtbarkeit und Kontrolle über die Datenbanken


Zero Data Loss Recovery Appliance Overview

37

Delta Push

•DBs access and send only changes • Minimal impact on production

•Real-time redo transport instantly protects ongoing transactions

Protected Databases

Protects all DBs in Data Center

• Petabytes of data • Oracle 10.2-12c, any platform • No expensive DB backup agents

Delta Store

• Stores validated, compressed DB changes on disk • Fast restores to any point-in-time using deltas • Built on Exadata scaling and resilience • Enterprise Manager end-to-end control

Recovery Appliance

Replicates to Remote Recovery Appliance

Offloads Tape Backup


Data Guard ähnliche Sicherung für alle Datenbanken

38

Generische Bit-Kopie Backup Appliance

• Tägliches Backup • “Data loss”: alle Transaktionen seit dem letzten backup

Zero Data Loss Recovery Appliance

• Verwendet Data Guard kontinuierliches “real-time redo transport” um laufende Transaktionen sofort zu schützen.

Protected Databases

Datenverlust ist von Natur aus schlecht. Noch schlimmer...Es schafft massive Konsistenz Fragen über Datenbanken


Delta-Only Architecture No More Full Backups: Database Optimized Incremental-Forever

Delta Push

Delta Push Source Deduplication

• Fast Incremental Backup - Never reads duplicate blocks - Never sends duplicate blocks • Eliminates Undo Blocks for committed transactions • Eliminates Unused Blocks

Delta Store Backup Management

• Stores only change data • Compresses at block-level • Ships only Deltas to Replica

Protected Database Compressed Delta Store

Dramatic Database I/O & Network Savings

Change Data

No more full backups, only changes

Disaster Recovery

39


Wie administriere ich die ZDLRA?

40

… Administrierung & Monitoring über Cloud Control


Weitere Informationen…

ZDLRA Produktüberblick

https://www.oracle.com/engineered-systems/zero-data-loss-recovery-appliance/index.html

ZDLRA Data Sheet

http://www.oracle.com/technetwork/database/availability/recovery-appliance-ds-2297776.pdf

http://www.oracle.com/us/products/oracle-zdlra-final1-2301371.pdf

6 Gründe für Exadata – Exadata Database Machine, 22.07.2014 41 Frank Schneede, BU Database









Oracle Security Portfolio

INFRASTRUCTURE

Information & Services

DATABASE MIDDLEWARE APPLICATION INTERACTION

Operating Systems (Oracle Linux, Oracle Solaris)

Storage (Tape, Disk)

Server

Appliances

Database

DB Vault

Audit Vault

Advanced Security Option (ASO)

Data Masking

Secure Backup

Identity Govern. Life Cycle Role Life Cycle Privileged Account

Access Managem. SingleSignOn Authorisations Federations Mobile & Social Integrations Risk & Fraud

Oauth

Directory Services

Risk & Compliance Manager; Segregation of Duty

Configuration Management

Transaction Guard

Policy Manager

Securing mobile und stationary devices

Integrating social networks

Oracle Components

Safe Harbor Statement - DOAG

Documents

Transcript of Safe Harbor Statement - DOAG