Hubbry Logo
Oracle DatabaseOracle DatabaseMain
Open search
Oracle Database
Community hub
Oracle Database
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Oracle Database
Oracle Database
Oracle Database
View on Wikipedia
from Wikipedia

Oracle Database
DeveloperOracle Corporation
Initial release1979; 46 years ago (1979)
Stable release
23ai[1] Edit this on Wikidata / 19 September 2023; 2 years ago (19 September 2023)
Written inAssembly language, C, C++[2]
TypeMulti-model database
LicenseProprietary[3]
Websitewww.oracle.com/database/

Oracle Database (commonly referred to as Oracle DBMS, Oracle Autonomous Database, or simply as Oracle) is a proprietary multi-model[4] database management system produced and marketed by Oracle Corporation.

It is a database commonly used for running online transaction processing (OLTP), data warehousing (DW) and mixed (OLTP & DW) database workloads. Oracle Database is available by several service providers on-premises, on-cloud, or as a hybrid cloud installation. It may be run on third party servers as well as on Oracle hardware (Exadata on-premises, on Oracle Cloud or at Cloud at Customer).[5]

Oracle Database uses SQL for database updating and retrieval.[6]

History

[edit]

Larry Ellison and his two friends and former co-workers, Bob Miner and Ed Oates, started a consultancy called Software Development Laboratories (SDL) in 1977, later Oracle Corporation. SDL developed the original version of the Oracle software. The name Oracle comes from the code-name of a Central Intelligence Agency-funded project Ellison had worked on while formerly employed by Ampex;[7] the CIA was Oracle's first customer, and allowed the company to use the code name for the new product.[8]

Ellison wanted his database to be compatible with IBM System R, but that company's Don Chamberlin declined to release its error codes.[9] By 1985 Oracle advertised, however, that "Programs written for SQL/DS or DB2 will run unmodified" on the many non-IBM mainframes, minicomputers, and microcomputers its database supported "Because all versions of ORACLE are identical".[10]

Releases and versions

[edit]

Oracle products follow a custom release-numbering and -naming convention. The "ai" in the current release, Oracle Database 23ai, stands for "Artificial Intelligence". Previous releases (e.g. Oracle Database 19c, 10g, and Oracle9i Database) have used suffixes of "c", "g", and "i" which stand for "Cloud", "Grid", and "Internet" respectively. Prior to the release of Oracle8i Database, no suffixes featured in Oracle Database naming conventions. There was no v1 of Oracle Database, as Ellison "knew no one would want to buy version 1".[11][9] For some database releases, Oracle also provides an Express Edition (XE) that is free to use.[12][13]

Oracle Database release numbering has used the following codes:

Legend:
Unsupported
Supported
Latest version
LTR = Long-Term Release, IR = Innovation Release
Oracle
Database
Version 		Initial
Release
Version 		Initial
Release
Date 		Terminal
Version 		Marquee
Features
Latest version: Oracle Database 23ai (LTR) 23.4.0 On May 2, 2024, Oracle Database 23ai[14] was released on Oracle Cloud Infrastructure (OCI) as cloud services, including OCI Exadata Database Service, OCI Exadata Database Cloud@Customer, and OCI Base Database Service. It is also available in Always Free Autonomous Database. Oracle Database 23c (previously released in 2023) was renamed to Oracle Database 23ai (23.4) due to the significant additional engineering effort to add features that bring AI capabilities to the data in Oracle Database.

Oracle Database 23c (23.2 and 23.3) was released in 2023: April 2023 (Linux) Oracle Database Free - Developer Release[15] September 2023 Oracle Database on Base Database Service[16]

AI Vector Search[17] (includes new Vector data type, Vector indexes, and Vector SQL operators/functions), JSON Relational Duality,[18] JSON Schema Validation, Transactional Microservices Support, OKafka, Operational Property Graphs, Support for SQL/PGQ, Schema Privileges, Developer Role, In-database SQL Firewall, TLS 1.3 Support, Integration with Azure Active Directory OAuth2, True Cache for mid-tier caching, Readable Per-PDB Standby, Globally Distributed Database with active-active RAFT-based replication, Real-time SQL Plan Management, Priority Transactions, SQL Syntax Simplification, Schema Annotations, Data Use Case Domains, Column Value Lock-free Reservations
Supported: Oracle Database 21c (IR) 21.1.0 December 2020 (cloud)[19]

August 2021 (Linux)[20]

Blockchain Tables, Multilingual Engine - JavaScript Execution in the Database, Binary JSON Data Type, Per-PDB Data Guard Physical Standby (aka Multitenant Data Guard), Per-PDB GoldenGate Change Capture, Self-Managing In-Memory, In-Memory Hybrid Columnar Scan, In-Memory Vector Joins with SIMD, Sharding Advisor Tool, Property Graph Visualization Studio, Automatic Materialized Views, Automatic Zone Maps, SQL Macros, Gradual Password Rollover
Supported: Oracle Database 19c (LTR) 19.1.0 // 12.2.0.3 February 2019 (Exadata)[21]

April 2019 (Linux)[22]
June 2019 (cloud)

Active Data Guard DML Redirection, Automatic Index Creation, Real-Time Statistics Maintenance, SQL Queries on Object Stores, In-Memory for IoT Data Streams, Hybrid Partitioned Tables, Automatic SQL Plan Management, SQL Quarantine, Zero-Downtime Grid Infrastructure Patching, Finer-Granularity Supplemental Logging, Automated PDB Relocation
Unsupported: Oracle Database 18c (IR) 18.1.0 // 12.2.0.2 February 2018 (cloud, Exadata)[23]

July 2018 (other)[24]

18.17.0
January 2022 		Polymorphic Table Functions, Active Directory Integration, Transparent Application Continuity, Approximate Top-N Query Processing, PDB Snapshot Carousel, Online Merging of Partitions and Subpartitions
Unsupported: Oracle Database 12c Release 2 12.2.0.1
March 2017 		August 2016 (cloud)

March 2017 (on-premises)

12.2.0.1
March 2017 		Native Sharding, Zero Data Loss Recovery Appliance, Exadata Cloud Service, Cloud at Customer
Unsupported: Oracle Database 12c Release 1 12.1.0.1 July 2013[25] 12.1.0.2
July 2014 		Multitenant architecture, In-Memory Column Store, Native JSON, SQL Pattern Matching, Database Cloud Service
Unsupported: Oracle Database 11g Release 2 11.2.0.1 September 2009[26] 11.2.0.4
August 2013 		Edition-Based Redefinition, Data Redaction, Hybrid Columnar Compression, Cluster File System, Golden Gate Replication, Database Appliance
Unsupported: Oracle Database 11g Release 1 11.1.0.6 September 2007 11.1.0.7
September 2008 		Active Data Guard, Secure Files, Exadata
Unsupported: Oracle Database 10g Release 2 10.2.0.1 July 2005[27] 10.2.0.5
April 2010 		Real Application Testing, Database Vault, Online Indexing, Advanced Compression, Data Guard Fast-Start Failover, Transparent Data Encryption
Unsupported: Oracle Database 10g Release 1 10.1.0.2 2003 10.1.0.5
February 2006 		Automated Database Management, Automatic Database Diagnostic Monitor, Grid infrastructure, Oracle ASM, Flashback Database
Unsupported: Oracle9i Database Release 2 9.2.0.1 2002 9.2.0.8
April 2007 		Advanced Queuing, Data Mining, Streams, Logical Standby
Unsupported: Oracle9i Database 9.0.1.0 2001 9.0.1.5
December 2003 		Oracle Real Application Clusters (RAC), Oracle XML DB
Unsupported: Oracle8i Database 8.1.5.0 1998 8.1.7.4
August 2000 		Native internet protocols and Java, Virtual Private Database
Unsupported: Oracle8 Database 8.0.3 June 1997 8.0.6 Recovery Manager, Partitioning. First version available for Linux.[28]
Unsupported: Oracle 7.3 7.3.0 February 1996 7.3.4 Object-relational database
Unsupported: Oracle 7.2 7.2.0 May 1995 Shared Server, XA Transactions, Transparent Application Failover
Unsupported: Oracle 7.1 7.1.0 May 1994 Parallel SQL Execution. First version available for Windows NT.[29]
Unsupported: Oracle7 7.0.12 June 1992 Distributed 2-phase commit,[8] PL/SQL stored procedures, triggers, shared cursors, cost-based optimizer
Unsupported: Oracle 6.2 6.2.0 Oracle Parallel Server
Unsupported: Oracle v6 6.0.17 1988 6.0.37 Row-level locking, SMP scalability / performance, storing of undo in database,[8] online backup and recovery, B*Tree indexes, PL/SQL executed from compiled programs (C etc.). First version available for Novell Netware 386.[30]
Unsupported: Oracle v5 5.0.22 (5.1.17) 1985 5.1.22 C2 security certification. Support for distributed database systems[8] and client/server computing. First version available for OS/2. Correlated sub-queries.[31] DOS version supports extended memory.[8]
Unsupported: Oracle v4 4.1.4.0 1984 4.1.4.4 Multiversion read consistency. Halloween Problem solved. Improved concurrency.[8] First version available for MS-DOS[32][33] and IBM mainframe.[8]
Unsupported: Oracle v3 3.1.3 1983 Concurrency control, data distribution, and scalability. Re-written in C for portability to other operating systems, including UNIX.[34][8]
Unsupported: Oracle v2 2.3 1979 First commercially available SQL RDBMS. Basic SQL queries, simple joins[35] and CONNECT BY joins. Atomic role-level SQL statements. Rudimentary concurrency control and database integrity. No query optimizer. Written in assembly language for the PDP-11[8] to run in 128KB of RAM.[36] Ran on PDP-11 and VAX/VMS in PDP-11 compatibility mode.[8]
Legend:
Unsupported
Supported
Latest version
LTR = Long-Term Release, IR = Innovation Release

The Introduction to Oracle Database includes a brief history on some of the key innovations introduced with each major release of Oracle Database.

See My Oracle Support (MOS) note Release Schedule of Current Database Releases (Doc ID 742060.1) for the current Oracle Database releases and their patching end dates.

Patch updates and security alerts

[edit]

Prior to Oracle Database 18c, Oracle Corporation released Critical Patch Updates (CPUs) and Security Patch Updates (SPUs)[37] and Security Alerts to close security vulnerabilities. These releases are issued quarterly; some of these releases have updates issued prior to the next quarterly release.

Starting with Oracle Database 18c, Oracle Corporation releases Release Updates (RUs) and Release Update Revisions (RURs).[38] RUs usually contain security, regression (bug), optimizer, and functional fixes which may include feature extensions as well. RURs include all fixes from their corresponding RU but only add new security and regression fixes. However, no new optimizer or functional fixes are included.

Competition

[edit]

In the market for relational databases, Oracle Database competes against commercial products such as IBM Db2 and Microsoft SQL Server.[13] Oracle and IBM tend to battle for the mid-range database market on Unix and Linux platforms, while Microsoft dominates the mid-range database market on Microsoft Windows platforms. However, since they share many of the same customers, Oracle and IBM tend to support each other's products in many middleware and application categories (for example: WebSphere, PeopleSoft, and Siebel Systems CRM), and IBM's hardware divisions work closely[citation needed] with Oracle on performance-optimizing server-technologies (for example, Linux on IBM Z). Niche commercial competitors include Teradata (in data warehousing and business intelligence), Software AG's ADABAS, Sybase, and IBM's Informix, among many others.

In the cloud, Oracle Database competes against the database services of AWS, Microsoft Azure, and Google Cloud Platform.

Increasingly, the Oracle database products compete against open-source software relational and non-relational database systems such as PostgreSQL, MongoDB, Couchbase, Neo4j, ArangoDB and others. Oracle acquired Innobase, supplier of the InnoDB codebase to MySQL, in part to compete better against open source alternatives, and acquired Sun Microsystems, owner of MySQL, in 2010. Database products licensed as open-source are, by the legal terms of the Open Source Definition, free to distribute and free of royalty or other licensing fees.

Reception

[edit]

The Rosen Electronics Letter in February 1983 stated that Oracle was "the most comprehensive offering we've seen" among databases, with good marketing and substantial installed base encouraging developers to write software for it. The newsletter especially approved of the user interface, noting the "simplicity of setting up 'programs'—queries, data manipulation, updates—without actually programming".[39]

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Oracle Database

View on Grokipedia
from Grokipedia
Oracle Database is a , management system (DBMS) produced and marketed by , functioning primarily as an object-relational database management system (ORDBMS) that stores, manages, and retrieves structured and in a multiuser environment. It supports the Structured Query Language (SQL) as its standard interface for data manipulation, while also accommodating procedural extensions like , , and APIs such as OCI and JDBC for advanced application development. Designed for enterprise-scale operations, Oracle Database ensures concurrent access, transaction integrity through compliance, high performance via optimized indexing and partitioning, and robust recovery mechanisms using redo logs and control files to maintain data consistency even in the event of failures. Developed originally in 1977 by Larry Ellison, Bob Miner, and Ed Oates as part of Relational Software, Inc. (later renamed Oracle Systems Corporation in 1982), Oracle Database pioneered the commercial implementation of relational database technology based on Edgar F. Codd's 1970 model. The first version, Oracle V2, released in 1979, was the world's first commercially available SQL-based relational DBMS, running on a Digital Equipment Corporation PDP-11 minicomputer and marking a significant milestone in database history by enabling portable, multiplatform data management. Subsequent innovations included client/server architecture in 1985, distributed database support in the 1980s, and Real Application Clusters (RAC) in 2001 for high availability across clustered environments. Over its evolution, Oracle Database has incorporated object-oriented features in the , XML and web services support in the , and cloud-native capabilities with the launch of Oracle Database Cloud Service in 2013 and Autonomous Database in 2018, which automates provisioning, tuning, and scaling using . The current long-term support release, AI Database 26ai (introduced in 2025), builds on this legacy with over 300 enhancements focused on integration, including AI Vector Search for semantic querying of embeddings, Relational Duality for hybrid relational-NoSQL development, and automated optimizations for resource estimation and query performance to boost developer productivity and enable trusted AI insights across on-premises, cloud, and hybrid deployments. With editions ranging from the free Oracle Database 26ai Free for developers to enterprise-grade options like Enterprise Edition and Exadata, it powers mission-critical applications in sectors such as , healthcare, and , maintaining its position as a market leader in database technology.

Overview

Definition and Core Functionality

Oracle Database is a proprietary multi-model database management system (DBMS) produced and marketed by , functioning primarily as an object-relational database management system (ORDBMS). It serves as a comprehensive platform for storing, managing, and retrieving structured and unstructured data, primarily organized in relational tables, enabling efficient for enterprise applications. It supports multiple data models, including relational, object-relational, for document-oriented storage, and spatial data, enabling versatile data handling. The system leverages Structured Query Language (SQL) as its primary interface for interacting with data, allowing users to perform queries, updates, and administrative tasks across large-scale datasets. At its core, Oracle Database supports essential operations through SQL sublanguages: Data Definition Language (DDL) for creating, altering, and dropping database structures like tables and indexes; Data Manipulation Language (DML) for inserting, updating, deleting, and selecting data; and Data Control Language (DCL) for managing user permissions and access rights. It also provides robust transaction processing that adheres to ACID properties—ensuring atomicity (all-or-nothing execution), consistency (data integrity maintenance), isolation (concurrent transaction independence), and durability (permanent changes post-commit)—which are critical for reliable data handling in multi-user environments. Key basic components include tables, which store data in rows and columns as the fundamental units of relational organization; schemas, which group related database objects such as tables and views owned by a specific user; users, who represent accounts with credentials for accessing the database; and sessions, which establish a connection between a user and the database instance for executing operations. Oracle Database's implementation draws from the pioneered by E. F. Codd in his paper "A Relational Model of Data for Large Shared Data Banks," which introduced data representation via relations (tables) based on mathematical relations to eliminate and ensure logical consistency. Oracle adopted and commercialized this model, incorporating Codd's principles of normalization and declarative querying to support scalable, integrity-focused .

Market Position and Usage

Oracle Database maintains a dominant position in the relational database management system (RDBMS) market, consistently ranked as the most popular DBMS by the , where it has held the top spot throughout 2025 with a score significantly ahead of competitors like and . This leadership is particularly pronounced in enterprise segments, where is recognized as a Leader in the 2024 for Cloud Database Management Systems, evaluated for its completeness of vision and ability to execute in cloud environments. The system's prevalence stems from its reliability for mission-critical applications, powering data-intensive operations across large-scale organizations. It is widely adopted in key industries such as , where banks rely on it for high-volume and ; healthcare, for managing patient records and operational ; , to handle secure and applications; and , supporting scalable transaction platforms and inventory management. These sectors value Oracle Database's , features, and in handling complex, high-stakes workloads that demand minimal downtime and robust . Oracle Database integrates effectively with enterprise ecosystems, including ERP systems like for streamlined order management and financial synchronization; CRM platforms such as for real-time customer data sharing; and big data tools like Hadoop for processing large-scale analytics through connectors and data flows. Deployment options span on-premises installations for legacy environments, hybrid configurations combining local and resources, and full cloud migrations via Oracle Cloud Infrastructure, enabling flexible scaling for diverse organizational needs. Notably, approximately 98% of Fortune 500 companies utilize some form of Oracle's integrated cloud, database, and enterprise software, underscoring its entrenched role in global enterprise infrastructure.

History

Origins and Early Development

In 1977, Larry Ellison, Bob Miner, and Ed Oates founded Software Development Laboratories (SDL) in Santa Clara, California, with the goal of creating a commercial relational database management system (RDBMS). The company's inspiration stemmed from IBM's System R project, an experimental RDBMS that implemented Edgar F. Codd's relational model and introduced Structured Query Language (SQL) as its query interface; Ellison had learned of these developments through published papers and sought to build a portable commercial version. Initially funded by $2,000 of their own money and a $50,000 contract from the CIA—codenamed Project Oracle—the startup focused on developing software that could handle relational data without tying it to specific hardware. By 1979, SDL had renamed itself Relational Software, Inc. (RSI) and released Version 2, skipping Version 1 to suggest maturity; this marked the first commercially available SQL-based RDBMS. Written in , Version 2 ran on Digital Equipment Corporation's (DEC) PDP-11 with just 128 KB of RAM and supported basic SQL queries, simple joins, and atomic transactions, enabling structured for early enterprise applications. Shortly after, RSI ported the software to DEC's VAX platform using a PDP-11 , demonstrating early efforts toward cross-platform compatibility on systems. Key innovations in the early 1980s emphasized portability and scalability. In 1983, Oracle Version 3 was released, rewritten entirely in to create a single codebase that could run unchanged on mainframes, minicomputers, and personal computers—surpassing the platform-specific constraints of hierarchical databases—a groundbreaking achievement for RDBMS at the time. In the same year, the company renamed itself Oracle Systems Corporation to align with its flagship product. This version introduced multiuser access and distributed processing capabilities, allowing the database to operate across heterogeneous environments without . By 1985, Version 5 further advanced the product with full client-server architecture support, enabling networked applications where client processes could query a central server database, along with features for querying remote data sources. These milestones solidified Oracle's position as a leader in relational technology, and by the mid-1980s, it had become the largest database vendor, with its implementation of SQL contributing to the language's standardization and influencing competitors to adopt it, drawing from the outlined in the Overview while prioritizing practical commercial deployment.

Major Releases and Versions

