ok thanks... only thing I can think of is did you change the port for the DB?

I'll take a look at dbunload and see if I can get a better understanding

and this is an upgrade from RTM --> MR1 --> MP1 --> MR2 or something different?

Hi, the command is as follows -

dbunload -c "dbf=<%SEPM_Installation_Folder%>\db\sem5.db;start=dbsrv9;uid=dba;pwd=<password>" -ar

all in a single line.....give the appropriate path to the SEPM installation folder where its mentioned, and the password would be the password used for logging into the SEPM console

<Please note here that in case you have changed the admin password since the first time you logged in, the original admin login password would be the one that you need to type here for the command to be successful>

Also note that this take time from anywhere between 5 minutes to an hour depending on the Database size. Additionally, for example, if the DB size is 2 GB, there should be 2 GB or more free space on the drive where the SEPM is installed, since the tool first unpacks the DB, and then cleans it up to a more presentable size

Do let us know if this is helpful.

Abhishek, your suggestion works with both Manager and Database services stopped. Thank you.

You must stop the Database service.

No Problem. Anytime.....

:smileyvery-happy:

Hi, anyonw can post their space savings after doing this procedure?

Thanks
Oliver

We just went from ~3.5GB to slightly under 1GB running about 75 clients.

Is dbunload only available for MR2 installations?  If we're running MR1 and our database size is getting out of hand, do I *HAVE* to upgrade to MR2 to use this utility to compact it?

My current sem5.db size is about 12GB and growing, with about 225 clients... and I've already lowered much of the data retention dates from the defaults to 5-7 days.

we only provide dbunload on the MR2 CD (its part of the SEPM install)... you may be able to contact support and get a copy - alternatively there is the free to download developer version of Sybase ASA9 which has a full admin console and dbunload included.

I ran dbunload -c "dbf=C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db;start=dbsrv9;uid=dba;pwd=XXXXXXXX" -ar  with the database service stopped and it worked perfeclty. Thanks!

@ oliversl db went from 8.97gb to 1.94gb

Message Edited by jrudacille on 05-09-2008 07:37 AM

Message Edited by jrudacille on 05-12-2008 05:06 AM

HI,

I've upgraded to SEP 11.0.2000.

I try dbunload, it steel working but when the job stop, my database has the same size (about 8Go with 50users).

Please have you got a tip to decrease the size?

Best regards,

Siegfried

Hi,

I retry this morning.
The database doesn't decrease, it takes 7.9 GB on my server.

I've resolved login/logoff problems on my Citrix servers when i roll back to NAV 10.1.5 (unmanaged).

I'm thinking of revert all of servers (7 servers and 90 computers) and computers with this version.

It takes too much time for me to administer SEPM.

Regards.

Hi,

My database grew up to 8.1Go today ... please help me!

Why it didn't decrease with dbunload?

Thanks a lot.

Siegfried

HI,

Today database size is 8.2 Go ...

Have a good day.

I've just open a ticket ...

Message Edited by Siegfried on 06-04-2008 11:22 PM

My 19GB and growing db (220 clients) did not shrink after going through the dbload process.  It ran through successfully, but the resulting database was the same size it started out as.... I'm running MR2.

Hi,

If you have upgraded from an older version to MR2, the hotline said i have to uninstall SEPM (just the console), delete the database and reinstall with MR2.
After that, you have to reconfigure you client with a script to change the sylink.xml file.

My Db was 8.6 Go large and now it is 0.6 Go.

Sorry for my english today, i had a bad night .... and cofee isn't in my veins :-)

This could be bad advice, please consider carefully before proceeding at your own risk, but it did work for me without any noticeable problems. 

I was able to shrink my database with dbunload eventually.... note I don't know the consequences of doing this but for me, there appeared to be no immediately noticeable side effects.

* Backup your database first *

1) I used dbisqlc.exe to connect to my sem5 database.

2) I ran "select count(*) as thecount from binary_file where deleted=1;" it resulted in approx 1500 records, however running "select count(*) as thecount from binary_file where deleted=0" resulted in 24....   this appeared to be cause of my large database.... whether or not this is normal I don't know.

3) So, next I ran "delete from binary_file where deleted=1;" to get rid of these 1500 massive records.

4) Then I re-ran dbunload as suggested many times in this thread...

My database went from nearly 20Gb down to 500Mb.... but is slow growing once again.   Hopefully it will plateau at a reasonable size.

Again, I don't know the side effects of clearing out the binary_file table manually like this, you are doing this at your own risk.

Message Edited by grant604 on 06-19-2008 01:19 PM

I'm curious, if I just deleted my all SEP client install packages, then in SEPM, would the list of packages under Admin -> Install Packages be empty?  

Because on my SEPM, both MR1 and MR2 packages are still listed there, and I know that I'm able to use the MR2 one to upgrade portions of my network still.... so it still appears to be working normally.

