1. This is the Oracle OOW template
This is the Oracle OOW template. You, Ikeda-san, will use your Fujitsu template for your part. And we could decide later if it's easier to copy my stuff into your template. That's fully up to you.
TOPIC as ANNOUNCED:
Does Upgrade = Downtime? Minimal Downtime Strategies for Planned Maintenance
This session will examine options and methods available for performing database
upgrades in the time window that fits your business needs. You will learn about
upgrade techniques ranging from traditional command line upgrades to
Transportable Tablespaces, Oracle Data Guard, Oracle Streams, and Oracle Golden
Gate. A comparison of upgrade methods by Fujitsu Hokuriku Systems Ltd. will
provide hard data to help you make the right choices for your upgrade scenario.
Does Upgrade = Downtime? Minimal Downtime Strategies for Planned Maintenance
Mike Dietrich – ORACLE Corporation – Upgrade Development Group
Takuya Abe – ORACLE Japan – Sales Consulting
Takashi Ikeda – Fujitsu Hokuriku Systems Ltd. Japan

2. Introduction Who we are??? COMMENT:
We should do a brief introduction who we are. It would be great if we 3 do a picture together in San Francisco and put it in the presentation.

3. Introduction Mike Dietrich: http://blogs.oracle.com/UPGRADE COMMENT:
We should do a brief introduction who we are. It would be great if we 3 do a picture together in San Francisco and put it in the presentation.

4. <Insert Picture Here>
Agenda
<Insert Picture Here>
Downtime?
Different Techniques - Overview
Different Techniques – The Details
Practical comparison by Fujitsu Hokuriku

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 to
Patch set upgrades
Example: Patch set upgrade from to
Patches which modify the dictionary
Why do you encounter database downtime when you are doing a database upgrade?
Reason for this is: We have to put the database into upgrade mode. This means we switch a lot of things in the background to silence so it won't be any interference with the upgrade itselves. During an upgrade just the data dictionary gets upgraded. If we move data from machine A to machine B we call this migration. During an upgrade the database is protected against changes apart internal changes in the dictionary. And this usually means "Downtime" for a system. It will apply to Database release upgrades as well as to patch set upgrades and dictionary changing patches (which are issued very seldomly). 5

6. The Goal Goal: The 3 Magic Upgrade Questions:
Reduce the downtime according to your requirements and business needs
The 3 Magic Upgrade Questions:
Are you changing operating systems?
Will you be moving to new hardware?
How much downtime can you experience?
The goal of most customers is now to reduce the downtime according to their business needs and requirements.
In our opinion there are three magic upgrade questions to answer:
Will you stay or change the operating system?
Will you get new hardware to move the database to?
How much downtime will you get for the entire upgrade/migration? 6

7. <Insert Picture Here>
Agenda
<Insert Picture Here>
Downtime?
Different Techniques - Overview
Different Techniques – The Details
Practical comparison by Fujitsu Hokuriku 7

8. Change to a new OS and new HW Overview
slow Possible upgrade/migration downtime fast
(strongly dependent on data volume)
Oracle 11.1
Oracle 10.2
Transportable DB
Oracle 10.1
expdp/impdp
x Transportable TS
Oracle 9.2
Streams
Works since Oracle Version
Oracle 8i
Golden Gate
Oracle8
Oracle7
COPY CTAS SQL*Loader
Oracle6
exp/imp
Oracle5 8

9. Keep the OS – Upgrade and change HW Overview
slow Possible upgrade/migration time fast
(may or may not depend on data volume)
Transient Stby
Oracle 11.1
Oracle 10.2
Transportable DB
Logical Stby
Oracle 10.1
expdp/impdp
TTS
Oracle 9.2
Streams
Works since Oracle Version
Oracle 8i
Golden Gate
Oracle8
Oracle7
COPY CTAS SQL*Loader
Upgrade Command Line
Oracle6
exp/imp
Oracle5 9

