Vous êtes sur la page 1sur 29
Exadata MAA Best Practices Migrating Oracle Databases Doug Utzig Exadata and MAA Best Practices August
Exadata MAA Best Practices Migrating Oracle Databases Doug Utzig Exadata and MAA Best Practices August
Exadata MAA Best Practices Migrating Oracle Databases Doug Utzig Exadata and MAA Best Practices August
Exadata MAA Best Practices Migrating Oracle Databases Doug Utzig Exadata and MAA Best Practices August

Exadata MAA Best Practices Migrating Oracle Databases

Doug Utzig Exadata and MAA Best Practices

August 2012

Key Points <Insert Picture Here> 2

Key Points

Key Points <Insert Picture Here> 2
<Insert Picture Here>
<Insert Picture Here>
Key Points <Insert Picture Here> 2
Migrating to Exadata 1. Migration Preparation is Essential 2. Pick the Right Migration Method 3.

Migrating to Exadata

1. Migration Preparation is Essential

2. Pick the Right Migration Method

3. Fast Network Reduces Migration Time

1. Migration Preparation is Essential 2. Pick the Right Migration Method 3. Fast Network Reduces Migration
Key Point #1 Migration Preparation is Essential Simplify and Optimize during migration leads to the

Key Point #1

Key Point #1 Migration Preparation is Essential Simplify and Optimize during migration leads to the best
Key Point #1 Migration Preparation is Essential Simplify and Optimize during migration leads to the best

Migration Preparation is Essential

Simplify and Optimize during migration leads to the best performance and highest availability on Exadata.

is Essential Simplify and Optimize during migration leads to the best performance and highest availability on
Migration Goal • Move your data Simplify and Optimize – Get rid of baggage –

Migration Goal

Move your data

Simplify and Optimize

Get rid of baggage

–

Better performance

Better resource utilization

Better stability

and Optimize – Get rid of baggage – Better performance – Better resource utilization – Better
and Optimize – Get rid of baggage – Better performance – Better resource utilization – Better
Database Migration to Exadata Learn Exadata Learn Exadata Database Machine Target Environment Oracle Database 11g

Database Migration to Exadata

Learn Exadata

Database Migration to Exadata Learn Exadata Learn Exadata Database Machine Target Environment Oracle Database 11g Release

Learn Exadata Database Machine

Target Environment

Oracle Database 11g Release 2 Upgrade Guide Upgrade Companion (MOS 785351.1)

Automatic Storage Management (ASM)

Oracle Real Application Clusters (RAC)

Linux 64bit or Solaris x86

Exadata software maintenance (MOS 888828.1)

Oracle Real Application Clusters (RAC) Linux 64bit or Solaris x86 Exadata software maintenance (MOS 888828.1) 6
Database Migration to Exadata Simplify and Optimize Simplify and Optimize For Exadata Smart storage Hybrid

Database Migration to Exadata

Simplify and Optimize

Simplify and Optimize

For Exadata

Smart storage

Hybrid Columnar Compression (HCC)

For Best Practice (MOS 757552.1)
For Best Practice (MOS 757552.1)

Default init.ora

Undecorated SQL (w/ good stats)

Improved schema object layout

Fewer tablespaces and data files

Large database extent size

Character set (MOS 123670.1)

object layout Fewer tablespaces and data files Large database extent size Character set (MOS 123670.1) 7
Database Migration to Exadata Prepare Source and Exadata Target Migration Preparation Prepare source system Database

Database Migration to Exadata

Prepare Source and Exadata Target

Migration Preparation

Prepare source system

Database upgrade to 11.2

Hardware upgrade

Drop unnecessary schema objects

Prepare Exadata system
Prepare Exadata system

ASM Configuration

Redundancy

compatible.rdbms

Install latest versions (MOS 888828.1)

Review Exadata Critical Issues (MOS

1270094.1)

• compatible.rdbms Install latest versions (MOS 888828.1) Review Exadata Critical Issues (MOS 1270094.1) 8
Migration Strategy Test • Use Real Production Workload – Real Application Testing (RAT) • Database

Migration Strategy

Test

Use Real Production Workload

Real Application Testing (RAT)

Database Workload Replay

SQL Performance Analyzer (SPA)

Database Workload Replay • SQL Performance Analyzer (SPA) 1. Test migration to non-Exadata Linux x86-64 +
Database Workload Replay • SQL Performance Analyzer (SPA) 1. Test migration to non-Exadata Linux x86-64 +

