|
Dave, I can't imagine that it would take very long to manually convert an Oracle script to a DB2 script. I have done it dozens of times and it runs in the minutes category. I would ask you Oracle people if they can get you the create scripts that Oracle stores. If you would like, post one, and I will post an annotated copy. Your biggest challenge is not in moving the data, but in the fundamental way that Oracle and DB2 work. Oracle schemas are tied to an owner. That is like a library. Every user has a schema. Most of the time references are qualified to the schema. That does not tie in well to the way that most people use libraries and DB2. David Morris Schemas --- me.... I would buy ERWin. Reverse engineer the database schemas into ERWin. ERWin establishes a connection to the database and reads the catalogs for the meta-data and builds the database in the tool. Correct and edit in the tool. Change the target database in the tool to the 400. Finish corrections and edits. Recreate the generation scripts Use OpsNav to execute the scripts against the 400. That puts the database there and documents it. Next, export the data from Oracle. Most DBs have import/export functions in multiple formats, including csv. Import the data (load) to DB2. On the 400, this is CPYFRMIMPF. These last two steps are much faster (loads and unloads) than other forms, like ODBC or DPropR or whatever, and are generally refered to in everybody's docs as load and unload. The 400 can do loads in parallel, given the resources.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.