10. Keep the HW – just upgrade the database Overview
slow Possible upgrade/migration time fast
(may or may not depend on data volume)
Oracle 11.1
Oracle 10.2
Oracle 10.1
expdp/impdp
TTS
Oracle 9.2
Streams
Works since Oracle Version
Oracle 8i
Golden Gate
Oracle8
Oracle7
COPY CTAS SQL*Loader
Upgrade DBUA or Command Line
Oracle6
exp/imp
Oracle5 10

11. <Insert Picture Here>
Agenda
<Insert Picture Here>
Downtime?
Different Techniques - Overview
Different Techniques – The Details
Practical comparison by Fujitsu Hokuriku 11

12. "Regular" Database Upgrade
Upgrade duration is mainly dependent on the number of installed components
Typical upgrade duration: minutes
DBUA
Command Line
Same HW, same OS
Same HW, different OS
Different HW, same OS
Different HW, different OS
Customers always ask about this, but it is very difficult to estimate. Upgrade duration can be affected by hardware characteristics (CPU power, IO, available RAM). Beyond that, the most important factor is the number of objects in the database. An EBS database, for example, will have more than 30,000 objects.
Synonyms get touched to add new entries to DEPDENDENCY$ when you upgrade from Oracle 9i to a higher release. If a customer has more than ~100k synonyms then this can add some additional time to the upgrade downtime. Synonyms will be "touched" and recompiled during the upgrade script process - not during recompilation.
Having dictionary statistics up-to-date for the optimizer it very important if you want to minimize the
Time it takes to upgrade. If there are no dictionary statistics or they are stale, they will get collected
During the upgrade.
Datafile headers get touched, and the format of redo logs can change during upgrade if COMATIBLE will be increased. Thus the low rate of dependency there. x x x
© 2010 Oracle Corporation 12

13. 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
Same HW, different OS
Different HW, same OS
Different HW, different OS
Customers always ask about this, but it is very difficult to estimate. Upgrade duration can be affected by hardware characteristics (CPU power, IO, available RAM). Beyond that, the most important factor is the number of objects in the database. An EBS database, for example, will have more than 30,000 objects.
Synonyms get touched to add new entries to DEPDENDENCY$ when you upgrade from Oracle 9i to a higher release. If a customer has more than ~100k synonyms then this can add some additional time to the upgrade downtime. Synonyms will be "touched" and recompiled during the upgrade script process - not during recompilation.
Having dictionary statistics up-to-date for the optimizer it very important if you want to minimize the
Time it takes to upgrade. If there are no dictionary statistics or they are stale, they will get collected
During the upgrade.
Datafile headers get touched, and the format of redo logs can change during upgrade if COMATIBLE will be increased. Thus the low rate of dependency there. x x x x x x x x
© 2010 Oracle Corporation 13

14. 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
Customers always ask about this, but it is very difficult to estimate. Upgrade duration can be affected by hardware characteristics (CPU power, IO, available RAM). Beyond that, the most important factor is the number of objects in the database. An EBS database, for example, will have more than 30,000 objects.
Synonyms get touched to add new entries to DEPDENDENCY$ when you upgrade from Oracle 9i to a higher release. If a customer has more than ~100k synonyms then this can add some additional time to the upgrade downtime. Synonyms will be "touched" and recompiled during the upgrade script process - not during recompilation.
Having dictionary statistics up-to-date for the optimizer it very important if you want to minimize the
Time it takes to upgrade. If there are no dictionary statistics or they are stale, they will get collected
During the upgrade.
Datafile headers get touched, and the format of redo logs can change during upgrade if COMATIBLE will be increased. Thus the low rate of dependency there.
CTAS COPY
SQL Loader
Same HW, same OS
Same HW, different OS
Different HW, same OS
Different HW, different OS x x x x x x x x
© 2010 Oracle Corporation 14

