19819599151532804185/full Transport 12c

Minimal Downtime Migration
with Full Transportable Export/Import
Mike Dietrich
Master Product Manager
Database Upgrade
Oracle Corporation
Updated: Oct 30, 2015

Copyright 2015 Oracle and/or its affiliates. All rights reserved. | Minimal Downtime Migration with Full Transportable
$> whoami
6 years
RDBMS Core & Mission Critical Support
5.5 years
Technology Presales for DataGuard, Upgrades
Mike Dietrich
Master Product Manager
>7 years
ST Upgrade Development Team
Database Upgrades & Migrations
MikeDietrichDE
http://blogs.oracle.com/UPGRADE
50%
50%
Reference
Projects
+ x%
Workshops
Worldwide
Development
Work
Copyright 2015 Oracle and/or its affiliates. All rights reserved. |
Supported Versions
2025
2024
2023
2022
2021
2020
2019
2018
2017
2016
2015
(GA: Sep 2009)
2014
Oracle 11.2
2013
(GA: Aug 2007)
2012
Jan 2012
Jul 2010
Oracle 11.1
2011
(GA: Jul 2005)
Jan 2009
2010
Oracle 10.2
2009
(GA: Jan 2004)
2008
2007
Oracle 10.1
today
Jul 2013
Aug 2012
Aug 2015
Jan 2015
May 2017
Oracle 12.1
Jun 2018
(GA: Jun 2013)
Dec 2020
Jun 2021
Oracle 12.2
(GA: xxx 2016)
Premier Support
Waived Extended Support
Paid Extended Support
Sustaining Support
Database Upgrade Blog
http://blogs.oracle.com/UPGRADE
"The migration of all 16 German Electronic

Income Tax databases to Oracle Database 12c
in less than 10 months went smooth and fine.
We are very satisfied with the performance
and the robustness of Oracle Database 12c."
Anja Albrecht, Rechenzentrum der Finanzverwaltung NRW
Proper Preparation
The Road to Success
Migration
Very large database
Cross platform with limited
amount of downtime
Options
Migrate a large database
Cross platform, cross Endianness

With limited downtime
Realistic options
Data Pump
Transportable Tablespaces
Full Transportable Export/Import
Plus:
Oracle Golden Gate
Oracle Streams
RMAN Incremental Rolled Forward Backups
25%
of +Terabyte Migrations get

delayed or fail because of
insufficient network hardware,
setup or bandwidth
Network Bandwidth
Net Data
Volume
Theoretical
11 MB/sec
40 GB/hour
1 Gbit Ethernet
110 MB/sec
400 GB/hour
10 Gbit Ethernet
1100 MB/sec
4000 GB/hour
Infiniband IB 4xQDR
4000 MB/sec
14400 GB/hour
Interface
100 Mbit Ethernet
Real World
Transfer Transfer Throughput

Throughput
<30 GB/hour
<300 GB/hour
<3000 GB/hour
<11000 GB/hour
10
Concept Transportable Tablespaces

impdp
"'"sys/sys
as sysdba"'"
expdp
"'"sys/sys
as sysdba"'"
TRANSPORT_DATAFILES=
TRANSPORT_TABLESPACES=TS1,TS2
TTS feature available since Oracle 8i
Cross platform support since Oracle 10g
Self Contained?
Read Only
75TB
Read Write
75TB
11
Transportable Tablespaces Pros and Cons
Pro
Potentially very fast
Copying large files can be faster than

exporting & importing everything
No need to rebuild indexes
Cross platform since Oracle 10g

Decrease copy/convert time by using
RMAN Incremental Backups
Proven solutions for EBS and other
apps available
Con
SYSTEM/SYSAUX can't be transported

Complexity is your enemy
Too many objects to rebuild
Views, synonyms, sequences
Simple is better for fast TTS!!!
Too many objects in tablespaces

slow down meta expdp/impdp
(Sub)partitions, partitioned indexes
12
Concept Transportable Tablespaces xTTS
Cross platform support
V$TRANSPORTABLE_PLATFORM
LITTLE ENDIAN PLATFORMS

HP IA Open VMS
HP Open VMS
HP Tru64 UNIX
RMAN
Linux IA (32-bit)
Linux IA (64-bit)
Linux x86 64-bit
Microsoft Windows IA (64-bit)

