Data Loss Prevention

I am getting Corrupted incident received Code 1802

I work in a very big enterprise and we are currently on our 10th Database in Oracle at 33gb a piece. Slowly we are running out of space. I've done some reserach but the answers didn't seem to be very clear.

1. What can be done to reuse Tablespace? I've deleted 50k incidents and there wasn't any space free'd up. How do you TRULY purge tablespace. I understand that Oracle won't consolidate the free space but there doesn't seem to be any free space at all after deleting a large amount of incidents.

2. We do image monitoring through e-mail. If the image is harmless, what can I do to keep the incident but get rid of the image itself to help save on space?

Thanks!

You can search the DLP admin guide for Limit Incident Data Retention action.  Page 837.  

Hi,

This is one of the most painfull issues with DLP system (data is keep growing and demands more storage).

We udnerstood it one year ago, that we suddenly discover we are out of space, since DLP Tables took 250 GB!!!

This year we were smarter.

With the help of our briliant DBA's:
1. we took the tables

2. copy them to our test enviornment

3. load them to the app and ensure the data is correct

4. Then DBA took some actions in order to compress the data, which provide us another 100 GB on same table space

5. Then they did same process on production, Of course that it demands downtime

If you want, I can try and ask the the full procedure since i asked them to document it.

Anyway

what we are doing as well is to keep only 6 months incidents, we archive all other incidents and delete them (after we ensure that we have backup).

Once you delete incindets, some of the incidents will be written on the space which was used by the incidents you deleted (but not all of it, it's something related to how DLP built and Oracle tables)...

Good Luck

Hello,

 When you delete in incidents space is not really released by oracle, but at least you should not see any increase of tablespace space used as oracle will reuse available space.

So as other people said, it is nice (and sometimes mandatory for legal reason) to archive incidents (and so delete them from DLP) on a regular basis to avoid tablespace to increase too much and also for performance of DLP UI.

 Regards.

When you delete an incident from the interface it merely flags it as deleted.  The incident is then purged by the purging process on Enforce typically at midnight.  We have had the incident purging process quit working several times.  I would query the DB incidents table for all incidents flagged as deleted and make sure that the number reduces to zero overnight.  If this is not happening then none of the incidents are ever being deleted.