4000000000800000 - Lvm Snapshot Detected That Is Too Full; 4000000001000000 - Lvm Snapshot Detected With Invalid Attributes; 4000000002000000 - Drbd Split Brain - Oracle E5-APP-B Alarms And Maintenance

Alarms and Maintenance
The Logical Volume Manager (LVM) creates read-only snapshots of the database. These LVM snapshots
are present when an audit of the LSMS database is active and when the database is being downloaded
to EAGLE. An LVM snapshot provides rollback and recovery capability to the active database. All
LVM snapshots are removed when no longer needed, or are removed and recreated when in continuous
use such as during an LSMS audit which may last several hours.
Recovery
Contact My Oracle Support

4000000000800000 - LVM Snapshot detected that is too full

This alarm usually occurs when an LVM snapshot has remained in existence too long and has a higher
full percentage than expected; however, the alarm may occur also if an unusually large number of
updates, distributed evenly across the entire database, have been received.
The Logical Volume Manager (LVM) creates read-only snapshots of the database. These LVM snapshots
are present when an audit of the LSMS database is active and when the database is being downloaded
to EAGLE. An LVM snapshot provides rollback and recovery capability to the active database. All
LVM snapshots are removed when no longer needed, or are removed and recreated when in continuous
use such as during an LSMS audit which may last several hours.
Recovery
Contact My Oracle Support

4000000001000000 - LVM Snapshot detected with invalid attributes

An LVM snapshot has been detected with invalid attributes. This alarm may occur if an LVM snapshot
cannot be removed completely due to an error in the LVM subsystem. Restarting the ELAP software
may clear this condition.
Recovery
Contact My Oracle Support

4000000002000000 - DRBD Split Brain

This alarm occurs when the ELAP A and B servers have simultaneous outages or if the three heartbeat
paths are lost between the two servers. If either condition occurs, neither server can determine which
server has the most recent copy of the database. The first system to recover becomes the HA active
system. Manual action is required to determine which copy of the shared data is valid and to
resynchronize with the other system.
Recovery
My Oracle Support
Contact
E76220 Revision 1, July 2016
(MOS).
(MOS).
(MOS).
(MOS).
Platform and Application Alarms
78