Microsoft Windows x86 64-bit
Microsoft Windows IA (32-bit)
Solaris Operating System (x86)
Solaris Operating System (x86-64)
BIG ENDIAN PLATFORMS

HP-UX (64-bit)
HP-UX IA (64-bit)
CONVERT
FILE
COPY
DBMS_FILE_
TRANSFER
FILE
COPY
AIX-Based Systems (64-bit)

IBM zSeries Based Linux
IBM Power Based Linux
Solaris[tm] OE (32-bit)
Solaris[tm] OE (64-bit)
13
Concept Transportable Tablespaces xTTS
TTS cross platform
RMAN creates a file copy

Can be done on source or target system
Use the faster storage
Takes approximately the same amount of time as a backup and requires staging space
Multiple channels can be used
Example: RMAN> CONVERT TABLESPACE users,example
TO PLATFORM 'Linux IA (32-bit)'
FORMAT='/stage/transport_linux/%U';
DBMS_FILE_TRANSFER converts implicitly and does not require staging but is generally
slower
14
Upgrade/Migration: Transportable Tablespaces

Rebuild meta information
(views, synonyms, trigger, roles etc)
SOURCE Database 11.2.0.4
DESTINATION Database 12.1.0.2

VIEWS
VIEWS
Read Only
SCOTT
HUGO
SYSTEM
SYSAUX
UNDO
TEMP
CODE
SCOTT
PRIVS
HUGO
SYSTEM
SYSAUX
UNDO
TEMP
CODE
PRIVS
15
Possible options
Moving meta information
The brute force approach
Data Pump
expdp/impdp CONTENT=METADATA_ONLY
The smart approach
DBMS_METADATA
SELECT DBMS_METADATA.GET_DDL('SYNONYM', SYNONYM_NAME,

OWNER) FROM all_synonyms where owner='PUBLIC' and
table_owner not in ('SYS');
16
Transportable Tablespaces
Avoid physical file copies when possible
Use a physical standby

as your transporter
Mount from two sides
TTS
Tablespaces can be mounted

from two databases at the
same time as long as they
are set read-only
STANDBY
PHYS
TTS
STANDBY
PHYS
Take special care on:
Time zone versions must be equal prior to transport
Otherwise Data Pump will block the meta import
Be careful with starting values for sequences
17
The biggest pain points of TTS?
Copy and convert a large database

Rebuild all the meta information
18
TTS Pain Points
Size
Solution:
RMAN Incremental Backups
Complexity
PERL scripts in MOS Note:1389592.1 and in

MOS Note: 2005729.1
Source: 10.2.0.3 or newer
Target: 11.2.0.4 or newer
Solution:
Data Pump feature allows

One Command Migration
Source: 11.2.0.3 or newer
Target: 12.1.0.1 or newer
Can be combined
19
Pure Transportable Tablespace with Incremental Backups

impdp"'"sys/sys
"'"sys/sysasassysdba"'"
sysdba"'"
expdp
TRANSPORT_DATAFILES=
TRANSPORT_TABLESPACES=TS1,TS2
Convert and apply

backups
Downtime!!!

Read Write
VIEWS
VIEWS
Read Only
SCOTT
HUGO
SYSTEM
SYSAUX
UNDO
TEMP
CODE
PRIVS
Data Pump
SCOTT
HUGO
SYSTEM
SYSAUX
UNDO
TEMP
CODE
PRIVS
20
Full Transportable Export/Import with Copies
VIEWS
VIEWS
Read Only
SCOTT
HUGO
SYSTEM
SYSAUX
UNDO
TEMP
CODE
PRIVS
Data Pump
SCOTT
HUGO
SYSTEM
SYSAUX
UNDO
CODE
PRIVS
TEMP
21
Full Transportable Export/Import with Backups
Convert and apply

