Thank you John. I'm not sure that's the issue here as the invalid state seems to persist even through a MView refresh. These views are designed to transform, stabilize and version production data for reporting in a mobile app. The initial and somewhat complex transformations are handled in series of standard views that can then be replicated in the MView with little more than a SELECT * query. I do have a live sysdate-based timestamp in the view data that gets posted to the MView. Could that be the source of Invalid-ness? Otherwise, the data is a pretty stable and doesn't change much from day to day, and the MView, itself, performs as expected. However, If I understand you correctly, maybe I don't care because the content of the MView is the snapshot from 3:30a, e.g. yesterday's final state, and that's what I want. Make sense? Thanks for the help. Dave
↧