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

Create a technical support case if you need further support.

Database size increases due to transaction logs in Control Manager (TMCM)

    • Updated:
    • 20 Feb 2015
    • Product/Version:
    • Control Manager 6.0
    • Platform:
    • Windows 2003 Server R2
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 2012 Enterprise
    • Windows 2012 Server Essentials
    • Windows 2012 Web Server Edition
Summary

Know what to do when transaction logs become bigger and eat up space causing the TMCM database to get increase its size. 

Details
Public

To resolve the issue:

  1. Stop the following services:
    1. Trend Micro Control Manager service
    2. Trend Micro Management Infrastructure service.
  2. Back up the TMCM database.
  3. Shrink the TMCM database transaction log. Choose one of the following options:
    1. In Object Explorer, connect to an instance of the SQL Server Database Engine and then expand that instance.
    2. Expand Databases, and then right-click the database that you want to shrink.
    3. Point to Tasks, point to Shrink, and then click Files.
    4. Do the following:
      1. Select Log as the file type.
      2. Mark the Release unused spacecheck box.
        Selecting this option causes any unused space in the file to be released to the operating system and shrinks the file to the last allocated extent. This reduces the file size without moving any data.
    5. Click OK.

    If you still need more help with shrinking the transaction log using this method, refer to theMicrosoft article: Shrinking the Transaction Log.

    Execute the following SQL query:

    BACKUP LOG <TMCM db Name>_Log WITH TRUNCATE_ONLY
    GO
    DBCC SHRINKFILE(<TMCM db Name>_Log , 10)
    GO

    The <TMCM DB name> is the name of the Control Manager database. For example, if the name of the Control Manager database is db_controlManager, the command would be the following:

    BACKUP LOG db_ControlManager_Log WITH TRUNCATE_ONLY
    GO
    DBCC SHRINKFILE(db_ControlManager_Log , 10)
    GO

    Since BACKUP LOG WITH TRUNCATE_ONLY is no longer a recognized BACKUP option in SQL Express 2008 you will encounter the following error after executing this query:

    Msg 155, Level 15, State 1, Line 1
    'TRUNCATE_ONLY' is not a recognized BACKUP option.

    Another way of shrinking the transaction logs in SQL server 2008 Express is to send Log Backups to “NUL:” using command:

    BACKUP LOG [db_name] TO DISK = N'Nul:

     
    This problem has been resolved in TMCM 6.0 Patch 4 and the fix is also included in TMCM 6.0 SP1.
  4. Start the following services:
    • Trend Micro Management Infrastructure service
    • Trend Micro Control Manager service.
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1060713
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.