Basically, I'm trying to figure out what (if any) are the consquences of what I did are, and I can't seem to find anything that has been affected.

Knottyropes wrote:

Grant:

 

 read page 68 it will explain it some.

Basically you just deleted your SEP client install packages

 

 

https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&thread.id=7034&view=by_date_ascending&page=7

C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32> dbunload -c "dbf=<%full path to%>\sem5.db;start=dbsrv9;uid=DBA;pwd=<%passwd%>" -ar
w/ both "Symantec Endpoint Protection Manager" and "Symantec Embedded database services" stop

it took 10 minutes or so and sem5.db became 23,235,496KB -> 1,224,208KB

perfect for us, thank you all.

Message Edited by jrudacille on 06-26-2008 12:02 PM

I have just taken over the IT department. I have had several issues with SEP 11 I have manged to migrate all our end user to the new MR2 version. I have noticed that the sem5.bd is 4.5GB i have tried using the below script to truncate the database, to which is fails on ***** SQL error: Invalid user ID or password I have spoken to the 3rd party that installed endpoint, is there any way to get around this password issue rather than a fresh install?

Also the C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\content is up to 40gb can this be truncated as well?

SEP Manager upgraded from 11.0.1000 to 11.0.2000

dbunload shrink sem5.db from 20GB to 21GB :smileysurprised:

PLEAS HELP!

second pass

dbunload shrink sem5.db from 21GB to 21GB

is it posible to reinstall SEP Manager without lost of client database (but with deleting sem5.db)?

I've followed these steps but my database keeps growing.  I only have ~ 40 users and I am up to 18GB now!

Does anyone know if swapping to a MSSQL database will help at all?  I can't imagine what is taking up so much room...

I was reading this topic, because I have a problem regadering de sem5.db-file.
I tried the dbunload-tool to shrink the database from the huge size of 45 GB.
After running dbunload the database hasn't shrunk a bit.

I tried de dbvalidator-tool to check the dabase, this check told me that several links for LuDownloadPackage are wrong.

Following file explains it: mail.n-tree.nl/download/sep11/dbvalidator.log

Can somebody explain the problem?

I can't believe this! I was using kbase article: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008022616103648 to try and shrink a 1.2GB database for 400 clients in  a test VM system :)  MR4 MP1a - whatever the latest build is that's supposed to work OK

It's not precise!! THe article is just plain wrong in three places of precedure of starting/stopping services..

You have to start database access to do the backup then stop it to do the dbunload -- it's totally wrong but easy to fix!! Why dont Symantec do this - they are a largeish computer company and probably have people that can edit the kbase files so they are accurate, and then test them a few times to ensure accuracy.
 
I am sure that I am not the only person to find this particular article wrong, and then have to resort to using this confusing "forum" system to find a solution.   

Why do Symantec leave inaccurate kbase articles in the wild?

Better yet - why not fix this POS EndPoint product and all it's crazy 1980's add-in database systems and whacko webserver plugins once and for all??? 

You just about have to be a db-admin to manage this SEP product!   The fact I wasted another 15 minutes on typing this instead of is purely due to the fact  I am testing this latest MR4 MP1a *working* version "one last time" before  I contemplate migrating my last few thousand desktops over to S0ph0s. - Looks like the migration will go ahead!

I'm urgently looking for a solution to get my sem5.db file smaller.  This is the embedded database of SEP 11 MR4.  I had some troubles to get the disk space larger but now I'm at the point that this SEP Management server must replicate with our other affiliate.  With a 20 GB size in the database, this is almost impossible over our communication line.
So I was looking for a way to get it smaller.
I used the DBunload tool but after running 10 hours, the new size was still 20 GB.  I don't understand why this database needs to be so big.
Does anybody have another suggestion to get the database smaller ?

Stop both "Symantec Endpoint Manager Service and Symantec Embedded Database Service"

Check your path to dbunload.exe is the same as below and the path to your sem5.db is the same
If they are not substitute your paths for the ones below.

NOTE! make sure the quotes are in the right place as shown below and replace YourDatabasePassword with your own password used when installing the database.

Make sure you have at least 1.5 times the size of your database in free disk space.

Place this command line in a batch file and ensure its just one line.

Depending on the size of the database it can take mins to hours to run, sometimes it looks like it has hung, if you check tasks you will see db9serv.exe using some cpu, if its not using any cpu at all then its probably hung, seek advice from Support.

Once its finished don't forget to start the 2 services you stopped at the beginning.
"C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\dbunload.exe" -c "dbf=C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db;start=dbsrv9;uid=dba;pwd=YourDatabasePassword" -ar
All the Best

hello
i have try Abhishek advice it work
but the problem is that the SEM5.db almost fill my hard drive space
now the space just remain 400 MB
the sem5.db is 60 GB
if i run dbunload it still need space to create the sem5.dbR and sem5.LogR file

is there a way to redirect the  .dbr and .logr file to another harddrive??