Oracle's newest autonomous database services take away the mystery and overhead of deploying and managing high performance databases. On August 7th, Oracle announced the Autonomous Transaction Processing service, comparing it to a self driving car. For a database service this means, easy provisioning, self managing in terms of backups, patching, availability and performance and zero downtime scaling
Lets take a quick look at deploying an ATP instances and connecting to it via sql developer
Login to your Oracle Cloud account at https://cloud.oracle.com using your tenant, username and password.
Once logged in select Autonomous Transaction Processing from the top left hamburger menu
Oracle Cloud Infrastructure allows logical isolation of users within a tenant through Compartments. This allows multiple users and business units to share a tenant account while being isolated from each other. Select a compartment you wish to provision an ATP database instance in or create one. Here I've picked a pre provisioned compartment called DBPM.
Needless to say, you then hit the Create Autonomous Transaction Processing button. Quite a mouthful, I just like to call it ATP
On the Create ATP page, you need some basic info for provisioning. A name, size of your instance in cores and storage and an admin password.
Scroll down the form and you will see a couple of licensing options
Oracle allows you to bring your unused on-prem licenses to the cloud and your instances are billed at a discounted rate. This is the default option so ensure you have the right license type for this subscription
This means your cloud service instance should include database license. This is an all-inclusive cost and you do not need to bring any additional licenses to cloud
Finally, you can create tag for your instance to group them together for easier search and management. For eg. Dev_DB or Tier1_appDB, Fin_DB etc
Hit button at the bottom and your database will be provisioned in a few minutes.
Lets now connect to this database.
Select the ATP instance you just provisioned
Click Service Console button and provide username (admin) and password you provided at the time of provisioning
From the Admin panel, select ‘Download Client Credentials’. Provide a keystore password and save the file to your local machine. You will need this file and keystore password to connect to the database later.
The credentials zip file contains the encryption wallet, Java keystore and other relevant files to make a secure TLS 1.2 connection to your database from client applications. Store this file in a secure location.
Next, we will connect to the nodeAppDB database using Oracle SQL Developer.
Launch SQL Developer and select Add connection top left
Enter a connection name, username (admin) and password provided at the time of provisioning. Select connection type as ‘Cloud PDB’
Configuration file is the connection wallet downloaded from ATP console. Enter keystore password provided at the time of wallet download from the admin console
Finally, select service name from drop down. Service name is database name followed by suffixes low, medium or high. These suffixes determine degree of parallelism used and are relevant for a DSS workload. For OLTP workloads its safe to select any of them. We select nodeappdb_medium
Test your connection and save. You now have a secure connection to your cloud database. As simple as that.