| Author |
Message
|
| swann |
 Posted: Tue Jan 03, 2012 8:28 am Post subject: ODBC error |
 |
|
Acolyte
Joined: 21 Jun 2011
Posts: 50
|
Hi Friends ,
I am using MB 7 and i tried to connect to oracle database using odbc connections.I have finished the required configuration on odbc.ini files.But i am coming up with these errors..
BIP2393E: Database error: ODBC return code '-1' from data source ''BOBJE'' using ODBC driver manager ''libbipodbc.a(odbc.so)''.
The broker received an error when processing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database about this error.
Use the following messages to determine the cause of the error. Typical problems are an incorrect data source, or table names. Correct either the database or the broker configuration.
BIP2322E: Database error: SQL State ''08001''; Native Error Code '0'; Error Text ''[IBM][ODBC Oracle Wire Protocol driver]Connection refused. Verify Host Name and Port Number.''.
The error has the following diagnostic information: SQL State ''08001'' SQL Native Error Code '0' SQL Error Text ''[IBM][ODBC Oracle Wire Protocol driver]Connection refused. Verify Host Name and Port Number.''
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.
BIP2322E: Database error: SQL State ''08001''; Native Error Code '-1'; Error Text ''[IBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-12203: unable to connect to destination''.
The error has the following diagnostic information: SQL State ''08001'' SQL Native Error Code '-1' SQL Error Text ''[IBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-12203: unable to connect to destination''
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. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Jan 03, 2012 8:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| swann wrote: |
| Connection refused. Verify Host Name and Port Number |
|
|
| Back to top |
|
|
| swann |
| Posted: Tue Jan 03, 2012 8:46 am Post subject: |
|
|
Acolyte
Joined: 21 Jun 2011
Posts: 50
|
| The port number and hostname are correct,the same odbc connection was working in my dev stage and i tried to connect it in qa with different DSN but this time it wasnt working.. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jan 03, 2012 8:51 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 03, 2012 9:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| swann wrote: |
| The port number and hostname are correct,the same odbc connection was working in my dev stage and i tried to connect it in qa with different DSN but this time it wasnt working.. |
"Connection refused" is often a firewall. The port number and hostname may be correct, but perhaps they can't be reached over the network from your QA environment in the way they can be from your dev environment.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| swann |
| Posted: Tue Jan 03, 2012 9:04 am Post subject: |
|
|
Acolyte
Joined: 21 Jun 2011
Posts: 50
|
| Yes i issued the mqsicvp command and facing these error messages in QA. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jan 03, 2012 9:09 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| swann wrote: |
| Yes i issued the mqsicvp command and facing these error messages in QA. |
Therefore, this is not a WMB problem. What help are you expecting from WMB resources? Check with your SysAdmin.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| swann |
| Posted: Tue Jan 03, 2012 10:45 am Post subject: |
|
|
Acolyte
Joined: 21 Jun 2011
Posts: 50
|
| How could i check if it is a firewall issue,Is there any command to test the connection. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jan 03, 2012 10:59 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
PING command works really well. Come on, how long have you worked in I.T. ? Firewall issues are very basic.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 03, 2012 11:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| swann wrote: |
| How could i check if it is a firewall issue,Is there any command to test the connection. |
Telnet to the specific address and port you're using in the ODBC. If that won't connect it's a network issue.
Note that just pinging or doing a telnet is insufficient because that will use the default port for those commands, not the one for the database. Many firewalls are configured on a port by port basis so a telnet to the host may succeed but a telnet to the database port on the host will fail.
I'm amazed you've worked with WMQ for any length of time and not hit a firewall issue. Most channel problems are caused by this and you always have to prove to the network people it doesn't work for anything before they stop claiming it's an issue with the MCA!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 03, 2012 12:48 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
| I'm amazed you've worked with WMQ for any length of time and not hit a firewall issue. Most channel problems are caused by this and you always have to prove to the network people it doesn't work for anything before they stop claiming it's an issue with the MCA! |
Wow! I'm amazed that your network people even know what an MCA is...
They just tell me it must be MQ... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 03, 2012 12:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
Wow! I'm amazed that your network people even know what an MCA is...
They just tell me it must be MQ... |
It's surprising how quickly they pick it up after you've screamed "The MCA comes with the software! The MCA is not changed! I didn't write the MCA! It's the same MCA we were using yesterday" (or similar) a few times while whirling a trout in an informative and satisfying manner on various body parts.
It's equally surprising that having learnt the name of the component and endured a rabid rant on the resiliance of the WMQ channel software, contrasted with the weakness of the network change control process, you have to go through the whole thing again next time it happens!
I just need a properly sized Trout Of Teaching.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| joebuckeye |
| Posted: Wed Jan 04, 2012 5:32 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 365
Location: Columbus, OH
|
My favorite issue in dealing with firewalls is when you find there is a problem and get the firewall team on the issue.
They 'look into it' and then tell you to 'try again'.
It then works and we ask what they did and the answer is always 'nothing'.
Then we ask 'why did it suddenly start working then?' and the answer is always 'I don't know'. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 04, 2012 5:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| joebuckeye wrote: |
| It then works and we ask what they did and the answer is always 'nothing'. |
The network team never do anything to fix the problem.
The other network gotcha (which I'll mention here for completeness) is the "destination host unreachable" error. Typically caused by the host name not resolving to an IP address because the DNS entry is hosed up but can occur even on an explict IP address if the routing tables have been edited badly enough.
Again never caused by the network team and mysteriously fixes itself shortly after you mention it to them. In extreme cases (and if you get rabid enough after days of fruitless effort) you may find the network team modify their position from:
| Quote: |
| Nothing's changed on the network side |
to
| Quote: |
| Nothing's changed on the network side apart from that change we made the night before your channels stopped working but that couldn't possibly be causing the problem you're seeing |
In these situations send your mind into your happy place, avoid grinding your teeth (unless you've got good dental) and suggest with as much restraint as you have left that they reverse the change just as an experiment. Then take a few moments practicing your surprised face for when your channels come back up.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jan 04, 2012 5:51 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
A traceroute/tracert output also really helps the netwrok team realise that it is their problem especially as there is already a working connection.
Comparing the output can be very illuminating.
'Oh.... It shouldn't go there....'
Is a common reaction by the network team to this sort of problem.
_________________
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 |
|
|
|
|
