Avoid Datafile Conversion during Transportable Database
(Doc ID 732053.1)
Last updated on APRIL 04, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 220.127.116.11 [Release 10.2 to 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 16-Dec-2013***
When migrating to a new platform with Transportable Database (RMAN CONVERT DATABASE command), the default behavior is to perform datafile conversion on all datafiles in the database. However, only datafiles that contain undo data require conversion, including all datafiles contained within the SYSTEM tablespace, all datafiles contained within any other tablespace that contains any ROLLBACK segments, and all UNDO tablespaces. Depending on the storage infrastructure and the conversion method used, the time required for a platform migration can be reduced significantly by skipping the conversion process on datafiles that do not require it.
In Oracle Database 10g Release 2 and Oracle Database 11g Release 1, skipping the conversion process on selected datafiles can only be accomplished when performing a target platform conversion and following the steps shown below. It is not possible to skip conversion for any datafile when performing a source platform conversion.
NOTE: When converting FROM/TO HP Tru64 UNIX, in addition to files with UNDO segments, all files with ASSM headers need conversion.
Refer Slow/Poor Performance While Performing Rman Convert on Source HP Tru64 Platform <Document 1442798.1>
Note 1079563.1 RMAN DUPLICATE/RESTORE/RECOVER Mixed Platform Support
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document