Validation catalogue

Append-only. Evidence and owners for each area of acceptance.

Validation areas, the evidence required, and the owner
AreaEvidenceOwner
Technical completenessCounts, partitions, file manifests, checksums, rejected-row dispositionMigration lead
Data correctnessAggregates by key and period, referential checks, sampled query reconciliationData owner
Business fitnessCritical reports, semantic definitions, key business outcomesBusiness owner
Explained divergenceEvery difference classified as defect, intended improvement or unexplainedBusiness owner
Workload fitnessQuery, batch and concurrency results against the pre-migration baselinePlatform lead
SecurityLeast-privilege access, encryption, audit and credential checks under real rolesSecurity owner
Operational readinessMonitoring, alerts, support route, runbooks, defect processService owner

Set acceptance thresholds before rehearsal. For each result record the source and target positions, the method, the time, the scope, the reviewer and the conclusion. Attach raw output where it helps, with a short note on what it shows.

Reviewed 25 August 2026

These are my own views, written from years of building and moving large Oracle data platforms. They are not Oracle’s official guidance and this is not Oracle documentation. Volatile product claims are quarantined in Product facts that will date.