Troubleshoot > Troubleshooting and Limitations – Discovery Modules > Troubleshooting and Limitations – Oracle Database Server Discovery

Troubleshooting and Limitations – Oracle Database Server Discovery

This section describes troubleshooting and limitations for Oracle Database Server discovery.

  • If you need to discover Oracle 8g, use the following values in jdbcDrivers and jdbcPreUrls:

    jdbcDrivers:

    <oracle>com.inet.ora.OraDriver</oracle>
    <oracleSSL>com.mercury.jdbc.oracle.OracleDriver</oracleSSL>

    jdbcPreUrls:

    <oracle>jdbc:inetora:%%ipaddress%%:%%protocol_port%%:%%sqlprotocol_dbsid%%?logging=false&amp;loginTimeout=%%protocol_timeout%%</oracle>
    <oracleSSL>jdbc:mercury:oracle://%%ipaddress%%:%%protocol_port%%;ServiceName=%%sqlprotocol_dbsid%%</oracleSSL>
  • Oracle Data Guard Discovery cannot distinguish the logic standby instance or physical standby instance. SQL query cannot fetch such information if standby databases cannot be connected by SQL*Plus.
  • Oracle account will be locked if Data Flow Probe tries to log in to Oracle with SQL*Plus many times but fails. This depends on the Oracle configuration.