Category: Cloud

12 Days of #Cloud: Day 2

Today, let’s create a 2 node RAC instance on Oracle Cloud. The database creation steps are similar.

First, choose the release of the database.

 

The Service Packaging definition says “Standard and Enterprise packages include their respective on-premises capabilities and add Transparent Data Encryption. High Performance adds all database options excluding: RAC, In-Memory and Active Data Guard. Extreme Performance includes all options.”

So, to create the RAC instance, we need to choose “Extreme Performance” service.

In the Service Details screen, choose RAC checkbox. You have the following options:

• RAC
• Data Guard
• Golden Gate

As soon as you choose RAC, the other options go away. So at this time, it looks like the RAC database may not have Data Guard or Golden Gate.

Here are all the options chosen in Service Details.

I chose 1 CPU machine but looks like RAC instance does not like that.

All is good, the summary screen shows (note the compute shape):

 

That’s it. Rest of the work is done by Oracle Cloud for you.

After about 1+ hours, the RAC instance is created.

The database service has two nodes, 4 OCPUs, 30GB memory.

Enable the ports to connect to database using SQL*Net and to use OEM Database Express. The menu does not have an option to view Dbaas Monitor with the current version of Cloud.

Let’s login to the database backend servers, and verify the services.

The disk allocation on both servers are pretty identical. The standby activation can be completed only after we make sure there are no errors.

The three file systems /dev/asm/data-369, fra-219 and redo-506 are ACFS (u02, u03 & u04) and shared on both systems.

Everything seems to have configured right.

 

 

12 Days of #Cloud: Day 1

There are two ways for SQL Developer to connect to a DBaaS Cloud Instance.

Review how to create a DBaaS Cloud Instance.

1. Using SQL*Net

By default, the Oracle DBaaS Cloud Service blocks access to 1521 port used by SQL*Net. You have to open the port before you can connect using SQL Developer.

Log in to the Oracle Database Cloud Service and click on the service name to see the details. Note down the Public IP address and the Connect String.

Click on the Database Cloud Service menu and choose “Access Rules”.

Enable the “ora_p2_dblistener” access rule, by clicking the menu under Actions.

Now, you can use SQL Developer from your desktop to connect to the Cloud Database as you would connect to any on-premise database. Use the Public IP address as the hostname and the service name in the connect string.

2. Using SSH

This method is a bit more secure. Let’s turn off the 1521 port to make sure our connection using SSH works indeed. Confirm SSH is enabled.

In SQL Developer menu, click on View –> SSH. Then right click and choose “Create New SSH Host”.

Provide the Cloud Database Service Public IP address and the SSH key file. Enable port forwarding on port 1521.

Oops, I chose a wrong key file. Instead of the private key, selected the public key file. Let me fix by editing the SSH host entry.

Now choose “New Connection” in SQL Developer, and configure a connection using connection type SSH. You still have to enter the service name of the cloud database.

When you click Test button,  you will be asked the SSH key passphrase.

And, that’s it. You are ready to go.