Ask the Community
Groups
Traverse Oracle Monitor Troubleshooting - Connect IT Community | Kaseya
<main> <article class="userContent"> <h3 data-id="question"><strong>QUESTION:</strong></h3> <p>How do I troubleshoot the Oracle monitor tests that are not working?</p> <p> </p> <p><strong>RESOLUTION:</strong></p> <ul><li>In order for Traverse to monitor the Oracle database, please make sure the Oracle database supports remote network (SQL*net) queries<br><br></li> <li>Clients/applications to test remote connectivity (please test from the DGE or DGEx server that will be monitoring the Oracle database):<br>-- TNSPING<br><br>-- TOAD<br><br>-- SQL*Plus<br><br></li> <li>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:<br><p><em>"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.</em></p> <p><em>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."</em></p> <br>-- Set SQLNET.ALLOWED_LOGON_VERSION=8 in the oracle/network/admin/sqlnet.ora file<br><br><br>Source: <a href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fstackoverflow.com%2Fquestions%2F24100117%2Fora-28040-no-matching-authentication-protocol-exception">http://stackoverflow.com/questions/24100117/ora-28040-no-matching-authentication-protocol-exception</a><br><br></li> <li>Review Oracle configuration files:<br><br>sqlnet.ora<br><br>tnsnames.ora<br><br>listener.ora<br><br></li> <li>At the time of this writing, the JDBC driver for Oracle Database supports the following encryption implementations within sqlnet.ora:<br><br>RC4_256<br>RC4_128<br>RC4_56<br>RC4_40<br>DES<br>DES40</li> </ul><ul><li>A Wireshark capture can provide additional troubleshooting information to determine what part of the connection attempt is having issues.<br><br>To get started on reviewing the Wireshark capture yourself:<br>-- Filter on the listener port, in my example I am using port '1521' (e.g. tcp.port == 1521)<br><br>-- 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<br><img src="/attachments/token/B353SkII2hmm3y0EC3mEnOYFH/?name=oracle.png" alt="oracle.png" width="844" height="366" class="embedImage-img importedEmbed-img"></img><br><br><img src="/attachments/token/uKX6ggJwMDCi7ZUaPRgv3yIqC/?name=oracle2.png" alt="oracle2.png" class="embedImage-img importedEmbed-img"></img><br><br> --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</li> </ul><p> </p> <p><strong>APPLIES TO </strong></p> <p>All versions of Traverse </p> <p> </p> <p><strong>REFERENCE </strong></p> <p>None</p> </article> </main>