Video Screencast Help

SEPM Database Getting Down due to the size of DB

Created: 10 Apr 2014 | 11 comments

Hello Support,

 

We have Symantec Endpoint Protection manager installed on windows server 2003 and couple of Months back I have upgraded from 12.1.3 SEP manager to 12.1.4 Manager and updated the client versions too.

From Some days every three to four gap the Database goes down and Symantec Embedded Database service will stop and if we try to manually start then it will not start again.

After reading some where in support forum i have tried to shringk the database but shrink will stop at 10%.

Some where in forum mentioned like this

::::

1) Navigate to C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\ within Windows Explorer.

2) Locate the sem5.log and rename it to sem5.log.old

3) Open a command prompt  and navigate to the following location: cd d:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32

4) Issue the following command: dbsrv12 -f "d:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db

5) Start the Symantec Embedded Database service through the service control manager (services.msc).

Symantec need to create some Fix to solve this. ATM I try to install SEM again and save the DB to SQL Express. Then Restore my DB Backup to SQL Express.

::::

After doing this the database service will work for some hours like 2 to 3 hours then again same issue.

 

sem5.db Database size is 4.52 GB and sem5.log will go upto 400 + Mb in some minute then the database stopped suddenly.

 

Operating Systems:

Comments 11 CommentsJump to latest comment

Rafeeq's picture

how many clients you have in your network? whats the  number of content revison stored in liveudpate?

SameerU's picture

Hi

Do you have SQL maintainence configure

Esle what is the size alloted in SQL for storing the logs

Regards

James007's picture

How many content revisions do you have set ?

Disk Space Management procedures for the Symantec Endpoint Protection Manager

Article:TECH96214 | Created: 2009-01-17 | Updated: 2014-01-03 | Article URL http://www.symantec.com/docs/TECH96214

Best Practices for configuring the number of content revisions to keep in Symantec Endpoint Protection Manager

Article:TECH92225 | Created: 2009-01-05 | Updated: 2013-11-05 | Article URL http://www.symantec.com/docs/TECH92225
Peer Basha's picture

@ Rafeeq

How many clients you have in your network? whats the  number of content revison stored in liveudpate?

We have nearly 50 clients.

Peer Basha's picture

@ Hello Cooldude

 

What is the available space in your drive?

Nearly 400 GB left in drive

Rafeeq's picture

run the Db validator which is found in the tools folder.

cooldude's picture

When you try to start the DB service it reflect any error?

Check the attach thread comment

https://www-secure.symantec.com/connect/forums/sym...

James007's picture

If above Solution does nt work you can rasied Support ticket.

How to create a new case in MySymantec

http://www.symantec.com/business/support/index?page=content&id=TECH58873

Phone numbers to contact Tech Support:-

Regional Support Telephone Numbers:

  • United States: 800-342-0652 (407-357-7600 from outside the United States)
  • Australia: 1300 365510 (+61 2 8220 7111 from outside Australia)
  • United Kingdom: +44 (0) 870 606 6000

Additional contact numbers:http://www.symantec.com/business/support/contact_techsupp_static.jsp

SMLatCST's picture

I've noticed that some forum members post the steps to recreate the Transaction Log (the steps you posted in the OP) without proper warning as to the consequences, and without any prior troubleshooting either.

This should really stop.  Recreating the transaction log will result in loss of data!  You must accept this risk, and preferably make an attempt at troubleshooting first, before recreating it.

As it's not solved your issue, and as you have plenty of space on the disk, I'd recommend either logging a support case with Symantec, or taking a look at the err.log or out.log files (these will be in the same folder as the embedded DB) and revewing these for errors.

.Brian's picture

Great post and very true yes

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.