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.
Received on Mon Feb 09 1998 - 00:00:00 CST
