Oracle Database 12c Release 2 Training - doag.org · Title: Oracle Database 12c Release 2 Training...

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

Oracle Database 12c Release 2 A short Overview

1

Harald Wolf Sales Consulting Oracle Deutschland B.V. & Co.KG


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.


Agenda

Releaseplan – Cloud First

Availability – Everything a bit better

Admin – Optimize Daily Work

Database In-Memory – Getting faster and faster

Security – Comprehensive and more in-depth

Multitenant – Latest improvements

Sharding – Highest Performance for special cases

Express Cloud Service – Nothing is cheaper

3


• 12.2 planned Jan./Feb. CY2017 –we will release “cloud first” using

the “Exadata Express” Cloud Service

– then we will release for download and other Oracle Database Cloud Services

• Refer to MOS (My Oracle Support) note 742060.1

4

Oracle Database 12c R 2 Schedule (Rolling Release)

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

Oracle Database 12c Release 2 Major Features

Massive Cost Savings and Cloud Agility with Multitenant

Plus more features for better Performance, Availability, Security, Analytics, and Application Development Massive = »Mächtig gewaltig, Egon!«... die Olsenbande!

Massive Web Applications with Sharding

Massive Performance with Database In-Memory


Current Industry Trends : Dev Ops

6

Software defined infrastructure

Closer collaboration between developers (left)

and operations (right)

Continuous Delivery (Appl., Infra, Monitoring)


Current Industry Trends : In Memory

7

Continued decreasing cost of

memory

Non Volatile Memory becomes more widely

available (ORLs + TEMP) Die Platte wird 60!!!

$

Increasing demand for Real Time Analytics


Hybrid Cloud Scenarios

Architecture Spanning

• Big Data SQL Cloud Service

• Multitenant with Proxy PDBs

• Sharding

Use Case Specific

• Backup Service

• Hybrid Data Guard (DR)

Multi Cloud

• Oracle compatible hybrid cloud

• GoldenGate Service

• Integration Service

8

Dev Test

Prod

DR

Oracle Solutions


Multitenant

• Location transparency for applications spanning PDBs

Big Data SQL

• Cold Data migrates to file system(Hadoop, OnPrem or Cloud)

Sharding

• Global web-scale “shard-friendly” applications

Hybrid Cloud Architecture Spanning

9

Big Data SQL

With Oracle Database 12c


Agenda









10


Availability – Continuous Innovation & Improvement

11

Cloud Internet Client-Server

1990s 2000s 2010s

Oracle 5, 6, 7, 8 Oracle 8i, 9i, 10g Oracle 11g, 12c

Availability Transactions Referential Integrity

Crash Recovery Online Backup Point-in-Time

Recovery

Data Guard Recovery Manager

Flashback Query/DB/Table Portable Clusterware

Online DDL Transparent App Failover

Active Data Guard Zero Data Loss Recovery

Appliance Edition Based Redefinition

Application Continuity Express Cloud Service


More 12.2 High Availability Innovations

Application Continuity

• Planned maintenance enhancements

Active Data Guard • Diagnostic, Tuning, SQL Plan Analyzer and

In-Memory on Standby • No user disconnect on failover • Multi-node parallel apply in RAC • High-speed block comparison between

Primary and Standby • More secure (SSL-based redo transport,

automatically maintain password files)

More partition maintenance operations now online (“Hermann the German”)

Online Table Move

12

SALESTABLE

Q1 Q2 Q3


Oracle Database 12c Release 2 : Real Application Clusters Scalability and Availability

Better scalability (for singleton services) supporting cloud bursting

Efficient management of large scale deployments

Better availability due to reduced reconfiguration times


• Service-oriented Buffer Cache Access over time determines the data (on database object level) accessed by the service. This information

– Is persisted in the database.

– Is used to improve data access performance (e.g. do not manage data of a service in an instance that does not host the service).

– Can be used to pre-warm an instance cache prior to a service startup (fresh start or relocation).

Optimized Singleton Workload Scaling (Restore Affinity) Service-oriented Buffer Cache Access (Optimized Reconfiguration Time)


1 0 1 0 1 0 1 0 0 0 0 1 0 0 1 1 1 0 0 1 0 1 0 0 1

