Overview
This is a typical engagement for a software company with one Oracle DBA who also handles other duties, running a small number of production Oracle databases on virtual machines in a public cloud account the company owns. AceMQ and a partner Oracle DBA add on-call and a scheduled maintenance routine under an AceMQ contract.
Challenge
A single DBA cannot take leave without risk, cannot be on call every night, and rarely has time for the work that prevents incidents: timed restores, Release Update planning and reviewing the slowest SQL. The company has backups that report success, a patch level that lags and a runbook that lives in one person's head.
Environment
Oracle Database 19c Standard Edition 2 on Linux virtual machines in the customer's cloud account, RMAN backups to object storage, Prometheus monitoring, and applications that cannot tolerate long unplanned outages.
Approach
AceMQ starts with a fixed-scope health check, then onboards to cover: alert routing, access arrangements that the customer's security team controls, runbooks for the failures found, and a named AceMQ engineer and partner DBA on the account. From then on the work runs on a schedule.
Solution
- Runs a health check of backup and restore, archive handling, patch level and the slowest recurring SQL
- Times a full restore to a separate host and compares it with the recovery target
- Routes database alerts to the AceMQ on-call rota with a 15-minute P1 response
- Plans each Release Update window with a rollback and tests it first on a copy
- Reviews the top SQL and plan changes each month using tools the Standard Edition 2 license allows
- Writes the runbooks the in-house DBA keeps in their head and reviews them after each incident
Outcome
The engagement delivers a written health check report, a timed and documented restore, runbooks for the failures it found, an on-call rota that covers nights and leave, a Release Update plan and a monthly written review. The company's DBA gets cover and time for the work only they can do.