Database Migration Method -Transportable Tablespaces

 

Data Pump Full Transportable

 

1. On the on-premises database host, prepare the database for the Data Pump full transportable export by placing the user-defined tablespaces in READ ONLY mode.

2.On the on-premises database host, invoke Data Pump Export to perform the full transportable export.

3.Use a secure copy utility to transfer the Data Pump Export dump file and the datafiles for all of the user-defined tablespaces to the Database Classic Cloud Service compute node.

4.Set the on-premises tablespaces back to READ WRITE.

5.On the Database Classic Cloud Service compute node, prepare the database for the tablespace import.

6.On the Database Classic Cloud Service compute node, invoke Data Pump Import and connect to the database.

7.After verifying that the data has been imported successfully, you can delete the dump file.

 

 Steps :

 

1. CREATE DIRECTORY Exp_for_cloud AS '/u01/Exp_for_cloud';

2. SELECT tablespace_name, file_name FROM dba_data_files; --Save the output

3. SELECT 'ALTER TABLESPACE '||tablespace_name||'READ ONLY;' FROM dba_data_files; -- exicute output for readonly datafiles

4. expdp system FULL=y TRANSPORTABLE=always VERSION=12 DUMPFILE=expdat.dmp DIRECTORY=Exp_for_cloud

5. scp –i Your_private_file_name //dump/Exp_for_cloud/expdat.dmp oracle@IP_address_of_your_machin:/u01/Imp_from_prim

6. scp –i Your_private_file_name //dump/datafile_locatiosn/*.dbf oracle@IP_address_of_your_machin:/u01/Imp_from_prim --*/ copy all datafiles to cloud  output from step 2

7. SELECT 'ALTER TABLESPACE '||tablespace_name||'READ WRITE;' FROM dba_data_files; -- exicute output for back in readwrite datafiles

4. CREATE DIRECTORY Imp_from_prim AS '/u01/Imp_from_prim';

5. impdp system FULL=Y TRANSPORTABLE=always DIRECTORY=Imp_from_prim \

                                'YOUr_datafile_location/example01.dbf', \

                                'YOUr_datafile_location/fsdata01.dbf',\

Database Migration Method - DataPump

Data Pump Conventional Export/Import

 

This example provides a step-by-step demonstration of the tasks required to migrate a schema from an on-premises Oracle database to an Oracle Database Classic Cloud Service database.

 

"Data Pump Export Modes" in Oracle Database Utilities for Release 12.2, 12.1 or 11.2.

"Data Pump Import Modes" in Oracle Database Utilities for Release 12.2, 12.1 or 11.2.

Steps :

1. CREATE DIRECTORY Exp_for_cloud AS '/u01/Exp_for_cloud';

2. expdp system SCHEMAS=vishal,vishalbh ,****,**** DIRECTORY=Exp_for_cloud

3. scp –i Your_private_file_name //dump/Exp_for_cloud/expdat.dmp oracle@IP_address_of_your_machin:/u01/Imp_from_prim

on cloud db server 

4. CREATE DIRECTORY Imp_from_prim AS '/u01/Imp_from_prim';

5. impdp system SCHEMAS=vishal,vishalbh ,****,**** DIRECTORY=Imp_from_prim

Database Migration Method from on-Primises to OCI cloud

Database Migration Methods : 

You can migrate your on-premises Oracle Database database to an Oracle Database Cloud database using a number of different methods that use several different tools.

Not all migration methods apply to all migration scenarios. Many of the migration methods apply only if specific characteristics of the source and destination databases match or are compatible. Moreover, additional factors can affect which method you choose for your migration from among the methods that are technically applicable to your migration scenario.

Some of the characteristics and factors to consider when choosing a migration method are:

·         On-premises database version

·         Oracle Database Cloud database version

·         On-premises host operating system and version

·         On-premises database character set

·         Quantity of data, including indexes

·         Data types used in the on-premises database

·         Storage for data staging

·         Acceptable length of system outage

·         Network bandwidth

To determine which migration methods are applicable to your migration scenario, gather the following information.

1.    Database version of your on-premises database:

·         Oracle Database 11g Release 2 version lower than 11.2.0.3

·         Oracle Database 11g Release 2 version 11.2.0.3 or higher

·         Oracle Database 12c Release 1 version lower than 12.1.0.2

·         Oracle Database 12c Release 1 version 12.1.0.2 or higher

2.    For on-premises Oracle Database 12c Release 1 databases, the architecture of the database:

·         Multitenant container database (CDB)

·         Non-CDB

3.    Endian format (byte ordering) of your on-premises database’s host platform

Some platforms are little endian and others are big endian. Query V$TRANSPORTABLE_PLATFORM to identify the endian format, and to determine whether cross-platform tablespace transport is supported.

Oracle Database Cloud uses the Linux platform, which is little endian.

4.    Database character set of your on-premises database and Oracle Database Classic Cloud Service database

Some migration methods require that the source and target databases use compatible database character sets.

5.    Database version of the Oracle Database Cloud database you are migrating to

·         Oracle Database 11g Release 2

·         Oracle Database 12c Release 1

Oracle Database 12c Release 1 databases created on Oracle Database Cloud use CDB architecture. Databases created using the Enterprise Edition software edition are single-tenant, and databases created using the High Performance or Extreme Performance software editions are multitenant.

 

1.       Migrating from Oracle Database 11g to Oracle Database 11g in the Cloud

2.       Migrating from Oracle Database 11g to Oracle Database 12c in the Cloud

3.       Migrating from Oracle Database 12c CDB to Oracle Database 12c in the Cloud

4.       Migrating from Oracle Database 12c Non-CDB to Oracle Database 12c in the Cloud

 

Below Method are dependent on above 4 types of migrations.

Topics

•             Data Pump Conventional Export/Import

•             Data Pump Full Transportable

•             Data Pump Transportable Tablespace

•             Remote Cloning a PDB

•             Remote Cloning Non-CDB

•             RMAN Cross-Platform Transportable PDB

•             RMAN Cross-Platform Transportable Tablespace Backup Sets

•             RMAN Transportable Tablespace with Data Pump

•             RMAN CONVERT Transportable Tablespace with Data Pump

•             SQL Developer and INSERT Statements to Migrate Selected Objects

•             SQL Developer and SQL*Loader to Migrate Selected Objects

•             Unplugging/Plugging a PDB

•             Unplugging/Plugging Non-CDB