You are on page 1of 7

UpgradingaDatabaseUsingTransportableTablespaces(TTS)(DocID1457743.

1)
InthisDocument
Goal
Solution

IsTransportableTablespaces(TTS)thebestwaytoupgrademydatabase?

WhataretheprerequisitesforusingTTS?

WherecanIfindagoodexampleforhowtodothis?

CanImovemydatabasefromthisRDBMS/OStothatRDBMS/OScombination?

Arethefollowingcombinationssupported?

CanImigratemyOracleEBusinessSuite(EBS)usingTTS?

Istestingnecessary?

References
ThisdocumentisbeingdeliveredtoyouviaOracleSupport'sRapidVisibility(RaV)processandthereforehasnotbeen
subjecttoanindependenttechnicalreview.

APPLIESTO:
OracleDatabaseEnterpriseEditionVersion9.2.0.1to12.1.0.1[Release9.2to12.1]
Informationinthisdocumentappliestoanyplatform.

GOAL
ThisnoteaddressesupgradingdatabasesviatheTransportableTablespacesmethod,oftenreferredtoasTTSorxTTS
(crossplatformTTS).

SOLUTION
IsTransportableTablespaces(TTS)thebestwaytoupgrademydatabase?
Therearemanywaystoupgradeadatabase.Whichmethodyouusedependsonwhatyouneedtoaccomplish,howbig
thedatabaseis,andhowlongyouhavetoaccomplishit.TTSisonemethodthatyoucanuse.In12c,theFull
Transportablefeatureisintroduced,whichismuchmoreflexibleandeasiertousethanTTS,becauseyounolongerneed
toexplicitlynameallthetablespacesinyourdatabase,andobjectsinSYSTEMcannowbetransportedaswell.Whenthe
sourcedatabaseis11.2.0.3orhigher,andthetargetis12c,TTSisbetterusedfortransportingasubsetoftablespaces
fromonedatabasetoanother,vs.transportingtheentiredatabasetoanotherversionand/orplatform.
Thechartbelowshowssomeadvantages/disadvantagesofusingTransportablefunctionalityasitcomparestotheother
methodsthatarediscussedintheOracleDatabaseUpgradeGuide(11gR2)andOracleDatabaseUpgradeGuide12c
Release1(12.1).
UpgradeMethod
TransportableTablespaces
(TTS)

Advantages
Sourcedatabase
remainsintact.
Lessdowntimethan
straightexport/import
utilitiesbecauseonly
theobjectmetadata
isexported,notthe
data.
Allowsallthreeofthe
following,singly,orin
combination:

Disadvantages
Crossplatform
migrationcanoccur
onlywithRDBMS
version10gor
higher.
Requiresupfront
preparationinterms
ofselfcontainment
requirements(not
requiredfortheother
methods).

OptimalFor...
Flexibility,especially
crossplatform
migrationwhenthe
sourcedatabaseis<
11.2..0.3andthe
targetdatabaseis<
12c.
Upgradinglarge
databasesthatneed
tobemovedtoa
differentserver,

FullTransportable(Data
Pumpwith
TRANSPORTABLE=ALWAYS
andFULL=Yparameters)

Version
upgrade.
32bitto64bit
upgrade.
Crossplatform
migration
(version10g+
only).
Usesanew,empty
targetdatabase(i.e.
justSYSTEM,
SYSAUX,UNDO,
TEMPtablespaces).
Thereforedata
dictionary
inconsistencies,
spuriousobjectsthat
don'tbelongtoSYS
andSYSTEM,etc.are
cleanedup.
Allowsfordryrunsto
determinedowntime
requirementsfor
changecontrol,and
theopportunityto
workoutanyissues
intheprocess
beforehand.
Noneedfora
completedatabase
backupbefore
beginningthe
process,asthe
sourcedatafilesare
nevertouchedother
thantoputthemin
readonlymode.