1 0 1 1 1 0 0 1 0 1 0 0 1 1 1 0 0 1 0 1 0 0 1 0 1

0 0 1 0 0 1 0 1 0 0 0 0 1 1 1 1 0 1 0 1 0 0 1 0 1

1 0 1 0 1 0 1 0 0 0 0 1 0 0 1 1 1 0 0 1 0 1 0 0 1 0 1 0 0 1 0 1 0 0 1 0 0 1 1 1 0 0 1 0 1 0 0 1 0 1 0 0 1 0 0

1 0 1 1 1 0 0 1 0 1 0 0 1 1 1 0 0 1 0 1 0 0 1 0 1 1 1 1 1 1 0 1 0 0 1 1 1 0 0 1 0 1 0 0 1 0 1 1 1 1 0 1 1 0 1

0 0 1 0 0 1 0 1 0 0 0 0 1 1 1 1 0 1 0 1 0 0 1 0 1 0 0 1 0 1 0 1 0 0 1 0 0 1 1 0 1 0 1 0 0 1 0 1 0 1 0 1 0 0 0

15

• Using Oracle Multitenant, PDBs can be opened as singletons (in one RAC-Instance only), in a subset of instances or in all instances at once.

• If certain PDBs are only opened on some instances, Pluggable Database Isolation

– improves performance by • Reducing DLM operations for

PDBs not open in all instances.

• Optimizing block operations based on in-memory block separation.

– improves availability by • Ensuring that instance failures of instances

only hosting singleton PDBs will not impact other instances of the same RAC-based CDB.

Optimized Singleton Workload Scaling Pluggable Database Isolation

NEW IN 12.2 PRIOR TO 12.2 Inter Cluster Messages


• Node Weighing is a new feature that considers the workload hosted in the cluster during fencing

• The idea is to let the majority of work survive, if everything else is equal

– Example: In a 2-node cluster, the node hosting the majority of services (at fencing time) is meant to survive

– Further aspects (e.g. ASM instance availability or public network availability) are taken into consideration

• DBAs can overrule and rate a service as a “critical” based on business needs

Node Weighting in RAC 12.2 Idea: If Everything else is equal Let the majority of workload survive Formerly: Quite inflexible

✔







Node Weighting in RAC 12.2 Idea: Everything equal, let the majority of work survive

✔


Agenda









19


Management – Continuous Innovation & Improvement

20

Cloud Internet Client-Server

1990s 2000s 2010s

Oracle 5, 6, 7, 8 Oracle 8i, 9i, 10g Oracle 11g, 12c

Management Enterprise Manager V$ Views

Explain Plan Wait Events SQL Tracing

Diagnostics Pack Tuning Pack

Testing Packs Lifecycle Pack

AWR, ASH SQL Monitor

Multitenant Database Database Appliance

Database & Exadata Cloud


12.2 Manageability Improvements

AWR Enhancements

• Per PDB AWR Support

• PDB Snapshots

• Support for ADG Standby

Real Application Testing

• Improved scalability for large workloads

• Improved PL/SQL replay for long running calls

EM Express

• Improved Multitenant support

• Simpler configuration

• SPA and Resource Manager support

21

EM Cloud Control

• Support for Sharding

• Management of large volume PDB environment


12.2 Manageability Improvements continued

Index Usage Statistics

• Track index usage with no overhead

• Views provide usage histograms and access

22

SQL Tuning Advisor

• Support for ADG Standby


Agenda









23


In-Memory DB Option - Resumee

• „Turbo-Lader“ an bewährte Technologie „geflanscht“ Nicht komplett neue Datenbank (30 Jahre Evolution)

• 5 Faktoren für Perf.: Columnar representation, In-Memory, Compressed, Highly-Parallel (SIMD=Single Instruction for Multiple Data), ext. Parallel

• IM gibt es schon sehr, sehr lange: BiiN, VLDB: 32-Bit sind kalter Kaffee....

• Siemens-PLM Projekt: PROD-Server Linux 2 TB => OEM alles grün

• IMDB: Software sehr stabil und performant!!!

• IMDB Option auf allen Plattformen verfügbar (AIX, HP-UX, Linux, Solaris, Windows,...)

