Using oracle DBMS_FLASHBACK.ENABLE_AT_TIME with materialized views -
i'm trying find workaround problem oracle atomic materialized view refresh takes long.
we need snapshot number of large database tables @ given point in processing day (just once day). expdb this, works fine requires second database restore. testing materialized view this, we've found full non-atomic refresh quick (about 30 min in our environment), atomic refresh takes many hours. (we understand fast refresh may option, not simple, of mvs involve joins of many tables.)
so i'm wondering if use dbms_flashback.enable_at_time freeze session @ point in time, issue dbms_mview.refresh(non-atomic). question whether dbms_job spawned refresh() runs in same session client, or if starts own session.
Comments
Post a Comment