잡학문구

Upload Data Files to Your Object Store

Upload to your cloud-based object store the data files that you want to load to your Autonomous Transaction Processing database. This tutorial uses an object store in the Oracle Cloud Infrastructure Object Storage service.

1. Log in to your Oracle Cloud Infrastructure Console with the following credentials provided by your Oracle Cloud administrator: cloud tenant, user name, password.

Description of the illustration log_in_to_oci_object_storage_with_username_password

1. Select Object Storage from the menu at the top left of the Oracle Cloud Infrastructure console. Select Object Storage from the sub-menu.

Description of the illustration select_object_storage

1. Select a compartment in which to create a bucket to upload your database table data.

Description of the illustration select_a_compartment

1. Click Create Bucket to create the storage bucket in which to upload your source files. You will later copy this staged data into tables in your Autonomous Transaction Processing database. 

Description of the illustration create_a_bucket

1. Enter a bucket name, select the standard storage tier, and click Create Bucket.

Description of the illustration create_a_bucket_dialog

1. Click Upload Object to begin selecting the data files to upload to the bucket.

Description of the illustration click_upload_object

1. Navigate to the location of the data files on your local computer. Drag and drop each file individually or click Upload Object to upload each file individually.
   This example uploads the data files of the SH tables (sales history tables from an Oracle sample schema). Click here to download a zip file of the 10 SH data files for you to upload to the object store. Unzip the data files from the zip file, because zip files cannot be uploaded. Upload each unzipped data file individually.
   Note: Alternatively, you can use curl commands to upload large numbers of files.

Description of the illustration upload_data_files_to_bucket

1. The data files are uploaded to the bucket. These files staged in the cloud are ready to be copied into the tables of your Autonomous Transaction Processing database. Remain logged in to Oracle Cloud Infrastructure Object Storage.

Description of the illustration uploaded_data_files_in_bucket

Create an Object Store Auth Token

To load data from an Oracle Cloud Infrastructure Object Storage object store, you need to create an Auth Token for your object store account. The communication between your Autonomous Transaction Processing database and the object store relies on the Auth Token and username/password authentication.

1. If you have logged out of Oracle Cloud Infrastructure Object Storage, log back in with the following credentials provided by your Oracle Cloud administrator: cloud tenant, user name, password.
2. Hover your mouse cursor over the human figure icon at the top right of the console and click User Settings from the drop-down menu.

Description of the illustration click_user_settings

1. Click Auth Tokens under Resources on the left of the console.

Description of the illustration click_auth_tokens

1. Click Generate Token.

Description of the illustration click_generate_token

1. A pop-up dialog appears. Set the Auth Token by performing the following steps:
1. In the pop-up dialog, enter a description.
2. Click the Generate Token button.
3. Copy the generated token to a text file. The token does not appear again.
4. Click Close.

Description of the illustration enter_descriptions_and_click_generate_token

Description of the illustration copy_the_generated_token

Create Object Store Credentials in your Autonomous Transaction Processing Schema

Now that you have created an object store Auth Token, store in your Autonomous Transaction Processing atpc_user schema the credentials of the object store in which your data is staged.

1. Open SQL Developer and connect to your Autonomous Transaction Processing database as user atpc_user. See the previous tutorial in this series, Connecting to SQL Developer and Creating Tables, for steps to connect SQL Developer to your Autonomous Transaction Processing database as atpc_user.
2. In a SQL Developer worksheet, use the create_credential procedure of the DBMS_CLOUD package to store the object store credentials in your atpc_user schema.
1. Create a credential name. You reference this credential name in the copy_data procedure in the next step.
2. Specify the credentials for your Oracle Cloud Infrastructure Object Storage service: The username and the object store Auth Token you generated in the previous step.
   
   begin
   DBMS_CLOUD.create_credential (
   credential_name => 'OBJ_STORE_CRED',
   username => '<your username>',
   password => '<your Auth Token>'
   ) ;
   end;
   /

Description of the illustration create_credential_in_adwc_schema

After you run this script, your object store's credentials are stored in your Autonomous Transaction Processing atpc_user schema.

Copy Data from Object Store to Autonomous Transaction Processing Database Tables

The copy_data procedure of the DBMS_CLOUD package requires that target tables must already exist in in your Autonomous Transaction Processing database. In the previous tutorial in this series, Connecting SQL Developer and Creating Tables, you created in your Autonomous Transaction Processing atpc_user schema all of the target tables. 

Now run the copy_data procedure to copy the data staged in your object store to your Autonomous Transaction Processing atpc_user tables. 

1. In a SQL Developer worksheet, use the copy_data procedure of the DBMS_CLOUD package to copy the data staged in your object store.
   • For credential_name, specify the name of the credential you defined in section 3, Create Object Store Credentials in your Autonomous Transaction Processing Schema. 
   • For file_uri_list, specify the URL that points to the location of the file staged in your object store. The URL is structured as follows. The values you specify are in bold:
     https://swiftobjectstorage.<region name>.oraclecloud.com/v1/<tenant name>/<bucket name>/<file name>
     
   • Click here for an example script. In the script, use your own table names, region name, tenant name, bucket name, and file names.
     Note: The region name, tenant name, and bucket name can all be found in one place by clicking the ellipsis option menu and going to file details.
     Note: If you receive an error message that your atpc_user does not have read/write privileges into the Object Store, you may need to properly set up your user privileges or contact your administrator to do so.
     

     

     Description of the illustration data_loading_script
     

ORA-20404: Object not found - https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/lgcnscorp/tutorial_load_atpc/ 
ORA-06512: "C##CLOUD$SERVICE.DBMS_CLOUD",  757행 
ORA-06512: "C##CLOUD$SERVICE.DBMS_CLOUD",  1879행 
ORA-06512:  1행 

1. After you run the procedure, observe that the data has been copied from the object store to the tables in your Autonomous Transaction Processing database.
   

   

   Description of the illustration result_of_loading_table

All data load operations done using the PL/SQL package DBMS_CLOUD are logged in the tables dba_load_operations and user_load_operations. These tables contain the following:

• dba_load_operations: shows all load operations.
• user_load_operations: shows the load operations in your schema.

1. Query these tables to see information about ongoing and completed data loads. For example:
   SELECT table_name, owner_name, type, status, start_time, update_time, logfile_table, badfile_table FROM user_load_operations WHERE type = 'COPY';
2. Examine the results. The log and bad files are accessible as tables:
   TABLE_NAME STATUS ROWS_LOADED LOGFILE_TABLE   BADFILE_TABLE
   ---------- ------------ ----------- -------------   -------------
   CHANNELS FAILED COPY$1_LOG      COPY$1_BAD
   CHANNELS COMPLETED 5   COPY$2_LOG COPY$2_BAD

Next Tutorial 

Using Oracle Machine Learning with Autonomous Data Warehouse Cloud ServiceUsing Oracle Machine Learning with Autonomous Data Warehouse Cloud Service

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 a create user statement to create the user atpc_user. In the next tutorial, you will create sales history tables in the atpc_user schema and load data into these tables from an object store.

1. Open a SQL Developer worksheet and run the following SQL statements to create the user atpc_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;
2. 
   
   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 named DWROLE.
   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 ON directory DATA_PUMP_DIR, EXECUTE privilege on the PL/SQL package DBMS_CLOUD  
   
   



3. In the next tutorial, "Connecting SQL Developer to Autonomous Transaction Processing", you will connect SQL Developer to your Autonomous Transaction Processing database as user atpc_user, and define SH tables(sales history tables from an Oracle sample schema) for that user. Later, you will load data into those tables from an Object Store.

Create SH Tables in your Autonomous Transaction Processing Database

After you have connected SQL Developer to your Autonomous Transaction Processing database, use a SQL Developer worksheet to define CREATE TABLE statements to create the SH tables (sales history tables from an Oracle sample schema) in the atpc_user schema. In the next tutorial, you will load data into these tables from an object store.  

