Being a pioneer of Symantec Endpoint 11 I found myself with a pretty uncomfortable situation. In front of some of disproportionate size (even 7Gb for less than 10 clients) database I decided to get to the bottom. The discovery comes after a careful search in the KB Symantec. All installations for Version 11 MR2 suffered from this flaw. The database size grew like a madman. The arrival of the MR2 solves the problem. But more than solving it, avoid it. Indeed if it is true that the database does not will undergo further increases, it is also true that if we do not bother to maintain it definitely alone will not fit in its correct dimensions. THE Rel. 11 MR2 is equipped with a new tool called Dbunload that serves this purpose. The tool must be launched from the command line, and deals with the re-compacting the database and its decrease in size. For practicality riporto contents KB (TECH104278)  Official Symantec
Problem You notice that the embedded database grows overly large. You want to use the Dbunload.exe tool to shrink it.
Solution The Dbunload tool is provided with Symantec Endpoint Protection 11.0.2 (Maintenance Release 2). To obtain Maintenance Release 2, read the document . Note: The problem that causes the embedded database to grow overly large is solved in Maintenance Release 2, but migrating to Maintenance Release 2 does not shrink the database automatically. To shrink the database, you must use the Dbunload tool. To use the Dbunload tool on 32-bit Operating Systems Ensure that you have available free drive space equal to 1.5 to two times the size of the database. Using the Database Back Up and Restore wizard, make a backup copy of the following file:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db Stop the following services: Symantec Endpoint Protection Manager Symantec Embedded Database Start the service Symantec Embedded Database. Click Start > Run, type CMD, click OK, and then type the following two lines at the prompt:cd \Program Files\Symantec\Symantec EndpointProtection Manager\ASA\win32 dbunload -c "uid=dba;pwd=password_set_during_install" -ar Note: If you get the following result: ***** SQL error: Specified database file already in use Stop the Symantec Embedded Database Service and run the command again. Note: If you get the following result: ***** SQL error: Database server not found Run the following command : dbunload -c "dbf=C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db;start=dbsrv9;uid=dba;pwd=password_set_during_install" -ar To use the Dbunload tool on 64-bit Operating Systems On 64-bit Operating systems, the path should be changed accordingly, and only the dbunload command that specifies the full path to the sem5.db database will work.The procedure and commands would look something like this: 1   Stop the following services:Symantec Endpoint Protection Manager Symantec Embedded Database2.  Click Start > Run, type CMD, click OK, and then type the following two lines at the prompt: cd \ProgramFiles (x86)\Symantec\Symantec Endpoint Protection Manager\ASA\win32 dbunload -c "dbf=C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db;start=dbsrv9;uid=dba;pwd=password_set_during_install" -ar Note: If you get the following result: ***** SQL error: Specified database file already in use Stop the Symantec Embedded Database Service and run the command again The time to reduce the size of the database will depend on several factors, including, but not limited to: available drive space, amount of memory, speed of the processor, size of the database, and other server and background functions running on the target system at the time of dbunload being used. Note: “password_set_during_install” is the password you supplied while installing Symantec Endpoint Protection Manager initially. Once the dbunload process has finished, you can: Restart the service Symantec Embedded Database. Start the service Symantec Endpoint Protection Manager. References “AccessingMaintenance Release 2 for Symantec Endpoint Protection 11.0” at:
Share: