Author Topic: Delete large volume of data from OnDemand  (Read 3922 times)

pjguillory

  • Guest
Delete large volume of data from OnDemand
« on: December 22, 2008, 01:18:05 PM »
Has anyone ever had to delete large quantities of data from OnDemand?  We have about 365 million documents -- that is the number of individual rows in the application group tables.  These were loaded in larger batches -- sometimes up to 10,000 documents in one batch.  The size of this data in the our cache folders is about 480 GB.  These are associated with 7 application groups which will not need to exist after this data is removed.

We are running OnDemand v7.1.2.11 on Solaris.  Our data is in cache only.

We've used "arsadmin unload" for deleting several batches at once, but never for this volume of data.  Is this the best option? 

If we just delete the application groups, I believe that would probably drop the associated database tables, but would that remove the data in cache also? 

What about the impact while we're unloading/deleting all of this data?

Thanks!

Paula Guillory
Chevron Information Technology Company




rick

  • Guest
Re: Delete large volume of data from OnDemand
« Reply #1 on: December 24, 2008, 11:03:03 AM »
Paula,

Here are the choices...

1. Check if the documents have crossed their expiration period has be crossed then it is a better idea to run ARSMAINT manually, which would delete the data automatically.

2. If you require all the data to be in the application group then it would be better you delete the application group.

3. If you require some of the data to be deleted in the application group, then it is better to collect the load ids of all the loads and run it as a batch script in the host side scripting using arsadmin.

The impact of deleting/unloading could be you can never get back those data :)

rbarrenechea

  • Guest
Re: Delete large volume of data from OnDemand
« Reply #2 on: December 01, 2009, 01:21:42 PM »
Paula:

Key question here is do you need any of the data on the application. If the answer is no, then delete the application (Backup first). Then run the cache maintenance process so it complete a full clean (release) of the space, plus a Database re-org and statistics.

Impact out of no access to this data anymore your database will be quite busy will running the process.