1. Copy and paste this code snippet to a SQL Developer worksheet.worksheet. Run the script to create the SH tables.

   

   Description of the illustration sql script to create sh tables

Examine the SH Tables that you Created

Now that you have created the SH tables, take a moment to examine them. In the next tutorial, you will load data into these tables from an object store.

1. Note that the new tables also appear in the SQL Developer Connections panel. 

   

   Description of the illustration list of new tables in atpc_user  
2. Examine the details of each column of the CHANNELS table.
   

   

   Description of the illustration details of the CHANNELS table
   
3. Click the Data tab of the CHANNELS table. Note that so far, you have defined tables, but these tables are not yet populated with Data.
   

   

   Description of the illustration no data yet in CHANNELS table
   
4. In the next tutorial, "Loading Your Data", you will load data from an object store into these SH tables.

Next Tutorial

Loading Your Data to Autonomous Transaction Processing  

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.

1. In the console, in the details page of your new Autonomous Transaction Processing database, select DB Connection.
   

   

   Description of the illustration open_service_console
2. The Database Connection dialog opens for downloading client credentials. For wallet type, select Instance 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.
   Click Download Wallet.
   

   

   Description of the illustration database_connection_dialog
3. In the Download Wallet dialog, enter an encryption password for the wallet, confirm the password, and then click Download.
   

   

   Description of the illustration download_wallet
4. Click Save File, and then click OK.
5. 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.

1. Open SQL Developer on your local computer. In the Connections panel, right-click Connections and select New Connection.
   Note:
   Depending on your version of SQL Developer, do not right-click Cloud Connection or Database 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
2. 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 the admin user's password that you or your Autonomous Transaction Processing administrator specified when creating the service instance.
• Connection Type - Select Cloud Wallet.
• Configuration File - Click Browse, and select the Client Credentials zip 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.  

Description of the illustration new_select_database_connection_dialog

1. Click Test.
   Status: Success displays at the left-most bottom of the New/Select Database Connection dialog.
2. Click Connect.
   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 a create user statement to create the user atpc_user. In the next tutorial, you will create sales history tables in the atpc_user schema and load data into these tables from an object store.

1. Open a SQL Developer worksheet and run the following SQL statements to create the user atpc_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;

2. 

    

   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 named DWROLE.
   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 ON directory DATA_PUMP_DIR, EXECUTE privilege on the PL/SQL package DBMS_CLOUD  
   
   
3. In the next tutorial, "Connecting SQL Developer to Autonomous Transaction Processing", you will connect SQL Developer to your Autonomous Transaction Processing database as user atpc_user, and define SH tables(sales history tables from an Oracle sample schema) for that user. Later, you will load data into those tables from an Object Store.

Next Tutorial

Connecting SQL Developer to Autonomous Transaction Processing

인스턴스 생성

오라클 클라우드에 Sign in 하고 인스턴스 생성하기.

1. 오라클 클라우드 접속(https://oracle.com) 후 우측 상단의  View Accounts 클릭 후 Sign in to Cloud 클릭.
2. Oracle Cloud 계정 입력 후 Next 클릭
   

   

   Description of the illustration cloud_login
3. 사용자이름과 패스워드 입력 후 Sign In 클릭
   

   

   Description of the illustration cloud sign in
4. Oracle Cloud page에서 왼쪽 상단의 navigation menu 클릭(일명 햄버거 메뉴).
   

   

   Description of the illustration cloud console
5. Autonomous Transaction Processing 클릭.
   

   

   Description of the illustration console navigation
6. The console for Autonomous Database displays. You can use the List Scope drop-down menu to select a compartment; in this example the Doc compartment is selected. Click here for documentation on creating compartments.ㄹㅇㄴㅁㄹ
7. 
   This console shows no databases. If there were a long list of databases, you could filter the list by using the Filters drop-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.
   Click Create Autonomous Database to create a database instance.

   

   Description of the illustration create_autonomous_transaction_processing_database
8. 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, choose Transaction Processing as 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:

   • Password and Confirm 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.
   
   
   Click
    Create Autonomous Database
   

   

   Description of the illustration create_dialog_finish_top

   

   Description of the illustration create_dialog_finish
9. The Create Autonomous Database dialog closes. On the console, the Lifecycle State field indicates that the database is Provisioning. When creation is completed, the Lifecycle State field changes to Available.

   

   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.

1. In the console, in the details page of your new Autonomous Transaction Processing database, select DB Connection.
   

   

   Description of the illustration open_service_console
2. The Database Connection dialog opens for downloading client credentials. For wallet type, select Instance 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.
   Click Download Wallet.
   

   

   Description of the illustration database_connection_dialog
3. In the Download Wallet dialog, enter an encryption password for the wallet, confirm the password, and then click Download.
   

   

   Description of the illustration download_wallet
4. Click Save File, and then click OK.
5. 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.

1. Open SQL Developer on your local computer. In the Connections panel, right-click Connections and select New Connection.
   Note:
   Depending on your version of SQL Developer, do not right-click Cloud Connection or Database 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
2. 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 the admin user's password that you or your Autonomous Transaction Processing administrator specified when creating the service instance.
• Connection Type - Select Cloud Wallet.
• Configuration File - Click Browse, and select the Client Credentials zip 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.  

Description of the illustration new_select_database_connection_dialog

1. Click Test.
   Status: Success displays at the left-most bottom of the New/Select Database Connection dialog.
2. Click Connect.
   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 a create user statement to create the user atpc_user. In the next tutorial, you will create sales history tables in the atpc_user schema and load data into these tables from an object store.

1. Open a SQL Developer worksheet and run the following SQL statements to create the user atpc_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 named DWROLE.
   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 ON directory DATA_PUMP_DIR, EXECUTE privilege on the PL/SQL package DBMS_CLOUD  
   
   
2. In the next tutorial, "Connecting SQL Developer to Autonomous Transaction Processing", you will connect SQL Developer to your Autonomous Transaction Processing database as user atpc_user, and define SH tables(sales history tables from an Oracle sample schema) for that user. Later, you will load data into those tables from an Object Store.

Next Tutorial

Connecting SQL Developer to Autonomous Transaction Processing

Create an Instance

Sign in to Autonomous Transaction Processing and create an instance.

1. Sign in from https://cloud.oracle.com/home. On the Oracle Cloud page, click Sign In.
2. On the Cloud Account page, enter your cloud account name and click Next.
   

   

   Description of the illustration cloud_login
3. Enter your User Name and Password and click Sign In to sign in to your Oracle Cloud Account
   

   

   Description of the illustration cloud sign in
4. On the Oracle Cloud Infrastructure page, click the navigation menu in the upper left to show top level navigation choices.
   

   

   Description of the illustration cloud console
5. Click Autonomous Transaction Processing.
   

   

   Description of the illustration console navigation
6. The console for Autonomous Database displays. You can use the List Scope drop-down menu to select a compartment; in this example the Doc compartment is selected. Click here for documentation on creating compartments.
   This console shows no databases. If there were a long list of databases, you could filter the list by using the Filters drop-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.
   Click Create Autonomous Database to create a database instance.

   

   Description of the illustration create_autonomous_transaction_processing_database
7. 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, choose Transaction Processing as 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:

   • Password and Confirm 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.
   
   
   Click
    Create Autonomous Database
   

   

   Description of the illustration create_dialog_finish_top

   

   Description of the illustration create_dialog_finish
8. The Create Autonomous Database dialog closes. On the console, the Lifecycle State field indicates that the database is Provisioning. When creation is completed, the Lifecycle State field changes to Available.

   

   Description of the illustration provisioning_state

Next Tutorial

Connecting SQL Developer to Autonomous Transaction Processing