| Author |
Message
|
| bloomy |
 Posted: Fri Dec 16, 2011 11:11 am Post subject: |
 |
|
Acolyte
Joined: 11 Feb 2009
Posts: 61
Location: Bloomington, IL USA
|
| Quote: |
BIP2322E: Database error: SQL State 'IM002'; Native Error Code '0'; Error Text '[DataDirect][ODBC lib] Data source name not found and no default driver specified'.
BIP8891E: Verification failed. Failed to connect to datasource 'DNSBRK1' with user ID 'mbadmin'. Preceding messages contain further information.
|
Are you sure there is another broker running on the same server, if yes then I would suggest to try a manual connection from this server to the DB using "db2 connect to..." command with the credentials you have entered for the broker. If this is succesful I am sure that your odbc.ini has something setup incorrectly, 3 things you can check.
1. You have the correct driver in the odbc stanza in odbc.ini
2. InstallDir is correct, this looks something like this /opt/ibm/mqsi/6.1/ODBC/...
Looking at the error you got, it definitely looks like a credentials problem so try connecting to the DB from db2 prompt as suggested above. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Fri Dec 16, 2011 11:43 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| sprasad |
| Posted: Fri Dec 16, 2011 12:40 pm Post subject: Re: Error while starting Message Broker |
|
|
Novice
Joined: 15 Dec 2011
Posts: 24
|
| Vitor wrote: |
| sprasad wrote: |
| Its been a while this Broker is restarted. |
If there was no ODBC connection the broker would not have been running, or at least not working.
| sprasad wrote: |
| Is there a chance that someone has changed the password and it has to reset in DSN files? |
The password isn't in the ini file. If it's been changed then yes you'd need to update the broker.
I did change the password using mqsichangebroker command. But mqsicvp command is still failing with the below error.BIP2322E: Database error: SQL State 'IM002'; Native Error Code '0'; Error Text '[DataDirect][ODBC lib] Data source name not found and no default driver specified'.
BIP8891E: Verification failed. Failed to connect to datasource 'UAQ4BKDB' with user ID 'wbrkadm'. Preceding messages contain further information.
| sprasad wrote: |
| the ini file looks fine |
I thought we started this with the ini file not having an entry for the non-starting broker? So how is it fine? |
yes but as I told you the .odbc.ini. file was hidden and I was checking the wrong file. I checked the right file and it has entries. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 16, 2011 12:54 pm Post subject: Re: Error while starting Message Broker |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sprasad wrote: |
| I checked the right file and it has entries. |
Then it's as simple as a mismatch in credentials.
Either broker is using the wrong password (which isn't any password you've found in the ini file) or the password in the database isn't what you think it is.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sprasad |
| Posted: Fri Dec 16, 2011 12:56 pm Post subject: |
|
|
Novice
Joined: 15 Dec 2011
Posts: 24
|
| bloomy wrote: |
| Quote: |
BIP2322E: Database error: SQL State 'IM002'; Native Error Code '0'; Error Text '[DataDirect][ODBC lib] Data source name not found and no default driver specified'.
BIP8891E: Verification failed. Failed to connect to datasource 'DNSBRK1' with user ID 'mbadmin'. Preceding messages contain further information.
|
Are you sure there is another broker running on the same server, if yes then I would suggest to try a manual connection from this server to the DB using "db2 connect to..." command with the credentials you have entered for the broker. If this is succesful I am sure that your odbc.ini has something setup incorrectly, 3 things you can check.
1. You have the correct driver in the odbc stanza in odbc.ini
yes the stanza has correct driver
2. InstallDir is correct, this looks something like this /opt/ibm/mqsi/6.1/ODBC/...
the install directory is correct.
Looking at the error you got, it definitely looks like a credentials problem so try connecting to the DB from db2 prompt as suggested above. |
I did try db2 connect with the userid and am able to connect.
there is another broker running on the same server, but odbc.ini file is different for both the brokers. Also the references are correct in broker configurations. |
|
| Back to top |
|
|
| sprasad |
| Posted: Fri Dec 16, 2011 12:59 pm Post subject: Re: Error while starting Message Broker |
|
|
Novice
Joined: 15 Dec 2011
Posts: 24
|
| Vitor wrote: |
| sprasad wrote: |
| I checked the right file and it has entries. |
Then it's as simple as a mismatch in credentials.
Either broker is using the wrong password (which isn't any password you've found in the ini file) or the password in the database isn't what you think it is. |
Hi Vitor, as I explained, I have changed the password using mqsichangebroker command. Correct if i am using the wrong command. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 16, 2011 1:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Then I suggest:
a) An ODBC trace to see what's going on
b) A PMR if that doesn't help
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sprasad |
| Posted: Fri Dec 16, 2011 3:17 pm Post subject: |
|
|
Novice
Joined: 15 Dec 2011
Posts: 24
|
I fixed the issue. Here is what happened.
The .profile for the userid i am using for all MB operations including database was pointing to mqsiprofile which has wron odbc.ini file. I corrected that. Once re-login I was able to start the Broker sucessfully.
Hope this helps. Thanks for your replies and support. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 16, 2011 5:33 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sprasad wrote: |
| The .profile for the userid i am using for all MB operations including database was pointing to mqsiprofile which has wron odbc.ini file. |
You shouldn't edit the IBM supplied .mqsiprofile. That way if it's changed by a future fix pack your changes won't be lost.
The reference to odbc.ini should be in .profile. Where you'd have seen it day 1 of your problem investigation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Dec 16, 2011 11:34 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
to add to Vitor's last comment,
If you have the ODBCINI environment variable defined in the ACCOUNT then it is easy to setup another broker on the same system that uses a totally different set of ODBC connections.
For example running SystemTest and UAT brokers on the same system.
The brokers run under different accounts and the accounts are setup to point to the right file via $ODBCINI.
To reiterate, DO NOT modify the mqsiprofile script supplied with the Broker Runtime. setup the $ODBCINI in the script that uses the mqsiprofile.
_________________
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 |
|
|
| sprasad |
| Posted: Sat Dec 17, 2011 1:38 am Post subject: |
|
|
Novice
Joined: 15 Dec 2011
Posts: 24
|
| Vitor wrote: |
| sprasad wrote: |
| The .profile for the userid i am using for all MB operations including database was pointing to mqsiprofile which has wron odbc.ini file. |
You shouldn't edit the IBM supplied .mqsiprofile. That way if it's changed by a future fix pack your changes won't be lost.
I did not change anything in .mqsiprofile but have changed the pointer to the right .mqsifile.
The reference to odbc.ini should be in .profile. Where you'd have seen it day 1 of your problem investigation. |
correct. |
|
| Back to top |
|
|
| sprasad |
| Posted: Sat Dec 17, 2011 1:41 am Post subject: |
|
|
Novice
Joined: 15 Dec 2011
Posts: 24
|
| smdavies99 wrote: |
to add to Vitor's last comment,
If you have the ODBCINI environment variable defined in the ACCOUNT then it is easy to setup another broker on the same system that uses a totally different set of ODBC connections.
For example running SystemTest and UAT brokers on the same system.
The brokers run under different accounts and the accounts are setup to point to the right file via $ODBCINI.
Yes. But here they are using two different mqsiprofile files. So I had to edit .profile file. And also the same userid is used for both TEST and UAT 
To reiterate, DO NOT modify the mqsiprofile script supplied with the Broker Runtime. setup the $ODBCINI in the script that uses the mqsiprofile. |
I did modify the .mqsiprofile. only .profile. |
|
| Back to top |
|
|
| adubya |
| Posted: Sat Dec 17, 2011 12:12 pm Post subject: |
|
|
Partisan
Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK
|
| sprasad wrote: |
| smdavies99 wrote: |
to add to Vitor's last comment,
If you have the ODBCINI environment variable defined in the ACCOUNT then it is easy to setup another broker on the same system that uses a totally different set of ODBC connections.
For example running SystemTest and UAT brokers on the same system.
The brokers run under different accounts and the accounts are setup to point to the right file via $ODBCINI.
Yes. But here they are using two different mqsiprofile files. So I had to edit .profile file. And also the same userid is used for both TEST and UAT
To reiterate, DO NOT modify the mqsiprofile script supplied with the Broker Runtime. setup the $ODBCINI in the script that uses the mqsiprofile. |
I did modify the .mqsiprofile. only .profile. |
Presumably you've missed out the key word "not" there, as in "I did not" |
|
| Back to top |
|
|
|
|
