WebSphere MQ Resources

More documents

Recommendations

Info

WebSphere MQ Troubleshooting119037 Link "LINK" that should point to"REALTARGET" does not exist onsystem "SERVER".ErrorNumberRemoveError Message119003 Failed to stop queue manager with TAG“TAG” on server “SERVER".Correct the link LINK on serverSERVER to point to REALTARGET andretry the operation.For file system layout 3 symbolic linksmust also exist on the target server.Create the required link LINK toREALTARGET on server SERVER andretry the operation.ActionThe queue manager “TAG” on server“SERVER” could not be stoppedthrough the Recovery Kit. For furtherinformation and investigation, changethe logging level to DEBUG.Depending on the machine load theshutdown timeout values possibly haveto be increased.60 WebSphere MQ Recovery Kit Administration Guide
119004 Some orphans of queue manager withTAG “TAG” could not be stopped onserver "SERVER". Tried it “tries” times.119010 Listener for queue manager with TAG"TAG" failed to stop on server"SERVER".ErrorNumberResource MonitoringError Message119005 Queue manager with TAG “TAG” onserver "SERVER" failed.119009 Listener for queue manager with TAG“TAG” failed on server "SERVER".119011 “CHECKTYPE" PUT/GET Test forqueue manager with TAG "TAG" failedon server "SERVER" with return code"Code"119012 Client connect test for queue managerwith TAG "TAG" on server "SERVER"failed with return code "Code".Try killing the orphans manually andrestart the Queue Manager again.For further information change thelogging level to DEBUG.This message will only appear if themonitoring for the listener isenabled. For further informationchange the logging level to DEBUG.ActionCheck the IBM WebSphere MQ alertlog on SERVER for possible errors. Thismessage indicates a queue managercrashThis message will only appear ifmonitoring of the listener is enabled.For further information change thelogging level to FINE.This message will only appear if thePUT/GET Test is enabled and the testqueue exists. For further informationchange the logging level to FINE andcheck the IBM WebSphere queuemanager error log (/var/mqm/errors) onSERVER for possible errors and correctthem. Verify that the file systems arenot full.This message will only appear ifListener management is enabled.This message indicates a problemwith the listener or the queuemanager.Check the log for possible errorsand correct them.The return code Code is the returncode of the amqscnxc command.LifeKeeper for Linux 61
Page 1 and 2:
LifeKeeper ® for LinuxWebSphere MQ
Page 3 and 4:
Table of ContentsIntroduction .....
Page 5 and 6:
WebSphere MQ Recovery KitAdministra
Page 7 and 8:
IntroductionAbbreviationsThe follow
Page 9 and 10:
RequirementsRecovery Kit Installati
Page 11 and 12: WebSphere MQ Recovery Kit OverviewF
Page 13 and 14: WebSphere MQ Configuration Consider
Page 19 and 20: Configuring WebSphere MQ for Use wi
Page 21 and 22: Configuring WebSphere MQ for Use wi
Page 23 and 24: Configuration Changes After Resourc
Page 25 and 26: WebSphere MQ Configuration Examples
Page 33 and 34: LifeKeeper Configuration TasksLifeK
Page 35 and 36: LifeKeeper Configuration TasksChann
Page 37 and 38: LifeKeeper Configuration TasksUnext
Page 39 and 40: LifeKeeper Configuration Tasks6. On
Page 41 and 42: LifeKeeper Configuration Tasksa. No
Page 43 and 44: LifeKeeper Configuration TasksThe p
Page 45 and 46: LifeKeeper Configuration TasksLifeK
Page 47 and 48: LifeKeeper Configuration TasksSever
Page 49 and 50: LifeKeeper Configuration TasksChang
Page 57 and 58: WebSphere MQ TroubleshootingWebSphe
Page 59 and 60: WebSphere MQ Troubleshootingnot exi
Page 61: WebSphere MQ Troubleshooting119039
Page 65 and 66: WebSphere MQ Troubleshooting119209
Page 67 and 68: Appendix B - Sample qm.ini Configur
show all

WebSphere MQ Resources

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?