eProseed Oracle Open World 2016 debrief - Oracle 12.2.0.1 Database

Copyright © 2014, eProseed and/or its affiliates. All rights reserved. | Confidential
$ WHOAMI
 Marco Gralike
 Principal Consultant
 eProseed, NL
 Oracle ACE Director for XMLDB / JSON / (IM)DB
 marco.gralike@eproseed.com
 Database Beta Test Lead since DB 11.1.0.6
 Personal website
 www.xmldb.nl
 www.gralike.com
2

ORACLE OPEN WORLD 2016
Database 12.2.0.1
3

AN OVERVIEW - ORACLE DATABASE 12.2
Part of this info is under NDA and can not yet be
shared (fully) outside eProseed like “sharding”…
4

WHEN AVAILABLE...?
5

MULTITENANT
7

• Online PDB…
– clone
– refresh
– reallocate
• 4096 PDB’s possible now (instead of 252)
• Application Containers
– An application container consists of an application root and one or more
application PDBs. The container stores data for a specific application, which
contains common data and metadata. You can upgrade or patch the
application once in the application root, and then synchronize the
application PDBs with the root.
8

• Application Containers
– Application Container Root
• PDB – A01
• PDB – A02…
Setup 
9

UPGRADE  ROOT APPLICATION CONTAINER
• Begin an upgrade of the app
– ALTER PLUGGABLE DATABASE APPLICATION saas_sales_app BEGIN UPGRADE '1.0' to '2.0';
<<<do stuff to upgrade the application pdb environment>>>
• End app upgrade
– ALTER PLUGGABLE DATABASE APPLICATION saas_sales_app END UPGRADE TO '2.0';
• SYNC the PDB’s to the new version (if needed)
– ALTER PLUGGABLE DATABASE APPLICATION […] SYNC
10

“SOME” STATEMENTS…
• ALTER PLUGGABLE DATABASE …APPLICATION… […]
– BEGIN INSTALL, END INSTALL
– BEGIN UPGRADE, END UPGRADE
– BEGIN PATCH, END PATCH
• Simple upgrades like ALTER TABLE
• Not simple  “operation not supported in an application patch” error  use BEGIN UPGRADE
– SYNC | SYNC ALL
11

CLONE  ROOT APPLICATION CONTAINER
12

RELOCATING  PLUGGABLE DATABASES
• CREATE PLUGGABLE DATABASE […]
FROM […] RELOCATE;
CREATE PLUGGABLE DATABASE hrpdb
FROM hrpdb@hrpdb_link RELOCATE;
13

PROXY PLUGGABLE DATABASE
• A proxy PDB provides access to another PDB either in
a remote or in the same CDB.
• A local proxy PDB is in the same CDB as its referenced
PDB, whereas a remote proxy PDB is in a different
CDB.
• A proxy PDB can reside in an application container.
• CREATE PLUGGABLE DATABASE […] AS PROXY
FROM […]
– must specify a database link to the referenced PDB
14

ADDITIONAL IMPROVEMENTS
• During a PDB clone operation, the source PDB no longer needs to be in readonly mode
• Flashback PDB and PDB restore points
– FLASHBACK PLUGGABLE DATABASE
• PDB lockdown profiles
• CREATE LOCKDOWN PROFILE medium;
• ALTER LOCKDOWN PROFILE medium DISABLE STATEMENT=('ALTER SYSTEM');
• ALTER LOCKDOWN PROFILE medium ENABLE STATEMENT=('ALTER SYSTEM') CLAUSE=('FLUSHSHARED POOL');
• PDBDEV> ALTER SYSTEM PDB_LOCKDOWN = ‘medium’
• Performance manageability enhancements (tightened to a specific PDB)
• Temporary tablespace
• CREATE TEMPORARY TABLESPACE (now called “shared”)
• CREATE LOCAL TEMPORARY TABLESPACE
15

SMALL RECAP / OVERVIEW FROM OOW SLIDES
16

17

18

SHARDING (NDA)
19

REASONING BEHIND IT…
20

BASICS
21

SHARDING ENVIRONMENT
22

BITS AND PIECES
• Oracle Sharding is implemented based on the Oracle Database partitioning feature.
• Shard Directors
– Shard directors route requests to the individual shards.
– Connection uses a shard director, which a lightweight global listener that redirects connection requests
to appropriate shards.
• Shard Catalog
– The shard catalog enables centralized life-cycle management of a sharded database and contains the
master copy of all duplicated tables in a Sharded Database (SDB) environment.
– a persistent store for SDB configuration data
• CREATE SHARDCATALOG
• ADD GSM; START GSM (create and start shard directors)
• CREATE SHARD (for each shard)
• DEPLOY
23

IN MEMORY DATABASE
24

WHAT IS AND/OR WHY?
25

ARCHITECTURE 12.1.0.2
26

IMCU-S AND SMU POOL
27

ARCHITECTURE 12.2.0.1
28

SOME NEW FEATURES
• In-Memory Expressions
– compressed columnar format
– frequently used query expressions
– JSON (via JSON Dataview)
• In-Memory FastStart
– Tablespace dedicated to flush data to or use content during DB startup
• In-Memory Virtual Columns
– Precalculated virtual column data in the memory store ( with if possible using SIMD processing)
• IMDB support for Oracle Active Dataguard
• ADO – Automatic Data Optimization support for IMDB
– Auto / constraint automatic loading in memory & offloading
– Zone/heat maps support (if “hot data” IMDB, if not “get out IMDB”)
29

JSON IN THE DATABASE
30

NEW JSON FEATURES IN THE DATABASE
• Generating JSON
• PL/SQL JSON Support
• JSON Dataview
– Automatic JSON schema generation
– Automatic relational view creation on JSON
– Automatic adding of virtual columns with relational content based on JSON
– Automatic JSON in IMDB using Dataview / VC / In Memory Expressions
• JSON Materialized View support (for IMDB)
31

JSON OPERATORS
• JSON_ARRAY
• JSON_OBJECT
• JSON_ARRAYAGG
• JSON_OBJECTAGG
32

JSON_ARRAY
33

JSON_OBJECT
34

JSON_ARRAYAGG
35

JSON_OBJECTAGG
36

BIG DATA / RELATED
37

…
40

• External tables based on Hadoop (HDFS & Hive) content
• Hybrid external tables
• Partitioned external tables

ORACLE EXADATA EXPRESS (12.2)
42

WHEN AVAILABLE...?
44

DOCUMENTATION
Currently on the internet:
• Oracle Database Exadata Express Cloud Service (main)
• Oracle Database Exadata Express Cloud Service (toc)
• Oracle Database New Features
• Database JSON Developer’s Guide (new!)
48

eProseed Oracle Open World 2016 debrief - Oracle 12.2.0.1 Database

More Related Content

What's hot (20)

Viewers also liked (6)

Similar to eProseed Oracle Open World 2016 debrief - Oracle 12.2.0.1 Database (20)

More from Marco Gralike (20)

Recently uploaded (20)

eProseed Oracle Open World 2016 debrief - Oracle 12.2.0.1 Database

Editor's Notes