Installation guide

If there are multiple caches, the path name of the cache to be checked must be specified. Memory
usage may be high if there are a large number of files, but mvf-check-cache displays the amount of
memory required so that the operator can add more virtual memory if needed
Performance of mvf-check-cache is hardware dependant. For example, on a Sunfire 280R,
mvf-check-cache can check about 130 files per second. With the quick check option enabled (checking
only file existence and file size), about 30,000 files per second can be checked.
mvf-clean-cache
(Topic number: 60506)
This command scans an IMPAX cache directory containing DICOM object files and generates a
report of files that do not belong there, either because the file name format is invalid or because this
location for the object file is not registered in the database. While working, it writes messages to the
stderr stream to keep the tool operator informed of its progress. The path name of the cache to be
scanned is specified on the command line. mvf-clean-cache begins by querying the database for the
list of ordinals for the files in the cache. It keeps this list in memory. If there is a large number of
files, memory usage 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-report-loss
(Topic number: 60524)
After repairs have been performed by mvf-check-cache (refer to page 84) mvf-clean-cache (refer
to page 85), and mvf-ddo-rescue, 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:
Marking mode
The default mode for the tool. In marking mode, the tool checks all the caches on the local server
for the presence of the DICOM object files that the database says should be present. For missing
files, the visible field in the database osr_location table is set to C. (Normally this field contains the
value T for true, or F for false). Changing this field makes these file locations invisible to the product
software.
AS300 Upgrade Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.3 85
Agfa Company Confidential—Subject to Non-Disclosure Obligation