| Date | 2017-08-08 |
| Authors | Graham O'Regan (Unlicensed) |
| Status | In progress/ |
| Summary | Hicom's DR refresh failed so the data ingested by the ETL is from the 6th rather than the 7th |
| Impact | Stale data in Revalidation |
Root Cause
Trigger
Resolution
Detection
Action Items
| Action Item | Type | Owner | Issue |
|---|---|---|---|
| mitigate/prevent | |||
Timeline
9:44 Martin Stanford email us to let us know
The Data Repository refresh did not successfully complete last night, and therefore the data currently available has not updated since yesterday morning. This also applies to the data available at 0530 for the various extract processes
We have a copy of today’s data available, and we are going to overwrite the DR using this at 1000. The Dr will be unavailable for a few minutes while this operation takes place.
The end result of this will be all data refreshed and up-to-date.
Please let me know if lack of availability at 10 will cause any major problems.
Supporting Information
e.g. monitoring dashboards
Add Comment