• Aber, In-Memory ist nicht die Lösung aller Probleme...


Keep Cache (seit ca. 10 Jahren, seit 10g)

• Wartungsfenster zum Durchstarten der DB – Unbedingt SGA_MAX_SIZE oder MEMORY_MAX_SIZE anpassen

– KEEP_CACHE Größe festlegen (Gesamt SGA beachten !!!)

• Objekte für den KEEP_CACHE definieren – Über AWR Report (Physical Segments Read)

• Nach dem Hochfahren der DB den KEEP Cache beladen – Full table scan bei den entsprechenden Tabellen

z.B. mit select /*+ FULL */

• In Monitoring einbinden, LRU verhalten des Keep Cache

Vorgehensweise für den Einsatz


“Einschalten” von Oracle In-Memory ist trivial…

1. In-Memory Größe konfigurieren (1!!! Parameter)

• inmemory_size = XXXX GB

2. Tabellen oder Partitionen für In-Memory festlegen • alter table | partition … inmemory;

Einzelne Spalten möglich

(Online Laden und Entladen)

3. Später drop “analytic” Indexes “Speed up” DML und Platz sparen


Important to Know... • IM default compression

– typical factor 6x to raw data on disk

• inmemory_size – Typical: 5-15% of raw data on disk

– Example: 10TB database IM-Cache = 1TB

• High Degree of Parallelism helpful – Single-User 40x

– Multi-User 4x

• Define Degree of Parallelism – System-Wide (Auto-DOP)

– or on selected Tables for In-Memory

• Operating the Database No Changes at all!!! No Risk!!! – Administration, Backup/Recovery, HA, ...

– In-Memory fully integrated in Cloud Control 12c/13c

27


Oracle DB In-Memory Beta Test @ German Customer

• SAP BW (After-Market Part-Sales) Database

• Environment – Linux, 500GB Memory, 40 Cores, 1.1TB Database

• Migrated in 30 Minutes – Includes: Install 12c, Upgrade 11g->12c, Load

Tables In-Memory

– Same hardware, same operating procedures, same processes

– NO application change, NO Risc, NO Island

• Performance Gain 8x to 16x

28


What’s new in 12.2 for Database In-Memory

2X Faster Joins 4X Faster

Expressions

Real-Time Analytics Automation

Dynamic Data Movement Between Storage &

Memory (ILM)

Massive Capacity

In-Memory on Exadata Flash

Column

On OLTP or DW

Active Data Guard

Support

Row Column

Multi-model

Native support for JSON Data type

29


Agenda









30


Audit Data, Event Logs

31

Database Firewall Users

Policies

Reports

Alerts

Network Events

Applications

Audit Vault

Audit Vault and Database Firewall 12.2

Databases


New in 12.2 Online Tablespace Encryption

32

• Online encryption of existing database tablespace files

• Full encryption of SYSTEM, SYSAUX, and UNDO tables (internal database structures)

• Offline tablespace encryption – 11.2.0.4 and 12.1.0.2 back port available

SALES

TABLESPACE

HCM TABLESPACE

HCM TABLESPACE

DF11233U*1 $5Ha1qui%H1 HSKQ112A14 FASqw34£$1 DF@£!1ahHH! DA45S& DD1

Acme 10 1/2/16 Acme 3 1/3/16 Acme 5 1/5/16 Acme 12 1/7/16 Acme 4 1/8/16 Acme 2 1/9/16


12.2 Security Innovations • Advanced Security Option

– Online and offline tablespace encryption – New algorithms (ARIA, SEED, GOST) for South Korean/Russian markets – Redaction of CLOB/NCLOB data identified using Regular Expressions

• Database Vault – Simulation mode for creating robust security rules for deployment – Security policy for grouping of realms, factors, and rules – Privilege Analysis uses full run-time and static usage for enforcing “Least Privilege”

• Real Application Security – RAS Administration Tool (RASADM) for authorization policies and management – Column-level Control for DMLs – Schema-wide RAS data policy management

• Auditing based upon Roles such as DBA 33


• Help SCs & partners quickly scan customer databases

– Understand risk profile and provide recommendations

– Help sales teams uncover new opportunities

