Hi Ravi Krishna,
I guess Liquibase is just going on the save side and reorg after each change that may put a table in a reorg pending state, as DB2s unique behavior with reorgs is quiet annoying.
I guess Liquibase is just going on the save side and reorg after each change that may put a table in a reorg pending state, as DB2s unique behavior with reorgs is quiet annoying.
As for your question there is a property you can set to prevent Liquibase from firing those reorg statements. It is tied to the ReorganizeTableGeneratorDB2 class and called "autoReorg". You may put that one in your liquibase.properties and no reorg will be fired altogether.
However you will have to manage reorgs completely on your own and in plain Sql as there is no ReorgTable-Change in Liquibase (and even if it is, there s currently no way to distinguish between manual and automatic reorgs).
However you will have to manage reorgs completely on your own and in plain Sql as there is no ReorgTable-Change in Liquibase (and even if it is, there s currently no way to distinguish between manual and automatic reorgs).
kind regards
Daniel