Date & time of incident:
Monday, December 5, 2011 - 11:24
Post date:
Monday, December 5, 2011 - 11:27
Incident Description:
ADCR3 database instance's node rebooted spontanously probably because of high load. After the node went back, that database instance has not restarted, so ADCR database is working on 2 nodes out of 3.
Service Element Affected:
DB & Application Platform Service for Projects & Experiments
Impact:
Service is degraded
Status:
Resolved
Resolution date:
Mon, Dec 5, 11:45
Posted by:
IT-DB
Unit responsible for resolution:
IT Department