| Author | 
		  Message
		 | 
		
		  | sasad | 
		  
		    
			  
				 Posted: Wed Apr 30, 2014 8:52 am    Post subject: [Oracle]ORA-01017: invalid username/password; logon denied | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 30 Apr 2014 Posts: 67
  
  | 
		  
		    
			  
				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, 
 
 
I tested it by executing following command, it completed successfully.
 
 
mqsicvp NODENAME -n DSN
 
 
used this DSN name in my compute node's property Data source. but when I am trying execute my message flow, I am getting following exception. 
 
 
(0x01000000:Name     ):DatabaseException = (
 
        (0x03000000:NameValue):File     = 'F:\build\slot1\S900_P\src\DataFlowEngine\MessageServices\ImbOdbc.cpp' (CHARACTER)
 
        (0x03000000:NameValue):Line     = 2438 (INTEGER)
 
        (0x03000000:NameValue):Function = 'ImbOdbcConnection::checkRcInner' (CHARACTER)
 
        (0x03000000:NameValue):Type     = '' (CHARACTER)
 
        (0x03000000:NameValue):Name     = '' (CHARACTER)
 
        (0x03000000:NameValue):Label    = '' (CHARACTER)
 
        (0x03000000:NameValue):Catalog  = 'BIPmsgs' (CHARACTER)
 
        (0x03000000:NameValue):Severity = 3 (INTEGER)
 
        (0x03000000:NameValue):Number   = 2322 (INTEGER)
 
        (0x03000000:NameValue):Text     = 'Child SQL exception' (CHARACTER)
 
        (0x01000000:Name     ):Insert   = (
 
          (0x03000000:NameValue):Type = 5 (INTEGER)
 
          (0x03000000:NameValue):Text = '28000' (CHARACTER)
 
        )
 
        (0x01000000:Name     ):Insert   = (
 
          (0x03000000:NameValue):Type = 2 (INTEGER)
 
          (0x03000000:NameValue):Text = '1017' (CHARACTER)
 
        )
 
        (0x01000000:Name     ):Insert   = (
 
          (0x03000000:NameValue):Type = 5 (INTEGER)
 
          (0x03000000:NameValue):Text = '[IBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-01017: invalid username/password; logon denied' (CHARACTER)
 
        )
 
      ) | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Simbu | 
		  
		    
			  
				 Posted: Wed Apr 30, 2014 11:08 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 17 Jun 2011 Posts: 289 Location: Tamil Nadu, India 
  | 
		  
		    
			  
				| Hi, have you tried reloading the execution group after mqsisetdbparms? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | sandman147 | 
		  
		    
			  
				 Posted: Thu May 01, 2014 9:04 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 01 Sep 2013 Posts: 42
  
  | 
		  
		    
			  
				| Bounce the Broker after issuing the mqsisetdbparms; mqsistop BROKER followed by mqsistart BROKER | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | sasad | 
		  
		    
			  
				 Posted: Mon May 05, 2014 3:20 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 30 Apr 2014 Posts: 67
  
  | 
		  
		    
			  
				| I did this, bounce the broker but still getting same error. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | fjb_saper | 
		  
		    
			  
				 Posted: Mon May 05, 2014 4:11 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 18 Nov 2003 Posts: 20768 Location: LI,NY 
  | 
		  
		    
			  
				If the password contains some strange characters, you may well have to specify it between double quotes i.e. -p "w&$!@(#F" 
 
Is your username / password of adequate length ? What are the limitation on the DB?   _________________ MQ & Broker admin | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | sasad | 
		  
		    
			  
				 Posted: Fri May 09, 2014 5:34 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 30 Apr 2014 Posts: 67
  
  | 
		  
		    
			  
				Hi all,
 
 
Thanks for your replies, But I was able to resolve this issue by selecting "Enable SQLDescribeParam" checkbox for my DSN in ODBC.
 
 
   | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |