| Author | 
		  Message
		 | 
		
		  | amar | 
		  
		    
			  
				 Posted: Tue Aug 06, 2002 11:25 pm    Post subject: mqsicreatbroker-problem | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 27 Jun 2002 Posts: 45
  
  | 
		  
		    
			  
				Hi, 
 
 
Iam using MQSI 2.1 Broker on AIX with Config Mgr 2.1 on NT 
 
 
My installation went succesfully on AIX (MQSI) 
 
 
but when i issued the command mqsicreatebroker I get following error 
 
 
BIP2321E
 
BIP2322E
 
BIP8040E
 
 
When I refered to the Message PDF there also I coulnot find the solution 
 
 
Note: All my Enviroment variable are set correctly 
 
I have Root login 
 
 
 
If any one solved same problem let me know
 
 
amar | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | jhalstead | 
		  
		    
			  
				 Posted: Wed Aug 07, 2002 12:23 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 16 Aug 2001 Posts: 258 Location: London 
  | 
		  
		    
			  
				Could is by that the LANG parameter is not en_US.  This sometime causes similar problems?
 
 
J | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | amar | 
		  
		    
			  
				 Posted: Wed Aug 07, 2002 12:39 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 27 Jun 2002 Posts: 45
  
  | 
		  
		    
			  
				Hi 
 
  I checked that parameter  LANG=en_US.  it is ok..
 
 
While Running mqsicreatebroker command, i am getting error like...
 
 
mqsicreatebroker  <BrokerName> -i db2admin -a password -q <QMGRNAME> -n <DatabaseName>
 
 
MQSeries queue manager running.
 
The setmqaut command completed successfully.
 
The setmqaut command completed successfully.
 
The setmqaut command completed successfully.
 
The setmqaut command completed successfully.
 
The setmqaut command completed successfully.
 
The setmqaut command completed successfully.
 
BIP2321E: Database error: ODBC return code '-1'.
 
The message broker encountered an error whilst executing a database operation. T
 
he ODBC return code was '-1'. See the following messages for information obtaine
 
d from the database pertaining to this error.
 
Use the following messages to determine the cause of the error. This is likely t
 
o be such things as incorrect datasource or table names. Then correct either the
 
 database or message broker configuration.
 
BIP2322E: Database error: SQL State 'IM002'; Native Error Code '0'; Error Text '
 
[MERANT][ODBC lib] Data source name not found and no default driver specified'.
 
The error has the following diagnostic information:     SQL State             'I
 
M002'     SQL Native Error Code '0'     SQL Error Text        '[MERANT][ODBC lib
 
] Data source name not found and no default driver specified'
 
This message may be accompanied by other messages describing the effect on the m
 
essage broker itself.  Use the reason identified in this message with the accomp
 
anying messages to determine the cause of the error.
 
 
BIP8040E: Unable to connect to the database.
 
The database cannot be accessed with the userid and password that were specified
 
 when the broker was created.
 
Check that the database is running, that an ODBC connection has been created and
 
 that the userid and password pair specified for ODBC connect on the mqsicreate
 
command are capable of being used to connect to the database using an ODBC conne
 
ction. Also ensure that the database has a adequat
 
 
regards
 
amar | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | jhalstead | 
		  
		    
			  
				 Posted: Wed Aug 07, 2002 4:33 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 16 Aug 2001 Posts: 258 Location: London 
  | 
		  
		    
			  
				Have you set up the /var/mqsi/odbc/.odbc.ini file with a stanza for the datasource you are referencing in the mqsicreate command?
 
 
Out of interest are you using DB2 or Oracle?
 
 
Can you connect to the database from the command line?
 
 
Jamier | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | MaryDegallo | 
		  
		    
			  
				 Posted: Wed Aug 07, 2002 5:06 am    Post subject: mqsicreatbroker - problem | 
				     | 
			   
			 
		   | 
		
		
		   Newbie
 
 Joined: 07 Apr 2002 Posts: 6 Location: EastCoast, USA 
  | 
		  
		    
			  
				Normally this means that the userid/password that you have given in createbroker command donot have access to the database. 
 
 
OR   
 
inadvertently you mahave created the BROKERDB  under a different userId other than db2admin. 
 
 
-Mary | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | jhalstead | 
		  
		    
			  
				 Posted: Wed Oct 16, 2002 8:52 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Master
 
 Joined: 16 Aug 2001 Posts: 258 Location: London 
  | 
		  
		    
			  
				Horse may well have bolted on this one!  However for anyone doing a search this could well be a result of the mqsi_setupdatabase script not being executed - for instance with Oracle this creates a symbolic link to the oracle client library which enables wqsi to interact!
 
 
Jamie | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |