| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2322E: Database error,Security processing failed with rea |
« View previous topic :: View next topic » |
| Author |
Message
|
| the_one |
 Posted: Fri May 14, 2010 6:17 pm Post subject: BIP2322E: Database error,Security processing failed with rea |
 |
|
Novice
Joined: 16 Dec 2008
Posts: 22
Location: PHX, AZ
|
Hi Gurus,
I m trying to create a broker (MB6.0.0.8, AIX)but for some reasons I m getting this error.
| Code: |
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 Security processing failed with reason "15" ("PROCESSING FAILURE"). SQLSTATE=08001 ''.
The error has the following diagnostic information: SQL State ''08001'' SQL Native Error Code '-30082' SQL Error Text ''[IBM][CLI Driver] SQL30082N Security processing failed with reason "15" ("PROCESSING FAILURE"). 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.
hamqsicreatebroker: Error from mqsicreatebroker command |
I tried to search this form for similar issues, but couldn;t find one.
I have created an empty broker DB2 database and tried to connect it with the DB2 user ID and it connects fine. So userName/Password are correct.
Is it anywhere related to DB2 bind thing?
Can you please suggest what I m missing.
_________________
See the marbles of the world, but never forget the drops of oil on the spoon. |
|
| Back to top |
|
 |
| the_one |
| Posted: Sun May 16, 2010 10:29 pm Post subject: |
|
|
Novice
Joined: 16 Dec 2008
Posts: 22
Location: PHX, AZ
|
I gave it a few tries, then I found that for some reasons, the directory ownerships for db2 instance were messed up.
I deleted the db2 instance (db2idrop) and recreated the databases.
This fixed my issue. 
_________________
See the marbles of the world, but never forget the drops of oil on the spoon. |
|
| 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
|
|
|
|
