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

Create a technical support case if you need further support.

Unable to shrink the Transaction logs in Deep Security

    • Updated:
    • 27 Nov 2019
    • Product/Version:
    • Deep Security 11.0
    • Platform:
    • N/A
Summary

In server0.log, there are too many entries showing "The transaction log for database 'DSM' is full due to 'LOG_BACKUP'." Below is a sample log:

Jun 09, 2019 1:10:50 PM com.thirdbrigade.manager.core.scheduler.JobQueuingThread doRun
SEVERE: ThID:24|TID:0|TNAME:Primary|UID:-1|UNAME:|Exception caught attempting to own and queue job, ManagerJobID: 1397175
com.microsoft.sqlserver.jdbc.SQLServerException: The transaction log for database 'DSM' is full due to 'LOG_BACKUP'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1535)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:467)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:409)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7151)
Details
Public

To resolve the issue:

  1. Stop the Deep Security Manager service.
  2. Login the database server desktop and login the SQL server with SQL Server Management Studio.
  3. Open a new query and execute the following: ​​
     
    Make sure to replace the <DSM_database_name> in the command below with the actual DSM database name of the customer. For "dbcc shrinkfile", use the default file name when creating database. However, if the customer changed it, modify the value to the correct Logical Name to database files. To find the Logical Name, right-click the database and go to Properties > Files.
    use <DSM_database_name> 
    go
    alter database <DSM_database_name> set single_user with rollback immediate
    go
    dbcc checkdb ('<DSM_database_name>', REPAIR_FAST)
    go
    dbcc shrinkdatabase ('<DSM_database_name>', TRUNCATEONLY)
    go
    dbcc shrinkfile ('<DSM_database_name>', TRUNCATEONLY)
    go
    dbcc shrinkfile ('<DSM_database_name>_log', TRUNCATEONLY)
    go
    alter database <DSM_database_name> set recovery simple
    go
    alter database <DSM_database_name> set multi_user with rollback immediate
    go
  4. Start the Deep Security Manager service.
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
000155820
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.