You are on page 1of 9

TransportableTablespace(TTS)RestrictionsandLimitations:Details,Reference,andVersion

WhereApplicable(DocID1454872.1)
InthisDocument
Purpose
Scope
Details

DefaultDATA_PUMP_DIRdoesnotworkwithPDBs

WhenusingtheIMPDPutility,andtheoptionTRANSPORT_TABLESPACES

WhenusingtheIMPDPutility,theTRANSPORT_DATAFILESparameter

WhenusingtheIMPDPutility,andtheoptionTRANSPORT_FULL_CHECK

WhenusingtheIMPDPutility,andtheoptionTRANSPORTABLE

WhenusingEXPDPutility,andtheoptionTRANSPORT_TABLESPACES

IndexOrganizedTables(IOT)canbecomecorruptwhenusingTransportableTablespace

ItisnotpossibletotransporttheSYSTEMtablespaceorobjectsownedbytheuserSYS

TransportableTablespaceimportusingIMPDPfailswhenthetablespacecontainsaspatialindex

JobsperformedintransportabletablespacemodehavespecificrequirementstopreventtheEXPDP/IMPDPjobfrom
failing

ExportingaSchemaInan11.2DatabaseWitha10gClientGivesORA1455

ConsiderationsforTimeZoneFileVersionsinTransportableTablespaceMode

CharacterSetandNationalCharacterSetLimitation

Tablespacewiththesamenamealreadyexists

ObjectswithUnderlyingObjectsMaterializedViewsorPartitionedTables

Objectswhereownerondestinationisnew

SizeLimitations

Tablespacecontainingspatialindexes

TablespacecontainingXMLTypes

UsingAdvancedQueuesinTransportabletablespaces

OpaqueTypes(suchasRAW,BFILE,andtheAnyTypes)canbetransported,however.

FloatingPointNumbersBINARY_FLOATandBINARY_DOUBLEtypes

TraditionalEXP/IMPwith11.2isdesupported

TraditionalEXP/IMPRestrictionswithOracle9i

Encryptedtablespaceshavethefollowinglimitations

DatabaseCharactersetsCompatibilitybetweenSourceandDestination

CompatibilityConsiderationsforTransportableTablespaces

OLAPApplicationAWTransportability

References

APPLIESTO:
OracleDatabaseEnterpriseEditionVersion10.1.0.5to12.1.0.1[Release10.1to12.1]
Informationinthisdocumentappliestoanyplatform.

PURPOSE
ThisarticlehasbeenwrittentodrawtogethertherestrictionsthatapplytotheTRANSPORTABLETABLESPACEFeature.
Theserestrictionsconsistofstandarddocumentedrestrictionsandareaswherecertaindatabasefeaturesdonot
transportandhavebeenraisedasOracleBugs.

EachrestrictionwillbedetailedwithDocumentationreferencesandVersionsgiven,whereapplicable.Examplelinkstothe
11.2and12.1documentationmaybereferenced.

SCOPE
ThisDocumentistobeavailableforthoseusingtheOracleTransportableTablepsaceFeature.
TousethisDocumentpleaseclickononeofthedetailsabovewhichwillguideyoutothepointrequired.

DETAILS
DefaultDATA_PUMP_DIRdoesnotworkwithPDBs
Restriction:InaCDB,thedefaultDataPumpdirectoryobject,DATA_PUMP_DIR,doesnotworkwithPDBs.Youmust
defineanexplicitdirectoryobjectwithinthePDBthatyouareusingwithDataPumpexport/import.
Reference:OracleDatabaseAdministrator'sGuide12cReleaseTransportingTablespacesBetweenDatabases
LimitationsonTransportableTablespacesGeneralLimitationsonTransportingData
AffectedVersion:12c+

WhenusingtheIMPDPutility,andtheoptionTRANSPORT_TABLESPACES
Restriction:WhenusingtheIMPDPutility,andtheoptionTRANSPORT_TABLESPACES.

