您的位置:首页 > 产品设计

symantec SEPM 12.1 db LOG 文件太大的解决办法

2015-07-20 11:51 375 查看
sqla000.tmp file is consuming hard drive spacehttp://www.symantec.com/business/support/index?page=content&id=TECH188303http://www.symantec.com/connect/forums/sem5log-keeps-growinghttp://www.symantec.com/connect/forums/sem5log-growing-huge-size

Problem

the sqla000.tmp file, found at \temp\sqla000.tmp is consuming several gigabytes of hard drive space.
ErrorNo error but the size of this file is larger than it should be and is consuming hard drive space. The sqla000.tmp file should typically be only about 200MB in size.
Environment
Windows Server 2008 R2, Symantec Endpoint Protection Manager 12.1 RU1 with an embedded database.CauseIt appears that a problem with the sem5.log is continually writing extra data to the \temp\sqla000.tmp file SolutionRebuild the sem5.log:Stop the Embedded Database service from services.msc
Note: If you did not install SEPM to the default location, change the paths below.Go to "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\" and rename sem5.log to sem5.log.old
(Use "Program Files (x86)" if the SEPM is on a 64-bit system)

Start a Command Prompt (cmd.exe) and
type:
CD C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\

Type the following & press Enter (again, use Program Files (x86) if on a 64-bit system)
dbsrv11 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db"

Start the Embedded Database service & restart the Symantec Endpoint Protection Manager service.
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: