Senior Oracle Database Administrator
Oracle 19c/21c · RAC · Data Guard · RMAN · Performance Tuning · CDB/PDB · GoldenGate · AWS
I keep mission-critical Oracle databases available, recoverable, and fast — and I publish the scripts and runbooks that prove it.
Senior Oracle DBA with 9+ years supporting enterprise Oracle databases across telecommunications (AT&T), automotive (General Motors), and government / postal — USPS mail-processing systems, complemented by a graduate background in healthcare informatics. My work centers on the operations that keep production online under real pressure: high availability, backup and recovery, performance tuning, patching, and multitenant administration.
I believe a DBA's credibility is best shown, not claimed — so my portfolio is a set of runnable, sanitized repositories with real scripts, sample output, and operational walkthroughs.
|
Core focus
|
Also strong in
|
Ten sanitized, production-style Oracle repositories — each with runnable scripts/runbooks, annotated sample output, and an Operational Screenshots (Proof of Work) section. Demo data only (
ORADEMO); no client identifiers.
|
Read-only daily health-check suite — availability, space, recoverability, and performance in a repeatable 10–15 minute pass.
|
Production RMAN library — full/incremental backups, control-file protection, validation, and restore/recovery playbooks with a 14-day window.
|
|
Top-down, DB-Time-first diagnostics — wait events, ASH, AWR, and top-SQL ranking that lead to one root cause.
|
Step-by-step Release Update, OPatch, rolling-RAC, Data Guard standby-first, and emergency rollback procedures.
|
|
Multitenant operations from |
The on-call operations playbook — daily checklist, startup/shutdown, incident response, and a blameless post-incident template.
|
|
GoldenGate replication monitoring, lag detection, and recovery — sanitized configs plus Extract/Replicat troubleshooting runbooks.
|
Data Guard administration & DR — switchover, failover, archive-gap resolution, DGMGRL broker operations, and standby-first patching.
|
|
RAC & clusterware operations — crsctl/srvctl, ASM diskgroup checks, service relocation, rolling maintenance, and node-eviction triage.
|
PowerShell, Python & SQL*Plus automation — scheduled health checks, RMAN/capacity reporting, alert-log parsing, and HTML/email delivery.
|
Real production activities reflected across the repositories above:
| Activity | Where it shows | |
|---|---|---|
| ✓ | Daily health checks | oracle-health-checks — availability, space, recoverability pass |
| ✓ | Backup & recovery procedures | oracle-rman-scripts — backup, validate, restore/recover playbooks |
| ✓ | Performance tuning | oracle-performance-tuning — wait/ASH/AWR root-cause method |
| ✓ | Patching procedures | oracle-patching-runbooks — RU, rolling RAC, datapatch, rollback |
| ✓ | Incident response | oracle-dba-runbooks — blocking, ORA-00257, listener, post-incident |
| ✓ | Multitenant administration | oracle-cdb-pdb-administration — PDB SAVE STATE, services, undo |
| ✓ | Troubleshooting | oracle-goldengate-configs — Extract/Replicat abends, lag, discards |
| ✓ | Disaster recovery & failover | oracle-dataguard-runbooks — switchover, failover, gap resolution, reinstate |
| ✓ | RAC & clusterware operations | oracle-rac-administration — crsctl/srvctl, ASM, service relocation, node eviction |
| ✓ | Automation & reliability | oracle-automation-toolkit — scheduled checks, reporting, alert-log parsing (PowerShell/Python) |
How I work (click to expand)
- Recoverability before change — never patch what I can't recover; validate restores, not just backups.
- Root cause, not symptom — measure where DB time goes, attribute it, change one thing, re-measure.
- Verify, don't assume — confirm each RAC node is ONLINE before the next; confirm source↔target in sync, not just "running."
- Write it down — runbooks that a tired engineer can follow at 2 a.m., with exact commands and a defined rollback.
Long-form write-ups of real (sanitized) production work. Replace the
#placeholders with your published LinkedIn/Medium URLs.
| # | Case Study | Topic |
|---|---|---|
| 1 | Recoverability Before Patching Oracle 21c | ARCHIVELOG conversion · RMAN · safe patching |
| 2 | Eliminating a Recurring PDB Startup Outage | Multitenant · SAVE STATE · availability |
| 3 | Rolling RAC Release Updates with Minimal Downtime | RAC · opatchauto · Data Guard pre-checks |
| 4 | Recovering GoldenGate Replication Lag | GoldenGate · Extract/Replicat · no data loss |
| 5 | From "Database Slow" to One Root Cause | AWR/ASH · wait events · SQL tuning |
Latest writing on Oracle operations, reliability, and performance. Add your published links below.
| Platform | Article | Link |
|---|---|---|
| Recoverability Before Patching: Risk → Routine | Read → | |
| Medium | Reading an AWR Report Top-Down | Read → |
| opatch vs datapatch: the two-step half of patchers miss | Read → | |
| Medium | The PDB That Wouldn't Open | Read → |
📫 More on LinkedIn.
| Credential | Issuer |
|---|---|
| Oracle Cloud Infrastructure — Foundations Associate | Oracle |
| Oracle Cloud Data Management — Foundations Associate | Oracle |
| Oracle Cloud Infrastructure — AI Foundations Associate | Oracle |
| OCI GoldenGate Workshop | Oracle |
| Graduate Certificate — Information Security & Assurance | Kennesaw State University |
| Degree | Institution |
|---|---|
| M.S., Information Security & Assurance | Kennesaw State University |
| M.S., Healthcare Management & Informatics | Kennesaw State University |
▸ Oracle automation — PowerShell/Python health checks, reporting, scheduling
▸ High availability & DR — RAC clusterware ops + Data Guard switchover/failover
▸ GoldenGate administration — monitoring, lag detection, and recovery patterns
▸ Performance engineering — top-down, DB-Time-first tuning methodology
▸ Cloud database architecture — Oracle on AWS / OCI; HA & DR design
▸ Database reliability — runbooks, SLOs, and blameless incident review
All repositories use sanitized, fictional demo data (ORADEMO) — no production, employer, or confidential information.
