DATABASE MANAGEMENT


Fixup options
The following table describes the options you can use with Fixup. The first column lists the options as they appear when you run Fixup using the Fixup tool or the Task - Start tool in the IBM® Lotus® Domino™ Administrator. The second column lists the equivalent command-line options that you use when you run Fixup using a console command or using a Program document.
Fixup options in Fixup tool and Task - Start toolCommand-line equivalentDescription
  • Fixup all databases
  • Fixup only this database or folder
databasepath"Fixup only this database or folder" runs Fixup only on a specified database or all databases in a specified folder. To run Fixup on a database in the Domino data folder, enter the file name, for example SALES.NSF. To run Fixup on a database or databases in folders within the data folder, enter the path relative to the data folder. For example, to run Fixup on all databases in the DATA\SALES folder, specify SALES.

"Fixup all databases" or no command line database path runs Fixup on all databases on the server.

Note To specify databases or folders to run on using the Fixup tool, select the database(s) or folder(s).

Report all processed databases to log file-LReports to the log file every database that Fixup opens and checks for corruption. Without this argument, Fixup logs only actual problems encountered.
Scan only since last fixup-IWhen you run Fixup on a specific database, Fixup checks only documents modified since Fixup last ran. Without this option, Fixup checks all documents.
Scan all documents-FWhen you run Fixup on all databases, Fixup checks all documents in the databases. Without this option, Fixup checks only documents modified since it last ran.

Note To specify this option using the Fixup tool, deselect "Scan only since last fixup."

Perform quick fixup-QChecks documents more quickly but less thoroughly. Without this option, Fixup checks documents thoroughly.
Exclude views (faster)-VPrevents Fixup from running on views. This option reduces the time it takes Fixup to run. Use if view corruption isn't a problem.
Don't purge corrupted documents-NPrevents Fixup from purging corrupted documents so that the next time Fixup runs or the next time a user opens the database, Fixup must check the database again. Use this option to salvage data in documents if the corruption is minor or if there are no replicas of the database.
Optimize user unread lists-UReverts ID tables in a database to the previous release format. Don't select this option unless Customer Support recommends doing so.
Fixup transaction-logged databases-JRuns on databases that are enabled for transaction logging. Without this option, Fixup generally doesn't run on logged databases.

If you are using a certified backup utility, it's important that you schedule a full backup of the database as soon after Fixup finishes as possible.

Fixup open databases-OIf you run Fixup on open databases, Fixup takes the databases offline to perform the fixup.

This is the default if you run Fixup and specify a database name. Without this option, when you do not specify database names, Fixup does not run on open databases.

Don't fixup open databases-ZApplies only to running Fixup on a single database. When a database isn't taken offline and is in use, then Fixup is not run.

This is the default when Fixup is run on multiple databases.

Verify only-CVerifies the integrity of the database and reports errors. Does not modify the database (for example, does not purge corrupted documents).
Fixup subdirectories-YRuns Fixup on databases in subfolders (subdirectories).
Don't fixup subdirectories-yDoes not run Fixup on databases in subfolders (subdirectories).
Update this view only-T

database -T viewtitle

Updates a specific view in a database.

Note You cannot use Indirect (.IND) files with the -T flag to specify a view.

See also