Oracle Listener (ORANET_LISTENER)
Displays information about an individual listener process. ORANET_LISTENER
is available once the ORANET listener has been configured.
The ORANET_LISTENER icon is labelled LISTENER or <listenername>.
The ORANET_LISTENER
application class also monitors the scan listeners. When the scan listeners move from one Real Application Cluster Node to another, the KM will create the SCAN listener on that node.
In this Oracle km version, we changed the configuration of excluding listeners. In previous versions we have the option to enable/disable listeners from the configuration window, where we add listener. In this release we have removed this option and added new KM command and CMA configuration for this purpose.
You have an option to enable/disable listeners according to listener name or regular expression.
Note
In previous KM version, the following pconfig entry was existed for each listener to identify if it is enable/disable:
/OraNetConfig.{ListenerName}.monitorflag
( 1= Enabled)
In this KM version, this entry is removed from pconfig and instead we added the following new entry is added:
/OraNetConfig.__ANYINST__.ListenersFilterInActiveList
This variable will get value of all disabled listeners separated by comma (,)
Each listeners that are not existed in this pconfig entry � means it is enabled.
Listener Services
The listener services will be created under each listener. To get the listener services we run the following from ORACLE_HOME/bin:
>./lsnrctl services {listener name}
We added the option to enable/disable listener services. By default all listener services will be enabled. You can filter out from KM menu command or CMA. You can filter from root level or listener level.
If the listener has its filtered services list, then we take into consideration this filter, in case the listener has no filter on services we take into consideration the root level filter.
Root filter is done from ORANET application class or Global configuration of listeners on CMA. The listener filter is done from listener application class, and listener configuration in CMA.
Note
You have the option to filter out listeners services from ORANET root level or listener level.
Root Level (ORANET)
In this level you can filter out listener services for ALL listeners. You have the option to drag right and left listeners according to which you want to enable or disable.
Other option is using regular expression. The priority of the filter is for dragging list, in case you need to use regular expression , then all the services must be in active list.
Note
- The list of services belong to ALL listeners.
This filter will affect all services that their listener has no filter.
Listener Level
Set the filter you want to do , you have the following option:
- Check box of "Include all". This option is added to display all the listener services and to avoid the root filter.
- KM: Drag to left and right the services you want to enable/disable.
CMA: Add the list on CMA separated with comma - Use regular expresion.
When the "ListenerStatus" runs the services filter will be handles and add/destroy services according to the filter.
Note
The priority of the filter is the same as the above order. That is, if you disable all the services but you click on the "Include all ", then all the services will be displayed. If you use regular expression but you also set disabled list, then we ignore the regular expression
BMC PATROL properties
Item | Description |
---|---|
Active | Yes |
Created by | Discovery |
Parent class | ORANET_LISTENER_HOST |
Child class | None |
InfoBox
In addition to standard InfoBox fields, the ORANET_LISTENER InfoBox contains the following information.
Item | Description |
---|---|
SQL*NET Version | Version of SQL*NET used by the process |
Trace Level | Whether the trace level is ON or OFF |
Logging | Whether logging is ON or OFF, and the directory and file of the log |
Attributes (parameters)
The following attributes are available for this monitor type:
Comments
Log in or register to comment.