Choose your shape

Choose your shape

A common thing we heard from customers is that it would be desirable to use different shapes in a Data Guard configuration in the Oracle Cloud.

Well, this is now possible!

First things first, you need to create a primary database. For this blog post, I assume your network has been setup correctly already. If not, you can follow the Oracle Documentation to achieve this. This way we can go ahead immediately with the creation of the databases.

Step 1 is to Create a database system

In this post, to demonstrate the cross-shape functionality, we choose for the Database as a service and we will go for the VM’s.

Obviously, we do not have anything yet, so click on the “Create DB System”.

I have selected a vm running in AD1 in Frankfurt. Which makes sense to me as I am in Europe. For my primary database, I want it to have a little bit more compute power, so I have opted for a VM.Standard2.4 which can have up to 4 available cores on a single instance.

I mentioned single instance, but creating RAC is as easy as well. I have now selected total node count as 1. But if I want a RAC database, I would just select 2. Simple as that. Bear in mind that currently, we do not support yet RAC to single instance Data Guard yet. Keep an eye on the future !

Enterprise Edition High Performance, we leave that default and I like Grid infrastructure, so I leave that default as well.

To demo this, 256GB is more than sufficient, but you see you can have good storage options to move your database too. I am not sharing my public key here, sorry for this 😉

Depending on your current license, you can choose to bring your own license (BYOL) or to choose for license included

As a database server is nothing without a network, the wizard asks the networking info

Next step is to enter the Database information. This page displays after clicking “Next” in the wizard.

As you can see, we offer you plenty of choice regarding version. I would recommend to stick to the latest and greatest.

Then we specify the PDB name and give the SYS-user a very secure password. I recommend a mixture of lowercase, uppercase, numbers and a symbol to be sure. This information is also used in the TDE wallet.

For me the OLTP works fine, but you should align this to your own workload of course.

For a production system, I would definitely recommend to schedule the automatic backups. I will skip this for now, but take in mind that if you do not select this box, you will need to take care of your backups yourself.

There we go, we can click the magic button to create the database for us. Give it some time to complete

In case you did not know yet, you can follow the progress in the portal

After a while the db system is ready for use!


Then we go to the Data Guard associations via the Resources panel and we will add a Standby database.

This brings us to a similar wizard

When you hover the information circle next to “Select a shape” tells you that you can use a different shape. So I did select a smaller shape, as it is DR system. Remark, I also did select another Data center. I will put this one in AD2. And enter the network information. I have put a 2 next to the hostname prefix, so I know this host resides in AD2.

Then we give the admin password and the cloning procedure will begin after clicking the “Enable Data Guard” button.

After clicking the button, the configuration starts updating

After a while, we have a full green Data Guard configuration

Ok let’s verify inside the database. First the primary:

That looks normal and then the standby

That looks good too!

As you could suspect, we use the broker internally

So the proof of the pudding is the eating. We will perform a role transition. Of course, when everything fails, you can do this using the broker yourself, but automation is there, so this time we do it using the browser.

So in the Data Guard associations we find the button “switchover”

So when we click it, we get prompted for the password

and there it goes

After some short time, we find everything green again

Let’s verify

In AD1 we expect to find the standby

That looks good and in AD2 we find the new primary

The cool thing is, that it just works. When you follow the alert logs and doc-logs, no black magic happens behind the scenes. It is just Data Guard as you are used to, except cross vm shapes.

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

Leave a Reply

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

five × 1 =

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

%d bloggers like this: