Not sure why you feel it is necessary to truncate the log. The log is
intended for ORACLE internal use and not a good idea for you to mess
with it. I can only imagine that you are doing this because the log is
getting too big and the space can not be relcaimed after each fast
refresh. Not worth it spending time trying to figure out how to save
some disk space. I would fast refresh more frequently if the logs
indeed grow too quickly.
j_l_green_at_hotmail.com (jam) wrote in message news:<5991c9f2.0304140917.1b10c6b3_at_posting.google.com>...
> I have a materialized view with a log that I am using for fast
> refresh. Following each refresh, the log correctly becomes empty.
> Periodically I would like to truncate the empty log. The problem I
> have is that each time I truncate the log it is ignored when I do the
> next fast refresh. The only way I can then get Oracle to re-use the
> log is to do a complete refresh. Following the complete refresh the
> log is used correctly for the next fast refresh. It is impractical for
> me to do complete refreshes each day as the base table is very large
> and this would take most of the day. Fast refresh is ideal because I
> am only adding a small percentage of new rows each day (about 1%). I
> am using version 9.0.1
>
> Thanks, Jamie.
Received on Tue Apr 15 2003 - 13:03:13 CDT
