Oracle consulting · Consultative support · Remote DBA · Oracle Database, Exadata and Oracle Cloud
Oracle Consulting That Reads V$VERSION and DBA_FEATURE_USAGE_STATISTICS Before It Recommends Anything
MinervaDB Oracle consulting covers Oracle Database 19c, 21c and 26ai on commodity Linux, Oracle Database Appliance and Exadata, and every Oracle Cloud form from Base Database to Autonomous and Database@Azure, @AWS and @Google. The work is delivered by senior engineers who cite the V$, DBA_ or DBA_HIST_ view behind every finding, respect the licence boundary before running a query, write the blast radius and rollback before any change, and carry the 24×7 watch afterwards under your CSI. Vendor-neutral by principle: we are not an Oracle partner or reseller, so the recommendation can be to stay, to upgrade, to move to OCI, or to leave.
01 · Why MinervaDB for Oracle consulting
Oracle estates fail on lifecycle, licence and untested recovery long before they fail on the optimizer
Oracle Database is the most instrumented engine in production use. The failures we are called into are rarely mysteries in the engine; they are a 21c cliff nobody planned for, an option nobody meant to use, or a standby nobody has switched to.
Vendor-neutral
No licence resale, no partner incentives, no OCI margin. Oracle consulting recommendations are anchored in your AWR or STATSPACK data, your feature-usage delta and your support contract, including when the answer is Standard Edition 2, staying on 19c until 2029, or a staged exit to PostgreSQL.
Senior engineers only
Every engagement is led by principal-level Oracle DBAs who have run RAC on Exadata, reinstated failed primaries with Flashback, and read an audit letter with a customer. No junior bench learning on your time.
Licence boundary respected
CONTROL_MANAGEMENT_PACK_ACCESS is checked before any AWR or ASH query runs. On pack-free estates the same findings come from STATSPACK, V$SQLSTATS and V$SYSTEM_EVENT, so Oracle consulting never creates the exposure it was hired to remove.
Real 24×7 operations
Follow-the-sun coverage across APAC, EMEA and the Americas with a senior Oracle engineer on watch, S1 acknowledged within 15 minutes, SR management under your CSI, and every action timestamped in a shared incident system.
02 · Oracle consulting services
Six disciplines around the Oracle estate, one accountable team
Most Oracle consulting engagements start with the health check and grow into the discipline the evidence points at. All six are delivered by the same engineers, on-premises, on Exadata and on Oracle Cloud.
Figure 1. The MinervaDB Oracle consulting service map: architecture, performance, upgrades and migration, HA and DR, licensing and cost, and security, reliability and observability, entered through the health check and sustained by 24×7 consultative support and remote DBA.
Architecture and engineering
RAC versus Data Guard versus SEHA decided from measured availability needs and licence position; CDB and PDB design for 26ai; Exadata offload and IORM design; OCI landing zones with the exit path written first; and hands-on build and change work under a rollback.
Performance optimization
AWR, ASH and ADDM where licensed, STATSPACK and V$ sampling where not; SQL Plan Management to stop plan regressions rather than chase them; optimizer statistics and histogram hygiene; access-path and partitioning engineering; PGA, SGA and result-cache sizing from measured demand.
Upgrades, migration and modernization
19c to 26ai with AutoUpgrade, guaranteed restore points and a standby-first rehearsal; 21c exits before the July 2027 cliff; Zero Downtime Migration to OCI; Data Guard and GoldenGate cutovers; staged exits to PostgreSQL where per-core licensing no longer earns its keep. Data modernization →
High availability and disaster recovery
Data Guard broker with Fast-Start Failover and a third-site observer, Maximum Availability locally and Maximum Performance across regions, RMAN with block change tracking and monthly RESTORE VALIDATE, Flashback for reinstatement, and a drill calendar that produces measured RPO and RTO.
Licensing awareness and cost optimization
Feature-usage baseline and delta on every takeover, Enterprise Edition core right-sizing against measured CPU, SE2 with SEHA for fit-for-purpose workloads, BYOL versus licence-included and ECPU economics on OCI, and the support cliffs written into the business case.
Consultative support and remote DBA
24×7 senior coverage, SR management under your CSI, quarterly RU and monthly MRP calendar with out-of-place patching from gold images, backup verification and timed restores, and a monthly SLO report. 24×7 consultative support →
03 · Oracle consulting method
Baseline, attribute, change, validate: how the work is measured, inside the licence boundary
Oracle tells you where DB time goes. The method is to read that before touching anything, change one thing under SQL Plan Management, and re-measure against the same snapshots.
Figure 2. The Oracle performance engineering method and the evidence surface behind it, with the Diagnostics Pack boundary and the pack-free alternatives that produce the same findings.
An Oracle consulting baseline is a window of AWR or STATSPACK snapshots that includes month-end and batch peaks: DB time by SQL_ID, wait-class distribution, top segments by logical and physical I/O, redo volume, Data Guard transport and apply lag, and I/O latency per file. Attribution names the constraint from the wait class and the plan: a plan-hash change, a cardinality misestimate, bind sensitivity, a missing storage-index benefit on Exadata, or simply a cluster wait that a service placement change removes.
Changes are made one at a time and are reversible: a SQL plan baseline that can be dropped, a statistics gather with the previous statistics restorable from DBA_TAB_STATS_HISTORY, an index built ONLINE, a parameter with its scope and restart requirement stated. Blast radius and rollback are written before execution, and destructive steps carry a confirmation gate.
-- Licensed estate (Diagnostics Pack):
-- top SQL by DB time over the last 7 days of AWR
SELECT s.sql_id,
ROUND(SUM(s.elapsed_time_delta) / 1e6, 1) AS elapsed_s,
ROUND(SUM(s.cpu_time_delta) / 1e6, 1) AS cpu_s,
SUM(s.executions_delta) AS execs,
ROUND(SUM(s.buffer_gets_delta)
/ NULLIF(SUM(s.executions_delta), 0)) AS gets_per_exec,
COUNT(DISTINCT s.plan_hash_value) AS plans -- >1: unstable
FROM dba_hist_sqlstat s
JOIN dba_hist_snapshot n
ON n.snap_id = s.snap_id
AND n.dbid = s.dbid
AND n.instance_number = s.instance_number
WHERE n.begin_interval_time >= SYSDATE - 7
GROUP BY s.sql_id
ORDER BY elapsed_s DESC
FETCH FIRST 20 ROWS ONLY;
-- Pack-free estate: the same view of the shared pool,
-- no Diagnostics Pack exposure
SELECT sql_id, plan_hash_value, executions,
ROUND(elapsed_time / 1e6, 1) AS elapsed_s,
ROUND(buffer_gets / NULLIF(executions, 0)) AS gets_per_exec
FROM v$sqlstats
ORDER BY elapsed_time DESC
FETCH FIRST 20 ROWS ONLY; 04 · Oracle consulting for HA and DR
Data Guard engineered as a topology and proven by a drill calendar
A standby that has never been switched to is an assumption. Oracle consulting at MinervaDB designs the topology, then exercises it on a calendar so the RPO and RTO in the runbook are observed numbers.
Figure 3. Oracle consulting HA and DR reference topology: role-based services and pools, RAC or SEHA primary, synchronous standby with Fast-Start Failover, asynchronous cross-region standby, Data Guard broker and observer, RMAN and Flashback, and the drill calendar.
| Cadence | Drill | Evidence artefact |
|---|---|---|
| Continuous | Data Guard transport and apply lag against the RPO budget | V$DATAGUARD_STATS, DGMGRL SHOW CONFIGURATION LAG, alert history |
| Monthly | RESTORE VALIDATE and corruption sweep | RMAN log, V$DATABASE_BLOCK_CORRUPTION |
| Quarterly | Full restore and recover to a point in time on a scratch host, timed | Restore report with RTO and RPO measured on production-size data |
| Quarterly | Data Guard switchover through the broker, then switch back | DGMGRL transcript, service start and application reconnect timings |
| Per RU | Guaranteed restore point created before patching, dropped after verification | V$RESTORE_POINT before and after, standby-first patch log |
RAC or Data Guard, decided by the failure
Oracle consulting answers this from the failure mode: RAC protects against node loss with no service interruption for connected sessions that use Application Continuity; Data Guard protects against site, storage and logical failure. Most estates need Data Guard first, RAC where the availability target and the licence position justify it, and SEHA on Standard Edition 2 where it does not.
Fast-Start Failover without surprises
The observer runs on a third site, FastStartFailoverThreshold and the lag limit are set from the measured network, and the reinstatement of the old primary with Flashback is rehearsed, because the failover that fails is the one where the old primary cannot be brought back as a standby.
Standby-first patching
In MinervaDB Oracle consulting every quarterly RU is applied to the standby first from a gold image, out of place, followed by a broker switchover and the same on the former primary, with a guaranteed restore point at each step. Downtime is the switchover, and the fallback is a role change, not a restore.
05 · Oracle consulting for versions and patching
Oracle Database release streams and support dates we plan against
Verified against Oracle's Lifetime Support Policy and MOS note 742060.1 on 28 September 2026, and re-verified under your CSI at the start of every Oracle consulting engagement. The dates below decide the sequence of every upgrade programme.
Figure 4. Oracle consulting release calendar: Oracle Database release streams, patch streams, Exadata and Oracle Cloud lifecycle status as verified on 28 September 2026, and what each means for the estate.
| Release or stream | Current state | Lifecycle | What we do about it |
|---|---|---|---|
| Oracle Database 19c (Long Term) | Quarterly RUs, 19.32 in July 2026; monthly MRPs on Linux x86-64; the 19.28 Long Term RU's MRPs end January 2027 | Premier Support to 31 December 2029; Extended Support to 31 December 2032 with the uplift payable from 1 January 2030 | Stay on the latest RU rather than 19.28; plan the 26ai upgrade or an exit assessment before 2029, both full projects on commodity servers |
| Oracle Database 21c (Innovation) | Quarterly RUs plus CSPU security bundles | Premier Support ends 31 July 2027; no Extended Support | Hard cliff: upgrade to 26ai (19c is backwards) or exit before mid-2027 |
| Oracle AI Database 26ai (Long Term) | Quarterly RUs and monthly MRPs; on-premises Linux GA 27 January 2026; 23ai installs became 26ai through the October 2025 RU | Premier Support published to 31 December 2031 | The upgrade target; CDB-only, so non-CDB 19c estates convert during AutoUpgrade with the PDB plug-in rehearsed first |
| Patch streams | RU on the third Tuesday of January, April, July and October; MRP monthly on Linux x86-64 for 19c and 26ai; CSPU security-only elsewhere and on 21c | RURs discontinued since 2022; Long Term RU programme paused | "n-1 RU" policies are stale: latest RU, out of place from gold images, guaranteed restore point first, standby first |
| Exadata | X11M; ExaDB-D, ExaDB-XS on Exascale, Cloud@Customer; 19c and 26ai supported | Quarterly bundles; Oracle patches cells and dom0 on the cloud forms | Coordinate Grid Infrastructure and database patching with Oracle's infrastructure windows; exachk before every bundle |
| Oracle Cloud | Base Database on 19c, 21c and 26ai; Autonomous on 26ai with 19c instances on a scheduled upgrade path; Database@Azure, @AWS and @Google | Service-managed cadence; Autonomous upgrades on Oracle's schedule | Map each workload to the service whose divergence it can live with; the exit path is written before the migration starts |
Sources: Oracle Lifetime Support Policy for Technology Products and the Release Update 19.32 notes. Confirm the exact RU and MRP under your CSI at engagement start; Oracle publishes a new RU every quarter.
06 · Exadata and Oracle Cloud · Oracle consulting
Prove the offload you paid for, and pick the cloud form whose divergence you can live with
Exadata is bought for Smart Scan, storage indexes, Flash Cache and RAC consolidation; Oracle Cloud is a portfolio in which each service removes a different share of the DBA work and takes a different share of control. Oracle consulting measures the first and maps the second.
Figure 5. Exadata architecture as reviewed in an Oracle consulting audit, the responsibility split by layer on-premises, on ExaDB-D and Cloud@Customer, and on Autonomous, and the Oracle Cloud service map of what you keep and what you give up.
On Exadata, Oracle consulting answers one question first: is the workload actually offloading? Cell statistics in V$SYSSTAT compare bytes eligible for predicate offload with interconnect bytes returned by Smart Scan and bytes saved by storage index; Flash Cache read hits and IORM metrics from cellcli show whether consolidation is fair; exachk findings are cleared before every quarterly bundle. Direct-path reads, HCC ratios and the statements that fall back to block shipping are listed per SQL_ID.
On ExaDB-D, ExaDB-XS and Cloud@Customer the split is explicit: Oracle operates cells, dom0 and the fabric; MinervaDB operates Grid Infrastructure, the databases, the RUs and the drills, inside Oracle's infrastructure windows.
-- Exadata: is the workload offloading? (V$SYSSTAT cell statistics) SELECT name, ROUND(value / POWER(1024, 3), 1) AS gb FROM v$sysstat WHERE name IN ( 'physical read total bytes', 'cell physical IO bytes eligible for predicate offload', 'cell physical IO interconnect bytes returned by smart scan', 'cell physical IO bytes saved by storage index', 'cell flash cache read hits') ORDER BY name;
On Oracle Cloud, Base Database keeps root and SYSDBA and removes none of the DBA work; ExaDB-D keeps the database layer and hands the infrastructure to Oracle; Autonomous takes the operations and the SYS account with it and bills in ECPUs. Database@Azure, @AWS and @Google put OCI-managed Exadata inside the hyperscaler's data centre, which makes latency to the application tier the design question. Migration runs through Zero Downtime Migration or Data Guard with a rehearsed cutover and a fallback that is timed before the window.
07 · Oracle consulting for licensing awareness and cost
Oracle cost is licence cost, and the most valuable hour of Oracle consulting is the feature-usage delta
On every takeover MinervaDB snapshots DBA_FEATURE_USAGE_STATISTICS and delivers the delta in writing before changing anything, so you see which options and packs the estate is consuming before an audit letter shows you.
Figure 6. Oracle consulting licence and cost engineering: the feature-usage baseline, the classic accidental-option findings, edition and core right-sizing, the support cliffs in the business case, cloud economics and exit economics.
The classic findings
A standby opened read-only with apply running (Active Data Guard); INMEMORY_SIZE set without INMEMORY_FORCE = BASE_LEVEL; partitioned tables on an estate that never bought Partitioning; more than three user PDBs per CDB without Multitenant; AWR reports run with CONTROL_MANAGEMENT_PACK_ACCESS = NONE; OLTP compression or TDE enabled without the option.
Editions, cores and cliffs
Oracle consulting right-sizes Enterprise Edition cores against measured CPU, fit-for-purpose workloads moved to Standard Edition 2 with SEHA, core-factor and hard-partitioning rules checked on VMware and cloud, and the lifecycle dates written into the business case: 21c has no Extended Support after 31 July 2027, 19c pays the uplift from 1 January 2030, 26ai runs to the end of 2031.
Cloud and exit economics
BYOL versus licence-included, ECPU on Autonomous and OCPU on Base and ExaDB, Universal Credits commitments and their expiry, and Database@hyperscaler pricing modelled from measured utilisation. Where a schema is fit for purpose elsewhere, a staged PostgreSQL exit is scored per object and run beside the Oracle estate that must stay. Cloud database FinOps →
MinervaDB provides licensing awareness from the database's own usage views; it is not legal or contractual advice, and the contract, ULA or cloud agreement governs. We work alongside your licensing counsel and prepare the technical evidence they need.
08 · Oracle consulting for security, reliability and observability
Controls, SLIs and monitoring that do not create pack exposure
Oracle consulting at MinervaDB configures the controls and the evidence they generate together, and builds observability from V$ views and Enterprise Manager base features unless the packs are licensed.
Data security and compliance
Least-privilege roles and profiles, Transparent Data Encryption with a wallet or OKV key-management record, Database Vault where separation of duties is required, Unified Auditing retained for the compliance window, network encryption enforced, and the evidence pack for GDPR, HIPAA, PCI DSS, SOX and SOC 2 produced as a by-product of operations.
Data reliability engineering
Oracle consulting for reliability sets SLIs on DB time per transaction, Data Guard lag, backup success and restore time, and tablespace and ASM diskgroup headroom; error budgets per service; runbooks for switchover, restore, patching and PDB operations with a verification query before and a validation query after every destructive step; chaos drills on the calendar above.
Observability and monitoring
Oracle consulting for observability uses Enterprise Manager base monitoring or Prometheus exporters against V$ views, alert thresholds tuned to the workload rather than the template, wait-class and DB-time dashboards, and pack-aware collection so a monitoring query never turns into a Diagnostics Pack finding.
09 · Oracle health check and performance audit
The fixed-scope entry point to Oracle consulting at MinervaDB
Read-only, evidence-based, delivered as findings your own DBAs can verify, and priced per database. No change is made to production during the audit.
What is reviewed
Oracle consulting audits cover version, RU and MRP currency; initialisation parameters against workload and hardware; the wait profile and top SQL by DB time; plan stability and SQL Plan Management use; optimizer statistics and histogram health; segment and tablespace growth; RAC interconnect and service placement; Data Guard configuration and lag; RMAN strategy and restore evidence; feature usage against licence; security posture; and, on Exadata, offload efficiency and IORM.
What you receive
Findings ranked P0 to P2, each with the observation, the V$, DBA_ or DBA_HIST_ evidence, the recommended change with its rollback and the metric it is expected to move; the feature-usage delta in writing; a prioritised remediation plan; and a versioned report your team keeps whether or not MinervaDB does the remediation. Oracle Database health check: US $15,500 per database. Exadata and RAC health checks are scoped per estate.
Standing caveat: every recommendation on this page is tested on a non-production copy against production-representative data before it is applied to a production system, with a verified RMAN backup and a guaranteed restore point taken first and a disaster-recovery posture exercised by a timed restore.
10 · Oracle consulting rates
Transparent Oracle consulting rates
MinervaDB operates as a virtual corporation, so what you pay goes to Oracle engineering talent rather than office overhead. Emergency support is included in every retainer.
Remote consulting · $300 per hour
Hourly Oracle consulting: performance optimization, RAC and Data Guard design, Exadata and OCI advisory, SQL Plan Management, RU patching, AutoUpgrade and ZDM planning, RMAN and DR strategy, delivered remotely worldwide and available on short notice.
Remote DBA retainer · from $4,500 per quarter
Oracle consulting on retainer with ongoing remote DBA operations and a four-hour monthly minimum: 24×7 monitoring and alerting, incident response and SR management under your CSI, root-cause analysis, quarterly RU and monthly MRP management, backup verification and restore drills, and a monthly SLO report. Emergency support always included.
On-site consulting · $500 per hour
Architecture and strategy sessions, Exadata and OCI workshops, executive and engineering briefings, implementation and cutover presence, team training and on-site incident response, available in 46 cities worldwide. Travel applies.
11 · FAQ
Oracle consulting questions we are asked most
Short answers to what DBAs, architects and CIOs ask before the first call.
Which Oracle platforms does MinervaDB Oracle consulting cover?
Oracle Database 19c, 21c and 26ai on commodity Linux and Windows, Oracle Database Appliance, Exadata on-premises and Cloud@Customer, and every Oracle Cloud form: Base Database, ExaDB-D, ExaDB-XS on Exascale, Autonomous Database, and Database@Azure, @AWS and @Google. RAC, Data Guard, SEHA, GoldenGate and RMAN are covered on all of them.
What does an Oracle consulting engagement include?
A discovery call on estate, versions, HA posture, licence position and pain points, then a scoped engagement: a health check, an architecture or HA review, an upgrade or OCI migration plan, a licence and cost baseline, or ongoing consultative support and remote DBA. Every engagement ends with written deliverables that cite the V$, DBA_ or DBA_HIST_ view behind each finding, changes with rollback, and an action plan with the metric each item is expected to move.
How much does Oracle consulting cost?
Remote Oracle consulting is $300 per hour and on-site consulting is $500 per hour with travel applying. Remote DBA retainers start at $4,500 per quarter with a four-hour monthly minimum and emergency support included. An Oracle Database health check is US $15,500 per database; Exadata and RAC health checks are scoped per estate.
We are on Oracle Database 19c. Do we need to upgrade now?
Not immediately: 19c Premier Support runs to 31 December 2029 and Extended Support to 31 December 2032 with an uplift from 1 January 2030. What you do need now is to stay on the latest quarterly RU (19.32 as of July 2026) rather than the 19.28 Long Term RU, whose MRPs end in January 2027, and to plan the 26ai upgrade or an exit assessment so it is a project, not an emergency, before 2029.
Our databases are on 21c. What is the urgency?
High. Oracle Database 21c Premier Support ends on 31 July 2027 and there is no Extended Support. Upgrade to 26ai (19c would be a downgrade) or exit before mid-2027, with AutoUpgrade, a guaranteed restore point and a standby-first rehearsal.
Do you recommend RAC or Data Guard?
It depends on which failure you are protecting against and what the licence position allows. Data Guard protects against site, storage and logical failure and is the first thing most estates need; RAC protects against node loss for connected sessions and is justified where the availability target and Enterprise Edition licensing support it; SEHA gives Standard Edition 2 estates node failover without RAC. The decision is written down with the measured availability need behind it.
Can you help with Oracle licensing and cost?
Yes, from the database's own evidence: a DBA_FEATURE_USAGE_STATISTICS baseline and delta, Enterprise Edition core right-sizing against measured CPU, SE2 with SEHA where it fits, BYOL versus licence-included and ECPU economics on OCI, and the support cliffs in the business case. This is technical licensing awareness, not legal advice; we work alongside your licensing counsel.
Is Autonomous Database a good fit for us?
It is a good fit for workloads that can live with Oracle owning SYS, operations and the upgrade schedule, that bill sensibly in ECPUs, and that have an exit path through Data Pump or GoldenGate written before migration. It is a poor fit for workloads that need OS access, unsupported features or a patch cadence you control. The assessment says which, per workload.
How does MinervaDB Oracle support relate to Oracle Support?
MinervaDB engineers operate the estate and manage service requests under your own CSI; Oracle Support supplies patches and bug fixes. We are not an Oracle partner or reseller, so our recommendations carry no commission and can include leaving Oracle where that is the right answer.
How quickly can an Oracle consulting engagement start?
A health check can start within days of read-only access being granted; remote DBA coverage typically goes live inside the first month after a takeover pack (inventory, feature-usage baseline, backup verification, monitoring) is complete. Emergency engagements are handled under the S1 fifteen-minute acknowledgement target.
Talk to a senior Oracle consulting engineer
Bring an AWR or STATSPACK report from a peak window, the output of DBA_FEATURE_USAGE_STATISTICS, the last incident timeline and your support renewal to the first call. We will tell you which layer is the constraint, what the lifecycle dates mean for your estate, and what we would change first.