Oracle Database versions transitioned from simple numeric designations in the early to more descriptive naming conventions that highlighted emerging technological focuses. Version 7, released in June 1992, marked a significant milestone by introducing , enabling stored procedures, functions, and triggers for enhanced within the database. This version emphasized core advancements, including improved and capabilities. By the late , Oracle shifted to release numbers paired with suffixes to reflect strategic priorities. Oracle8, released in 1997, laid groundwork for object-relational features, but it was Oracle8i—launched in February 1999—that popularized the "i" suffix, signifying an -oriented database with native support, XML handling, and protocols for web-enabled applications. Oracle9i, released in June 2001 for Release 1 and May 2002 for Release 2, continued this emphasis while adding advanced , Real Application Clusters (RAC) for , and improved data warehousing tools. The naming evolution progressed with Oracle Database 10g in 2003 (general availability in early 2004), where the "g" denoted , introducing automated management features like Automated Storage Management (ASM) and self-tuning capabilities to support scalable, shared-resource environments. Oracle Database 11g, released in August 2007, retained the "g" while enhancing grid and manageability with features such as secure files and advanced compression. In 2013, Oracle Database 12c shifted to the "c" suffix for , with Release 1 in June introducing through container and pluggable databases to facilitate cloud consolidation. Modern releases adopted a pattern of (LTS) and innovation releases, with annual or biennial updates. Oracle Database 18c, available in February 2018 as a cloud-first release, and 19c, released in January 2019 for engineered systems and April 2019 for general availability, served as LTS versions emphasizing autonomous database capabilities for self-driving, self-securing, and self-repairing operations. Oracle Database 21c, launched in January 2021 for cloud and August 2021 for on-premises, focused on cloud-native innovations like tables and native support. As of 2025, the current LTS release is Oracle Database 23ai (version 23.4.0), made generally available in May 2024, which integrates AI features such as vector search, AI Vector Search indexes, and developer tools for embedding AI directly into database operations. In October 2025, Release Update 23.26.0 rebranded this lineage as Oracle AI Database 26ai, positioning it as an AI-native platform while maintaining through simple patch application without full upgrades. Oracle's support policy for these versions provides extended timelines for LTS releases to ensure stability. Premier Support for Oracle Database 19c runs until December 31, 2029, followed by Extended Support until December 31, 2032, allowing continued access to error corrections and security patches. For Oracle Database 23ai (and its 26ai evolution), Premier Support has been extended to December 31, 2031, underscoring its role as a long-term foundation for AI-integrated enterprise .
ReleaseInitial AvailabilityKey Naming FocusNotable Enhancements
Version 7June 1992Numeric introduction
8iFebruary 1999 (i)Java and XML support
9iJune 2001 (i)RAC and
10gEarly 2004Grid (g)ASM and self-tuning
11gAugust 2007Grid (g)Compression and security
12cJune 2013 (c)
18c/19cFebruary 2018 / April 2019 (c), LTSAutonomous features
21cJanuary 2021 (c), Innovation and
23ai / 26aiMay 2024 / October 2025AI (ai), LTSVector search and AI integration

Security and Patch Updates

Oracle's patch management for the Database follows a structured quarterly to address security vulnerabilities and ensure system stability. Since 2005, Oracle has issued Critical Patch Updates (CPUs) on the third Tuesday of , April, July, and October, providing fixes for multiple (CVEs) across its products, including the Database. These updates prioritize high-risk issues, such as remote code execution or , and are cumulative, incorporating prior fixes where applicable. For instance, the July 2025 CPU included six new security patches for Oracle Database products, targeting vulnerabilities in versions like 19c and 23ai. Throughout its history, Oracle Database has faced several notable security incidents that prompted rapid patch responses. In the early 2000s, multiple vulnerabilities affected versions 9i and 10g, allowing remote attackers to execute arbitrary SQL commands and gain elevated privileges; examples include CVE-2005-0297, which impacted mechanisms, and CVE-2005-4832, exploitable via authenticated sessions. In 2014, the vulnerability (CVE-2014-0160) in posed risks to Oracle products, including Database installations using affected libraries for network communications, potentially exposing sensitive memory contents; Oracle issued targeted alerts and patches to mitigate confidentiality breaches. More recently, the October 2025 CPU addressed ongoing vulnerabilities in Database 23ai through Release Update 23.26.0, which transitioned the product to AI Database 26ai while incorporating security fixes for potential exploits in AI-integrated features. Oracle distinguishes between update types to balance security, functionality, and platform-specific needs. Release Updates (RUs) are quarterly patches that bundle fixes from CPUs, bug resolutions, and minor enhancements; for example, Database 19.28 RU (July 2025) resolved known issues alongside stability improvements. Bundle Patches provide platform-tailored aggregates of RUs and CPUs, such as for Exadata or specific operating systems, ensuring comprehensive coverage without redundant applications. Customers are advised to apply these via My Oracle Support, which delivers alerts, advisories, and download links for patches. The primary tool for applying these patches is OPatch, a command-line utility included with Oracle Database installations, which automates patch analysis, application, and rollback while checking for conflicts. OPatch supports both one-off patches and bundled updates, requiring version 12.2.0.1.24 or later for recent releases, and integrates with My Oracle Support's conflict checker to validate compatibility before deployment. Oracle recommends testing patches in non-production environments to minimize , emphasizing proactive application of CPUs within 90 days to mitigate emerging threats.

Technical Architecture

Relational Database Model

The Oracle Database implements the model originally proposed by E. F. Codd in 1970, organizing data into tables that represent relations, where each table consists of rows (tuples) and columns (attributes). This structure allows for the storage of related data in a structured manner, with rows representing individual records and columns defining the data attributes for those records. uniquely identify each row within a table, ensuring no duplicates and facilitating efficient data retrieval, while foreign keys in one table reference the primary key in another table to establish relationships between tables, thereby maintaining across the database. To minimize and dependency issues, Oracle Database supports through normalization, a process that organizes tables into progressive normal forms: (1NF) eliminates repeating groups by ensuring atomic values in each column; (2NF) removes partial dependencies on non-key attributes; (3NF) eliminates transitive dependencies; and Boyce-Codd normal form (BCNF) further refines 3NF by requiring that every determinant be a . These normalization levels are achieved during the logical design phase, using primary and foreign keys to decompose tables and avoid anomalies such as insertion, update, and deletion inconsistencies, though may denormalize for performance in specific scenarios like data warehousing. Oracle Database complies with core elements of ANSI SQL standards, including (also known as SQL2) for foundational query operations and extending to SQL:2003 and later for advanced features, while introducing proprietary extensions to enhance functionality. A notable Oracle-specific extension is the CONNECT BY clause, which enables hierarchical queries to traverse tree-structured data, such as organizational charts or bill-of-materials, by specifying parent-child relationships without requiring recursive common table expressions found in standard SQL:1999. Data integrity in Oracle Database is enforced through constraints applied at the database level during table creation or alteration, preventing invalid data entry and ensuring consistency. Unique constraints prohibit duplicate values in a column or set of columns, allowing nulls unless combined with a NOT NULL clause; check constraints validate data against specified conditions, such as range limits or patterns; and referential integrity constraints, implemented via foreign keys, ensure that a child table's foreign key value matches an existing primary or unique key in the parent table, with options for actions like CASCADE deletes or SET NULL on parent key violations. These constraints are declaratively defined using SQL DDL statements and automatically validated by the database engine on every DML operation, providing robust protection without application-level coding. Transactions in Oracle Database adhere to the ACID properties—atomicity, consistency, isolation, and —ensuring reliable even in the event of failures. Atomicity is maintained by treating a transaction as an indivisible unit, with all changes committed or rolled back entirely using data stored in dedicated undo segments within the undo . Consistency is preserved through constraints and triggers that enforce business rules, while isolation prevents concurrent transactions from interfering via multi-version concurrency control (MVCC), allowing readers to see a consistent view without blocking writers. guarantees that committed changes survive system crashes, achieved by writing redo logs to disk before commit acknowledgment. Rollback segments, now largely superseded by automatic undo management in modern versions, store before-images of modified data blocks to enable transaction and recovery.

Instance and Database Structure

In Oracle Database, the terms "database" and "instance" refer to distinct but interdependent components. The database comprises a collection of physical files stored on disk, including datafiles that hold the actual user and , control files that record essential metadata such as the locations of datafiles and redo logs, and redo log files that capture all database changes to enable recovery in case of . These files exist independently of any running processes and form the persistent storage layer. The instance, on the other hand, is the dynamic set of memory structures and background processes that access and manage the database files during operation. Central to the instance is the , a region that includes the shared pool for storing parsed SQL statements, code, and dictionary cache; the buffer cache (also known as the database buffer cache) for caching frequently accessed data blocks to reduce I/O; and the redo log buffer for temporarily holding redo entries generated by transactions before they are persisted. Background processes run as part of the instance to perform maintenance tasks; notable examples include the Database Writer (DBWR), which asynchronously writes "dirty" (modified) buffers from the buffer cache to datafiles; the Log Writer (LGWR), which synchronously flushes the redo log buffer to redo log files during commits to ensure durability; and the (SMON), which handles crash recovery, cleans up temporary segments, and coalesces free space. Multiple DBWR processes can be configured for high-performance environments to manage I/O more efficiently. Oracle Database organizes data logically to abstract the physical storage, enabling flexible management and allocation. At the highest level, tablespaces serve as logical containers that group related datafiles and provide a layer of abstraction for storage administration; every database includes mandatory tablespaces like SYSTEM for objects and SYSAUX for auxiliary data. Within tablespaces, storage is allocated to segments, which represent individual objects such as tables, indexes, or segments, each confined to a single tablespace. Segments are composed of one or more extents, which are contiguous allocations of space from the datafiles, and the smallest unit is the data block, typically sized at 8 KB by default (though configurable as 4 KB, 16 KB, or larger during creation, depending on the operating system and workload needs). This hierarchical structure—blocks within extents, extents within segments, segments within tablespaces—facilitates efficient space management and data retrieval. The architecture of an Oracle instance supports scalable connection handling and query execution. In dedicated server mode, each client connection spawns a dedicated server (or thread on Windows) that manages the session's private memory in the Program Global Area (PGA), providing isolation but consuming more resources for high-connection scenarios. Conversely, shared server mode pools a limited number of server processes, with client connections routed through dispatchers; session-specific resides in the SGA's User Global Area (UGA) to support multiplexing and reduce overhead in environments with many short-lived sessions. For performance-intensive operations, parallel execution divides large SQL statements into granules of work processed concurrently by parallel execution (PX) servers, which act as producers (generating ) or consumers (receiving and processing it), enabling faster query completion on multi-CPU systems. Starting and shutting down an Oracle instance follows defined phases to ensure controlled access to the database. During startup, the NOMOUNT phase initializes the instance by allocating the and starting background processes without attaching to any database. The MOUNT phase then reads the control files to validate the database structure and attach the instance, but keeps datafiles closed for maintenance tasks like renaming files. Finally, the OPEN phase makes the database accessible by opening datafiles and redo logs, allowing user connections and transactions. Shutdown reverses this sequence: the database is closed (transactions committed or rolled back, files closed), dismounted (control files updated and closed), and the instance terminated ( deallocated, processes stopped), with options for normal, immediate, or transactional modes to balance consistency and speed.

