sorry, ignore my crap
"David Sharples" <david.sharples3_at_ntlworld.com> wrote in message
news:Ibg%9.3091$Uo5.36682_at_newsfep4-gui.server.ntli.net...
> you can import into the new db then move the tables into the different
> tablespaces. This will nto invalidate your indexes because you are not
even
> touching them.
>
>
> "Glen A Stromquist" <glen_stromquist_at_nospam.yahoo.com> wrote in message
> news:Njf%9.71834$c41.2292908_at_news2.telusplanet.net...
> > I am replacing a machine with a small database on it, so far I have
> created
> > a "blank" database on the new machine with just the tablespaces matching
> > the one I'm going to replicate. The twist to this is that on the
original
> > database the tables somehow wound up in the index tablespace when it was
> > built by the people who put the application in place.
> >
> > Whats the best way for me to get this rectified? I was thinking just
> import
> > it then issue a alter table move tablespace for all the affected tables,
> > but I've never had to use this before, I am assuming that once this was
> > done I'd have to either rebuild or recreate all the indexes in the
schema
> > as well?
> >
> > Or should I create all of the tables in the new schema first, then
import?
> > I actually did a quick test run of this, but got dozens of constraint
> error
> > messages, so I'd also have to write a script to disable all the
> constraints
> > before doing the import.
> >
> > Time is of the essence for this, as this is supposed to be a 24-7 db and
> > although I picked a "quiet" time to do this, I want to keep it as short
as
> > possible, which means taking an export from the one in place now just
> > before I take it offline and importing it into the new one.
> >
> > anyone have any better ideas?
> >
> > TIA
> >
> >
>
>
Received on Sun Feb 02 2003 - 17:51:44 CST
