Materialized view complete refresh fails with ora-02068

exec dbms_mview.refresh('WZ_PMS_INVOICE_DTLS','C');
BEGIN dbms_mview.refresh('WZ_PMS_INVOICE_DTLS','C'); END;
ERROR at line 1:
ORA-12008: error in materialized view refresh path
ORA-02068: following severe error from
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 820
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 877
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 858
ORA-06512: at line 1
Please help
RP

i traced this CTAS
alter session set timed_statistics = true;
alter session set events '10046 trace name context forever, level 12';
create table pms_temp as select telephone_no from pms_invoice_dtls@cdrwest;
create table pms_temp as select telephone_no from pms_invoice_dtls@cdrwest
ERROR at line 1:
ORA-02068: following severe error from
and it generated a trace file in udump
the last few lines contain the following
=====================
PARSING IN CURSOR #11 len=283 dep=1 uid=0 oct=6 lid=0 tim=1277033874638425 hv=3948238198 ad='9f4a5a30'
update seg$ set type#=:4,blocks=:5,extents=:6,minexts=:7,maxexts=:8,extsize=:9,extpct=:10,user#=:11,iniexts=:12,lists=decode(:13, 65535, NULL, :13),groups=decode(:14, 65535, NULL, :14), cachehint=:15, hwmincr=:16, spare1=DECODE(:17,0,NULL,:17) where ts#=:1 and file#=:2 and block#=:3
END OF STMT
PARSE #11:c=0,e=17,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=4,tim=1277033874638420
BINDS #11:
bind 0: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b781099c bln=24 avl=02 flg=05
value=3
bind 1: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b7810978 bln=24 avl=03 flg=05
value=448
bind 2: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b7810954 bln=24 avl=02 flg=05
value=22
bind 3: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b7810930 bln=24 avl=02 flg=05
value=1
bind 4: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b781090c bln=24 avl=06 flg=05
value=2147483645
bind 5: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b78108e8 bln=24 avl=02 flg=05
value=64
bind 6: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b78108c4 bln=24 avl=01 flg=05
value=0
bind 7: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b78108a0 bln=24 avl=03 flg=05
value=2475
bind 8: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b780fe9c bln=24 avl=02 flg=05
value=4
bind 9: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b780fe78 bln=24 avl=01 flg=05
value=0
bind 10: (No oacdef for this bind)
bind 11: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b780fe54 bln=24 avl=01 flg=05
value=0
bind 12: (No oacdef for this bind)
bind 13: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b780fe30 bln=24 avl=01 flg=05
value=0
bind 14: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b780fe0c bln=24 avl=05 flg=05
value=1642736
bind 15: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b780fde8 bln=24 avl=04 flg=05
value=131073
bind 16: (No oacdef for this bind)
bind 17: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b7810a08 bln=22 avl=03 flg=05
value=137
bind 18: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b78109e4 bln=24 avl=02 flg=05
value=68
bind 19: dty=2 mxl=22(22) mal=00 scl=00 pre=00 oacflg=08 oacfl2=1 size=24 offset=0
bfp=b78109c0 bln=24 avl=04 flg=05
value=104537
EXEC #11:c=1000,e=1183,p=0,cr=5,cu=1,mis=0,r=1,dep=1,og=4,tim=1277033874639736
STAT #11 id=1 cnt=0 pid=0 pos=1 obj=0 op='UPDATE '
STAT #11 id=2 cnt=1 pid=1 pos=1 obj=14 op='TABLE ACCESS CLUSTER SEG$ '
STAT #11 id=3 cnt=1 pid=2 pos=1 obj=9 op='INDEX UNIQUE SCAN I_FILE#_BLOCK# '
EXEC #3:c=726889,e=217706310,p=7,cr=417,cu=409,mis=0,r=0,dep=0,og=4,tim=1277033875797114
ERROR #3:err=2068 tim=1919250001
*** 2011-06-10 13:16:24.262
XCTEND rlbk=0, rd_only=1
STAT #6 id=1 cnt=1 pid=0 pos=1 obj=475 op='TABLE ACCESS FULL CDC_SYSTEM$ '

Similar Messages

Materialized view fast refresh raising error ORA-12031

