DB2 Monitoring issues

I have been trying to setup db2 monitoring using IBM DB2 template. We have installed the DB2 client on the solarwinds APE and all drivers and required packages in the AIX db2 server as per the documentation

documentation.solarwinds.com/.../SAM-IBM-DB2-sw4897.htm

I am still getting this below error for all component monitors, Is anyone is aware how to fix it..

Component Error:

ODBC data source returned an error. [IM002] [unixODBC][Driver Manager]Data source name not found, and no default driver specified

Thank you in advance.

@aLTeReGo

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

Typically the most common reason for this error is that people tend to install the 64bit ODBC driver, rather than the 32bit. By default, the SAM looks for a 32bit ODBC driver. However, this can be changed by editing the application, expanding the 'Advanced' section, and selecting 64Bit under 'Platform to run polling job on'.

Note that some drivers use a different connection string for x86 than x64. That will require additional changes to the template before it will work. For that reason, it's usually simpler/easier to just install the x86 driver to fix this issue than it is to change everything over to use the 64bit ODBC driver.

sannatar

Thank you @aLTeReGo for the response.

We have installed 32 bit, (v11.5.5_nt32_odbc_cli). However I changed x86 and tested, it is still the same error.

aLTeReGo

The issue is undoubtedly the connection string. It's my guess that the template was created using an OLE driver, rather than the CLI driver. That's just a guess, and one I can't confirm right now due to weather conditions impacting both power and internet connectivity to my lab. I would recommend reviewing the following URLs for the proper connection string to use. I recommend updating the connection string of only one component within the template and using the 'test' button to verify that it works. Once you find the correct ODBC connection string for your driver, then update the remaining components.

https://www.connectionstrings.com/ibm-db2/

https://www.connectionstrings.com/ibm-db2-odbc/

If for any reason none of ODBC connection strings in the links above seem to work, you can troubleshoot the driver and connectivity issues outside of Orion/SAM by opening the ODBC Windows Control Panel attempting to connect to your DB2 database there.

sannatar

Thanks for all the inputs, But we just figured out Preferred polling method was set to Agent.

After changing it to Agentess it started working,