====== Troubleshooting migration ======
<WRAP round tip 90%>
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//.
</WRAP>

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.

<WRAP round info 90%>
The most common reasons for data inconsistency:
   * Application or operating system crashes while data are written
   * Disk errors, sector corruption, write failures, driver errors
   * Excessive resource usage resulting in "timeout" when writing data
</WRAP>

The data for the update itself, depending on the version, can be found in the following folders:
  * Since version 12, the //%ProgramData%\TatraMed Software\T3C\Service// folder
  * Before version 12, the installation folder of //T3C Service// (the default folder is //%ProgramFiles(x86)%\TatraMed Software\T3C\Service//)

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:
  * The //job// or //study// folder - contains studies
    * if there is a problem with one particular study, we recommend deleting the specific subfolder
    * alternatively, you can delete the entire folder

  * The //robot// folder - contains a database with records of currently running automated tasks. You can delete it, some tasks may not be completed and will need to be repeated.
  * The //messages.db// file or the //message// folder - message database. You can delete it, you lose old messages.
  * The //rm.db// file or the //record// folder  - database with study transfer records. You can delete it, you lose history.
  * The //notifications.db// or //conf\notification.db// file - database with notification settings. You can delete it.
  * The //users.db// or //conf\user.db// file - database with user settings. You can delete it.

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.

<WRAP round important 90%>
Manual database repair is a very problematic and time-consuming work with an uncertain end.
</WRAP>

~~DISCUSSION:off~~