| Author |
Message
|
| Harsha_AS |
 Posted: Sun Dec 04, 2011 6:54 pm Post subject: MB - Data source name not found |
 |
|
Apprentice
Joined: 04 Dec 2011
Posts: 26
|
I am trying to map the target element from database table by giving the selet function in the mappping node. But i am getting the following error. I have specifed the DSN name in the properties of the mapping node, but still getting the error. Could anyone please help me on this?
Insert Type:INTEGER:5
Text:CHARACTER:MicrosoftODBC Driver Manager Data source name not found and no default driver specified |
|
| Back to top |
|
 |
| nukalas2010 |
| Posted: Sun Dec 04, 2011 10:11 pm Post subject: Re: MB - Data source name not found |
|
|
Master
Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....
|
It's clearly shows you the problem that...
Data source name not found and no default driver specified |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Dec 05, 2011 5:30 am Post subject: Re: MB - Data source name not found |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Harsha_AS wrote: |
| I have specifed the DSN name in the properties of the mapping node, but still getting the error. |
Test the DSN with mqsicvp if you have that. I don't know because you've not bothered to mention any details.
If that doesn't help you, post again with some more details of how you've configured the DSN for use with broker other than typing a name into the mapping node. A few pointers on what version of broker you're using and what platform you're running on might be nice as well.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Harsha_AS |
| Posted: Mon Dec 05, 2011 6:48 pm Post subject: |
|
|
Apprentice
Joined: 04 Dec 2011
Posts: 26
|
command mqsicvp is not working. i am getting "'mqsicvp' is not recognized as an internal or external command," error.
I have created the database from IBM DB2 command console and DSN from the administrator tool.
Settings -> Control Panel -> Administrative tools ->ODBC Data Source Admin -> System DSN
And the MB version i am using is "Version: 6.1.0" and i am running in Windows XP.
I am able to use the same data base and DSN from the compute node for accessing some other tables. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Dec 05, 2011 10:05 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Harsha_AS wrote: |
command mqsicvp is not working. i am getting "'mqsicvp' is not recognized as an internal or external command," error.
I have created the database from IBM DB2 command console and DSN from the administrator tool.
Settings -> Control Panel -> Administrative tools ->ODBC Data Source Admin -> System DSN
And the MB version i am using is "Version: 6.1.0" and i am running in Windows XP.
I am able to use the same data base and DSN from the compute node for accessing some other tables. |
Ok, 6.1 (I hope you have patched it from 6.1.0.0 though...) does not have the very much enhanced functionality in this area that 7.0 (And later) gives you with mqsicvp.
Then the 3rd and final step is to tell broker about the DSN using the 'mqsisetdbparms' command.
Are you sure that you have kept the case of the DSN the same throuought?
I've seen oddities like this (with some types of DB) before.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
