Dear List,
We need to remove data from our database everyday, so we are plannning to have a scheduled process for this. But the case is that we cannot simply remove the data. This data has to be made available at a later time if required. So this is the process that we have designed.
- The background process would first insert all the required data from the main database to another database.
- Now if this successfull, it would be deleted from the main database.
- The selection criteria on which the data to be purged is found is a business requirement. It is based on some date, but we cannot partition the data based on the date, otherwise we could have done with paritioning and dropping the partition could have been easily done.
- The data in the second database would be archived in a normal sequence
- If any user request for the data already purged, the data would be read from the second database and shown to him.
Now the issue, the data that has to be moved or deleted in such a way would mount to more that 10 GB of data, so is this method a good solution. Can anybody suggest a better approach for doing this.
We are using Oracle 9i database, Weblogic Application server and Java client. We have list partitioned our database.
Any other data purging techniques would be greatly appreciated.
Regards
Prem Chandran N
