HCL Notes and Domino 9.0 Social Edition Forum - question about compact and dbmt processes

~Dean Umkrother

Mar 21, 2013, 5:12 PM

74 Posts

Forwarded to development <>

compact/database: sw/ts

~Elizabeth Minfreelyjip

Mar 22, 2013, 7:06 PM

23 Posts

RE: question about compact and dbmt processes

Yes, you can use dbmt -force <n>, where n is the numerical day of the week (Sunday is 1). For example,

> load dbmt mail\db.nsf -force 6 (assuming today is Friday)

~Elizabeth Xantumiterikle

Mar 25, 2013, 7:23 PM

13 Posts

RE: question about compact and dbmt processes

Chad,

Thank you for your reply but I was actually asking if it possible to run the "dbmnt" command to compact a database which is always in use on an 8.5.3 server. I went through the Domino 9 documentation and didn't find an answer, hence the posting.

Currently I have to shut down the server and manually run the compact command to remove the white space from the database in question. I simply wanted to know if there are switches with the dbmnt command that I could use in a program document to avoid me taking down the server to do a compact process...

at 3:25 pm EST today I just ran compact from the server console and it compacted the databases without any problem ! I am a loss to explain why it didn't do this last week when I opened the ticket....

~Dexter Deswechekynds

Mar 25, 2013, 7:37 PM

191 Posts

My example should work for you

Part of the dbmt -force functionality will issue a drop of the database before compaction, so if the database is currently in use, this will free it and allow the compact to proceed. If you want to do this in a program document, you'd probably want a specific program document for that purpose, one day a week, and you'd set the force number to the day of the week on which you schedule the program document.

~Tanita Zeklutexakol

Apr 2, 2013, 8:27 PM

32 Posts

if all of the access is through the server process

that is remote access, dbmt should be able to compact it. Prior to the compact, dbmt will issue a drop <database>. If there are agents & add in programs running against the database, you should look into compact -replica which allows the database to be compacted while in use. When it comes time to rename the the database (it does a copy style compact) if the source database is still in use, it will cause the server to be bounced (which should be very quick) to get the rename to happen.

--Steve

~Evelyn Nonponeskioopsi

Mar 11, 2014, 9:20 AM

33 Posts

Solution

You can prevent access to the database needed to be compacted in serveral ways.

If it is a mail database stop the "Router task".

The "Agent manager" Task can be stopped too.

The "HTTP" task may also cause issues and can be stopped.

The Indexing tasks can be stopped too.

Make sure backup software isn't running, and that the virus scanner isn't doing a deep scan.

On the console use "drop all", or "drop user", or "drop path\database".

Make sure program documents are not configured to run at that time.

This can all be done using program documents or by hand.

This works very well.

Sincerely

Douglas Bryant

email@dbryant.de