Re: local copy of remote database -- how to solve this case?

On Thu, 31 May 2007 21:31:04 +0200, T-BAG <T-BAG_at_prisonbreak.invalid.com> wrote:

>Guys, thanks for all the input in this thread. I think I'll try
>materialized view approach.
>
>I created a query that "generates" the script which i can run locally:
>
>select 'CREATE MATERIALIZED VIEW ' || t.TABLE_NAME || ' AS SELECT * FROM
>' || t.TABLE_NAME || '@DBLINK;' || chr(10) from all_tables t where
>t.OWNER = 'ABC' and t.NUM_ROWS > 0
>
>and now I am stuck with indexes. is there a similar solution to write a
>query that could "generate" the script used to create indexes locally as
>they appear on the remote database?
>
>and my second question is about LONG type columns: will the appear
>properly in the materialized view or creating materialized view will be
>impossible with such colums?
>
>I would greatly appreciate your help.
>
>thanks,
>T-BAG
1 Oracle recommends against using the * wildcard in views. This is because the * will be resolved on view creation 2 Use dbms_metadata may be in conjunction with a decent editor, supporting regular expressions
3 Obviously LONG won't make it in a view, as they have been desupported in the previous century.

-- 

Sybrand Bakker
Senior Oracle DBA