Requiresreviewof
TTSrestrictionsand
limitations.
Notallobjectsare
transported
structural,norows
exportstillneeded.
Endianness
conversionmaybe
neededbetweenOS
platforms(not
requiredforplain
export/import).
Aseparatecopyof
thedatafilesis
needediflarge,this
canposeasignificant
spaceconsiderationif
thecopyisalsoon
thesourceserver.
Sourcedatabase
shouldbekeptviable
untilyouaresure
therearenoissues
asaresultofthe
process.
Original
export/importutilities
(exp,imp)arenot
supportedforuse
withTTSfor11gR2.
OLAPAnalytic
Workspaceswillneed
tobeexportedtoEIF
formatsbefore
migrationiftheOS
platformisdifferent.

Fulltransportableis
moreautomatedthan
transportable
tablespacesbecause
itmovesthe
metadataanduser
datathatresidesin
nontransportable
tablespacesthan
wouldpreviously
havebeenmovedin
multipleoperations.
Thismakesthefull
transportablefeature
usefulforefficiently
movingadatabaseto
anewcomputer
systemorupgrading
toanewreleaseof
OracleDatabase.
Removestheself
containment
requirementsthatare
neededforTTS.

Onlyforsource
databaseswith
RDBMSversion
11.2.0.3andupbeing
movedto12c.
Requiresreviewof
FullTransportable
restrictionsand
limitations.
Endianness
conversionmaybe
neededbetweenOS
platforms(not
requiredforplain
export/import).
Youcannottransport
anencrypted
tablespacetoa
platformwith
differentendianness.
Aseparatecopyof
thedatafilesis
needediflarge,this
canposeasignificant
spaceconsiderationif

whetherornotthe
OSorRDBMSversion
isthesame.
Seethesenotestoget
started:
Document1166564.1Master
NoteforTransportable
Tablespaces(TTS)
CommonQuestionsand
Issuesforfurtherdetails.
Document1454872.1
TransportableTablespace
(TTS)Restrictionsand
Limitations:Details,
Reference,andVersion
WhereApplicable
Document883153.1What
ObjectsAreExportedWith
TransportableTablespaces
(TTS)andtheORIGINAL
ExportUtility?
Document438035.1HowTo
UseTransportable
TablespacesToCopyOLAP
AnalyticWorkspaces

Flexibility,combined
withease.whenthe
sourcedatabaseis
11.2.0.3orhigher
andthetargetis12c,
especiallycross
platformmigration.
Upgradinglarge
databasesthatneed
tobemovedtoa
differentserver,
whetherornotthe
OSorRDBMSversion
isthesame.
Seethisdocumentationto
getstarted:
OracleDatabase
Administrator'sGuide12c
Release1(12.1)
TransportingDatabases
IntroductiontoFull
TransportableExport/Import
(includeslimitations)

Export/ImportUtilities
(withoutTTSparameters)

Fulltransportable
supportfor
multitenantcontainer
databases(CDBs)
andnonCDBs.
Sourcedatabase
remainsintact.
Lessdowntimethan
straightexport/import
utilitiesbecauseonly
theobjectmetadata
isexported,notthe
data.
Allowsallthreeofthe
following,singly,orin
combination:
Version
upgrade.
32bitto64bit
upgrade.
Crossplatform
migration
(version10g+
only).
Allowsfordryrunsto
determinedowntime
requirementsfor
changecontrol,and
theopportunityto
workoutanyissues
intheprocess
beforehand.
Noneedfora
completedatabase
backupbefore
beginningthe
process,asthe
sourcedatafilesare
nevertouchedother
thantoputthemin
readonlymode.

thecopyisalsoon
thesourceserver.
Sourcedatabase
shouldbekeptviable
untilyouaresure
therearenoissues
asaresultofthe
process.
OLAPAnalytic
Workspaceswillneed
tobeexportedtoEIF
formatsbefore
migrationiftheOS
platformisdifferent.

Sourcedatabase
remainsintact.
Allowsallthreeofthe
following,singly,orin
combination:
Version
upgrade.
32bitto64bit
upgrade.
Crossplatform
migration(no
version
limitation).
Sincethisisalogical
backupbeing
restored,nophysical
structuresfromthe
olddatabaseare
carriedover
therefore,if
corruptionswere