Multitenant and Cloud Architecture

Oracle Multitenant architecture, introduced in Oracle Database 12c Release 1 in 2013, allows a single Oracle Database instance to function as a container database (CDB) that consolidates multiple pluggable databases (PDBs). Each PDB provides a portable, self-contained environment with its own schemas, objects, and files, enabling logical isolation while sharing the CDB's resources such as the global area (SGA) and background processes. This design facilitates easier provisioning and migration, as PDBs can be plugged, unplugged, cloned, or relocated between CDBs without downtime, supporting rapid deployment in consolidated environments. The architecture offers key benefits including efficient resource sharing across PDBs, which reduces hardware and licensing costs; support for hot-pluggable operations that allow PDBs to be created, dropped, or switched online without affecting others; and unified management for patching, upgrades, and backups at the CDB level. For instance, a single CDB can support up to 4,096 PDBs on engineered systems or platforms, enabling massive consolidation of workloads while maintaining isolation and independent administration per PDB. Since Oracle Database 21c, the multitenant model is the only supported architecture, with non-CDB configurations desupported to emphasize this consolidated approach. In cloud environments, Oracle integrates multitenant capabilities through Oracle Cloud Infrastructure (OCI), particularly with the Autonomous Database service, which is inherently multitenant and serverless. Launched as a cloud-native offering and enhanced starting with Oracle Database 19c, Autonomous Database provides automatic scaling of compute (CPU cores) and storage based on workload demands, eliminating manual provisioning and ensuring high availability without administrator intervention. It supports hybrid deployments via Exadata Cloud Service, where on-premises Exadata systems can extend to OCI for seamless multitenant consolidation across environments. The evolution of multitenant architecture in cloud contexts has focused on AI-driven optimizations, particularly in releases 19c and later. In 19c, features like automatic indexing—powered by machine learning to monitor workloads and create or drop indexes autonomously—were introduced to enhance performance in multitenant setups. Oracle AI Database 26ai (as of October 2025) further advances this with built-in AI capabilities for Autonomous Database, including AI Vector Search for semantic querying of embeddings (extended with new metrics like ), natural language querying via Select AI, and model training directly within PDBs, enabling scalable AI integration while leveraging the multitenant framework for isolation and efficiency.

Key Features

SQL Support and Extensions

Oracle Database provides full conformance to the core features of the SQL:2023 standard, as established by the (ANSI) and the (ISO), enabling portable SQL queries across compliant systems. This compliance includes support for essential SQL elements such as data definition, data manipulation, and query operations, while Oracle actively participates in standards committees to ensure ongoing alignment with evolving specifications. To enhance querying capabilities beyond standard SQL, Oracle introduces proprietary extensions, notably analytic functions and the PIVOT/UNPIVOT operators. Analytic functions, such as ROW_NUMBER() and RANK(), allow for advanced windowed computations over partitions of result sets, enabling efficient ranking and aggregation without grouping the entire query. For instance, ROW_NUMBER() assigns a unique sequential number to each row within a partition, while RANK() handles ties by assigning the same rank to equal values and skipping subsequent ranks. Introduced in Oracle Database 11g, the PIVOT operator transforms rows into columns for crosstab reporting, and UNPIVOT reverses this process to normalize data, both streamlining complex data reshaping tasks. The core query language in Oracle centers on the SELECT statement, supporting both ANSI-standard JOIN syntax (e.g., INNER JOIN, LEFT OUTER JOIN) and the legacy Oracle syntax using equijoins in the WHERE with the (+) operator for outer joins. Subqueries are fully supported in various s, including WHERE, FROM, and SELECT, allowing nested queries for conditional filtering and derived tables. Set operators such as UNION, INTERSECT, and MINUS (equivalent to EXCEPT in the standard) combine result sets from multiple SELECT statements, with ALL variants preserving duplicates. Oracle's SQL implementation includes a rich set of data types tailored for diverse applications. VARCHAR2 supports variable-length character strings up to 32,767 bytes when the MAX_STRING_SIZE parameter is set to EXTENDED (available since Oracle Database 12c), surpassing the default 4,000-byte limit. Large object types like CLOB for character data and BLOB for binary data handle extensive content beyond VARCHAR2 limits. Native support, introduced in Oracle Database 12c, allows storage and querying of documents using dedicated functions and a data type in later releases, while spatial data is managed via the SDO_GEOMETRY object type for geometric representations. Oracle AI Database 26ai introduces the for storing TRUE and FALSE values, compliant with SQL:2023. For executing SQL statements, Oracle provides tools such as , a for interactive and batch SQL processing, and SQL Developer, a graphical that supports query building, execution, and database browsing.

PL/SQL and Advanced Programming

is Oracle Corporation's procedural language extension to Structured Query Language (SQL), designed to enable block-structured programming directly within the Oracle Database environment. It combines the declarative nature of SQL with procedural constructs such as loops, conditional statements, and , allowing developers to create robust, database-resident applications. enhances SQL by embedding it within procedural code, supporting the development of stored subprograms that improve performance through reduced network traffic and centralized logic. This integration facilitates the encapsulation of business rules at the data layer, promoting consistency and security in enterprise applications. The core structure of PL/SQL code revolves around the block, which serves as the fundamental unit for organizing declarations and statements. A PL/SQL block optionally begins with a section for defining local elements, followed by a mandatory BEGIN section for executable statements, an optional EXCEPTION section for error management, and concludes with END followed by a . The section accommodates variable declarations, cursor definitions, and subprogram specifications, while the BEGIN section executes SQL and procedural commands. For instance, a basic anonymous block might declare a numeric variable, perform an assignment and query in BEGIN, and terminate cleanly with END. Named blocks, such as those within procedures, follow the same format but can be nested for modular code organization. This structure ensures logical , aiding in and . Variables in PL/SQL are declared in the DECLARE section using explicit types such as NUMBER for numerics, VARCHAR2 for strings, or DATE for temporal values, with initial values assigned via the := operator. Constants are similarly declared but prefixed with the CONSTANT keyword and must be initialized at declaration since they cannot be reassigned. These elements support data abstraction by allowing type-safe manipulation within blocks, and they can reference SQL data types for seamless integration with queries. Cursors, another key element, handle multi-row query result sets: explicit cursors are user-defined with DECLARE CURSOR, opened via OPEN, rows fetched using FETCH into variables, and closed with CLOSE; implicit cursors are automatically managed by PL/SQL for single-row DML operations. Cursor variables, declared as REF CURSOR types, enable dynamic result set passing between subprograms, enhancing flexibility in complex . Packages represent a modular approach to PL/SQL programming, grouping related variables, cursors, procedures, and functions into a single database object for improved organization and reusability. A package consists of two components: the specification, which publicly declares interfaces such as procedure signatures and global variables without implementation details, and the private body, which provides the actual code logic. This separation enforces encapsulation, hiding internal details while exposing only necessary elements, and supports overloading of subprograms with the same name but different parameters. Packages persist in the database schema, allowing global access across sessions and reducing compilation overhead through stored dependencies. Advanced PL/SQL features extend its capabilities for event-driven and dynamic operations. Triggers are specialized PL/SQL blocks automatically executed in response to database events like INSERT, UPDATE, or DELETE on tables or views, enforcing integrity constraints or auditing without application intervention. They operate at row level, firing once per affected row for granular control, or at statement level, firing once per SQL statement for efficiency with bulk operations; compound triggers combine both scopes within a single unit for complex scenarios. Stored procedures perform actions without returning values and are invoked via CALL or EXECUTE, while functions return computed values of specified types and integrate into SQL expressions, both supporting parameters (IN, OUT, IN OUT) for data exchange. Dynamic SQL enables runtime construction of statements unavailable at compile time, primarily through the EXECUTE IMMEDIATE command for non-query operations or anonymous blocks, or via DBMS_SQL for advanced multi-row handling, mitigating SQL injection risks with bind variables. PL/SQL integrates seamlessly with external languages and modern architectures to support hybrid application development. Since Oracle Database 8i, an embedded (JVM) allows loading and executing Java classes directly in the database, callable from PL/SQL via the DBMS_JAVA package for tasks like XML processing or custom algorithms. For .NET environments, Oracle's Data Provider for .NET (ODP.NET) facilitates bidirectional calls between PL/SQL subprograms and C# or VB.NET code, enabling managed access to Oracle data types and transactions. In Oracle AI Database 26ai, PL/SQL enhancements include native support for building RESTful APIs through packages like UTL_HTTP and utilities, allowing database procedures to expose endpoints for , Relational Duality, and AI-driven applications without . Error handling in PL/SQL relies on exceptions, which are runtime errors trapped and processed to prevent abrupt program termination. The EXCEPTION section declares handlers for specific exceptions using WHEN clauses, allowing custom actions like logging or user notifications before re-raising or propagating the error. Built-in system exceptions include NO_DATA_FOUND, raised when a SELECT INTO returns no rows, and DUP_VAL_ON_INDEX for unique constraint violations, each mapped to Oracle error codes for precise identification. User-defined exceptions are declared in DECLARE with EXCEPTION and raised explicitly via RAISE or the RAISE_APPLICATION_ERROR procedure, which also sets custom error messages and codes between -20000 and -20999. This mechanism ensures fault-tolerant code, with propagation to outer blocks if unhandled locally.

Backup, Recovery, and High Availability

