Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

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?

April 26, 2017alarm Black condition message module Oracle PrimeAlert running server

0

Posted

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?

1 Answer

0

Posted

There may be several reasons for this. First, one of the module parameters for the Oracle server may be wrong. Check that the module parameters are correct by running the script HALDBMSAlertOracle-check.sh (included in the distribution), then edit the module and enter the parameters from the script output Second, you may have encountered a known problem with version 1.1 of HALDBMSAlertOracle-check.sh which was released with PrimeAlert for Oracle version 1.0.1. Newer releases of the module contain the updated script. Please download a newer version of the module. Finally, you may be encountering a character set problem. Use the following command to find your character set: SQL> select VALUE from V$NLS_PARAMETERS where PARAMETER=’NLS_CHARACTERSET’; Oracle modules version 1.0.5 and earlier do not support multi-byte character sets such as UTF8. This issue is dealt with in later releases. Please download a newer version, or contact Halcyon if you encounter this problem.