Run Live Demo


Supported Versions 9, 10g, 11g
Collection Methods JDBC Queries
Data Collected Oracle Data CollectionsDownload PDF
  • Oracle account with CONNECT and SELECT_CATALOG_ROLE privilege on the monitored instance.
  • Longitude JDBC queries to Oracle instances are not blocked by by a firewall.
  1. Use Monitor Devices
  2. If necessary, select a Longitude Remote Agent.
  3. Select Oracle
  4. Enter the name of the Oracle server to be monitored in the Computers field.
  5. The Instance value is used by Longitude to distinguish between different Oracle instances being monitored on the same server. It is recommended to set the Instance to be the same as the Oracle Instance, but any unique string may be used. Registering the same Instance twice on the same computer will overwrite the details of the first registration.
  6. Enter the name of the Oracle Instance being monitored. This name should be resolvable through the tns_listener on the Oracle server.
  7. Enter the name of the Oracle User account.
  8. Enter the Password for the Oracle User
  9. Enter the Port used to communicate with Oracle via JDBC. The default port for Oracle is 1521.
  10. Enter the TopNQueries value – this will be used for the maximum number of results returned by the Oracle_LongQueries collector. The default value is 10.
  11. Click Monitor
  12. Repeat the configuration steps with different Instance and Oracle Instance values to monitor additional Oracle instances on he same server.
  • Collections fail with a Read timed out error:
    Longitude is unable to connect with the Oracle server on the specified port. Check the following:

    • Check the Oracle server is being resolved to the correct IP Address.
    • Check the port used by Oracle
    • If other Longitude applications are monitored on the Oracle server, check the Computer Status screen to determine the agent used for collecting data for the Oracle server. All Longitude applications will be collected by this agent, regardless of the selection in the Monitoring configuration. Verify that the Agent for the Oracle server is able to make a JDBC connection over the specified Oracle port.
    • The Oracle listener port can be checked using a Port Transaction.
  • Collections fail with a 12505 reads ‘TNS: listener could not resolve SID given in connection description error:
    Check that the Oracle Instance specified is correct.
  • Collections fail with a The Network Adapter could not establish the connection error:
    Check that the tns_listener is running on the Oracle server.
  • Collections fail with an ORA-01017: invalid username/password; logon denied error:
    Check that the username and password for the specified Oracle instance are correct.
  • Collections fail with an ORA-01045: user … lacks CREATE SESSION privilege; logon denied error:
    The Oracle user account does not have CONNECT privilege to the specified Oracle Instance.
  • Collections fail with an ORA-00942: table or view does not exist error:
    The Oracle user account does not have SELECT_CATALOG_ROLE privilege to the specified Oracle Instance.


OpenManage SnmpTrap