Oracle Internals

  There's a tension that's existed in enterprise software for years. App developers want to work with JSON — it maps cleanly to how modern applications are built, it's flexible, and it's what most REST APIs speak natively. DBAs and architects, on the other hand, have good reasons to stick with relational models: referential integrity, normalized schemas, ACID transactions, and predictable query performance. The typical compromise involves some combination of ORMs, ETL pipelines, or storing JSON blobs in columns — none of which feels particularly clean. Oracle 23c takes a different approach with a feature called JSON Relational Duality Views, and it's one of the more genuinely interesting things to come out of this release. What it actually does The idea is straightforward once you see it. A duality view sits on top of your existing relational tables and exposes their data as JSON documents — but this isn't a one-way read-only projection. Applications can read, i...

This comes up more often than you'd think. You've done everything right —   STATISTICS_LEVEL   is set to   TYPICAL , you've gathered schema stats with   DBMS_STATS.GATHER_SCHEMA_STATS , and every table in the schema shows   MONITORING = YES   in   DBA_TABLES . But when you query   DBA_TAB_MODIFICATIONS , you get nothing back. The reason is simpler than most people expect. Oracle doesn't log every single DML change into that view. It only registers a table once the volume of changes clears a meaningful bar — somewhere around 10% of the table's data. One update, ten inserts, a handful of deletes — none of that is enough. The view is designed to help Oracle decide when statistics have gone stale, not to be a full audit trail. There's also a timing issue. Even when changes do cross the threshold, Oracle keeps that information in the SGA first and flushes it to the dictionary periodically — every 3 hours by default. So even if you've crossed the thresh...

Securing infrastructure remains critical aspects for everyone and for DBA that also means securing the database. This not just mean to secure your data written on disk (Encryption at rest) but also to secure your data which flows through network between client and network.  All leading Database providers comes up with TLS encryption for these in-flight transactions which secure the communication over the network. In this blog we will cover, how to enable TLS based encryption for Oracle Database.  There has been various blogs and sources of information to achieve this aspect but one may struggle to find a common place which list down all these activities at one place. I will try to consolidate them  which will includes steps for RAC and Standby as well. TLS is an incremental version of SSL version 3 and TLS1.2 is the latest one in the series. Using Oracle Database SSL provides:     1. Encrypt communication between client and server.     2. Authenticate ...

Artificial Intelligence and High-Performance Computing (HPC) workloads are fundamentally changing infrastructure requirements across enterprises. Traditional cloud architectures optimized for web applications often struggle with the networking demands of distributed AI training, large-scale simulations, and tightly coupled compute workloads. This is where Oracle Cloud Infrastructure (OCI) differentiates itself. OCI’s RDMA (Remote Direct Memory Access) cluster networking architecture is specifically engineered for low-latency, high-throughput computing environments. Instead of treating HPC as a secondary cloud use case, OCI was designed with performance-sensitive workloads as a core architectural priority. In this article, we’ll explore how OCI RDMA networking works, why it matters for HPC and AI workloads, and where organizations can achieve measurable performance improvements. Understanding the HPC Networking Problem Most cloud workloads are loosely coupled. Examples include: Web appl...