| Author |
Message
|
| Vitor |
 Posted: Tue Nov 22, 2011 8:08 am Post subject: Invalid logon to an Oracle ODBC |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
OS: Solaris
WMB: 7.0.0.3
Oracle: 11g
A newly configured box is being tested with a specially written test flow which works fine on Windows.
On Solaris against the same database (but clearly not the same ODBC configuration!) the flow's blowing up with a SQL code 1017 "invalid log on". I've done a mqsicvp <broker name> -n <ODBC name> and that works, the ODBC name in the flow's user trace is the same one I'm using in the ODBC.
Looking at the ESQL (data source is in a Compute node) there's nothing obviously hinky. Is there somewhere else where the credentials could have been specified to override the ones I used on mqsisetdbparms? Do I need to do something else as well as mqsisetdbparms??? Are there credentials hidden in the code, bar file property, beer mat, anywhere? Is there another check I can perform? The ODBC trace was worthless in that it shows the user id I expoect and "*******" for a password, then a SQL 1017 coming back.
I sort of knew that from the broker error. 
Suggestions welcomed, especially anything blindingly obvious I'm overlooking.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Nov 22, 2011 8:11 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
What context is the user id in at the Oracle box ? ie. is there a domain assumed at the Oracle box for Windows conx but not Solaris conx ?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Nov 22, 2011 8:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| What context is the user id in at the Oracle box ? ie. is there a domain assumed at the Oracle box for Windows conx but not Solaris conx ? |
My understanding is that the user in question is an Oracle one, but I'll increase my understanding.
On the assumption there's an assumed domain I'm not supplying why is the mqsicvp acting like the data source works? More importantly, how can I get whatever the mqsicvp command is using to connect in the way of credentials into the flow?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 22, 2011 8:19 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Try adding -u to the mqsicvp, and then -u and -p. See if you can replicate the failure this way. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 22, 2011 8:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| on the assumption there's an assumed domain I'm not supplying why is the mqsicvp acting like the data source works? More importantly, how can I get whatever the mqsicvp command is using to connect in the way of credentials into the flow? |
mqsicvp may be using the Broker service user when you issue the -n. You only issued the ODBC trace when trying from the Broker runtime, not during the mqsicvp right?
Try ODBC tracing the successful mqsicvp and as well try utility tracing mqsicvp. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Nov 22, 2011 8:33 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| mqsicvp may be using the Broker service user when you issue the -n. You only issued the ODBC trace when trying from the Broker runtime, not during the mqsicvp right? |
Right, but the mqsicvp result quotes the correct id not the broker's service id. It could be bluffing & I'll take another trace.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
