| Author |
Message
|
| pcelari |
 Posted: Sat Feb 07, 2009 7:09 pm Post subject: Need Help! wmbadmin unable to connect to DB on Linux x-86 |
 |
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
Hi,
I installed MQ v7, DB2 9.1 and wmb6.1 on a x-86 Linux machine. and configured WMBBKRDB as documented. But my mqsicreatebroker command:
mqsicreatebroker MYBROKER -i wmbadmin -a passwd -q MYBROKER -n WMBBKRDB -u wmbadmin -p passwd
failed with
SQL State ''08001''; Native Error Code '-30082'; Error Text ''[IBM][CLI Driver] SQL30082N Security processing failed with reason "15"
to check security, I run the command as wmbadmin
db2 connect to WMBBKRDB
successfully. But connect failed if I provide the user name and passwd in the following command:
db2 connect to WMBBKRDB user wmbadmin using "passwd"
SQL30082N Security processing failed with reason "15" ("PROCESSING FAILURE").
SQLSTATE=08001
I couldn't understand, how could it be that I can connect to DB without a specifying userid and password, but fail when I supply them explicitly?
I uninstalled and reinstalled DB2 9.1, plus fixpack 6a, but everything still the same. I also applied the license after installation.
Has anyone ever expierenced such strange behavior? what could I have missed?
thank you for any insight!
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sun Feb 08, 2009 12:07 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
|
| Back to top |
|
|
| pcelari |
| Posted: Sun Feb 08, 2009 8:56 am Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
thank you for pointing that out. But that reason code explanation is also part of the error message.
Yes, I set my .odbc.ini correctly. but "db2 connect to" command doesn't even use ODBCINI, right?
How come the one without specifying id/pswd succeeds, while the same command with id/pswd fails?
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Feb 08, 2009 9:15 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Db2 connect to ....
does not use ODBC as you surmised.
However broker uses ODBC for its connections. This has to be setup properly before broker will work. There are numerous posts in this forum about this very topic.
Back to your db2 connects.
I would hazard at a guess that you are using a command terminal that is looged on as something like 'db2admin'. If so then you get admin access to the db without having to specify a password.
Make sure the user you are trying to use is properly authorised to access the particular database in question. I always test the connectivity this way before trying to create the broker.
_________________
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 |
|
|
| jonesn |
| Posted: Thu Mar 05, 2009 6:33 am Post subject: |
|
|
Apprentice
Joined: 09 Jan 2002
Posts: 47
|
Guys,
Did this question get resolved? I have the same issue when trying to create a 6.1 broker on Linux and do not undestand why the command is failing. I am supplying the correct userid & password when I attempt to connect manually but the command fails. Does DB2 need the username/password to be configured over & above the standard linux security, i.e. /etc/passwd?
Another point to note is that I have previously created brokers using DB2 on AIX without problems & as I am porting the creating steps across to Linux I would not expect this to be an issue.
Thanks
_________________
---
Nick Jones
IBM Certified Solutions Expert (WebSphere MQ Integrator) |
|
| Back to top |
|
|
| pcelari |
| Posted: Thu Mar 05, 2009 2:46 pm Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
No, it's not yet resolved.
I uninstalled the db2 v9.1 and installed v8.2 expecting it to work. But it didn't. Still getting the same error:
SQL30082N Attempt to establish connection failed with security reason "26" ("SERVER SECURITY PLUGIN ERROR"). SQLSTATE=08001
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
|
| jonesn |
| Posted: Thu Mar 05, 2009 3:27 pm Post subject: |
|
|
Apprentice
Joined: 09 Jan 2002
Posts: 47
|
I think this problem is nothing to do with message broker nor ODBC, it is simply how to configure DB2 on Linux (Fedora 9 with all latest patches). These are the steps I followed...
As Root user
Install DB2 9.1 using db2setup creating dbinst as instance owner
Install FixPack 6a using installFixPack
As dbinst user
db2 start database manager
db2 create database mqsibkdb
db2 connect to mqsibkdb
db2 bind ~/sqllib/bnd/@db2cli.lst grant public CLIPKG 5
db2 grant connect, createtab, bindadd, create_external_routine on database to user mqm
Note that no errors or warnings are generated by running these commands so I have no reason to think anything failed.
As dbinst user
db2 connect to mqsibkdb user mqm using <passwd>
SQL30082N Security processing failed with reason "15" ("PROCESSING FAILURE")
Any help gratefully accepted.
Thanks
_________________
---
Nick Jones
IBM Certified Solutions Expert (WebSphere MQ Integrator) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Mar 05, 2009 3:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Just try with grant all.
You might be a few permission shy of the needed set. (I did not see any execute (for stored procs etc...) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jonesn |
| Posted: Fri Mar 06, 2009 6:20 am Post subject: |
|
|
Apprentice
Joined: 09 Jan 2002
Posts: 47
|
Success
I have managed to create the broker after making the following change. Amend /etc/pam.d/system-auth-ac so that the password encryption algorithm is changed to sha256 rather than sha512 which is the default. The password for the user must be reset using the passwd command. This is explained more fully in the following...
http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14223029
Thanks
_________________
---
Nick Jones
IBM Certified Solutions Expert (WebSphere MQ Integrator) |
|
| Back to top |
|
|
| pcelari |
| Posted: Fri Mar 06, 2009 8:31 am Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
SUCCESS!
Thanks a lot for sharing this!
I changed the encription to DES as IBM suggested, and reset all user password.
with this, the mqsicreatebroker command completed successfully.
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
|
|
|