15. 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 can be very fast, but there are times when caution is needed.
NOT AN OFFICIAL REFERENCE FOR THIS, BUT CAN BE USED (WITHOUT CUSTOMER NAME) AS EXAMPLE:
Amadeus (large European customer, largest airline and hotel booking system in the world) uses TTS as an upgrade mechanism. They had issues with patch upgrades, because they can switch their application to READ ONLY mode. In this mode the travel agent can see open seats but not book them. Therefore Amadeus was trying to transport tablespaces from to They were able to decrease downtime from 1.5 hours to 15 minutes.
Note:
Description
ALTER TABLESPACE READ ONLY waits for all active transactions to complete including transactions which are not touching the tablespace to be made read only. This enhancement alters the behaviour such that ALTER TABLESPACE READ ONLY will only wait on relevant transactions.
The full backup is needed because the tablespaces are now in a new database – backups from the previous database cannot be restored to the new one.
TTS
Same HW, same OS
Same HW, different OS
Different HW, same OS
Different HW, different OS x
≥10g x
≥10g
© 2010 Oracle Corporation 15

16. 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, same OS
Different HW, different OS, same Endianness
Different HW, different OS, different Endianness x
TTS can be very fast, but there are times when caution is needed.
NOT AN OFFICIAL REFERENCE FOR THIS, BUT CAN BE USED (WITHOUT CUSTOMER NAME) AS EXAMPLE:
Amadeus (large European customer, largest airline and hotel booking system in the world) uses TTS as an upgrade mechanism. They had issues with patch upgrades, because they can switch their application to READ ONLY mode. In this mode the travel agent can see open seats but not book them. Therefore Amadeus was trying to transport tablespaces from to They were able to decrease downtime from 1.5 hours to 15 minutes.
Note:
Description
ALTER TABLESPACE READ ONLY waits for all active transactions to complete including transactions which are not touching the tablespace to be made read only. This enhancement alters the behaviour such that ALTER TABLESPACE READ ONLY will only wait on relevant transactions.
The full backup is needed because the tablespaces are now in a new database – backups from the previous database cannot be restored to the new one. x x x
© 2010 Oracle Corporation 16

17. Oracle Streams x x x x 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
TTS can be very fast, but there are times when caution is needed.
NOT AN OFFICIAL REFERENCE FOR THIS, BUT CAN BE USED (WITHOUT CUSTOMER NAME) AS EXAMPLE:
Amadeus (large European customer, largest airline and hotel booking system in the world) uses TTS as an upgrade mechanism. They had issues with patch upgrades, because they can switch their application to READ ONLY mode. In this mode the travel agent can see open seats but not book them. Therefore Amadeus was trying to transport tablespaces from to They were able to decrease downtime from 1.5 hours to 15 minutes.
Note:
Description
ALTER TABLESPACE READ ONLY waits for all active transactions to complete including transactions which are not touching the tablespace to be made read only. This enhancement alters the behaviour such that ALTER TABLESPACE READ ONLY will only wait on relevant transactions.
The full backup is needed because the tablespaces are now in a new database – backups from the previous database cannot be restored to the new one.
Streams
Same HW, same OS
Same HW, different OS
Different HW, same OS
Different HW, different OS x x x x
© 2010 Oracle Corporation 17

18. Oracle Golden Gate x x x x 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
Same HW, different OS
Different HW, same OS
Different HW, different OS
TTS can be very fast, but there are times when caution is needed.
NOT AN OFFICIAL REFERENCE FOR THIS, BUT CAN BE USED (WITHOUT CUSTOMER NAME) AS EXAMPLE:
Amadeus (large European customer, largest airline and hotel booking system in the world) uses TTS as an upgrade mechanism. They had issues with patch upgrades, because they can switch their application to READ ONLY mode. In this mode the travel agent can see open seats but not book them. Therefore Amadeus was trying to transport tablespaces from to They were able to decrease downtime from 1.5 hours to 15 minutes.
Note:
Description
ALTER TABLESPACE READ ONLY waits for all active transactions to complete including transactions which are not touching the tablespace to be made read only. This enhancement alters the behaviour such that ALTER TABLESPACE READ ONLY will only wait on relevant transactions.
The full backup is needed because the tablespaces are now in a new database – backups from the previous database cannot be restored to the new one. x x x x
© 2010 Oracle Corporation 18

