To fine tune the suggestions aready made, you probably don't want to drop all the table but just tables both in production and development/test. I would create a list of tables exported from production via export / show and use this to create a drop table script.
Mike -----Original Message----- Sent: Monday, January 06, 2003 4:29 AM To: Multiple recipients of list ORACLE-L The best method that I know is: 1) export from production. 2) drop user cascade in development or at least drop all tables. 3) create user in development. 4) import into development with indexes=n and constraint=n. 5) import again into development with rows = n and ignore = y. Step 4 will build all the tables with the data. Step 5 will build indexes and enable constraints. If the tables already exist in the target database then import will not recreate them. As for the data you may have constraints that reject the insert of records. Lets say you have a fact table and a lookup table that contain the branches names. On the fact table you have constraint: branch id must be in the branch table. When you import the fact table before the branch table all the records will be rejected because the branch table does not have the ids yet. Yechiel Adar Mehish -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Hand, Michael T INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
