Oracle Exadata SIG - nlOUG · PDF fileDifferent Ways to Upgrade and Migrate to Oracle Database 12c . ... •Standby Database Upgrades ... EM Cloud Control

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

Oracle Exadata SIG 12c – Database & Enterprise Manager

Different Ways to Upgrade and Migrate to Oracle Database 12c

Jan van Tiggelen Principal Sales Consultant Oracle Database Technology


Upgrade to Oracle Database 12c Oracle

7.3.4

Oracle

8.0.6

Oracle

8.1.7.4

Oracle

9.0.1.4

Oracle

9.2.0.8

Oracle

10.1.0.5

Oracle

10.2.0.5

Oracle

11.1.0.7

Oracle

11.2.0.2

Oracle

12.1.0.1/2

Oracle 7.3 (GA: 1996)

Oracle 8.0 (GA: 1997

Oracle 8.1 (GA: 1998)

Oracle 9.0 (GA: 2001)

Oracle 9.2 (GA: Jul 2002)

Oracle 10.1 (GA: Jan 2004)

Oracle 10.2 (GA: Jul 2005)

Oracle 11.1 (GA: Aug 2007)

Oracle 11.2 (GA: Sep 2009)

Oracle 12.1 (GA: Jun 2013)

DIRECT 11.2.0.2

DIRECT 11.1.0.7

DIRECT 10.2.0.5

11.2.0.2 9.2.0.8 7.3.4

11.2.0.2 9.2.0.8 8.0.6

10.2.0.5 8.1.7.4

10.2.0.5 9.0.1.4

11.2.0.2 9.2.0.8

11.2.0.2 10.1.0.5

Please note: This graph will apply to database upgrades only!



Upgrade Options to Oracle Database 12c

Oracle 11.1

Less Downtime?

Oracle 11.2.0.1/2

Oracle 10.2

Oracle 11.2.0.3/4

Near-Zero Downtime?

Transportable Tablespaces

Logical Standby

Golden Gate +

Transient Standby

Full Transportable Export/Import

RMAN Inc Bck +

expdp/impdp

catctl.pl

DBUA HW



• catctl.pl

• Runs database upgrade in parallel

• Up to 40% faster upgrade

• Used and proven by selected Oracle Database 11g global customers

– Telco billing

– >100 SAP systems

– Large DWH

New Parallel Upgrade

Faster Upgrade – Less Downtime

catctl.pl

script3.sql script2.sql script1.sql

script4.sql

script5.sql

script6.sql

script6.sql

script7.sql

script8.sql

script9.sql

script10.sql

script11.sql



• Mass Upgrades

• Grid Infrastructure Upgrades

• RAC Database Upgrades

• Standby Database Upgrades

Note: Requires Lifecycle Management Pack

EM Cloud Control

Enterprise Manager Mass and RAC Upgrades



Migration Options to Oracle Database 12c

Oracle 11.1

Less Downtime?

Oracle 11.2.0.1/2

Oracle 10.2

Oracle 11.2.0.3/4

Near-Zero Downtime?

Golden Gate +

Full Transportable Export/Import

RMAN Inc Bck +

Transportable Tablespaces

expdp/impdp

SQL*Loader

CTAS, COPY

TDB Only same Endianness



Oracle Database and Exadata Compression



Oracle Database Compression Overview Compression Feature Application Fit Availability

Query Compression • Data Warehouses

• Scan Oriented Access

Exadata/SuperCluster, ZFS Storage (NAS), Axiom (SAN)

Archive Compression • All Applications

• Cold / Historical Data

Exadata/SuperCluster, ZFS Storage (NAS), Axiom (SAN)

OLTP Table Compression • All Applications

• Actively Updated Data

Database 11g Advanced Compression

SecureFiles Comp/De-dupe • All Applications

• Unstructured (File) Data


Network Compression • Data Guard Redo

• Transport Compression


Backup Compression • RMAN Compression

• Data Pump Compression


Basic Compression • Direct Path Load

• Data Warehousing

Database 9i Core Feature

Public 10


Hybrid Columnar Compression Overview

• Hybrid Columnar Compressed Tables

– New Approach to Compress Database Tables and Partitions

– Compressed Tables Can Still be Modified using Conventional DML Operations, such as INSERT and UPDATE

– Useful for Data that is Bulk Loaded and Queried

•Update Activity is Light (Archive)

• How it Works

– Tables are Organized into Compression Units (CUs)

• Compression Units are Larger than Database Blocks

– Within Compression Unit, Data is Organized by Column Instead of by Row

• Column Organization Brings Similar Values Close Together, Enhancing Compression

Compression Unit

10x to 15x Storage Reduction

Public 11


Heat Map

• 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 – Data modification times are tracked at the row level and aggregated to the block level

– Modification times, full table scan times, and index lookup times are tracked at the segment level


0101101110101010010100100100001000 1010101101001011010011100001010010

Archive Data

01110000101000101101110

10101001010010010000100

01010101101001011

010101001010010010001

Automatic Data Optimization Usage Based Data Compression

14

Hot Data

3X

Advanced Row Compression

Warm Data

1010101011101010011010111000010100010110

1110101010010100100100001000101010110100

1011010011100001010010010100001001000010

0010101011010010

10X

Columnar Query Compression

1000010100100101001010110111000010

10101010111010100110101110000101000101101110

10101001010010010000100010101011010010110100

11100001010010010100001001000010001010

101010101110101001101011100001010001011011

15X

Columnar Archive Compression

01110101010010 10000100010101 01011100001010

10101010111010100110101110

00010100010110111010101001

01001001000010001010101101

00101101001110000101001001

01000010010000100010101011

10011010

10100101001001000010001

1110010100100101001010110111011010

101010101110101001101011100001011101011001


Multitenant

Public 15


AP OE GL

New Multitenant Architecture Memory and processes required at container level only

16

System Resources

GL OE AP


GL OE AP

Oracle Database Architecture More efficient utilization of system resources

17

System Resources


Managing Shared Resources Resource management in a multitenant environment

18

GL OE AP

High Priority Medium Priority Low Priority


Exadata for Database as a Service (DBaaS)

Public 19


Enterprise Database-as-a-Service

• Enterprise Database-as-a-Service is the new approach

• Consolidates and virtualizes hardware and software to dramatically reduce management and costs

• Brings cloud simplicity, standardization, and agility to databases in the enterprise

• Improves performance, availability and security while ensuring QoS for mixed workloads

Enterprise DBaaS

Public 20


New Oracle DB 12c Multitenant Architecture Pluggable Databases (PDB) Share Resources and Administration

A Transformational Architecture for Database Cloud • Operational cost of one database and OS, benefits of many databases

• One database patch, upgrade, backup, standby, monitoring

• Dynamically provision or upgrade a database in minutes

• Completely transparent to Applications

Many Databases each in an OS & VM

Sales DB

Assets DB

Billing DB

VM

O/S

Parts DB

VM

O/S

VM

O/S

VM

O/S

Single O/S, No VMs Needed

Single Multitenant Database

Billing PDB

Parts PDB

Sales PDB

Assets PDB

Single Physical Container Database

Public 21


End-to-End DBaaS and Platform Management

• End-to-End Management in a single pane

• Manage Database Services

• And Underlying Platform

– Hardware

• All Exadata components

– Software

• Deep Database and OS tools

Public 22


Exadata Resource Management and Workload Balancing

Public 23


L L H

IORM: I/O Scheduling for Quality of Service

Finance Database

Exadata Storage Server

L L L

H H H H

Low Priority DSS Consumer Group Queue

OLTP Consumer Group Queue

I/O Resource Manager Finance Database

Sales Database

L L

H H H

Low Priority DSS Consumer Group Queue

OLTP Consumer Group Queue

Sales Database

Low Priority

High Priority

Public 24


IORM for Multiple Databases

• Manage I/Os between databases

• Important for database consolidation

• Configure an inter-database IORM plan

Inter-Database IORM Plan

Database Shares

Sales 4

Marketing 1

Support 1

Other 1

Shares for “Other” are used for all other

databases

Public 25


Inter and Intra Database IORM

0

10

20

30

40

50

60

70

80

90

100

Disk Utilization

Support (1 share)

Marketing (1 share)

Sales (2 shares) - Batch (1 share)

Sales (2 shares) - Critical (4 shares)

Inter-database IORM plan controls how disk is utilized between

databases

Database resource plan controls how disk is utilized between

Consumer Groups in a database

Public 26


Setting cpu_count: Partition Approach to Manage CPU

0

4

8

12

16

20

24

28

32

cpu_count settings • Partition CPUs among the database

instances

• sum(cpu_counts) <= # cpu threads

• Partitioning provides maximum isolation

• No CPU contention between instances

• But if one instance is idle, its CPU allocation is unused

• Best for performance-critical databases

Number of CPUs

Instance A: 8 CPUs

Instance B: 8 CPUs

Instance C: 4 CPUs

Instance D: 4 CPUs

Public 27


Setting cpu_count: Over-Subscribe Approach

0

4

8

12

16

20

24

28

32

cpu_count settings • Over-subscribe the CPUs among the database instances

• sum(cpu_counts) <= 3 x # cpu threads

• Monitor CPU utilization to see if there’s room!

• Over-subscribing provides efficient CPU utilization

• Some contention for CPU if databases are sufficiently loaded

• Contention is controlled, so system is still stable

• Best for non-critical databases

Number of CPUs

Instance A: 8 CPUs

Instance B: 8 CPUs

Instance C: 8 CPUs

Instance D: 8 CPUs

Public 28


Instance Caging to CDB Resource Plans • Pre-12c: databases managed with Instance Caging

• 12c: PDBs managed with CDB Resource Plans

• To convert from Instance Caging to CDB Resource plans

– Use cpu_count as PDB’s “share”

– Use cpu_count / num_cpus as PDB’s “utilization limit” (optional!)

Database Name cpu_count

SALES 16

MARKETING 8

SUPPORT 8

PDB Name Shares Utilization Limit

SYS 16 50%

GOLD 8 25%

SILVER 8 25%

is equivalent to

Public 29


Exadata Network Resource Management

• Exadata Network Resource Management uniquely prioritizes critical database messages through the entire fabric

– From database to InfiniBand card through InfiniBand switches to storage

– Latency sensitive messages prioritized over batch, reporting, and backup messages

– Log file writes have highest priority to ensure low latency transactions

• Compliments Exadata CPU and IO Resource management to ensure safe consolidation of workloads and databases

• Completely automatic & transparent 0

100000

200000

300000

400000

0 2 4 6 8 10 12

Tra

nsa

cti

on

s p

er

Se

c

Time

Without Network RM, OLTP

performance drops when a

network intensive workload is

introduced

Network Resource Management maintains steady performance

DB Version 11.2.0.4 or 12c, Switch 2.1.3-4

New

Public 30

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Different Ways to Upgrade and Migrate to Oracle Database 12c

Documents

Oracle Exadata SIG - nlOUG · PDF fileDifferent Ways to Upgrade and Migrate to Oracle Database 12c . ... •Standby Database Upgrades ... EM Cloud Control