Release Notes

18 Migrating an Oracle Database to Dell EMC SC Series Storage | CML1001
If the endianness of the source and target platforms have different endian formats, an additional step must be
executed to correct data conversion of numeric values during a database. The additional step can be
performed on either the source or target platform. Omitting this critical step will result in failures or corruption
and unsuccessful migration. Refer to the Oracle knowledge base article, How to Migrate to different Endian
Platform Using Transportable Tablespaces With RMAN (Doc ID 371556.1), for step-by-step instructions.
3.7 Selecting and executing the migration methodology
While there are many different ways to migrate a database, there is not one method that can address all
situations. In many cases, it is not uncommon to use multiple methods in a complex database migration. To
decide which method(s) to use, consider the following factors:
• System and database endian formats of source and target systems
• System OS on source and target systems
• Database version on source and target systems
• Windows of downtime
Table 3 summarizes some of the popular migration methodologies available. A brief description of each
methodology follows after the table. Administrators are encouraged to explore each one and review the
vendor’s documentation as each method has its advantages and limitations.
Migration methodology
OS platform/endian format
Migration methodology
Source and target are different
• Transportable tablespaces (including cross-platform and full
transportable, section 3.7.5)
• Export/import facilities (including Data Pump, section 3.7.6)
• RMAN (section 3.7.7)
• Oracle Data Guard (section 3.7.8)
• Oracle Golden Gate (section 3.7.9)
• Streams Replication (section 3.7.10)
• Oracle ASM (section 3.7.1)
Source and target are the same
• Oracle ASM (section 3.7.1)
• Linux LVM (section 3.7.2)
• Linux utilities (section 3.7.3)
• Including the methodologies in the preceding row (source and
target are different)