Autonomous Database: Creating an Autonomous Transaction Processing Instance
In this post I’m going to demonstrate how quick and easy one can create an Autonomous Transaction Processing, short ATP, instance of Oracle’s Autonomous Database Cloud Services. Oracle’s ATP launched on the 7th of August 2018 and is the general purpose flavor of the Oracle Autonomous Database. My colleague SQLMaria (also known as Maria Colgan 😉 ) has already done a great job explaining the difference between the Autonomous Transaction Processing and the Autonomous Data Warehouse services. She has also written another post on what one can expect from Oracle Autonomous Transaction Processing. I highly recommend reading both her articles first for a better understanding of the offerings.
Last but not least, you can try ATP yourself today via the Oracle Free Cloud Trial.
Now let’s get started. Provisioning an ATP service is, as said above, quick and easy.
tl;dr
To create an instance you just have to follow these three simple steps:
- Log into the Oracle Cloud Console and choose “Autonomous Transaction Processing” from the menu.
- Click “Create Autonomous Transaction Processing“
- Specify the name, the amount of CPU and storage, the administrator password and hit “Create Autonomous Transaction Processing“
Creating an ATP instance
In order to create an ATP environment you first have to logon to the Oracle Cloud Console. From there, click on the top left menu and choose “Autonomous Transaction Processing“.
On the next screen you will see all your ATP databases, in my case none, because I haven’t created any yet. Hit the “Create Autonomous Transaction Processing” button.
A new window will open that asks you about the display and database name, the amount of CPUs and storage capacity, as well as the administrator password and the license to use.
The display name is what you will see in the cloud console once your database service is created. The database name is the name of the database itself that you will later connect to from your applications. You can use the same name for both or different ones. In my case I will use a different name for the database than for the service.
The minimum CPU and storage count is 1, which is what I’m going for. Don’t forget that scaling the CPUs and/or storage up and down is fully online with Oracle Autonomous Database and transparent to the application. So even if you don’t know yet exactly how many CPUs or TBs of storage you need, you can always change that later on which no outages!
Next you have to specify the password for the admin user.
The admin user is a database user with administrative privileges that allows you to create other users and perform various other tasks.
Last but not least, you have to choose which license model you want to use.
The choice is either bringing your own license, i.e. “My organization already owns Oracle Database software licenses“, sometimes also referred to as “BYOL” or “Bring Your Own License“, which means that you do already have some unused Oracle Database licenses that you would like to reuse for your Autonomous Transaction Processing instance. This is usually done if you want to migrate your on-premises databases into the cloud and want to leverage the fact that you have already bought Oracle Database licenses in the past.
The other option is to subscribe to new Oracle Database software licenses as part of the provisioning. This option is usually used if you want to have a new database cloud service that doesn’t replace an existing database.
Once you have made your choice, it’s time to hit the “Create Autonomous Transaction Processing“.
Your database is now being provisioned.
Once the state changes to Green — Available, your database is up and running.
Clicking on the name of the service will provide you with further details.
Congratulations, you have just created your first Autonomous Transaction Processing Database Cloud Service. Make sure you also check out the Autonomous Transaction Processing Documentation.
Originally published at geraldonit.com on August 28, 2018.
