| Data Upload using DDL from new to old DB with fewer columns [message #61696] |
Tue, 18 May 2004 13:12  |
Mike
Messages: 417
Registered: September 1998
|
Senior Member |
|
|
How do I get Oracle to ignore additional columns on an upload from a newer DB to an older DB. They are essentially the same but the old one has fewer columns which I can live without in the old DB. Looking for as much info as possible in:re to spinning data back to old DB's. THANKS SO MUCH!!
|
|
|
|
|
|
| Re: Data Upload using DDL from new to old DB with fewer columns [message #61709 is a reply to message #61697] |
Wed, 19 May 2004 06:47  |
Mike
Messages: 417
Registered: September 1998
|
Senior Member |
|
|
I'm not sure if SQL Loader will ignore unneeded columns in the data, when going from a newer software version/framework we have created to an older software version/framework.
Also we have not really loaded our 1.4 data into an older 1.3.3 db.
The closest we have done is old 1.4 data into a new 1.4 db, and we had to manually change the load data.
I belive a SQL script could be created that would convert one into the other. For that matter, couldn’t we create a SQL statement that loads one db from another, without the need to export the data and re-import it?
We are currently using a db loading script that a colleague wrote, who is no loner with us, that will load and unload a database. However, this is only good between same version DB’s. We want to take data from a newer DB and transfer it to an older DB that has fewer “columns”.
We know how to run the load between like environments, but not the details behind it.
|
|
|
|
| Re: Data Upload using DDL from new to old DB with fewer columns [message #62837 is a reply to message #61709] |
Wed, 18 August 2004 09:51 |
Bob Shuster
Messages: 2
Registered: August 2004
|
Junior Member |
|
|
Hi Mike,
You can try FastReader from WisdomForce (www.wisdomforce.com). FastReader unloads Oracle tables into flat text file very fast(in my case 10 million records unloaded in 6 sec). At same time FastReader generates ctl files for SQL Loader. So if you will writes script that:
1) Run FastReader
2) Run ctl files that FastReader generates. So you don't need export/import data each time and it is really fast. One more thing: FastReader can to not lock tables during unload if you configure it. It can be very helpful sometimes when you are dealing with production database
Hope, it helps.
Bob
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
