Risks, Limitations & Assumptions

  • The integration can manage critical/recovery failure alerts for the following two scenarios when the user activates App Failure Notifications in the settings:
    • Connectivity Exception
    • Authentication Exception
  • Oracle Cluster will send any duplicate/repeat failure alert notification for every 6 hours.
  • Metrics can be used to monitor Oracle resources and can generate alerts based on the threshold values.
  • We have provided the provision to give Cluster Ip Address OR HostName in configuration, but hostName provision will work only if the host name resolution works.
  • Oracle Cluster supports only Classic Gateway and NextGen Gateway. Not supported with Cluster Gateway.
  • No support of showing activity logs.
  • The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
  • Component level thresholds can be configured on each resource level.
  • Latest snapshot metric support from Gateway 14.0.0.
  • Currently, SSH authentication is supported using credentials (username and password). However, SSH key-based authentication is not supported.

Troubleshooting

Before troubleshooting, ensure all prerequisites prerequisites are met.

If Oracle Cluster integrations fail to discover or monitor, troubleshoot using the following steps:

  • Check if any alerts have been generation on the cluster or in vprobe.
  • If there is an error or alert related to the end device connectivity or authentication, try checking the reachability of the end device from the gateway with the following commands:
    • to ping the scan hostname provided in the configuration: {ping <scan name>}
    • to try telnet: {telnet <scan name> <Port>}
    • to try ssh to the end device: {ssh <username>@<node IP Address>}
    • to connect to the gcli: {gcli} {db oracledb <scan_name> <username> <password> <db_port> <db_name>:servicename 15000 10000 insecure Yes "SELECT INST_ID, INSTANCE_NUMBER, INSTANCE_NAME, HOST_NAME FROM gv$instance"}
    • to try SSH to nodes: {ssh <user name>@<node IPAddress>}