Re: Data Offloading

You could do lots of things:

• You could create a view with the conditions you wanted, and export the view (I think)
• You could write a fast data dump routine in either pro*c or OCI and then dump the view -- the dump program should also create a SQL*loader control file for easy loading if/when needed.
• You could partition the table in such a way that the old data would be in its own partition -- but it sounds like your purge condition might be too complex for this. "Kerri Adams" <x97cjq_at_stfx.ca> wrote in message news:3937F160.C0403CF0_at_stfx.ca...
  > Hi,
  > I am currently working on a project where we have to offload data from
  > the production database and store the data on tapes. In the future, if
  > the data is ever requested, it has to be either imported back into the
  > production database or imported into a dummy database so that it can be
  > queried. Since we only want to export certain rows from a table there
  > are extra steps involved with using the export command. The only way
  > that we have come up with to accomplish this would be to do the
  > following steps:
  > 1. Create a new table containing only the rows that need to be exported
  > using
  > the CREATE AS statement.
  > 2. Add the constraints to the newly created table.
  > 3. Export the new table.
  > 4. When export has terminated successfully, drop the new table.
  > 5. Delete the rows that have been exported from the data tables.
  > I was wondering if anyone knew of alternate ways of offloading data onto
  > tapes that can be later loaded back into a database without having to
  > use the export/import commands. Or if anyone knows of an alternate
  > method of accomplishing this by using the export/import commands.
  > Thanks,
  > Kerri Adams
  >
  >
  >
  >