Does Upgrade = Downtime? Minimal Downtime Strategies for Planned Maintenance Mike Dietrich – ORACLE Corporation – Upgrade Development Group Takuya Abe

<Insert Picture Here>

Does Upgrade = Downtime?Minimal Downtime Strategies for Planned Maintenance

Mike Dietrich – ORACLE Corporation – Upgrade Development GroupTakuya Abe – ORACLE Japan – Sales ConsultingTakashi Ikeda – Fujitsu Hokuriku Systems Ltd. Japan

2

Introduction• Who we are???

3

Introduction• Mike Dietrich: http://blogs.oracle.com/UPGRADE

4


Agenda

Downtime?

Different Techniques – The Details

Practical comparison by Fujitsu Hokuriku

Different Techniques - Overview

5

Why Downtime?

• Why do we encounter downtime during a database upgrade?• Database is in "UPGRADE" mode• The data dictionary will be upgraded• The database is protected against changes apart from upgrade• ►This usually means downtime• It applies to:• Database release upgrades

• Example: Upgrade from 10.2.0.3 to 11.2.0.2

• Patch set upgrades• Example: Patch set upgrade from 11.2.0.1 to 11.2.0.2

• Patches which modify the dictionary

6

The Goal

• Goal:• Reduce the downtime according to your requirements

and business needs

• The 3 Magic Upgrade Questions:1)Are you changing operating systems?

2)Will you be moving to new hardware?

3)How much downtime can you experience?

7


Agenda

Downtime?




8

Change to a new OS and new HWOverview

exp/impexp/imp

COPYCTAS

SQL*Loader

COPYCTAS

SQL*Loader

x Transportable TSx Transportable TS

Transportable DBTransportable DB

StreamsStreams

Golden GateGolden Gate

expdp/impdpexpdp/impdp

Wo

rks

sin

ce

Ora

cle

Ve

rsio

n

slow Possible upgrade/migration downtime fast(strongly dependent on data volume)

Oracle8

Oracle 9.2

Oracle 10.1

Oracle 10.2

Oracle 11.1

Oracle 8i

Oracle7

Oracle6

Oracle5

9

Keep the OS – Upgrade and change HWOverview

exp/impexp/imp

COPYCTAS

SQL*Loader

COPYCTAS

SQL*Loader

TTSTTS

Transportable DBTransportable DB

StreamsStreams


Wo

rks

sin

ce

Ora

cle

Ve

rsio

n

slow Possible upgrade/migration time fast(may or may not depend on data volume)

Oracle8

Oracle 9.2

Oracle 10.1

Oracle 10.2

Oracle 11.1

Oracle 8i

Oracle7

Oracle6

Oracle5

Logical StbyLogical Stby

Transient StbyTransient Stby

UpgradeCommand Line

UpgradeCommand Line


10

Keep the HW – just upgrade the databaseOverview

exp/impexp/imp

COPYCTAS

SQL*Loader

COPYCTAS

SQL*Loader

TTSTTS

StreamsStreams


Wo

rks

sin

ce

Ora

cle

Ve

rsio

n

slow Possible upgrade/migration time fast(may or may not depend on data volume)

Oracle8

Oracle 9.2

Oracle 10.1

Oracle 10.2

Oracle 11.1

Oracle 8i

Oracle7

Oracle6

Oracle5

UpgradeDBUA or Command Line

UpgradeDBUA or Command Line


11


Agenda

Downtime?




12© 2010 Oracle Corporation 12

"Regular" Database Upgrade

• Upgrade duration is mainly dependent on the number of installed components• Typical upgrade duration: 15-90 minutes

DBUA Command Line

Same HW, same OS

Same HW, different OS

Different HW, same OS

Different HW, different OS


Export/Import and Data Pump

• Upgrade duration is mainly dependent on data volume• exp/imp will work between Oracle5 and Oracle 11.2• expdp/impdp will work starting from Oracle 10.1• Faster and more powerful than "old" exp/imp• NETWORK_LINK parameter could be very beneficial

exp/imp expdp/impdp

Same HW, same OS





CTAS, COPY command and SQL*Loader

• Upgrade duration is mainly dependent on data volume• Create-Table-As-Select and COPY work on database links

with restrictions• SQL*Loader requires unload of data

• Both techniques work since Oracle 7 or earlier – across versions

CTASCOPY

SQLLoader

Same HW, same OS





Transportable Tablespaces

• TTS works since Oracle 8i• Cross platform and cross Endianness since Oracle 10g• Unplug data tablespaces and plug them into a new db

• But objects in SYSTEM and SYSAUX have to be transported as well

• Complexity could be a constraint

TTS

Same HW, same OS




≥10g≥10g

≥10g≥10g


Transportable Database

• TDB works since Oracle 10.2• Cross platform, but NOT cross Endianness• RMAN automates the platform conversion

• Database must be switched into READ ONLY mode

TTDB

Same HW, same OS

Same HW, different OS, same Endianness

Same HW, different OS, different Endianness


Different HW, different OS, same Endianness

Different HW, different OS, different Endianness


Oracle Streams

• Oracle Streams works since Oracle 9.2• Setup a copy of the database, upgrade it and replicate

everything to the copy• Cross platform and cross Endianness• Downstream Capture as fallback

• But complex to setup and may have performance limitations

Streams

Same HW, same OS





Oracle Golden Gate

• Oracle Golden Gate works since Oracle 8i• Similar concept to Oracle Streams

