29 Mar 2012 17:08
ORA 942 on mview refresh
Just solved this a couple of days ago, with similar frustrations over many months due to the lack of information about the source of the error. I also worked around it for a long time by recreating the MV myself. Finally, some of the articles and advice I found sunk in. The failures were caused by missing object permissions. My access to the base objects used in the MV was role-based. Creating the MV was never a problem but the refresh job kept failing. Once I asked my DBA for direct select permissions on the base objects, problem was solved. The PL/SQL refresh package cannot work on objects without direct grants to the owner of the refresh job. Bob Laverty ------------------------------ From: "Stephens, Chris" <Chris.Stephens@...> Date: Tue, 27 Mar 2012 15:22:36 -0500 Subject: ORA 942 on mview refresh 11.2.0.3 EE on RHEL5 I'm having a helluva time tracking down the source of an ORA-00942 error refreshing a materialized view. I've done "alter system set events '942 trace name errorstack level 3';" but that just shows the call to dbms_mview.refresh as the SQL in the trace file. As the owner of the materialized view I can run the SQL the MV is based on + create the same MV with only a different name. This is one of those materialized views built on a nested rabbit hole of other views and materialized views which complicates things.(Continue reading)
RSS Feed