migrating oracle databases gert prieber

Gert Prieber Escala / AIX Product Manager

Migrating Oracle Databases

2 ©Bull, 2011 Migrating Oracle Databases with Bull OLM

Customer migration concerns

Can it be done?

Technical

Costs

Can it be done within the budget?

Schedule

Can it be done on time?

Bus

ines

s C

ontin

uity

Can it be done without downtime?

Skills

Do we have the required skills?

Operational

How well will it work?

Automation is key for success


What can OLM do for you ?


- for migrations between heterogeneous OS and HW platforms -  reducing significantly migration risks, complexity and

downtime

OLM has been designed ..

Solaris

HP-UX PA-RISC

Itanium

SPARC

x86

Power7


- ‘no downtime’ cross platform migrations -  While performing simultaneously an Oracle release upgrade -  Supporting business critical production environments -  Pre-requisite: source and destination database must be

-  on Oracle EE -  on release 10g or 11g


Solaris

HP-UX PA-RISC

Itanium

SPARC

x86

Power7


- to accelerate Oracle release upgrades -  between homogeneous or heterogeneous platforms -  up to 50% downtime reduction for 9i to 10g/11g upgrades -  Zero downtime for 10g to 11g upgrades



Is OLM a product or a service ?


What is OLM ?

SW Toolkit

Services

OLM

You OLM is services offer provided by

the local Bull affiliate


- Minimal production impact -  Minimal interruption of service

-  Minimal overhead on the production

database

-  Ensure application compatibility

-  No loss of data

-  Guarantee the migration success

OLM design point

Database Migration in Heterogeneous Environments


Migration tool market

Care to buy licenses for a migration ?


Oracle Database Migration Tools

Database Migration Tools on the market

-  Golden Gate -  Data integration solution: Replication across

heterogeneous system

-  Quest Shareplex for Oracle -  Oracle replication tool including migration and upgrade

-  EMS Data Pump for Oracle

-  Convert popular database to Oracle

-  XenoBridge -  heterogeneous migration: databases and platforms

Tools under licenses


Oracle standard tools


Oracle Database Migration Standard Methods

Technology

Source database Release

Endian Conversion

Source/target Platform

Additionnal Operation

Export/Import From Oracle 9i Yes Can be different

Rman Duplicate From Oracle 9i No Must be the same

Instantiate a 9i Database.

Need an upgrade to 10g/11g version

DBCA clone From Oracle 9i No Must be the same

Data Pump From Oracle 10g Yes Can be different

XTTS Transportable Tablespace +

Rman Convert

From Oracle 10g Yes Can be different Migration at Tablespace level.


OLM added vaule


- Based on standard Oracle migration methods: Export/Import in 9i or DataPump in 10g/11g

- Set of shell, PL/SQL and SQL scripts - Provide a migration methodology to migrate a set of

schemas - Better performances using server and Oracle parallelism - Validation of the migration - Migration scenarios with or without database downtime

OLM automation toolkit is based on standard tools

OLM is independent from Oracle release and operating system on source and target platforms


- Validation and verification -  Controlled by a single tool which integrates various standard tools -  Prerequisites verification and migration validation / export consistent data

- Migrates only necessary application schemas -  Avoid full database migration warnings/errors and complex report -  Take into account dependences inter schemas (role , grant ..) -  Migrate all dependents PUBLIC objects (roles, database links, directories, synonyms) -  Solve Oracle exp/imp or datapump bugs (dblinks 10g, jobs owner 11g …)

- Automatic migration process -  Sequence basic operations and generate report of each step (Extract, Copy, Create) -  Produce scripts to recreate schemas on target database (tablespaces, users, objects,

data)

OLM – added value over standard tools


- Resume Migration capability on process error -  Avoid restart from 1st step migration process when an error occurs -  Able to resume from any basic step (exp metadata, a schema, scripts creation) -  Speed up migration (long lasting migration schema)

- Parallelism configuration -  Better performance using server and database parallelism -  Configure parallelism (build sets of tables with exp/imp)

- Migration without database downtime -  Step 1: Migration while production running (using Consistent Export) -  Step 2: Synchronization using Oracle Streams while production running -  OLM scripts to configure, initiate and replicate updates at schema level with Oracle

Streams -  Minimum overhead and impact on activity

OLM – added value over standard tools


OLM : Migration Methods

Database Source Version 9i

Database Source Version 10g/11g

Export/import

Database Link

Export/import +

Database Link

Datapump

Datapump +

Oracle Streams Without downtime

Mode

Downtime Mode

OLM is based on Oracle standard Methods

OLM requires same prerequisites as Oracle Tools

X


OLM – zero downtime migration pricipals

Oracle 9i/10g/11g

Oracle 10g/11g

HP / SUN Bull Escala

Step 2: Synchronization

Step 1: Migration

Step 0: pre-building of the target DB


OLM – how it works


Oracle database - Migration Lifecycle

Pre-migration

–  audit of databases and servers –  identification of critical success factors –  audit report with migration strategy

Post-migration Migration Pre-sales