19. Logical Standby Database – SQL Apply
SQL Apply Rolling Upgrade works since Oracle
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
Same HW, different OS
Different HW, same OS
Different HW, different OS
TTS can be very fast, but there are times when caution is needed.
NOT AN OFFICIAL REFERENCE FOR THIS, BUT CAN BE USED (WITHOUT CUSTOMER NAME) AS EXAMPLE:
Amadeus (large European customer, largest airline and hotel booking system in the world) uses TTS as an upgrade mechanism. They had issues with patch upgrades, because they can switch their application to READ ONLY mode. In this mode the travel agent can see open seats but not book them. Therefore Amadeus was trying to transport tablespaces from to They were able to decrease downtime from 1.5 hours to 15 minutes.
Note:
Description
ALTER TABLESPACE READ ONLY waits for all active transactions to complete including transactions which are not touching the tablespace to be made read only. This enhancement alters the behaviour such that ALTER TABLESPACE READ ONLY will only wait on relevant transactions.
The full backup is needed because the tablespaces are now in a new database – backups from the previous database cannot be restored to the new one. x
© 2010 Oracle Corporation 19

20. 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
TTS can be very fast, but there are times when caution is needed.
NOT AN OFFICIAL REFERENCE FOR THIS, BUT CAN BE USED (WITHOUT CUSTOMER NAME) AS EXAMPLE:
Amadeus (large European customer, largest airline and hotel booking system in the world) uses TTS as an upgrade mechanism. They had issues with patch upgrades, because they can switch their application to READ ONLY mode. In this mode the travel agent can see open seats but not book them. Therefore Amadeus was trying to transport tablespaces from to They were able to decrease downtime from 1.5 hours to 15 minutes.
Note:
Description
ALTER TABLESPACE READ ONLY waits for all active transactions to complete including transactions which are not touching the tablespace to be made read only. This enhancement alters the behaviour such that ALTER TABLESPACE READ ONLY will only wait on relevant transactions.
The full backup is needed because the tablespaces are now in a new database – backups from the previous database cannot be restored to the new one.
Transient Standby
Same HW, same OS
Same HW, different OS
Different HW, same OS
Different HW, different OS x
© 2010 Oracle Corporation 20

21. Section Divider

22. Introduction
Takuya Abe Sales Consulting Oracle 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. Best Practices, Innovative Ideas, from Japan
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
Fujitsu SPARC Enterprise: Migrating from Oracle9i Database to Oracle Database 11g
Oracle Database ILM Solution based on Fujitsu ETERNUS DX/SPARC Enterprise - Lower storage costs and power consumption for long-term data storage -
Performance verification of Oracle RAC /Oracle BIEE on Fujitsu Blade Server - Validating Scalability by Adding Nodes -
Verification of Oracle Database 11g for Data Warehousing Using Fujitsu SPARC Enterprise - Performance Improvement Based on Data Segment Compression and ASM Utilization -
Effective resource utilization by In-Memory Parallel Execution in Oracle Real Application Clusters 11g Release 2
Oracle Database 11g Release 2 Improving Batch Processing Speed using In-Memory Parallel Execution on Oracle Real Application Clusters
Performance improvement of the entire Data Warehouse system on NEC Express5800/Scalable HA Server by using Oracle Database 11g Release 2 In-Memory Parallel Query
Active Data Guard 11g, RMAN Network Duplicate, Snapshot Standby, Apply Performance and Fast-Start Failover w/ Hitachi Ltd.
Best Practices for Oracle Automatic Storage Management (ASM) on Hitachi Dynamic Provisioning(HDP)
Data Guard Redo Transport Compression and Proper Network Configuration w/ Hitachi Ltd
Data Guard SQL Apply on IBM Power Systems Performance Validation