Youcannotexporttransportabletablespacesandthenimportthemintoadatabaseatalowerreleaselevel.
Thetargetdatabaseintowhichyouareimportingmustbeatthesameorhigherreleaselevelasthesourcedatabase.
TheTRANSPORT_TABLESPACESparameterisvalidonlywhentheNETWORK_LINKparameterisalso
specified.
Transportablemodedoesnotsupportencryptedcolumns.
Reference:OracleDatabaseUtilitiesChapter3DataPumpImport
AffectedVersion:AllVersions

WhenusingtheIMPDPutility,theTRANSPORT_DATAFILESparameter
Restriction:WhenusingtheIMPDPutility,theTRANSPORT_DATAFILESparametercannotbeusedinconjunctionwith
theQUERYparameter.
Reference:OracleDatabaseUtilitiesChapter3DataPumpImport
AffectedVersion:AllVersions

WhenusingtheIMPDPutility,andtheoptionTRANSPORT_FULL_CHECK
Restriction:WhenusingtheIMPDPutility,andtheoptionTRANSPORT_FULL_CHECK.Thisparameterisvalidfor
transportablemode(ortablemodewhenTRANSPORTABLE=ALWAYSwasspecifiedontheexport)onlywhenthe
NETWORK_LINKparameterisspecified.
Reference:OracleDatabaseUtilitiesCapter3DataPumpImport
AffectedVersion:AllVersions

WhenusingtheIMPDPutility,andtheoptionTRANSPORTABLE
Restriction:WhenusingtheIMPDPutility,andtheoptionTRANSPORTABLE.
TheImportTRANSPORTABLEparameterisvalidonlyiftheNETWORK_LINKparameterisalsospecified.
TheTRANSPORTABLEparameterisonlyvalidintablemodeimports(thetablesdonothavetobepartitioned
orsubpartitioned).
TheuserperformingatransportableimportrequirestheDATAPUMP_EXP_FULL_DATABASEroleonthe
sourcedatabaseandtheDATAPUMP_IMP_FULL_DATABASEroleonthetargetdatabase.
TomakefulluseoftheTRANSPORTABLEparameter,theCOMPATIBLEinitializationparametermustbesetto
atleast11.0.0.

Reference:OracleDatabaseUtilitiesCapter3DataPumpImport
AffectedVersion:Greaterthan11.0.0

WhenusingEXPDPutility,andtheoptionTRANSPORT_TABLESPACES
Restriction:WhenusingTheEXPDPutility,andtheoptionTRANSPORT_TABLESPACES
Transportablejobsarenotrestartable.
Transportablejobsarerestrictedtoadegreeofparallelismof1.
TransportabletablespacemoderequiresthatyouhavetheDATAPUMP_EXP_FULL_DATABASErole.
Transportablemodedoesnotsupportencryptedcolumns.
Thedefaulttablespaceoftheuserperformingtheexportmustnotbesettooneofthetablespacesbeingtransported.
TheSYSTEMandSYSAUXtablespacesarenottransportable.
Alltablespacesinthetransportablesetmustbesettoreadonly.
IftheDataPumpExportVERSIONparameterisspecifiedalongwiththeTRANSPORT_TABLESPACESparameter,then
theversionmustbeequaltoorgreaterthantheOracleDatabaseCOMPATIBLEinitializationparameter.
TheTRANSPORT_TABLESPACESparametercannotbeusedinconjunctionwiththeQUERYparameter.
InRDBMSversions<10.2.0.4therewasa4Kcharacterlimitonthetransportable_tablespacesparameterafixin
10.2.0.4increasedthisto32K.Thecompatibilityparametermustbeatleast10.2.0.4orhighertoimplementthishigher
limit.(SeeDocument1131484.1ExpdpTransportableTablespaceFailsWithORA39071forfurtherdetails.)
Reference:OracleDatabaseUtilitiesChapter3DataPumpImport
AffectedVersion:Greaterthan11.0.0,exceptwherenoted.

