Video Screencast Help

Symantec Endpoint Protection DB Log Problem

Created: 04 Jun 2012 • Updated: 04 Jun 2012 | 3 comments

Hey guys,

I don't understand why a log can grow to such unimaginable sizes, in just 3 months of having SEP installed this log grew up to 65+GB

I had to create a script to clear it and still, just after today's updates, it went from 516KB to 450MB

To me, that just doesn't make any sense.

Here is the script:

@echo off
REM Stop the services
net stop semsrv
net stop SQLANYs_sem5
REM Allow deletion
attrib -r "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.log"
REM Delete the log file
del "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.log"
REM Recreate the file (this time empty)
"C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\dbsrv11" -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db"
REM Restart the services
net start SQLANYs_sem5
net start semsrv

Create a .bat file with these lines in it and run it.

You might want/need to add (x86) next to Program Files if you have Windows Server x64 installed

Comments 3 CommentsJump to latest comment

pete_4u2002's picture

is this SEP for SBE?

if yes, check this link

This issue has been fixed in Symantec Endpoint Protection 12 Release Update 1 (RU1) Maintenance Patch 1 (MP1).

Symantec Endpoint Protection Manager (SEPM) database transaction log (sem5.log) consumes excessive hard drive space in SEP SBE 12.1 RU1

Shulk's picture

Pete is right if you are using SBE, however if you are using Enterprise Edition (EE), simply enable both options Truncate the database transaction logs and Rebuild Indexes from the SEPM Database Maintenance Tasks to keep Sem5 under control:

  1. Log in to the Sep Manager.
  2. Click Admin and select Servers.
  3. Select the localhost under Servers.
  4. Under Tasks, Select Edit Database Properties.
  5. In the General tab under Database Maintenance Tasks.
  6. Select the checkboxes next to Truncate the database transaction logs and Rebuild Indexes.
  7. Click OK to apply the changes.

(Source: TECH166658)

To reduce the size of Sem5 right away, simply click on Truncate Transaction Log Now and Rebuild Indexes Now from Admin/Servers/Tasks.

Hope it helps! And don't forget to mark the solution!


Mithun Sanghavi's picture


There is a Tool available for Shrinking the Database.

Shrink the Symantec Endpoint Protection Manager (SEPM) 12.1 embedded database

Also, check this Article:

How to periodically free up the space used by the sem5.log in EPSBE 12.1 RU1

Hope that helps!!

Mithun Sanghavi
Associate Security Architect


Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.