Service Maintenance Completed: Enterprise Database (Multiple Services Impacted)

Last Updated: 03/26/2019
Login to subscribe

Start Date & Time

Tue, 03/26/2019 - 9:30pm

End Date & Time

Tue, 03/26/2019 - 11:00pm


Due to complexities with the March 25 Enterprise Database maintenance, additional work needs to be completed tonight. The production Enterprise Database (EDB) service will undergo maintenance from 9:30 p.m. to 11 p.m. this evening. It will impact services that are dependent upon the Enterprise Database, including Federated Identity Service and services that rely on it for authentication and logins (see Impact and Affected Services below).


The Federated Identity Service will be down briefly for approximately 5-10 minutes during the maintenance window. New authentication activity and logins will not be possible during these times. Dependent services may also experience interruptions during the maintenance window (see Affected Services below).

The Registry Jobstream will be disabled on Monday, March 25, and other automated jobs related to data feeds, extracts, and provisioning of third-party systems will also be down during the maintenance window.

Users will be unable to create new courses in Canvas and Desire2Learn and new enrollments will be delayed until the work is completed.

Affected Services

The following services are dependent upon the Enterprise Database and may experience interruptions during the maintenance:

  • Grouper (,
  • Mobile MyCUInfo (
  • Northstar (
  • Federated Identity Service/Shibboleth ( and services that rely on it for authentication and logins, including:
    • MyCUInfo  
    • D2L
    • Canvas
    • Student Printing 
    • Qualtrics (will not affect recipients ability to respond to surveys)
    • Digication
    • Voicethread
  • Book Store data retrieval (via MyCUInfo)
  • Learning Management Systems course creation and enrollments
  • Oracle Identity Manager backfill of data to the EDB will be queued up during the maintenance and processed when complete (e.g. user display name changes via will not immediately propagate to the EDB)
  • Batch data integrations
  • Data integrations APIs