We changed the underlying table column size (length). So the materialized view which is built on that table throws an error now since the MV column still has the old size.
This is an Oracle 11gR2 database.
How can I change the MV column's length to match the table's new column size without dropping the MV and recreating it?


alter materialized view <your_mv_here> compile– Fatih Keleş Dec 19 '12 at 20:31