Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

The Control Manager (TMCM) database remains massive after purging all logs

    • Updated:
    • 27 Jul 2016
    • Product/Version:
    • Control Manager 6.0
    • Platform:
    • Windows 2000 Advanced Server
    • Windows 2000 Server
    • Windows 2003 Enterprise Server
    • Windows 2003 Standard Server Edition
Summary

The TMCM database size still remains huge even after purging the other logs and optimizing the database.

Details
Public

Control Manager (TMCM) also stores Command Tracking logs which cannot be purged via the console. This leads to a substantial growth in the database size.

To purge the Command Tracking logs:

 
This procedure will involve the usage of the Truncate Table SQL Command, that will permanently remove all virus logs, security logs, and other logs that will be truncated. Before proceeding, back up the TMCM database.
  1. Open the SQL Query.
  2. Stop the TMCM Services.
  3. Run the following scripts in SQL query:
     
    If the TMCM server is a Child server in a cascading environment, and is scheduled to perform Upload Logs at a certain schedule, the logs being uploaded to the Parent CM server will be lost if the tb_templog is truncated.

    truncate table tb_tvcscommandlist;
    truncate table tb_tvcsCommandTaskqueue;
    truncate table tb_commanditemtracking;
    truncate table tb_commandtracking;
    Backup log db_controlmanager with truncate_only;
    exec sp_dboption 'db_controlmanager', 'trunc. log on chkpt.', 'TRUE';
    exec sp_dboption 'db_controlmanager', 'autoshrink', 'TRUE';

  4. Restart the TMCM Services.

You can also change the automatic purge settings for the Command Tracking logs (90 days for CommandTracking and 24 hours for CommandTaskQueue) in the SystemConfiguration.xml file:

  • CommandItemTracking and commandTracking are configured in "m_iCommandTrackingLogPurgeRange".
  • CommandTaskQueue table is configured in "m_iCommandQueueTimeOut".

Restart the TMCM services after changing the settings in the XML file.

Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1033271
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.