Timeintensivenot
feasibleforlarge
databases.

OracleDatabaseUpgrade
Guide12cRelease1(12.1)
ChooseanUpgradeMethod
forOracleDatabaseThe
Export/ImportMethodfor
MigratingDataWhen
UpgradingOracleDatabase

Smallerdatabases
needingtobemoved
toadifferentserver,
regardlessof
whethertheOSor
RDBMSversionisthe
same.

presentinthesource
database,theywill
notbepresentinthe
target.
Tablespacesare
newlyreorganizedin
termsofspace
usage.
Noneedfora
completedatabase
backupbefore
beginningthe
process,asthe
sourcedatafilesare
nevertouched.
DBUA

GUIautomatesthe
process.
Inplaceupgradeof
thedatadictionary
anddatafileheaders,
sonoseparatecopy
ofthedatafilesis
needed.
Therearenonon
transferrableobjects.

GUIcontrolsthe
process.
Requirescomplete
backupbefore
beginningthe
upgradeprocess.
Requiresabackout
plananddowntimeto
executeit,ifneeded.
Datadictionaryisnot
rebuilt,soany
inconsistencies
remain.
The"oldversion"of
thedatabaseno
longerexists.

Databasesthatdo
notneedtobemoved
toanotherserveror
OSwhenupgraded.
Seethesenotestoget
started:
Document
1503653.1Complete
ChecklistforManual
UpgradestoOracle
Database12cRelease1
(12.1)
Document739485.1Howto
estimatethetimerequired
toupgradeadatabase?
Document870814.1
CompleteChecklistto
UpgradetheDatabaseto
11gR2usingDBUA
Document871665.1HowTo
RestoreADatabaseBackTo
TheSourceReleaseAfter
UpgradingItToOracle
11gR2UsingDBUA

ManualUpgradeviaOracle
providedScripts

Controloverthe
processbeingrun.
Inplaceupgradeof
thedatadictionary
anddatafileheaders,
sonoseparatecopy
ofthedatafilesis
needed.
Therearenonon
transferrableobjects.

Requiresknowledge
ofthemanual
commands.
Requirescomplete
backupbefore
beginningthe
upgradeprocess.
Requiresabackout
plananddowntimeto
executeit,ifneeded.
Datadictionaryisnot
rebuilt,soany
inconsistencies
remain.
The"oldversion"of
thedatabaseno

Databasesthatdo
notneedtobemoved
toanotherserveror
OSwhenupgraded.
Seethesenotestoget
started:
Document
1503653.1Complete
ChecklistforManual
UpgradestoOracle
Database12cRelease1
(12.1)

longerexists.

Document837570.1
CompleteChecklistfor
ManualUpgradesto11gR2
Document429825.1
CompleteChecklistfor
ManualUpgradesto11gR1
Document316889.1
CompleteChecklistfor
ManualUpgradesto10gR2

Unplug/plugPDBintoHigher
Version

Databaseisupgraded
bysimplyunplugging
fromoneCDB,
pluggingintoanother
CDBofhigher
version,andrunning
anupgradescript.
Theupgradescript
canberunon
multiplePDBsinthe
sameCDBatonce.

Multitenantoption
requiredformore
thanonePDBina
CDB.
Samerestrictions
applyfor
considerationssuch
ascharacterset,and
installedoptions.
TheCDB's
charactersetand
installedoptionsmust
beequaltoora
supersetoftheones
forthePDB.
Backup
recommended.

PDBsingeneral.
Movingtoadifferent
server,whetheror
nottheOSorRDBMS
versionisthesame.
SeetheOracle
documentationfor
UpgradingaPluggable
Databaseforcomplete,
stepbystep,upgrade
instructions.

