| Author | 
		  Message
		 | 
		
		  | girish_kulkarni | 
		  
		    
			  
				 Posted: Tue Apr 03, 2012 9:38 am    Post subject: Not able to start queue manager after server reboot | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 08 Oct 2010 Posts: 32
  
  | 
		  
		    
			  
				Hi All,
 
 
 
 
We are using horizantal red hat linux cluster active-active cluster. Same queue manger is created in both the servers.
 
 
I am facing below mq error while starting the queue manager after server reboot on both the servers.
 
 
AMQ6119: An internal WebSphere MQ error has occurred ('43 - Identifier removed'
 
from semop.)
 
 
After doing research, I run below commands to release the semophorores.
 
 
amqiclen -v -x -m MB7QMGR
 
 
amqiclen -x -m MB7QMGR
 
 
But still I am facing problem. Please advice as it is very urgent for us.
 
 
 
Thanks in advance. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqjeff | 
		  
		    
			  
				 Posted: Tue Apr 03, 2012 9:41 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Master
 
 Joined: 25 Jun 2008 Posts: 17447
  
  | 
		  
		    
			  
				What do you mean by "same queue manager is created on both machines"?
 
 
Did you run crtmqm twice?
 
 
Then it's not the same queue manager.
 
 
If you did *not* run crtmqm twice, you need to be *explicit* about the *exact* steps that you did run, and *explicit* about *which* of the two machiens you are having issues with. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | girish_kulkarni | 
		  
		    
			  
				 Posted: Tue Apr 03, 2012 9:49 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 08 Oct 2010 Posts: 32
  
  | 
		  
		    
			  
				| Ok. Actually I am not able to start the queue manager after server reboot. Queue manager was working fine from long time. I had to restart without stoping the queue manger. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Tue Apr 03, 2012 10:01 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| girish_kulkarni wrote: | 
   
  
	| Ok. Actually I am not able to start the queue manager after server reboot. Queue manager was working fine from long time. I had to restart without stoping the queue manger. | 
   
 
 
 
Yes, yes we get that. What I (and I think my most worthy associate) are slightly unclear on is exactly how you've configured this active/active setup across the 2 machines; specifically how many queue managers WMQ thinks there are, rather than how many queue managers you think there are.
 
 
Once we have a clearer idea how this is supposed to work, we'll be better able to advise why they're not working. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mvic | 
		  
		    
			  
				 Posted: Tue Apr 03, 2012 11:30 am    Post subject: Re: Not able to start queue manager after server reboot | 
				     | 
			   
			 
		   | 
		
		
		    Jedi
 
 Joined: 09 Mar 2004 Posts: 2080
  
  | 
		  
		    
			  
				
   
	| girish_kulkarni wrote: | 
   
  
	| But still I am facing problem. Please advice as it is very urgent for us. | 
   
 
 
I guess it would help to know what code level you are at.  But check into APAR IV07986, which is fixed in 7.0.1.7 and later.
 
 
If that doesn't fix it, open a PMR if you need urgent help. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | girish_kulkarni | 
		  
		    
			  
				 Posted: Fri Apr 06, 2012 2:12 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 08 Oct 2010 Posts: 32
  
  | 
		  
		    
			  
				| Thanks for your reply. I raised a PMR and asked me to apply fix pack 7.0.1.8. Now it is working fine. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |