RMAN is Oracle’s built-in backup and recovery utility, and most environments schedule full (or level-0 incremental) database backups on a recurring cycle. When a backup job’s STATUS is recorded as FAILED, the most recent full-backup attempt did not produce a usable backup, directly threatening your recovery point objective if it goes unnoticed. Required permissions: GRANT […] Read more
In addition to full database backups, most recovery strategies also back up archived redo logs so that point-in-time recovery is possible between full backups. A failed archived-log backup job breaks that chain and can leave a recovery gap even when the most recent full backup succeeded. Required permissions: GRANT SELECT ON V_$RMAN_BACKUP_JOB_DETAILS TO redgate_monitor_user CONTAINER=ALL; […] Read more
Invalid objects are views, PL/SQL packages, procedures, functions, triggers, and materialized views whose status has changed to INVALID, typically because a dependency was altered or dropped. A small number is often transient and self-resolving, but a growing or persistent count can point to a failed deployment, a missing grant, or a dependency issue that will […] Read more
ORA-00600 (internal error) and ORA-07445 (operating-system exception) indicate that Oracle hit a condition its own code did not expect. They can signal bugs, corruption, or resource problems and should always be investigated, often with a support SR. Required permissions: GRANT SELECT ON V_$DIAG_ALERT_EXT TO redgate_monitor_user CONTAINER=ALL; GRANT SELECT ON V_$CONTAINERS TO redgate_monitor_user CONTAINER=ALL; These are […] Read more
This metric returns a count of the job steps that failed in the latest execution of all jobs on the instance. This should be a calculated measure, where the change is what should alert the DBA. If any step in a job fails in the latest execution, this alert counts those failures and returns a […] Read more
One or more SQL Agent jobs exist that are not owned by the database owner. You should fix these jobs so that they’re owned by the appropriate person. If the owning account is removed from Active Directory, the job may fail. Read more
Get the count of Images that have been created with no Data Masker masking set applied. Run this solely on the Instance where you have the SQLClone_Config DB Setup (about ~5ms to run). Read more
This metric counts the number of principals who are members of the sysadmin fixed server role. Adding a normal user to this role could pose a security risk and is not recommended. Read more
This metric returns the number of foreign keys that have their is_not_trusted flag set to 1 in the sys.foreign_keys table. An untrusted foreign key may threaten a database's referential and data integrity. Read more
What are custom metrics?
The Redgate Monitor custom metric feature lets you run T-SQL queries against your SQL Servers to collect specific data. You can analyze and receive alerts about your custom data just like everything else Redgate Monitor collects.
But what if you don’t want to write your own queries? No problem. Redgate has brought together a range of quality custom metrics for you to use in Redgate Monitor, which are all are free, tried and tested. You can install straight away, and use the resources on this site to help you write your own.
Redgate Monitor is a SQL Server performance monitoring tool that gives you real-time and historical SQL Server performance data with alerts and diagnostics.
With its embedded expertise from SQL Server experts and MVPs, it gives you the information and advice you need to find and fix issues before users are even aware.
This custom metric measures the total database file size (data files and log file combined). An increase in this metric signals that a database was grown. When not done by the DBA, this is an autogrow. Excessive autogrow events should be prevented as this can result to file fragmentation. Try to manually grow files before […] Read more
This metric will display the total number of active backups and restores on a server. This can be used to correlate with other metrics to explain why disk IO and CPU usage could have changed. Read more
37,500
0
