Autonomous Data Guard – First steps

Autonomous Data Guard – First steps

Recently we have announced a new member in the Autonomous family: Autonomous Data Guard. Yes it is really autonomous! All is automatic and it is very easy to use. Here are the first steps on how to use it.

The GUI way

Create your ADB-S Database. You can do this by clicking the “Create autonomous Database” button.

Fill in some basic information

Make sure you select a 19c database

And of course you will need a good password.

For Demo purposes (I will destroy it afterwards anyhow) I took network settings to be available from everywhere, but if you want to deploy it for production use, please use your own VCN and make sure it is not publicly available on the world wide web.

When the creation has finished, we need to enable the Autonomous Data Guard. By default it is disabled.

It is as easy as clicking the button

You agree that the magic will incur some service costs. Which of course is normal as we are using more resources.
During the creation of the peer database it tells you it is busy doing so

So you see here that no hard work is to be done. Just click the link and the system does everything for you. Whilst it is doing so, it is a good moment to have a look at the documentation here:

And after a while we have setup our Autonomous Data Guard in a serverless ADB instance!

Maybe it goes without saying, but if you want to terminate the instance, the bystander database is also cleaned up

Using the tooling

This is even simpler.

From my earlier post about OCI tooling to setup Data Guard, you might remember that I store my longer-to-type commands in environment variables, so I keep doing so for this.

To Create an autonomous database the command is pretty simple:

Don’t forget to make sure to specify a 19c version. At the date of publication, the default is still 18c and Autonomous Data Guard is not available there. It gives you back a Json with all the info:

And of course this good friend is also quickly created

But we can check it with OCI too:

I have then stored the OCID from the new pvanpuymcli database in my ADBID variable and to enable it for Autonomous Data Guard you just issue following command

Then it returns a lot of Json again to inform you

And afterwards you see it starts provisioning again, just as the GUI did

And after a while, when all is done, it is just as if you did it via GUI


This is literally as simple as clicking a button and to quote my Friend Franck Pachot “It just works”. Always nice to hear.

For the commandline, it is also a very simple command:

And with the corresponding Json

During the role transition, you can see it in the GUI too

This state also prevents you from doing strange things to the ADB. Which makes sense, as during a role transition you don’t want to get stuck.

Something very nice, which I really like is that when the role transition finished, it just tells you how it went


Setting up Autonomous Data Guard on a serverless instance is very simple. Despite the process being very complex, the tooling guys did a great job to make this work!

It just works!

As always, questions, remarks? 
find me on twitter @vanpupi

Leave a Reply

Your email address will not be published. Required fields are marked *

two × three =

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: