During an internal database migration of a secondary system, an existing database view was ‘dropped’ before its replacement view was available. The replacement view requires 8+ hours to fully populate with historical data going back more than 4 years. Without the view available for database queries, the dashboard component of the administrative console (which relies in part on this database and view structure) errored and was unable to serve customer requests.
An interim fix was to create a small replacement view with historical data going back only 3 weeks. This was performed to bring the dashboard application online. The final resolution came once a replacement view was fully populated and made available.
This outage did not involve or impact transaction processing.