INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

archiving data from one schema to another

archiving data from one schema to another

(OP)
All, I am using Oracle 11g and Toad and I am planning a migration of data from one schema to another.
The data is order data that is old and we want to archive the data to another schema.

Copying the data is easy enough. But, planning the removal of the data from the current production schema, that's another matter.

There are some 15 different tables involved with various dependancies.
Is there a tool / method that can be used to determine the order in which records are deleted or is the common practice to disable the keys until after the deletions are finished?

David Pimental
(US, Oh)

RE: archiving data from one schema to another

Just curious, Is there a pressing reason to remove the old data. For reporting and data analysis it nice to have the older data and oracle certainly doesn't care. With proper indexing and/or partitioning accessing a billion records is as fast as accessing a 100.

Bill
Lead Application Developer
New York State, USA

RE: archiving data from one schema to another

(OP)
Well, the biggest problem is that at least some of the data will be replaced.
We add Institutional Records to our database and every 6 months to a year we get the latest update from a 3rd party.
So, we need to wipe out records that we haven't used and load the new batch.

I hope that answers your question.

dpimental

David Pimental
(US, Oh)

RE: archiving data from one schema to another



The best way to deal with such requirements would be to partition the table(s).
If you store each partition in their own tablespace, you can then easily detach the tablespace using transportable tablespaces method and attach to a "reporting" instance (db).
noevil

----------------------------------------------------------------------------
The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close