Fixup options
The information in this topic describes the options that are available when you run Fixup.
Fixup options in Fixup tool and Task - Start tool | Command-line equivalent | Description |
---|---|---|
|
|
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 |
-L |
Reports 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 |
-I |
When 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 |
-F |
When 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 |
-Q |
Checks documents more quickly but less thoroughly. Without this option, Fixup checks documents thoroughly. |
Exclude views (faster) |
-V |
Prevents 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 |
-N |
Prevents 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 |
-U |
Reverts 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 |
-J |
Runs 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 |
-O |
If 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 |
-Z |
Applies only to running Fixup on a single database. When a database is not taken offline and is in use, then Fixup is not run. This is the default when Fixup is run on multiple databases. |
Verify only |
-C |
Verifies the integrity of the database and reports errors. Does not modify the database (for example, does not purge corrupted documents). |
Fixup subdirectories |
-Y |
Runs Fixup on databases in subfolders (subdirectories). |
Don't fixup subdirectories |
-y |
Does not run Fixup on databases in subfolders (subdirectories). |
Update this view only |
-T |
Updates a specific view in a database. Note: You
cannot use Indirect (.IND) files with the -T flag
to specify a view. |
DAOS option for Fixup
You can run the following DAOS option (-D) for Fixup from the command line only. As with other Fixup options, you can add the -N option to prevent deletion of documents.
Because
transaction logging is required in DAOS-enabled databases, you must
include the -J
option for the -D
option.
Command-line |
Description |
---|---|
-J -D dbname.nsf |
Purges or fixes documents in the specified database containing objects stored in the Document Attachment and Object Service (DAOS) in three cases: when a document is corrupted, when the DAOS ticket (reference) is outdated, or when the associated object (.NLO file) is missing. The If the .NLO file location information stored in a DAOS ticket is outdated, this option updates it. This option also forces recalculation of the DAOS reference count and size information that you can display using the Show Directory command. |