| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem with mqsilist |
« View previous topic :: View next topic » |
| Author |
Message
|
| pawel_janowski |
 Posted: Thu Dec 18, 2008 3:08 am Post subject: Problem with mqsilist |
 |
|
Apprentice
Joined: 13 Dec 2006
Posts: 38
|
Hi!
When I try to list objects deployed to an execution group on my broker running:
| Code: |
| mqsilist BRK1 -e eg1 |
from user on which Config Manager runs (not the broker user), I obtain the following ODBC error:
| Code: |
BIP2322E: Database error: SQL State ''82''; Native Error Code '0'; Error Text ''523 80''.
The error has the following diagnostic information: SQL State ''82'' SQL Native Error Code '0' SQL Error Text ''523 80''
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.
|
Notes:
1)
works fine and lists my broker and config manager
2) the user is a member of mqm and mqbrkrs groups
Any ideas?
Regards,
Pawel
_________________
Pawel Janowski |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Dec 18, 2008 3:57 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
The vanilla 'mqsilst' command just reads entries from the Windows Registry or the registry directory on *nix systems and does not go anywhere near the Broker database.
When you add the -e then you are asking it to list the flows deployed to a particular EG. This (AFAIK) still requires a DB lookup hence the error message you are seeing.
Can you access the broker database using SQL (you didn't say what DB or OS you are using btw) but from a quick search on this forum for "523 80", I will hazzard a guess that it is Oracle.
Can you access the DB using SQLPLUS ?
Have you setup BOTH the DB profile (eg ORACLE_HOME etc) and the broker profile on the account you are using to execute the mqsilist command?
_________________
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 |
|
|
| mqmatt |
| Posted: Thu Dec 18, 2008 5:05 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Correct - mqsilist -e requires access to the broker's system database while the basic mqsilist does not.
The problem is probably just that the Config Manager userid does not have permissions to access the broker's system database, while the broker userid does. |
|
| Back to top |
|
|
| pawel_janowski |
| Posted: Thu Dec 18, 2008 5:05 am Post subject: |
|
|
Apprentice
Joined: 13 Dec 2006
Posts: 38
|
Hi!
I should supply more details - I've got DB2 8.2 as a broker DB and I can access (connect) it from the Config Manager user, but the user has no rights to select data from BROKER% tables.
Regards,
Pawel
_________________
Pawel Janowski |
|
| 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
|
|
|
|