backups
VIEWS
VIEWS
Read Only
SCOTT
HUGO
SYSTEM
SYSAUX
UNDO
TEMP
CODE
PRIVS
Data Pump
SCOTT
HUGO
SYSTEM
SYSAUX
UNDO
TEMP
CODE
PRIVS
22
Let's do it
using RMAN Incremental Rolled Foward Backups
23
Overview - Phases
Phase 1 - Initial Setup phase
Phase 2 - Prepare phase
Phase 3 - Roll Forward phase
Phase 4 - Final Incremental Backup
Phase 5 - Transport Phase: Import all Metadata
Phase 6 - Validate the Transported Tablespaces
Phase 7 - Cleanup
24
Download the PERL scripts from MOS Note:1389592.1
Key scripts:
Extract them to: /home/oracle/xtt

25
Choose the best method
RMAN backup / convert
Faster
Requires staging space for CONVERT
xttdriver.pl -p and -c
DBMS_FILE_TRANSFER
Backup
Slower
Does not require staging space
CONVERT happens implicitly
xttdriver.pl -S and -G
Convert
Restore &
Convert
Staging
26
Create a destination database
For Full Transportable Export/Import:
SourceDB must be 11.2.0.3 or higher

DestDB must be 12.1.
COMPATIBLE equal or higher

Identical database character sets
Identical national characher sets
Identical time zone versions
Oracle Database
Release
Default
Time Zone
Version
10.2.0.3 11.1.0.7
DST V4
11.2.0.1
11.2.0.2 - 11.2.0.4
12.1.0.1, 12.1.0.2
Most recent time zone file:
DST V11
DST V14
DST V18
DST V24
27
Identify tablespaces to be transported
Configure:
xtt.properties
## Tablespaces to transport
## ========================
tablespaces=TS1,TS2
## Source database platform ID
## ===========================
platformid=13
## Source system file locations
## ============================
## Location where datafile copies are created
## during the "-p prepare" step.
dfcopydir=/oracle/DQ1/rman_stage
## backupformat
## -----------## Location where incremental backups are created.
backupformat=/oracle/DQ1/rman_stage
## Destination system file locations

## =================================
## Location where datafile copies are placed by the user
## when they are transferred manually from souce system.
stageondest=/oracle/DQ1/rman_stage
## storageondest
## ------------## Location where the converted datafile copies will be
## written during the "-c conversion of datafiles" step.
## This is the final location of the datafiles
## where they will be used by the destination database.
storageondest=/oracle/DQ1/sapdata50
## backupondest
## -----------## Location where converted incremental backups
## on the destination system will be written during
## the "-r roll forward datafiles" step.
backupondest=/oracle/DQ1/rman_stage_incr
28
Enable block change tracking in source database
ALTER DATABASE ENABLE BLOCK CHANGE TRACKING USING FILE '<name>' REUSE;
Copy all xtt-scripts to the destination host
Set TMPDIR=/home/oracle/xtt on both hosts

/home/oracle/xtt
/home/oracle/xtt
Copy xtt scripts including modified xtt.properties
29
Create data file copies on source
[oracle@source]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl p

Creates the following files used later:
xttplan.txt
rmanconvert.cmd
Staging
30
Transfer files to destination host
Not necessary if your staging location is available to the destination host (NFS etc)
xtt.properties: dfcopydir = stageondest
Staging
31
Copy rmanconvert.cmd to destination
Convert the data file copies and write them to storageondest
[oracle@dest]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl c
Copy
/home/oracle/xtt
rmanconvert.cmd
Staging
32
Create incremental backups on source
[oracle@source]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl -i

Creates the following files used later:
tsbkupmap.txt
incrbackups.txt [not necessary here due to NFS mount]
i
i
Staging
33
Transfer incremental backups to destination host
Not necessary if your staging location is available to the destination host (NFS etc)
xtt.properties: backupformat = stageondest
i
Staging
34
Copy xttplan.txt and tsbkupmap.txt to destination
Convert the inc backups and merge them into tablespace files on storageondest
[oracle@dest]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl r
xttplan.txt
Copy
/home/oracle/xtt
tsbkupmap.txt
iC
iC
Staging
iC
iC
35
Record FROM_SCN on source for next incremental backup
[oracle@source]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl -s

Writes it into xttplan.txt
SCN
xttplan.txt
Staging
36
Repeat entire Phase 3 as often as necessary
Increase of frequency will decrease file sizes
Staging
37
Set tablespaces read/only Downtime!
SQL:SOURCEDB> alter tablespace TS1 read only;

