XAResourceManager failing.
Hi all, I have a tricky problem with a XAResourceManager running on Oracle8. Env. SunSolaris, MQ5.2. Friday nigth one of our servers was shut down and when trying to start the Qmanager on the server it didn't start with the following error text. $ strmqm QMTEST AMQ7626: XA resource manager initialization failure. Refer to the error log for more information. I checked the qm.ini file and the XAResourceManager initiation.. XAResourceManager: Name=Oracle BPD1ADM SwitchFile=/opt/mqm/mwas/xatm/ora8swit XAOpenString=Oracle_XA+Acc=P/arbor/arbtest+SesTm=35+LogDir=/tmp/ora.log+DB=BPD1ADM/ Which looked OK to me, I have a very limited experience of oracle and XAResourceManager. And the error log states: --- 09/30/02 05:14:20 PM AMQ6175: The system could not dynamically load the library /opt/mqm/mwas/xatm/ora8swit. The error message was ld.so.1: amqzxma0: fatal: libucb.so.1: open failed: No such file or directory. The Queue Manager will continue without this module. EXPLANATION: This message applies to Sun Solaris systems. The dynamically loadable file /opt/mqm/mwas/xatm/ora8swit failed to load correctly due to an internal error. and the MQSeries error recording routine has been called. ACTION: Check that the file has not been corrupted then use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. --- 09/30/02 05:14:20 PM AMQ7622: MQSeries could not load the XA switch load file for resource manager 'Oracle BPD1ADM'. EXPLANATION: An error has occurred loading XA switch file /opt/mqm/mwas/xatm/ora8swit. If the error occurred during startup then the queue manager will terminate. At all other times the queue manager will continue without this resource manager meaning that it will no longer be able to participate in global transactions. The queue manager will also retry the load of the switch file at regular intervals so that the resource manager will be able to participate again should the load problem be resolved. ACTION: Look for a previous message outlining the reason for the load failure. Message AMQ6175 is issued if the load failed because of a system error. If this is the case then follow the guidance given in message AMQ6175 to resolve the problem. In the absence of prior messages or FFST information related to this problem check that the name of the switch load file is correct and that it is present in a directory from which it can be dynamically loaded by the queue manager. The easiest method of doing this is to define the switch load file as a fully-qualified name. Note that if the queue manager is still running it will need to be restarted in order that any changes made to its configuration data can be picked up. We recreated the ora8swit file but the Qmanager still wont start... Anyone have an idea what migth be causing all this?? Please Advice Erik _ Chat with friends online, try MSN Messenger: http://messenger.msn.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
5.3 kernel parameters compared to 5.2 (HP)
Hi, Has anybody looked at WMQ 5.3 compared to MQ 5.2 on HP?Specifically at the kernel requirements. The first parm in Quick Beginnings is shmmax. This looks like it went from 4 MEG to 536 MEG. And I can't find any explanation for this. The first system that I'm going to try out 5.3 on only has 40 Meg of shared memory and I was hoping to install this quietly without reboots or anything. Anybody with experience?Any comments from IBM? What's changed so much with 5.3? Thanks Tom
Re: Primary and Secondary Logs on Linear Logged Qmgr
John, I've got your question with some delay - I'm receiving digests only to save time on reading. You might have got an answer already, but if it's not the case, I can give you one, which most likely will solve your problem. The answer is, of course, as most of the answers, in the IBM docs. "When nothing else helps, read the documentation" - I myself did this only after a lot of banging of my head against the desk :o) The answer is that primary and secondary log settings are as important for linear logging, as they are important for the circular one. And it is most that adjustment of those settings can provide the solution for your transaction BACKED_OUT problem. Have a look at "System Admin", Ch. 15 Recovery and Restart, Linear Logging, p. 215: "The number of log files used with linear logging can be very large, depending on your message flow and the age of your queue manager. However, there are a number of files that are said to be active. Active files contain the log entries required to restart the queue manager. The number of active log files is usually the same as the number of primary log files as defined in the configuration files." p. 218: "If the primary log files are completely filled before the long-running transaction completes, secondary log files are used to avoid the risk of a log full situation if possible." p. 220: "The total number of primary and secondary log files cannot exceed 63, which, in the presence of long-running transactions, limits the maximum amount of log space that can be made available to the queue manager for restart recovery." This means that no matter how much space you might have in your /var/mqm/log file system, you can't process transaction that won't fit into ACTIVE logs during checkpointing for persistent messages. It looks like for some reason application that's putting messages to your queue has an unusually long-running transaction. Most probable (correct me if I'm wrong) you have in your qm.ini standard settings of Log: LogPrimaryFiles=3 LogSecondaryFiles=2 This gives you up to 5 active files - which easily can cause 2003 - MQRC_BACKED_OUT for a long-running transaction. In view of all mentioned above you have the following options: 1. Increase number of ACTIVE logs in qm.ini. Determine yourself the balance you want between Primary and Secondary files, or use IBM's 3:2 ratio. Maximum number of ACTIVE logs can't exceed 63. You'll have to stop and start Queue Manager for the new settings to take effect. 2. Increase size of log file (LogFilePages parameter). This will involve recreation of the Queue Manager, though, and should be used only if the you hit the maximum of 63 for ACTIVE (Primary + Secondary) logs and still have 2003 problem. Those are administrative solutions and have an advantage that you don't have to change an application. As such they are limited - it would be always possible for an application to generate such a long-running transaction that won't fit into most carefully tuned ACTIVE log files. The 2003-MQRC_BACKED_OUT problem is created by the application and, whenever possible, should be best and most effectively resolved in the application. The sender of the persistent messages can have control over the length of its transactions and should use this opportunity. Controlling the size of the Logical Unit of Work by issuing intermediate MQCMITs after certain amount of messages would ensure that no single transaction would become a long-running one under any circumstances. If application doesn't use intermediate MQCMITs, this is an invitation for the 2003 problem that would strike sooner or later. Any delay in communication for such an application (network problems, receiving server or queue manager down, etc.) could cause potential accumulation of messages in the transmission queue of the sending channel high enough to cause the 2003 problem. Since delays in communication are always possible, keeping the size of transactions always within reasonable and predefined limits would make the overall messaging network more stable. I hope this will help you. Regards, Vlad. -Original Message- From: John Matoba [mailto:[EMAIL PROTECTED]]=20 Sent: 25 September 2002 09:34 To: [EMAIL PROTECTED] Subject: Primary and Secondary Logs on Linear Logged Qmgr Do primary and secondary log settings in the qm.ini apply to linear logged queue managers? I can see where they are needed for circular logging, but what is the purpose of using these settings in a linear logged setting? We are currently receiving a 2003 error from an application running against a linear logged queue manager. It has a long-running uow that would certainly cause this error on a circular logged queue manager, but I don't know how you can get a 2003 error on a linear logger queue manager unless you run out of disk space or exceed MAXUMSGS (neither of which is the case)? Thanks in Advance, John Mat
Re: no SYSTEM.DEF.CLNTCONN
Hi Francios, Try thse steps:- Stop the queue manager strmqm -c strmqm Now try creating your client channel, everything should work fine. Hope this helps. Cheers, Adi From: "Francois Van der Merwe1" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 09/30/2002 04:08 PM ZE2 Please respond to "MQSeries List" <[EMAIL PROTECTED]> Sent by:"MQSeries List" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:no SYSTEM.DEF.CLNTCONN Windows 2000: WMQ 5.3 After creating a new queue manager it seems like all default objects are present except SYSTEM.DEF.CLNTCONN with the result that when I try to create a new client connectoin I get the error: AMQ4000 I managed to create SYSTEM.DEF.CLNTCONN via runmqsc, but it does not show up in the "WebSphere MQ Explorer" console, but when I list it under runmqsc, it is there. After this I still can't create any client channels. Any ideas? Francois van der Merwe Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: no SYSTEM.DEF.CLNTCONN
Francois, Don't you mean SYSTEM.DEF.SVRCONN? By default no objects prefixed with SYSTEM.* is displayed in the explorer. JOnas Nyberg Electrolux IT Solutions - Sweden -Original Message- From: Francois Van der Merwe1 <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Mon, 30 Sep 2002 16:08:18 +0200 Subject: no SYSTEM.DEF.CLNTCONN Windows 2000: WMQ 5.3 After creating a new queue manager it seems like all default objects are present except SYSTEM.DEF.CLNTCONN with the result that when I try to create a new client connectoin I get the error: AMQ4000 I managed to create SYSTEM.DEF.CLNTCONN via runmqsc, but it does not show up in the "WebSphere MQ Explorer" console, but when I list it under runmqsc, it is there. After this I still can't create any client channels. Any ideas? Francois van der Merwe Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Larry Smolic/ISD/VWA is out of the office.
I will be out of the office starting 30/09/2002 and will not return until 31/12/2002. For middleware issues please contact mailto:[EMAIL PROTECTED]. Other e-mails can be sent to mailto:[EMAIL PROTECTED] - Laz. IMPORTANT - (1) The contents of this email and its attachments may be confidential and privileged. Any unauthorised use of the contents is expressly prohibited. If you receive this email in error, please contact us, and then delete the email. (2) Before opening or using attachments, check them for viruses and defects. The contents of this email and its attachments may become scrambled, truncated or altered in transmission. Please notify us of any anomalies. (3) Our liability is limited to resupplying the email and attached files or the cost of having them resupplied. (4) The VWA collects personal information to enable it to perform its functions. For more information about the use, access and disclosure of this information, refer to our privacy policy at www.workcover.vic.gov.au Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
no SYSTEM.DEF.CLNTCONN
Windows 2000: WMQ 5.3 After creating a new queue manager it seems like all default objects are present except SYSTEM.DEF.CLNTCONN with the result that when I try to create a new client connectoin I get the error: AMQ4000 I managed to create SYSTEM.DEF.CLNTCONN via runmqsc, but it does not show up in the "WebSphere MQ Explorer" console, but when I list it under runmqsc, it is there. After this I still can't create any client channels. Any ideas? Francois van der Merwe Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: MQSeries Server 5.2.1 on Win2000
Jim, try this Check that your queue manager is set to automatic Stop and restart the IBM MQSeries service Check the status of the queue manager Log off and on Check the status of the queue manager again (I have a faint memory of having seen the unavailable status when then service is not started) Christian Wolfhagen Senior Consultant Cressida Technology Ltd. Phone: +45 4848 2593 Mobile: +45 2176 7113 e-mail: [EMAIL PROTECTED] WWW: http://www.cressida.info Attachments within this mail have been automatically compressed using ZipMail for Notes and Exchange to save you Time, Storage and Bandwith! See www.cressida.info/products_mk.shtml for details! -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]] On Behalf Of Wert, Jim Sent: 27. september 2002 23:45 To: [EMAIL PROTECTED] Subject: Re: MQSeries Server 5.2.1 on Win2000 MQSeries Services is started and set to start automatically. It is set to Log on as Local System Account. I'm using the IBM MQSeries Services console to define the properties of the queue manager. The startup type for the queue manager is set to automatic. I can also start the queue manager from this screen. After logging off and then back on, the status of the queue manager changes from running to unavailable. My MQSeries queue manager log files indicate that the queue manager has started, but I can't determine why it is going to unavailable status. Any other ideas? Thanks! Jim -Original Message- From: Paul Clarke [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 5:15 PM To: [EMAIL PROTECTED] Subject: Re: MQSeries Server 5.2.1 on Win2000 >When I sign off of the Windows 2000 server, my queue manager is stopping. >What do I need to do to keep the queue manager running after I've logged off >the server? You need to start the Queue Manager as a service. Paul G Clarke WebSphere MQ Development IBM Hursley Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: MQSeries Server 5.2.1 on Win2000
Title: RE: MQSeries Server 5.2.1 on Win2000 I had the sane problem, but when i looked at the error logs i found that there was an authorization error. It said that the amqzfu0 module used for auth's could not be loaded dynamically. I tried changing the registry settings but that didn't help. I then installed mq series in the default directory and everything was fine. However this was with MQ v5.3. Check for the processes that are running and see if you are missing any processes by comparing. That would ideally tell you which process is failing. Also see if any FDC files are being created. Use them for debugging... -Original Message- From: Wert, Jim [mailto:[EMAIL PROTECTED]] Sent: Friday, September 27, 2002 4:45 PM To: [EMAIL PROTECTED] Subject: Re: MQSeries Server 5.2.1 on Win2000 MQSeries Services is started and set to start automatically. It is set to Log on as Local System Account. I'm using the IBM MQSeries Services console to define the properties of the queue manager. The startup type for the queue manager is set to automatic. I can also start the queue manager from this screen. After logging off and then back on, the status of the queue manager changes from running to unavailable. My MQSeries queue manager log files indicate that the queue manager has started, but I can't determine why it is going to unavailable status. Any other ideas? Thanks! Jim -Original Message- From: Paul Clarke [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 5:15 PM To: [EMAIL PROTECTED] Subject: Re: MQSeries Server 5.2.1 on Win2000 >When I sign off of the Windows 2000 server, my queue manager is stopping. >What do I need to do to keep the queue manager running after I've logged off >the server? You need to start the Queue Manager as a service. Paul G Clarke WebSphere MQ Development IBM Hursley Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Revisited: >4MB probelm on Solaris
>>>Even if you havn't had the problem, it would be great to get confirmed >>>that someone have succeeded to send >4MB messages using JMS to attach >>>to a Solaris queue manager - binding mode or tcpip mode. Johan I assume you have checked that the default 4Mb message size limits have been overridden: 1) On the queue manager itself 2) On the server connection end of your channel 3) On the client connection end of your channel I believe all three are required to make this work. Nigel This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
