We are conducting a database schema migration and need to create a new column that is not null with a default value of 0. The table being altered will be signiicant in row count, up to 200 million rows with large width (30 columns, all ints and numbers). We believe that DDL is not logged, yet what impact does a default value cause to the redo log and rollback segments when altering a table? We are concerned about the impact to the redo and RBS filling up. Is this a valid concern? Any suggestions on ways to implement this to minimize the impact to our customers production systems?
ALTER TABLE foo
ADD (new_column INTEGER