WebSphere MQ Resources

More documents

Recommendations

Info

119035 CHECKTYPE check for queue managerwith TAG "TAG" failed on server"SERVER" because no TCP PORTdirective found in config file"CONFIGFILE" - ignoring.119042 “CHECKTYPE” check for queuemanager with TAG “TAG” failed onserver “SERVER” because no TCPPORT information was found viarunmqsc.119043 TCP Listener configuration could not beread, reason: “REASON”.119044 No TCP Listener configured, no TCPPORT information was found viarunmqsc: “MESSAGE”.Make sure the queue managerconfiguration file (qm.ini) exists andcontains a TCP section as requiredduring installation.Add the TCP section to the queuemanager configuration file.Verify that the port information for thelistener objects has been defined and isaccessible via runmqsc.Verify that MQ is running and the portinformation for the listener objects hasbeen defined and is accessible viarunmqsc.Verify that the port information for thelistener objects has been defined and isaccessible via runmqsc.CreateError Error MessageNumber001022 END failed hierarchy “CREATE” ofresource “TAG” on server “SERVER”with return value of “VALUE”.119020 Create MQSeries queue managerresource with TAG “TAG” for queuemanager “QMGR” failed.119022 Failed to create dependency between“PARENT” and “CHILD”.119023 Creating the filesystem hierarchies forqueue manager with TAG “TAG”failed. File systems: “Filesystems”.119029 No TCP section configured in"CONFIGFILE" on server "SERVER".119031 Queue manager "DIRTYPE" directory("DIRECTORY") not on shared storage.119038 Creation of queue manager resourcewith TAG "TAG" failed on server"SERVER".ActionCheck the LifeKeeper log on server“SERVER” for possible errors creatingthe resource hierarchy. The failure isprobably associated with the queuemanager not starting.Check the LifeKeeper log for possibleerrors creating the resource. The failureis probably associated with the queuemanager not starting.Check the LifeKeeper log for possibleerrors creating the dependency.Check the LifeKeeper log for possibleerrors creating the filesystemhierarchies.Add the TCP section to the queuemanager configuration file on serverSERVER. See section “ConfigurationRequirements” for details.Move the directory DIRECTORY toshared storage and retry the operation.Check the LifeKeeper log on serverSERVER for possible errors, correctthem and retry the operation.LifeKeeper for Linux 58
WebSphere MQ Troubleshooting119039 TCP section in configuration file"FILE" on line "LINE1" is locatedbefore LOG section on line "LINE2" onserver "SERVER".119040 Creation of MQSeries queue managerresource by create_ins was successfulbut no resource with TAG “TAG”exists on server “SERVER”. Sanitycheck failed.119041 Creation of MQSeries queue managerresource was successful but no resourcewith TAG “TAG” exists on server“SERVER”. Final sanity check failed.ExtendError Error MessageNumber119024 Instance "TAG" can not be extendedfrom "TEMPLATESYS" to"TARGETSYS". Reason:REASON119027 The user "USER" does not exist onserver "SERVER".119028 The user "USER" has a differentnumeric UID on server "SERVER1"(SERVER1UID) then it should be(SERVER2UID).119029 No TCP section configured in"CONFIGFILE" on server "SERVER".119030 Queue manager "QMGR" notconfigured in "CONFIGFILE" onserver "SERVER".119036 Link "LINK" points to "LINKTARGET"but should point to "REALTARGET" onserver "SERVER".It’s recommended for the TCP sectionto be located after the LOG: section inthe queue manager configuration file.Move the TCP section to the end of thequeue manager configuration file andretry the operation.Check the LifeKeeper log for possibleerrors during resource creation.Check the LifeKeeper log for possibleerrors during resource creation.ActionCorrect the failure described inREASON and retry the operation.Create the user USER on SERVER withthe same UID as on the primary serverand retry the operation.Change the UID so that USER has thesame UID on all servers and reinstallWebSphere MQ on the server whereyou have changed the UID and retry theoperation.Add the TCP section to the queuemanager configuration file on serverSERVER.See section “ConfigurationRequirements” for details.The queue manager QMGR you aretrying to extend is not configured in theglobal configuration file on the targetserver SERVER. Add the queuemanager stanza to the config fileCONFIGFILE on server SERVER andretry the operation.For file system layout 3 symbolic linksmust point to the same location on thetemplate and target server SERVER.LifeKeeper for Linux 59
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: WebSphere MQ Troubleshootingnot exi
Page 63 and 64: 119004 Some orphans of queue manage
Page 65 and 66: WebSphere MQ Troubleshooting119209
Page 67 and 68: Appendix B - Sample qm.ini Configur
show all

WebSphere MQ Resources

Create successful ePaper yourself

Delete template?

Save as template?