Oracle Autonomous Database Professional key terms

A fully managed Oracle Cloud Database that automatically provisions, patches, tunes, scales, and secures itself, requiring minimal manual administration from the user.

A consumption-based Autonomous Database model where Oracle manages all infrastructure and the customer pays only for the compute and storage actually used.

An Autonomous Database model hosted on Exadata infrastructure isolated to a single customer, offering stronger isolation and control over patching schedules.

The underlying Oracle Exadata hardware and software stack that provides the compute, storage, and networking resources for Autonomous Database deployments.

A container database on dedicated Exadata infrastructure that hosts one or more Autonomous Databases, managing their shared resources and lifecycle operations.

A setting chosen at creation that configures the database for a specific use case, such as Transaction Processing, Data Warehouse, JSON, or APEX, affecting defaults and optimizations.

An Autonomous Database workload type tuned for high-concurrency, mixed transactional and reporting workloads, using indexing and caching optimized for OLTP.

An Autonomous Database workload type optimized for analytical queries and bulk data loading, using columnar processing, parallel execution, and automatic partitioning.

A feature that automatically increases compute resources when demand rises and releases them when demand falls, without manual intervention, up to a defined limit.

Oracle CPU, the unit used to size compute resources for Autonomous Database, where one OCPU equals one physical core or two hyperthreads of compute capacity.

Elastic Compute Processing Unit, a newer sizing metric for Autonomous Database that measures compute capacity more flexibly than OCPU for some workload types.

A shared pool of compute resources within a Dedicated Deployment from which multiple Autonomous Container Databases draw capacity dynamically.

A no-cost Autonomous Database offering with limited compute and storage that never expires, suitable for learning, prototyping, and small applications.

The process of creating an Autonomous Database instance by specifying a workload type, compute size, storage, credentials, and network access settings.

Constraints applied to an Autonomous Database instance that cap compute, storage, or session consumption, used to control cost and contention.

The credential for the ADMIN database user, set at provisioning time and required to manage users, privileges, and objects inside the database.

A downloadable zip file containing connection credentials, including a client credential file and network settings, used to securely connect applications to an Autonomous Database.

A two-way authentication scheme where both client and server present certificates, commonly required for secure connections to Autonomous Database using a wallet.

An encrypted connection option for Autonomous Database that can use server-side authentication without a wallet, often combined with a network access control list.

A network security setting that restricts which IP addresses or CIDR ranges may connect to an Autonomous Database instance.

A network configuration that exposes an Autonomous Database only on a private subnet within a customer VCN, preventing access from the public internet.

A configuration that identifies how a client reaches an Autonomous Database, defined by a service name, host, port, and protocol such as TCPS.

A logical identifier used in a connect descriptor to route a client session to a particular database service, such as one tuned for high or low concurrency.

The text form of a connect descriptor that tells a client application where and how to connect to an Autonomous Database instance.

A browser-based SQL and database development tool built into Autonomous Database, offering worksheets, object browsing, and query execution without installing client software.

A suite of web-based tools bundled with Autonomous Database for SQL, data loading, modeling, monitoring, and administration tasks.

A monitoring interface that shows real-time and historical performance data for an Autonomous Database, including active sessions, wait events, and SQL statistics.

A built-in repository that periodically captures performance statistics and snapshots, used to analyze trends and compare database behavior over time.

A real-time diagnostic feature that tracks execution progress and resource usage of long-running SQL statements, showing plans and wait activity.

A feature that monitors workload patterns and automatically creates, validates, and removes indexes that improve query performance, without user action.

A tool that analyzes SQL statements and recommends improvements such as indexes, statistics refreshes, or plan changes to reduce execution time.

The browser-based dashboard in Database Actions that displays CPU, storage, session, and alert information for an Autonomous Database instance.

An Oracle export and import utility used to move schemas and data into Autonomous Database, supporting dump files stored in object storage.

A cloud storage service used as a staging location for dump files, credential access, and data loading operations into Autonomous Database.

A stored authentication object in the database that holds the username and password needed to access cloud object storage during data loading or export.

A Database Actions tool that guides users through loading files such as CSV or JSON from local storage or cloud storage into tables.

A database object that reads data stored outside the database, such as files in object storage, without first loading it into a table.

An Oracle replication product used to migrate and continuously synchronize data from source databases into Autonomous Database with minimal downtime.

An Oracle migration service that orchestrates moving databases to Autonomous Database with minimal outage using tools such as Data Pump and GoldenGate.