Monitor DB2 database

Hi Toto251,

Are the DB2 drivers installed on the PRTG server / Remote Probe? Because .NET can't connect to them via ADO without the drivers, as far as I can tell? This should be what you need.

Other versions can be found here.

Kind regards,
Stephan Linke, Tech Support Team

Hello,

Yes, the DB2 drivers are installed on the PRTG Server, and then configuring in the ODBC.

Do you have any other ideas ?

Thanks :)

Darnit :) Could you get me the output of the script disclosed here? Just paste it into PowerShell ISE, add

Get-OledbRegistered

at the end of the script and hit play, it should work straight away.

This a ODBC connection. So I don't see in oled part but I see it in odbc driver

PS C:\Users\prtg> Get-OledbRegistered

SOURCES_NAME        : SQLOLEDB
SOURCES_PARSENAME   : {0C7FF16C-38E3-11d0-97AB-00C04FC2AD98}
SOURCES_DESCRIPTION : Microsoft OLE DB Provider for SQL Server
SOURCES_TYPE        : 1
SOURCES_ISPARENT    : False
SOURCES_CLSID       : {0C7FF16C-38E3-11d0-97AB-00C04FC2AD98}

SOURCES_NAME        : MSDataShape
SOURCES_PARSENAME   : {3449A1C8-C56C-11D0-AD72-00C04FC29863}
SOURCES_DESCRIPTION : MSDataShape
SOURCES_TYPE        : 1
SOURCES_ISPARENT    : False
SOURCES_CLSID       : {3449A1C8-C56C-11D0-AD72-00C04FC29863}

SOURCES_NAME        : ADsDSOObject
SOURCES_PARSENAME   : {549365d0-ec26-11cf-8310-00aa00b505db}
SOURCES_DESCRIPTION : OLE DB Provider for Microsoft Directory Services
SOURCES_TYPE        : 1
SOURCES_ISPARENT    : False
SOURCES_CLSID       : {549365d0-ec26-11cf-8310-00aa00b505db}

SOURCES_NAME        : MSDASQL
SOURCES_PARSENAME   : {c8b522cb-5cf3-11ce-ade5-00aa0044773d}
SOURCES_DESCRIPTION : Microsoft OLE DB Provider for ODBC Drivers
SOURCES_TYPE        : 1
SOURCES_ISPARENT    : False
SOURCES_CLSID       : {c8b522cb-5cf3-11ce-ade5-00aa0044773d}

SOURCES_NAME        : MSDASQL Enumerator
SOURCES_PARSENAME   : {c8b522cd-5cf3-11ce-ade5-00aa0044773d}
SOURCES_DESCRIPTION : Microsoft OLE DB Enumerator for ODBC Drivers
SOURCES_TYPE        : 2
SOURCES_ISPARENT    : False
SOURCES_CLSID       : {c8b522cd-5cf3-11ce-ade5-00aa0044773d}

SOURCES_NAME        : SQLOLEDB Enumerator
SOURCES_PARSENAME   : {DFA22B8E-E68D-11d0-97E4-00C04FC2AD98}
SOURCES_DESCRIPTION : Microsoft OLE DB Enumerator for SQL Server
SOURCES_TYPE        : 2
SOURCES_ISPARENT    : False
SOURCES_CLSID       : {DFA22B8E-E68D-11d0-97E4-00C04FC2AD98}

SOURCES_NAME        : MSDAOSP
SOURCES_PARSENAME   : {dfc8bdc0-e378-11d0-9b30-0080c7e9fe95}
SOURCES_DESCRIPTION : Microsoft OLE DB Simple Provider
SOURCES_TYPE        : 1
SOURCES_ISPARENT    : False
SOURCES_CLSID       : {dfc8bdc0-e378-11d0-9b30-0080c7e9fe95}

PS C:\Users\prtg> Get-OdbcDriver

Name      : Microsoft Access-Treiber (*.mdb)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Driver do Microsoft Paradox (*.db )
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Driver do Microsoft Excel(*.xls)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Microsoft Text Driver (*.txt; *.csv)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Driver da Microsoft para arquivos texto (*.txt; *.csv)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Microsoft dBase-Treiber (*.dbf)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : SQL Server
Platform  : 32-bit
Attribute : {Driver, APILevel, FileUsage, Setup...}

Name      : Microsoft Excel Driver (*.xls)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Driver do Microsoft dBase (*.dbf)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Microsoft Paradox-Treiber (*.db )
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Microsoft ODBC for Oracle
Platform  : 32-bit
Attribute : {Driver, APILevel, FileUsage, Setup...}

Name      : Microsoft Text-Treiber (*.txt; *.csv)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Microsoft Excel-Treiber (*.xls)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Microsoft Access Driver (*.mdb)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Driver do Microsoft Access (*.mdb)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Microsoft Paradox Driver (*.db )
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : Microsoft dBase Driver (*.dbf)
Platform  : 32-bit
Attribute : {Driver, APILevel, FileExtns, FileUsage...}

Name      : IBM DB2 ODBC DRIVER - C_IBMDB2_clidriver
Platform  : 32-bit
Attribute : {Driver, Setup, CPTimeout}

Name      : SQL Server
Platform  : 64-bit
Attribute : {Driver, APILevel, FileUsage, Setup...}

Then you should be able to register it via:
regsvr32 <IBM DB2 ODBC DRIVER - C_IBMDB2_clidriver dll file>