Posted: Thu Jul 23, 2009 8:47 am Post subject: active logs
Centurion
Joined: 30 Nov 2007 Posts: 126
Hi Guys,
I had a scenerio where I had to change the active logs to 4 primary and 3 secondary instead of 3 & 2 resp. The messages are rolled back because the 3 primary logs that are being created get maxed out. I dont see the 4th one being created. I had bounced the QM too to take affect. But no luck..The server has lot of disk space. So I dont think we are facing a space issue..
Any ideas as to why the 4th primary log is not being created after the three are maxed out?
Posted: Thu Jul 23, 2009 10:20 am Post subject: Re: active logs
Poobah
Joined: 15 May 2001 Posts: 7722
Before you bounced the QM it still only knew about 3.
After you bounced it all your transaction were committed or backed out and you haven't needed the 4th one yet. The manual states the QM will build it when it feels like it. Only at QM creation time do you see all your primaries right away.
velocity wrote:
The server has lot of disk space.
Why then are you going from 3 allllllllll the way up to 4? Just jack up the logs to several gigs worth, otherwise you'll be upping it from 4 to 5, from 5 to 6, etc. _________________ Peter Potkay
Keep Calm and MQ On
Cause . . . . . : This message is issued periodically by WebSphere MQ to
help you identify which journal receivers can be removed from the system
because they are no longer required for media recovery.
Recovery . . . : None
Technical Description . . . . . . . . : The date of the oldest journal
entry required for media recovery is 07/23/09 11:19:49. This entry is contained
in journal receiver AMQA004202. Journal receivers older than this are not
required by WebSphere MQ for media recovery. If the journal receiver name is
**********, WebSphere MQ was unable to determine the name of the receiver.
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