Our application folks asked us to recreated Materialized views as extract from one database to another. Export is obviously out of question in 10g as it treats MViews as tables on creation (run into that before).
Why is export out of the question? Export is used ALL of the time to export materialized views.
You can export just the metadata or the data also.
So we are using SQL Developer DDL extraction for that and getting this message - unable to render MView... Anyone has any ideas?
What EXACT steps are you using: every selection and choice please?
Also what platform are you on?
DB Platform is RHEL 6.5 64bit.
SQL Developer 4.0.3 is 64bit Windows (running on my machine).
Export/import actually created materialized views as tables - so in order to create mviews, I had to drop tables first
Still, some of the views in original database SQL Developer fails to render. I've tried to use DDL export, DDL rendering - error's the same, can't render.
Message as follows:
-- Unable to render MATERIALIZED VIEW DDL for object BUD.SIT_EXT_VAL_GROSS with DBMS_METADATA attempting internal generator.
And the code still doesn't look right
You lack the privs necessary to use dbms_metadata package to generate the DDL, so we fall back to a 'best guess' which looks at the data dictionary to build the CREATE OR REPLACE.
I wonder though why this particular view - others in the same schema came out quite all right.
I've re-built almost a 100 of MViews, but not the ones with that "rendering" problem.