| Author |
Message
|
| jainvik7 |
 Posted: Wed May 21, 2008 1:18 am Post subject: broker commands not responding |
 |
|
Apprentice
Joined: 19 Feb 2006
Posts: 38
|
Hi all,
the broker commands on one of our servers is not responding.
mqsilist
mqsistop etc etc all get into hung state .... did anyone face a similar issue? Any pointers how to proceed with this.
Thanks |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed May 21, 2008 1:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Version of WMB? Level of maintenance applied? Platform you're running on?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jainvik7 |
| Posted: Wed May 21, 2008 1:48 am Post subject: |
|
|
Apprentice
Joined: 19 Feb 2006
Posts: 38
|
Version V6 a
and we just realised that the broker is not able to connect to the database.
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 '12170'; Error Text ''[DataDirect][ODBC Oracle driver][Oracle]ORA-12170: TNS:Connect timeout occurred ''.
The error has the following diagnostic information: SQL State ''08001'' SQL Native Error Code '12170' SQL Error Text ''[DataDirect][ODBC Oracle driver][Oracle]ORA-12170: TNS:Connect timeout occurred ''
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 |
|
| Back to top |
|
|
| AkankshA |
| Posted: Wed May 21, 2008 1:51 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| Quote: |
| 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 |
also chk that the remoter server is available in case the DB is not local
_________________
Cheers |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 21, 2008 1:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jainvik7 wrote: |
| Version V6 a |
IBM are using letters for maintenance now? I turn my back for a few moments...... 
You still don't mention which platform.
| jainvik7 wrote: |
we just realised that the broker is not able to connect to the database.
...
BIP2322E: Database error: SQL State ''08001''; Native Error Code '12170'; Error Text ''[DataDirect][ODBC Oracle driver][Oracle]ORA-12170: TNS:Connect timeout occurred ''.
The error has the following diagnostic information: SQL State ''08001'' SQL Native Error Code '12170' SQL Error Text ''[DataDirect][ODBC Oracle driver][Oracle]ORA-12170: TNS:Connect timeout occurred ''
|
That does seem fairly definitive, and I'm sure your DBAs will be delighted to look into it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
