The SQL-Toolkit plugin require the respective database clients to be installed on the Netprobe machine. This article also applies to Oracle, Sybase and Sybase Server plugins.
Database Client Installation
For monitoring individual databases, the respective database client (e.g. Oracle Client) will need to be installed on the Netprobe machine. Please refer to the section named Configure the Netprobe and database client libraries in the SQL-Toolkit Plugin User Guide.
For time to time there are changes in operating systems and databases. Please refer to the Compatibility Matrix if the versions of software are supported by ITRS.
32-bit and 64-bit Database Libraries
The filename of Netprobe binary can usually determine its bit version. The _64 suffix means that it is 64-bit, otherwise it is likely 32-bit.
For Linux and Unix, the "file" command can find out whether an executable or library file is 32 or 64 bit.
$ file ./netprobe.linux_64
64-bit Oracle Client
$ file libclntsh.so.11.1
Errors in Netprobe Log
Unable to locate Database Client
If Netprobe is unable to locate the database client, users can check the Netprobe log for errors.
Example error message for Oracle database:
libclntsh.so: cannot open shared object file: No such file or directory
Example error message for Sybase ASE database:
libsybintl_r64.so: cannot open shared object file: No such file or directory
32-bit Netprobe but with 64-bit Database Client
wrong ELF class: ELFCLASS64
64-bit Netprobe but with 32-bit Database Client
wrong ELF class: ELFCLASS32
32-bit and 64-bit Mismatched on IBM AIX
(The below error message is for Oracle database with library file libclntsh.so)
Could not load module libclntsh.so. System error: Exec format error
32-bit and 64-bit Mismatched on Windows
(The below error message is for Oracle database with library file oci.dll)
oci.dll: %1 is not a valid Win32 application