WhataretheprerequisitesforusingTTS?
TaketimetothoroughlyreviewtherestrictionsandlimitationsforTTS,followbestpractices,andreviewtheTTSmaster
note,whichcontainscommonquestions,errors,andalistofknowncorruptionbugs.Thistakesupfrontwork,butwill
helpensureasmoothexportandimportwithoutissues.Onceyou'vemadethisinitialinvestmentoftimeonthe
prerequisites,upgrading/movingseveraldatabasesofthesameversionbecomesquiteefficient.
Restrictionsandlimitationsareconsolidatedintothisnote:Document1454872.1TransportableTablespace(TTS)
RestrictionsandLimitations:Details,Reference,andVersionWhereApplicable
Bestpracticesarediscussedinthisnote:Document1457876.1BestPracticesforUsingTransportableTablespaces
(TTS).
Commonquestions,errors,andalistofknowncorruptionbugsaregatheredinthisnote:Document1166564.1
MasterNoteforTransportableTablespaces(TTS)CommonQuestionsandIssues

WherecanIfindagoodexampleforhowtodothis?
TheTTSmasternoteDocument1166564.1providessomegoodnotesthathaveeasytofollowexamples.Theyarealso
listedhereforconvenience.(SeetheTTSmasternoteforASMnotes.)
Document371556.1HowtomovetablespacesacrossplatformsusingTransportableTablespaceswithRMAN
Document243304.110g+TransportableTablespacesAcrossDifferentPlatforms"alsogivesanicebeginningtoend
example
Document733824.1HowToRecreateadatabaseusingTTS(TransportableTablespace)

CanImovemydatabasefromthisRDBMS/OStothatRDBMS/OScombination?
TransportableTablespaceswerefirstintroducedin8i,soyoucanuseTTSbetweenanyversionofthedatabasefrom8ion,
aslongasit'sonthesamearchitecture.Startingin10g,youcanalsomovea10g+databaseacrossOSplatforms
(differentarchitectures)withTTS(sometimesalsoreferredtoasXTTSforcrossplatform).YoucanalwaysfindtheOS
platformssupportedforTTSbyyourversionofthesourcedatabasebyrunningthisquery.Iftheplatformyou'relookingto
moveTOisonthislist,thenyoucanmoveyour10g+databasetoit.

SQL>Thislisttakenfrom11.2.0.3.OlderRDBMSversionsmaycontainfewerplatforms.
SQL>Thelistwillnotcontaintheplatforminfoforthedatabasefromwhichyouarerunningthe
query.
SQL>colplatform_namefora35
SQL>select*fromv$transportable_platformorderbyplatform_id
PLATFORM_IDPLATFORM_NAMEENDIAN_FORMAT

1Solaris[tm]OE(32bit)Big
2Solaris[tm]OE(64bit)Big
3HPUX(64bit)Big
4HPUXIA(64bit)Big
5HPTru64UNIXLittle
6AIXBasedSystems(64bit)Big
7MicrosoftWindowsIA(32bit)Little
8MicrosoftWindowsIA(64bit)Little
9IBMzSeriesBasedLinuxBig
10LinuxIA(32bit)Little
11LinuxIA(64bit)Little
12MicrosoftWindowsx8664bitLittle
13Linuxx8664bitLittle
14Linuxx8632bitLittle
15HPOpenVMSLittle
16AppleMacOSBig
17SolarisOperatingSystem(x86)Little
18IBMPowerBasedLinuxBig
19HPIAOpenVMSLittle
20SolarisOperatingSystem(x8664)Little
21AppleMacOS(x8664)Little
SQL>Youcaneasilyfindtheplatforminfoforthedatabaserunningtheabovequerybyusingthe
followingSQL:
SQL>SELECTtp.platform_id,substr(d.PLATFORM_NAME,1,30),ENDIAN_FORMAT
FROMV$TRANSPORTABLE_PLATFORMtp,V$DATABASEd
WHEREtp.PLATFORM_NAME=d.PLATFORM_NAME