Hi All,
I have a table named TblA on A database. I have created mview name mviewTblA on database B.
When I tried to Complete refresh on mviewTblA it is getting refresh but with fast refresh it is raising an error i.e ORA-12031: cannot use primary key columns from materialized view log on "NIMS"."PIPER_ENABLED_EXCHANGES" ORA-06512: at "SYS.DBMS_SNAPSHOT", line 794 ORA-06512: at "SYS.DBMS_SNAPSHOT", line 851 ORA-06512: at "SYS.DBMS_SNAPSHOT", line 832 ORA-06512: at line 2
BEGIN
DBMS_MVIEW.REFRESH('MVIEWTBLA','F');
END;
I checked with database "A", there is an materialized view log. Tell me how i can view/update that materialized view log i.e. want to see and confirm that materialized view log is created with primary key or not.
Please suggest me on this.
Message was edited by:
user593684

.. I use following code (from asktom.oracle.com) to check any limitations on mview
variable x refcursor
declare
l_data EXPLAINMVARRAYTYPE;
begin
dbms_mview.explain_mview( '&MV_NAME', l_data );
open :x for
select capability_name, possible,
msgno, msgtxt
from table( cast( l_data as EXPLAINMVARRAYTYPE ) )
order by seq;
end;
column msgtxt format a30 word_wrapped
print x;

Dimension refresh fails with ORA-34034

Hi All,
We are currently experiencing a strange behaviour when we refresh one of our dimensions.
One of our dimensions is refreshed daily and has been working fine until yesterday when it fails with this error:
<ERROR>
<![CDATA[
XOQ-01601: error while loading data for Cube Dimension "OLAPUSER.PROD" into the analytic workspace
ORA-34034: 742 is already a value of SALES!PROD_CLASS_SURROGATE.
XOQ-01600: OLAP DML error while executing DML "SYS.AWXML!R11_LOAD_DIM"]]>>
</ERROR>
The PROD dimension is a balanced hierarchy and we've checked theren't any duplicate keys at every level of the hierarchy.
Any idea?
Thanks

I have seen this (in 11.1.0.7, I believe) when the metadata cache ("kgl") gets out of synch with the data dictionary. Specifically there is a flag that determines if prefixes get added to dimension members ("use surrogates" in AWM terms) that becomes false instead of true. If you look at the generated SQL in the OUTPUT column of the CUBE_BUILD_LOG you may find that sometimes a prefix is added to dimension members (e.g. "LEAF_LEVEL_" || dim_table.leaf_column) and othertimes it is not (e.g. just dim_table.leaf_column). A workaround if this is the case may be to execute the following (as dba) before building the dimension.
alter system flush shared_pool;

Materialized view - fast refresh not working on joins

Hello,
Is it true that fast refresh for materialized view is not possible when I do a union of 2 tables, although both tables have materialized view logs ?

there are a number of restrictions with fast refresh, read Materialized View Fast Refresh Restrictions and ORA-12052 [ID 222843.1]
edit: his royal kyteness has posted on this before
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:6506967884606
Edited by: deebee_eh on Apr 25, 2012 3:13 PM

Materialized view fast refresh ...getting ORA-22992: error

Hi All,
Oracle version 11.1.0.7
While creating a materialized view(Fast refresh) on remote tables ... i am getting the ORA-22992: cannot use LOB locators selected from remote tables ... error.
but the actual scenario is... i am not selecting any of the BLOB/LOB columns from the remote tables. I did n't include them in my materialized query.
I am able to refresh it complete but couldn't refresh it fast. Here i want to mention other thing... when ever i have records in Mat view log(Base table has a blob cloumns in it)
i am getting the above error. when no record in the Mat view log(i.e on BLOB base table) .. i can able to refresh it as FAST.
MV_CAPABILITIES table tells that ...My Mat view is able to refresh it FAST.I don't know howw to approach to solve this issue.could some one tell me the approach..to solve it?
Here is the sample code ....this is what i have done so fat
session 1 (REMOTE_ONE)
I have created synonyms for the remote tables on current schema. That's why i didn't include @DBLINK.
create table RT_A ( col1_A varchar2(20), col2_A BLOB,COL3_A NUMBER);
create a table RT_B (COl1_B varchar2(20), col2_B BLOB, COL3_B NUMBER);
create a table RT_C (COL1_C varchar2(20), col2_C VARCHAR2,COL3_C NUMBER);
create MATERIALIZED VIEW LOG ON RT_A
WITH ROWID EXCLUDING NEW VALUES;
create MATERIALIZED VIEW LOG ON RT_B
WITH ROWID EXCLUDING NEW VALUES;
create MATERIALIZED VIEW LOG ON RT_C
WITH ROWID EXCLUDING NEW VALUES;
grant select on RT_A to CUURRENT_ONE with grant option;
grant select on RT_B to CUURRENT_ONE with grant option;
grant select on RT_C to CUURRENT_ONE with grant option;
grant select on MLOG$_RT_A to CUURRENT_ONE with grant option;
grant select on MLOG$_RT_B to CUURRENT_ONE with grant option;
grant select on MLOG$_RT_C to CUURRENT_ONE with grant option;Session 2 (CUURRENT_ONE)
create materialized view ABC_MV
BUILD IMMEDIATE REFRESH FORCE ON DEMAND START WITH SYSDATE NEXT SYSDATE+1
AS
select A.ROWID AS A_ROWID,
B.ROWID as B_ROWID,
C.ROWID AS C_ROWID,
A.COL1_A,
B.col1_B,
c.col1_c
from RT_A, RT_B,RT_C
where COL3_A = COL3_B(+)
and COL3_B = COL3_C(+)Appreciate your help.
Thanks,
Mike

