MQSeries.net :: View topic

lung · Posted: Sat Aug 30, 2003 8:22 pm Post subject:

Hi,

I'm having a few problems due to a deployment attempt yesterday.

My first attempt at deploying is unsuccessful. After checking on the logs, I found out that the Queue Manager's log on the Config Manager is full. First question - How do I clear the Queue Manager's log? My Config Manager machine is a Windows 2000 machine.

During the process of finding out why the first attempt of deployment is unsuccesful, I restarted the machine. The MQ channels went down, and in the process of restarting them, I accidentally deleted the a deployment message in the transmission queue.

Now, I can no longer perform a delta deployment because the Config Manager will return the error BIP1510E - Unable to deploy configuration data. It appears the Config Manager is waiting for the previous deployment to come back. But I have already deleted the deployment message in the transmission queue!

One solution to solve this problem is to perform a FORCED complete deployment. But I don't want to do this if necessary. There are a lot of message flows running in the broker (which is on an OS/390 machine) in which if I perform a complete deployment, it will take ages to complete and possible results in a timeout (which is not good).

So here's my second question - Can I perform a FORCED delta deployment? Or is there any other way around this problem? Can I delete off a DB2 entry in the Config Manager's database that is corresponding to the deployment?

This is happening in my Production environment.
Please advice.

Thanks!