Materialized View Log Not Registering/Purging in 184.108.40.206 Master; SLOG$ Entry Missing
(Doc ID 1155843.1)
Last updated on AUGUST 04, 2018
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 11.2]
Information in this document applies to any platform.
- Creating a distributed materialized view in a mview database < 11.2 with an 22.214.171.124 master database seems to succeed (no errors), but the mview logs are no longer purging in the 126.96.36.199 master database.
- Manually registering the materialized view has no effect.
- When the following query is run, it does not show that the materialized view is registered:
COLUMN owner HEADING 'Owner' FORMAT A6
COLUMN name HEADING 'Mview Name' FORMAT A30
COLUMN snapshot_site HEADING 'Mview Site' format a30
COLUMN current_snapshots HEADING 'Last Time Refresh' format a21
select l.snapshot_id, owner, name, substr(snapshot_site,1,30) snapshot_site,
to_char(current_snapshots, 'mm/dd/yyyy hh24:mi:ss') current_snapshots
from dba_registered_snapshots r, dba_snapshot_logs l
where r.snapshot_id = l.snapshot_id (+)
>> no rows selected
Master was upgraded to 188.8.131.52. Mview database is 10.2.0.4, but bug indicates the issue will occur with mview databases < 11.2. The materialized view log was purging until the materialized view was dropped and recreated.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document