DATABASE ENGINEERING · LEARNING JOURNAL
A practical record of virtual machines, Ansible automation, database resilience, AWS migration, and the path toward agentic operations.
Explore the lab tracks →lab:
control: ansible-01
oracle: [ora-01, ora-02, ora-03]
db2: [db2-01, db2-02, db2-03]
postgres: [pg-01, pg-02, pg-03]
sybase: [ase-01, ase-02, ase-03]
# examples only — no secretsLAB COMMAND CENTER
Select a platform to turn the roadmap into a focused three-VM lab plan. Progress is saved only in this browser.
LAB TRACKS
Each track starts with architecture and discovery, then adds automation, workload, backup, recovery, and observability.
Understand compute, CPU, memory, storage, networking, snapshots, templates, and the difference between a VM and a database instance.
Create one control node to manage the lab through inventories, roles, variables, vault-protected secrets, and idempotent playbooks.
Design a primary, standby, and utility/test host. Learn RMAN, ARCHIVELOG, recovery validation, continuous workload, and Data Guard concepts.
Plan primary, HADR standby, and quorum/utility roles. Record log shipping, peer state, takeover behavior, backup, and restore tests.
Build primary, streaming standby, and backup/monitoring hosts. Observe WAL generation, replication lag, base backups, and point-in-time recovery.
Document a primary ASE host, companion/DR host, and backup/monitoring host. Exact topology depends on licensed features and version.
GROWTH PATH
Create repeatable VMs with approved images, isolated networking, storage plans, and resource limits.
Use Ansible for discovery and orchestration. Keep database-native work in Oracle, Db2, PostgreSQL, or ASE utilities.
Model accounts, transactions, ledgers, and audit events. Ramp from a small dataset; measure throughput and log generation.
Schedule baseline backups, archive logs continuously, test restores, and measure RPO, RTO, apply lag, and evidence.
Create a sandbox AWS account structure, then learn DMS assessment, endpoints, replication instance or serverless capacity, tasks, monitoring, and validation.
Begin read-only: summarize alerts, collect diagnostics, and propose runbook steps. Require approval for changes and never expose credentials.
REFERENCE FLOW
NON-NEGOTIABLES
This journal publishes concepts and sanitized examples. It must never contain real credentials, private keys, account IDs, internal hostnames, production data, or unreviewed destructive commands.