User guide

may be high but mvf-clean-cache displays the amount of memory required and the operator can add
more virtual memory if necessary.
mvf-clean-cache does not access the contents of the cache files. It works by examining the file names
and reporting the problem. A copy of the report and additional diagnostic messages are written to the
log file. Since mvf-clean-cache may be run on a live system, new files (less than one hour old) are
skipped. Thus, temporary files created by the SCP are ignored.
Performance of mvf-clean-cache is hardware dependent. For comparison, on a Sunfire 280R,
mvf-clean-cache can check approximately 50,000 files per second
mvf-ddo-rescue
This command takes any number of files and directory arguments to determine whether they are
DICOM objects. If the argument is a directory, it analyzes all the files in that directory and recursively
analyzes all files in all subdirectories. If a file is a DICOM object, then mvf-ddo-rescue determines
whether the DICOM object is damaged. If it is undamaged, then mvf-ddo-rescue attempts to find the
object in the database. If the object is found in the database, mvf-ddo-rescue checks for a local cache
location for the object. If a local cache location is found, then mvf-ddo-rescue compares the DICOM
object file with the DICOM object file in the cache to see whether:
1. The cache file is missing
2. The cache file is a duplicate
or
3. The cache file is different
If a problem exists, mvf-ddo-rescue attempts to give precise details. A copy of the report and additional
diagnostic messages are written to the log file.
Performance of mvf-ddo-rescue is hardware dependent. For example, on a Sunfire 280R, mvf-ddo-rescue
can analyze about 40 files per second. Performance also depends on how many files must be identified
by searching the original_sop_instance_uid field in the database.
mvf-report-loss
After repairs have been performed by mvf-check-cache (refer to page 69) mvf-clean-cache (refer to
page 69), and mvf-ddo-rescue (refer to page 70), mvf-report-loss is used to perform the last two steps
of the repair process:
1. It determines what cache files have been lost and generates a "Loss Report" for the customer. The
body of the report contains one line for each study affected and the report is sorted by patient
name and study date.
2. It unregisters the missing cache files from the database, preventing display, transmit, and archive
errors that are caused when the product tries to access files that are missing from the cache.
mvf-report-loss has two corresponding modes of operation:
AS300 Upgrade Guide—IMPAX 6.2 or later to IMPAX 6.4 70
AGFA COMPANY CONFIDENTIAL