Re: transportable tablespaces

Thank you Jonathan!
Now I'm really embarassed by asking it. But I really missed that "file location" link in my brains. :( Maybe I had too much Oracle theory the last days and left my common sense behind ... I will take this exam ASAP!!!

Susanne

"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> schrieb im Newsbeitrag news:1004522256.6545.1.nnrp-01.9e984b29_at_news.demon.co.uk...
>
> Tablespaces are obviously the 'easy' and convenient
> thing to use to specify what you want to export - but
> you can't specify them for the import as the target
> database won't know where to find the relevant
> files.
>
> Furthermore, a benefit of specifying files for the import is
> that you can change the names of files on the destination
> machine. Oracle works out automatically which new file
> names belongs to which tablespaces.
>
> The ability to list the tablespaces on the import is simply
> a 'belts and braces' approach to ensuring that you are
> probably importing the data you intended to import.
>
>
> --
> Jonathan Lewis
> http://www.jlcomp.demon.co.uk
>
> Host to The Co-Operative Oracle Users' FAQ
> http://www.jlcomp.demon.co.uk/faq/ind_faq.html
>
> Author of:
> Practical Oracle 8i: Building Efficient Databases
>
> Screen saver or Life saver: http://www.ud.com
> Use spare CPU to assist in cancer research.
>
> Susanne Bagl wrote in message ...
> >Sorry for bothering you with this question, but I'm preparing for OCP and
> >need some help to understand the transportable tablespace feature.
> >
> >During EXP I'm using TRANSPORT_TABLESPACE=Y and TABLESPACES=users,
indexes
> >and FILE=expdmp.dat to save structural information
> >With IMP I need TRANSPORT_TABLESPACE=Y and DATAFILES='(users01.dbf,
> >users02.dbf, index01.dbf, index02.dbf)' ...
> >
> >Why DATAFILES for IMP and not TABLESPACES (isn't the structural
information
> >about the exported tablespaces contained in the export-file?) Maybe this
> >question is stupid, but it's not logic for me. Looking it up on technet
> >doesn't make it clearer to me (the 1. and 3. paragraph are quite
> >contradictory to me):
> >
> >"You must specify DATAFILES.
> >TABLESPACES,TTS_OWNERS, FROMUSER and TOUSER are optional. The FILE
> parameter
> >specifies the name of the structural information export file.
> >
> >When you specify TABLESPACES, the supplied tablespace names are compared
to
> >those in the export file. Import returns an error if there is any
mismatch.
> >Otherwise, tablespace names are extracted from the export file."
> >
> >Can anyone using this feature in practise help me out?
> >
> >Thanks,
> >
> >Susanne
> >
> >
> >
> >
> >
>
>
Received on Wed Oct 31 2001 - 04:27:46 CST