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

Article:TECH178718  |  Created: 2012-01-11  |  Updated: 2012-04-27  |  Article URL http://www.symantec.com/docs/TECH178718
Article Type
Technical Solution


Issue



The Symantec Endpoint Protection 12.1 RU1 Small Business Edition database transaction log becomes excessively large. This file may grow to 20GB or more.


Error



The Windows Application Event Logs may contain SQLANY 11.0 errors containing the text:

Fatal error, disk full when writing to "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.log"

Windows System Event Log may contain the following:

[date] [time] Warning Srv SERVERNAME N/A 2013 The C: disk is at or near capacity.  You may need to delete some files.

 


Cause



SEP 12.1 with an Enterprise license has options to configure how often SEP can perform database maintenance.  SEP SBE is designed to perform this database maintenance as well, but on a fixed schedule that is not configurable within the user interface.  In SEP SBE 12.1 RU1, the transaction log does not seem to reduce in size.  In SEP SBE, there is also no Truncate Transaction Log Now button.  


Solution



This issue has been fixed in Symantec Endpoint Protection 12 Release Update 1 (RU1) Maintenance Patch 1 (MP1).  For information on how to obtain the latest build of Symantec Endpoint Protection, read TECH 103088: Obtaining an upgrade or update for Symantec Endpoint Protection or Symantec Network Access Control.

Alternately, the following manual process is recommended to be performed as needed:

1) Stop the Symantec Endpoint Protection Manager and Symantec Embedded Database services.
2) Rename or delete the current sem5.log
3) Click Start Run and type CMD then click OK
4) In the Command Prompt type:
    For 32-bit: CD C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\
    For 64-bit: CD C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\ASA\win32\
5) Press Enter. This will change directories to the folder containing dbsrv11.exe.
6) To force the recreation of sem5.log, type:
    For 32-bit: dbsrv11 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db"      (There is a space after -f and "C:\...)
    For 64-bit: dbsrv11 -f "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db"     (There is a space after -f and "C:\...)
7) Press Enter
8) Click Start > Run and type services.msc then click OK
9) Start the Symantec Endpoint Protection Manager and Symantec Embedded Database services.


Supplemental Materials

SourceETrack
Value2660649



Article URL http://www.symantec.com/docs/TECH178718


Terms of use for this information are found in Legal Notices