Confidential Information, Disclaimer and Trade Marks
This document serves as a Root Cause Analysis for the campusM service interruption experienced by Ex Libris customers on March 17th. 2020.
The goal of this document is to share our findings regarding the event, specify the root cause analysis, outline actions to be taken to solve the downtime event, as well as preventive measures Ex Libris is taking to avoid similar cases in future.
Service interruption was experienced by Ex Libris customers served by the campusM AP01 instance at the APAC Data Centre during the following hours:
March 17th , 2020 from 12:10 AM until 12:27 AM Singapore time
During the event, the service was unavailable for the environment .
Root Cause Analysis
Ex Libris Engineers investigated this event to determine the root cause analysis with the following results:
A database process, designed to align analytics data, was causing a high-volume creation of temp files, and a failure of the database.
Technical Action Items and Preventive Measures
Ex Libris has taken the following action and preventive measures to avoid such an occurrence in future:
- Preventive Measures - The database process was divided to smaller procedures to ensure database file space availability as well as additional manual monitoring of the process. The process was a one-time run and was completed successfully
In addition to the ongoing, real-time communications from the Ex Libris Status page an initial summary of the events was sent to all affected customers on August 13, 2019.
ExLibris is committed to providing customers with prompt and ongoing updates during Cloud events. Ongoing and prompt updates on service interruptions appear in the system status portal at this address: http://status.exlibrisgroup.com/
These updates are automatically sent as emails to registered customers.
|March 25, 2020||Initial Publication|