Oracle Database provides robust mechanisms for , recovery, and to protect and minimize downtime in enterprise environments. These features are integral to ensuring business continuity, supporting automated backups, , and clustered architectures that enable and . Central to these capabilities is Recovery Manager (RMAN), an Oracle Database client that automates and recovery tasks while handling underlying procedures such as validation and error correction, eliminating reliance on operating system scripts or . RMAN supports full backups of the entire database and incremental backups that capture only changes since the last backup, allowing efficient storage and faster restores. Complementing RMAN, Oracle Data Pump utilities facilitate logical backups and migrations by exporting and importing data and metadata. The Data Pump Export utility (expdp) unloads schemas, tables, tablespaces, or the full database into a dump file set stored on the server-side via directory objects, supporting parallel processing for performance. The corresponding Import utility (impdp) loads these files into a target database, enabling remapping of schemas or data and filtering to include or exclude specific objects. These tools are particularly useful for cross-platform transfers or creating test environments without physical file copies. Recovery options in Oracle Database emphasize flexibility and precision, leveraging archived redo logs for complete data replay. In ARCHIVELOG mode, the database archives filled online redo logs, preserving all transaction changes for subsequent recovery operations. Point-in-time recovery (PITR) via RMAN restores the database from a predating the target point and applies archived redo logs or incremental backups to roll forward to a specific System Change Number (SCN), timestamp, log sequence, or , ensuring no up to the desired moment. This process recreates committed transactions while allowing incomplete recovery to exclude unwanted changes. Oracle Flashback Technology offers lightweight alternatives for targeted recoveries without full restores. Flashback Query retrieves committed data as it existed at a prior SCN or directly from the database, using undo data for historical views. Flashback Table reverts a single table to a past state by restoring its data from a or flashback logs, while Flashback Database rewinds the entire database to a specified SCN or time using flashback logs in the fast recovery area, bypassing the need for archived redo application in many cases. These features require enabling flashback logging and setting retention targets, providing rapid recovery with minimal downtime compared to traditional PITR. For , maintains synchronized standby databases to protect against failures and enable disaster recovery. A physical standby database is a block-for-block identical copy of the primary, kept current through real-time redo apply for read-only querying or . In contrast, a logical standby database applies SQL statements derived from the primary's redo stream, allowing an independent physical structure that supports read-write operations and rolling upgrades. Data Guard configurations can include up to 30 standbys managed via or the Data Guard broker, with protection modes balancing data safety and performance. Oracle Real Application Clusters (RAC), introduced in Oracle 9i, extends through clustering, allowing multiple database instances to access a shared database simultaneously. RAC distributes workloads across nodes for and , automatically detecting failures and redirecting connections to surviving instances without downtime. This shared-everything architecture supports 24/7 operations for mission-critical applications, integrating with storage solutions like for enhanced performance and resilience. In AI Database 26ai, advancements enhance cloud-based resilience with autonomous recovery and patching capabilities. The Zero Data Loss Autonomous Recovery Service provides fully managed, real-time protection across multicloud environments, using Data Guard for sub-second recovery point objectives and automatic replication to eliminate during outages. Additionally, zero-downtime patching for Oracle Grid Infrastructure updates user-space binaries in a rolling fashion without halting RAC databases, ensuring continuous during . These features automate administrative tasks, reducing manual intervention in deployments.

Editions and Licensing

Standard and Enterprise Editions

Oracle Database offers two primary commercial editions for on-premises deployments: Standard Edition 2 (SE2) and Enterprise Edition (EE). These editions cater to different scales of operations, with SE2 targeted at smaller environments like workgroups or departmental applications, while EE supports large-scale, mission-critical systems requiring advanced capabilities and scalability. Both editions share core functionalities but differ significantly in feature sets, hardware limits, and extensibility options. Standard Edition 2 is optimized for cost-effective solutions in smaller deployments, providing essential features such as basic partitioning for managing large tables and basic compression to reduce storage needs. However, it imposes strict hardware restrictions, licensed on servers with a maximum capacity of 2 sockets, with a runtime limit of 16 CPU threads, making it unsuitable for high-performance or distributed environments. Notably, SE2 does not include support for Real Application Clusters (RAC), though it offers Standard Edition for basic using Oracle Clusterware on up to two nodes. These constraints ensure SE2 remains accessible for mid-sized applications without the overhead of full enterprise licensing. In contrast, Enterprise Edition delivers the complete Oracle Database feature set, enabling unlimited scaling across processors and nodes. It includes advanced partitioning for complex , advanced compression for significant storage and I/O savings, and the Diagnostics and Tuning Packs for and optimization. EE also supports Real Application Clusters for clustered and load balancing, along with options like Active Data Guard for real-time data protection. This edition is ideal for enterprise-wide deployments demanding robustness and extensibility. Licensing for both editions follows Oracle's standard models: Named User Plus (NUP), which requires a license per named user accessing the database (minimum of 25 NUP per processor for processor-based entitlements), or Processor, based on the total number of processors or cores adjusted by a processor core factor (typically 0.5 for , meaning half the cores are licensed). Enterprise Edition often incurs higher costs due to its broader feature inclusion, while Standard Edition 2 benefits from simpler, lower-tier pricing suitable for limited-scale use. Additionally, Oracle Database Express Edition (XE), a free variant based on Oracle Database 21c, supports development, deployment, and distribution with restrictions to 12 GB of user data, 2 GB of RAM, and 2 CPU cores, serving as an entry point without commercial . As of 2025, Oracle also offers Oracle AI Database 26ai Free, the current free edition for developers aligned with the latest release, featuring the same resource limits (2 CPUs, 2 GB RAM, 12 GB user data).
Feature/LimitStandard Edition 2 (SE2)Enterprise Edition (EE)
Basic PartitioningIncludedIncluded (plus advanced)
CompressionBasicAdvanced
Real Application Clusters (RAC)Not includedIncluded
Processor Limit2 sockets, 16 CPU threadsUnlimited
High AvailabilityStandard Edition HA (2 nodes)Full RAC and options
Diagnostics PackNot includedIncluded

and Specialized Offerings

Oracle Autonomous Database, available on Oracle Cloud Infrastructure (OCI), represents a serverless, fully managed database service that leverages for automated provisioning, tuning, scaling, and security patching. Introduced in , it eliminates the need for manual database administration by self-driving, self-securing, and self-repairing through integrated AI capabilities. Within the Autonomous Database family, Autonomous Transaction Processing (ATP) supports high-volume workloads with automatic scaling and concurrency management, while Autonomous Data Warehouse (ADW) optimizes for by accelerating data loading and query performance using columnar storage and vectorized execution. Both services deploy in isolated, multi-tenant environments on OCI, ensuring data isolation and elastic resource allocation without . Oracle offers specialized database variants tailored for performance-critical scenarios. Oracle Database In-Memory accelerates by storing data in a highly optimized, , enabling real-time querying of large datasets with SIMD vector processing. TimesTen, an , serves as a caching layer for Oracle Database, reducing latency for operational applications by maintaining frequently accessed data in RAM. Additionally, provides a hybrid solution on OCI, combining 's relational engine with an in-memory accelerator for massive-scale queries on transactional data. Cloud deployments of Oracle Database utilize flexible licensing models, including pay-per-use based on compute, storage, and data transfer consumption, as well as Bring Your Own (BYOL), which allows customers to apply existing on-premises licenses to reduce costs by up to 76% on services like Autonomous Database. Oracle Database 23ai, available in cloud environments, introduces AI Vector Search, enabling semantic queries on such as documents and images alongside structured relational . In 2025, enhanced AI integration in Autonomous Database through the release of AI Database 26ai, which extends generative AI workloads with native support for multimodal and automated model deployment, allowing seamless transitions from 23ai via quarterly updates without re-certification. This update emphasizes AI-native features for enterprise-scale generative applications, building on the multitenant to support hybrid cloud deployments.

Security Mechanisms

Access Control and Auditing

Oracle Database employs several authentication mechanisms to verify user identities before granting access. User identifiers (usernames) are not case-sensitive by default; Oracle converts non-quoted usernames to uppercase internally, storing and referencing them accordingly, which allows logins and SQL statements to use any case variation. For example, CREATE USER scott creates a user stored as SCOTT. Using double quotes preserves the exact case, making it case-sensitive, such as CREATE USER "Scott" requiring exact matching for connections and references. In contrast, passwords are case-sensitive since Oracle Database 11g. The primary method is password-based , where users provide credentials stored in encrypted form within the database's , supporting features like account locking after failed login attempts, password expiration, and complexity requirements such as minimum length and reuse restrictions. Operating system (OS) authentication allows users to connect without entering a password by leveraging the host operating system's credentials, typically requiring membership in a designated OS group like the "dba" group for administrative access, which enables centralized user management without storing passwords in the database. Wallet-based authentication utilizes (PKI) through Oracle Wallets, which store digital certificates and private keys to enable secure, certificate-based logins over SSL/TLS connections, reducing reliance on passwords for high-security environments. Since Oracle Database 19c with the July 2025 Release Update, (MFA) has been supported for native users, incorporating push notifications or certificate-based factors alongside passwords to enhance security for database logins. Authorization in Oracle Database controls what authenticated users can do through a system of privileges and roles. System privileges, such as CREATE TABLE or SELECT ANY TABLE, and object privileges, like SELECT on a specific table, are granted or revoked using SQL statements like GRANT and REVOKE, allowing administrators to assign granular permissions; for example, GRANT CREATE SESSION TO user_name enables basic connectivity. Predefined roles simplify management by bundling related privileges: the DBA role provides extensive administrative capabilities, including DELETE ANY TABLE, while the CONNECT role grants only the CREATE SESSION privilege for basic access, with recommendations to use custom roles for tailored security. Administrators can query data dictionary views to examine granted roles and privileges. The DBA_ROLE_PRIVS view shows roles granted to users or other roles, DBA_SYS_PRIVS displays system privileges granted to users or roles, and DBA_TAB_PRIVS lists object privileges granted on database objects such as tables and views. These views can be queried with a filter on the GRANTEE column to view information for a specific user or role, for example: SELECT * FROM DBA_ROLE_PRIVS WHERE GRANTEE = 'USERNAME'; analogous queries apply to DBA_SYS_PRIVS and DBA_TAB_PRIVS. Querying these DBA_ views generally requires the SELECT ANY DICTIONARY system privilege or the DBA role. These views reflect direct grants; effective privileges may include those inherited through role hierarchies. Fine-grained access control is achieved via Virtual Private Database (VPD), which enforces row- and column-level security by dynamically appending predicates to SQL queries based on user context, using policies defined with the DBMS_RLS package and requiring the ADMINISTER ROW LEVEL SECURITY POLICY privilege. Auditing in Oracle Database tracks user activities to ensure accountability and compliance. Standard auditing captures mandatory events like SYS operations and can be configured for statement, privilege, schema, or object-level tracking, storing records in database tables such as SYS.AUD$ for analysis. Fine-grained auditing (FGA), part of Oracle Database Enterprise Edition, enables value-based policies to audit specific data access, such as rows where a column meets certain conditions, using the DBMS_FGA package to define policies that trigger on SELECT, INSERT, UPDATE, or DELETE statements. Introduced in Oracle Database 12c, unified auditing consolidates standard, fine-grained, and RLS auditing into a single framework, writing records to a secure, tamper-evident trail in the AUDSYS schema or OS files, which supports compliance with regulations like SOX and GDPR through filtered policies and reduced administrative overhead. For centralized management, Oracle Audit Vault collects and stores audit data from multiple databases in a dedicated repository, providing prebuilt reports for compliance standards including SOX and GDPR, with support for Oracle Database 23ai including SQL Firewall integration for enhanced activity monitoring. Introduced in Oracle Database 23ai, SQL Firewall provides kernel-level protection against and unauthorized SQL execution by inspecting all incoming connections and statements in real time. It allows administrators to define policies using the DBMS_SQL_FIREWALL package to learn, block, or log unexpected SQL patterns and session contexts, integrating with unified auditing for comprehensive monitoring and compliance reporting. This feature enhances database security without requiring external appliances.

