What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Monitor DB2 database

Votes:

0

Your Vote:

Up

Down

Hello,

I have to monitor DB2 database. So I am using ADO sensor but I have the following message "The 'IBMDADB2' provider is not registered on the local machine."

My connection string is like : "Provider=IBMDADB2;Database=myDataBase;Hostname=myServerAddress;Protocol=TCPIP; Port=50000;Uid=myUsername;Pwd=myPassword;"

Does anyone have already configure ado sensor for DB2 ? My conncetion string syntax is OK ?

Thanks for your response.

ado database db2

Created on Jul 19, 2017 7:42:31 AM by  toto251 (0) 1



5 Replies

Votes:

0

Your Vote:

Up

Down

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

Created on Jul 19, 2017 9:24:06 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello,

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

Do you have any other ideas ?

Thanks :)

Created on Jul 19, 2017 10:13:42 AM by  toto251 (0) 1



Votes:

0

Your Vote:

Up

Down

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.

Created on Jul 19, 2017 10:37:32 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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...}

Created on Jul 19, 2017 11:54:42 AM by  toto251 (0) 1

Last change on Jul 20, 2017 12:35:14 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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

Created on Jul 20, 2017 12:37:04 PM by  Stephan Linke [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.