Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Database Performance Analyzer (DPA) > Registering an Oracle database instance that uses only SHA-2 to calculate checksums

Registering an Oracle database instance that uses only SHA-2 to calculate checksums

Updated May 4, 2017


If an Oracle database instance is configured to use only SHA-2 (Secure Hash Algorithm 2) to calculate checksums, the following error message is displayed when you try to register it as a monitored instance or as the DPA repository:

An unknown error has occurred. The provided message is "Could not get JDBC Connection; nested exception is java.sql.SQLException: Oracle Error ORA-12650".

To enable DPA to connect to Oracle databases that use only SHA-2, you must update the JDBC driver as described below.

After you update the driver, DPA will not be able to connect to database instances that run Oracle 9 or earlier. If you need to monitor Oracle 9 database instances, keep the existing driver and configure other Oracle instances to use SHA-1. 


  • DPA 11.0 and earlier


  1. Stop DPA:
    • On Windows, stop the Ignite PI Server service.
    • On Linux, run the command from the DPA directory.
  2. Go to the following folder:


  3. Rename the following file:

    Original name New name
  4. Go to Oracle Database JDBC Driver & UCP Downloads.
  5. Download ojdbc7.jar and place it in the following location:


  6. Download Patch 20960881 for release from Oracle.

    For more information about this patch, see Oracle support

  7. Extract the downloaded file.
  8. Go to the 20960881\files\jdbc\lib\ojdbc7.jar directory and copy the entire \oracle directory.
  9. Paste the \oracle directory in the following location:


    The resulting path should be:


  10. Restart DPA:
    • On Windows, restart the Ignite PI Server service.
    • On Linux, run the command from the DPA directory.

You can now register database instances that are configured to use only SHA-2.


Last modified
12:49, 5 May 2017