| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Queue Manager Ended abnormally |
« View previous topic :: View next topic » |
| Author |
Message
|
| sudhaRam |
 Posted: Fri Nov 30, 2007 9:01 am Post subject: |
 |
|
Novice
Joined: 13 Nov 2007
Posts: 12
|
The things that i did in UNIX end,
Log in as someone in the 'mqm' group.
Record the logging parameters of the failing queue manager by checking '/var/mqm/qmgrs/OLDQMGR/qm.ini'. These parameters include the type, number, size and location of the log files.
Create a queue manager called 'TEMP' with identical logging parameters. For example, 'crtmqm TEMP' will create a new queue manager with the default size and number of circular logs.
Type 'cd /var/mqm/log'. Type 'ls -l'. You should see subdirectories for each of your queue managers, including the new 'TEMP' queue manager.
Type 'rm -rf OLDQMGR'.
Type 'mv TEMP OLDQMGR'.
Copy the /var/mqm/qmgrs/TEMP/amqalchk.fil to /var/mqm/qmgrs/OLDQMGR/ (backing up the original)
Type 'strmqm OLDQMGR' to restart your original queue manager.
The Channel from Mainframe is running fine now as we emptied the Transmission Queue and Reset the channel sequence number. Thanks for all ur help |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Nov 30, 2007 9:31 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
So you blew away all the data on your queue manager and then you deleted all the data in the MF's transmission queue. OK then. If you have trouble with a database would you delete all the rows to solve it?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| sudhaRam |
| Posted: Fri Nov 30, 2007 9:38 am Post subject: |
|
|
Novice
Joined: 13 Nov 2007
Posts: 12
|
| Different issues have different resolution.In this case we tried all the option of starting the listener, resetting the channel sequence number. The problem here was the ping channel was a normal completion, and the transmission Queue Properties were altered in Mainframes. The Get Enabled was inhited and the trigger set changed to No automatically. Even the Alter Queue Option did not work. Once we set the Transmission Queue and tried to start the channel it went to Retry and the Transmission Queue Properties changed. With no option we tired deleting the messages. All problems will not have the same solution |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Nov 30, 2007 9:47 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The channel was retrying because the sequence #s were mismatched because you blew away the sequence #s when you fooled around with deleting and overlaying files. The XMITQ and Channel behaviour after that was perfectly normal and working as designed. You did not have to delete all the messages!
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