• Logmining happens outside the database• Faster and easier to setup and more datatypes supported

Golden Gate

Same HW, same OS





Logical Standby Database – SQL Apply

• SQL Apply Rolling Upgrade works since Oracle 10.1.0.3• Logical Standby database is upgraded first• Switchover exchanges roles between primary and standby• Then the former production is upgraded

• Downtime reachable: less than 1 minute

SQL Apply

Same HW, same OS





Transient Logical Standby Database

• Recommended beginning with Oracle 11g• Start with Physical Standby• Convert to Logical Standby, upgrade using SQL Apply• Use Flashback Database to return to Physical Standby

configuration• Downtime reachable: less than 1 minute

Transient Standby

Same HW, same OS




21

Section Divider

22

Introduction

• Takuya AbeSales ConsultingOracle Japan

23

Upgrade conditions in Japan

• There are many databases running old versions in Japan• Why?

• Basically, they tend to improve their existing databases and not upgrading them• Kaizen

• Each divisions in a company has their own systems with their own policies• It’s not easy to standardize or consolidate the systems

• Afraid of the impact on applications by upgrading database

• It’s difficult to convince customers to upgrade databases

24

Working with Upgrade Development

• Upgrade Development team members came to Japan last year to promote upgrading databases• Provide an upgrade workshop • Several meetings with Japanese partner companies

• Good and close relationship between U.S. and Japan• Keeping contact and discuss upgrade projects in Japan• Task Force Team for upgrading large-scale projects

25

Collaboration with Partners in japan

• Oracle Japan cooperates with many partner companies• Fujitsu, NEC, Hitachi, HP,etc• NS Solution, CTC, etc

• From our partners perspective, there was not enough information available about database upgrades• We had tested and created documents about database

upgrades with Fujitsu at the Technology Verification Center in Oracle Japan’s office

26

Oracle GRID Center

Best Practices, Innovative Ideas, from Japan

27

Performs Key Technical Activities at Oracle Japan

Utilize Various Hardware

Servers, Storages and Network

Switches provided by Strategic

Partners

Collaborative Verification Testing

Engineers from Partners, Oracle

Japan and Oracle Development

Publish Outputs

28

White Papers• Oracle Database 11g Release 2 Improving OLTP System Performance Using Database Smart Flash Cache with Fujitsu SPARC Enterprise

http://www.fujitsu.com/downloads/STRSYS/system/fj-gc-dbsfc.pdf• Fujitsu SPARC Enterprise: Migrating from Oracle9i Database to Oracle Database 11g

http://www.oracle.com/technetwork/database/enterprise-edition/fj-gc-spe-migrate-1-132029.pdf• Oracle Database ILM Solution based on Fujitsu ETERNUS DX/SPARC Enterprise - Lower storage costs and power consumption for long-term

data storage -http://www.fujitsu.com/downloads/STRSYS/system/fj-gc-eternus-ilm.pdf

• Performance verification of Oracle RAC /Oracle BIEE on Fujitsu Blade Server - Validating Scalability by Adding Nodes -http://www.oracle.com/technology/global/jp/tech/grid/doc/GRIDCenter-Fujitsu-BIEE_v1.0_English.pdf

• Verification of Oracle Database 11g for Data Warehousing Using Fujitsu SPARC Enterprise - Performance Improvement Based on Data Segment Compression and ASM Utilization -http://www.fujitsu.com/downloads/SPARCE/whitepapers/fj-gc-spe-dwh-10-en.pdf

• Effective resource utilization by In-Memory Parallel Execution in Oracle Real Application Clusters 11g Release 2 http://www.oracle.com/technetwork/middleware/bi-foundation/twp-in-mem-pq-gridcenter-ns-solutio-133291.pdf

• Oracle Database 11g Release 2 Improving Batch Processing Speed using In-Memory Parallel Execution on Oracle Real Application Clustershttp://www.oracle.com/technetwork/database/features/bi-datawarehousing/twp-in-mem-pq-batch-gridcenter-ns-s-134459.pdf

• Performance improvement of the entire Data Warehouse system on NEC Express5800/Scalable HA Server by using Oracle Database 11g Release 2 In-Memory Parallel Queryhttp://www.oracle.com/technetwork/database/features/performance/twp-in-mem-pq-gridcenter-nec-eng-11-130343.pdf

• Active Data Guard 11g, RMAN Network Duplicate, Snapshot Standby, Apply Performance and Fast-Start Failover w/ Hitachi Ltd.http://www.hitachi.co.jp/products/it/storage-solutions/techsupport/whitepaper/pdf/11gdg_wp_v1_e.pdf

• Best Practices for Oracle Automatic Storage Management (ASM) on Hitachi Dynamic Provisioning(HDP)http://www.hitachi.co.jp/products/it/storage-solutions/techsupport/whitepaper/pdf/hdp_bestpractice_wp_e.pdf

• Data Guard Redo Transport Compression and Proper Network Configuration w/ Hitachi Ltdhttp://www.hitachi.co.jp/Prod/comp/soft1/oracle/pdf/OBtecinfo-08-008.pdf

• Data Guard SQL Apply on IBM Power Systems Performance Validationhttp://www.oracle.co.jp/solutions/grid_center/ibm/pdf/GRIDCenter_SQLApply_PowerSystems_en.pdf

29

30

Documents

Does Upgrade = Downtime? Minimal Downtime Strategies for Planned Maintenance Mike Dietrich – ORACLE Corporation – Upgrade Development Group Takuya Abe