The unique problem · The green dashboard trap
The backup job has completed nightly for four years. The standby says it is shipping and applying. The alert count is high, but the team has learned which ones to ignore. None of that is evidence. It is the absence of a failure that has not happened yet.
The failure mode is always the same. The estate runs quietly, so nobody schedules a look at it. There is no renewal date, no end-of-support deadline, no auditor asking — nothing external forces the check. The first real test is the outage, and by then you are finding out and fixing at the same time.
That is what makes this different from an upgrade or a migration. Those have a date on them. This one has nothing, until it has everything.
What the dashboard shows
— not on the dashboard —
Why teams skip it
Teams do not skip this because they are careless. They skip it because every incentive points elsewhere, and because the estate keeps behaving.
No deadline
Upgrades have an end-of-support date. Licences have a renewal. An estate that runs has neither, so it never reaches the top of anyone’s list.
Who would check it
They already know it works. Asking them to prove it reads as distrust, so nobody asks.
Needs a window
Everyone knows they should. Booking downtime to prove something that is probably fine never wins against shipping a release.
What usually triggers the call
The DBA who holds the estate resigns, or goes on long leave. An auditor asks for evidence of a tested restore. A near-miss recovers, but too slowly. A new CIO asks a question nobody can answer with a document. Only the first is a choice.
The stakes
An untested restore does not fail quietly. It fails at 02:00, on the database that carries the business, with the whole company watching — and the discovery and the fix arrive in the same hour.
One week, fixed scope, nothing in production is changed. You get a list, ranked, with what it costs to fix. You decide the order.
Unbounded. Every decision made under time pressure, by whoever is awake, with no baseline to compare against.
The point of the review
The cheapest moment to find out is any moment that is not an incident. Same findings. Different night.
Product · 03
A one-week, fixed-scope review of what you are actually running — and an honest verdict on whether you need a managed service at all.
Scope: full estate inventory · one restore actually performed · €2,900 fixed
Every assessment is led and signed off by a senior Oracle DBA — 10+ years in production. The verdict is never delegated.
What you'll get — five deliverables
Select a deliverable to exploreTap a deliverable to explore
What we do
Versions, patch levels, parameters, dependencies. What is running, not what the documentation says is running.
What this will feel like
The estate on the page may not match the estate your team believes it is running. Old versions, forgotten parameters and undocumented dependencies tend to surface together. Seeing that gap written down can feel untidy. It is also the first time everyone is working from the same map. And one rule holds for the entire engagement: you can stop it at any point, for any reason. Everything verified up to that moment is documented — and it’s yours.
You can stop here. Fixed scope and fixed price, in writing, before this starts. Nothing runs until you approve it.
What we do
How many alerts a day you receive, and how many of them actually mean something.
What this will feel like
The number may show that your team has learned to ignore most of what the monitoring sends. That can feel like criticism of the people carrying the pager. It is not. The result separates alert fatigue from individual performance and gives the team a signal they can trust again. And one rule holds for the entire engagement: you can stop it at any point, for any reason. Everything verified up to that moment is documented — and it’s yours.
You can stop here. Fixed scope and fixed price, in writing, before this starts. Nothing runs until you approve it.
What we do
On a critical database. Not a backup log review. A restore.
What this will feel like
A real restore asks for a controlled window and removes the comfort of a green backup log. If it works, you leave with evidence. If it does not, the failure happens during a planned test with time to fix it — not during the incident that needed the backup. And one rule holds for the entire engagement: you can stop it at any point, for any reason. Everything verified up to that moment is documented — and it’s yours.
You can stop here. Fixed scope and fixed price, in writing, before this starts. Nothing runs until you approve it.
What we do
With what we would fix first and roughly what it costs.
What this will feel like
Not every finding will deserve immediate work. Ranking them means some familiar problems move down the list while one quiet risk moves to the top. That prioritisation can challenge the current plan, but it gives every decision an explicit reason and an approximate cost. And one rule holds for the entire engagement: you can stop it at any point, for any reason. Everything verified up to that moment is documented — and it’s yours.
You can stop here. Fixed scope and fixed price, in writing, before this starts. Nothing runs until you approve it.
What we do
Manage it in-house, hire someone, or outsource. Whichever the evidence supports.
What this will feel like
The verdict may be that you do not need a managed service. It may be that the team needs one hire, a short remediation project, or outside ownership. The uncomfortable part is giving up the preferred answer. The useful part is leaving with an answer the evidence can defend. And one rule holds for the entire engagement: you can stop it at any point, for any reason. Everything verified up to that moment is documented — and it’s yours.
You can stop here. Fixed scope and fixed price, in writing, before this starts. Nothing runs until you approve it.
What we do
Versions, patch levels, parameters, dependencies. What is running, not what the documentation says is running.
What this will feel like
The estate on the page may not match the estate your team believes it is running. Old versions, forgotten parameters and undocumented dependencies tend to surface together. Seeing that gap written down can feel untidy. It is also the first time everyone is working from the same map. And one rule holds for the entire engagement: you can stop it at any point, for any reason. Everything verified up to that moment is documented — and it’s yours.
You can stop here. Fixed scope and fixed price, in writing, before this starts. Nothing runs until you approve it.
What we do
Versions, patch levels, parameters, dependencies. What is running, not what the documentation says is running.
What this will feel like
The estate on the page may not match the estate your team believes it is running. Old versions, forgotten parameters and undocumented dependencies tend to surface together. Seeing that gap written down can feel untidy. It is also the first time everyone is working from the same map. And one rule holds for the entire engagement: you can stop it at any point, for any reason. Everything verified up to that moment is documented — and it’s yours.
You can stop here. Fixed scope and fixed price, in writing, before this starts. Nothing runs until you approve it.
What we do
How many alerts a day you receive, and how many of them actually mean something.
What this will feel like
The number may show that your team has learned to ignore most of what the monitoring sends. That can feel like criticism of the people carrying the pager. It is not. The result separates alert fatigue from individual performance and gives the team a signal they can trust again. And one rule holds for the entire engagement: you can stop it at any point, for any reason. Everything verified up to that moment is documented — and it’s yours.
You can stop here. Fixed scope and fixed price, in writing, before this starts. Nothing runs until you approve it.
What we do
On a critical database. Not a backup log review. A restore.
What this will feel like
A real restore asks for a controlled window and removes the comfort of a green backup log. If it works, you leave with evidence. If it does not, the failure happens during a planned test with time to fix it — not during the incident that needed the backup. And one rule holds for the entire engagement: you can stop it at any point, for any reason. Everything verified up to that moment is documented — and it’s yours.
You can stop here. Fixed scope and fixed price, in writing, before this starts. Nothing runs until you approve it.
What we do
With what we would fix first and roughly what it costs.
What this will feel like
Not every finding will deserve immediate work. Ranking them means some familiar problems move down the list while one quiet risk moves to the top. That prioritisation can challenge the current plan, but it gives every decision an explicit reason and an approximate cost. And one rule holds for the entire engagement: you can stop it at any point, for any reason. Everything verified up to that moment is documented — and it’s yours.
You can stop here. Fixed scope and fixed price, in writing, before this starts. Nothing runs until you approve it.
What we do
Manage it in-house, hire someone, or outsource. Whichever the evidence supports.
What this will feel like
The verdict may be that you do not need a managed service. It may be that the team needs one hire, a short remediation project, or outside ownership. The uncomfortable part is giving up the preferred answer. The useful part is leaving with an answer the evidence can defend. And one rule holds for the entire engagement: you can stop it at any point, for any reason. Everything verified up to that moment is documented — and it’s yours.
You can stop here. Fixed scope and fixed price, in writing, before this starts. Nothing runs until you approve it.
How the engagement runs
Read-only discovery.
Your DBA sees every query we run. Production is never touched.
Reproduction on a replica.
Findings become evidence instead of opinions — with a short note after each session.
The verdict session.
Go/no-go, the evidence behind it, and the roadmap — walked through live, with your team in the room.
Timeline is set at scoping, in writing, with the quote — it scales with your estate, not with our calendar.
Get started
60 minutes. Free. No pitch. You talk to the senior DBA who would run your assessment — not a salesperson.
What to bring
Your Oracle version(s), rough estate size, and your deadline. That’s enough.
What happens on the call
We ask about your migration window, your known risks, and what ‘verified’ needs to mean in your environment. You ask anything — including how we’d handle your specific setup.
What you leave with
A straight answer on whether this assessment fits your situation — including ‘it doesn’t.’ If it doesn’t, we say so on the call and you’ve lost an hour, not a budget.
Prefer email? hello@oracraft.com
Request sent
We’ll be in touch shortly to schedule your scoping call. hello@oracraft.com.