Why does the Agent have Oracle connections open even after the PrimeAlert for Oracle module has been unloaded?
This is caused when one or more processes named pad-oracle do not exit when the PrimeAlert for Oracle module is unloaded or scheduled off. This can interfere with a database shutdown. For example, the pad-oracle process may still have an open connection to the Oracle database. To work around this problem, kill any pad-oracle processes which are still running after the Oracle module has been unloaded or scheduled off.
Related Questions
- Why does the PrimeAlert for Oracle module have a Down (black) alarm condition with the message "Module Status is Not Accessible" even though the Oracle server is running?
- Why does the Agent have Oracle connections open even after the PrimeAlert for Oracle module has been unloaded?
- What is advanced benefits module in Oracle HRMS?
