Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Refreshing materialized view

Status
Not open for further replies.

himridul

Programmer
Jun 23, 2003
62
US
CREATE MATERIALIZED VIEW IND_UNMATCHED_MV
PARALLEL
BUILD DEFERRED
REFRESH COMPLETE ON DEMAND
AS
SELECT
aolindividualid
,truvuebestadressid
,infirstname
,inmiddlename
,inlastname
,rownum row_number
FROM individual
WHERE
aolindividualid NOT EXISTS (
SELECT /*+ HASH_AJ */
aolindividualid
FROM individual_tmp
) ;

DBMS_MVIEW.Refresh('IND_UNMATCHED_MV', 'C');

THIS REFRESH FUNCTION IS WORKING FINE WHEN BASE TABLE HAS 50 MILLION ROWS .

BUT REFRESHING FOR 150 MILLION OF ROWS IT'S GIVING THIS ERROR :

ORA-12008: error in materialized view refresh path
ORA-12801: error signaled in parallel query server P014 ORA-01652: unable to extend temp segment by 64 in tablespace TEMP


My questions are :
1. Why it's indicating tablespace TEMP while I'm doing this materialized view in default tablespace ?

2.Does "NOT EXISTS " degrade the functionality of materialized view?

Any help will be appreciated ..
 
1. TEMP tablespace is used for sorting that in turn is performed according to your hint.

2. Any additional condition may degrade its creation. Though once having been created it acts like an ordinary table.

Regards, Dima
 
Sem - Ref 186-775308

Refreshing Materialized Views

Could you tell me what size is your temporary table space.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top