The console for Autonomous Database displays. You can use theList Scopedrop-down menu to select a compartment; in this example theDoccompartment is selected. Clickherefor documentation on creating compartments.ㄹㅇㄴㅁㄹ
This console shows no databases. If there were a long list of databases, you could filter the list by using theFiltersdrop-down menu to filter by the state of the databases (available, stopped, terminated, and so on). You can also sort by workload type. Here Transaction Processing is selected. ClickCreate Autonomous Databaseto create a database instance.Description of the illustration create_autonomous_transaction_processing_database
The Create Autonomous Database dialog appears. Enter the following information:
Provide basic information for the Autonomous Database:
Choose a compartment- Select a compartment for the database from the drop-down list.
Display Name- Enter a name for the database for display purposes.
Database Name- Use letters and numbers only, starting with a letter. Maximum length is 14 characters. (Underscores not initially supported.)
Choose a workload type. Select the workload type for your database from the choices:
Transaction Processing- For this tutorial, chooseTransaction Processingas the workload type. Do not choose Data Warehouse.
Data Warehouse- (Alternatively you can chosen Transaction Processing as the workload type.)
Choose a deployment type. When you choose Transaction Processing as the workload type, you are presented with a choice of two deployment types:
Serverless- For this tutorial, select Serverless. This choice creates the autonomous database without provisioning a dedicated infrastructure.
Dedicated Infrastructure- (Alternatively, you can choose the Dedicated Infrastructure deployment type to create the autonomous database on a dedicated Exadata infrastructure. This tutorial does not cover the Dedicated Infrastructure deployment type.)
Configure the database:
Always Free- For this tutorial, do not activate this option. Always Free databases are provided free of charge, and are suitable for small-scale applications or for learning about and exploring Oracle Cloud Infrastructure.
CPU core count- Number of CPUs for your service.
Storage (TB)- Select your storage capacity in terabytes. It is the actual space available to your service instance, including system-related space allocations.
Auto Scaling- For this tutorial, do not activate this option. If you select the auto scaling option, Autonomous Transaction Processing can use up to three times more CPU and IO resources than specified by the number of OCPUs. When auto scaling is enabled, if your workload requires additional CPU and IO resources, the database automatically uses the resources without any manual intervention required.
Enable Preview Mode- For this tutorial, do not activate this option. 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.
Create administrator credentials:
PasswordandConfirm Password- Specify the password for ADMIN user of the service instance. The password must meet the following requirements:
The password must be between 12 and 30 characters long and must include at least one uppercase letter, one lowercase letter, and one numeric character.
The password cannot contain the username.
The password cannot contain the double quote (") character.
The password must be different from the last 4 passwords used.
The password must not be the same password that is set less than 24 hours ago.
Choose network access:
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 (ACLs). You can select from 4 IP notation types: IP Address, CIDR Block, Virtual Cloud Network, Virtual Cloud Network OCID).
Choose a license type:
Bring Your Own License- Select when you have existing licenses.
License Included- Select when you want to subscribe to new database software licenses and the database cloud service.
The Create Autonomous Database dialog closes. On the console, the Lifecycle State field indicates that the database isProvisioning. When creation is completed, the Lifecycle State field changes toAvailable.Description of the illustration provisioning_state
자율 데이터베이스 콘솔이 표시됩니다. 목록 범위 드롭 다운 메뉴를 사용하여 구획을 선택할 수 있습니다. 이 예에서는 Doc 구획이 선택되었습니다. 구획 만들기에 대한 설명서를 보려면 여기를 클릭하십시오
자율 데이터베이스 콘솔이 표시됩니다. 목록 범위 드롭 다운 메뉴를 사용하여 구획을 선택할 수 있습니다. 이 예에서는 Doc 구획이 선택되었습니다. 구획 만들기에 대한 설명서를 보려면 여기를 클릭하십시오.
Download the Credentials Zip File
Once you have created the database, download the credentials zip file for client access to that database. You will use this file in the next step, and in the next tutorial to connect SQL Developer to your Autonomous Transaction Processing database.
The Database Connection dialog opens for downloading client credentials. For wallet type, selectInstance Wallet. Note: 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. ClickDownload Wallet. Description of the illustration database_connection_dialog
Store the zip file and make note of the password. You will use the zip file in the next step to define a SQL Developer connection to your Autonomous Transaction Processing database.
Define a SQL Developer Connection
Define a SQL Developer connection to the database in your Autonomous Transaction Processing service.
Open SQL Developer on your local computer. In the Connections panel, right-clickConnectionsand selectNew Connection. Note: Depending on your version of SQL Developer, donotright-clickCloud ConnectionorDatabase Schema Service Connections. That menu selection is for connecting to a different Oracle cloud service, the Oracle Database Schema Service. Description of the illustration select_new_connection
The New/Select Database Connection dialog appears. Enter the following information:
Connection Name - Enter the name for this cloud connection.
Username - Enter the database username. Use the default administrator database account (admin) that is provided as part of the service.
Password - Enter theadminuser's password that you or your Autonomous Transaction Processing administrator specified when creating the service instance.
Connection Type - SelectCloud Wallet.
Configuration File - ClickBrowse, and select theClient Credentialszip file, downloaded from the Autonomous Transaction Processing service console by you, or given to you by your Autonomous Transaction Processing administrator.
Service - In the drop-down menu, service selections are prepended with database names. Select the tpurgent, tp, high, medium, or low menu item for your database. These service levels map to the TPURGENT, TP, HIGH, MEDIUM and LOW consumer groups, which provide different levels of priority for your session. Note: Earlier versions of SQL Developer may not support this feature.
ClickTest. Status: Success displays at the left-most bottom of the New/Select Database Connection dialog.
ClickConnect. An entry for the new connection appears under Connections.
Create a User in your Autonomous Transaction Processing Database
Once you have connected SQL Developer to your Autonomous Transaction Processing database, use a SQL Developer worksheet to define acreate userstatement to create the useratpc_user. In the next tutorial, you will create sales history tables in theatpc_userschema and load data into these tables from an object store.
Open a SQL Developer worksheet and run the following SQL statements to create the useratpc_user, swapping in a password with the guidelines provided in the following Note section. create user atpc_user identified by "<password>"; grant dwrole to atpc_user;Description of the illustration sql_developer_commands_create_atpc_userNote: Autonomous Transaction Processing requires strong passwords. The password you specify must meet the default password complexity rules. This database checks for the following requirements when you create or modify passwords:
The password must be between 12 and 30 characters long and must include at least one uppercase letter, one lowercase letter, and one numeric character.
The password cannot contain the username.
The password cannot be one of the last four passwords used for the same username.
The password cannot contain the double quote (") character
Note: Autonomous Transaction Processing databases come with a pre-defined database role namedDWROLE. This role provides the common privileges for a database user:CREATE ANALYTIC VIEW, CREATE ATTRIBUTE DIMENSION, ALTER SESSION, CREATE HIERARCHY, CREATE JOB, CREATE MINING MODEL, CREATE PROCEDURE, CREATE SEQUENCE, CREATE SESSION, CREATE SYNONYM, CREATE TABLE, CREATE TRIGGER, CREATE TYPE, CREATE VIEW, READ,WRITE ONdirectoryDATA_PUMP_DIR, EXECUTEprivilege on the PL/SQL packageDBMS_CLOUD
In the next tutorial, "Connecting SQL Developer to Autonomous Transaction Processing", you will connect SQL Developer to your Autonomous Transaction Processing database as useratpc_user, and defineSHtables(sales history tables from an Oracle sample schema) for that user. Later, you will load data into those tables from an Object Store.
