Endpoint Protection

 View Only
Expand all | Collapse all

Symantec Embedded database can not be restarted

Migration User

Migration UserJan 21, 2013 03:26 AM

  • 1.  Symantec Embedded database can not be restarted

    Posted Jan 17, 2013 10:49 PM

    Hi all,

    When restarting Symantec Embedded database, it takes too long to stop the db service. After a while I get the report that the service can not be stopped. The status of Symantec Embedded database in services.msc hang at stopping. 

    When checking the err.log in SEPM\db folder I get this information:

     

    *** ERROR *** Assertion failed: 201847 (9.0.2.3654)
    Checkpoint log: write to H:\Symantec Manager\db\sem5.db failed with status 112: filesystem may be full or file size has exceeded system limits
     
    Can not do anything with it, must restart the server. We use SEPM 11.0.7101, Win server 2003 Std x86. The size of sem5.db in SEPM\db\ folder comes up to 7,064,096 KB.
    Have anybody faced this problem before? 
     
    Thank you all for your answer and suggestion!
     
    Regards,
    Nguyen Cao


  • 2.  RE: Symantec Embedded database can not be restarted

    Posted Jan 17, 2013 10:57 PM

    HI,

    How much disk space available in Drive ?

    Try to Shrink database

    https://www-secure.symantec.com/connect/downloads/shrink-symantec-endpoint-protection-manager-121-embedded-database



  • 3.  RE: Symantec Embedded database can not be restarted

    Posted Jan 18, 2013 12:01 AM

    Hi Ashish,

    Our SEPM drive has about 5.6GB free space.

    Thank you for the tool, I will try to shrink the DB and check the performance again.



  • 4.  RE: Symantec Embedded database can not be restarted

    Posted Jan 18, 2013 01:53 AM

    One more question Ashish: Do I need to stop Symantec Embedded Database before shrinking?



  • 5.  RE: Symantec Embedded database can not be restarted

    Posted Jan 18, 2013 02:11 AM

    HI,

    Yes you need to start the Embedded Database but your case your service are stopped ..

     

    Do you have configure any Disk Quote in System drive ?

     

    May be you can follow this artical

     

    Symantec Endpoint Protection 11.x: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

    Article:TECH102333  |  Created: 2007-01-21  |  Updated: 2011-11-09  |  Article URL http://www.symantec.com/docs/TECH102333
     

     



  • 6.  RE: Symantec Embedded database can not be restarted

    Posted Jan 18, 2013 02:28 AM

    Hi Ashish,

    I do not configure any disk quota in System drive.

    I manage to start the Symantec Embedded database and currently running the database shrinking now but it seems to take very long time (the screenshot I took 30 minutes after running ShrinkEmbeddedDB.bat).



  • 7.  RE: Symantec Embedded database can not be restarted

    Posted Jan 18, 2013 02:30 AM

    Hi,

    Yes it's take time you can wait untill it's not finish and after check how much disk space free



  • 8.  RE: Symantec Embedded database can not be restarted

    Posted Jan 18, 2013 03:04 AM

    "Our SEPM drive has about 5.6GB free space" - is this the same drive we are talking about as in the error you have mentioned?:

    Checkpoint log: write to H:\Symantec Manager\db\sem5.db failed with status 112: filesystem may be full or file size has exceeded system limits

     

    Is this a virtual machine? Any chances of increasing the size of teh drive by other means?



  • 9.  RE: Symantec Embedded database can not be restarted

    Posted Jan 18, 2013 05:22 AM

    Thanks Ashish,

    I will try to run database shrinking once again.

    Do you have any solution if shrink tool can not help?

     

    @ Sebastian,

    Yes the machine is virtual machine. The drive is the same, we only use drive H for SEPM and free space size is 5.6GB

    I have tried to shrink database one time but nothing change after 3 hours so I stopped the shrink process, try to reboot the server, free some disk space and try to run database shrink tool once again.

    Anything new will be updated here.

     

    Cheers,

    Nguyen Cao



  • 10.  RE: Symantec Embedded database can not be restarted

    Posted Jan 18, 2013 05:50 AM

    I know this is a bit of a silly question, but given the specific error message you're receiving, can you confirm what filesystem your H: drive is using?

    The error message seems to suggest it might not be using NTFS...



  • 11.  RE: Symantec Embedded database can not be restarted
    Best Answer

    Posted Jan 18, 2013 06:31 AM

    Oh yeah, and ShrinkEmbeddedDB.bat is for SEP12.1, for v11.* SEPM's you're meant to use dbunload:

    http://www.symantec.com/docs/TECH104278



  • 12.  RE: Symantec Embedded database can not be restarted

    Posted Jan 21, 2013 03:26 AM

    Hi

    Please try to repair SEPM.

    Regards



  • 13.  RE: Symantec Embedded database can not be restarted

    Posted Jan 21, 2013 04:20 AM

    Thank all,

    I'll try one more time with dbunload.

    Regards,

    Nguyen Cao



  • 14.  RE: Symantec Embedded database can not be restarted

    Posted Jan 21, 2013 04:30 AM

    Did you see my first post?  Like I said, it's a bit silly but can you confirm what filesystem your H:\ drive is using?



  • 15.  RE: Symantec Embedded database can not be restarted

    Posted Jan 21, 2013 06:19 AM

    Hi,

    The File system in H drive is NTFS, just like you guess.



  • 16.  RE: Symantec Embedded database can not be restarted

    Posted Jan 21, 2013 06:59 AM

    Oh!  I was actually wondering if it might be using a different filesystem as the error message indicates the sem5.db file has reached the limits of the filesystem.

    Does the out.log file provide any other information?



  • 17.  RE: Symantec Embedded database can not be restarted

    Posted Jan 21, 2013 09:03 PM

    Hi,

    Thank you for your answer, I guess that you think the file system in H: is FAT32 or something. But with FAT32 the file size can not come up to nearly 7GB (it will be around 4GB).

    Anyway,

    I tried to clear H drive and then run dbunload again. It worked, now my sem5.db reduce to 4.5GB. I can stop and start Symantec Embedded Database properly.

    Thank you all and have a nice day guys!

     

    Regards,

    Nguyen Cao