We have one of our exchange servers whose hdb and spooler and in an error state. Upon checking log files, we can see that it is because of the spooler queues. How do we get rid of the queues in spooler when it is in an error state?
Hi kanandaguberan ,
Which product is this question referring to? If I know which this question is for, I can move it to the appropriate product community, where it's more likely that experts will see it and respond.
This is for Nimsoft/ UIM
Thanks! I have moved this question to the CA Infrastructure Management community under the CA UIM category.
1) Check the <nimsoft>\robot\q1.rdb and q2.rdb files. These are the queue files for the spooler.
If q2.rdb is small (~1KB) and q1.rdb is continuing to grow, there's probably corrupt data in q2.rdb that's causing QoS to queue on the spooler.
2) Stop the robot.
3) Move q2.rdb to a temp folder
4) Restart the robot.
This will allow the robot to create a new q2.rdb file which should then allow q1.rdb to begin to flush. An analysis of the archived q2.rdb may show corrupt data via illegal characters which was disrupting the normal data flow.
If you don't mind loosing any data, you can simply delete both of those files and they will be recreated after the robot is re-activated.
I did check these files and they seem to be of the same size, however the last modified date was on the 7th of this month. The log file has entries saying it is queued and later has an entry saying unable to find the path specified.
does the .rdb maximum file size can be configured in spooler probe (Message queue size limit)?
Yes the maximum queue size is configurable through the parameter.
Thanks. And what is the default size for the maximum queue size parameter? Any references to calculate it?
No default value for max size. The data retention period (7 days) is default behavior.