SQL:SOURCEDB> alter tablespace TS2 read only;
Read Only
Read Only
Staging
38
Create final incremental backup on source
[oracle@source]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl -i
i
Read Only
Read Only
i
Staging
39
Copy xttplan.txt and tsbkupmap.txt to destination
Convert final inc backups and merge them into tablespace files
[oracle@dest]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl r
xttplan.txt
Copy
/home/oracle/xtt
tsbkupmap.txt
iC
iC
Read Only
Read Only
Staging
iC
iC
40
Prepare destination database for Full Transportable Export/Import
SQL:DESTDB> CREATE DIRECTORY ftex_dir AS '/home/oracle/dp';

SQL:DESTDB> GRANT READ, WRITE ON DIRECTORY ftex_dir TO mike;
SQL:DESTDB> CREATE PUBLIC DATABASE LINK v112 USING 'v112';
Read Only
Database Link
Read Only
41
Start Full Transportable Export/Import
[oracle@dest]$ impdp mike/passwd@v121 NETWORK_LINK=v112

FULL=Y TRANSPORTABLE=ALWAYS [VERSION=12]
METRICS=Y EXCLUDE=STATISTICS
LOGTIME=ALL LOGFILE=ftex_dir:v112fullimp.log
TRANSPORT_DATAFILES='/oracle/DQ1/sapdata50/ts1.dbf'
TRANSPORT_DATAFILES='/oracle/DQ1/sapdata50/ts2.dbf'
impdp FULL=Y TRANSPORTABLE=ALWAYS
Read Only
Database Link
Read Only
42
Phase 6 - Validate the Transported Tablespaces
Validate transported tablespaces
RMAN> validate tablespace TS1, TS2 check logical;
Read Only
RMAN>
Read Only
43
Phase 7 - Cleanup
Set tablespaces on source read/write
Cleanup all files created for this process
Cleanup staging area if not done already
44
Yes, we made it
It looks a bit complicated at first sight but once you tried it, it is very straight forward
45
46

19819599151532804185/full Transport 12c

Uploaded by

Copyright:

Available Formats

19819599151532804185/full Transport 12c

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

19819599151532804185/full Transport 12c

Uploaded by

Copyright:

Available Formats

Minimal Downtime Migration

with Full Transportable Export/Import

Updated: Oct 30, 2015

Database Upgrades & Migrations

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

(GA: Sep 2009)

(GA: Aug 2007)

(GA: Jul 2005)

(GA: Jan 2004)

(GA: Jun 2013)

Waived Extended Support

Paid Extended Support

Database Upgrade Blog

"The migration of all 16 German Electronic

Migrate a large database

Cross platform, cross Endianness

of +Terabyte Migrations get

100 Mbit Ethernet

Transfer Transfer Throughput

Concept Transportable Tablespaces

TTS feature available since Oracle 8i

Cross platform support since Oracle 10g

Transportable Tablespaces Pros and Cons

Potentially very fast

Copying large files can be faster than

Cross platform since Oracle 10g

SYSTEM/SYSAUX can't be transported

Too many objects to rebuild

Views, synonyms, sequences

Simple is better for fast TTS!!!

Too many objects in tablespaces

(Sub)partitions, partitioned indexes

Concept Transportable Tablespaces xTTS

Cross platform support

LITTLE ENDIAN PLATFORMS

Microsoft Windows IA (64-bit)

BIG ENDIAN PLATFORMS

AIX-Based Systems (64-bit)

Concept Transportable Tablespaces xTTS

TTS cross platform

RMAN creates a file copy

Use the faster storage

Upgrade/Migration: Transportable Tablespaces

SOURCE Database 11.2.0.4

DESTINATION Database 12.1.0.2

Moving meta information

The brute force approach

The smart approach

SELECT DBMS_METADATA.GET_DDL('SYNONYM', SYNONYM_NAME,

Avoid physical file copies when possible

Use a physical standby

Mount from two sides

Tablespaces can be mounted

Take special care on:

Time zone versions must be equal prior to transport

Otherwise Data Pump will block the meta import

Be careful with starting values for sequences

The biggest pain points of TTS?

Copy and convert a large database