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

Hi,

I think the easiset way would be to create a new database on the NT-Server taking int oaccount misfit storage clauses of the NW-database. Then create the well-sized tablespaces with the same names as you have in NW. If you've missized tables then issue all your modified create table statements to create empty tables, if all in NW is well-sized ommit this step. The last step will be the import. Set the Flag "Ignore Creation Errors" and all should go the right way.

On Fri, 27 Mar 1998 04:09:33 GMT, 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?
>
>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!!
>
>
>
>

--

Regards

Matthias Gresz    :-)

GreMa_at_T-online.de