Re: Refreshing Data in the Clone Database

Hi,

    I can tell you're a newbie ;-)

    Just rerun the IMPORT with IGNORE=Y in your parameter list. If the table definitions in the production database have been altered you will get errors in those table. You will have to alter the tables in the clone database to match production and then rerun the IMPORT (with IGNORE=Y) and just import the bad table(s). You will also have to manually drop any tables and indexes which have been dropped since the last export . New tables and indexes will be created by the IMPORT utility.

    Pick up a copy of Kevin Loney's Oracle DBA Handbook from Oracle Press Osborne/McGraw-Hill and read it -- then reread it -- then read it again.

regards

Jerry Gitomer

popbui_at_usa.net wrote in message <7j3ma2$neq$1_at_nnrp1.deja.com>...
>Hi.
>I'm a new Oracle DBA and need help in refreshing data in a clone
>database without shutting down the production database and do the
>cloning again.
>I only have the full database export from production database and I need
>to refresh data in the clone database once a month.
>I tried to do the import from production database export and got some
>errors because the tablespaces, user's objects already existed.
>Which will be the easy way to do it?.
>1. Export users's objects and then truncate and drop all users (there
>are about 100 users) before doing the import.
>2. Truncate and drop all users and then doing the import from full
>database export (will get some errors because some tablespaces,
>datafiles, users, objects already existed).
>Any suggestions, helps, options would be appreciated.
>Thank you very much.
>
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.
Received on Thu Jun 03 1999 - 11:40:08 CDT