Ilana Weiser commented on Mar 31, 2011

Re: Maintenance tasks

In general, the majority of IBM technotes do not recommend the use of fixup as part of a weekly maintenance schedule. This is especially true if Transaction Logging is being used in the environment.

Regarding fixup as part of a weekly maintenance schedule:

As per Technote 7006573:

"There is no need to run Fixup or Updall as part of a weekly maintenance schedule. Fixup should be run only if corruption is suspected of a database"

Regarding updall as part of a weekly maintenance schedule:

As per Technote 7006573:

"Updall is run every night by default. Run Updall with switches if view corruption is suspected. "

As per Technote 1299683:

"Run Fixup to fix any corrupted databases - At server startup and as needed"

As per Technote 1193738:

"Fixup is designed to recover corrupt data. This utility manages data in an invalid state but occasionally is unable to manage data errors which can result in server hangs or crashes."

Regarding fixup for Transactional logged Database :

As per IBM Technote 7009309 :

"In most situations, you no longer need to run the Fixup task to recover databases following a system failure. Excluding Fixup results in quicker server restarts, since Fixup must check every document in each database, while transaction log recovery applies

or undoes only those transactions not written to disk at the time of the system failure"

As per IBM Technote 7006573:

"Keep in mind that, after you set up transaction logging, Fixup is not needed or used to bring databases back to a consistent state."

Nathan G Hambridge commented on Aug 18, 2008

Untitled

-S 10 is handy as it will only run the compact -B on the DB's when the white space is greater than %10