Representative engagements
Client names are withheld under confidentiality agreements; the problems, the approach and the outcomes are exactly as delivered.
RAC stabilisation and Data Guard DR for a regional bank
Challenge
A two-node RAC cluster behind core banking suffered recurring node evictions, and the disaster-recovery site had never been failover-tested — a regulatory finding waiting to happen.
What we did
Root-caused the evictions to interconnect and ASM configuration, re-engineered the cluster, built a physical standby with Data Guard, and ran documented switchover drills with the bank's team.
Outcome
Zero unplanned cluster outages in the twelve months after remediation; DR switchover demonstrated in under fifteen minutes; audit finding closed.
On-premises Oracle estate migrated to Oracle Cloud
Challenge
Ageing hardware, an expiring data-centre contract and an ERP database that had to move with minimal downtime and no licence surprises.
What we did
Assessment and licensing review, target architecture on OCI Base Database, GoldenGate-based replication for a near-zero-downtime cutover, and post-migration tuning.
Outcome
Cutover completed in a weekend window with under thirty minutes of downtime; infrastructure cost reduced versus the renewal quote; operations continued under managed support.
Claims analytics and renewal-retention modelling for an insurer
Challenge
Rising claims leakage and falling renewal rates, with years of policy and claims data that reporting described but never explained.
What we did
Built an analytics foundation over the claims and policy systems, delivered a claims-anomaly model and a renewal-propensity model, and trained the client's analysts to operate them.
Outcome
Flagged claims prioritised for review; renewal outreach targeted by propensity score; the client's team carrying the models forward independently.
In-house DBA team replaced by 24×7 managed support for a SaaS provider
Challenge
A software company hosting Oracle databases for its own customers depended on a single DBA — no night cover, no leave cover, and no documentation.
What we did
Onboarded all production databases with a full health check, set up monitoring and escalation, documented every environment, and assigned a named engineer backed by the 24×7 team.
Outcome
Round-the-clock cover from month one; incident response times inside SLA; the company's engineers back on product work instead of database firefighting.
Have a similar situation?
Describe it in a few lines; we'll tell you how we'd approach it and what it would take.