.....be sure to use the -J option.

Transaction logging is good for servers. It's like your parents telling you to eat more fiber, you don't ask why just know that it is. However if you run fixup on database that is transaction logged then it will not actually do anything to that database.

Unless you run it like this that is:

load fixup -F -J dbname

Darren Duke   |   August 27 2012 09:46:45 AM   |    lotus notes    |  
  |   Next Document   |   Previous Document

Discussion for this entry is now closed.

Comments (5)

Gravatar Image
1 - David Schaffer    http://davidschaffer.us    08/27/2012 2:08:14 PM

I've got servers with a weekly program document for "fixup -f -v -l". Probably been that way since R7. Never changed when we added transaction logging and DAOS.

OK to just add -J?

Gravatar Image
2 - ML       08/28/2012 1:39:56 AM

load fixup [database] -J

Runs fixup against databases that have transaction logging enabled. If this parameter isn't used, fixup doesn't check these databases.

Gravatar Image
3 - Darren Duke    http://blog.darrenduke.net    08/29/2012 7:33:03 AM

It may affect you if you use Archived Transaction Logging, so make sure to do a full NSF backup after fixup if you are using archived mode. Otherwise there is no issue other than you are running fixup for the first time in years ;)

Gravatar Image
4 - Ben Rose       09/10/2012 4:01:17 AM


If using transactional logging, you should disable all scheduled fixup tasks. They aren't required.

Gravatar Image
5 - Rodney Loureiro       04/10/2013 4:04:39 PM

About the subject, I have two questions. The transaction loggin file is necessarily a nsf file, or can be a simple data directory? And in case of the directory, how I set the fixup command?