–  schema and data migration using OLM –  synchronization between source and target systems

–  validation of the new environment –  additional services on demand (perf. tuning…)

–  starting point to introduce Escala servers and/or Bull Storeway storage

OLM, cornerstone of a migration project


OLM – Methodology

Step 1 Audit

DB + Server

Step 2 Audit needs +

constraints

è  DB characteristics è  Server activity

(CPUs, memory storage ..)

è  Network throughput è  Estimate migration

process duration

è  Evolutions required è  DB activity profile è  Critical DB level è  DB downtime

allowed

è  Define prerequisites on source (OS, CPUs, space …)

è  Define prerequisites on target (init parameters )

è  Recommendations and limits (Undo,temp TBS, data types …)

è  Define migration scenario using OLM: mode and method

Step 3 Audit Report

Phase 1 Audit


OLM Audit

-  Source Server -  SUNFIRE V890 8 CPUs (ULTRA SPARC IV 1.4 Ghz)

-  Rperf rating: 31,5 rperf, 3,9 rperf/CPU

-  Target Server -  PL1660 1 CPU (dual-core Power 6 - 3,5 Ghz)

-  Rperf rating: 16 rperf

-  Network throughput: 1 Gbit/s -  Database volume: 100 GB

Migration Time: 3 hours

CPU Impact on Source: 75% of 1 CPU

CPU Impact on Target: 10% of 1 CPU


OLM – Methodology

Phase 2 Migration

Migrate

Step 1 Installation

Step 2 Extract

schemas

Step 3 Copy dumps and scripts

Step 4 Create

schemas

Step 5 Validation

è  Installation OLM toolkit

è  Configure migration mode and method

è  Define list of schemas

è  Extract metadata è  Extract data è  Generate scripts to

recreate tablespaces, users, roles, dblinks …

è  Copy dump files using secure copy (scp, sftp ..)

è  Copy scripts

è  Create tablespaces, users, roles …

è  Import metadata è  Import data

è  Migration logs listing operations, warnings and errors

è  Schema comparison between source and target


OLM – Methodology

Phase 3 Synchronization

Propagate

Step 1 Configuration

Step 2 Synchronization

Step 3 End

Synchronizaton

è  Configure Capture, Propagation on source DB

è  Configure Apply on target DB

è  Start Apply è  Start Capture è  Monitoring

synchronization

è  Stop production on source DB è  Validate and stop

synchronization è  Recreate and initiate sequence

objects

Capture Apply


OLM – Methodology

Phase 4 Application Testing

Step 1 Capture

Workload Step 2

Init Flashback Step 3 Replay

è  Capture a workload on source with Oracle Real Application Testing (RAT)

è  Initiate Flashback database on target DB

è  Replay workload on target DB

Capture Workload

Replay Workload

Step 4 Restore from

flashback

è  Restore database from Flashback


OLM – After migration

-  Validation applications on new database -  Rehearsal applications using Oracle application testing (RAT)

and Flashback database facilities

-  Tuning the new database -  Tuning according to new version and database activity

-  Switchover production to new database -  Database downtime -  Configure network to introduce or replace server in the

infrastructure (DNS) -  Redirect applications to new database (connection string update) -  Start production on new database

After Migration


Demo environment in Grenoble

-  Source database 10g on SUN Solaris -  Migrate 2 schemas of 3,7 GB

-  Storage: File system

-  Target Database11g on Escala -  Storage: Oracle Automatic Storage Management (ASM)

-  OLM migration mode -  Migration without downtime database

-  Using Oracle Datapump Export/import and synchronization with Oracle Streams

Migration Demonstration using OLM

Migration Phase

Audit Phase -  Source DB and server Audit

-  OS check and DB report

-  Target DB and server Audit -  OS check and DB report

-  Migration scenario definition


Customer case: Mid-size North Europe hospital

-  Source database 9i single instance on Solaris -  Database volume: 200GB

-  File system storage on EMC array

-  Target Database10g RAC on AIX -  2-node RAC 10g database

-  ASM storage on Netapp array

-  OLM migration mode -  Migration with downtime database -  Using parallel export/import set of tables

-  Using DBlink copy for large tables

-  Migration to test and production environments

Oracle Database Migration for an Hospital infrastructure

Using OLM Migration Scenario

Service day Estimation -  Database and server Audit: 4 days -  Migration with OLM: 8 days (Exclude RAC installation and RAC DB creation)

OLM Migration


OLM pricing


OLM - costs

Audit: 5000 Euro

Tagessatz: 1200 Euro


- End to end migration solution -  Includes audit and validation phases

-  Ensures data integrity and application compatibility

- No license costs

- Ensures best performance -  Accelerates migrations for up to 50% over standard methods

-  Optimizes resources on source and destination

-  Ensures minimum response times impact on production server

- Minimum interruption of service -  Customized migration scenarios to best fit individual requirements

-  No downtime option for migrating business critical DBs -  Accelerates migration with downtime through optimized parallelism

Conclusion

OLM for a flexible and safe data migration


OLM press add


OLM - costs

migrating oracle databases gert prieber

Documents