Video Screencast Help

SEP: sem5 log size problem

Created: 29 Aug 2013 • Updated: 01 Sep 2013 | 8 comments
D@ry1's picture
This issue has been solved. See solution.

Hey guys,

We have this weird problem about the sem5 log becoming so much larger than it usually was, I read som KB and threads and most issues are said to be solve by doing the manual process on CMD by deleting the sem5.log and running a certain command to remake a new one and the other one is by upgrading to 12.1 RU1 MP1,

The thing is we're already running on 12.1RU2, are those procedure still applicable to us?


Operating Systems:

Comments 8 CommentsJump to latest comment

Ambesh_444's picture


Pleasze check this.

Thank& Regards,


"Your satisfaction is very important to us. If you find above information helpful or it has resolved your issue. Please don't forget to mark the thread as solved."

James007's picture

The thing is we're already running on 12.1RU2, are those procedure still applicable to us?

yes this applicable on sep 12.1.2 you can try this.

yoou can check this artical

Rafeeq's picture

Yes those are still applicable to this  versions. SEM5.log does not truncates and it keeps growing

In SEPM Enterprise version, you have the option to truncate this log and it can be scheduled as well. Unfortunately that option does not exist in SMB.

D@ry1's picture

Awesome you'd just got it right,. just one mor question, we set that the only 1000 logs within 30 days are going to be stored. does that mean if we do truncate the database it will exclude the latest 1000 logs on 30 days?


Rafeeq's picture

Yes . Apart from those client logs SEPM does keep of few logs like DB transcation logs , Whatever goes in dB will have a log in sem5.log file thats why it grows

If you want to clearout all the logs manually .  there is a way a way for that too

Clearing log data from the database manually
ᗺrian's picture

I do know this was resolved in 12.1 RU1 MP1 so i don't believe this should be happening, even in newer versions. Yes, you can run the manual process to clear. I have a batch file that I used to do this in the past.

Wouldn't hurt to check with support though on why this is happening.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Mithun Sanghavi's picture


I would suggest you migrating to Symantec Endpoint Protection 12.1 RU2 OR the Latest version of Symantec Endpoint Protection 12.1.3001

Check these Articles:

Symantec Endpoint Protection Manager (SEPM) Database Transaction Log (sem5.log) Consumes Hard Drive Space in SEP SBE 12.1 RU1

Shrink the Symantec Endpoint Protection Manager 12.1 embedded database

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

Hope this helps!!

Mithun Sanghavi
Associate Security Architect


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