1. Test migration to non-Exadata Linux x86-64 + ASM

Oracle 11g Release 2

Latest Exadata database patch (MOS 888828.1)

2. Test on your Exadata system

3. Test again for good measure

2 – Latest Exadata database patch (MOS 888828.1) 2. Test on your Exadata system 3. Test
Key Point #2 Pick the Right Migration Method There are many ways to migrate to

Key Point #2

Pick the Right Migration Method

Key Point #2 Pick the Right Migration Method There are many ways to migrate to Exadata
Key Point #2 Pick the Right Migration Method There are many ways to migrate to Exadata

There are many ways to migrate to Exadata - the “best” way depends on your environment and goals.

Migration Method There are many ways to migrate to Exadata - the “best” way depends on
Migration Methods   Migration Method Downtime factor   Data Guard Physical Standby Switchover (11.2)

Migration Methods

 

Migration Method

Downtime factor

 

Data Guard Physical Standby

Switchover (11.2)

Physical

Change rate + upgrade (11.1)

Block for block copy

 
   

Whole tablespace or database

Transportable Tablespaces

Data size

Typically best for OLTP

Transportable Database

Data size

Logical

Data Pump

Data size

Unload, reload with SQL

   

Easy to subset

Insert as Select

Data size

Typically best for DW

 

GoldenGate

Client reconnect

HA Options

Cross Platform Incremental Backups (w/ TTS)

Change rate + metadata size

Use in conjunction with other method to reduce downtime

Data Guard Transient Logical Standby

Client reconnect

Use in conjunction with other method to reduce downtime Data Guard Transient Logical Standby Client reconnect
High Availability Options • Cross Platform Incremental Backups – Reduce downtime for Transportable Tablespaces

High Availability Options

Cross Platform Incremental Backups

Reduce downtime for Transportable Tablespaces

Oracle GoldenGateBackups – Reduce downtime for Transportable Tablespaces – Reduce downtime for any method – Zero data

Reduce downtime for any method

Zero data loss fallback

Phased migration

method – Zero data loss fallback – Phased migration Data Guard Transient Logical Standby – Reduce

Data Guard Transient Logical Standbymethod – Zero data loss fallback – Phased migration – Reduce upgrade downtime coming from 11.1

Reduce upgrade downtime coming from 11.1 for Physical Standby

migration Data Guard Transient Logical Standby – Reduce upgrade downtime coming from 11.1 for Physical Standby
Reduce Migration Downtime XTTS + Cross Platform Incremental Backups ( MOS 1389592.1) • Standard XTTS

Reduce Migration Downtime

XTTS + Cross Platform Incremental Backups (MOS 1389592.1)

Standard XTTS but most data moved while source online

Reduce Downtime f(change rate + metadata size)

Traditional XTTS

Tablespaces

READ ONLY

Tablespaces READ ONLY Transfer and Convert Datafiles Export, Tablespaces

Transfer and Convert Datafiles

Tablespaces READ ONLY Transfer and Convert Datafiles Export, Tablespaces

Export,

Tablespaces READ ONLY Transfer and Convert Datafiles Export, Tablespaces

Tablespaces

Import

Metadata

READ

WRITE

XTTS w/ Incrementals

Key

Uptime

Downtime

Transfer and Convert Backup

Transfer and Convert Backup Create and Tablespaces READ ONLY Create and Export, Tablespaces

Create and

Transfer and Convert Backup Create and Tablespaces READ ONLY Create and Export, Tablespaces

Tablespaces

READ ONLY

Transfer and Convert Backup Create and Tablespaces READ ONLY Create and Export, Tablespaces

Create and

Transfer and Convert Backup Create and Tablespaces READ ONLY Create and Export, Tablespaces

Export,

Transfer and Convert Backup Create and Tablespaces READ ONLY Create and Export, Tablespaces

Tablespaces

Apply

Incremental

Apply

Incremental

Import

Metadata

READ

WRITE

and Export, Tablespaces Apply Incremental Apply Incremental Import Metadata READ WRITE 13
and Export, Tablespaces Apply Incremental Apply Incremental Import Metadata READ WRITE 13
Reduce Migration Downtime Oracle GoldenGate • Log-based data replication cross platform and version • Downtime

Reduce Migration Downtime

Oracle GoldenGate

Log-based data replication cross platform and version

Downtime f(client reconnect)

