Mq Error Reason 2189
Contents |
RSS
Mqopen 2085
Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum mq error 2059 Index » Clustering » Methods to solve Cluster resolution error 2189 Methods to solve Cluster resolution error 2189 « View previous topic :: View next mq error 2009 topic » Author Message prashant_powar Posted: Thu Apr 10, 2008 1:41 am Post subject: Methods to solve Cluster resolution error 2189 NewbieJoined: 10 Apr 2008Posts: 2 Hi All, To solve cluster resolution error I got http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.tro.doc/q039200_.htm the q out of the cluster and put it back in the cluster. By this way the information at repository gets refreshed. Is there any other way to refresh the information at repository and solve cluster resolution error? Thanks, Prash. Back to top AkankshA Posted: Thu Apr 10, 2008 1:48 am Post subject: Grand MasterJoined: 12 Jan 2006Posts: 1494Location: Singapore you might want to have a look at REFRESH http://www.mqseries.net/phpBB2/viewtopic.php?t=42802&sid=52c8998875aaa8edc66d796c075b131d CLUSTER command _________________Cheers Back to top Nigelg Posted: Thu Apr 10, 2008 4:59 am Post subject: Grand MasterJoined: 02 Aug 2004Posts: 1046 No, this is COMPLETELY wrong!!!! 2189 means that information about the queue has not been received back from the full repos qmgrs. The most likely cause is that the channels to/from the qmgrs are not running. That must be investigated first. The result of running REFRESH CLUSTER when the channels are not running is that all cluster metadata is lost, almost the exact opposite of the expected result. REFRESH CLUSTER is almost NEVER the correct response to a cluster problem._________________MQSeries.net helps those who help themselves.. Back to top Vitor Posted: Thu Apr 10, 2008 5:04 am Post subject: Grand High PoobahJoined: 11 Nov 2005Posts: 23698Location: Ohio, USA Moved to Clustering_________________Honesty is the best policy. Insanity is the best defence. Back to top Vitor Posted: Thu Apr 10, 2008 5:05 am Post subject: Grand High PoobahJoined: 11 Nov 2005Posts: 23698Location: Ohio, USA Mr Google wonders if this might help: http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg21225022_________________Honesty is the best policy. Insanity is the best defence. Back to top Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First Page 1 of 1 MQSeries.net Forum Index » Clusterihere for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack http://stackoverflow.com/questions/13687004/how-to-resolve-websphere-mq-reason-code-2195-related-error Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How to resolve WebSphere MQ Reason code 2195 related error? up vote 5 down vote favorite mq error 4 I am getting an WebSphere MQ Reason code 2195 MQRC_UNEXPECTED_ERROR when I try to connect to the message flows deployed on the execution group. Can somebody please tell me what exactly does this reason code mean? Queue manager, broker , execution group.. everything is up and running and the ports are also open. I am not getting anything worthwhile on the net. Please advise. websphere-mq messagebroker share|improve this question edited mq error reason Dec 3 '12 at 17:54 Charles 40.1k1069107 asked Dec 3 '12 at 15:59 Tanu 975514 add a comment| 2 Answers 2 active oldest votes up vote 6 down vote The 2195 return code is a high-level exception that is hit when errors are not caught at lower levels in the code. Very often these are generated when some external dependency such as file access or Os resources does not behave as expected and the failure cascades into WMQ. Usually when these errors are thrown, WMQ will produce an FDC file in {WMQ install dir}/errors to record the event. The FDC file tells which executable failed, the function that was executing during the failure, the environment, user ID and many other details. These can be used by IBM to diagnose the problem but are often useful for WMQ admins as well. As a general rule, for any WMQ error that you cannot easily diagnose, take a look in: {WMQ install dir}/qmgrs/{qmgr name}/errors/AMQERR01.LOG {WMQ install dir}/errors/AMQERR01.LOG {WMQ install dir}/errors/*.FDC When reporting an error, please post whether you found any error log entries or new FDC files in these locations and if so what the content of these was. This will make it easier for respondents to to provide answers that are specific and relevan