Welcome back.

In this part, we are going to focus on developer tools as well as

productivity and a few other topics. Let's get it started here.

So in terms of autonomous database, we say it empowers the developers, and it

provides the fastest as well as simplest creation of database. Just you need to
specify the capacity as well as name.

And that was a big deal for our developers earlier. When they need a database, they
need to reach out to IT admins and it was a long process. But now that dependency
is not there, and that way it improves the productivity.

So no database management, so no support from DBA required. It's fully automatic

tuning, scaling, updating, or upgrading, they all are managed by Oracle. And its
most flexible and productive for kind of development.

So a single database for relational JSON objects, spatial, graphs, text, et cetera.
So a full set of SDKs-- supports Java, Python, all this-- Go, .NET, and all of
these SDKs. So industry standard compliant-- ISO SQL, JDBC, and 249.

It's more flexible as well as productive since one single database supporting all
of this relational or different kind of objects and things. So apart from that, it
provides several other tools. For example, APEX as well as ORDS.

So they are nothing but browser-based applications that uses ORDS systems, Oracle
REST Data Services. And it provides features of kind of desktop based Oracle SQL
developer. And SQL developer web is enabled only for admin user by default.

And you can use ORDS admin-- enable schema packets that is basically used to enable
SQL developer for any other autonomous databases. So SQL developer web can also be
accessed by actually using URL where you will have the name [INAUDIBLE] and
particular string. So by using the web-based URL, you can access that from your
laptop or desktop machine.

So they provide basically a sophisticated development environment for SQLs,

PL/SQLs. It provides WHATSIT for running queries and scripts report interfaces. A
performance hub, on the other hand, for monitoring of applications as well as
database. Complete data modeling solutions are available in terms of tools.

This built-in application [INAUDIBLE] APEX. APEX is mostly used for simple low
code-based, web-based application development as well as execution. It is pre-
configured on autonomous database. Configuration patching, upgrading of all of the
Oracle Application Express components is fully managed by Oracle.

It provides a browser-based environment to load data, manage database objects, or

develop any kind of REST interfaces. It has the ability to connect with both SOAP
as well as RESTful style web services from Application Express in the database.

Developers can create applications with Oracle Application Express autonomous

transaction processing since all these tools are integrated. ORDS, this data
service makes developers access from applications super simple by automatically
building kind of REST interfaces through database tables [INAUDIBLE] procedures.

You will be able to do HTTP calls or GET, POST, PUT, and DELETE to autonomous
databases. And all the admin schema is REST enabled. So for SQL developer web
access by default. That's the one that's for developers here.

One thing we have covered, APEX and SQL Dev-web access requirements must be inside
the customer VCN. And service user, database admins are automatically granted the
use of tooling. And database must be enabled to use tooling.
So by using this ENABLE_SCHEMA procedure, you can grant this particular privelege
to any of the users within the database. You can access the URL for browser that is
inside the VCN. And if you are not inside the VCN, probably you can do port
forwarding also through bastion host-- that can be explored.

It is found in the DB Connection dialogue Application Connections. So all DBA

actions, their performance hub and session metrics grant database user role
PDB_DBA. So these are a few things in order to use this service tooling you have to
keep in mind.

The source on the database console is itself within autonomous databases. You would
be able to see the URL which you can copy and execute in order to get the web
interface. And Oracle SQL developer, web is also by default enabled, and it
provides you web based access to connect to autonomous database.

In terms of automatic indexing that makes developers job also very easy, they are
implemented in machine learning, and the reinforcement learning allows it to learn
from it's actions as all candidate indexes are validated before implementing. And
this is a continuous process.

And index activities are viewable, controllable, as well as auditable. So real-time

optimizer stats gathering ensures that the plans stay current as part of new
changes. So the first step starts with capture. Periodically, you capture the
application SQL history into a SQL repository. And that basically includes the SQL
or plans or those SQLs bind variables execution stats, et cetera.

And then in the second step, you identify the candidates, and you identify those
candidates' indexes that might get benefit with the newly captured SQL statements.
Create index candidates and [INAUDIBLE] or invisible indexes, and thus [INAUDIBLE]
or drop indexes obsoleted by newly created indexes [INAUDIBLE].

So these are the operations which goes on behind the scenes. Then you verify them,
and you basically, as part of verification, ask the optimizer for index candidates
to be used for capture SQL statement. Or [? materialize ?] the indexes and run SQL
to validate that index are able to improve their performance.

So all verification is done outside of the application workflow. And then you
decide on if performance is better for all the statements, index are marked as
visible. And if performance is worse for all the statements, then the index remains
invisible.

So performance is worse sometimes, some of the SQLs and the indexes are marked
visible except for the SQL statement that has regressed. So that is doing a lot of
intelligence before implementing.

And it also monitors for index users-- continuously monitored-- and automatically
created indexes that have not been in use for a long time. That would be selected
for dropping that [? transfer. ?] So it connect for dropping, and it is also done
automatically.

So you can switch this service off. It is the source control, so it will use only
one CPU for doing auto indexing. If you take a copy of your data and run on your
CPU, then you may run into security and data privacy issues. That's why without
compromising any security, it is able to basically do all of these activities on
the same database in a controlled fashion.

So in terms of orchestration and developer SDKs, we have data from orchestration

and we have our own OCI provider. You can download it from our Terraform URL. So in
terms of language SDK and IDE toolkits, these pages talk more in detail about the
concepts how to use those API.

You can use these Dockers with ATP examples on GitHub. We have an example of how to
build microservices using these autonomous databases. Client compute for database
in Oracle Cloud Marketplace. So Oracle demo client image is configured during OCI
compute provisioning.

So that Oracle Cloud developer image can be downloaded, and you can deploy it in
your tenancy. Let's quickly talk about migrating to autonomous databases. And
autonomous databases is an Oracle managed and secure environment.

And a physical database cannot simply be migrated to autonomous, because database

has to be converted to a Pluggable Database, it has to be upgraded to 19c, and as
well as if it's not encrypted, it has to be encrypted on the cloud. Any change to
Oracle shipped privilege or a stored procedure or views, they must be removed
before you bring legacy database to autonomous.

All legacy structures and unsupported features must be removed. They can
[INAUDIBLE] Large Objects-- LOBs. So migration uses Data Pump to move data into new
autonomous database.

And so as of [INAUDIBLE] release of this one, there was no DBMS_CLOUD support or--
so DMBS_CREDENTIALS used with impdp as well expdp. We have a schema advisor for
existing application and migration tooling that help or basically enable easy and
safe upgrade to modern, autonomous cloud. So they're on same [INAUDIBLE] Oracle
database has an on-prem, same language feature, APIs, and interface.

You can even convert MySQL PostgreSQL server DB with Oracle migration tools. And
transforms fully existing database state to a modern, autonomous cloud-- not just
for new applications. So all these tools let SQL developers-- they can be used for
bringing data, or you can use GoldenGate services. So without any downtime, you
will be able to bring up a database to autonomous cloud.

And GoldenGate cloud service is also available in form of marketplace image in OCI.
And from the OCI console, you can deploy that within no time. And you have to just
set your source as well as destination, and you can start moving data in real-time.

Definitely, you can use for a smaller data files object storage bucket is a good
place. For serverless, you can use DBMS_CLOUD or PL/SQL package-- CREATE_CREDENTIAL
followed with COPY_DATA. That will move the data in OSS into the database.
Password, it's OCI Auth Token. That is not the admin password, so that you have to
keep in mind.

It will be able to monitor the operation using user as well as DBA underscore load
operation tables. And for dedicated, you need to use the DBMS_CREDENTIALS for auth,
and then you can use Data Pump with impdp/expdp. Right now, we don't have
DBMS_CLOUD wrapper, but it might come soon.

In terms of online as well as continuous data migration, as I said, GoldenGate is a

developer marketplace that can be used, or Data Integration Platform Cloud Service
can be used. Service allows to configure autonomous as a target for application.
And you can also use test master creation on serverless-- use the service clone
features. In dedicated, you can use the same technique as a data migration for
clone creation.

So with this, we have covered data migration and a few other prospects. Now we'll
move to part five of autonomous database, where we will cover management as well as
monitoring operation, which is applicable to our autonomous database or transaction
processing. So [INAUDIBLE] autonomous database. Thanks for watching, and I will see
you in part five of this module.