Following on-commit snapshots not refreshed :

More fun with 10g->11 g migrations.

We datapumped a 10g on-commit mview over a db link to an 11.2.0.2 database (as part of a whole database move) - all seemed fine - no errors until in the alert log we began to see

Following on-commit snapshots not refreshed :
XXX.XXX

It seems that datapump (possible exp/imp does the same thing) has left the mview with a STALENESS value of IMPORT.

A full refresh of the Mview has since fixed it

0 comments:

Post a Comment