Thanks for the reply
In that he/she is selecting the LOB column from the remote database(master site).
I am just referencing the table which has BLOB column in it.I am not referencing any LOB column in my select(Mat view) query...
is there anything i need to check..?
Regards,
Mike

MATERIALIZED view on two tables with Fast Refresh

i Wanted to create MV on two tables with Fast refresh on commit.
I followed below steps
create materialized view log on t1 WITH PRIMARY KEY, rowid;
create materialized view log on t2 WITH PRIMARY KEY, rowid;
CREATE MATERIALIZED VIEW ETL_ENTITY_DIVISION_ASSO_MV
REFRESH fast ON commit
ENABLE QUERY REWRITE
AS
select A.ROWID B.ROWID,a.c1, DECODE(a.c1,'aaa','xxx','aaa') c2
from t1 A
join t2 b
on AB.c1= CD.c2;
i am getting below error.
Error report:
SQL Error: ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view
12054. 00000 - "cannot set the ON COMMIT refresh attribute for the materialized view"
*Cause: The materialized view did not satisfy conditions for refresh at
commit time.
*Action: Specify only valid options.
Basically i want to take record in MV by joinig two tables and if both of the base tables will updated then record should reflect in materialised view.
Please do the needfull.

does the table support PCT? the other restrictions on joins look to be ok in your statement.
maybe try creating first with on demand instead of commit to see does it create.
http://docs.oracle.com/cd/B19306_01/server.102/b14223/basicmv.htm
>
Materialized Views Containing Only Joins
Some materialized views contain only joins and no aggregates, such as in Example 8-4, where a materialized view is created that joins the sales table to the times and customers tables. The advantage of creating this type of materialized view is that expensive joins will be precalculated.
Fast refresh for a materialized view containing only joins is possible after any type of DML to the base tables (direct-path or conventional INSERT, UPDATE, or DELETE).
A materialized view containing only joins can be defined to be refreshed ON COMMIT or ON DEMAND. If it is ON COMMIT, the refresh is performed at commit time of the transaction that does DML on the materialized view's detail table.
If you specify REFRESH FAST, Oracle performs further verification of the query definition to ensure that fast refresh can be performed if any of the detail tables change. These additional checks are:
A materialized view log must be present for each detail table unless the table supports PCT. Also, when a materialized view log is required, the ROWID column must be present in each materialized view log.
The rowids of all the detail tables must appear in the SELECT list of the materialized view query definition.
If some of these restrictions are not met, you can create the materialized view as REFRESH FORCE to take advantage of fast refresh when it is possible. If one of the tables did not meet all of the criteria, but the other tables did, the materialized view would still be fast refreshable with respect to the other tables for which all the criteria are met.

Adcfgclone fails with ORA-04063: view "SYS.DBA_NETWORK_ACLS" error

