We defined the listener monitoring according to the Foglight For Oracle Guide, but cannot get the listener to be monitored
Running lsnrctl status shows that the listener exist, and it's up and running
Agent log shows errors on DBO_OS_Oracle_Listener_Status_Error.ksh script:
WARN [DBO-MYDB-highPriorityPool-6]
com.quest.qsi.fason.oracle.collection.processor.DBOUnixListenerStatusErrorProcessor -
Unexpected error string [] was returned from query DBO_OS_Oracle_Listener_Status_Error.ksh
The Listeners global administration screen allows editing the list of monitored listeners per instance, by adding or removing listeners from the list.
Adding a listener for monitoring is available either from Listeners global administration screen or from the Agent ASP, through Agent Status > OS Monitored Connection Profile.
One instance can have more than a single listener serving it; this is why the Listener name as typed in the Global Admin or ASP should correlate to the exact listener name as on the Database machine.
Please verify the following:
If the above were successfully completed, and still the listener cannot be monitored, read on.
Verifying the listener case sensitivity on the Database server and in Listeners global administration screen
1). Run this command on the Database machine
ps -ef | awk '/tnslsnr/ && !/awk/ { for (i=1; i0) {print $(i+1) } } }'
2). Check that the Listener to be monitored is in the list
3). Check if the Listener name as placed in the Listeners global administration screen or in the ASP matched the exact pattern as in the command output. UNIX is sensitive to upper/lower caps, and the name must be typed in the Agent exactly as it is in UNIX.
For example:
$ ps -ef | awk '/tnslsnr/ && !/awk/ { for (i=1; i0) {print $(i+1) } } }'
listener1
Listener2
LisTener
The output command shows that there are three different listeners. In Listeners global admin, the settings are as follows (see attached screenshot home.png)
As from UNIX perspective the listener as in the Listeners global admin, doesn't exist as it is typed differently than the listeners that are running on the UNIX itself. If listener1 would have been typed in Listeners global admin instead of LISTENER1, the Agent could start monitoring the listener requested.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center