more quick actions
minimize quick actions
Topic starter
Hi,
Know that an issue has been discovered in the migration scripts for Log table.
Find below a description of the issue and solution as it will appear in the Release Notes.
Let us know if you need more information.
With version 12, the length of Log list names can be up to 100 characters long (was 12).
This change affects the schema of HDS log tables (columns LogList) and the migration script delivered with versions 12.0.7 and 12.0.8 was incorrect.
The issue is that the migration script, as supplied with the installation package 12.0.7 and 12.0.8, was wrongly altering the column EvtTitle instead of the column LogList, causing potential future issues.
While a database based on an unchanged configuration would most probably continue to work properly, it may become unreliable after certain configuration changes. For example, new records with an associated label of more than 100 characters would fail to be inserted, and insertion of records for a new log list which name would be more than 12 characters would also fail.
If you have upgraded your HDS log tables with version 12.0.7 or 12.0.8, it is advised to apply the following changes manually:
• Alter the LogList column of Log tables to type it varchar(100),
• Alter the EvtTitle column of Log tables to type it varchar(255),
• Make sure the value of DBVersion is set to 4.
[Edit: Fixed in 12.0.9] If you are upgrading you HDS log tables with version 12.0.9 or later, no specific action is required apart from running the migration script.
Posted : 16/07/2019 3:43 pm
Thanks a lot Benoit!
Effectively I met this issue weeks ago when I was converting a big database (200GB).
That was the error I had on HDS.LOG, but I I didn't notify the issue believing it was my mistake.
For info, this is the error you have in HDS.LOG after this wrong conversion - the bad point is that this prevent HDS to work at all until the problem is solved
Posted : 16/07/2019 7:23 pm
Thanks for the feedback Filippo.
Note that this issue only occurs when schemas are manually migrated with the script provided in the bin directory. When databases are automatically updated at project startup everything is fine.
Posted : 17/07/2019 2:53 pm