Hi all,
While running adcfgclone on dbtier if fails with following error
ORA-04063: view "SYS.DBA_NETWORK_ACLS" error
here is the scene:
we are trying to clone a production instance for doing some patching
while running adcfgclone on target (test instance) it fails
our current environment is
application:R12.1.3
db:11.1.0.7
os: rhel 5.6
here is output from
autoconfig file:
SQLPLUS Executable : /u02/testoba/db/tech_st/11.1.0/bin/sqlplus
SQL*Plus: Release 11.1.0.7.0 - Production on Thu Apr 18 09:28:32 2013
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Enter value for 1: Enter value for 2: Enter value for 3: Connected.
PL/SQL procedure successfully completed.
Commit complete.
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
adcrobj.sh exiting with status 0
ERRORCODE = 0 ERRORCODE_END
.end std out.
.end err out.
AutoConfig Services Phase
Running Service Process 2 of 4 for AppsUtil
Executing script in InstantiateFile:
/u02/testoba/db/tech_st/11.1.0/appsutil/install/TESTOBA_testsrv/addbperms.sh
script returned:
addbperms.sh started at Thu Apr 18 09:28:32 IST 2013
The environment settings are as follows ...
ORACLE_HOME : /u02/testoba/db/tech_st/11.1.0
ORACLE_SID : TESTOBA
TWO_TASK :
PATH : /u02/testoba/db/tech_st/11.1.0/perl/bin:/u02/testoba/db/tech_st/11.1.0/bin:/usr/bin:/usr/sbin:/u02/testoba/db/tech_st/11.1.0/appsutil/jre/bin:/bin:/usr/bin/X11:/usr/local/bin:/u02/testoba/db/tech_st/11.1.0/appsutil/clone/bin/../jre/bin:/u02/testoba/db/tech_st/11.1.0/appsutil/clone/bin/../jre/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/oratest/bin:.
Library Path : /u02/testoba/db/tech_st/11.1.0/lib:/usr/X11R6/lib:/usr/openwin/lib:/u02/testoba/db/tech_st/11.1.0/lib:/usr/dt/lib:/u02/testoba/db/tech_st/11.1.0/ctx/lib
SQLPLUS Executable : /u02/testoba/db/tech_st/11.1.0/bin/sqlplus
     Changing permissions for file sqlplus.
     Changing permissions for file extproc.
     Changing permissions for file tkprof.
addbperms.sh exiting with status 0
.end std out.
.end err out.
AutoConfig Services Phase
Running Service Process 3 of 4 for AppsUtil
Executing script in InstantiateFile:
/u02/testoba/db/tech_st/11.1.0/perl/bin/perl -I /u02/testoba/db/tech_st/11.1.0/perl/lib/5.8.3 -I /u02/testoba/db/tech_st/11.1.0/perl/lib/site_perl/5.8.3 -I /u02/testoba/db/tech_st/11.1.0/appsutil/perl /u02/testoba/db/tech_st/11.1.0/appsutil/install/TESTOBA_testsrv/txkConfigDbOcm.pl
script returned:
Configuring OCM on the Database Tier....
Testing database connection...
Database connection test passed.
Response file /u02/testoba/db/tech_st/11.1.0/appsutil/clone/adclnocm.res required to configure OCM does not exists
ERRORCODE = 0 ERRORCODE_END
.end std out.
.end err out.
AutoConfig Services Phase
Running Service Process 4 of 4 for AppsUtil
Executing script in InstantiateFile:
/u02/testoba/db/tech_st/11.1.0/appsutil/install/TESTOBA_testsrv/txkcreateACL.sh
script returned:
You are running txkcreateACL.sh version 120.1
The environment settings are as follows ...
ORACLE_HOME : /u02/testoba/db/tech_st/11.1.0
ORACLE_SID : TESTOBA
PATH : /u02/testoba/db/tech_st/11.1.0/perl/bin:/u02/testoba/db/tech_st/11.1.0/bin:/usr/bin:/usr/sbin:/u02/testoba/db/tech_st/11.1.0/appsutil/jre/bin:/bin:/usr/bin/X11:/usr/local/bin:/u02/testoba/db/tech_st/11.1.0/appsutil/clone/bin/../jre/bin:/u02/testoba/db/tech_st/11.1.0/appsutil/clone/bin/../jre/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/oratest/bin:.
Executable : /u02/testoba/db/tech_st/11.1.0/bin/sqlplus
Executing txkcreateACL.sql ...
SQL*Plus: Release 11.1.0.7.0 - Production on Thu Apr 18 09:28:33 2013
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected.
FROM DBA_NETWORK_ACLS
ERROR at line 17:
ORA-06550: line 17, column 8:
PL/SQL: ORA-04063: view "SYS.DBA_NETWORK_ACLS" has errors
ORA-06550: line 16, column 3:
PL/SQL: SQL Statement ignored
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
txkcreateACL.sh: exiting with status 1
.end std out.
.end err out.
[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution. Errors are grouped by directory and phase.
The report format is:
<filename> <phase> <return code where appropriate>
[APPLY PHASE]
AutoConfig could not successfully execute the following scripts:
Directory: /u02/testoba/db/tech_st/11.1.0/appsutil/install/TESTOBA_testsrv
txkcreateACL.sh INSTE8_APPLY 1
AutoConfig is exiting with status 1
RC-50014: Fatal: Execution of AutoConfig was failed
Raised by oracle.apps.ad.clone.ApplyDatabase
StackTrace:
java.lang.Exception: RC-50014: Fatal: Execution of AutoConfig was failed
     at oracle.apps.ad.clone.ApplyDatabase.checkAutoConfigErr(ApplyDatabase.java:3192)
     at oracle.apps.ad.clone.ApplyDatabase.runCVMAndAutoConfig(ApplyDatabase.java:3010)
     at oracle.apps.ad.clone.ApplyDatabase.doConf(ApplyDatabase.java:649)
     at oracle.apps.ad.clone.ApplyDatabase.doApply(ApplyDatabase.java:473)
     at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:366)
     at oracle.apps.ad.clone.ApplyDBTier.<init>(ApplyDBTier.java:110)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
     at java.lang.reflect.Constructor.newInstance(Unknown Source)
     at oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:67)
     at java.lang.Thread.run(Unknown Source)
