| Author |
Message
|
| trycatch |
 Posted: Thu Dec 03, 2009 10:52 pm Post subject: [Oracle]ORA-01017: invalid username/password; logon denied |
 |
|
Newbie
Joined: 03 Dec 2009
Posts: 3
|
Hi Everyone,
I use Compute node to Fetch Data from ORACLE db :
I have created ODBC Connection , while creating connection I have provided TNS service Name,test connection is successful and Use the mqsisetdbparms command to associates a specific user ID and password with DSN resources: mqsisetdbparms BROKER -n DSNNAME -u USER -p PWD,
but when I debug message flow,the compute node throws an error,
Need help ... Please..
Error:
DatabaseException
File:CHARACTER:F:\build\S000_P\src\DataFlowEngine\ImbOdbc.cpp
Line:INTEGER:447
Function:CHARACTER:ImbOdbcHandle::checkRcInner
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2322
Text:CHARACTER:Child SQL exception
Insert
Type:INTEGER:5
Text:CHARACTER:28000
Insert
Type:INTEGER:2
Text:CHARACTER:1017
Insert
Type:INTEGER:5
Text:CHARACTER:[IBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-01017: invalid username/password; logon denied |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Thu Dec 03, 2009 11:23 pm Post subject: Re: [Oracle]ORA-01017: invalid username/password; logon deni |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| trycatch wrote: |
but when I debug message flow,the compute node throws an error,
|
Is it happening only when you debug the flow?
What version and OS that you are running this flow?
you can try use SQLPLUS and see if it is connecting successfully
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| trycatch |
| Posted: Fri Dec 04, 2009 12:21 am Post subject: |
|
|
Newbie
Joined: 03 Dec 2009
Posts: 3
|
Is it happening only when you debug the flow? when the borker is running,I can't see any result generated,so I debug it...
What version and OS that you are running this flow? WMB7.0, windows server 2003
you can try use SQLPLUS and see if it is connecting successfully：success
3Q. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Fri Dec 04, 2009 12:43 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
would you mind to get the trace - User Trace preferred.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| AkankshA |
| Posted: Fri Dec 04, 2009 4:05 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
you can first try mqsisetrdbparms with -d to remove the DSN associated info
and then again register the user n pswd
this may help
_________________
Cheers |
|
| Back to top |
|
|
| student |
| Posted: Fri Dec 04, 2009 6:40 am Post subject: |
|
|
Apprentice
Joined: 17 Mar 2009
Posts: 31
Location: UK
|
I had faced similar issues.
You can also look for error sqlnet.error log file. Some time user id get lockeds in oracle or you would get more details if there is any issues with oracle.
let us know if you find any error there. |
|
| Back to top |
|
|
| trycatch |
| Posted: Sun Dec 06, 2009 7:27 pm Post subject: |
|
|
Newbie
Joined: 03 Dec 2009
Posts: 3
|
Thank your help! I deleted all the settings with the Oracle database and then reconfigured,It running well.I don't know why...  |
|
| Back to top |
|
|
| angka |
| Posted: Wed Dec 23, 2009 7:37 pm Post subject: |
|
|
Chevalier
Joined: 20 Sep 2005
Posts: 406
|
Hi,
I got the same error also. So for the DSN what did you set??? Encrypt? so must the user id and password for the broker be same as the one for the database?? for e.g. both using mqsi and pw 12345? thanks |
|
| Back to top |
|
|
| dwilches |
| Posted: Wed Jan 12, 2011 7:56 am Post subject: |
|
|
Novice
Joined: 12 Jan 2011
Posts: 19
|
| trycatch wrote: |
| Thank your help! I deleted all the settings with the Oracle database and then reconfigured,It running well.I don't know why... |
I did the same and now it's working. But I'm not sure whether it was this or the restarting of the broker. |
|
| Back to top |
|
|
| Muhammad Haider |
| Posted: Mon Mar 14, 2011 11:21 pm Post subject: |
|
|
Apprentice
Joined: 14 Mar 2011
Posts: 43
|
I deleted all previously created identifiers and re-created using mqsisetdbparms command and it worked
Delete command:
mqsisetdbparms BROKERNAME -n IDENTIFIERNAME -d
Thanks! |
|
| Back to top |
|
|
| pratuluv |
| Posted: Wed Dec 14, 2011 6:09 am Post subject: Error connecting to DB from MB |
|
|
Acolyte
Joined: 25 May 2011
Posts: 53
|
I am trying to access ORacle Database from Message Broker. I have executed the below command
mqsisetdbparms MBBRK0C -n dsn::<dsn_name> -u <username> -p <password>
The connection is getting established but when I restart the broker and pass a message, I have the below database error. I have tried the below suggestions of deleting previously created identifiers. But it doesnt work. Also, I have a doubt, my WMB is installed on some other username. Is there any basic mandatory groups that either of the users should be part of? Please help
We are getting the following error Dec 13 12:20:46 hpbc3blade13 WebSphere Broker v7003[3283]: (MBBRK0C.FCV_CustFXTrade_D001)[7]BIP2322E: Database error: SQL State '28000'; Native Error Code '1017'; Error Text '[IBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-01017: invalid username/password; logon denied'. : MBBRK0C.1283360f-3401-0000-0080-f18a557b6d2c: /build/S700_P/src/DataFlowEngine/ImbOdbc.cpp: 518: ImbOdbcHandle::checkRcInner: : |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 14, 2011 6:47 am Post subject: Re: Error connecting to DB from MB |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pratuluv wrote: |
| Is there any basic mandatory groups that either of the users should be part of? |
Clearly the group membership / permissions of the id quoted in the mqsisetdbparms should allow access to the database but that's the only id and permission applicable here.
Does the password contain any special characters or anything the OS shell could be interpreting? Try the command again but omit the -p parameter and type the password manually. Remember you can test the ODBC with mqsicvp rather than a test message.
And remember to stop / start after the mqsisetdbparms.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Dec 14, 2011 7:06 am Post subject: Re: Error connecting to DB from MB |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| pratuluv wrote: |
I am trying to access ORacle Database from Message Broker. I have executed the below command
mqsisetdbparms MBBRK0C -n dsn::<dsn_name> -u <username> -p <password>
|
You don't need the 'dsn::' bit in front of the name. you can use (everywhere) just the name of the DSN. This can be anything. for example 'myuserdsn'.
That aside, did you then use the mqsicvp utility to test the access to the DSN?
There are two types of syntax to use.
mqsicvp -n <dsn> -u <user> -p <pass>
mqsicvp <broker> -n <dsn>
These are invaluable to finding this sort of problem.
Naturally, this is always assuming that
you did use SQL*Plus and actually login to the target DB first ?
The problem could be as simple as the oracle account being locked.
using SQL*Plus will tell you if that is the case.
all of this has been covered many times in this forum.
_________________
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 |
|
|
| pratuluv |
| Posted: Wed Dec 14, 2011 7:09 am Post subject: Re: Error connecting to DB from MB |
|
|
Acolyte
Joined: 25 May 2011
Posts: 53
|
| smdavies99 wrote: |
| pratuluv wrote: |
I am trying to access ORacle Database from Message Broker. I have executed the below command
mqsisetdbparms MBBRK0C -n dsn::<dsn_name> -u <username> -p <password>
|
You don't need the 'dsn::' bit in front of the name. you can use (everywhere) just the name of the DSN. This can be anything. for example 'myuserdsn'.
That aside, did you then use the mqsicvp utility to test the access to the DSN?
There are two types of syntax to use.
mqsicvp -n <dsn> -u <user> -p <pass>
mqsicvp <broker> -n <dsn>
These are invaluable to finding this sort of problem.
Naturally, this is always assuming that
you did use SQL*Plus and actually login to the target DB first ?
The problem could be as simple as the oracle account being locked.
using SQL*Plus will tell you if that is the case.
all of this has been covered many times in this forum. |
Thanks a lot. We just did that and it is resolved.  |
|
| Back to top |
|
|
|
|
