In Previous posts, we have created following related posts:
- Create a Metric Extension (ME) to Monitor FRA Usage on OEM
- Create an Incident Rule for Metric Extension ( ME ) to Monitor FRA Used in OEM
Now and then, FRA usage is easily over threshold, DBA needs logon system and manually run an archivelog backup. It is easily to make database hung if FRA usage is 100%.
Here we use “Corrective Actions” to run a RMAN archivelog backup when the FRA usage is over warning / Critical threshold.
Subscribe to get access
Read more of this content when you subscribe today.
10) After a little while, an alert is received about “Corrective action status=Succeed”
Corrective action=RMAN_AUTO_BACKUP_ARCHIVELOGS Corrective action owner=SYSMAN Corrective action status=Succeeded Corrective action output=SID: RACTEST1 HOME: /u01/app/oracle/product/11.2.0/dbhome_1 BASE: /u01/app/oracle SID: RACTEST1 HOME: /u01/app/oracle/product/11.2.0/dbhome_1 BASE: /u01/app/oracle Host=RACTEST1.ractest Target type=Cluster Database Target name=RACTEST-CLUSTER Categories=Capacity Message=The value of Flash Recovery Area % Used for +FRA is 82 Severity=Warning Event reported time=Dec 22, 2016 9:01:54 PM EST Target Lifecycle Status=Development Comment=RAC TEST Operating System=Linux Platform=x86_64 Associated Incident Id=209879 Associated Incident Status=New Associated Incident Acknowledged By Owner=No Associated Incident Priority=High Associated Incident Escalation Level=0 Event Type=Metric Alert Event name=ME$RACRecoveryAreaSpace:FRA_PERCENT_USED Metric Group=ME$RACRecoveryAreaSpace Metric=FRA_PERCENT_USED Metric value=82 Key Value=+FRA Key Column 1=FRA_NAME Rule Name=Flash Recovery Area Percent Used for ME
2 thoughts on “Use Corrective Action ( CA ) to Automate Archivelog Backup When FRA Usage is Over Threshold of Metric Extension ( ME ) in OEM”