Encryption and Data Protection

Oracle Database provides robust encryption mechanisms to protect data at rest and in transit, ensuring against unauthorized access. These features integrate seamlessly with the database's core architecture, allowing encryption without requiring changes to existing applications. Key technologies include (TDE) for data at rest and (TLS) for network communications, both leveraging industry-standard algorithms like AES. Transparent Data Encryption (TDE), introduced in Oracle Database 10g, enables encryption of sensitive data stored in tablespaces and individual columns without altering application logic. TDE uses Advanced Encryption Standard (AES) algorithms, supporting key lengths of 128, 192, or 256 bits, to protect data files from theft or unauthorized file system access. Tablespace encryption secures entire storage units, while column-level encryption targets specific sensitive fields, such as credit card numbers, using a master encryption key managed via Oracle Wallet. In Oracle Database 23ai, AES-256 with XTS-AES mode became the default, offering enhanced resistance to post-quantum attacks by providing greater security against future quantum computing threats. For data in transit, Oracle Database supports native network and the TCPS protocol based on TLS, securing communications over SQL*Net. Native uses algorithms like AES and 3DES to protect data exchanged between clients and servers, configurable via sqlnet.ora parameters without needing external certificates. TLS integration, available since Oracle Database 11g, employs SSL/TLS handshakes for and , ensuring end-to-end for connections in and on-premises environments. Oracle recommends TCPS for all database connections to mitigate man-in-the-middle attacks. Advanced protection features extend beyond basic encryption to address dynamic data exposure and integrity. Oracle Data Redaction, introduced in Oracle Database 12c, dynamically masks sensitive data in query results—such as replacing numbers with asterisks—without modifying the underlying data or requiring application changes. It supports full, partial, random, and redaction types, applied based on user roles or conditions. Oracle Label Security complements this by enforcing multilevel access controls through data labels, restricting row visibility based on classifications like "Top Secret" or departmental compartments, ideal for government and defense applications. To ensure tamper-proofing, Oracle Database 21c introduced blockchain tables, which are immutable, append-only structures that chain rows cryptographically to prevent unauthorized modifications or deletions. These tables use hash functions to verify data integrity, supporting use cases like audit trails and supply chain records without external blockchain infrastructure. Oracle AI Database 26ai (October 2025) further enhances security for cloud deployments by integrating NIST-approved post-quantum algorithms such as ML-KEM for key exchange and ML-DSA for signatures into TLS, providing forward compatibility against emerging quantum threats for data in transit.

Performance Optimization

Query Optimization and Indexing

Oracle Database employs a cost-based optimizer (CBO) to select the most efficient execution for SQL queries, a feature introduced in version 7.3 with enhancements such as histograms for improved selectivity estimates on non-uniform distributions. The CBO evaluates multiple possible plans and chooses the one with the lowest estimated cost, factoring in CPU, I/O, and network resources. To support accurate cost calculations, the optimizer relies on statistics about database objects, which are gathered and maintained using the DBMS_STATS package; this package collects on tables, indexes, columns, and partitions at various granularity levels, including and database-wide. Administrators can view the optimizer's chosen execution plan for a SQL statement using the EXPLAIN PLAN statement, which populates a plan table for analysis and helps diagnose performance issues without executing the query. Indexing in Oracle Database enhances query performance by providing quick access paths to data, with the index serving as the default structure for most scenarios due to its efficiency in handling high-cardinality columns with many distinct values. For low-cardinality columns, such as gender or status flags with few distinct values, bitmap indexes are more space-efficient, as they use bit vectors to represent row sets and support fast bitwise operations for set-based queries. Function-based indexes precompute the results of expressions or functions on column values, enabling the optimizer to leverage them for queries involving calculations, like UPPER(column_name) or . Domain indexes, an extensible type implemented via user-defined indextypes, cater to specialized data such as , where JSON search indexes—introduced in 12c and built on Oracle Text—facilitate full-text and structural queries on JSON documents, with further enhancements in later versions like 23ai and 26ai. Automatic indexing, introduced to automate index management, monitors workload changes and automatically creates, rebuilds, or drops indexes using the DBMS_AUTO_INDEX package, with options to override retention policies for secondary indexes; enhancements in 26ai include consideration of maintenance costs and support for function-based indexes. The optimizer employs various join methods to combine data from multiple tables, including nested loops for small result sets where an outer row probes an inner table iteratively, hash joins for large datasets by building a hash table on one input, and sort-merge joins for ordered data requiring sorting before merging. Starting with Oracle Database 12c, adaptive execution plans allow the optimizer to adjust join strategies at runtime based on actual row counts, such as switching from nested loops to hash joins if initial statistics prove inaccurate, controlled by the OPTIMIZER_ADAPTIVE_PLANS parameter. For cardinality estimation—the prediction of row counts filtered by predicates—the optimizer uses dynamic sampling when statistics are stale or absent, with the OPTIMIZER_DYNAMIC_SAMPLING parameter setting levels from 1 to 11; higher levels sample more blocks (up to the entire table at level 11) to refine estimates for complex predicates, improving plan accuracy without full scans.

Tuning and Monitoring Tools

Oracle Database provides a suite of built-in and licensed tools for diagnosing performance issues, monitoring system health, and proactively tuning workloads to ensure optimal efficiency. These tools leverage automated and to identify bottlenecks, recommend optimizations, and facilitate adjustments without extensive manual intervention. By integrating with the database's core , they enable database administrators to maintain and scalability across diverse environments, from on-premises deployments to cloud-based instances. The Automatic Workload Repository (AWR) serves as a foundational tool for diagnostics, automatically collecting, processing, and storing on database activity between periodic snapshots, typically taken every hour. These snapshots capture metrics such as workload profiles, time model , system and session , and details on high-load SQL statements, enabling the generation of comprehensive reports via or command-line interfaces. AWR reports highlight resource usage patterns and potential issues, supporting self-tuning mechanisms by providing data for further analysis tools. For instance, in Oracle Real Application Clusters (RAC) environments, AWR includes instance-level diagnostics to compare across nodes. Complementing AWR, the Automatic Database Diagnostic Monitor (ADDM) analyzes snapshot data to automatically detect and report performance problems, focusing on metrics like database time (DB time), which represents the cumulative processing time for user requests. ADDM employs a top-down approach to isolate root causes—such as excessive I/O or CPU contention—and generates actionable recommendations, including hardware upgrades or modifications, each quantified by estimated benefits in reduced DB time. These findings are stored in the database and accessible through Cloud Control, allowing administrators to implement changes that prioritize high-impact fixes and support ongoing monitoring in production, development, and test systems. For real-time monitoring, (OEM) Cloud Control offers a centralized that tracks database across hybrid and multicloud environments, providing proactive alerts, AI-powered insights, and visualization of key metrics like throughput and latency. OEM integrates with AWR and ADDM to deliver holistic views, including Zero Downtime Patching for maintenance without interrupting monitoring. It supports management of Oracle and non-Oracle targets, enabling administrators to optimize resources and ensure compliance through customizable thresholds. The SQL Tuning Advisor focuses on individual or sets of SQL statements, analyzing high-load queries identified via AWR to recommend improvements such as index creation, SQL rewrites, or plan stability measures, thereby preventing performance regressions and enhancing execution efficiency. Invoked through DBMS_SQLTUNE or OEM, it uses the automatic tuning optimizer to evaluate statements and provide precise actions with projected benefits, making it essential for proactive workload optimization. Tuning often involves addressing wait events, which indicate delays in database operations; for example, the "db file sequential read" event occurs when a session awaits a single-block read from a data file, commonly during index scans or control file rebuilds, with wait time reflecting actual I/O latency. High occurrences signal potential storage bottlenecks, tunable by optimizing query plans to reduce logical I/O or enhancing disk configurations. Parameter adjustments further refine performance, managed via the text-based initialization parameter file (init.ora) for static changes requiring instance restarts or the binary server parameter file (spfile) for dynamic modifications using the ALTER SYSTEM command post-startup. The spfile, auto-generated by tools like Database Configuration Assistant, allows persistent updates to settings like memory allocation without manual file editing, ensuring consistency across restarts. I/O calibration assesses storage subsystem capabilities by simulating workloads to measure maximum throughput and latency, helping determine if I/O-related issues stem from hardware limitations. Executed via the DBMS_RESOURCE_MANAGER.CALIBRATE_IO procedure, it generates results stored in DBA_RSRC_IO_CALIBRATE, informing decisions on parallelism degrees or upgrades to align with application demands. In the current long-term support release, AI Database 26ai (as of October 2025), particularly within Autonomous Database offerings, builds on prior AI-driven auto-tuning capabilities—initially enhanced in 23ai—that self-optimize configurations, patching, and using models, reducing administrative overhead. Key new performance features include the AI Vector Search optimizer for avoiding full table scans with vector indexes, automatic data clustering to enhance query performance based on workloads, vectorized query processing leveraging SIMD instructions for faster joins and aggregations, True Cache as an in-memory diskless cache for read-only workloads, and an In-Memory Advisor to identify and optimize workloads for Database In-Memory. Additionally, integrated capabilities, such as the for (introduced in 23ai), identify outliers in patterns by estimating probability densities, enabling proactive issue resolution in performance monitoring. These features extend to advanced vector-based searches, hybrid vector indexes, and in-database ML for , further automating tuning in cloud, on-premises, and hybrid environments.

Reception and Impact

Adoption and Competition