Arethefollowingcombinationssupported?
ThefollowinglistssomecommonscenariosandwhetherornottheyaresupportedbyTTS:
1.Move9.2.0.xonSolaris64bitto11.2.0.xonSolaris64bit(sameOS)?
Yes,TTSwillsupportthis,sincethe9.2.0.8supportsversionupgrades,andtheOSdidn'tchange.
2.Move9.2.0.xonSolaris64bitto11.2.0.xonLinuxx86_64?
No,TTSwillNOTsupportthis.TheendiannessoftheOSisdifferent(bigtolittle),andcrossplatformisnot
supporteduntil10g.Youwillneedtoupgradethedatabaseto10g(orhigher)onthecurrentserver,andthenuse
TTStomovecrossplatform.
3.Move9.2.0.xonSolaris64bitto11.2.0.xonAIXBasedSystems(64bit)?
No,TTSwillNOTsupportthis.Eventhoughtheendiannessisthesame(bothbig),theRDBMSversioniswritten
intothedatafileheaders,andcrossplatformisnotsupporteduntil10gtheimportwillfail.YoualsoCANNOTusea
10gexportbinarytoexportthe9idatabase,asitwillalsofailontheimport.Youwillneedtoupgradethedatabase
to10g(orhigher)onthecurrentserver,andthenuseTTStomovecrossplatform.Onceyoursourcedatabaseis
at10g(orhigher),iftablespacesyouaretransportingdonotcontainundoorrollbacksegments,youdonotneedto
convertthemwhenmovingtoanotherOSwiththesameendianness(rollbacksegmentsandundosegmentsare
removedfromadata/indextablespacewhenthetablespaceisputinreadonlymode).
4.Move10.1.0.xonAIXBasedSystems(64bit)to11.2.0.xonSolaris64bit?
Yes,TTSwillsupportthis,sinceendiannessisthesame(bothbig),andtheRDBMSversionis10g(orhigher).If
tablespacesyouaretransportingdonotcontainundoorrollbacksegments,youdonotneedtoconvertthemwhen
movingtoanotherOSwiththesameendianness(rollbacksegmentsandundosegmentsareremovedfroma
data/indextablespacewhenthetablespaceisputinreadonlymode).
5.Move10.1.0.xonLinuxx86_64to11.2.0.xonSolaris64bit?
Yes,TTSwillsupportthis,sincetheRDBMSversionis10g(orhigher).Youwillneedtoconvertthedatafilesbefore
importinginstructionsfordoingthisarecontainedinthenotesreferencedaboveunderthequestion,"WherecanI
findagoodexampleforhowtodothis?"

CanImigratemyOracleEBusinessSuite(EBS)usingTTS?
Yes,theEBSmigrationusesTTS,buthasitsownsetofscriptsandprocedures.Therestrictionsandlimitations
referencedinthisnotestillapply.PleaseseeoneofthefollowingnoteforEBSmigrationprocedures.
Document729309.1UsingTransportableDatabasetomigrateOracleEBusinessSuite11iUsingOracleDatabase
10.2.0or11.1.0
Document734763.1UsingTransportableDatabasetomigrateEBusinessSuiteR12UsingOracleDatabase10gR2
or11gR1

Istestingnecessary?
Absolutely!Anyupgradeprocessresultinginanewdatabaseversionandpossiblychangesinplatform,operatingsystem,
andhardwareshouldbethoroughlytestedtoensureallfunctionalityisverifiedandperformancemeetsexpectationsprior
toemployingtheprocessforproductionoperations.

REFERENCES
NOTE:733824.1HowToRecreateADatabaseUsingTTS(TransportableTableSpace)
NOTE:1457876.1BestPracticesforUsingTransportableTablespaces(TTS)
NOTE:419550.1DifferentUpgradeMethodsForUpgradingYourDatabase
NOTE:1454872.1TransportableTablespace(TTS)RestrictionsandLimitations:Details,Reference,andVersionWhere
Applicable
NOTE:1166564.1MasterNoteforTransportableTablespaces(TTS)CommonQuestionsandIssues
NOTE:371556.1HowtoMigratetodifferentEndianPlatformUsingTransportableTablespacesWithRMAN
NOTE:243304.110g+:TransportableTablespacesAcrossDifferentPlatforms
Didn'tfindwhatyouarelookingfor?