Gints Plivna ha scritto:
> Cosimo wrote:
>> Hi Dbas
>>
>> I ave a materialized view with logs:
>>
>> CREATE MATERIALIZED VIEW log
>> ON aspiag_scontrino
>> WITH PRIMARY KEY, ROWID (
>> dta_trunc_iscrizione,
>> dta_trunc_acquisto,
>> importo_number,
>> flg_superpremio,
>> tipo_punto_vendita,
>> provincia,
>> store,
>> produttore1,
>> produttore2,
>> tot_chance,
>> progr_chance,
>> group_id)
>> INCLUDING NEW VALUES;
>>
>> CREATE MATERIALIZED VIEW mv_aspiag_scontrino_general
>> REFRESH FORCE
>> START WITH SYSDATE
>> NEXT SYSDATE + 10/86400
>> AS
>> SELECT
>> COUNT(*),
>> COUNT(importo_number) count_importo,
>> dta_trunc_iscrizione,
>> SUM(importo_number) sum_importo,
>> flg_superpremio,
>> SUM(TOT_CHANCE) totale_inserimenti
>> FROM ASPIAG_SCONTRINO
>> WHERE PROGR_CHANCE=1
>> GROUP BY dta_trunc_iscrizione, flg_superpremio;
>>
>> The materialized view mv_aspiag_scontrino_general not refresh when a row
>> is inserted on table aspiag_scontrino.
>>
>> In the file init.ora ave:
>> job_queue_processes = 4
>> job_queue_interval = 60
>>
>> Where is the problem ?
>
>>From your question isn't clear whether it doesn't refresh MV at all, or
> it doesn't refresh it on commit?
>
> If it doesn't refresh on commit it is absolutely normal because you
> haven't said that :)
>
> Gints Plivna
> http://www.gplivna.eu/
>
it doesn't refresh MV after ten seconds (SYSDATE + 10/86400) or 60
seconds (job_queue_interval = 60).
It doesn't refresh anytime :-(
Refresh only if I drop the MV and rebuild...
Received on Wed Jul 12 2006 - 09:46:58 CDT
