Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Exp/Imp and old storage clauses

Re: Exp/Imp and old storage clauses

From: Ron Rogers <RROGERS_at_galottery.org>
Date: Thu, 16 Nov 2000 16:11:05 -0500
Message-Id: <10682.122308@fatcity.com>


Kenneth,
If you are doing a full database export it should include all of the = users, grants, tables, and privileges. It does not do triggers if I = remember correctly. When you do the imports after you have built the new = tablespaces and tables to meet your requirements, just import IGNORe=3DY = and it will ignore the fact that the tablespaces and tables ecist and = import the data okay. If you have integrity constraints be sure to import = the tables on the proper order to populate the tables in the right order = for the intergity constraints.
  ROR m=AA=BF=AAm

>>> kenneth_r_fowler_at_groton.pfizer.com 11/16/00 03:37PM >>> List,

I have been migrating a few database to 8.1.6 (from 7.n.n) on Solaris = lately
and when I do this I have been using exp/imp so that I can apply some of = the
storage strategies outlined in the "How To Stop Defragmenting and Start Living" document. The basic method I am using is...

  1. Create new empty database that have tablespaces with appropriate = default storage clauses (initial extent, next extent as per the doc's suggestions etc etc).
  2. Perform full export of old database.
  3. Use imp .... indexfile =3D filename.sql to extract sql for tables, = indexes and constraints.
  4. Use a nasty sed script I put together to process the above extracted sql to rip out all of the storage clauses defined at object level and = change tablespace clause to whatever I want etc
  5. Create the tables from sql generated in step 3 and 4.
  6. Import row data into the preexisting tables
  7. Create indexes, constraints from sql generated in step 3 and 4.
  8. Perform a final import (ignore =3D y) to import grants and any other = stuff I may have missed (should hopefully not be anything).

This is quite tedious, especially all of the checking I need to do to = verify
that the sed script works as desired. Anyone know of an easier/better way to import objects and default to the tablespace storage clause (that is, leave off the object storage clause!).

I would really love import to have a switch that would do this for me. Anyone else find themselves jumping through the same hoops?????

	Ken

(Kenneth R Fowler)
(860) 732 0026 (Voice)
(860) 732 3689 (Fax)
(860) 715 8346 (Fax to Email)
(860) 599 8791 (Fax @ Home)
Clinical Systems DBA Support Kenneth_R_Fowler_at_groton.pfizer.com=20

--=20
Please see the official ORACLE-L FAQ: http://www.orafaq.com=20 --=20
Author: Fowler, Kenneth R
  INET: kenneth_r_fowler_at_groton.pfizer.com=20

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (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 Received on Thu Nov 16 2000 - 15:11:05 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US