1. Instantiate target using any physical or logical method

2. Keep target in sync using GoldenGate

3. Redirect clients to target for switchover

Oracle 9.2 or later

Data type constraints

ARCHIVELOG and LOGGING

Oracle 9.2 or later • Data type constraints • ARCHIVELOG and LOGGING Source Oracle GoldenGate Exadata

Source

Oracle GoldenGate
Oracle
GoldenGate
Oracle 9.2 or later • Data type constraints • ARCHIVELOG and LOGGING Source Oracle GoldenGate Exadata

Exadata target

Oracle 9.2 or later • Data type constraints • ARCHIVELOG and LOGGING Source Oracle GoldenGate Exadata
Zero Data Loss Fallback and Phased Migration Oracle GoldenGate • Zero data loss fallback –

Zero Data Loss Fallback and Phased Migration

Oracle GoldenGate

Zero data loss fallback

After migration, switch replication direction

Redirect clients to source for fallback

Phased migration

Bi-directional replication

Pre-migration

Pre-migration Source Exadata target Post-migration Source Exadata target
Pre-migration Source Exadata target Post-migration Source Exadata target
Pre-migration Source Exadata target Post-migration Source Exadata target

Source

Exadata target

Post-migration

Pre-migration Source Exadata target Post-migration Source Exadata target
Pre-migration Source Exadata target Post-migration Source Exadata target
Pre-migration Source Exadata target Post-migration Source Exadata target

Source

Exadata target

S o u r c e Exadata target

Source

S o u r c e Exadata target

Exadata target

Pre-migration Source Exadata target Post-migration Source Exadata target S o u r c e Exadata target
Which One? • Your best approach – Application-specific requirements? • Oracle E-Business Suite (MOS 1133355.1)

Which One?

Your best approach

Application-specific requirements?

Oracle E-Business Suite (MOS 1133355.1)

Are you Simplified and Optimized?

Will you Simplify and Optimize?

HCC? During migration or after?

Source platform and source version?

Database size?

How much downtime?

Experience level?

Other business requirements?

Database size? – How much downtime? – Experience level? – Other business requirements? Best may not

Best may not be fastest

Database size? – How much downtime? – Experience level? – Other business requirements? Best may not

Scenario 1

Scenario 1 From Existing Exadata Database Machine (V1 or X2) • Simplified and Optimized already (?)

From Existing Exadata Database Machine (V1 or X2)

Simplified and Optimized already (?)

HCC released in 11gR2

Option When to Use 1 Data Guard Physical Standby •First choice 2 Data Guard Transient
Option
When to Use
1
Data Guard
Physical Standby
•First choice
2
Data Guard
Transient Logical Standby
•Reduce upgrade downtime from 11.1
Physical Standby •First choice 2 Data Guard Transient Logical Standby •Reduce upgrade downtime from 11.1 18

Scenario 2

Scenario 2 From Little Endian (Non-Exadata) • Example: Windows -> Exadata Option When to Use 1

From Little Endian (Non-Exadata)

Example: Windows -> Exadata

Option When to Use 1 Data Guard Physical Standby •No need to Simplify and Optimize
Option
When to Use
1
Data Guard
Physical Standby
•No need to Simplify and Optimize
2
Data Guard
Transient Logical Standby
•Reduce upgrade downtime from 11.1
3
Data Pump
•Simplify and Optimize
•Full data type support
•Cross platform support
4
GoldenGate
•Reduce downtime
•Zero data loss fallback
•Phased migration
support •Cross platform support 4 GoldenGate •Reduce downtime •Zero data loss fallback •Phased migration 19

Scenario 3

Scenario 3 From Big Endian • Example: AIX / HP-UX / SPARC -> Exadata Option When

From Big Endian

Example: AIX / HP-UX / SPARC -> Exadata

Option When to Use 1 Transportable Tablespaces •No need to Simplify and Optimize 2 Transportable
Option
When to Use
1
Transportable Tablespaces
•No need to Simplify and Optimize
2
Transportable Tablespaces + Cross
Platform Incremental Backups
•No need to Simplify and Optimize
•Reduce downtime
3
Data Pump
•Simplify and Optimize
4
GoldenGate
•Reduce downtime
•Zero data loss fallback
•Phased migration
Data Pump •Simplify and Optimize 4 GoldenGate •Reduce downtime •Zero data loss fallback •Phased migration 20
Key Point #3 Fast Network Reduces Migration Time Having a fast network is important for