please provide any suitable link or doc id or any workaround
thanks
Zavi

Hi;
Please review:
Adautocfg.Sh Fails With "ORA-01422: " While Executing Txkcreateacl.sh [ID 854746.1]
Database Cloning Failed With txkcreateACL.sh[36]: sqlplus [ID 603297.1]
R12 : Autoconfig script txkcreateACL.sh fails with error ORA-31003: Parent /sys/acls/ already contains child entry OracleEBS.xml [ID 1328458.1]
Regard
Helios

Materialized view fast refresh with date field

I have a situation where I need to create a materialized view worth of 6 months of data with fast refresh option from the master table. Somehow whenever I have the where clause added with the date field then it craps out with "ORA-12015: cannot create a fast refresh materialized view from a complex query".
Here is what I am trying to do. Please let me know if there is any other way to accomplish this.
create table test (id number, date_time DATE);
CREATE MATERIALIZED VIEW LOG ON test WITH ROWID;
CREATE MATERIALIZED VIEW cms.scoreboard_statistics_mv
BUILD IMMEDIATE
REFRESH FAST
WITH ROWID
AS
SELECT * from test
WHERE date_time >= sysdate - 180;
ORA-12015: cannot create a fast refresh materialized view from a complex query
Thanks,
Raj

It's crazy but a new time Metalink help us into the Note:179466.1
The restrictions that prevent snapshots from being fast refreshed depend on
the version of Oracle being used, a full list of these by version is included
in section 3. In all cases the snapshot defining query should:
- refer to fully qualified table names rather than to partial table names.
- refer to remote tables only, not to remote master views or synonyms.
- not generate context sensitive data. For example, do not create a simple
snapshot with a query that uses the SQL functions :SYSDATE, UID or USER.

ORA-12008:ERR OCCCURS WHEN MATERIALIZED VIEW IS REFRESHED FROM OTHER SCHEMA

Hi,
ORA-12008: Error occcurs when materialized view is refreshed from another schema, Following the output of the trace file when error occured.
/u01/app/oracle/admin/orcl92/bdump/orcl92_j000_23729.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
System name: Linux
Node name: newdbserver
Release: 2.6.9-5.ELsmp
Version: #1 SMP Wed Jan 5 19:30:39 EST 2005
Machine: i686
Instance name: orcl92
Redo thread mounted by this instance: 1
Oracle process number: 164
Unix process pid: 23729, image: oracle@newdbserver (J000)
*** SERVICE NAME:(SYS$USERS) 2008-05-23 10:30:51.848
*** SESSION ID:(462.21166) 2008-05-23 10:30:51.848
*** 2008-05-23 10:30:51.848
ORA-12012: error on auto execute of job 766
ORA-12008: error in materialized view refresh path
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2255
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2461
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
Regards,
Abhishek

Hi Damorgan,
As i said, when refresh materialized view from another schema, mentioned error occurs.
I have also granted accees explicitely still following error occurs.
ORA-12008: error in materialized view refresh path
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2255
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2461
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
Regards,
Abhishek
Message was edited by:
AbhishekRathod(user559364)

Materialized View fast refresh problems

I have two databases (A and B).
In database A, user NICK has a table called COLOUR_MASTER.
Also in that database, NICK issues the command create materialized view log on colour_master with primary key including new values (and yes, there is a primary key defined for this table)
In database B, there is a database link called A_LINK, connect to nick identified by password using 'dbA';
Also in database B, user IAN creates a materialized view CM_MV refresh fast as select * from colour_master@A_LINK
That statement completes successfully, and there are several million rows in CM_MV when it's done.
Immediately, IAN issues this command:
begin
dbms_mview.refresh('CM_MV');
end;
...and after a slight pause, he gets the error
ORA-12008: error in materialized view refresh path
ORA-02068: following sever error from A_LINK
ORA-03113: end-of-file on communication channel
Yet a +'select count(*) from colour_master@A_LINK'+ submitted immediately manages to return the correct number of records in database A -so that 3113 is a bit misleading, I think, in that instance A did not crash, the database remains accessible at all times, there are no networking issues (database A and B are both located in the same server room, so this isn't like I'm trying to connect half way round the globe).
The only thing I can think of is that there's a permissions problem causing this error. That because the MV creation is done via a link, there's no problem in IAN seeing the appropriate objects, but that once refreshes come into play, maybe there is.
Can anyone shed any light on why I can't do the fast refresh of the view I can happily create, please?

I'm surprised that no-one has asked you to do the obvious: try doing a select * from colour_master@A_LINK, without that being wrapped up in a create materialized view statment. Just do a plain select * from...
My bet is that you'll get an ORA_22992 cannot use LOB locators selected from remote tables error. And if you can't do a simple select * from a remote table, I suspect that you can reasonably expect fireworks when you try to create or refresh a materialized view on such a thing!
Here's a quick test:
In Database 1:
=========
SQL> create table A (col1 varchar2(2), col2 clob);
Table created.
SQL> alter table A add constraint A1 primary key (col1);
Table altered.
SQL> insert into A values ('AA','This is an entry into a clob column');
1 row created.
SQL> commit;
Commit complete.
SQL> create materialized view log on A with primary key including new values;
Materialized view log created.In Database 2
=========
SQL> connect ims_global/v0yager1@ussd
Connected.
SQL> create materialized view B refresh fast as
2 select * from A@remotedb_link;
Materialized view created.
SQL> exec dbms_mview.refresh('B');
BEGIN dbms_mview.refresh('B'); END;
ERROR at line 1:
ORA-12008: error in materialized view refresh path
ORA-02068: following severe error from REMOTEDB_LINK
ORA-03113: end-of-file on communication channel
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2251
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2457
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2426
ORA-06512: at line 1
SQL> drop materialized view B;
Materialized view dropped.
SQL> create materialized view B refresh fast as
2 select col1 from A@ims_link;
Materialized view created.
SQL> exec dbms_mview.refresh('B');
PL/SQL procedure successfully completed.Which seems to replicate your problem rather well, I think.
I don't know if there are any workarounds for this. I mean, obviously you can miss out the CLOB column in your 'create MV' statement as I just did, but I don't know whether you are even allowed or supposed to be able to create an MV on lob columns and that patch such-and-such will let you do it. Maybe someone else can provide that information.
But at least you won't have to play Russian roulette with your init.ora parameters!

Order by in MATERIALIZED VIEW not work successfully with first column (ID)

