ORA-600 / JAS-MIN / 0x600

A chart is not a diagnosis.

JAS-MIN + ORA-600. Oracle performance audits: data, evidence, internals and an action plan. No fortune-telling from a single chart.

JAS-MIN — Oracle Performance Evidence

Performance tuning
is not fortune-telling.

Your database needs people who understand what they are looking at. JAS-MIN — JSON AWR & Statspack Miner — is an Oracle performance analysis tool we develop. Our audits combine its capabilities with DBA and developer experience and knowledge of the database engine.

01 / DISTIL THE NOISE

Thousands of numbers.
A few useful questions.

We do not feed a pile of AWRs into a magic box. JAS-MIN organises measurements, models relationships and helps choose where to look deeper. This is how we distil signal from noise.

❯ ./jasmin --follow-the-evidenceDATA → Δ → MODELS → QUESTIONS
  1. [ data ]

    Check the input

    Measurement windows, load, waits and gaps. An empty entry does not always mean zero.

  2. Δ = now − before

    Calculate changes

    Ask how changes in statistics relate to load changes between adjacent windows. Not just which counter was largest.

  3. Δ → z

    Make scales comparable

    Centring and standardisation make differently scaled inputs comparable. Coefficients are then converted back to original units.

THE SAME PREPARED DATA

Four parallel perspectives. Not four successive filters.

Ridge / MODEL NOTES

Keep the multipliers in check.

Two statistics move almost together? Huge opposing coefficients can fit that history. Ridge penalises coefficient size to reduce sensitivity to those patterns.

This stabilises the fit. It does not prove which statistic causes the problem.

[ CHECK BEFORE USE ]

We check convergence, data quality and fit limitations. An ineligible result does not get a vote just because it looks convincing.

// MAGNITUDE BEFORE RANK

A gold medal for a tiny problem?

First place in a ranking does not tell you whether the problem is large. For major incidents we compare the model’s response to P99- and MAX-sized input changes; P90 provides a less extreme reference. Change the question and the leader may change.

Share % ≠ % DB TimeA share of that fit’s positive P90 score, not a measured share of database time.

Model score ≠ time recoveredIt is a lead to verify. We need the actual window, SQL, sessions and evidence of the mechanism.

02 / FOLLOW THE EVIDENCE

We don’t start
with “buy more CPU”.

We start by asking where the time goes — and why. This is the path from a bundle of reports to a decision you can justify.

  1. 0x01

    Context first.

    What slows down, when, and who is affected? We agree the audit goal, representative periods and data scope. We check snapshot coverage: a missing measurement is not evidence of a healthy system.

  2. 0x02

    Then the leads.

    JAS-MIN organizes AWR or STATSPACK reports and exposes trends, anomalies and relationships. We examine normal operation, busy periods and rare spikes. An average can do a great job of hiding a terrible Monday.

  3. 0x03

    Next: under the hood.

    We connect signals to SQL, execution plans, wait events, statistics and available logs. When needed, we agree additional measurements. Evidence separates a hypothesis from a cause — not a confident tone of voice.

  4. 0x04

    Finally: something actionable.

    You receive findings, evidence and priorities, plus risks and verification criteria for recommended changes. Implementation and environment testing are agreed separately. A report is not permission to modify production.

03 / WHAT’S UNDER THE HOOD

One TOP SQL list
won’t tell the whole story.

TIME / WORKLOAD

Where does the time go?

DB Time and DB CPU, workload, waits, I/O, instance and segment statistics. We separate periods and instances: one combined result can hide an important difference.

SQL / ENGINE

What is behind the symptom?

SQL cost and frequency, execution plans, child cursors, latches and mutexes — where the data supports assessment. If a plan or measurement is missing, we say what else is needed.

PATTERNS / OUTLIERS

Beyond the average.

Anomalies, correlations and regression models help prioritize leads. We compare typical workload behavior with the tail of the distribution. A model result is not a promise of seconds or money saved.

04 / DELIVERABLES, NOT DECORATIONS

A report for action.
Not for a drawer.

For the decision-maker: the problem, impact and order of actions. For the technical team: detail, linked evidence and clear limits to what is known. No need to guess what the author meant.

  • 01Findings and priorities
  • 02Charts and supporting evidence
  • 03Recommendations with risks
  • 04Before / after test criteria
  • 05Data gaps and open questions

05 / AI ASSISTED. HUMAN ACCOUNTABLE.

AI can help.
We own the conclusions.

Local calculations first, then a compact evidence package with its limitations. Optionally, AI can request specific evidence through MCP instead of drowning in thousands of reports. JAS-MIN helps ask better questions. We remain responsible for interpreting the answers.

We agree the data scope, transfer method and any use of an external model with you. JAS-MIN can analyze local reports; AI integration is optional. We review collected material for sensitive information — a masking setting does not replace that review.

Start with a conversation about the symptoms. Data sources depend on your environment, available measurements and license entitlements. Please do not send passwords or production dumps in the first email.

NEXT COMMAND / LET’S TALK

Got a problem?
You’re in the right place.

↗