| Author |
Message
|
| nelson |
 Posted: Tue Oct 25, 2016 10:02 am Post subject: ODBC return code '-2' |
 |
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
Hi All,
Have any of you seen this error before?
| Code: |
Oct 20 10:14:32 server user:err|error IIB[8912912]: IBM Integration Bus v9002 (broker.EG) [Thread 27244] (Msg 1/2) BIP2628E: Exception condition detected on input node 'flow.inputqueue'.
Oct 20 10:14:32 server user:err|error IIB[8912912]: IBM Integration Bus v9002 (broker.EG) [Thread 27244] (Msg 2/2) BIP2321E: Database error: ODBC return code '-2' using ODBC driver manager '/opt/ibm/IE02/lib/libodbcinterface.so'. |
It does not say much. 
Thanks in advance for your feedback. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Oct 25, 2016 10:24 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
It appears that you got an error from SQL that was transformed into an ODBC error. If you have specific errorhandling in place, I believe there is an ODBC function call that would allow you to retrieve the SQL information (error codes etc)...
Pending that can you do a user trace and would it be showing more? Or an ODBC trace?
Anyways it would be worth checking that the ODBC configuration for the DSN is valid and that the broker can indeed talk to the DB in question. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 25, 2016 11:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| Anyways it would be worth checking that the ODBC configuration for the DSN is valid and that the broker can indeed talk to the DB in question. |
mqsicvp is your friend.
An ODBC trace is your other friend.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| nelson |
| Posted: Tue Oct 25, 2016 11:56 am Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| fjb_saper wrote: |
It appears that you got an error from SQL that was transformed into an ODBC error. If you have specific errorhandling in place, I believe there is an ODBC function call that would allow you to retrieve the SQL information (error codes etc)...
Pending that can you do a user trace and would it be showing more? Or an ODBC trace?
Anyways it would be worth checking that the ODBC configuration for the DSN is valid and that the broker can indeed talk to the DB in question. |
Thanks fjb_saper. Well... the fact is that it was a particular incident in that moment. If I test the flow right now it works fine.  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Oct 25, 2016 12:32 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| nelson wrote: |
Thanks fjb_saper. Well... the fact is that it was a particular incident in that moment. If I test the flow right now it works fine. |
So what was different in the environment when the incident happened?
Table locked? Table being edited by someone else? DB down?
Are you able to realiably reproduce the condition?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
