DSR.MetaGeta(GET.DSNINFO):Cannot open database requested

antojj · Post by **antojj** » Wed Aug 09, 2006 5:34 am

Hi All,

I am querying from SQL server database using the ODBC stage.
The query is just selecting a single column from the source table.

I have created a ODBC Connection string in the DS Server. I have a user name / pwd for the same. I validated the test connection in the Server.

When entering the "Data Source Name", "username", "Password" in the ODBC stage and clicking the "Get SQL Info" button throws an error as follows:

DSR.MetaGeta(GET.DSNINFO)(SQLConnect('DSMISSqlSvr','MISCENTRALINTEGRATION')): BCI Error:
SQLSTATE=37000,CODE=4060,[DataStage][SQL Client][ODBC][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database requested in login 'MIS'. Login fails.

Not sure how this is happening.

If anyone has any thoughts please share.

Have to do a delivery by today.

Regards,

ray.wurlod · Post by **ray.wurlod** » Wed Aug 09, 2006 6:10 am

All of the square bracketed fields at the beginning of the message demonstrate that the ODBC driver was, in fact, able to connect to SQL Server. At that point, "Login fails." indicates that your credentials were not correct. Check that they are correct in DataStage, check that that user exists in SQL Server.

antojj · Post by **antojj** » Wed Aug 09, 2006 6:25 am

The ODBC driver is correct and still i am able to connect from the Sql Server Query Analyzer.

The point here i noticed is i changed the driver from
"Ascential SQL Server Wire Protocol" to "Sql Server".

It is working fine now.

Not sure what is happening in the driver???
Is there any change that distinguishes the driver?

Regards,

ray.wurlod · Post by **ray.wurlod** » Wed Aug 09, 2006 6:43 am

It's really annoying that the Ascential applications now seem to insist upon the Ascential-supplied ODBC drivers being used, and resist the use of other ODBC drivers even those that are ODBC 3.0 compliant. C'mon, guys, isn't ODBC a STANDARD?!! If you try to use the Ascential-supplied drivers from any other application, you'll get an error message explaining that they are only licensed for use with Ascential clients, which ultimately means you need two DSNs for each data source. Sheesh!

hexa · Post by **hexa** » Fri Aug 10, 2007 2:40 am

Hi,

I am also phasing same issues..

DSR.MetaGeta(GET.DSNINFO)(SQLConnect('DSMISSqlSvr','MISCENTRALINTEGRATION')): BCI Error:
SQLSTATE=37000,CODE=4060,[DataStage][SQL Client][ODBC][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database requested in login 'MIS'. Login fails.

I tried changing Driver SQL Server also but its not working...

Pls. help me in this out..

thanks lot

Hexa