MQ Tables COLD restart
MQ stands for "Message Queue". The Message Queue tables basically act as a work space for all of the information traveling between Automic components.
There are 14 MQ tables in v9 and v10
15 MQ tables in v11.1 (one more table because the JWP has been introduced)
26 tables in version 11.2 and v12 because of the Zero Downtime Upgrade:
Sometimes, old messages can be left in the MQ tables causing the Automic system to not be able to start correctly, or freeze. The most common reason for this is if the Automic system has been brought down ungracefully. The best example is if the server that Automic is on has been rebooted or crashed unexpectedly as in a Disaster Recovery (DR) scenario.
When the machine stops suddenly, the messages in the MQ tables are left. When Automic attempts to start the system in "Normal" mode, it will try and process these messages. Because they may no longer have valid information, the WPs or CPs will not connect properly and the system will be unable to start.
This should clear the MQ tables. However, because of potential database issues (locked tables, etc.) you still may not be able to start your system. You can select from the MQ tables to confirm that there are records left in these tables.
If this is the case, you will have to truncate from the MQ tables. Please contact support for the commands to perform this action.
Per default the COLDSTART procedure is not executed against the MQSRV table..
If for a particular reason the purging of this time is required, for example as suggested by BROADCOM support and a Consultant team, the troncation of this table must be done manually by a DBA or by an experienced user.
Either by calling the stored procedure 'UC_Truncate_Table' dedicated to the COLDSTART applied to the MQSRV table
Truncate table MQSRV.