Welcome back.

We will start with part two, where we are going to discuss about how
you can migrate to Autonomous Databases using MV2ADB. So on Oracle's site, you have
a web page dedicated to this, and it provides more information about the tool. But
before we start using MV2ADB, let's talk about what is the general migration path
when it comes to on-prem.

You have a database on-prem. You want to bring data to object Storage. And from
object storage, you take them to autonomous Oracle database. Because you cannot use
[INAUDIBLE] clone or something.

So that is the [INAUDIBLE] way. Either you can use SQL Developer-- if you have
certain files to upload, you can do that. But it is assisted approach to bring,
maybe, the data from exports to object storage. Or even for SQL*Loader files, once
they are in Object Storage, you would be able to move to Autonomous Database.

On a general migration techniques, DBMS_CLOUD, that was developed with [INAUDIBLE]

SQL [INAUDIBLE]. And that provides support for loading data from various formats,
whether it's desktop, or creating profiles in the cloud, to your tables, to
autonomous data warehouse.

And DBMS_CLOUD supports learning from various objects stores. So we start with
Oracle Cloud Infrastructure object stores or Oracle Cloud Infrastructure object
storage classic, or any Azure block storage, as well as Amazon S3. So it has
compatibility for all of these.

The more details about using this particular method, DBMS_CLOUD, you can refer to
the [INAUDIBLE] 2493502.1, and they have given examples on, step-by-step, how you
can create a credential, or how you copy data, or how you define the external
structures. So they are covered under the MOS Note and you can utilize them. The
other method of SQL developers, as data from SQL*Loader or MV2ADB. So these are the
supported methods if you want to move to Autonomous Databases.

From Cloud Migration best practice, you can use the Schema Advisor when you migrate
to Oracle Autonomous Database. And they provide you insight on what is available in
on-prem or the source, like if it can be moved or if it cannot be moved. Because
there are certain logistics inside, and we expect, mostly, to bring the data and
[INAUDIBLE], like any kind of partitioning requirements or indexes and things.

So that can be always done within the database by its own, right? So most of the
things it decides, and also changes the formats and all. So just bringing data, as
well as the referential integrity of business constants, is mostly enough for most
of the time.

And this MOS Note again, 2462677.1, they provide the Schema Advisor a little
details. And it is highly suggested to use that one on your source system so that
you can evaluate what can be moved or what you have to factor during the migration.
You can use the MV2ADB, when migrating to Oracle Autonomous Database, and we are
going to cover more details on this tool.

So the MOS Note which talks about MV2ADB is 2463574.1. And Move To Autonomous
Database is, basically, a new tool which will permit you to load data and migration
from your own team to autonomous database cloud, which basically leverages the
Oracle data from the export, Expdp, Impdp, and with a single command, it is able to
migrate to autonomous databases.

So data dump import allows you to, basically, import data from data dump file which
resides on Oracle Cloud Infrastructure object storage. And you can save your data
to your object storage, and then, that will be used for loading them to Autonomous
Database using MV2ADB.
So there are several operations which are supported. So multiple autonomous
databases supports operations such as auto operation and our Expdp operation, Impdp
operation. So they are covered in more details into the MOS Note.

So some of the prerequisites for using MV2ADB is you must have the OCI command line
interface installed. And if you have not already done it, you can always take that
from GitHub or from the cloud.oracle.com site.

So it takes a few minutes to get installed, and the prerequisites for them is
Python and a few packages. And once they are installed, you will have your tenancy-
related details, like [INAUDIBLE] of your tenancy, or auth tokens, and a few other
details with respect to for Oracle Cloud Infrastructure environment. And MV2ADB
will take use of that, and it can help you migrate.

The the operations which it is covered, like as I said, Auto operation, or Expdp,
Impdp. It has the ability to create bucket. It can delete buckets, list bucket
operations, or put dump, get dump. So all of these are supported methods along with
this tool, MV2ADB.

So the MOS Note talks about how it will get started by installing it, or running
the installer [INAUDIBLE] provides the script for you to use for migration. On a
high level, this migration to MV2ADB, there are different operation modes. And
these are also Expdp and Impdp. And then, we have OCI object storage bucket
operations, as well as it supports the object storage object operations such as
delete dump, or get dump, or list dump, or putting the dump into that.

On the right side, you see an example on how to use this utility, MV2ADB, along
with various parameters. Auto operation is one command of this in here that
performs the entire load data process into Autonomous Database Cloud. And Expdp
does it from the source, which is [INAUDIBLE], basically. And it can upload the
dump over to object storage, and Impdp then takes over to Autonomous Database
Cloud. The Impdp operation is going to import the schema into Autonomous Database
Cloud, which is copied over to object storage using the Expdp command here.

Here, I am concluding the part two. I believe like you might have got understanding
on how to use MV2ADB utility. And the MOS Note talks about much detail, along with
examples. So I will encourage you to take a look at them. And now with that one,
I'm going to move to part C, where will cover Oracle Zero Downtime Migration. So
thanks for watching.