• Report security risks and gaps

– Configuration, privileges, encryption, auditing, …

• Recommend relevant products

– TDE, Database Vault, AVDF, and more

• Downloadable free tool from MOS

Database Security Assessment Tool (DBSAT)

34

Enables New Security Sales Opportunities

XLS

TEXT

HTML

10.2, 11.2, 12c


Agenda









35


Key Benefits

Benefit Capability Enabled

Minimize CapEx • More applications per server

Minimize OpEx • Manage many as one (reduced patching!) • Standardized procedures & service levels • Enable self-service provisioning

Maximize Agility • Snapshot cloning for development and testing • Portability through “pluggability” • Scalability with RAC

Easy • To Adopt: Applications run unchanged • To Use: Interface is SQL


• PDB Hot Clone – Faster test master instantiation

PDB Hot Clone

CRM

HR

Oracle Cloud

Pricing Retail

On-Premises

CRM


PDB Refresh


• PDB Refresh – Simple operation for latest data

CRM

HR

Oracle Cloud

Pricing Retail

On-Premises

CRM



• PDB Refresh – Simple operation for latest data

• PDB Relocate – Relocate with no downtime

PDB Relocate

CRM

HR

Oracle Cloud

Pricing Retail

On-Premises

CRM


12.1 PDB Static, Cold Cloning

GL AP

PRODUCTION DEVELOPMENT

GLDEV APDEV OEDEV

OE

2. alter pluggable database oe open read only;

Datafile Copy

3. create pluggable database oedev from oe@dblink;

1. alter pluggable database oe close; T5

4. alter pluggable database oe open read write force; T5 4. alter pluggable database oedev open; T5

T0 T5 T50

OE OE OE OE OEDEV OEDEV

Clone SCN


12.2 PDB Hot Cloning

GL AP

PRODUCTION DEVELOPMENT

GLDEV APDEV OEDEV

OE

REDO, UNDO and Datafile Copy

T5

OE OE OEDEV OEDEV OE

T30 T0 T50 T20 T70

Begin Clone SCN

1. create pluggable database oedev from oe@dblink; T20

2. alter pluggable database oedev open; T30

End Clone SCN

Final REDO Copy and ROLLBACK


• Flashback PDB

• Per-PDB Character Set

• 4096 PDBs per Container-DB (increased from 252)

• Memory & I/O resource prioritization in addition to CPU

• Configurable isolation via Lockdown Profiles

Isolation with Economies of Scale

Retail

Pricing

Multitenant Container


What is an Application Container ?

• An Application container is a collection of PDBs consisting of Application Root and all Application PDBs associated with it. PDBs logically (applicationwise) grouped together.

43

CDB$ROOT

App Root

App PDB 1

App PDB 2

PDB1

CDB$ROOT

APP Root PDB1

App PDB 1

App PDB 2

Physical Representation Logical Representation


• Application Container comprises – Application Root (Master)

– Application PDBs (for each Tenant)

– Application Seed (for provisioning)

• PDBs share application objects – Code, metadata and data

• Further simplifies management – Apply updates to application container

– Sync tenant PDBs from central master

• Suitable for all applications – SaaS, franchise, divisional, etc.

Application Container

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

PDB as Trusted Partition

Non-CDB with licensed options and Multitenant

Multitenant with options licensed across CDB

PDB as Trusted Partition

EE 56 cores 48 cores 48 cores

Multitenant 48 cores 48 cores 48 cores

Options 4 cores per option 48 cores per option 4 cores per option

Total $XXXK + 38% -11%

# of Databases to Manage:

Consolidate diverse options with no license penalty

Spatial & Graph

Advanced Analytics

No Spatial & Graph or Advanced Analytics

48 cores 4 cores 4 cores

Spatial & Graph, Advanced Analytics licensed across CDB

48 cores

Spatial & Graph

Advanced Analytics

4 cores 4 cores 40 cores


Agenda









46


Customers Who Drove Requirements for Oracle Sharding Findet man (fast)alle zwischen SFA und San Jose ;-))

47


Custom OLTP Applications

Examples:

• Large billing systems

• Airline ticketing systems (Large)

• Online financial services (Large)

• Media companies (Large)

