{"name":"RMAN Full Backup Failures (24h)","description":"Counts failed full database backup jobs recorded in RMAN's job history within the last 24 hours. If your backup strategy uses incremental level-0\/level-1 backups instead of traditional full backups, change input_type to 'DB INCR'; run SELECT DISTINCT input_type FROM v$rman_backup_job_details to see the values recorded in your environment. Confirm your scheduled backup window falls inside the period you are querying.","tsql":"-- Returns the count of failed RMAN full database backup jobs in the last 24 hours\r\n-- RMAN backup jobs operate at the whole-CDB level, reported at instance level (con_id 0)\r\nSELECT 0 AS con_id,\r\n       COUNT(*) AS metric_value,\r\n       LISTAGG(input_type || ' started ' || TO_CHAR(start_time, 'DD-MON HH24:MI') || ' ' || status,\r\n               '; ' ON OVERFLOW TRUNCATE)\r\n           WITHIN GROUP (ORDER BY start_time DESC) AS alert_detail_text\r\n  FROM v$rman_backup_job_details\r\n WHERE input_type = 'DB FULL'\r\n   AND status = 'FAILED'\r\n   AND start_time > SYSDATE - 1","instances":true,"instances_comment":"Reported at instance level (con_id 0); RMAN operates at whole-CDB level","databases":{"mode":1},"frequency":1800,"frequency_comment":"seconds (collected every 30 minutes)","rateofchange":false,"metricenabled":true,"alertname":"RMAN full backup failed","alertdescription":"One or more RMAN full database backup jobs failed within the last 24 hours, directly threatening your recovery point objective. The alert detail text lists the failed jobs and start times; check the RMAN log for the failure cause and re-run the backup.","aboveorbelow":"above","_thresholds_high":{"selected":true,"value":0},"collections":1,"alertenabled":true,"_thresholds_medium":{"selected":false},"_thresholds_low":{"selected":false},"targetentitytype":2}