The reason why is because bdbreconfig determines what method it will use when reconfiguring. In some cases that method is save off data, drop table, create table, load data (a long time ago it used to always be this method). Other cases that method is to issue DBMS ALTER table command (this is much quicker for large tables). In either case the assumption would be that the starting point is that the runtime data definition matches the current table describe in DBMS. If that assumption is wrong, a 512 error could be reported as well.
Last edited by Brendan Shine : 8th June 2017 at 22:30.