SEP12.1 RU1- Assertion failed: 200114[sem5] (11.0.1.2472)

[DCSEPadmin]

URGh. I got this Assertion failed: 200114[sem5] (11.0.1.2472)  this morning. It happened at midnight. Server has 10GB of free space.I hide the real IP and name below. What is really frustrating is Enterprise support for a critical ticket says to DR the server which I don't think I really need to do. I hear this happens all the time.

Isn't there an easy way to fix this database?

Below is my Out.log

I. 12/15 00:00:46. Starting checkpoint of "sem5" (sem5.db) at Thu Dec 15 2011 00:00
I. 12/15 00:00:46. Finished checkpoint of "sem5" (sem5.db) at Thu Dec 15 2011 00:00
I. 12/15 00:00:46. Starting checkpoint of "sem5" (sem5.db) at Thu Dec 15 2011 00:00
I. 12/15 00:00:46. Finished checkpoint of "sem5" (sem5.db) at Thu Dec 15 2011 00:00
E. 12/15 00:01:00. *** ERROR *** Assertion failed: 200114[sem5] (11.0.1.2472)
Can't find values for row 54c:11 in index 'I_SEM_COMPLIANCE_LOG_IDX_PLUS'
I. 12/15 00:01:00. Connection terminated abnormally
I. 12/15 00:01:00. Disconnected TCPIP client's AppInfo: IP=IPCHANGED;HOST=NAMECHANGED;OSUSER=SYSTEM;OS='Windows 2003 Build 3790 Service Pack 2';EXE='C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\bin\SemSvc.exe';PID=0xe98;THREAD=0x1a3c;VERSION=11.0.1.2472;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-300
I. 12/15 00:01:00. Database server shutdown requested via server console
I. 12/15 05:54:22. SQL Anywhere Network Server Version 11.0.1.2472

I. 12/15 05:54:22. OEM Authenticated Edition, licensed only for use with authenticated OEM applications.
I. 12/15 05:54:22.

I. 12/15 05:54:22. Copyright © 2001-2009, iAnywhere Solutions, Inc.
I. 12/15 05:54:22. Portions copyright © 1988-2009, Sybase, Inc. All rights reserved.
I. 12/15 05:54:22. Use of this software is governed by the Sybase License Agreement. Refer to http://www.sybase.com/softwarelicenses
I. 12/15 05:54:22.

I. 12/15 05:54:22. 4 logical processor(s) on 2 physical processor(s) detected.
I. 12/15 05:54:22. Processor limit (licensed processors): 16
I. 12/15 05:54:22. Maximum number of physical processors the server will use: 2
I. 12/15 05:54:22. This server is licensed to:
I. 12/15 05:54:22.     Symantec
I. 12/15 05:54:22.     Symantec
I. 12/15 05:54:22. Running Windows 2003 Build 3790 Service Pack 2 on X86_64
I. 12/15 05:54:22. Server built for X86 processor architecture
I. 12/15 05:54:22. 131072K of memory used for caching
I. 12/15 05:54:22. Minimum cache size: 131072K, maximum cache size: 1048576K
I. 12/15 05:54:22. Using a maximum page size of 8192 bytes
I. 12/15 05:54:22. Starting database "sem5" (C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db) at Thu Dec 15 2011 05:54
I. 12/15 05:54:22. Performance warning: Database file "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" consists of 5 disk fragments
I. 12/15 05:54:22. Note: The size of 'C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db' is larger than expected
I. 12/15 05:54:22. Database recovery in progress
I. 12/15 05:54:22.     Last checkpoint at Thu Dec 15 2011 00:00
I. 12/15 05:54:22.     Checkpoint log...
I. 12/15 05:54:25.     Transaction log: sem5.log...
I. 12/15 05:54:36.     Rollback log...
I. 12/15 05:54:36.     Checkpointing...
I. 12/15 05:54:36. Starting checkpoint of "sem5" (sem5.db) at Thu Dec 15 2011 05:54
I. 12/15 05:54:36. Finished checkpoint of "sem5" (sem5.db) at Thu Dec 15 2011 05:54
I. 12/15 05:54:36. Recovery complete
I. 12/15 05:54:37. Database "sem5" (sem5.db) started at Thu Dec 15 2011 05:54
I. 12/15 05:54:37. This database is licensed for use with:
I. 12/15 05:54:37.     Application: Symantec Endpoint Protection Manager
I. 12/15 05:54:37.     Company: Symantec Corp
I. 12/15 05:54:37. Database server started at Thu Dec 15 2011 05:54
I. 12/15 05:54:37. Trying to start SharedMemory link ...
I. 12/15 05:54:37.     SharedMemory link started successfully
I. 12/15 05:54:37. Trying to start TCPIP link ...
I. 12/15 05:54:37. Starting on port 2638
I. 12/15 05:54:37.     TCPIP link started successfully
I. 12/15 05:54:37. Now accepting requests
E. 12/15 05:54:40. *** ERROR *** Assertion failed: 200114[sem5] (11.0.1.2472)
Can't find values for row 54c:11 in index 'I_SEM_COMPLIANCE_LOG_IDX_PLUS'
I. 12/15 05:55:15. Database server shutdown requested via server console

My err.log

12/15 00:01:00. *** ERROR *** Assertion failed: 200114[sem5] (11.0.1.2472)
Can't find values for row 54c:11 in index 'I_SEM_COMPLIANCE_LOG_IDX_PLUS'
12/15 05:54:40. *** ERROR *** Assertion failed: 200114[sem5] (11.0.1.2472)
Can't find values for row 54c:11 in index 'I_SEM_COMPLIANCE_LOG_IDX_PLUS'
12/15 07:24:20. *** ERROR *** Assertion failed: 200114[sem5] (11.0.1.2472)
Can't find values for row 54c:11 in index 'I_SEM_COMPLIANCE_LOG_IDX_PLUS'

and so forth.

 Thanks for any help! I need it.  

[Mithun Sanghavi]

Hello,

The sem5.log may be corrupted. 

Perform a disaster recovery:

Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

Again, Check this Article

Symantec Endpoint Protection Manager 12.1 sends an email notification indicating an Embedded Database Error.

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

 

 

Hope that helps!!

[DCSEPadmin]

Thanks! That looks like the exact problem. I will try it a later today.

[DCSEPadmin]

I'm hoping support can review this http://www.sybase.com/detail?id=1039329

and recover this. I have complex groups, policies, hardware restrictions and really can't afford to redo everything. Perhaps there is a sybase master at symantec!? Ive found some others with this problem online and I dont think redoing an enterprise server solution every time there is a database problem really a solution. It reminds me of windows 10 years ago. I had no idea this was the best the embedded database could do. I wish Symantec would have pushed in the literature to use MSSQL if they can support that better.

[Mithun Sanghavi]

Hello,

I understand your point.

However, I would suggest you to create a case with Symantec Technical Support. 

(You can even PM me the Case #. Let me see if something could be done.)

 

You can log a case on web portal :

QuickStart Guide - Create and Manage Support Cases in SymWISE

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

How to update a support case and upload diagnostic files with MySupport

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

Hope that helps!!

[DCSEPadmin]

I ended up going back to 11.7 through the DR procedure. I will then go to 11.7 MP1 and then 12.1Ru1.

[Mithun Sanghavi]

Hello,

I appreciate you updating the Symantec Forums and this Thread on the same.