You can access Database Actions from Autonomous Database. Database Actions provides development tools, data tools, administration, and monitoring features for Autonomous Database. Using Database Actions you can run SQL statements, queries, and scripts in a worksheet.
About Database Actions (SQL Developer Web)
Database Actions provides a web-based interface with development, data tools, administration, monitoring, and download features for Autonomous Database.
The following table lists the main features of Database Actions. Database Actions on your Autonomous Database instance may include additional cards if you download applications from Oracle Cloud Marketplace.
|Feature Area||Database Actions Cards|
SQL, Data Modeler, REST, JSON, Charts, Scheduling, Oracle Machine Learning, Graph Studio, and Oracle APEX
Data Load, Catalog, Data Insights, Data Transforms, and Data Analysis
Database Users, APEX Workspaces, Data Pump, Download Client Credentials, and Set Resource Management Rules
Performance Hub and Database Dashboard
Download Oracle Instant Client and Download SODA Drivers
Restful Data Services (ORDS) and SODA and Access Oracle Machine Learning Restful Services
See About Database Actions in Using Oracle Database Actions for more information.
Access Database Actions as ADMIN
Database Actions (also known as SQL Developer Web) is bundled with each Autonomous Database instance.
Database Actions runs in Oracle REST Data Services and access is provided through schema-based authentication. To use Database Actions, you must sign in as a database user whose schema is enabled for Database Actions. By default the ADMIN user is enabled to access Database Actions.
See Provide Database Actions Access to Database Users to enable another database user's schema to access Database Actions.
Note:If your Autonomous Database is configured to use a Private Endpoint, then you can only access Database Actions from clients in the same Virtual Cloud Network (VCN).
See Configuring Network Access with Private Endpoints for more information.
To access Database Actions from the Oracle Cloud Infrastructure Console:
- On the Autonomous Database Details page click the Database actions dropdown list.
- Select a quick link to go directly to a quick link action or select
View all database actions to access the full Database
For example, click SQL to use a SQL Worksheet. On the SQL Worksheet you can use the Consumer Group drop-down list to select the consumer group to run your SQL or PL/SQL code. See Executing SQL Statements in the Worksheet Editor for more information.
Depending on your browser, if the Console cannot access the database as ADMIN you will be prompted for your database ADMIN username and password.
Description of the illustration adb_database_actions_signin.png
Provide Database Actions Access to Database Users
The ADMIN user provides access to Database Actions for other database users.
Database users who are not service administrators do not have access to the Oracle Cloud Infrastructure Console. The ADMIN user provides access to Database Actions as follows:
Use Database Actions to create a user and assign roles to the user. If the user already exists, check that Web Access is selected for the schema (with Web Access selected, the user's card shows REST Enabled).
See Create Users on Autonomous Database for information on adding database users.
See Required Roles to Access Tools from Database Actions for information on required roles for Database Actions.
Provide the user with a URL to access Database Actions.
After adding a user and selecting Web Access, the ADMIN provides a user with the URL to access Database Actions:
- In Database Actions, click to show the available actions.
- Under Administration select Database
This displays information about users, such as user names, whether a user is REST Enabled, and the last login date and time. On a user's card, the icon on the left displays the user status with one of the following colors: green (Open), blue (Locked), or red (Expired).
The default view is Card View. You can select either grid view or card view by clicking the Card View or Grid View icons.
- A URL is displayed in the user's card only if the user is REST Enabled. It provides the URL to access Database Actions. Click to copy the URL to the clipboard.
- Provide the user with the URL you copied.
After you provide the URL to a user, to access Database Actions the user pastes the URL into their browser and then enters their Username and Password in the Sign-in dialog.
See Manage Users and User Roles on Autonomous Database - Connecting with Database Actions for more information.
Required Roles to Access Tools from Database Actions
Lists the database roles required to use the built-in Autonomous Database tools.
When you connect to Database Actions as the ADMIN user, many database roles are set to allow you to access the available Autonomous Database tools. When you connect to Database Actions as a non-ADMIN user, some of the Database Actions cards for Autonomous Database tools are hidden if you do not have required permissions.
As the ADMIN user, set the appropriate roles to allow user access to Autonomous Database tools. See Manage User Roles and Privileges on Autonomous Database for more information.
|Autonomous Database Tool||Required Role||More Information|
|Oracle Machine Learning (OML)||
||Oracle Machine Learning|
||Using Oracle Graph with Autonomous Database|
|Data Studio (including: Catalog, Data Load, Data Analysis, Data Insights)||
Access Database Actions, Oracle APEX, Oracle REST Data Services, and Developer Tools Using a Vanity URL
By default you access Oracle APEX apps, REST endpoints, and developer tools on Autonomous Database using the
oraclecloudapps.com domain name.
You can optionally configure a vanity URL or custom domain name that is easy to remember to
help promote your brand identity.
After you acquire a desired domain name and matching SSL certificate from a vendor of your choice, deploy an Oracle Cloud Infrastructure Load Balancer in your Virtual Cloud Network (VCN) using your Autonomous Database as the backend. Your Autonomous Database instance must be configured with a private endpoint in the same VCN. See Configuring Network Access with Private Endpoints for more information.
To learn more, see the following: