ORA-12008 in MV refresh with no other errors

I have a scheduler job that refreshes multiple MV's. When one fails, it only shows
ORA-12012: error on auto execute of job 1258189
ORA-12008: error in materialized view refresh path
No other errors show up either in the alert log or the resulting trace file. It will refresh fine if I perform the refresh manually after the error.
How can I figure out what is causing the problem (i.e. get additional errors)? Is there some directive I can give to get more information?
Solaris 10, Oracle 10.2.0.1

Note:401971.1-Refresh Of MVIEW Via Database Job Fails ORA-12012 ORA-12008 ORA-942

Similar Messages

Instance crashing with ORA-00469: CKPT process terminated with error

Hi,
Instance crashing with ORA-00469: CKPT process terminated with error on 10.2.0.4. Any possibe causes?
Thanks,
Madhav

I did check alert log and trace files. I just find this in alert log:
ORA-00469: CKPT process terminated with error
Trace file:
*** 2009-07-29 02:22:06.840
*** SERVICE NAME:(SYS$BACKGROUND) 2009-07-29 02:22:06.839
*** SESSION ID:(275.1) 2009-07-29 02:22:06.839
error 469 detected in background process
ORA-00469: CKPT process terminated with error

ORA-12008: error in materialized view refresh path with ORA-01652

I have a temp tablespace with 2 tempfiles of 2GB each (total 4GB) but still refresh of materialized view is failing with following error:
5646690 - BIS Materialized View Refresh Program
ORA-12008: error in materialized view refresh path
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP1
I checked and temp ts is completly filled
SQL> select TABLESPACE_NAME, BYTES_USED, BYTES_FREE from V$TEMP_SPACE_HEADER;
TABLESPACE_NAME BYTES_USED BYTES_FREE
TEMP1 2147483648 0
TEMP1 2147483648 0
My question is how do I find out how much space I need for temp tablespace. what 's the best practise to size temp tablespace when running refresh. refresh is done by client who is submitting a request thru ebiz apps so I 'd like to size it correctly without having to keep guessing.
Thanks so much in advance for any help

Hello,
Temp tablespace size depends how much sort by , order by operation your application performing. You can create new temp tablespace and drop old one with bigger file size
CREATE TEMPORARY TABLESPACE TEMP02 TEMPFILE '\mypath_to_temp\TEMP02' SIZE 256M REUSE AUTOEXTEND ON NEXT 256M MAXSIZE 8192M EXTENT MANAGEMENT LOCAL;
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP02;
Drop tablespace temp including contents; -- Make sure you delete on temp data files.Here is link for your reading purpose
http://www.idevelopment.info/data/Oracle/DBA_tips/Tablespaces/TBS_3.shtml
Regards
Edited by: OrionNet on Mar 6, 2009 6:15 PM

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, ORA-12008: error in materialized view refresh path

I want to refresh a materialized view, but I get an ORA-12008 error.
Does anybody have an idea? I do not find any errors in my refresh statement.
CREATE MATERIALIZED VIEW scott.dummy_mv
TABLESPACE test
BUILD IMMEDIATE
USING INDEX TABLESPACE idx_test
REFRESH
     START WITH sysdate
     NEXT ROUND(SYSDATE)+5/24
     WITH PRIMARY KEY
ENABLE QUERY REWRITE
AS
SELECT KM.ID ID
          ,KM.USERNAME USERNAME
       ,KM.ABTID ABTID
FROM my_table KM
scott@orcl>desc dummy_mv
Name                                      Null?    Typ
ID                                        NOT NULL NUMBER(4)
USERNAME                                  NOT NULL VARCHAR2(30)
ABTID                                     NOT NULL NUMBER(4)
scott@orcl>
BEGIN
SYS.DBMS_JOB.REMOVE(6579);
COMMIT;
END;
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
( job       => X
   ,what      => 'dbms_refresh.refresh(''"scott"."dummy_mv"'');'
   ,next_date => to_date('07.01.2009 05:00:00','dd/mm/yyyy hh24:mi:ss')
   ,interval => 'ROUND(SYSDATE)+5/24              '
   ,no_parse => FALSE
SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || to_char(x));
COMMIT;
END;
scott@orcl>exec dbms_refresh.refresh('dummy_mv');
BEGIN dbms_refresh.refresh('dummy_mv'); END;
FEHLER in Zeile 1:
ORA-12008: error in materialized view refresh path
ORA-00947: not enough values
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 820
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 877
ORA-06512: in "SYS.DBMS_IREFRESH", Zeile 683
ORA-06512: in "SYS.DBMS_REFRESH", Zeile 195
ORA-06512: in Zeile 1
scott@orcl>

crupper wrote:
I get the same error:
scott@orcl>exec dbms_mview.refresh('dummy_mv','c');
BEGIN dbms_mview.refresh('dummy_mv','c'); END;
FEHLER in Zeile 1:
ORA-12008: error in materialized view refresh path
ORA-00947: not enough values
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 820
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 877
ORA-06512: in "SYS.DBMS_SNAPSHOT", Zeile 858
ORA-06512: in Zeile 1
I would first check the "query" information of the DBA_SNAPSHOTS/DBA_MVIEWS dictionary views if it reveals anything obvious.
But it looks more like an internal error while processing the refresh. You can get more information about the error by tracing the session. A "alter session set sql_trace = true;" before running the refresh should be sufficient. Disconnect afterwards and check the generated trace file for errors either using "tkprof" and checking the output or by manually searching for "err=" in the trace file.
Which 4-digit version of Oracle are you using?
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

ORA-12008: error in materialized view refresh path... Bug?

SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE    11.2.0.3.0      Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
SQL> drop materialized view log on test_tbl;
Materialized view log dropped.
SQL> drop materialized view mv_test_tbl;
Materialized view dropped.
SQL> drop table test_tbl;
Table dropped.
SQL> create table test_tbl(
2   test_id   number(10)   primary key,
3   test_name varchar2(10) not null)
4 ;
Table created.
SQL> insert into test_tbl values (1,'bob');
1 row created.
SQL> insert into test_tbl values (2,'joe');
1 row created.
SQL> insert into test_tbl values (3,'john');
1 row created.
SQL> commit;
Commit complete.
SQL> create materialized view log on test_tbl
2 with primary key , rowid, sequence
3 (
4   test_name
5 )
6 including new values;
Materialized view log created.
SQL> create materialized view mv_test_tbl
2 refresh fast on commit
3 as
4 select test_id,
5         test_name
6 from   test_tbl;
Materialized view created.
SQL> update test_tbl set test_name = 'hello' where test_id = 1000;
0 rows updated.
SQL> commit;
Commit complete.Ok, so that's all good. Now if I create the materialized view log with the COMMIT SCN option:
SQL> drop materialized view log on test_tbl;
Materialized view log dropped.
SQL> drop materialized view mv_test_tbl;
Materialized view dropped.
SQL> create materialized view log on test_tbl
2 with primary key , rowid, sequence
3 (
4   test_name
5 ),
6 commit scn
7 including new values;
Materialized view log created.
SQL> create materialized view mv_test_tbl
2 refresh fast on commit
3 as
4 select test_id,
5         test_name
6 from   test_tbl;
Materialized view created.
SQL> update test_tbl set test_name = 'hello' where test_id = 1000;
0 rows updated.
SQL> commit;
commit
ERROR at line 1:
ORA-12008: error in materialized view refresh path
ORA-01006: bind variable does not exist
SQL>Committing an update that updates no rows against a master table for a single table fast refreshable materialized view results in the error above when the materialized view log on the master table is created with the COMMIT SCN option. I'm guessing that this isn't how things are supposed to work. Or am I missing something here? Anyone else encountered this before?
Cheers.
Edited by: Stain on Jan 25, 2013 1:27 PM

