Use the Oracle Cloud Infrastructure console to create an autonomous database
instance and create a user.
You can start from the cloud.oracle.com homepage. Click Sign in.
On the Cloud Account page, enter the cloud account name that you received
from your welcome email or your cloud administrator. Click Next.
Enter your username and password. Click Sign In.
On the Oracle Cloud Console, click the navigation menu in the upper corner to
show top-level navigation choices. This video shows the steps to create an
autonomous database in Autonomous Transaction Processing. The same steps
apply to creating an autonomous database in Sutonomous Data Warehouse. In the list
of available services, select Autonomous Transaction Processing.
The console for Autonomous Database appears. You can use the List Scope drop-down
menu to select a compartment. In this example, the Doc compartment is selected.
Although this console shows that no databases have yet been created, if there
were a long list of databases, you could filter the list by using the Filters
drop down menu to filter the state of the database: available, stopped,
terminated, and so on. You can also filter the list by workload type. You can choose
transaction processing or data warehouse as your workload type. Click Create
Autonomous Database. In the create autonomous database dialog,
select a compartment for the database from the drop down list. Enter a database
display name for display purposes. Enter the database name. Choose the workload
type. Autonomous Transaction Processing is automatically selected. You can
alternately choose Data Warehouse as the workload type. Choose the deployment type.
The Shared Infrastructure deployment type runs the autonomous database
without provisioning a dedicated infrastructure. Otherwise, you can choose
the Dedicated Infrastructure deployment type to run the autonomous database on a
dedicated Exadata infrastructure. You can optionally create an always free
database. Always free databases are provided free of charge and are suitable
for small-scale applications or for learning about and exploring Oracle Cloud
Infrastructure. Specify the number of CPUs for your service. Select your
storage capacity in terabytes. If you select the auto scaling option because
your workload requires additional CPU and i/o resources, the database
automatically uses the resources without any manual intervention required.
Oracle periodically provides a preview version of autonomous database. You can
enable the preview mode to test your applications and become familiar with
features in the next release of autonomous database. Snd specify an
administrator password for the admin user of the service instance.
By default, secure connections are allowed from all IP addresses. You can
control and restrict access to your autonomous database by setting network
access control lists. For licensed type, select whether you are
using an included license or bringing your own license. Click Create Autonomous
Database. The Create Autonomous Database dialog
closes. On the console, the State field indicates that the database is
provisioning. When creation is completed, the State field changes from
provisioning to available. Once you have created the instance,
download the credentials zip file for client access to that instance. From the
autonomous database Details page click DB Connection.
Download a zip file containing the security credentials and network
configuration files to access your instance. Oracle recommends you download
the database-specific wallet type, instance wallet, to provide to your end
users and for application use whenever possible. The other wallet type, regional
wallet, should only be used for administrative purposes that require
potential access to all autonomous databases within a region. You're
prompted to create a password for the credential zip file. Enter a password and
click Download to download the file. Store the file and make note of the
password. Some database clients require both the credentials wallet and the
password to connect to the database. SQL Developer versions 18.2 and later
don't require the password. Now you can define the SQL Developer
connection to the database in your Autonomous Transaction Processing
service. Click New Connection to open SQL Developer and define the
connection. Specify a connection name. Enter the database user name using the
default administrator database account, admin, that is provided as part of the
service. Enter the admin user's password that you or your cloud administrator
specified when creating the service instance. For connection type, select
Cloud Wallet. For the configuration file, click Browse and select the client
credentials zip file. And if you're using a version of SQL Developer older than
18.2 there is a Keystore Password field for entering the client credentials zip
file password. For the service, select TP urgent, TP, high,
medium, or low. These service levels map to the TP urgent, TP, high, medium, and low
consumer groups which provide different levels of performance and concurrency.
Click Connect to connect to your database.
Once you have connected SQL Developer to your Autonomous Transaction
Processing database, use a SQL Developer worksheet to define database
users. Autonomous Transaction Processing databases come with a predefined
database role named dwrole. This role provides the common privileges for a
database user.
For detailed steps on performing the example shown in this video, go to the
Oracle Learning Library and open the tutorial named Getting Started and
Provisioning an Autonomous Database.
Learn more at cloud.oracle.com/atp.