Events that are automatically recorded when a problem occurs on the Exadata cell node must be cleared when the problem is corrected. The cleaning process can be done automatically and sometimes it is not cleaned automatically. In this case, if you want to send a weekly or daily report, you will be constantly informed about the problem.
You can access detailed information about an event on the cell node via cellcli with the following command:
CellCLI> list alerthistory 45_2 detail
alertDescription: "A generic component suspected of causing a fault"
alertMessage: "A generic component is suspected of causing a fault. Component Name : /SYS/MB/RISER1/PCIE4/F20CARD Fault class : fault.chassis.device.esm.eol.exceeded Fault message : http://www.sun.com/msg/SPX86-8002-S3"
alertAction: "For additional information, please refer to http://www.sun.com/msg/SPX86-8002-S3"
Use the following command to check if there are any errors on the cellnode:
CellCLI> alter cell validate configuration
Cell orclceladm01 successfully altered
If no errors are returned, all problems are resolved. In this case, you can clear all relevant event logs. You can use the following command to clean.
Delete Exadata cell node alert history:
CellCLI> drop alerthistory 45_1,45_2
Alert 45_1 successfully dropped
Alert 45_2 successfully dropped
If you perform the drop for a single event and if there are other events that are linked to this event, it will fail as follows. Therefore, you have to drop all the events related to the problem at once.
CellCLI> drop alerthistory 45_2
CELL-02643: DROP ALERTHISTORY command did not include all members of the alert sequence for 45_2. All members of the sequence must be dropped together.
Use the following command to delete all event records:
CellCLI> drop alerthistory all
Alert 57_1 successfully dropped
Alert 57_2 successfully dropped
After deleting all records, no results will be returned in alerthistory.
CellCLI> list alerthistory