Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Interesting (painful) Migration Problem (Nov 7.2.2.4.10 -> NT 7.3.3.0.0)

Re: Interesting (painful) Migration Problem (Nov 7.2.2.4.10 -> NT 7.3.3.0.0)

From: Al <al_at_work>
Date: 1998/04/01
Message-ID: <6ftppd$e3s6@piper.ncr.pwgsc.gc.ca>#1/1

This should be very easy.

Step 1. Create your DB on the NT box. Careful with your NLS settings.

Step 2. Define your tablespaces on the NT box.

Step 3. Import with ignore=y.

Now your done.

Joel Garry wrote in message <6fhh7d$esk$1_at_pebble.ml.org>...
>In article <351b2344.186281702_at_news.mindspring.com>,
> <nassif_at_mndsprng.cm> wrote:
>>hi,
>>
>>We've got an interesting and painful migration in progress.
>>
>>We're moving a ~8 Gigabyte 7.2.2.4.10 Database from a Novell 4.11
>>server to a 7.3.3.0.0 NT 4.0 Svc Pk 3 server.
>>
>>Yeah, I know, we're insane.
>>
>>Anyone got any experience with this?
>
>Well, I admit I haven't done that particular insanity. But I am
 obsessively
>and compulsively compelled to say, if the import is too slow, to consider
>dumping to a flat file (ie, spool and select statements) and use SQL*Loader
>on tables you've pre-created. Assuming you don't have too psychotic of a
>data set.
>
>Yes this is more work than exp/imp, but it may require less Prozac if it is
>faster overall. Look around for or write scripts for dumping to flat
 files.
>Be sure to order tables for relational integrity if you are using it.
>
>jg
>
>>
>>We have done the following:
>>1) exported the 7.2.2.4.10 DB to a dump file
>> (it's about 1.3 G)
>>2) Created a database on the new server
>>
>>Problems: The import program will try to create sys volumes instead
>>of lettered drives, so we can't just import it (plus we need to fix
>>some structural issues....)
>>
>>We have a plan:
>>a. Create tablespaces for the data, indexes, etc
>>b. Create the users on the new box with quotas in those tablespaces
>>c. Run the import and pray that each user's tables make it into the
>>new tablespaces
>>d. Rewrite and run scripts to recreate the constraints and procedures
>>that didn't make it
>>
>>Is there any way to make this any less difficult?
>>Any pitfalls to avoid?
>>
>>Any information you may have would be greatly appreciated...
>>Thanks much!
>>
>>Nassif!!
>>
>>
>>
>>
>
>
>--
>These opinions are my own and not necessarily those of Information Quest
>jgarry@eiq.com http://www.informationquest.com
>http://ourworld.compuserve.com/homepages/joel_garry
>"See your DBA?" I AM the @#%*& DBA!
Received on Wed Apr 01 1998 - 00:00:00 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US