/
2016-11-29 Hicom DR Refresh Failure
2016-11-29 Hicom DR Refresh Failure
Date |
|
Authors | Graham O'Regan (Unlicensed) |
Status | Complete |
Summary | Hicom's internal refresh failed, from Martin Stanford "I'm sorry to announce that issues were encountered with the nightly refresh of v1.15 last night. This means that the changes for this release have not yet been applied to the data on the live DR. We have identified the cause of the problem, and anticipate a successful resolution for tonight's refresh." |
Impact | stale data was displayed until the refresh succeeded. |
Root Cause
Hicom's internal refresh failed.
Trigger
Their refresh runs nightly
Resolution
Hicom notified us when the refresh succeeded and we asked them to open access to our service account outside the normal operating windows so we could rerun our ETL processes.
Detection
Email from Hicom
Action Items
Action Item | Type | Owner | Issue |
---|---|---|---|
Timeline
- 8:37 email received from Martin to let us know that the refresh had failed.
- 9:26 email received from Marting to let us know that the next refesh succeeded.
Supporting Information
None.
, multiple selections available,
Related content
2016-12-16 Hicom DR Refresh Failed
2016-12-16 Hicom DR Refresh Failed
More like this
2017-08-14 Hicom DR refresh failed
2017-08-14 Hicom DR refresh failed
More like this
2021-09-29 NDW ETL overnight jobs failed
2021-09-29 NDW ETL overnight jobs failed
More like this
2020-11-18 Reval Legacy/Old GMC Sync
2020-11-18 Reval Legacy/Old GMC Sync
More like this
2021-12-06 GMC sync & Connections giving errors
2021-12-06 GMC sync & Connections giving errors
More like this
2021-07-23 TIS-NDW ETL failure
2021-07-23 TIS-NDW ETL failure
More like this
Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213