Re: Tablespaces and Export/Import

In article <01bd356e$94689b00$b42fe4c7_at_SAMHC180.sys.eds.com>, Steve Sochacki <steve.sochacki_at_exmi01.exch.eds.com> wrote:
>I have a database on one physical server that has two drives, C: and D:. I
>have different tablespaces distributed across these drives. I did a full
>database export and went to import it on another server (which is RAID)
>with 5 drives and the same tablespaces spread across all 5. When the
>import runs, I get error mesages stating it can't create some directories,
>loads some of the tablepsaces correctly but most of the tables end up in
>the USER tablespace. The whole database is imported and works correctly
>but I lost the efficiency of having the indexes and data on separate
>drives. Is the import smart enough to look for the physical drives (C & D)
>and ignore the tablespaces on the other drives? Is there a better way to
>move all the database objects (stored procedures, tables, synonyms.....)
>than an export/import? Any help would be appreciated.

You may need to alter user of the schemata before they are exported to have the default tablespace you want. I've noticed a tendency for the temp tablespace to not be correctly defined, especially. Also, you might want to check out the rows=N on import to preallocate the space, then alter table parameters like next and maxextents unlimited before importing with ignore=y and rows=y. Read through your utilities manual again about imp/exp.

See if your volume manager has a way to put the tablespaces in one spot or another.

>
>

-- 
These opinions are my own and not necessarily those of Information Quest
jgarry@eiq.com                           http://www.informationquest.com
http://ourworld.compuserve.com/homepages/joel_garry
"See your DBA?"  I AM the @#%*& DBA!