Key Point #3

Key Point #3 Fast Network Reduces Migration Time Having a fast network is important for quick
Key Point #3 Fast Network Reduces Migration Time Having a fast network is important for quick

Fast Network Reduces Migration Time

Having a fast network is important for quick migration, but watch out for bottlenecks in other areas.

Migration Time Having a fast network is important for quick migration, but watch out for bottlenecks
Networks for Moving Data • 3 network choices – No fibre channel • Best Practice

Networks for Moving Data

3 network choices

No fibre channel

Best Practice

Network Ports (Full Rack) 10 Gb/s Ethernet 16 40 Gb/s InfiniBand 8 1 Gb/s Ethernet
Network
Ports (Full Rack)
10 Gb/s Ethernet
16
40 Gb/s InfiniBand
8
1 Gb/s Ethernet
24 (14 in X2-8)

Large MTU

IPoIB connected mode

Use all database servers

Active/active bonding on Ethernet

Requires customer switch support

Do not change InfiniBand to active/active

Active/active bonding on Ethernet • Requires customer switch support • Do not change InfiniBand to active/active
Bottleneck Not Always the Network • Non-network bottlenecks – Slow source system I/O – CPU

Bottleneck Not Always the Network

Non-network bottlenecks

Slow source system I/O

CPU to send and receive

IB network
IB network

1GB_file

# scp 1GB_file 192.168.20.139:/tmp

Slow
Slow

100% 1060MB 66.3MB/s

00:16

CPU max
CPU max

Small I/O

scp(1) 4KB I/O

# scp 1GB_file 192.168.20.139:/tmp Slow 100% 1060MB 66.3MB/s 00:16 CPU max – Small I/O • scp(1)

23

Moving Data Direct to ASM • Databases on Exadata use ASM – Direct to ASM

Moving Data Direct to ASM

Databases on Exadata use ASM

Direct to ASM network transfer

RMAN BACKUP AS COPY AUXILIARY

DBMS_FILE_TRANSFER

Convert during XFR 11.2.0.3 backport

ASMCMD CP

Tool

1 stream

4 stream

DFT

217

MB/s

771 MB/s

RMAN

585

MB/s

1542 MB/s

Active/active 10Gb/s Ethernet

Use latest versions if different endian

–

Bytes transferred != bytes written

MB/s Active/active 10Gb/s Ethernet – Use latest versions if different endian – Bytes transferred != bytes
Staging Data • Staging space – DBFS • Recommended for best performance • MOS 1054431.1

Staging Data

Staging space

DBFS

Recommended for best performance

MOS 1054431.1

NFS

NOT local disk

Data • Staging space – DBFS • Recommended for best performance • MOS 1054431.1 – NFS
Data • Staging space – DBFS • Recommended for best performance • MOS 1054431.1 – NFS
Key Points and Business Takeaways 26

Key Points and Business Takeaways

Key Points and Business Takeaways 26
Key Points and Business Takeaways 26
Key Points and Business Takeaways 26
Migrating to Exadata Key Points and Takeaways 1. Migration Preparation is Essential Simplify and Optimize

Migrating to Exadata

Key Points and Takeaways

1. Migration Preparation is Essential

Points and Takeaways 1. Migration Preparation is Essential Simplify and Optimize during migration leads to the

Simplify and Optimize during migration leads to the best performance and highest availability on Exadata.

2. Pick the Right Migration Method

There are many ways to migrate to Exadata - the “best” way depends on your environment and goals.

3. Fast Network Reduces Migration Time

Having a fast network is important for quick migration, but watch out for bottlenecks in other areas.

Migration Time Having a fast network is important for quick migration, but watch out for bottlenecks
Migrating to Exadata Resources and References • Planning – Latest Exadata Software (MOS 888828.1) –

Migrating to Exadata

Resources and References

Planning

Latest Exadata Software (MOS 888828.1)

Upgrade Companion (MOS 785351.1)

Methods

Physical

MAA on OTN

MOS 1055938.1, 413484.1, 1133355.1

Logical

MAA on OTN

MOS 737460.1, 1055938.1, 1085687.1

High Availability Options

MOS 1389592.1

Oracle GoldenGate on OTN

Network and Staging

DBFS (MOS 1054431.1)

Options • MOS 1389592.1 • Oracle GoldenGate on OTN • Network and Staging – DBFS (MOS
30
30

30

31
31

31