Lead Data Architect – Oracle​/Exadata

Role Summary

Own the source‑of‑truth understanding of the existing Oracle Exadata environment and ensure nothing critical is lost or misinterpreted during migration. This role is about semantic extraction, not defending Oracle.

• Oracle System Intelligence
  • Analyze Oracle schemas across:
  • RAC
  • PDBs
  • Sharded/partitioned tables
  • Interpret:
  • Triggers
  • Sequences
  • Materialized views
  • PL/SQL frameworks
  • Document implicit behaviors relied on by applications.
• SQL & Transaction Semantics
  • Analyze AWR/ASH and SQL Monitor data to determine:
  • Real transaction boundaries
  • Locking assumptions
  • Concurrency behavior
  • Identify Oracle‑specific constructs that cannot be replicated directly.
• Dependency & Risk Identification
  • Build the Oracle feature dependency matrix:
  • PL/SQL
  • Hints
  • Optimizer behavior
  • Isolation‑level dependencies
  • Classify:
  • Safe‑to‑migrate
  • Requires redesign
  • Requires application change
• Baseline Authority
  • Define golden data sets and expected results.
  • Validate correctness of test harness outputs against Oracle baselines.
• Advisory Role
  • Advise Spanner architects on:
  • Semantic traps
  • Hidden coupling
  • Oracle behavior apps implicitly depend on

• 12 years of deep Oracle experience.
  • Expert in:
  • Exadata internals
  • AWR/ASH
  • SQL tuning at scale
  • Strong PL/SQL framework knowledge.
  • Experience with very large databases (10s-100s of TB).
  • Ability to translate Oracle semantics into neutral architectural concepts.

• Oracle behavior reference model
• SQL signature catalog
• Oracle feature dependency report
• Migration risk classification
• Baseline correctness definitions