HP3000-L Archives

July 2003, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Charles Finley <[log in to unmask]>
Reply To:
[log in to unmask][log in to unmask], 25 Jul 2003 11:36:28 -0400627_iso-8859-1 Chevy: Weekend Update recognizes its obligation to present responsible
opposing viewpoints to our Editorials. Here with an Editorial Reply is Ms.
Emily Litella.

Emily: What's all this fuss I keep hearing about evil at Hewlett-Packard?
Now why would some Silicon Valley company want to bring more evil into the
world? Why, I thought that company liked to invent things but evil was
invented a long time ago. Personally, I thought that David and Bill were
really nice men. Now I come to find out that that they were playing good
geek/bad geek. Not that this honey-pot has any right to [...]39_25Jul200311:36:[log in to unmask]
Date:
Thu, 24 Jul 2003 19:18:18 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (91 lines)
Using our tools what we do is:

On the HP 3000:
1) Extract the IMAGE schema.
2) Extract the IMAGE data.
3) Transfer the schema definition and data to the target machine.

On the target machine:
4) Use the IMAGE schema to generate the various SQL statements needed to
build a "schema" on the relational platform.  This includes CREATE TABLE
statements, constraints (to establish and maintain master/detail
relationships), the creation of Index's to replicate IMAGE keys and
automatic master behavior, the creation of special indexes to replace
third-party indexing behavior.
5) Run the generated SQL scripts in order to create the database structures.
6) Run a DBLOAD program to load the extracted data above.
7) Use the new Oracle database.

Furthermore, if the machines are networked together it takes us about as
long to create an Oracle, DB2 or SQL Server database as it does to unload an
IMAGE database and load it onto another HP 3000.  After installation of a
few programs on the source HP 3000, you issue a command from the target
machine and it causes the schema and data to be extracted and placed in a
local directory.  You then issue a command to build an populate the new
database.  That's it, you're done!  Of course you end up with your data
stored in the same structure as it was on the HP 3000.  In other words,
there is no nominalization, etc.  On the other hand, you could migrate a
large number of databases very quickly.

If we can agree on the size of a sample database you could send us a store
to disk of an IMAGE database that's "not too big" and we'll do a sample one
for you for free.  The more complicated the database the better.  We will
return to you an Oracle database that you can simply restore into Oracle.
Our tools have additional features as well.  For example, you can identify a
field as a date field and have it stored that way on Oracle or change
character fields to VARCHAR's.  Of course our free offer is limited to an
across the board cloning database migration.

Our website is www.xformix.com propaganda has not kept up with our tools so
there is no mention of this separate capability on the site.  However,
you're probably more interested in results and tangibles than propaganda
anyway, so tell you what. If we can agree on the size of a sample database,
you could send us a store to disk of an IMAGE database that's "not too big"
and we'll do a sample one for you for free.  (That way you get to see if
we're pulling your leg.)  We will send you an Oracle database that you can
simply restore into Oracle.   We have additional features as well.  For
example, you can identify a field as a date field and have it stored that
way on Oracle or change character fields to VARCHAR's.

Charles Finley
Transformix Computer Corporation
Oceanside, CA
(760) 439-3146

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Jay Chandru
> Sent: Thursday, July 24, 2003 6:33 PM
> To: [log in to unmask]
> Subject: Data migration from Turbo Image to Oracle Apps (11i)
>
>
> Data migration from Turbo Image to Oracle Apps (11i)
>
> 1. Identify the databases and datasets that are to be migrated
> 2. Map fields of each dataset to fields in a relational database
> 3. Establish the relation ships in the relational database
> 4. Apply validations and correction routines to the data in relational
> database
> 5. populate oracle internal tables from the relational database
> 6. run oracle interface to populate the oracle apps tables
> 7. Repeat this process until the data migrated is clean
>
> If anybody has worked on a similar assignment or anybody who has an idea
> about the possible holes in such a migration or any damn knowledge of the
> same, pls. share
>
> Thank you,
> Jay
>
> _________________________________________________________________
> They are beautiful. They are in danger.
> http://server1.msn.co.in/Slideshow/BeautyoftheBeast/index.asp Our
> four-legged friends.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2