IndexOrganizedTables(IOT)canbecomecorruptwhenusingTransportableTablespace
Restriction:IndexOrganizedTables(IOT)canbecomecorruptwhenusingTransportableTablespace(TTS)from
Solaris,LinuxorAIXtoHP/UX.Currentlythereisnopatchforthisissue,theIndexOrganizedTables(IOT)needtobe
recreatedaftertheTTS.
References:Document371556.1HowtoMoveTablespacesAcrossPlatformsUsingTransportableTablespacesWith
RMAN,Bug9816640closedasnotfeasibletofix.
AffectedVersion:AllVersionscurrently(checkenhancementBug12683199forversionimplemented).

ItisnotpossibletotransporttheSYSTEMtablespaceorobjectsownedbytheuserSYS
Restriction:SYSTEMTablespaceObjects.ItisnotpossibletotransporttheSYSTEMtablespaceorobjectsownedby
theuserSYS.SomeexamplesofsuchobjectsarePL/SQL,Javaclasses,callouts,views,triggers,roles,procedures,
synonyms,users,privileges,dimensions,directories,andsequences.ThesemustbecreatedseparatelyfromtheTTS
operation,withscriptsorexport/import.
Note:ThefollowingDatabaseSchemas/UsersarealsotreatedsaperSYS:'CTXSYS,'ORDSYS','MDSYS','ORDPLUGINS',
'LBACSYS','XDB','SI_INFORMTN_SCHEMA','DIP','DMSYS','DBSNMParetreatedasobjectsownedby'SYS'andnot
exportedwithTTS.
Reference:OracleDatabaseAdministrator'sGuideTransportingTablespacesBetweenDatabases.
AffectedVersion:Allversions

TransportableTablespaceimportusingIMPDPfailswhenthetablespacecontainsaspatialindex
Restriction:TransportableTablespaceimportusingIMPDPfailswhenthetablespacecontainsaspatialindexdefinedin
it.
Reference:Document579136.1IMPDPTRANSPORTABLETABLESPACEFAILSforSPATIALINDEX
AffectedVersion:11.1andbelow,seeDocument6085408.8formoredetails.

JobsperformedintransportabletablespacemodehavespecificrequirementstopreventtheEXPDP/IMPDP
jobfromfailing
Restriction:JobsperformedintransportabletablespacemodehavespecificrequirementstopreventtheIMPDPjob
fromfailing,beforeanythingisimported.
References:OracleDatabaseUtilitiesChapter2DataPumpExport/Chapter3DataPumpImport,
OracleDatabaseAdministrator'sGuideConsiderationsforTimeZoneFileVersionsinTransportable

