| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unable to connect to DB from WMB(Compute node using ODBC DSN |
View previous topic :: View next topic |
| Author |
Message
|
| vininx |
 Posted: Mon Dec 12, 2011 7:33 pm Post subject: Unable to connect to DB from WMB(Compute node using ODBC DSN |
 |
|
Acolyte
Joined: 13 Oct 2009
Posts: 69
|
Hi All,
I am having a message flow which is throwing below error in syslog while connecting to the DB,
| Code: |
BIP2322E: Database error: SQL State 'IM002'; Native Error Code '0'; Error Text '[DataDirect][ODBC lib] System information file not found. Please check the ODBCINI environment variable.' |
I have associated the user and password with mqsisetdbparms. When I use mqsicvp command with user name and password to test the DSN I am able to connec to the database, but when I issue without user name and password, it is throwing the below error,
| Code: |
BIP8272E: Datasource 'ORA_DSN' has not been associated with broker 'MB7BROKER'.
This invocation of the mqsicvp command requires that the datasource name has been associated with the broker, using the mqsisetdbparms command.
Check that this datasource has been associated with the broker |
I am using WMB7.0.0.3 in Linux.I have read that once when mqsisetdbparms is set we need to restart the execution group for it to connect to the DB. I did that , but, still the above error occurs.I havent tried by bouncing the broker. Please confirm whether we need to bounce the broker for mqsisetdbparms to work or am I missing anything in configuration?
My Config settings:-
----------------------
1) Edited odbc.ini to configure the remote DB. Edited all 3 stanzas with appropriate values
2) The odbc.ini has mqm:mqbrkrs, placed in /var/mqsi/odbc/odbc.ini
3) Set the ODBCINI variable in my own shell script and placed in /var/mqsi/common/profile path
4) Used mqsisetdbparms for authorizing user database.
5) Restarted execution group.
I am sorry that I've posted the same in another thread too. |
|
| Back to top |
|
 |
| Sam Uppu |
| Posted: Tue Dec 13, 2011 3:02 pm Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| Check if the ODBCINI environment variable is populated with the value you set. |
|
| Back to top |
|
|
| MrSmith |
| Posted: Wed Dec 14, 2011 1:48 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
if the above doesnt work post the section (if allowed) of the odbc.ini you have configure and the mqsisetdbparms you used, sometimes its hard to see the wood for the trees
_________________
-------- *
“Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read.” |
|
| Back to top |
|
|
| adubya |
| Posted: Wed Dec 14, 2011 8:51 am Post subject: |
|
|
Partisan
Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK
|
Login to the Linux WMB server as the user broker runs under.
Type "cat $ODBCINI"
Does this command result in your changed odbc.ini file being displayed ? |
|
| Back to top |
|
|
| vininx |
| Posted: Wed Dec 14, 2011 8:19 pm Post subject: |
|
|
Acolyte
Joined: 13 Oct 2009
Posts: 69
|
Hi,
I haverestarted the broker and it worked for me |
|
| Back to top |
|
|
|
|
|
|
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
