Re: import issue

On Apr 27, 8:38 am, sam <samuel_st..._at_yahoo.com.br> wrote:
> I receive a dump of a schema from an external db and I got to import
> it on my db. This have to be done on a daily basis.
> Problem: There are objects on the dump specifically mapped to various
> tablespaces, that did not exists on my db, and when I do the import
> with the 'fromuser' 'touser', it does the imp from some objects,
> mapping them from the default tablespace of the user on my db, but it
> fails on the tables with *lobs...
> The first thing that come to mind is use an indexfile, create the
> structure and then perform the import, 'but' as this have to be
> performed on a daily basis, it could lead to a big problem when
> dealing with changes on the other side, this is a critical db and I
> cannot risk to have an error on this imp due to a change made on the
> structure of the other db...
> Maybe I am missing something, I made a workaround here, but id there
> some 'correct' way of doing that?

One way would be to use the indexfile and have a script that handles checking for proper tablespaces, if new ones are needed create them and let you know you need to pay some manual attention to the old ones. Shouldn't be too difficult given a modicum of shell or perl expertise. A lot depends on the specifics, such as which platform, do you have enough disk space to have new tablespaces for some period until you can look at it, the range of changes to be handled, how you handle stats creation, how long all this stuff takes, etc.

jg

--
@home.com is bogus.
"The only thing I can compare it to is to flying in dreams." - Peter
Diamandis, soon to be offering microgravity flights at $3500/per
through the Sharper Image - rides formerly known as the Vomit Comet.