If you are unable to create a new account, please email support@bspsoftware.com

 

DM-DBM-0303 The DBMS driver 'OLEDB' is not supported.

Started by vijayhai, 14 Jan 2014 12:11:10 PM

Previous topic - Next topic

vijayhai

Hello,

We are trying to use a SQL server source.

All the details of the source is fed into the alias file and when the rundsjob is run it is giving the below error.

DM-DBM-0303 The DBMS driver 'OLEDB' is not supported.

Content of alias file
XXXX 'ABCD' OLEDB  'User Id=UsrRead;Password=password;Database=ACDB;Data Source=HEX001\\MSSQLATL;Provider=sqloledb (SQL Server OLE-DB);Integrated Security=FALSE;COGNOSSQL=FALSE' ''

Connection to oracle seems to work fine.

About the environment : On 64 bit linux enviroment
DM catalog db : oracle

Please let me know if anybody had faced similar problems and how was it resolved.

Appreciate your help.

Thanks
VJ


MFGF

Hi,

"Provider=sqloledb (SQL Server OLE-DB)" would be the correct provider for SQL Server 2000. Is this what you are using?

If you have SQL Server 2005 it needs to be "Provider=sqlncli (SQL Server 2005 native client)"
If you have SQL Server 2008 it needs to be "Provider=sqlncli10 (SQL Server 2008 native client)"
If you have SQL Server 2012 it needs to be "Provider=sqlncli11 (SQL Server 2012 native client)"

Cheers!

MF.
Meep!

vijayhai

Thanks MF,

We are using SQL Server 2008. I have updated Provider=sqlncli10. Still giving the same issue.

Is there any configuration setting need to change at data manager level to make it understand what OLEDB is  ?

Thanks
VJ

MFGF

Hi,

No - Data Manager already understands what OLEDB is. What version of Data Manager are you using? Did you set the Provider to "sqlncli10 (SQL Server 2008 native client)" - including the text and parentheses exactly as I put them here?

Do you have a catalog? I'm wondering why you are using a db alias file if you do? If so, open up the catalog in Data Manager Designer and take a look at the definition of the data source there. What do you see?

Cheers!

MF.
Meep!

vijayhai

Thanks MF.

We made it work using ODBC using SQL server driver from Microsoft. It solved the purpose.

Thanks
VBS