Oracle Database has maintained its position as the leading relational database management system (RDBMS), topping the DB-Engines rankings as of March 2025 based on popularity metrics including mentions in technical discussions, job postings, and social media activity. It powers a significant portion of enterprise workloads globally, with adoption driven by its scalability and integration capabilities, particularly in sectors requiring high reliability such as finance. For instance, major banks including Lloyds Banking Group, BNP Paribas, and Mitsubishi UFJ Financial Group have expanded their use of Oracle Database for cloud migrations and performance enhancements, leveraging features like Oracle Exadata for core banking platforms. The database is deeply integrated with Oracle Fusion Cloud Applications, enabling seamless data management across ERP, HCM, and SCM modules through tools like Oracle Integration Cloud and embedded APEX extensions. This integration supports automated processes and real-time , contributing to Oracle's dominance in enterprise application ecosystems. In the cloud era, Oracle Cloud Infrastructure (OCI) has experienced rapid growth, with its infrastructure-as-a-service market position strengthening to lead in certain enterprise segments despite AWS holding the overall largest share at 29% in Q1 2025. OCI's expansion challenges traditional on-premises deployments by offering multicloud options, including a strategic partnership with that allows direct deployment of Oracle Database services within Azure data centers via Oracle Database@Azure, available in 31 global regions as of November 2025. This collaboration facilitates low-latency interconnects and unified support, accelerating migrations for organizations seeking hybrid environments. Key competitors include , which focuses on Windows-centric environments and integration with Azure; open-source options like and , favored for cost-effectiveness in web and smaller-scale applications; and , which retains a niche in mainframe and legacy systems. Oracle Database leads in (OLTP) workloads, handling high-volume, mission-critical transactions for enterprises where performance and compliance are paramount. Oracle Database has significantly influenced the RDBMS landscape by extending SQL capabilities for analytics, such as through Big Data SQL, which enables unified querying across Hadoop, , and relational data without movement, thereby reducing latency and enhancing security. Its implementation of ANSI SQL standards, including advanced analytic functions for ranking, aggregation, and modeling, has shaped industry practices for in-database processing and reporting.

Criticisms and Limitations

Oracle Database has faced significant criticism for its high licensing and maintenance costs, which often deter organizations from long-term adoption. The perpetual licensing model requires an annual support fee equivalent to 22% of the net license fee, resulting in substantial recurring expenses that can escalate with inflationary adjustments of up to 8% per year. These costs have prompted many enterprises to migrate to open-source alternatives such as , which offer similar functionality without the ongoing fees, enabling significant savings on licensing and support. The system's complexity contributes to a steep for database administration, requiring specialized skills to manage tuning, patching, and optimization effectively. Administrators often describe the setup and as challenging, particularly for those transitioning from simpler platforms, due to the depth of tools and configurations. Additionally, Oracle's reliance on features, such as custom extensions and Exadata hardware optimizations, fosters , making migrations costly and technically difficult as applications become tightly coupled to Oracle-specific implementations. Limitations in adapting to modern paradigms have also drawn scrutiny, including a historically slower embrace of NoSQL capabilities compared to dedicated NoSQL databases like , despite the addition of native support in later versions to handle . concerns persisted through the , with multiple critical vulnerabilities disclosed in Critical Patch Updates, such as those in 2010 affecting components like JavaVM and enabling remote exploits. In 2025 perspectives, while Oracle's AI features in releases like Database 26ai have received praise for enabling in-database vector search and agentic automation to accelerate enterprise AI workflows, criticisms of cloud pricing persist, with licensing models seen as prohibitively expensive for scaling workloads. Meanwhile, open-source and cloud-native alternatives like and Amazon RDS are gaining traction among small and medium-sized enterprises (SMEs), which prioritize cost-effectiveness and ease of deployment over Oracle's enterprise-scale features.