Query Rewrite is an option for a Materialized View, not a Materialized View Log. Also, query rewrite is used as an optimization technique which "transforms a SQL statement expressed in terms of tables or views into a statement accessing one or more materialized views that are defined on the detail tables". I don't think it plays any role in the refresh path.
Regardless, it made no difference.
SQL> create materialized view mv_test_tbl
2 refresh fast on commit
3 ENABLE QUERY REWRITE
4 as
5 select test_id,
6         test_name
7 from   test_tbl
8 ;
Materialized view created.
SQL> update test_tbl set test_name = 'hello' where test_id = 1000;
0 rows updated.
SQL> commit;
commit
ERROR at line 1:
ORA-12008: error in materialized view refresh path
ORA-01006: bind variable does not exist
SQL>Edited by: Stain on Jan 25, 2013 2:06 PM

ORA-12008: error in materialized view refresh path in 10g

Hi, all.
The database is on 10gr2.
I am testing materized view refresh.
However, I got the following errors.
exec dbms_refresh.refresh('"STGFAB"."MV_OPTION_TEST_HO1"');
ORA-12008: error in materialized view refresh path
ORA-01008: not all variables bound
ORA-02063: preceding line from L8ZFAB
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2254
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2460
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
Thanks in advance.
Best Regards.

Subject:      Materialized View Refresh Fails on Second Attempt With ORA-01008 'Not All Variables Bound' Error
     Doc ID:      Note:472261.1      Type:
--MM

ORA-12008: error in materialized view refresh path ;;; PLZ HELP ME

Hi all,
I 'm using Oracle Database 10g Enterprise Edition Release 10.2.0.1.0; I got these errors when I tried to refresh my materialized view ;
ORA-12008: error in materialized view refresh path
ORA-01555: snapshot too old: rollback segment number 5 with name "_SYSSMU5$"
too small
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2255
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2461
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2430
I don't understand what mean these errors and why i got them?
Someone can help me please ?
Thanks
regards,

