Home » Applications » Oracle Fusion Apps & E-Business Suite » 'Data Purge' functionality
'Data Purge' functionality [message #198096] Sat, 14 October 2006 17:24 Go to next message
mihirca
Messages: 6
Registered: September 2006
Junior Member
Dear All

I want to know about the 'purge data' functionality.

What does 'purge data' achieve? What are the benefits? What are the implications if it is not done....

Kindly advise

Regards
Mihir
Re: 'Data Purge' functionality [message #198269 is a reply to message #198096] Mon, 16 October 2006 06:22 Go to previous messageGo to next message
David.K.Dickson
Messages: 413
Registered: October 2005
Location: Surrey, England
Senior Member
mihirca wrote on Sat, 14 October 2006 23:24
What does 'purge data' achieve? What are the benefits? What are the implications if it is not done....

Purge Data moves transactions out of the main section of the database.

This keeps the database at a reasonable size. You only have immediately accessible the data that you need on a regular basis. This means that inserts, updates, queries and reports all run faster, which means that you can do more in the time available.

Failure to purge data periodically will result in a database that just grows and grows and grows. Eventually inserting or updating a single record will take 10 times as long as it does today, and queries and reports will take 10 times as long as they do today. It won't be much longer until it is 100 times longer.

If you use Archive and Purge, you can copy your data to another area (outside the main database but still accessible) before removing it from the database. In most countries there is a legal requirement to store all financial data for a specified period. In UK, I believe that it is seven years, so I would suggest that UK organisations should use Archive and Purge with all of their Applications and make sure that the Archive copies are retained for at least seven years.

Cool HTH

David
Re: 'Data Purge' functionality [message #456681 is a reply to message #198096] Wed, 19 May 2010 04:10 Go to previous message
suiren97
Messages: 48
Registered: May 2007
Location: Malaysia
Member
We understand data has to be archived and purged regularly based on each organization requirement.

Besides checking all related table count, is there a way to ensure such maintenance is done according to schedule in order to prevent database keeps growing?


Previous Topic: Default Journal Category
Next Topic: usage accelarator
Goto Forum:
  


Current Time: Tue Dec 06 04:52:52 CST 2016

Total time taken to generate the page: 0.10327 seconds