Question

I am facing a major issue in a production environment where i had introduced a materialized view with a view log in order to refresh on commit to the master table. I tested this out with sql developer and it works perfectly.

But when the underlying table is updated using my application which is using iBatis to commit to the table, the materialized view is not getting updated with the new values.

Can anyone tell me what might be the issue here?

Appreciate your help in this regard

Was it helpful?

Solution

First, look at Determining the Fast Refresh Capabilities of a Materialized View. That indicates what types of fast refresh are available.

Then find the exact SQL statements used by both contexts, compare them and see if their difference are related to any of the POSSIBLE = 'N' rows in MV_CAPABILITIES_TABLE.

Here's a wild guess: in SQL Developer you're using a single INSERT statement, but iBatis is using a combination of INSERT and UPDATE. REFRESH_FAST_AFTER_INSERT = Y, but REFRESH_FAST_AFTER_ANY_DML = N.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top