And if all else fails (not that the advice already given will!), we have a
tool that can manipulate the DDL for the users objects VERY quickly and
easily, through a "rule based" change (e.g. Modify <ALL> tables storage
clauses within <USERS> schema to <TABLESPACE>):

http://www.cool-tools.co.uk/products/dbatool.html

It's free, have at it!

HTH

Mark

-----Original Message-----
Sent: 07 November 2002 14:44
To: Multiple recipients of list ORACLE-L


Extra security could be to give zero quota on other tablespaces.
-----Original Message-----
Sent: donderdag 7 november 2002 14:59
To: Multiple recipients of list ORACLE-L


I have a full export of user to where I need to import all his
objects/grants
but into a NEW tablespace.  What's the easiest way I can assure that
~everything~ is imported.  Will I need to use a combination of INDEXFILE
and other procedures or will a full export; drop tablespace; create new
tablespace; alter user's default tablespace; full import suffice for
all objects? Thanks for any tips.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Mark Leith
  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).

Reply via email to