Bei zu grossen Log_Log und/oder Change_Change Tabellen kann es vorkommen, dass die Datenbankverbindung in ein Timeout läuft und die Installation damit abbricht.
Ein Workaround ist folgendes:
Log_Log Tabelle truncaten
Manuell dieses SQL-Skript einspielen und zuvor die Timeouts im MySQL Workbench erhöhen:
ALTER TABLE `change_change` CHARACTER SET = utf8mb4; ALTER TABLE `change_change` CHANGE COLUMN `originator_identifier` `originator_identifier` VARCHAR(255) NOT NULL , CHANGE COLUMN `originator_name` `originator_name` VARCHAR(255) NOT NULL , CHANGE COLUMN `description` `description` VARCHAR(5000) NULL DEFAULT NULL , CHANGE COLUMN `description_html` `description_html` VARCHAR(5000) NULL DEFAULT NULL ; ALTER TABLE `change_change_participant` CHARACTER SET = utf8mb4 ; ALTER TABLE `change_change_object_type` CHARACTER SET = utf8mb4 ; ALTER TABLE `change_change_originator_type` CHARACTER SET = utf8mb4 ; ALTER TABLE `change_change_type` CHARACTER SET = utf8mb4 ; ALTER TABLE `servicedmcore_organization_unit` CHARACTER SET = utf8mb4 ; ALTER TABLE `servicedmcore_organization_unit_record` CHARACTER SET = utf8mb4 ; ALTER TABLE `servicedmcore_organization_unit_record` CHANGE COLUMN `short_name` `short_name` VARCHAR(255) NULL DEFAULT NULL ; ALTER TABLE `servicedmcore_organization_unit_record` CHANGE COLUMN `name` `name` VARCHAR(255) NOT NULL ; ALTER TABLE `servicedmcore_core_identity` CHARACTER SET = utf8mb4 ; ALTER TABLE `servicedmcore_core_identity` CHANGE COLUMN `readonly_display_name` `readonly_display_name` VARCHAR(255) NULL DEFAULT NULL ; ALTER TABLE `change_change_participant` CHANGE COLUMN `identifier` `identifier` VARCHAR(255) NOT NULL , CHANGE COLUMN `name` `name` VARCHAR(255) NOT NULL ; ALTER TABLE `change_change_object_type` CHARACTER SET = utf8mb4 ; ALTER TABLE `change_change_object_type` CHANGE COLUMN `description_key` `description_key` VARCHAR(255) NULL DEFAULT NULL ; ALTER TABLE `change_change_object_type` CHANGE COLUMN `name_key` `name_key` VARCHAR(255) NOT NULL ; ALTER TABLE `change_change_originator_type` CHANGE COLUMN `name_key` `name_key` VARCHAR(255) NOT NULL ; ALTER TABLE `change_change_participant` CHANGE COLUMN `attribute` `attribute` VARCHAR(255) NULL DEFAULT NULL ; ALTER TABLE `change_change_type` CHANGE COLUMN `name_key` `name_key` VARCHAR(255) NOT NULL , CHANGE COLUMN `description_key` `description_key` VARCHAR(255) NULL DEFAULT NULL ; ALTER TABLE `servicecorelogin_user_claim_value` CHARACTER SET = utf8mb4 ; ALTER TABLE `servicecorelogin_user_claim_value` CHANGE COLUMN `string_value` `string_value` LONGTEXT NULL DEFAULT NULL , CHANGE COLUMN `reference` `reference` VARCHAR(255) NULL DEFAULT NULL ; ALTER TABLE `servicecorelogin_username` CHARACTER SET = utf8mb4 ;
CoreOne Application Services
Employments now have a new state called
deleted
and all the state changes are stored in a history table. This allows you to identify recently deleted employments from workflows and other places.In some cases, the reverse identity task failed while synchronizing multi value fields from the target system to the CoreOne Meta Directory
CoreOne Installer
The CoreOne Workflow Runner and the CoreOne Workflow UI are now fully supported with the installer
CoreOne Connector OpenLDAP
While adding new members to a group, there was the possibility of getting a “This object does not exists” error, when a referenced member of the group not actually exists in the target system. This case is now handled in the connector.