Retail / E-commerce · Enterprise · $320K · owned by Yusuf Abdel-Rahman
Steve has not written one for this account. Everything it would read is below.
Every record Steve is allowed to cite
VP Data Platform
Principal Platform Engineer
Retail / E-commerce · Enterprise · $320K · owned by Yusuf Abdel-Rahman
Steve has not written one for this account. Everything it would read is below.
Every record Steve is allowed to cite
VP Data Platform
Principal Platform Engineer
Enterprise Architect
VP Retail Technology
Next step: Re-baselined Phase 2 cutover runbook due 2026-07-24
Change-data-capture from the legacy Oracle order store silently omitted CLOB and BLOB columns whenever a resync was triggered. Reproduced on the 11.2 source, patched the connector, and the customer re-ran the affected partitions cleanly.
The full three-year order history did not complete inside the 52 hour weekend window. Split the load into 14 partition-aligned chunks and raised parallelism to 24 writers, which brought the run to 31 hours.
During dual-run, roughly 0.4 percent of inventory rows differ between the legacy warehouse and Vantage, concentrated in adjustments posted after 22:00 local. Investigating a timezone handling difference in the legacy extract. Still open.
Helena confirmed the Phase 2 cutover date has moved from 2026-08-03 to 2026-09-14 and asked us to re-baseline the runbook against the new date. Marcus walked through the open inventory reconciliation gap on the dual-run and said he is comfortable it is an extract-side timezone issue rather than an ingestion defect. Dev Sundaram was invited and did not attend, and no apology or reason was logged. Helena remains positive on Phase 1 and cited the orders domain running for six weeks without an incident.
Walked the Phase 2 target architecture covering orders, inventory and pricing, with a dual-run period of four weeks per domain before the legacy extracts are retired. Marcus said his platform group is two engineers, both of whom are also carrying the point-of-sale replatform through Q3. Dev raised the question of whether the reconciliation layer should live in Vantage or stay in their existing control framework, and asked for a written runbook before committing.
Enterprise Architect
VP Retail Technology
Next step: Re-baselined Phase 2 cutover runbook due 2026-07-24
Change-data-capture from the legacy Oracle order store silently omitted CLOB and BLOB columns whenever a resync was triggered. Reproduced on the 11.2 source, patched the connector, and the customer re-ran the affected partitions cleanly.
The full three-year order history did not complete inside the 52 hour weekend window. Split the load into 14 partition-aligned chunks and raised parallelism to 24 writers, which brought the run to 31 hours.
During dual-run, roughly 0.4 percent of inventory rows differ between the legacy warehouse and Vantage, concentrated in adjustments posted after 22:00 local. Investigating a timezone handling difference in the legacy extract. Still open.
Helena confirmed the Phase 2 cutover date has moved from 2026-08-03 to 2026-09-14 and asked us to re-baseline the runbook against the new date. Marcus walked through the open inventory reconciliation gap on the dual-run and said he is comfortable it is an extract-side timezone issue rather than an ingestion defect. Dev Sundaram was invited and did not attend, and no apology or reason was logged. Helena remains positive on Phase 1 and cited the orders domain running for six weeks without an incident.
Walked the Phase 2 target architecture covering orders, inventory and pricing, with a dual-run period of four weeks per domain before the legacy extracts are retired. Marcus said his platform group is two engineers, both of whom are also carrying the point-of-sale replatform through Q3. Dev raised the question of whether the reconciliation layer should live in Vantage or stay in their existing control framework, and asked for a written runbook before committing.