instead of hacking by hand - you could use a pretty printer
http://sourceforge.net/projects/pretoria
"makbo" <makbo_at_pacbell.net> wrote in message
news:3E9C9EF8.4040104_at_pacbell.net...
> guy wrote:
>
> [...]
> > Oracle started importing the data but I got a bunch of errors while it
was
> > trying to create some tables: "tablespace not existing" errors or
something
> > similar...
> [...]
> > How can I force the imp command to simply import all the stuff into the
> > default tablespace for the yyy user?
> [...]
>
> Did you get the errors on some but not all tables?
>
> Did the tables with errors all contain LOB columns?
>
> If so, you've run into a problem that has me stumped too...
> LOB storage is somewhat of a beast unto itself...every time I try to
> deal with it, whether it's partitioning, rollback/undo, or imp/exp, it
> seems to involve problems that don't crop up with other data types.
>
> In short, I don't think there is a way to import a table with LOB's into
> a different tablespace unless you pre-create the table with your desired
> storage parameters and then import with IGNORE=Y.
>
> IMP has an INDEXFILE option to write DDL to a file which you can then
> edit by hand to help with this process.
>
Received on Wed Apr 16 2003 - 13:50:16 CDT
