Altering Master Table Causes COMPILATION_ERROR Even After Same Changes Made to Mview
Last updated on AUGUST 06, 2013
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.4 to 126.96.36.199 [Release 10.2 to 11.2]
Information in this document applies to any platform.
After altering the master table and making the same changes to the materialized view's container table, the materialized view will not refresh; it has a status of INVALID and a staleness of COMPILATION_ERROR. The only remedy is to drop and recreate the materialized view after changing the master table. The two cases documented for this are where a column datatype is changed or a column length is changed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms