Re: Export for Upgrade

"Richard Foote" <richard.foote_at_bigpond.com> wrote in message news:J_Ao9.48689$g9.140543_at_newsfeeds.bigpond.com...
> Comments at end
>
> "Chuck" <chuckh_at_softhome.net> wrote in message
> news:anulil$hn8oa$1_at_ID-85580.news.dfncis.de...
> >
> > "Jonathan Bliss" <bliss_jonathan_at_hotmail.com> wrote in message
> > news:6yjo9.503$Eb6.59991_at_newsfep1-gui.server.ntli.net...
> >
> > > Thanks for this, I'll give it a go. As for the import, if the 8.1.7
> > 8import
> > > won't read it, I don't see why I cannot add my windows box to my
> tnsnames
> > on
> > > the Unix box and run the 7.2 import from the Unix box.
> > >
> > > Jonathan
> > >
> > >
> >
> > You'd still need to be able to access the export file from the unix box
so
> > you'd either need to store the file locally, or use the same technique
> (i.e.
> > a named pipe) to pipe the data directly from the exp utility into the
imp
> > utility. Also if you do use the 7.2 import utility against an 8i
database
> > you are probably going to run into problems with imp not recognizing the
> > catalog objects it needs. If it complains run the 7.2 catexp.sql script
> > against the 8i database and try the import again. When finished be sure
to
> > rerun the 8i catexp script against it to put the catalog back the way it
> > was.
> >
> >
>
> Hi Chuck,
>
> Ouch, not what I would recommend ....
>
> Running the 7.2 export utility against the 8i database is the only way to
go
> here. By definition, it will ensure only objects recognisable to the 7.2
> database are exported, that's the whole point. What use is a Materialized
> View in 7.2 ?

I think you (or I) are confused. The object here is to get data out of a 7.2 database into an 8i database, not the other way around. Received on Tue Oct 08 2002 - 08:49:23 CDT