35+ YEARS IN MARKET
Continuously operating since 1990. 25,000+ consulting hours delivered and 596+ critical production incidents resolved. Pattern recognition only decades of real operation can build.
ORACLE PERFORMANCE TUNING — SINCE 1990
When the report that used to run in 3 minutes takes 40, the problem is rarely hardware. It's plan instability, stale stats, the wrong index, or a wait event hidden inside the AWR. We find it.
Certified Oracle DBAs trusted by
THE EASY DIAGNOSIS
The vendor says: upgrade the license
Each extra core on Oracle Enterprise costs a fortune. If the query is still doing a full table scan on 200M rows, more CPU just burns money faster.
Internal DBA focuses on what's visible
Top SQL by CPU, top SQL by elapsed. But the real bottleneck is in latch: cache buffers chains, in a hot block serializing the entire application. Without 30 days of historical ASH, no one sees it.
Plan flipping in production
Query ran fast for 3 months. Stats were gathered in a bad window, the CBO changed the plan, and now it takes the database down at 8 AM. Bind peeking, adaptive cursor sharing, plan baselines — who masters them?
HTI reads the AWR before the meeting ends
Send the AWR and ASH report. In 24h we return root cause, proposed fix and estimated gain. No need to give us access just to discover the problem.
TECHNICAL SCOPE
Not "rebuild index and review init parameter". Quantitative wait-event analysis, workload segmentation by service, and a fix with proven reduction measured in comparative AWR.
AWR snapshot-by-snapshot reading, baseline vs incident comparison, wait-class segmentation (User I/O, Concurrency, Cluster). We catch what ADDM ignores.
Capture, evolution and lock-in of stable plans with SPM. We end plan flipping caused by bind peeking or volatile stats. Adaptive features under control.
Diagnosis of gc current block busy, gc cr block lost, cross-instance enqueues. Service rebalancing per instance. Cache fusion under real load, not a whitepaper.
Diskgroups with hot spots, badly multiplexed redo logs, ASMM vs AMM. I/O optimization without changing storage — using what's already paid for.
Partition pruning strategy, local vs global indexes, bitmap in DW, IOT in lookup. When partition exchange saves the ETL and when it hurts OLTP.
11g→19c with no plan regression. Optimizer_features_enable, pre-migration SQL Plan Baselines, workload capture with SQL Tuning Sets. Upgrade without an all-nighter.
ORACLE AMEC — ONLY ONE IN BRAZIL
Not an analyst who learned Oracle during quarantine. A team that's been training Oracle DBAs since before 9i, in a controlled physical room at PIT/SP.
35 years reading AWR. The wait-event pattern that looks new to you is, to us, a variant of something we saw in 2008.
MEASURED RESULTS
MAJOR RETAILER
Monthly close
Accounting close query on Oracle 19c cut from 40 minutes to 90 seconds with SQL Plan Baseline + correlated subquery rewrite.
FINANCIAL INSTITUTION
4-node RAC
Eliminated gc current block busy on a 4-node RAC via service rebalance and hash partitioning. Average CPU dropped from 85% to 25%.
PUBLIC SECTOR
Upgrade 11g → 19c
Migration from Oracle 11.2.0.4 to 19c on a 12TB environment with no rollback and no plan regression, using SPA + SPM + pre-captured STS.
METHODOLOGY
AWR/ASH collection
You send AWR (1 week, 1h interval) + ASH report from the problem window + alert.log from the last 30 days. No environment access required.
Technical diagnosis
Wait-class segmentation, top SQL by DB time analysis, plan-flip / latch / enqueue identification. Report with documented root cause.
Prioritized fix plan
Fixes ordered by ROI: what returns 80% of the gain with 20% of the risk. Impact estimate based on measurement, not opinion.
Supervised rollout
Staging implementation with comparative SPA, validation, production deploy with rollback plan. Post-fix AWR proves the gain.
FAQ
No. The initial diagnosis runs on AWR report, ASH report and alert.log that you generate and send. We only request access when the fix enters staging — and even then with a restricted, audited user revoked at project end.
Both. On Standard Edition the toolset is smaller (no native AWR, no partitioning), so we use Statspack, V$ views and compatible strategies. The gain is often larger because most SE environments are deeply under-optimized.
With SQL Plan Management (SPM). We capture the optimized plan, lock it as an accepted baseline, and any new plan only reaches production if it's provably better. Immune to bad stats collection or bind peeking changes.
We guarantee diagnosis with documented root cause. In 95% of AWRs submitted over the past 5 years, we delivered at least 30% reduction in CPU or elapsed time on the target query. When it's not possible, we say so upfront — no charge for the fix.
Yes. OCI Autonomous, OCI Base Database, AWS RDS for Oracle and Azure Database for Oracle. Tools change (OEM vs Performance Insights vs CloudWatch); diagnosis principles do not.
20 minutes with a Senior Oracle DBA. You send the AWR, we return the technical diagnosis. No sales form, no 30-page proposal.
Versions and editions covered
WHY HTI
Sustaining critical environments in Brazil since 1990. We're not a generic consultancy that learned databases — we are The Database Company.
Continuously operating since 1990. 25,000+ consulting hours delivered and 596+ critical production incidents resolved. Pattern recognition only decades of real operation can build.
The only MySQL Authorized Education Center (AMEC) of Oracle University in Brazil — achieved twice. Over 1,000 DBAs trained in official HTI courses.
DBAs operate from a restricted-access room at PIT São José dos Campos: 24h CCTV, biometric access, dedicated rack. No remote freelancers, no improvised workstations. Compliance that goes beyond internal policy.
Behavioral monitoring developed in-house. Detects anomalous ingestion patterns and access to protected objects — no third-party tool dependency.