| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem: Create Broker WBIMB V6 using MQ V6 |
View previous topic :: View next topic |
| Author |
Message
|
| relheop |
 Posted: Fri Mar 16, 2007 8:58 am Post subject: Problem: Create Broker WBIMB V6 using MQ V6 |
 |
|
Apprentice
Joined: 30 Jan 2003
Posts: 40
|
Hi all,
I installed DB2 server on solaris 10.
I have create a database, but when i tried to connect to DB2 SERVER( server edition DB2 8.1 FixPak 10) i am getting the following error
db2 connect to brokerdatabase user brokeruser
SQL30082N Attempt to establish connection failed with security reason
"26" ("SERVER SECURITY PLUGIN ERROR"). SQLSTATE=08001.
db2 connect to brokerdatabase woks ok. I can connect.
Result: I can't create broker using mqsicreatebroker command.
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.
BIP2322E: Database error: SQL State ''08001''; Native Error Code '-30082'; Error Text ''[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason "26" ("SERVER SECURITY PLUGIN ERROR"). SQLSTATE=08001 ''.
The error has the following diagnostic information: SQL State ''08001'' SQL Native Error Code '-30082' SQL Error Text ''[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason "26" ("SERVER SECURITY PLUGIN ERROR"). SQLSTATE=08001 ''
This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error.
BIP8040E: Unable to connect to the database.
The database cannot be accessed with the userid and password that were specified when the broker was created.
Check that the database is running, that an ODBC connection has been created and that the userid and password pair specified for ODBC connect on the mqsicreate command are capable of being used to connect to the database using an ODBC connection. Also ensure that the database has a adequate number of database connections available for use.
Any suggestions would be appreciated
Thanks in advance
 |
|
| Back to top |
|
 |
| pcelari |
| Posted: Fri Mar 16, 2007 11:19 am Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
did you grand the necessary users access rights? here's from my notes. I setup mine on Solaris 9.
12. Grand DB2 database access to user wbibadm and mqm with the following steps:
1. Login as instance owner or as a user with sysadm right,
db2 connect to MQSIBKDB
2. Run the following command:
db2 grant connect, createtab, bindadd, create_external_routine on database to wbibadm
3. Note, since user mqm is both a user and a group name, an “user” switch is needed to grand the same right:
db2 grant connect, createtab, bindadd, create_external_routine on database to user mqm
BTW, you need to upgrade v8.1 to version 9, which is 8.2 sp whatever.
good luck.
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
|
| relheop |
| Posted: Fri Mar 16, 2007 11:46 am Post subject: |
|
|
Apprentice
Joined: 30 Jan 2003
Posts: 40
|
I did it.
It looks like a problem with the db2 system configuration. My first step was to connect to db2 using the broker or the instance owner ID. Command: db2 connect to database user instance/broker user. -> not succesful
I can connect to db2 using command: db2 connect to database
using su - broker user or instance owner ID before.
It's a new db2 installation. We have one installation on Solaris 8 running without problems. Now we have a new box with Solaris 10. |
|
| Back to top |
|
|
| relheop |
| Posted: Sun Mar 25, 2007 12:40 pm Post subject: |
|
|
Apprentice
Joined: 30 Jan 2003
Posts: 40
|
Cause
The Solaris 10 provide enhanced encryption method "bsdmd5" for passwords which is an encrypted password much longer than the standard "UNIX" encryption method. DB2 need to be at DB2 8.1 FP14 or higher to support bsdmd5 encryption.
Solution
Disabled the use of the bsdmd5 encryption or install DB2 8.1 FP14 or higher (APAR IY88926) |
|
| 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
|
|
|
|