TablespaceMode,
Document1275433.1DataPumpTTSImportFailsWithORA39002AndORA39322DueToTIMEZONE
Conflict.
AffectedVersion:AllVersions(Documentedsince11.2perdocBug10417805fixed.

ExportingaSchemaInan11.2DatabaseWitha10gClientGivesORA1455
Restriction:ExportingaSchemaInan11.2DatabaseWitha10gIMP/EXPClientGivesORA1455.Thisisbecauseon
11.2,bydefaultdeferredsegmentcreationfeatureisturnedon.Whenatableiscreatedwithlocallymanagedtablespace
thenitspropertyvalueisverybig.Ifweinsertanyrowinthetablethenit'ssegmentgetscreatedandpropertyvalue
updatedto536870912.
Reference:ThislimitationisdiscussedinDocument1166564.1MasterNoteforTransportableTablespaces(TTS)
CommonQuestionsandIssues
AffectedVersion:Allversions

ConsiderationsforTimeZoneFileVersionsinTransportableTablespaceMode
Restriction:Jobsperformedintransportabletablespacemodehavethefollowingrequirementsconcerningtimezonefile
versions:IfthesourceisOracleDatabase
11grelease2(11.2.0.2)orlaterandtherearetablesinthetransportablesetthatuseTIMESTAMPWITHTIMEZONE
(TSTZ)columns,thenthetimezonefile
versiononthetargetdatabasemustexactlymatchthetimezonefileversiononthesourcedatabase.
IfthesourceisearlierthanOracleDatabase11grelease2(11.2.0.2),thenthetimezonefileversionmustbethesameon
thesourceandtargetdatabase
foralltransportablejobsregardlessofwhetherthetransportablesetusesTSTZcolumns.
Iftheserequirementsarenotmet,thentheimportjobabortsbeforeanythingisimported.Thisisbecauseiftheimportjob
wereallowedtoimportthe
objects,theremightbeinconsistentresultswhentableswithTSTZcolumnswereread.
Toidentifythetimezonefileversionofadatabase,youcanexecutethefollowingSQLstatement:
SQL>SELECTVERSIONFROMV$TIMEZONE_FILE
And
ThisselectgivesallTimeStampwithTimeZone(TSTZ)columnsinyourdatabase:
selectc.owner||'.'||c.table_name||'('||c.column_name||')'
||c.data_type||''col
fromdba_tab_colsc,dba_objectso
wherec.data_typelike'%WITHTIMEZONE'
andc.owner=o.owner
andc.table_name=o.object_name
ando.object_type='TABLE'
orderbycol
/

Reference:ForIMPDPconsiderationsclickonthefollowinglink11gR2Databaseutilitiesguide.
ForEXPDPconsiderationsclickonthefollowinglink11gR2Databaseutilitiesguide.
AffectedVersion:11gonwards

CharacterSetandNationalCharacterSetLimitation
Restriction:Thesourceandtargetdatabasemustuseacompatiblecharactersetandnationalcharacterset.
Reference:OracleDatabaseAdministratorsGuideTransportingTablespacesBetweenDatabasesLimitationson
TransportableTablespaceUse
AffectedVersion:Allversions

Tablespacewiththesamenamealreadyexists
Restriction:Youcannottransportatablespacetoatargetdatabaseinwhichatablespacewiththesamenamealready
exists.However,youcanrenameeitherthe
tablespacetobetransportedorthedestinationtablespacebeforethetransportoperation.
12g+:InaContainerDataBase(CDB),youcannottransportatablespacetoatargetcontainerthatcontainsatablespace
ofthesamename.However,differentcontainerscanhavetablespaceswiththesamename.Asin11g,youcanusethe
REMAP_TABLESPACEimportparametertoimportthedatabaseobjectsintoadifferenttablespace.Alternatively,beforethe
transportoperation,youcanrenameeitherthetablespacetobetransportedorthetargettablespace.
Reference:OracleDatabaseAdministratorsGuideTransportingTablespacesBetweenDatabasesLimitationson
TransportableTablespaceUse
OracleDatabaseAdministrator'sGuide12cReleaseTransportingTablespacesBetweenDatabases
LimitationsonTransportableTablespacesGeneralLimitationsonTransportingData
AffectedVersion:Allversions

ObjectswithUnderlyingObjectsMaterializedViewsorPartitionedTables
Restriction:Objectswithunderlyingobjects(suchasmaterializedviews)orcontainedobjects(suchaspartitioned
tables)arenottransportableunlessallof
theunderlyingorcontainedobjectsareinthetablespaceset.
ReviewTable"ObjectsExportedandImportedinEachMode"fromtheOracleDatabaseUtilitiesdocumentation,thereare
severalobject
typesthatarenotexportedintablespacemode.
Reference:OracleDatabaseAdministratorsGuideTransportingTablespacesBetweenDatabasesLimitationson
TransportableTablespaceUse
AffectedVersion:Allversions

Objectswhereownerondestinationisnew
Restriction:Iftheowner/softablespaceobjectsdoesnotexistontargetdatabase,theusernamesneedtobecreated
manuallybeforestartingthetransportable
tablespaceimport.
Reference:OracleDatabaseAdministratorsGuideTransportingTablespacesBetweenDatabasesLimitationson
TransportableTablespaceUse
AffectedVersion:Allversions

SizeLimitations
Restriction:Inexpdp,whenthenumberoftablespacesdefinedwastoobig,asetoferrorswasreported(ORA39006:
internalerror,ORA39065:unexpectedmasterprocessexceptioninDISPATCH,ORA06502:PL/SQL:numericorvalue
error:characterstringbuffertoosmall,ORA39097:DataPumpjobencounteredunexpectederror6502).
Thebufferlimitationforthequerystatementwas2000,changedto32Kin11g.Aworkaroundisavailable
inDocument566875.1ifpatchingisnotpossible.
References:Document566875.1SizeLimitationsOnCrossPlatformTransportableTablespaces,unpublishedBug
5249074EXPDPERRORSWHENMANYTRANSPORTABLETABLESPACESDEFINED
AffectedVersion:AllVersionslowerthan11gbackportedPatch5249074availablefor10.2.0.3,10.2.0.4.

Tablespacecontainingspatialindexes
Restriction:BeawarethatTTSacrossdifferentendianplatformsarenotsupportedforspatialindexesin10gR1and
10gR2suchalimitationhasbeenreleasedin11g
specificSpatialpackagesmustberunbeforeexportingandaftertransportation,pleaseseeOracleSpatialdocumentation.
Reference:OracleSpatialDeveloper'sGuide
AffectedVersion:Allversions

TablespacecontainingXMLTypes
Restriction:BeginningwithOracleDatabase10gRelease2,youcantransporttablespacesthatcontainXMLTypes,but
youmustusetheIMPandEXPutilities,notDataPumpwhenusingEXP,ensurethattheCONSTRAINTSandTRIGGERS
parametersaresettoY(thedefault).Forversions11.1andhigher,youmustuseonlyDataPump,nottheIMPandEXP
Utilities.Forfurtherdetailsseethefulldocumentationbelow:
ThefollowingqueryreturnsalistoftablespacesthatcontainXMLTypes:
selectdistinctp.tablespace_namefromdba_tablespacesp,
dba_xml_tablesx,dba_usersu,all_all_tablestwhere
t.table_name=x.table_nameandt.tablespace_name=p.tablespace_name
andx.owner=u.username
selectdistinctp.tablespace_name
fromdba_tablespacesp,
dba_xml_tab_colsx,
dba_usersu,
all_all_tablest
wheret.table_name=x.table_name
andt.tablespace_name=p.tablespace_name
andx.owner=u.username
TransportingtablespaceswithXMLTypeshasthefollowinglimitations:
ThedestinationdatabasemusthaveXMLDBinstalled.
SchemasreferencedbyXMLTypetablescannotbetheXMLDBstandardschemas.
SchemasreferencedbyXMLTypetablescannothavecyclicdependencies.(Limitationremovedin11.2.0.2by
unpublishedBug4158608:ORA03113:REGISTERSCHEMAWITHCYCLICDEFINITIONS.)
XMLTypetableswithrowlevelsecurity(RLS)arenotsupported,becausetheycannotbeexportedorimported.
Notethatthislimitationisnotlistedinthe12cdocumentation,butisanactuallimitationfor12.1.(UnpublishedBug
17319395TTSIMPORTDOESNOTIMPORTRLSPOLICYFUNCTIONfor12.1.0.2isfiledandshouldbefixedin12.2.)
IftheschemaforatransportedXMLTypetableisnotpresentinthedestinationdatabase,itisimportedand
registered.Iftheschemaalreadyexistsinthedestinationdatabase,anerrorisreturnedunlesstheignore=yoptionisset.
IfanXMLTypetableusesaschemathatisdependentonanotherschema,theschemathatisdependedonisnot
exported.Theimportsucceedsonlyifthatschemaisalreadyinthedestinationdatabase.(Limitationremovedin11.1.0.7
byunpublishedBug5950173EXPDPDOESNOTHANDLEXMLSCHEMADEPENDENCIES.)
YoumustuseonlyDataPumptoexportandimportthemetadatafordatathatcontainsXMLTypes(11.1and
higher).
Reference:OracleDatabaseAdministratorsGuideTransportingTablespacesBetweenDatabasesLimitationson
TransportableTablespaceUse
AffectedVersion:Allversions,exceptasnoted.

UsingAdvancedQueuesinTransportabletablespaces
Restriction:AdvancedQueuesTransportabletablespacesdonotsupport8.0compatibleadvancedqueueswithmultiple
recipients.
Reference:OracleDatabaseAdministratorsGuideTransportingTablespacesBetweenDatabasesLimitationson
TransportableTablespaceUse
AffectedVersion:Allversions

OpaqueTypes(suchasRAW,BFILE,andtheAnyTypes)canbetransported,however.
Restriction:OpaqueTypesTypes(suchasRAW,BFILE,andtheAnyTypes)canbetransported,buttheyarenot
convertedaspartofthecrossplatformtransportoperation.
Theiractualstructureisknownonlytotheapplication,sotheapplicationmustaddressanyendiannessissuesafterthese
typesaremovedtothenewplatform.
Reference:OracleDatabaseAdministratorsGuideTransportingTablespacesBetweenDatabasesLimitationson
TransportableTablespaceUse
AffectedVersion:Allversions

FloatingPointNumbersBINARY_FLOATandBINARY_DOUBLEtypes
Restriction:FloatingPointNumbersBINARY_FLOATandBINARY_DOUBLEtypesaretransportableusingDataPumpbut
nottheoriginalexportutility,EXP.
Reference:OracleDatabaseAdministratorsGuideTransportingTablespacesBetweenDatabasesLimitationson
TransportableTablespaceUse
AffectedVersion:Allversions

TraditionalEXP/IMPwith11.2isdesupported
Restriction:BeforeperformingaTTSprocedureiiitimportanttobeawarethattheuseoftraditionalEXP/IMPwith11.2
isdesupported.OriginalExportisdesupportedforgeneraluseasofOracleDatabase11g.Theonlysupporteduseof
originalExportinOracleDatabase11gisbackwardmigrationofXMLTypedatatoOracleDatabase10grelease2(10.2)or
earlier.Therefore,OraclerecommendsthatyouusethenewDataPumpExportandImportutilities,exceptinthefollowing
situationswhichrequireoriginalExportandImport.
Reference:OracleDatabaseUtilitiesOriginalExport
AffectedVersion:11.2upwards

TraditionalEXP/IMPRestrictionswithOracle9i
Restriction:WhenperformingaTTSprocedurewithOracle9iitisimportanttobeawareoftheObjectsExportedand
ImportedintheTablespaceMode.Thedocumentbelowdetailsthis.
Reference:Document883153.1WhatObjectsAreExportedWithTransportableTablespaces(TTS)andtheORIGINAL
ExportUtility
AffectedVersion:9i

Encryptedtablespaceshavethefollowinglimitations
Restriction:Beforetransportinganencryptedtablespace,youmustcopytheOraclewalletmanuallytothedestination
database,unlessthemasterencryptionkeyisstoredinaHardwareSecurityModule(HSM)deviceinsteadofanOracle
wallet.Whencopyingthewallet,thewalletpasswordremainsthesameinthedestinationdatabase.However,itis
recommendedthatyouchangethepasswordonthedestinationdatabasesothateachdatabasehasitsownwallet
password.SeeOracleDatabaseAdvancedSecurityAdministrator'sGuideforinformationaboutHSMdevices,about
determiningthelocationoftheOraclewallet,andaboutchangingthewalletpasswordwithOracleWalletManager.
YoucannottransportanencryptedtablespacetoadatabasethatalreadyhasanOraclewalletfortransparentdata
encryption.Inthiscase,youmustuseOracleDataPumptoexportthetablespace'sschemaobjectsandthenimportthem
tothedestinationdatabase.YoucanoptionallytakeadvantageofOracleDataPumpfeaturesthatenableyoutomaintain
encryptionforthedatawhileitisbeingexportedandimported.SeeOracleDatabaseUtilitiesformoreinformation.
Youcannottransportanencryptedtablespacetoaplatformwithdifferentendianness.
Tablespacesthatdonotuseblockencryptionbutthatcontaintableswithencryptedcolumnscannotbetransported.You
mustuseOracleDataPumptoexportandimportthetablespace'sschemaobjects.YoucantakeadvantageofOracleData
Pumpfeaturesthatenableyoutomaintainencryptionforthedatawhileitisbeingexportedandimported.SeeOracle
DatabaseUtilitiesformoreinformation.
Reference:OracleDatabaseAdministratorsGuideTransportingTablespacesBetweenDatabasesLimitationson
TransportableTablespaceUse
AffectedVersion:11.2(N.B.TTSforTDEencryptedtablespacesortablepacescontainingtableswithencrypted
columnsarenolongersupportedfrom12c)

DatabaseCharactersetsCompatibilitybetweenSourceandDestination

Restriction:Thesourceandthedestinationdatabasesmustusecompatibledatabasecharactersets.Thatis,oneofthe
MinimumCompatibilitySetting
followingmustbetrue:
TransportScenario
SourceDatabase
DestinationDatabase
Thedatabasecharactersetsofthesourceandthetargetdatabasesarethesame.
Thesourcedatabasecharactersetisastrict(binary)subsetofthetargetdatabasecharacterset,andthefollowing
threeconditionsaretrue:
+Thesourcedatabaseisinversion10.1.0.3orhigher.
+Thetablespacestobetransportedcontainnotablecolumnswithcharacterlengthsemanticsorthemaximum
characterwidthisthesameinboththesourceandtargetdatabasecharactersets.
+ThetablespacestobetransportedcontainnocolumnswiththeCLOBdatatype,orthesourceandthetarget
databasecharactersetsarebothsinglebyteorbothmultibyte.
Thesourcedatabasecharactersetisastrict(binary)subsetofthetargetdatabasecharacterset,andthefollowing
twoconditionsaretrue:
+Thesourcedatabaseisinaversionlowerthan10.1.0.3.
+Themaximumcharacterwidthisthesameinthesourceandtargetdatabasecharactersets.
Reference:OracleDatabaseAdministratorsGuideTransportingTablespacesBetweenDatabasesLimitationson
TransportableTablespaceUse
AffectedVersion:Allversionsunlessspecificallymentioned

CompatibilityConsiderationsforTransportableTablespaces
Whenyoucreateatransportabletablespaceset,OracleDatabasecomputesthelowestcompatibilitylevelatwhichthe
destinationdatabasemustrun.Thisisreferredtoasthecompatibilitylevelofthetransportableset.BeginningwithOracle
Database11g,atablespacecanalwaysbetransportedtoadatabasewiththesameorhighercompatibilitysetting,
whetherthedestinationdatabaseisonthesameoradifferentplatform.Thedatabasesignalsanerrorifthecompatibility
levelofthetransportablesetishigherthanthecompatibilitylevelofthedestinationdatabase.
Thefollowingtableshowstheminimumcompatibilityrequirementsofthesourceanddestinationtablespaceinvarious
scenarios.Thesourceanddestinationdatabaseneednothavethesamecompatibilitysetting.
Table141MinimumCompatibilityRequirements
MinimumCompatibilitySetting
TransportScenario

SourceDatabase

DestinationDatabase

Databasesonthesameplatform

8.0

8.0

Tablespacewithdifferentdatabaseblocksizethanthe
destinationdatabase

9.0

9.0

Databasesondifferentplatforms

10.0

10.0

OLAPApplicationAWTransportability
Restriction:OLAPApplicationAWTransportability
AWcanonlybetransportedviaTTSif:
"AWtransportabilityonlyworksiftheplatform/operatingsystem/wordsize/endianness/etcmatch."
IfnoneorsomeoftheaboveonlymatchandAWsareincludedinintheTTSexport,theTTSprocesswillresultinthis
errorwhenimporting:
ORA37145:(XSTTS_PLAT)Cannottransportanalyticworkspaceacrossplatforms.
IfthisisthecasethenpleasereferencethefollowingMOSarticle:
HowToCopya10.2OlapApplicationFromOneSystemToAnother(DocID437595.1)
Reference:HowToCopya10.2OlapApplicationFromOneSystemToAnother(DocID437595.1)
AffectedVersion:Allversionsunlessspecificallymentioned

REFERENCES

Didn'tfindwhatyouarelookingfor?