References

  1. https://docs.oracle.com/cd/B19306_01/server.102/b14220/intro.htm
  2. https://www.oracle.com/database/50-years-relational-database/
  3. https://docs.oracle.com/en/database/oracle/oracle-database/18/cncpt/introduction-to-oracle-database.html
  4. https://docs.oracle.com/en/database/oracle/oracle-database/26/nfcoa/introduction.html
  5. https://www.oracle.com/database/technologies/oracle-database-software-downloads.html
  6. https://www.oracle.com/database/what-is-a-relational-database/
  7. https://docs.oracle.com/en/database/oracle/oracle-database/26/sqlrf/Types-of-SQL-Statements.html
  8. https://docs.oracle.com/html/E25789_01/intro.htm
  9. https://db-engines.com/en/ranking
  10. https://www.oracle.com/news/announcement/oracle-named-leader-in-gartner-magic-quadrant-for-cloud-database-management-systems-2025-01-21/
  11. https://www.certlibrary.com/blog/comprehensive-guide-to-oracle-database-19c-features-benefits-and-business-value/
  12. https://www.simplyblock.io/glossary/what-is-oracle/
  13. https://www.ralantech.com/resources/oracle-database-when-why-should-you-use-oracle-database/
  14. https://docs.oracle.com/en/cloud/paas/integration-cloud/sap-adapter/using-sap-adapter-oracle-integration-generation-2.pdf
  15. https://blog.skyvia.com/oracle-and-salesforce-integration/
  16. https://docs.oracle.com/en/middleware/fusion-middleware/data-integrator/14.1.2/odibd/integrating-hadoop-data.html
  17. https://www.fool.com/investing/2025/09/14/oracle-red-hot-ten-titans-growth-stock/
  18. https://www.oracle.com/corporate/
  19. https://nap.nationalacademies.org/read/6323/chapter/8
  20. https://content.dsp.co.uk/the-history-of-oracle-corporation-1977-2000
  21. https://www.britannica.com/money/Oracle-Corporation
  22. https://quartr.com/insights/edge/a-castle-in-the-sky-the-story-of-oracle
  23. https://www.orafaq.com/wiki/Oracle_7
  24. https://docs.oracle.com/cd/A87860_01/doc/server.817/a76962.pdf
  25. https://www.orafaq.com/wiki/Oracle_9i
  26. https://docs.oracle.com/cd/B14117_01/server.101/b10750/chapter1.htm
  27. https://endoflife.date/oracle-database
  28. https://blogs.oracle.com/database/post/oracle-database-18c-now-available-on-the-oracle-cloud-and-oracle-engineered-systems
  29. https://blogs.oracle.com/database/post/introducing-oracle-database-21c
  30. https://blogs.oracle.com/database/post/oracle-23ai-now-generally-available
  31. https://mikedietrichde.com/2024/11/20/important-update-to-oracle-database-19c-support-timelines/
  32. https://mikedietrichde.com/2024/11/27/premier-support-end-date-for-oracle-database-23ai-has-been-adjusted/
  33. https://www.oracle.com/security-alerts/cpufaq.html
  34. https://www.oracle.com/security-alerts/
  35. https://www.oracle.com/security-alerts/cpujul2025.html
  36. https://nvd.nist.gov/vuln/detail/CVE-2005-0297
  37. https://nvd.nist.gov/vuln/detail/CVE-2005-4832
  38. https://www.oracle.com/security-alerts/alert-cve-2014-0160.html
  39. https://www.oracle.com/security-alerts/cpuoct2025.html
  40. https://docs.oracle.com/cd/E24628_01/doc.121/e39376/opatch_overview.htm
  41. https://blogs.oracle.com/ebstech/critical-patch-update-for-july-2025-now-available
  42. https://docs.oracle.com/en/database/oracle/oracle-database/21/cncpt/introduction-to-oracle-database.html
  43. https://docs.oracle.com/en/database/oracle/oracle-database/21/cncpt/data-integrity.html
  44. https://docs.oracle.com/en/database/oracle/oracle-database/26/dwhsg/data-warehouse-logical-design.html
  45. https://docs.oracle.com/cd/G30560_01/books/DMR/c-Overview-of-Siebel-Data-Model-afs1022619.html
  46. https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/Oracle-Compliance-with-Older-Standards.html
  47. https://docs.oracle.com/en/database/oracle/oracle-database/26/sqlrf/Hierarchical-Queries.html
  48. https://docs.oracle.com/en/database/oracle/oracle-database/18/sqlrf/constraint.html
  49. https://docs.oracle.com/en/database/oracle/oracle-database/26/cncpt/transactions.html
  50. https://docs.oracle.com/en/database/oracle/oracle-database/19/cncpt/physical-storage-structures.html
  51. https://docs.oracle.com/en/database/oracle/oracle-database/19/cncpt/oracle-database-instance.html
  52. https://docs.oracle.com/en/database/oracle/oracle-database/19/cncpt/process-architecture.html
  53. https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/DB_BLOCK_SIZE.html
  54. https://oracle-base.com/articles/12c/multitenant-overview-container-database-cdb-12cr1
  55. https://docs.oracle.com/en/database/oracle/oracle-database/23/multi/introduction-to-the-multitenant-architecture.html
  56. https://www.oracle.com/database/multitenant/
  57. https://www.oracle.com/autonomous-database/
  58. https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/autonomous-auto-scale.html
  59. https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/autonomous-auto-index.html
  60. https://docs.oracle.com/en/database/oracle/oracle-database/26/nfcoa/oracle-ai-database-26ai-new-features-guide.pdf
  61. https://blogs.oracle.com/cloud-infrastructure/post/take-advantage-of-oracle-database-23ai-autonomous-database
  62. https://www.oracle.com/database/features/
  63. https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/SQL-Standards.html
  64. https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/RANK.html
  65. https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/MAX_STRING_SIZE.html
  66. https://docs.oracle.com/en/database/oracle/oracle-database/21/adjsn/json-in-oracle-database.html
  67. https://docs.oracle.com/cd/B32485_01/appdev.110/b31695/intro.htm
  68. https://docs.oracle.com/en/database/oracle/oracle-database/21/lnpls/overview.html
  69. https://docs.oracle.com/en/database/oracle/oracle-database/26/lnpls/block.html
  70. https://docs.oracle.com/en/database/oracle/oracle-database/19/lnpls/plsql-error-handling.html
  71. https://docs.oracle.com/en/database/oracle/oracle-database/26/bradv/getting-started-rman.html
  72. https://www.oracle.com/database/technologies/high-availability/rman.html
  73. https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-data-pump-export-utility.html
  74. https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/datapump-import-utility.html
  75. https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/rman-performing-flashback-dbpitr.html
  76. https://docs.oracle.com/en/database/oracle/oracle-database/26/admin/managing-archived-redo-log-files.html
  77. https://docs.oracle.com/cd/E11882_01/appdev.112/e41502/adfns_flashback.htm
  78. https://docs.oracle.com/en/database/oracle/oracle-database/26/sbydb/introduction-to-oracle-data-guard-concepts.html
  79. https://www.oracle.com/database/real-application-clusters/
  80. https://docs.oracle.com/cd/A97385_01/rac.920/a96597.pdf
  81. https://www.oracle.com/database/zero-data-loss-autonomous-recovery-service/faq/
  82. https://docs.oracle.com/en/database/oracle/oracle-database/23/fppad/zero-downtime-grid-patching.html
  83. https://docs.oracle.com/en/database/oracle/oracle-database/21/dblic/Licensing-Information.html
  84. https://docs.oracle.com/cd/E55822_01/DBLIC/editions.htm
  85. https://docs.oracle.com/en/database/oracle/oracle-database/26/ladbi/about-standard-edition-high-availability.html
  86. https://www.oracle.com/a/ocom/docs/corporate/oracle-software-licensing-basics.pdf
  87. https://www.oracle.com/database/technologies/appdev/xe.html
  88. https://www.oracle.com/database/free/
  89. https://www.oracle.com/a/ocom/docs/database/fast-reliable-secure-database-through-automation.pdf
  90. https://docs.oracle.com/en-us/iaas/autonomous-database-serverless/doc/previous-feature-announcements.html
  91. https://www.oracle.com/a/ocom/docs/database/how-oracle-autonomous-database-transform-database-it-outsourcing.pdf
  92. https://www.oracle.com/database/technologies/datawarehouse-bigdata/adw-patterns.html
  93. https://livelabs.oracle.com/pls/apex/r/dbpm/livelabs/view-workshop?wid=3433
  94. https://apexapps.oracle.com/pls/apex/r/dbpm/livelabs/view-workshop?wid=3282&clear=RR%2C180&session=13976108850040
  95. https://www.oracle.com/a/ocom/docs/database/gartner-newsletter-oracle-report.pdf
  96. https://www.oracle.com/cloud/pricing/
  97. https://blogs.oracle.com/cloud-infrastructure/post/license-investment-byol-autonomous-database
  98. https://www.oracle.com/news/announcement/oracle-announces-availability-database-23ai-with-ai-vector-search-2024-05-02/
  99. https://www.oracle.com/news/announcement/ai-world-database-26ai-powers-the-ai-for-data-revolution-2025-10-14/
  100. https://www.oracle.com/database/ai-native-database-26ai/
  101. https://docs.oracle.com/en/database/oracle/oracle-database/26/sqlrf/Database-Object-Names-and-Qualifiers.html
  102. https://docs.oracle.com/en/database/oracle/oracle-database/19/spuss/understanding-password-case-sensitivity-and-upgrades.html
  103. https://docs.oracle.com/cd/B19306_01/network.102/b14266/authmeth.htm
  104. https://docs.oracle.com/en/database/oracle/oracle-database/19/dbseg/configuring-authentication.html
  105. https://blogs.oracle.com/database/post/new-mfa-jul2025
  106. https://docs.oracle.com/en/database/oracle/oracle-database/26/dbseg/configuring-privilege-and-role-authorization.html
  107. https://docs.oracle.com/en/database/oracle/oracle-database/26/dbseg/using-oracle-vpd-to-control-data-access.html
  108. https://docs.oracle.com/en/database/oracle/oracle-database/26/dbseg/introduction-to-auditing.html
  109. https://docs.oracle.com/en/database/oracle/oracle-database/23/dbseg/value-based-auditing-fine-grained-audit-policies1.html
  110. https://www.oracle.com/security/database-security/audit-vault-database-firewall/
  111. https://blogs.oracle.com/cloudsecurity/post/sql-firewall-now-built-into-oracle-database-23c
  112. https://docs.oracle.com/en/database/oracle/oracle-database/21/asoag/introduction-to-transparent-data-encryption.html
  113. https://docs.oracle.com/en/database/oracle/oracle-database/21/dbseg/configuring-network-data-encryption-and-integrity.html
  114. https://docs.oracle.com/cd/B19306_01/network.102/b14268/asotrans.htm
  115. https://docs.oracle.com/en/database/oracle/oracle-database/23/dbtde/transparent-data-encryption.pdf
  116. https://docs.oracle.com/en/database/oracle/oracle-database/19/dbseg/configuring-secure-sockets-layer-authentication.html
  117. https://docs.oracle.com/en/database/oracle/oracle-database/23/shard/using-tcps-protocol-and-transport-layer-security.html
  118. https://docs.oracle.com/en/database/oracle/oracle-database/19/asoag/introduction-to-oracle-data-redaction.html
  119. https://docs.oracle.com/en/database/oracle/oracle-database/21/olsag/introduction-to-oracle-label-security.html
  120. https://www.oracle.com/security/database-security/label-security/
  121. https://blogs.oracle.com/database/oracle-ai-database-26ai-pqc
  122. https://docs.oracle.com/cd/A57673_01/DOC/server/doc/MIG73/apd.htm
  123. https://docs.oracle.com/en/database/oracle/oracle-database/21/arpls/DBMS_STATS.html
  124. https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/EXPLAIN-PLAN.html
  125. https://docs.oracle.com/en/database/oracle/oracle-database/21/cncpt/indexes-and-index-organized-tables.html
  126. https://docs.oracle.com/cd/A97385_01/server.920/a96520/indexes.htm
  127. https://docs.oracle.com/en/database/oracle/oracle-database/18/adjsn/indexes-for-json-data.html
  128. https://docs.oracle.com/en/database/oracle/oracle-database/26/arpls/DBMS_AUTO_INDEX.html
  129. https://docs.oracle.com/en/database/oracle/oracle-database/18/tgsql/joins.html
  130. https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/OPTIMIZER_ADAPTIVE_PLANS.html
  131. https://docs.oracle.com/cd/E11882_01/server.112/e41573/stats.htm
  132. https://docs.oracle.com/en/database/oracle/oracle-database/19/tdppt/automatic-database-performance-monitoring.html
  133. https://docs.oracle.com/en/database/oracle/oracle-database/23/tgdba/awr-report-ui.html
  134. https://www.oracle.com/enterprise-manager/
  135. https://docs.oracle.com/en/database/oracle/oracle-database/21/tgsql/sql-tuning-advisor.html
  136. https://docs.oracle.com/en/database/oracle/oracle-database/26/refrn/descriptions-of-wait-events.html
  137. https://docs.oracle.com/en/database/oracle/oracle-database/18/ntqrf/initialization-parameter-file-overview.html
  138. https://docs.oracle.com/en/database/oracle/oracle-database/19/tgdba/IO-configuration-and-design.html
  139. https://docs.oracle.com/en/database/oracle/machine-learning/oml4sql/23/mlsql/expectation-maximization-anomaly-detection.html
  140. https://www.oracle.com/database/data-analysis-oracle-database-23ai/
  141. https://threadgoldconsulting.com/research/most-popular-database-management-software-2025
  142. https://db-engines.com/en/blog_post/110
  143. https://www.oracle.com/news/announcement/lloyds-banking-group-expands-collaboration-with-oracle-to-support-tech-transformation-2025-03-20/
  144. https://group.bnpparibas/en/press-release/bnp-paribas-signs-a-partnership-with-oracle-to-further-develop-its-cloud-strategy
  145. https://www.oracle.com/news/announcement/mitsubishi-ufj-bank-collaborates-with-oracle-to-build-next-generation-platform-2025-04-22/
  146. https://blogs.oracle.com/apex/enhancing-oracle-fusion-applications-with-oracle-apex-getting-started
  147. https://www.oracle.com/integration/application-integration/
  148. https://www.cloudzero.com/blog/cloud-service-providers/
  149. https://www.oracle.com/news/announcement/oracle-database-at-azure-2023-09-14/
  150. https://news.microsoft.com/source/2024/03/14/microsoft-and-oracle-expand-partnership-to-satisfy-global-demand-for-oracle-databaseazure/
  151. https://techcommunity.microsoft.com/blog/oracleonazureblog/oracledatabaseazure-expands-footprint-to-31-regions-and-strengthens-security-wit/4471109
  152. https://www.oracle.com/cloud/azure/
  153. https://www.gartner.com/reviews/market/cloud-database-management-systems/vendor/oracle/product/oracle-database/alternatives
  154. https://www.gartner.com/reviews/market/cloud-database-management-systems/compare/amazon-web-services-vs-oracle
  155. https://www.oracle.com/webfolder/technetwork/tutorials/obe/db/12c/bigdatasql/bigdatasql_hol.html
  156. https://www.oracle.com/database/technologies/sql-analytics.html
  157. https://licensingoracle.com/oracle-license-cost-optimization-nine-themes-in-2025/
  158. https://www.enterprisedb.com/cost-savings-roi-moving-oracle-postgresql
  159. https://www.supportrevolution.com/resources/moving-away-from-oracle-database-in-2025-your-best-options/
  160. https://www.g2.com/products/oracle-database/reviews?qs=pros-and-cons
  161. https://dbplus.tech/en/2024/05/30/the-toughest-challenges-and-problems-with-oracle-database/
  162. https://www.gartner.com/reviews/market/strategic-cloud-platform-services/vendor/oracle/product/oracle-cloud-infrastructure/likes-dislikes
  163. https://www.optisolbusiness.com/insight/struggling-with-vendor-lock-in-why-postgresql-is-your-exit-strategy
  164. https://www.infoworld.com/article/2201363/beware-of-nosql-standards-in-oracle-s-clothing.html
  165. https://www.oracle.com/security-alerts/cpujul2010.html
  166. https://www.oracle.com/security-alerts/cpuoct2010.html
  167. https://www.theregister.com/2025/10/16/oracle_ai/
  168. https://www.gartner.com/reviews/market/cloud-database-management-systems/vendor/oracle/product/oracle-database/likes-dislikes
  169. https://estuary.dev/blog/oracle-database-alternatives/
  170. https://stackby.com/blog/best-database-software-for-for-small-business/
Add your contribution
Related Hubs
User Avatar
No comments yet.