thank you Justin,
I found in my alertDB.log this line ;
Mon Aug 20 03:00:54 2007
ORA-01555 caused by SQL statement below (SQL ID: 64a7sdbbvknta, Query Duration=1021 sec, SCN: 0x0004.4a145344):
Mon Aug 20 03:00:54 2007
INSERT /*+ BYPASS_RECURSIVE_CHECK */ INTO "MANAGEMENT"."MVIEW_COMPUTERS"("ID","WINVERSION","ANTIVIRUS","GUID","INSTALLDT","CONNECTION_TYPE","GROUPID
","QUOVACOUNTRY") SELECT "C"."ID","C"."WINVERSION","C"."ANTIVIRUS","C"."GUID","C"."INSTALLDT","C"."CONNECTIONTYPE","C"."GROUPID","C"."QUOVACOUNTRY"
FROM "MANAGEMENT"."COMPUTERS" "C"
So i execute this query to found the TUNED_UNDORETENTION value ;
SELECT *
FROM V$UNDOSTAT v
WHERE v.MAXQUERYID = '64a7sdbbvknta'
and i have this result :
BEGIN_TIME     20070820 02:53:42
END_TIME     20070820 03:03:42
UNDOTSN     1
UNDOBLKS     51242
TXNCOUNT     5012
MAXQUERYLEN     1060
MAXQUERYID     64a7sdbbvknta
MAXCONCURRENCY     21
UNXPSTEALCNT     0
UNXPBLKRELCNT     0
UNXPBLKREUCNT     0
EXPSTEALCNT     14
EXPBLKRELCNT     51392
EXPBLKREUCNT     0
SSOLDERRCNT     1
NOSPACEERRCNT     0
ACTIVEBLKS     606920
UNEXPIREDBLKS     19896
EXPIREDBLKS     612728
TUNED_UNDORETENTION     1841
I don't know exactly which value i should set my parameter?
Message was edited by:
HAGGAR

Refresh Collection Snapshots Error ORA-12008 ORA-01555

Need some insight!
Ct is implementing R12.1.1 ASCP using existing 11.5.10 EBS as source.
In source EBS, when running Refresh Collection Snapshots (RCS) in COMPLETE mode, we encounter this error:
ORA-12008: error in materialized view refresh path
ORA-01555: snapshot too old: rollback segment number 13 with name "_SYSSMU13$" too small
ORA-12008: error in materialized view refresh path
ORA-01555: snapshot too old: rollback segment number 13 with name "_SYSSMU13$" too small
All the snapshot entities got refreshed successfully (in 5 minutes) but the Refresh Collection Snapshot request itself ends with ERROR (after 4 hrs).
Appreciate your input on this one.
Thanks,
Jake

Welcome to the forums !
ORA-01555 is a common error condition. There are typically two solutions (or a combination of both) -
1. Increase rollback / undo tablespace size
2. Run your process when the database is not active (i.e. few or no updates/deletes/inserts etc).
More information may be available in these MOS Docs
211121.1 - How To Run MSRFWOR - Refresh Collections Snapshots Concurrent Request From The Application
207644.1 - Data Collections is Failing - All Errors - First Diagnostic Steps
306418.1 - 11.5.10 MSRFWOR: Refresh Collection Snapshot Performance Is Poor and Fails with Errors
369173.1 - MSRFWOR Refresh Collection Snapshots Performance Database Bug 4196039
308487.1 - Refresh Collection Snapshot Request Fails Yet The Request Shows Complete Normal
HTH
Srini

Materialed View Refresh Error ORA-12008: error in materialized view refresh

Hi,
I am trying to refersh the following materialized view with the below command and getting the below error
begin
DBMS_MVIEW.REFRESH('GLVW_MIS_ADB');
end;
The following error has occurred:
ORA-12008: error in materialized view refresh path
ORA-12840: cannot access a remote table after parallel/insert direct load txn
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 803
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 860
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 841
ORA-06512: at line 2
Please advice on this.
Thanks & Regards,
Kartik

$ oerr ora 12840
12840, 00000, "cannot access a remote table after parallel/insert direct load txn"
// *Cause: Within a transaction, an attempt was made to perform distributed
// access after a PDML or insert direct statement had been issued.
// *Action: Commit/rollback the PDML transaction first, and then perform
// the distributed access, or perform the distributed access before the
// first PDML statement in the transaction.
$

Error: ORA-12008: error in materialized view refresh path

Hello Dba' s
We are on 12.0.6 EBS with 10.2.0.5 DB on Sun solaris SPARC 64 bit.
We are getting below error while Refreshing Materialized View.
Start of log messages from FND_FILE
Error: ORA-12008: error in materialized view refresh path
ORA-00600: internal error code, arguments: [kcblasm_1], [103], [], [], [], [], [], [] Occured while Refreshing Materialized View
End of log messages from FND_FILE
Not sure how to proceed.We have just upgraded our database from 10.2.0.3 to 10.2.0.5.
Also we still have our test instance with 10.2.0.3 database ,there refreshing MV completed successfully.
Also refreshing through TOAD gives below error:-
BEGIN
DBMS_SNAPSHOT.REFRESH(
LIST => 'XXPPL.XXPPL_OPM_TRANSACTIONS_MV'
,PUSH_DEFERRED_RPC => TRUE
,REFRESH_AFTER_ERRORS => FALSE
,PURGE_OPTION => 1
,PARALLELISM => 0
,ATOMIC_REFRESH => TRUE
,NESTED => FALSE);
END;
Error at line 2
ORA-12008: error in materialized view refresh path
ORA-00600: internal error code, arguments: [kcblasm_1], [103], [], [], [], [], [], []
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2256
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2462
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2431
ORA-06512: at line 2
Please advice.
Thanks,
Edited by: user12209274 on Nov 23, 2010 2:10 AM

thank you Justin,
I found in my alertDB.log this line ;
Mon Aug 20 03:00:54 2007
ORA-01555 caused by SQL statement below (SQL ID: 64a7sdbbvknta, Query Duration=1021 sec, SCN: 0x0004.4a145344):
Mon Aug 20 03:00:54 2007
INSERT /*+ BYPASS_RECURSIVE_CHECK */ INTO "MANAGEMENT"."MVIEW_COMPUTERS"("ID","WINVERSION","ANTIVIRUS","GUID","INSTALLDT","CONNECTION_TYPE","GROUPID
","QUOVACOUNTRY") SELECT "C"."ID","C"."WINVERSION","C"."ANTIVIRUS","C"."GUID","C"."INSTALLDT","C"."CONNECTIONTYPE","C"."GROUPID","C"."QUOVACOUNTRY"
FROM "MANAGEMENT"."COMPUTERS" "C"
So i execute this query to found the TUNED_UNDORETENTION value ;
SELECT *
FROM V$UNDOSTAT v
WHERE v.MAXQUERYID = '64a7sdbbvknta'
and i have this result :
BEGIN_TIME     20070820 02:53:42
END_TIME     20070820 03:03:42
UNDOTSN     1
UNDOBLKS     51242
TXNCOUNT     5012
MAXQUERYLEN     1060
MAXQUERYID     64a7sdbbvknta
MAXCONCURRENCY     21
UNXPSTEALCNT     0
UNXPBLKRELCNT     0
UNXPBLKREUCNT     0
EXPSTEALCNT     14
EXPBLKRELCNT     51392
EXPBLKREUCNT     0
SSOLDERRCNT     1
NOSPACEERRCNT     0
ACTIVEBLKS     606920
UNEXPIREDBLKS     19896
EXPIREDBLKS     612728
TUNED_UNDORETENTION     1841
I don't know exactly which value i should set my parameter?
Message was edited by:
HAGGAR

Mview refresh and ORA-12008 error

I am getting the following when I try to refresh a materialized view. This error occurs the first time I try to refresh, then if I try again, the refresh is successful.
Most of what I have been able to glean about this error is that it is related to M$log changes, however, this view does not use nor build upon an other views that use, mview logs. Any ideas?
ORA-12008: error in materialized view refresh path
ORA-01555: snapshot too old: rollback segment number 13 with name "_SYSSMU13$" too small
ORA-02063: preceding line from db1
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2537
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2743
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2712
ORA-06512: at line 2

Hi j_70!
I'm not exactly sure about the answer, but I guess that the ORA-01555 is the main problem. Have you tried to grow your Undotablespace? I think that the refresh of the MVIEW takes a long time (like a long SELECT-Statement) and if there are many UPDATE and INSERT-Statements while the refresh is in progress than ORA-01555 may be the consequence.
If you have Oracle 10g use the Undo-Advisor to look for the problem.
Hope this helps!

ORA-12008: error in snapshot refresh path

I am getting this error even i am specifying to use other rollback segment
ALTER ROLLBACK SEGMENT R02 SHRINK;
SET TRANSACTION USE ROLLBACK SEGMENT R02;
alter materialized view PAY_REV_BREAKUPWITHWOFF NOLOGGING;
BEGIN dbms_mview.refresh('PAY_REV_BREAKUPWITHWOFF') ; END;
ERROR at line 1:
ORA-12008: error in snapshot refresh path
ORA-01562: failed to extend rollback segment number 1
ORA-01628: max # extents (505) reached for rollback segment SYS_RBS
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 617
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 674
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 654
ORA-06512: at line 1

The reason why it's still using SYS_RBS seems to be that since you are refreshing a materialized view, it might be doing parallel DMLs. In this case the clause of specifying a particular rollback segment is ignored.
In addition to the above, try taking the rollback segment offline by executing
alter rollback segment SYS_RBS offline;
and then drop it by running
drop rollback segment SYS_RBS;
Then create new one and see if it works.
if the above mentioned doesn't work somehow...
try to change the extents storage parameter by running
alter rollback segment sys_rbs storage (MAXEXTENTS 1000);
Can't be sure as i currently don't have access to my system
Hope this helps
Message was edited by:
thrilller

M_View failed inrefresh throws error: ORA-12008/ORA-01843:not a valid month

I am not able to refresh this matrialized view in 2 databases.Can some one help please
======================================================
SQL> exec dbms_refresh.refresh('OID_SYNCH.OID_SYNCH_EMPLOYEES_HR');
BEGIN dbms_refresh.refresh('OID_SYNCH.OID_SYNCH_EMPLOYEES_HR'); END;
ERROR at line 1:
ORA-12008: error in materialized view refresh path
ORA-01843: not a valid month
ORA-02063: preceding line from HR
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2251
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2457
ORA-06512: at "SYS.DBMS_IREFRESH", line 685
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
======================================
DDL of Matrialized view is as:
CREATE MATERIALIZED VIEW "OID_SYNCH"."OID_SYNCH_EMPLOYEES_HR" ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "OID_SYNCH_D" BUILD IMMEDIATE USING INDEX REFRESH COMPLETE ON DEMAND START WITH sysdate+0 NEXT trunc(sysdate + 1) USING DEFAULT LOCAL ROLLBACK SEGMENT
DISABLE QUERY REWRITE AS ( select hr_person_id, hr_employee_status, hr_employee_number,hr_workbrain_id, hr_last_name, hr_first_name, hr_full_name,
hr_known_as, hr_middle_names, hr_previous_last_name,hr_suffix, hr_email_address, hr_user_name,system_person_type, user_person_type, hr_start_date, hr_last_update_date,home_city, home_state, home_zip, home_country,home_last_update_date,position_name, job_name,work_location_code, work_location_desc,work_city, work_state, work_zip,work_country,work_last_update_date,hr_supervisor_name,hr_supervisor_id,hr_sup_last_update_date,termination_date
from oid_synch_employees@hr )

>
I am not able to refresh this matrialized view in 2 databases.Can some one help please
>
Post the ddl for the source table.
Also do a test. Create a table that is a clone of the MV table. Then try to do an INSERT INTO SELECT * FROM the source table into the clone table and see if you get an error.
Don't forget to post the 4 digit Oracle versions of the source and target databases.

Shutdown immediate hangs ORA-12012, ORA-12008, ORA-06512

We have a problem while immediate shutting down the database:
alert.log:
Errors in file /data_archiv/oracle/admin/EGB/bdump/egb_j001_7708.trc:
ORA-12012: error on auto execute of job 3
ORA-12008: error in materialized view refresh path
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 1883
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2089
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
Mon Jun 11 16:20:29 2007
Job queue slave processes stopped
Mon Jun 11 16:26:36 2007
Active call for process 7695 user 'oracle' program 'oracle@lxegbp2qs (J000)'
SHUTDOWN: waiting for active calls to complete.
Trace:
/data_archiv/oracle/admin/EGB/bdump/egb_j001_7708.trc
Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /data_archiv/oracle/product/10g
System name:     Linux
Node name:     lxegbp2qs
Release:     2.6.5-7.244-smp
Version:     #1 SMP Mon Dec 12 18:32:25 UTC 2005
Machine:     i686
Instance name: EGB
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 7708, image: oracle@lxegbp2qs (J001)
*** SERVICE NAME:(SYS$USERS) 2007-06-11 16:20:28.759
*** SESSION ID:(273.1) 2007-06-11 16:20:28.759
*** 2007-06-11 16:20:28.759
ORA-12012: error on auto execute of job 3
ORA-12008: error in materialized view refresh path
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 1883
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2089
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
The job with id 3 should not run during shut down (needs only seconds):
select substr(what, 1, 70), TO_CHAR(last_date, 'DD.MM.YYYY HH24:MI:SS') as last_date, TO_CHAR(next_date, 'DD.MM.YYYY SQL> HH24:MI:SS') as next_date from dba_jobs where job=3;
SUBSTR(WHAT,1,70)
LAST_DATE NEXT_DATE
dbms_refresh.refresh('"TEST"."MV_TEST"');
11.06.2007 06:00:06 12.06.2007 06:00:00
Any ideas where to look for?

Active call for process 7695 user 'oracle' programKill active call process mentioned in alert.log.

ORA-12008 in MV refresh with no other errors

Similar Messages

Maybe you are looking for