Hi Christophe,
this seems to be a new bug...
We will try to locate the problem. At the moment we suspect that the 'move'-errors are triggered by table access to columns which were added later and were defined with 'NULL' as default value and this value was not yet changed.
This behaviour was part of a perfprmance optimization to only actually enter the default value of an added column once that column is accessed.
To identify all table columns which could potentially be affected, please execute the following SQL query:
select t.schemaname, t.tablename, t.createdate as tables_createdate, t.createtime as tables_createtime, t.alterdate as tables_alterdate, t.altertime as tables_altertime, c.createdate as columns_createdate, c.createtime as columns_createtime, c.alterdate as columns_alterdate, c.altertime as columns_altertime, c.columnname, c.default from tables t, columns c where t.createdate
The next step would then be to use an SQL update command to really enter 'NULL' for all rows in the affected tables - of course we will try to locate the bug in the meantime...
Thorsten
