Traverse Oracle Monitor Troubleshooting - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Traverse Oracle Monitor Troubleshooting - Connect IT Community | Kaseya

QUESTION:

How do I troubleshoot the Oracle monitor tests that are not working?

RESOLUTION:

In order for Traverse to monitor the Oracle database, please make sure the Oracle database supports remote network (SQL*net) queries
Clients/applications to test remote connectivity (please test from the DGE or DGEx server that will be monitoring the Oracle database):
-- TNSPING

-- TOAD

-- SQL*Plus
It has been determined that there may be connection issues with specific versions Oracle Database. One known version that may have issues with Traverse Oracle monitoring is 12.1:
"In 12.1, the default value for the SQLNET.ALLOWED_LOGON_VERSION parameter has been updated to 11. This means that database clients using pre-11g JDBC thin drivers cannot authenticate to 12.1 database servers unless theSQLNET.ALLOWED_LOGON_VERSION parameter is set to the old default of 8.

This will cause a 10.2.0.5 Oracle RAC database creation using DBCA to fail with the ORA-28040: No matching authentication protocol error in 12.1 Oracle ASM and Oracle Grid Infrastructure environments."

-- Set SQLNET.ALLOWED_LOGON_VERSION=8 in the oracle/network/admin/sqlnet.ora file

Source: http://stackoverflow.com/questions/24100117/ora-28040-no-matching-authentication-protocol-exception
Review Oracle configuration files:

sqlnet.ora

tnsnames.ora

listener.ora
At the time of this writing, the JDBC driver for Oracle Database supports the following encryption implementations within sqlnet.ora:

RC4_256
RC4_128
RC4_56
RC4_40
DES
DES40

A Wireshark capture can provide additional troubleshooting information to determine what part of the connection attempt is having issues.

To get started on reviewing the Wireshark capture yourself:
-- Filter on the listener port, in my example I am using port '1521' (e.g. tcp.port == 1521)

-- Once filtered, make sure to decode the information on port '1521' as TNS. To do this, right-click on one of the packets and select 'Decode As'. Set port '1521' to TNS

--If assistance is required in reviewing the Wireshark capture further, support is more than happy to assist. Please include the Wireshark capture upon creating a support ticket

APPLIES TO

All versions of Traverse

REFERENCE

None