Problem
If the Oracle databases crashes, it is shutdown with the abort option or any non-normal shutdown, the Ignite monitor can become hung. Typically this happens because the Ignite 6.x monitoring sessions is hung waiting for the database link to return results. Since the session on the monitored database is no longer there, the results will never arrive and the monitor waits indefinitely. To determine if this problem is occuring for you, execute the following query on the repository database:
SELECT s.sid, s.serial#, s.module, sw.event, sw.state
FROM v$session s, v$session_wait sw
WHERE s.sid = sw.sid
AND UPPER(s.module) LIKE UPPER('%&DBName%');
If the Ignite Quickpoll process for the database is waiting on "SQL*Net more data from dblink" (or similar), you have the problem.
Resolution
To resolve the issue:
- Kill the session in the Ignite repository via the "ALTER SYSTEM KILL SESSION '&sid,&serial';" command.
- Restart the Ignite monitor for this database.
Detecting the Problem in the Future
To detect the problem in the future, a custom alert in Ignite can help. This alert and instructions are located in the Ignite Custom Alerts Library.