Last update: 4 August 2017
In the following situations you may get an error message "INT value = 0: Incompatible type 8" (or different datatypes other than INT, or different type values other than 8):
This message is shown in the log or trace output when the "On-the-fly" migration of objects from former Folio versions did not finish properly.
Please note: A hotfix is available correcting issues with the version migration ("On-the-fly" migration). In the hotfix list of your Fabasoft Folio / Fabasoft eGov-Suite version, look up the ID FOLIX07827 and compare the version number to the version number of your coostd.exe / coostd library on the backendservers, to find out if the hotfix is already installed.
The Upgrade Definition feature is a built-in tool to do object migrations between different Fabasoft Folio versions.
The CSVs in the backend migration folders are used in three ways:
This means, even if the CSV migration files on the backends were correct and consistent during the release update (step 1), loosing or corrupting the CSV file later can lead to problems reading object versions and archived objects (both created with former Folio versions).
The MMC cleanup feature reads the metadata of objects and object versions to calculate if files may be deleted or not. That's why you can see such error messages ("incompatible type") in the cleanup logs in case your system has the depict issue. As the error does not affect the calculation to keep files or not, affected objects will be cleaned up as expected.
This behaviour can have two main reasons. One or both reasons may apply.
The setup process copies Upgrade Definition files (also called "CSV migration") from the Setup Kit to all Backendservers. The file path of this migration files is:
Windows: C:\Program Files\Fabasoft\Components\Server\CooSrv\files\migration
Before a release update process, the CSV files delivered from Fabasoft Solutions need to be patched ("Solution Migration"), so object references in the CSV get replaced by object addresses. The resulting CSV file needs to be copied back to the Setup kit (this is not an automatic process and will be performed by the operator).
During the following Setup process, the patched CSV files are copied to the backendservers (see path above).
Attention: Before performing file operations in the following sections, please create a backup of the migration folder of all backend servers
Check if the migration folders are consistent
Please remember, before changing/copying any files, create a backup of the migration folders of all backendservers.
If you have doubts, please contact the Fabasoft Support.
Upgrade definitions are used to migrate objects, object classes, datatypes from former Fabasoft Folio versions to the current version. In the CSV files that migrations are specified.
If a CSV Upgrade Definition does not cover all possible changes, the migration process may not run and a wrong datatype might be sent to the Folio Kernel.
INT value = 0: Incompatible type 8 means: A INT value 0 was sent to the kernel, but the Kernel expected a value of datatype OBJECT (8). The reason may be, that the new datatype of a property should be object, but the old INT value was not covered by the migration.
If you were able to validate missing Upgrade Definition entries, please contact your project manager for support.
As the above explanation illustrated, the migration folders on the Backend servers are very important.
We recommend to adapt your backup strategy to backup the migration folders on a regular basis.