| Author | 
		  Message
		 | 
		
		  | gisly | 
		  
		    
			  
				 Posted: Thu May 10, 2012 6:05 am    Post subject: WMB7 Windows7 Oracle Connection fails | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 10 May 2012 Posts: 29
  
  | 
		  
		    
			  
				Hi everybody! I have looked for this error everywhere but I think I haven't found anything relative to my case.
 
 
I have got a 32bit-Message Broker 7.0 installed on Windows7 (64 bit). I am trying to connect to an Oracle database using an ODBC (I have already performed mqsisetdbparms for the broker). However, I get the following error:[IBM][ODBC Oracle driver][Oracle]ORA-12154: TNS:could not resolve the connect identifier specified. 
 
"Test connection" in the Windows ODBC manager works. The name I use is mentioned in the tnsnames.ora file.
 
Has anyone come across a similar issue? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Thu May 10, 2012 6:08 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				Are you using the correct Windows ODBC administration tool to define the ODBC; i.e. defining a 32 bit ODBC for your 32 bit WMB to use rather than a 64 bit ODBC which it can't?
 
 
http://support.microsoft.com/kb/942976 _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | gisly | 
		  
		    
			  
				 Posted: Fri May 11, 2012 1:26 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 10 May 2012 Posts: 29
  
  | 
		  
		    
			  
				| Yes, I am using the 32-bit ODBC administration tool. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqjeff | 
		  
		    
			  
				 Posted: Fri May 11, 2012 2:06 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Master
 
 Joined: 25 Jun 2008 Posts: 17447
  
  | 
		  
		    
			  
				did you set ORAHOME in a global manner or ensure that it is visible to the Broker?
 
 
does it work from mqsicvp? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | gisly | 
		  
		    
			  
				 Posted: Fri May 11, 2012 2:31 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 10 May 2012 Posts: 29
  
  | 
		  
		    
			  
				I have set ORACLE_HOME, which is visible to the broker.
 
 
In my version (7.0.0.0) mqsicvp can have only one parameter (the name of the broker), so I can't test the connection with it. Should I consider an update? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqjeff | 
		  
		    
			  
				 Posted: Fri May 11, 2012 2:46 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Master
 
 Joined: 25 Jun 2008 Posts: 17447
  
  | 
		  
		    
			  
				| Yes.  There's no reason you shouldn't at least be at 7.0.0.3. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | gisly | 
		  
		    
			  
				 Posted: Fri May 11, 2012 5:04 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 10 May 2012 Posts: 29
  
  | 
		  
		    
			  
				I've updated MB to 7.0.0.3, and here's the output of mqsicvp:
 
BIP8873I: Starting the component verification for component 'LenaBroker'.
 
BIP8876I: Starting the environment verification for component 'LenaBroker'.
 
BIP8894I: Verification passed for 'Registry'.
 
BIP8894I: Verification passed for 'MQSI_REGISTRY'.
 
BIP8894I: Verification passed for 'Java Version'.
 
BIP8894I: Verification passed for 'MQSI_FILEPATH'.
 
BIP8878I: The environment verification for component 'LenaBroker' has finished s
 
uccessfully.
 
BIP8882I: Starting the WebSphere MQ verification for component 'LenaBroker'.
 
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.ADMIN.QUEUE' on queue man
 
ager 'LenaQM'.
 
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.EXECUTIONGROUP.QUEUE' on
 
queue manager 'LenaQM'.
 
BIP8886I: Verification passed for queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on
 
queue manager 'LenaQM'.
 
BIP8884I: The WebSphere MQ verification for component 'LenaBroker' has finished
 
successfully.
 
BIP8874I: The component verification for 'LenaBroker' has finished successfully.
 
 
BIP8071I: Successful command completion.
 
 
 
Can I assume that it does not check the databases at all? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqjeff | 
		  
		    
			  
				 Posted: Fri May 11, 2012 5:06 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Master
 
 Joined: 25 Jun 2008 Posts: 17447
  
  | 
		  
		    
			  
				| mqsicvp -n will check the datasource | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Fri May 11, 2012 5:10 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| mqjeff wrote: | 
   
  
	| mqsicvp -n will check the datasource | 
   
 
 
 
As will mqsicvp <Broker Name> -n
 
 
(to be pedantically clear) _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | gisly | 
		  
		    
			  
				 Posted: Fri May 11, 2012 5:15 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 10 May 2012 Posts: 29
  
  | 
		  
		    
			  
				| It says the command mqsicvp has a wrong syntax. Does it work for MB 7.0.0.3? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqjeff | 
		  
		    
			  
				 Posted: Fri May 11, 2012 5:16 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Master
 
 Joined: 25 Jun 2008 Posts: 17447
  
  | 
		  
		    
			  
				okay, so to be exact, but you should have seen this yourself from mqsicvp /?, the syntax is 
   
	| Code: | 
   
  
	| mqsicvp <broker name> -n <datasource name> | 
   
 
 
 
So for example 
   
	| Code: | 
   
  
	| mqsicvp BKR70 -n MYDSN | 
   
 
 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Fri May 11, 2012 5:33 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| mqjeff wrote: | 
   
  
	okay, so to be exact, but you should have seen this yourself from mqsicvp /?, the syntax is 
   
	| Code: | 
   
  
	| mqsicvp <broker name> -n <datasource name> | 
   
 
 | 
   
 
 
 
 
 
 
Or 
 
 
   
	| Code: | 
   
  
	| mqsicvp -n <datasource name> -u <user> -p <password> | 
   
 
 
 
If all else fails, you could resort to reading the description of the command in the documentation here    _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | gisly | 
		  
		    
			  
				 Posted: Fri May 11, 2012 5:46 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 10 May 2012 Posts: 29
  
  | 
		  
		    
			  
				Yes, I've read it, but that's what it says:
 
 
C:\Program Files (x86)\IBM\MQSI\7.0>mqsicvp LenaBroker -n BRK01 -u rm -p passwor
 
d
 
BIP8872W: Verifies a broker.
 
Syntax:
 
 mqsicvp brokerName
 
 
 
 Command Options:
 
 'brokerName' name of the broker
 
 
BIP8001E: Unknown flag 'n' selected.
 
When using this command interface the user should only select the supported flag
 
s.
 
Correct and reissue the command. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Fri May 11, 2012 5:54 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| gisly wrote: | 
   
  
	| Yes, I've read it,  | 
   
 
 
 
Not very carefully.
 
 
   
	| gisly wrote: | 
   
  
	C:\Program Files (x86)\IBM\MQSI\7.0>mqsicvp LenaBroker -n BRK01 -u rm -p passwor
 
 | 
   
 
 
 
You either specify the -n flag with the -u & -p or you quote the broker name and the -n flag.
 
 
You can't specify both for reasons which are obvious after a moment's thought. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | gisly | 
		  
		    
			  
				 Posted: Fri May 11, 2012 6:17 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 10 May 2012 Posts: 29
  
  | 
		  
		    
			  
				It doesn't work still
 
 
C:\Program Files (x86)\IBM\MQSI\7.0>mqsicvp LenaBroker -n BRK01
 
BIP8872W: Verifies a broker.
 
Syntax:
 
 mqsicvp brokerName
 
 
 
 Command Options:
 
 'brokerName' name of the broker
 
 
BIP8001E: Unknown flag 'n' selected.
 
When using this command interface the user should only select the supported flag
 
s.
 
Correct and reissue the command. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |