Spotlight alarms indicate when the Oracle database exceeds acceptable performance thresholds.
| Alarm | Alarm | Description |
|---|---|---|
| Agent Status alarm |
Spotlight raises the Agent Status alarm when the status of the EM agent is down. OEM is a Web-based database administration and monitoring tool that manages Oracle components and administers Oracle databases. When installed and active, OEM communicates with the databases it administers via a set of EM agent processes under the automated DBSNMP user account. | |
| Archive Critical Failure alarm | An Archive Critical Failure alarm indicates that the number of working archive destinations for the database instance is about to fall below the minimum number needed to archive Oracle redo logs successfully. When you see this alarm, you should make space in the archive log destination by purging – or by backing up to an offline medium – any archived files that are not immediately needed. | |
| Archive Destination Failed alarm | Spotlight raises an Archive Destination Failed alarm when at least one of the archive destinations specified for redo log files has become full. See Archive Destination Failure alarm below. | |
| Archive Destination Failure alarm | An Archive Destination Failure alarm when at least one of the archive destinations specified for redo log files is about to become full. When you see this alarm, you should make space in the archive log destination by purging it, or by backing it up to an offline medium. | |
| Array Fetch Size alarm | When more than one row is retrieved from an Oracle database in a single SELECT (an array fetch), the amount of network traffic associated with SELECT operations is radically reduced. The Array Fetch Size alarm is raised when the array fetch size for the database may be too low. | |
| ASM Balance alarm | This alarm indicates that there is unbalanced access to one or more of the disks in the ASM (Automatic Storage Management) disk group that has been allocated to the Oracle instance. | |
| ASM Service Time alarm | This alarm indicates that the average time taken to perform I/O on the ASM instance has exceeded a specified threshold value. (Service time represents the response time of a disk plus any wait time experienced during disk operations.) | |
| ASM Status alarm | When a Spotlight connection is lost, Spotlight automatically tries to re-establish the connection. The ASM Status alarm indicates that Spotlight is re-establishing its connection to the ASM diskgroup for the Oracle instance. | |
| Average Time to Sync a Redo Log Entry alarm |
The Average Time to Sync a Redo Log Entry alarm (formerly the Average Redo Write Time alarm) is activated when the time taken to write redo log entries exceeds a threshold. Unlike most other Oracle write I/Os, Oracle sessions must wait for redo log writes to complete before they can continue processing. | |
| Buffer Busy Wait alarm | The Buffer Busy Wait alarm occurs when a session cannot access a block because it is in use by another session. The two most common causes are insufficient free lists for a table or insufficient rollback segments. | |
| Cache Buffer Chains Latch Wait alarm | The Cache Buffer Chains Latch Wait alarm occurs because contention for the cache buffer chains latch exceeds a threshold. | |
| Cache Buffer LRU Chains Latch Wait alarm | The Cache Buffer LRU Chains Latch Wait alarm occurs because contention for the cache buffer chains latch exceeds a threshold. | |
| Collection Status alarm |
Spotlight raises the Collection Status alarm when collection of data for the OEM (Oracle Enterprise Manager) stops. Perhaps the server is running low on disk space. The Collection Status alarm often occurs with the Files Pending Upload Alarm. | |
| Continued Fetch Rate alarm | Oracle sometimes needs to migrate a row in a database from its original block to a new block, or needs to chain an updated row across multiple blocks. These migrated and chained rows cause additional I/O, and the Continued Fetch alarm occurs when the number of these "continued row" fetches exceeds a threshold. | |
| CPU Busy alarm | The CPU Busy alarm occurs when the total CPU utilization of the system exceeds a threshold. | |
| CPU Virtualization Overhead alarm | The CPU Virtualization Overhead alarm is activated when Virtualization Overhead is greater than a threshold and CPU Usage is 95% or higher. | |
| Data Guard Configuration Alarm |
The Data Guard Configuration Alarm occurs on a Primary database in an Oracle Data Guard environment. Please supply details of Standby connections to Spotlight so Spotlight can monitor the Oracle Data Guard environment. In monitoring the Oracle Data Guard environment Spotlight can alert you if key elements of the Oracle Data Guard environment are not working, or if Standby instances are lagging behind. | |
| Dispatchers Busy alarm | The Dispatchers Busy alarm occurs when all or most dispatcher processes are busy. In an MTS environment, multiple sessions share a smaller number of shared server processes. The servers are usually allocated by a smaller number of dispatcher processes. | |
| Estimated Shared Pool Size alarm | This alarm occurs when the Shared Pool is set too small. A possible cause is the use of literals rather than bind variables in SQL statements. You can also increase the size of the Shared Pool. | |
| Excessive RBS Activities alarm | The Excessive RBS Activities alarm occurs when there are high rollback extent/shrink/wrap activities. | |
| Files Pending Upload alarm |
Spotlight raises the Files Pending Upload alarm when a significant number of XML files are pending upload indicating a problem with the upload process. The strategy for dealing with this alarm is dependent on the OEM control. The OEM control is defined in the Spotlight configuration for OEM. This alarm may occur in conjunction with the Collection Status Alarm. | |
| Flash Cache Insert Skip: DBWR Overloaded alarm | The Flash Cache Insert Skip: DBWR Overloaded alarm is raised when the ratio of insert skips from the DBWR being overloaded exceeds a threshold. | |
| Flash Cache Read Latency | The Flash Cache Read Latency alarm is raised when the time taken to read a single block from flash cache exceeds a threshold. This may be caused by a low performance flash device. | |
| Flash Cache Write Complete Waits |
The Flash Cache Write Complete Waits alarm is raised when the ratio of 'write complete waits: flash cache' to DB time exceeds a threshold. | |
| Flashback Buffer Wait alarm | The Flashback Buffer Wait alarm indicates that the percentage of available time spent waiting for the Recovery Writer (RVWR) to write data to the flashback logs has exceeded a specified threshold. | |
| Flashback Space Usage alarm | This alarm is raised when the amount of used space in the Flashback Recovery Area exceeds a threshold. | |
| Free Buffer Waits alarm | The Free Buffer Waits alarm occurs when free buffer waits (as a proportion of total waits) exceeds a threshold. | |
| In Memory CPU Overhead alarm | In-Memory Overhead Alarm | The In Memory CPU Overhead alarm is raised when the in-memory database is using too much CPU. |
| In Memory Undo Latch Wait alarm | The in memory undo latch is associated with Oracle's relatively new in memory undo (IMU) structures. These structures hold in memory information formerly maintained in rollback (undo) segments. | |
| Instance Failed alarm | Spotlight raises an Instance Failed alarm when a specified instance has failed because of an Archiver error. See Archive Critical Failure alarm above. | |
| Insufficient Flashback Logs alarm | This alarm fires when the flashback logs in the flashback area do not cover the amount of time specified in the parameter DB_FLASHBACK_RETENTION_TARGET. | |
| Job Processes Busy alarm |
The Job Processes Busy alarm occurs when all or most job queue processes are busy. | |
| Large Pool Full alarm | This alarm fires when the Large Pool allocation heap is full. The Large Pool is used in MTS for session memory, and can be used by parallel execution and backup processes. | |
| Latch Free Waits alarm | If a session needs to acquire a latch that is held by another session, a latch free wait may occur. The presence of latch free waits may indicate a bottleneck within the SGA. (The specific action depends on the latch.) | |
| Library Cache Latches alarms | These alarm fire when the time spent waiting on library cache latches or library cache pin latches exceeds a threshold. Library cache latches (or mutexes in 10g R2 and above) protect the cached SQL statements and object definitions held in the library cache within the Shared Pool. | |
| Library Cache Miss Rate alarm | The Library Cache Miss Rate alarm occurs when the library cache hit ratio falls below a given threshold. | |
| Lock Wait alarm | The Lock Wait alarm occurs when the proportion of time sessions spend waiting for locks exceeds a threshold. | |
| Log Buffer Space Wait alarm | The Log Buffer Space Wait alarm occurs if the amount of time spent waiting for space in the redo log buffer exceeds a threshold. | |
| Log Switch Time alarm | The Log Switch Time alarm occurs when the amount of time spent waiting for log switch events exceeds a threshold. | |
| Low Free Physical RAM alarm | The Low Free Physical RAM alarm occurs when the server’s available RAM is low. | |
| Maximum Queued Time alarm |
The Maximum Queued Time alarm becomes active when a session has been in the parallel execution queue for longer than the specified threshold. Note: Applies only to Oracle 11g Release 2. | |
| Multi-threaded Server alarm |
The Multi-threaded Server alarm occurs when all or most multi-threaded server (MTS) or dispatcher processes are busy. | |
| Non-reclaimable Flashback Space alarm | This alarm is raised when the amount of non-reclaimable used space in the Recovery Area (flashback area) exceeds a threshold. Non-reclaimable files include archived redo logs, which must be backed up before being deleted. | |
| Oracle Memory on Disk alarm | The Oracle Memory on Disk alarm is activated when the amount of guest physical memory mapped to machine memory is less than the current combined size of Oracle's SGA and PGA. | |
| Oracle Parameters for Predictive Diagnostics alarm | Predictive Diagnostics Oracle Parameters Alarm | The Predictive Diagnostics feature cannot predict the behavior of Oracle databases without the access to Oracle data that is granted by several Oracle parameters. |
| Oracle Status alarm | When a Spotlight connection is lost, Spotlight automatically tries to re-establish the connection. The Oracle Status alarm indicates that Spotlight is re-establishing its connection to the Oracle instance. | |
| Parallel Query Server alarms | The Parallel Query Server alarm occurs when all or most parallel servers are busy. Parallel server processes perform work to resolve SQL statements that are being executed in parallel. If all parallel server processes are busy, parallel SQL may be downgraded, or even executed serially, thus increasing its execution time. Spotlight can raise these Parallel Query Server alarms: Parallel Query Servers Busy, Parallel Queries Downgraded, and Parallel Queries Serialized. | |
| Parse Ratio alarm |
The Parse Ratio alarm is raised when the ratio of parse calls to execute calls exceeds a threshold. Note This alarm is initially disabled; see Total Parse Wait Time Ratio alarm. | |
| Predictive Diagnosticsalarms |
Predictive Diagnostics Bottleneck Collector Alarm |
Predictive Diagnostics alarm (SQL Collector, Bottleneck Collector or Performance Modeling Collector alarm) is raised when the appropriate collection of predictive data has not been scheduled. |
| Predictive DiagnosticsCustom SQL Error alarm |
This alarm indicates that the customized SQL query use to represent database concurrency within Predictive Diagnostics has returned an error. | |
| Predictive DiagnosticsOracle Parameters alarm | The Predictive Diagnostics feature cannot predict the behavior of Oracle databases without the access to Oracle data that is granted by several Oracle parameters. | |
| Redo Allocation and Redo Copy Latch Wait alarms | Redo Allocation Latch and Redo Copy Latch Wait Alarms |
The Redo Allocation and Redo Copy Latch Wait alarms are raised when there is contention for the redo allocation latch and redo copy latch. |
| Result Cache Find/Create Ratio alarm | Result Cache Find/Create Ratio Alarm | When Oracle executes SQL queries, the result cache stores the result sets of specified queries in shared memory for later use. The Find/Create Ratio alarm occurs when the rate of find operations on the result cache drops below the rate of create operations, and indicates that the contents of the result cache are under-used. |
| Result Cache Latch Sleep Ratio alarm | Result Cache Latch Sleep Ratio Alarm | Spotlight raises the Result Cache Latch Sleep Ratio alarm when the rate of latch sleeps for the Result Cache latch indicates that there is contention on the Result Cache latch, where multiple processes are competing to use the latch and are causing a significant degradation in response time. |
| Row Cache objects Latch Wait | Row Cache Objects Latch Wait Alarm | The row cache objects latch protects the contents of the row cache; the section of the shared pool to cache dictionary information. |
| Sequential Read Average Time alarm | Sequential Read Average Time Alarm | The Sequential Read Average Time alarm occurs if the average time for a random datafile read exceeds a given threshold. |
| Sequential Read Time alarm | This alarm fires when the average time that Oracle takes to read a single block of data — typically an index-based lookup — is significantly higher than the average time recorded during calibration. | |
| Sessions Queued alarm |
The Sessions Queued alarm becomes active when the number of sessions in the parallel execution queue exceeds a threshold. Note: Applies only to Oracle 11g Release 2. | |
| Shared Pool Latch Wait alarm | Shared pool latches control access to the shared pool memory map. | |
| Shared Pool Lock Percentage alarm | This alarm is raised when one user session holds a lock on object(s) in the Shared Pool for a prolonged period, and causes other sessions to wait on the same resource. This "blocking lock" happens rarely. When it does occur, use a SQL query to find the affected sessions. | |
| Shared Server Converted into Dedicated Server alarm | Spotlight raises an alarm when many shared servers are converted, leaving too few shared servers to meet the demand. Converted shared servers will have a status of WAIT(RECEIVE) in v$shared_server. | |
| Status Error alarm |
This alarm is raised when there is a problem with the way the OEM configuration has been defined in Spotlight. Correct the values entered in the dialog View | Options | OEM Monitoring. | |
| Temporary IO Wait Ratio alarm | Spotlight raises the Temporary IO Wait Ratio alarm when the time spent in temporary IO waits is too high as a percentage of the time spent performing user calls on the Oracle database. | |
| Total Parse Wait Time Ratio alarm |
Spotlight raises this alarm when the amount of time spent parsing SQL statements as a percentage of the active database time exceeds a level that may cause latch contention on the shared pool and library cache latches. Note: The Total Parse Wait Time Ratio alarm is available for (Oracle 10.2 and later). When monitoring earlier Oracle systems, consider reactivating the (disabled) Parse Ratio alarm. | |
| Unarchived Logs alarm |
The Unarchived Logs alarm occurs when the number of unarchived redo logs exceeds a threshold. If all online logs need archiving, database update activity can be suspended while the redo log writer waits for the next log to be archived. | |
| Unix Status alarm | When a Spotlight connection is lost, Spotlight automatically attempts to re-establish the connection. Where the Oracle database is hosted on a Unix server, this alarm indicates that Spotlight is re-establishing its connection to the Unix server. | |
| WMI Status alarm | When a Spotlight connection is lost, Spotlight automatically attempts to re-establish the connection. Where the Oracle database is hosted on a Windows server, this alarm indicates that Spotlight is re-establishing its WMI connection to the Windows server. | |
| Write Complete Wait alarm | Spotlight raises the a Write Complete Wait alarm when write complete waits (as a proportion of total waits) exceed a threshold. Write complete waits occur when a session tries to modify a block that is currently being written to disk by the database writer process. |
Note: Spotlight on Oracle Data Guard alarms occur in the Alarm Log of the Primary Database in the Oracle Data Guard environment. See Spotlight on Oracle Data Guard Alarms for more information.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center