Dears,
I am trying to create a Materialized View as below:
CREATE MATERIALIZED VIEW HR.MV_EMP
PCTFREE 10
MAXTRANS 255
TABLESPACE users
STORAGE (
INITIAL 65536
MINEXTENTS 1
MAXEXTENTS 2147483645
BUILD IMMEDIATE
REFRESH ON DEMAND
AS
SELECT *
FROM employees
where rownum < 5000 order by employee_id desc ;But while querying the MATERIALIZED VIEW, it did not work successfully as the data did not appear in the accurate order.
I tried to create the same MATERIALIZED VIEW but order by another column (Column Date), it worked successfully and the data appeared in the accurate order.
It means that MATERIALIZED VIEW not work successfully with the first column (id).
Can you please help me in this ?
Thanks & regards,,

A few pointers :
1. As has been pointed out, the ROWNUM has been incorrectly placed. ROWNUM values are assigned as rows are fetched from the source before the ORDER BY. You need to ORDER BY first (in a SubQuery) and then ROWNUM afterwards (outside the SubQuery).
2. I wonder why you want only the last 5000 EMPLOYEE_IDs. What if Employee_ID 1 is still an active employee (he is the founder, first employee and CEO ?). There could be very many "low" EMPLOYEE_IDs that are still active.
3. Logically I would expect some filter other than the ROWNUM ... ORDER BY to be used to select candidate rows. Then, an ORDER BY in the CREATE query would be unnecessary.
4. When querying the Materialized View you must explicitly ORDER BY (irrespective of whether you did or did not do an ORDER BY in the CREATE ...)
5. How do you expect to refresh the MV ? Will it always be a COMPLETE Refresh ? Remember that your "5000 employees" filter would likely exclude older employees at the next refresh. If you use some other filter, it should be consistent across all refreshs.
Hemant K Chitale

Materialized View cannot use filter columns ORA-12033

Hello Forum members,
I am creating the following MV with Can you please advise me??
Thanks
SQL> create materialized view log on his_swi with rowid including new values;
Materialized view log created.
SQL>
SQL> CREATE MATERIALIZED VIEW His_Swi_mv
2 refresh fast with rowid
3 AS
4 select quarter,sum(sw_po),sum(sw_po_fre),
5 sum(sw_por_sta+sw_porunt_swi+sw_por_hb+sw_po_free) as proj from
6 history_switch group by quarter;
his_swi group by quarter
ERROR at line 6:
ORA-12033: cannot use filter columns from materialized view log on
"EM"."HIS_SWI"

Hello Forum members,
Please ignore the above post.
got solution from : http://www.jusungyang.com/DWfolder/MaterializedViews/MVlogFilterColumns.txt
Thanks

Materialized view fast refresh

I would like to create a fast refresh materialized view. The query is below.
create materialized view dw_v_bal_txn_fast
BUILD IMMEDIATE
refresh fast
as
SELECT b.machine_id,nvl(p.promotion_code_id,0)promotion_code_id,p.promotion_code_name
,min(bal_transaction_id) bal_transaction_id
,offered_promotion_id
,operator_session_id
,decode((case when count(*)>1 then 1 else 0 end),1,max(transaction_type),0,max(transaction_type))transaction_type
,sum(balance_change) balance_change
,min(transaction_time) transaction_time
,min(dtransaction_time) dtransaction_time
,count(*)cnt
,count(balance_change)cnt_balance_change
FROM balance_transaction b,promotion_code p
WHERE
b.machine_id=p.machine_id(+) and
b.promo_code_id=p.promotion_code_id(+)
and b.transaction_type in (3,5)
GROUP BY b.machine_id
,p.promotion_code_id,p.promotion_code_name
,offered_promotion_id
,operator_session_id
The materialized view logs are as follows:
create materialized view log on pims_repo.balance_transaction WITH SEQUENCE, ROWID
(machine_id,bal_transaction_id,MONEY_DEVICE_ID,offered_promotion_id,operator_session_id,transaction_type,
balance_change,transaction_time,dtransaction_time,EXT_KEY,PROMO_CODE_ID,IMP_FILE_HISTORY_ID,PROMOTION_CODE,ACCOUNT_MASTER_ID,EZCODE_VALUE,
PRIZECODE,PROMO_CODE_VALUE_ID
INCLUDING NEW VALUES
create materialized view log on pims_repo.promotion_code WITH SEQUENCE, ROWID
(machine_id,promotion_code_id,CONFIGURATION_ID,PROMOTION_CODE_TYPE_ID,PROMOTION_CODE_NAME,PRICE,credit,PROMOTION_ID,
ACTIVE_START_TIME,DACTIVE_START_TIME,ACTIVE_END_TIME,DACTIVE_END_TIME,AVAILABILITY,CREDIT_TYPE,TIME_MODIFIER,
DAYS,START_TIME,DURATION,TRAFFIC_WATERMARK,TRAFFIC_PERIODS,TRAFFIC_PERIOD_LEN,TRAFFIC_MIN_TIME,TRAFFIC_MAX_TIME,DERIVED
,EXPIRED,uses,USES_ON_PURCHASE,SORT_KEY,FILTER_KEY,EXT_KEY,IMP_FILE_HISTORY_ID,LINKED_PROMOTION_CODE,MARGIN_CRITERIA,
SELECTION_ODDS,AD_ONLY,REFILL_AMOUNT,FILLS
INCLUDING NEW VALUES
and the join columns (machine_id,promotion_code_id) of promotion_code has unique constraint in it.But it still says
ORA-12015: cannot create a fast refresh materialized view from a complex query
Can anyone please let me know what else needto be done.
Thanks in advance.

There are certain restriction on create meterialize view with Fast Refresh
For example in your case,
Restrictions on Fast Refresh on Materialized Views with Joins Only
-They cannot have GROUP BY clauses or aggregates.
-Rowids of all the tables in the FROM list must appear in the SELECT list of the query.
-Materialized view logs must exist with rowids for all the base tables in the FROM list of the query.
Full list of restrictions here
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14223/basicmv.htm#i1006803

Financial Statement Generators fail with ORA-01722

We upgaded from 11.5.10.2 to R12.1.3. Since then we have FGSs fail with ora-01722

*+<Moderator edit - deleted MOS Doc content - pl do NOT post such content - it is a violation of your Support agreement>+*
Please refer:
R12: FSG: PERF0005 Error Detected In GET_DEF_LDGS – ORA-01403: No Data Found Common Issues [ID 1368691.1]
R12: RGRARG FSG Completes with Error, rgrsap.rgrsxp: ORA-01722: Invalid Number [ID 579655.1]

EXPDP fails with ORA-39125: Worker unexpected fatal error in KUPW $

Hi Friends,
Oracle 10.2.0.4.0 on Sun OS
Im trying to do metadata_only export using EXPDP
Facing the below error
ORA-39125: Worker unexpected fatal error in KUPW $ WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB []
ORA-31642: The following SQL statement fails:
BEGIN "SYS". "DBMS_RULE_EXP_RULES." SCHEMA_CALLOUT (1,1,1, '10 .02.00.04.00 ') END;
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA", line 907
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW $ WORKER", line 6307
PL / SQL Call Stack
object line object
handle number name
51bf5dc20 15032 package body SYS.KUPW $ WORKER
51bf5dc20 6372 package body SYS.KUPW $ WORKER
51bf5dc20 2396 package body SYS.KUPW $ WORKER
51bf5dc20 6944 package body SYS.KUPW $ WORKER
51bf5dc20 1314 package body SYS.KUPW $ WORKER
51c7e8650 2 anonymous block
====================================
Findings:
I check the status of DBMS_RULE_EXP_RULES
OWNER OBJECT_NAME OBJECT_TYPE STATUS
SYS DBMS_RULE_EXP_RULES PACKAGE BODY VALID
SYS DBMS_RULE_EXP_RULES PACKAGE VALID
PUBLIC DBMS_RULE_EXP_RULES SYNONYM VALID
DBMS_METADATA & DBMS_SYS_ERROR packages are valid.
======================================================
Error in the alert:
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=25, OS id=6506
to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_01', 'SYS', 'KUPC$C_1_20120908075037', 'KUPC$S_1_20120908075037', 0);
kupprdp: worker process DW01 started with worker id=1, pid=26, OS id=6633
to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_01', 'SYS');
when i check the trace file, find the below error
ORA-04063: package body "SCH.COLLECTION" has errors
But when I check the status of the package, it's valid.
Thanks for your help
KSG

Hi;
Is it full exp? Of yes please review:
DataPump Export Fails With Errors ORA-39125 ORA-31642 ORA-1422 [ID 790988.1]
Full And Schema DataPump Exports Fail With Errors ORA-39125 ORA-31642 During DBMS_SCHED_EXPORT_CALLOUTS.SCHEMA_CALLOUT [ID 1109045.1]
EXPDP FAILS WITH ORA-39125 ORA-31642 DBMS_SCHED_EXPORT_CALLOUTS [ID 445291.1]
Full Database DataPump Export (EXPDP) Fails With Errors ORA-39125 ORA-4045 ORA-1031 On XDB.XDB_PI_TRIG [ID 1102434.1]
Errors ORA-39125 ORA-1801 When Running DataPump Export (EXPDP) [ID 815683.1]
Regard
Helios

Materialized view complete refresh fails with ora-02068

Similar Messages

Maybe you are looking for