ITM Agent Insights: ITCAM Agent Workspaces go blank in Portal TEPS.

Most commonly, this is seen in a RAC environment with multiple SCAN listeners. Below are instructions for configuring the listener.ora file to monitor RAC SCAN listeners:

To start, the current design of listener monitoring:

a) the agent parses listener.ora, and gets listener addresses.

b) the agent tries to reach the listener addresses one by one using Oracle utility 'tnsping' or OCI API ServerAttach(), to determine the listener's status according to the output.

So, given the contents of the listener.ora, the Oracle agent cannot get the real address of SCAN listener from $ORACLE_HOME/network/admin/listener.ora.

Take LISTENER_SCAN3 in listener.ora as an example:

LISTENER_SCAN3 =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = IPC)(KEY = LISTENER_SCAN3))
    )
  )

The agent can only monitor SCAN listeners if the customer manually defines a new listener.ora in a separate directory with the SCAN listeners' real address or hostname.

Example using LISTENER_SCAN3:

LISTENER_SCAN3 =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = IPC)(HOST = <IPADDR or HOSTNAME>)(PORT =
<PORT>)
    )
  )

Note: Replace and with real listener IP or hostname and the DB port number, respectively.

Reconfigure the agent instance and set the configuration parameter:

"Net Configuration Files Directories(KRZ_TNS_PATHS)"

as the full path of the manually defined listener.ora, so that the agent can read the new listener.ora.

And then restart the agent instance.

Lastly, instruct the customer to change the agent configuration parameter:

KRZ_LOAD_ORACLE_NET to 'FALSE'

The agent will not load $ORACLE_HOME/network/admin/listener.ora and tnsnames.ora with this configuration.

Example:

config/rz_<agentInstance>.config:
KRZ_LOAD_ORACLE_NET='FALSE'

Restart the agent instance.