To avoid problems with broken records, we recommend keeping only the necessary number of records in the system. Otherwise, the application may become slow, because a lot of data is constantly being transferred. I.e. delete already processed studies and messages. T3C is neither a PACS nor a billing/archiving system, but a communication system for the safe and fast transmission of large DICOM studies.
When using T3C system, it may happen that some records become inconsistent and although they can sometimes be used in normal operation, such records cannot be automatically converted when upgrading the system. During the update, all records are gradually converted. Only when this process goes without error will the records be rewritten to a new version. In any error occures, the original records are restored and the successfully updated records are discarded.
The most common reasons for data inconsistency:
The data for the update itself, depending on the version, can be found in the following folders:
When a problem occurs, you can examine the migration log file for any errors. The log file is logs\migrator.log or log\migrator.log. The following is a description of the data in the Service folder by version:
Once the problem is fixed, you need to run the installer again to migrate the records. Other errors may occur, so the process needs to be repeated.
Manual database repair is a very problematic and time-consuming work with an uncertain end.