| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Snapshot (Materialized View) Maladies
They look fine to me. Of course I'm reading this with Notes 6.5, running on crossover 3.0 and SuSE 9.1...
Ron Thomas
Hypercom, Inc
rthomas_at_hypercom.com
"To really screw up Linux you have to work at it...To really screw up Windows, you have to work ON
it..."
Mark.Bobak_at_il.proquest.com
Sent by:
oracle-l-bounce_at_freelists.o To
rg oracle-l_at_freelists.org
cc
06/04/2004 02:21 PM Subject
RE: Snapshot (Materialized View) Maladies
Please respond to
oracle-l_at_freelists.org
There's another one, Jared. 5pt font.
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of
Jared.Still_at_radisys.com
Sent: Friday, June 04, 2004 5:08 PM
To: oracle-l_at_freelists.org
Subject: Re: Snapshot (Materialized View) Maladies
> Our main issue with them is that there is nothing reported in the alert
> log and no easy detection method for problem determination when they are
> NOT WORKING! You must check DBA_JOBS and numerous other tables via
> scripts for exceptions (such as - job running too long, job hasn't run
> at all, job not running at frequency or time specified, etc). Worst of
> all, sometimes even these queries fail to detect that the snapshot has
> not refreshed, and ain't ever gonna. In extreme cases, we've had to
> rebuild several million row mviews at the recommendation of Oracle,
> simply because we had a network outage or some other glitch.
>
> Any comments or similar experiences?
>
Many times. Network glitches can cause the MV slave/master sync
to go awry. I've found the result of it in the mv logs, and could
determine why they would not refresh, but could not determine how
it happened ( I forget exact details at the moment )
The last time it happened was 2 hours before I had to get to the
airport to catch a plane for HOTSOS. :(
That time, dropping/recreating the refresh group fixed the problem.
Jared
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------Received on Fri Jun 04 2004 - 16:34:15 CDT
 |
 |