Endpoint Protection

 View Only
  • 1.  cannot start sem5 database

    Posted Sep 20, 2011 04:42 AM

    anyone seen this... 

    i cannot start the symnatec embedded database, each time i start the service it it stops i get the follwoing erros in the log..

     

    I. 09/20 10:18:07. Starting database "sem5" (D:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db) at Tue Sep 20 2011 10:18
    I. 09/20 10:18:07. Database recovery in progress
    I. 09/20 10:18:07.     Last checkpoint at Fri Sep 16 2011 14:57
    I. 09/20 10:18:07.     Checkpoint log...
    I. 09/20 10:18:07. Performance warning: Database file "D:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" consists of 13147 disk fragments
    I. 09/20 10:18:18.     Transaction log: sem5.log...
    E. 09/20 10:18:19. *** ERROR *** Assertion failed: 100904 (9.0.2.3654)
    E. 09/20 10:18:19. Failed to redo a database operation (id=1, page_no=0xd000006a, offset=0x513) - Error: Primary key for table 'SEM_CONTENT' is not unique
    I. 09/20 10:18:19. *** ERROR *** Assertion failed: 100904 (9.0.2.3654)
    I. 09/20 10:18:19. Failed to redo a database operation (id=1, page_no=0xd000006a, offset=0x513) - Error: Primary key for table 'SEM_CONTENT' is not unique
    I. 09/20 10:18:19.
    I. 09/20 10:18:19. Attempting to save dump file at 'C:\WINDOWS\TEMP\sa_dump.dmp'
    I. 09/20 10:18:19. Dump file saved
    E. 09/20 10:18:19. Internal database error *** ERROR *** Assertion failed: 100904 (9.0.2.3654)
    E. 09/20 10:18:19. Failed to redo a database operation (id=1, page_no=0xd000006a, offset=0x513) - Error: Primary key for table 'SEM_CONTENT' is not unique -- transaction rolled back 

     

    I have tried a windows defrag...  but it wont defrag the datbase file so i nsuspect i need to do something else.

     

    has anyone got any idea before i rebuild the AV server

     

    kev
     



  • 2.  RE: cannot start sem5 database

    Broadcom Employee
    Posted Sep 20, 2011 05:55 AM

    from the sybase error list

    'Assertion 100904: Failed to redo a database operation' is generated when
    the server fails to recover the database based on information stored in the
    transaction log.  This assertion never included the actual reason for the
    recovery failure. The actual error message is now included in the assertion
    message. In many cases the cause of the recovery failure was failure to find
    a data file that was used in a LOAD TABLE statement. In cases where the data
    file had been deleted recovery could not continue. The fact that the file
    is missing is now incorporated into the assertion message.
     

    http://forums.sybase.com/cgi-bin/webnews.cgi/readme-9.0.2.3302-9.0.2.3643.html?cmd=itempart-120043&part=2&group=sybase.public.sqlanywhere.general&utoken=b58.4a083670.1804289383@temp:0_~2-260eeaad1916e89f05e700/readme-9.0.2.3302-9.0.2.3643.html

     

    reconfigure the SEPM using the management server configuration wizard.



  • 3.  RE: cannot start sem5 database
    Best Answer

    Broadcom Employee
    Posted Sep 20, 2011 06:12 AM

    Hi,

    The following steps have been shown to resolve this issue. Note that these steps assume the default installation directories for the SEPM:

    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: C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32
    4. Issue the following command: dbsrv11 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db
    5. Start the Symantec Embedded Database service through the service control manager (services.msc). 

    Check this article

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