Oracle Net Listeners


After you have installed PATROL for Oracle Enterprise Database, you must configure a monitoring policy for the profile that you want to start monitoring.

In remote monitoring, you can monitor listeners configured on the UNIX platforms only. 

The following video (3:58) illustrates the steps to configure Oracle Net Listeners monitoring:



icon-play@2x.png https://youtu.be/IrNbTPh2QKY


To configure Oracle net listeners

  1. Perform one of the following steps:
    • In BMC Helix Operations Management, go to Configuration > Monitor Policies.
    • In TrueSight Operations Management, go to Configuration > Infrastructure Policies.
  2. On the Create Monitoring Policy page, enter the policy name and other details and then click Add Monitoring Configuration.
  3. From the Monitoring Solution list, select Oracle Enterprise Database.
  4. From the Monitor type list, select Oracle Net Listener.
  5. In the Environment configuration section, click Add, enter the following details, and save the policy:

    Field

    Description

    Environment name

    Enter the environment name.

    Listener details

    Hosts

    Click Add.

    Type

    Select the host type – Local, Remote, or RAC.

    Host name

    Enter the host name.

    Credentials

    Enter the user name and password of a user with the privileges to the Oracle home directory.

    For local monitoring, if the PATROL default account has access to the Oracle home directory and execute permissions on the Oracle binaries like lsnrctl, crsctl, and so on, leave the field blank.

    Oracle home

    Enter the path of the Oracle home directory. For a RAC node, enter the path of the grid home directory.

    SSH port

    Enter the SSH port to connect to the remote host or RAC node.

    Use global configuration

    If you can connect to all Oracle hosts with same credentials, select the check box and enter same host details in the Global configuration section.

    Global configuration

    Credentials

    The credentials to access all Oracle hosts that you want to monitor are same, enter those credentials in the section.

    Note: Credentials are required for a remote host and remote RAC host.

    Oracle home

    Enter the path of the Oracle home directory. For a RAC node, enter the path of the grid home directory.

    SSH port

    Enter the SSH port to connect to the remote host or RAC node.

    Filters > Listener

    Listener filter type

    Select if you want to include or exclude listeners from monitoring.

    Listener filter

    Add the listeners. 

    Regular expressions are supported. For example, to include all listeners that begin with MGMT and end with LSNR, enter ^MGMT.*|.*LSNR$

    Filters > Services

    Services filter type

    Select if you want to include or exclude listeners from monitoring.

    Services filter

    Add the services.

    Regular expressions are supported. For example, to include all services that begin or end with DATA, enter ^DATA.*|.*DATA$

    Environment settings

    Logging

    Select the check box to enable logging for all Oracle net listeners that you are monitoring in the specified environment.

    Device mapping

    By default, the collected data is shown in the PATROL Agent hierarchy on the Devices page. To collect data under a separate device, select the check box.

    If you select the check box, a new device with the name of the Oracle host is created on the Devices page.

    Java collector settings

    Java home

    The path to the JRE directory (or the $JAVA_HOME environment variable) on the PATROL Agent host.

    If you use the $JAVA_HOME variable, the Java location is depends on the following:

    • No user name and password are entered for the Java collector settings; the KM uses the Java location of the user running the PATROL agent.
    • A user name and password are entered for the Java collector settings; the KM uses Java location of the user entered in the collector settings.

    If you enter a path for the JRE directory, you must enter the full path, such as C:\Program files\Java\jre1.8.0_151. Do not use the short path format.

    If you do not enter a value in this field, the KM looks for the Java installed in the PATROL Agent home directory as:

    • Linux: $PATROL_HOME/../openjdk; $PATROL_HOME/../jre64
    • Windows: %PATROL_HOME%/../openjdk; %PATROL_HOME%/../jre64

    JVM Arguments

    The optional Java Virtual Machine (JVM) arguments for the Java collector

    Username

    The local user name to start the Java process.

    Password and Confirm password

    The user password to start the Java process.

    Collection settings

    Enter the collection settings and save the configurations.

    Global monitoring setting

    Logging

    To enable logging for the KM, select the check box.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*