Re: Data loading from production to development

Onkar,

Why you want some of the tables from production to development? When development team is working on a new release/enhancement/bug fixes, it should get the clone of production. However, you may want to get a smaller subset of the production copy (in terms of number of rows) for quick installtion in different servers.
What we do is we get full export from production once, scale it down by selectively deleting rows. Take a full export of this database for baseline production copy untill next deployment in production.

If your production database is too big for a export import process, clone it using physical backup, scale it down to 15-20 gb in size so that you can quickly inport in to different enviroments.

Sandeep

--
http://www.freelists.org/webpage/oracle-l