• Online information services (Large)

• Social media companies (Large)

Large =Peta-/Zetta-Bytes

Characteristics

• Application must specify a sharding key for optimal performance – sharding is not application transparent

– e.g. customer_id, account_id etc

• Primary usage pattern

– Direct routing to a shard based on sharding key

– Single-shard operations for highest performance

• Secondary usage pattern

– Proxy routing for multi-shard queries (reporting)

– Able to tolerate lesser performance than direct routing used for single-shard operations

48

Application Profile for Sharding


• Each shard has its own CPU, memory & disk

• Data is partitioned using a sharding key (i.e. account_id)

• Presented to the application as a single logical database

Oracle Sharding – A Database Architecture Pattern

An unsharded table in a single physical database

Server

A sharded table horizontally partitioned in N independent databases (shards)

Server A Server B Server C

A Non-sharded Database (KISS) A Sharded Database

Sharding = Shared Nothing (not really new!) „Warmed Up“ with NO-SQL DBs Who has ever dealt with Replication in his Life???


Oracle Database 12c Release 2 Offers Choice

Oracle Sharding

…

A single logical database

A single physical database

N Physical Databases

Oracle RAC

…


…

51

Oracle Database Sharding - Benefits

Linear Scalability Fault Tolerant Geographic Distribution

Add shards online to increase database throughput. Online

split and rebalance.

No shared hardware or software to isolate faults. Shards may run different

Oracle releases.

User defined data placement for performance, availability, DR or to

meet regulatory requirements.

…


Shard Director

Centralized Schema Management

52

Shard 1

Shard 2

Shard n

Shard Catalog

connect to GDS$CATALOG service

alter session enable shard ddl;

create tablespace set …

create user ...

create sharded table …

..

Create duplicated table …


Flexible Deployment On-Premises or Cloud

• Validated on Oracle IaaS with Oracle MAA Best Practice blueprint for 12.2

• Hybrid requires customers implement global routing to application tiers local to shards. Oracle sharding routes from an application tier to the appropriate shard

• Automated DBCS for sharding is on development roadmap

53

On-Premises Cloud Hybrid


License Requirements for Oracle Sharding

• Oracle Enterprise Edition is a pre-requisite – Each shard is a standalone Oracle Database

• Each shard must be licensed for one of the HA options, either Active Data Guard, GoldenGate or RAC – Includes right to deploy shard directors, the shard catalog and its Data Guard standby(s)

• Additional Active Data Guard or RAC licenses are required for catalog DB if used for catalog HA

• No separate license for Oracle Partitioning is required for sharded or duplicated tables created using Oracle Sharding

• Enterprise Manager licensing to be determined


Agenda









56


Definition of Exadata Express

What is it?

• Official name: Oracle Database Exadata Express Cloud Service

• Successor to current Schema Service

• Runs Oracle Database 12c Release 2, with options

• Leverages Pluggable Database (PDB) containerization technology

• Hosted on Oracle Exadata machines

What’s included?

• Provides preconfigured Oracle Application Express (APEX)

• Supports diverse Oracle Database clients over SQL*Net

• Supports new interfaces (in addition to SQL) including REST/JSON, documents

• Delivers database containerization advancements (e.g. lock-down, RM)

• Fully managed by Oracle, w/ automatic patching & upgrade, no DBA required

57


Customer Use Cases

58

Databases in Cloud Considering Oracle

Database Cloud Services

Database Upgrades Experimenting with

Oracle Database 12cR2


• All popular languages supported

• Full database support for – JSON

– REST

• Development tools included – Application Express

– SQL Developer

59

Application Development on Exadata Express

Free 30-day trial accounts

and more …


Database development and testing

60

Dedicated

Exadata Full-Instance

Enterprise Exadata

Express

Highest database availability, scalability and performance

SMB, departmental applications, sandboxes

Enterprise applications

DB 12.2 “Cloud First”

Spectrum of Oracle Database Cloud Services

60

Oracle Database 12c Release 2 Training - doag.org · Title: Oracle Database 12c Release 2 Training...

Documents

Transcript of Oracle Database 12c Release 2 Training - doag.org · Title: Oracle Database 12c Release 2 Training...