I thought I'd start off this blog with how to start with your DBaaS account. So you just got in your email the credentials for your brand new DBaaS account. Super! Now what?
To start, go to cloud.oracle.com and click the Sign In button in the upper right of the page.
On the next page, in the upper left is the My Services panel. Use the select list to select Public Cloud Services then click the Sign in to My Services button just below it.
Now we fill out the Identity Domain is usually something meaningful to you like your company followed by numbers. Something like ORACLE1234567. Its found in your welcome email as well.
Next you will be asked to sign in. Use the credentials in your email for username, password.
Now click Sign In. Next is the good stuff, what you have been waiting for, your cloud account! (Actually, you will probably be asked to change your password, then some security questions, but after that is the good stuff)
You are now on the My Services Dashboard. Here we can see info about your cloud databases, backup service, java service and computer resources. (Some of these may or may not be visible depending on what you have purchased) On the Database Cloud Service panel, click the Open Service Console link (upper right) to get to the DBaaS Console.
Here we have the DBaaS console. We can create and delete cloud databases, view information about our created databases and even patch, yes patch, databases right from this console. Lets create a database. To start, click the Create Instance button in the right of the page. This will bring up the Create Instance wizard with the steps in this train.
The 1st stop on the train is the Subscription step. Here we choose what type of database we want and the billing frequency. Choose Oracle Database Cloud Service and whatever billing frequency you wish. Im going to choose Monthly. The Oracle Database Cloud Service - Virtual Image just sets up a VM for you, no database, no backup/recovery, no cool patching from the UI. We are going to ignore that option for now. After selecting Billing Frequency, click Next (upper right).
Next up, Software Release. 12c rocks so there is no question on which options to choose here. Just incase, choose 12c and click Next. On the Software Edition page, we can choose what edition of the DBaaS 12c instance we want. To break it down a bit further for you, Enterprise Edition is just regular enterprise edition without the options. High Performance is nearly all the options, except In-Memory Database, Active Data Guard and RAC, with Extreme Performance being everything.
After you have made your edition choice, click Next.
Lets take the Service Details page one panel at a time. In the upper left is Instance Configuration. Here we provide the wizard with the instance name and a description. Next we select a compute shape. Compute Shapes come in 2 flavors, regular and high memory. The high memory option has twice as much memory as the regular options and the same number of OCPUs. Choose from 1 OCPU and 7.5 GB of memory all the way to 16 OCPUs and 240 GB of memory (can it play doom?). Just a note, you can always change the shape in the DBaaS console later on after the instance has been created. The last attribute here is the VM Public Key. Every DBaaS instance is created with a public key that needs the corresponding private key to connect. Upon instance creation, only port 22 (ssh) is open and you need the private key to connect. Keys are really easy to make. This link will step you through creating a key pair. We have also included a pair here for you to get started with. I recommend creating your own. On the page, click the edit button and then for Key file name, use the file browse button to fine the key on your desktop and upload it. When finished, click the Enter button.
In the panel just below is Database Configuration. For the sake of time, lets just leave most of the default values but provide a password here. Now this password will be the password used for all the services and logins for this instance. (APEX admin, glassfish admin, dbaas_monitor user, sys, etc) Please don't use 123456 or manager. (maybe 1234567 or manager1? I kid, don't use those either). Also as stated, failover database is coming soon.
Once you have chosen a secure, hard to guess password, look at the Backup and Recovery Configuration panel in the upper right. The first attribute is Backup Destination lets us choose where are backups are going and if we really want backups at all. This could be a development instance where you don't want backups because you are not going to put anything you can recover later into it or you are using it to test out an application and all the data is pre created with scripts you have. But on the other hand, this cloud be an instance where you care what happens to the data and objects created within.
We have the ability to have backups using block or local storage as well as block (local) and cloud storage. If you have a cloud storage account (can get a trial here), provide the storage container for the Cloud Storage Container attribute. The syntax is:
So for my service, I would use mystorage-oracle1234567/myContainer. Creating a container can be done through curl via a rest service. Ill jumpstart you by including the following curl commands to connect and create a container.
curl -v -X GET -H 'X-Storage-User: storage_service_name-identity_domain_name:USERNAME' -H 'X-Storage-Pass: PASSWORD' https://storage.us2.oraclecloud.com/auth/v1.0
To create a container:
curl -v -X PUT -H 'X-Auth-Token: AUTH_XXXXXXXXXXXXX' https://storage.us2.oraclecloud.com/v1/storage_service_name-identity_domain_name/myNewContainer
Again, substitute the appropriate variables above. Help using the REST APIs for the storage containers can be found here. The username and password are the ones for your storage account or are the same as the database cloud service. Check your Services Dashboard for the presence of the Oracle Cloud Storage Service. Last note on this, storage_service_name might be the word Storage depending on what type of storage you have (metered or non-metered). Metered subscription will be Storage, Non-metered will be storage_service_name. I have a metered subscription so my form will look like the following:
After filling out these 3 sections, click Next for a final review page. When ready, click the Create button on the upper right.
Now take a break, have a snack but in about 30 minutes, you will have a fully functional 12c database in the cloud with backup/recovery configured, ssh enabled, APEX installed, a specially created dbaas monitor, as well as much, much more. Congratulations, you have just created your first 12c cloud database in Oracle's Public Cloud!
Next up, connecting to the new cloud instance via sql developer over ssh.