Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Archive > 2017October06 - Cleanup > Monitor an Oracle 12c database on Ignite 8.1 to 8.3

Monitor an Oracle 12c database on Ignite 8.1 to 8.3

Overview

Ignite supports Oracle 12c as both a repository database and as a monitored target. However, Oracle 12c has not been fully tested on Ignite. Caution should be taken when monitoring a production or other critical instance.

Environment

SolarWinds DPA has native support for Oracle 12c single tenant since SolarWinds DPA 9.0. The article below is for Confio Ignite 8.1 to 8.3. SolarWinds recommends all customers still using Confio Ignite to upgrade to SolarWinds DPA. 

Steps

  1. An upgraded Oracle JDBC driver or SQL*Net parameter modification may be required. Ignite ships with an Oracle 10g JDBC driver so that it can connect to both 11g and 9i instances. However, that driver has issues connecting to some Oracle 12c instances. If the following error is seen, you have this issue: "ORA-28040: No matching authentication protocol". There are two workarounds for this problem (either solution works, only need to implement one of them):
    • Upgrade to an Oracle 11g or 12c JDBC driver. Follow these instructions to update the Oracle JDBC driver for Ignite. See important notes below about updating the JDBC driver.
    • Set SQLNET.ALLOWED_LOGON_VERSION parameter on both client and servers to values that matches the minimum version supported in the system, e.g. 9 or 10.
  2. Oracle 12c now includes two types of users, common (global to all databases) or local (specific for a pluggable database). When using a 12c database as a repository or registering it for monitoring, either can be used as follows:
    • Common User - when running the Ignite wizard to either create a repository or register an instance for monitoring, the Ignite wizard first logs in as a DBA user to check privileges, optionally create a user account among other tasks. The default database at that point is CDB$ROOT and when Ignite tries to create a standard user, e.g. IGNITE, the following error may be seen: "ORA-65096: invalid common user or role name". The workaround for this error is to use a new format for common usernames, e.g. C##IGNITE. The C## at the front of the username informs Oracle it is a common user.
    • Local User - pre-create a pluggable database with a local user. When using the Ignite wizard, either to create the repository or register an instance for monitioring, select the "Use Existing User" option in the Ignite wizards. Provide the pre-created username to the wizard and Ignite will skip the username creation step.

Notes for Updating the JDBC Driver

  1. If you upgrade the JDBC driver, it could be overwritten if you reinstall or upgrade Ignite. Depending on which version of JDBC ships with Ignite you may need to re-install the JDBC driver as a result.
  2. If you upgrade to the Oracle 12c JDBC driver (ojdbc6.jar) you must be running a JRE/JDK of at least 1.6. This is the version that ships with Ignite for Windows and Linux, but if you have upgraded or installed the 64 bit JRE/JDK, make sure it is at least 1.6. To check the version you can use the "java -version" command.
  3. A similar note to #2 above. If you upgrade to the Oracle 11g JDBC driver (ojdbc5.jar), you must be running at least a JRE/JDK 1.5 or higher.
  4. Oracle JDBC drivers are typically backwards compatible for two versions. If you install a 12c JDBC driver, you may not be able to monitor Oracle 9i databases. If you install an 11g JDBC driver, you may not be able to monitor 8i databases.

 

 

Last modified

Tags

Classifications

Public