Why Oracle task persistence database size isn't reducing upon running the Garbage Collector?

book

Article ID: 48977

calendar_today

Updated On:

Products

DIRECTORY CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On SECURITY MISC CODES SINGLE SIGN ON - LEGACY CA Data Protection (DataMinder) CA User Activity Reporting

Issue/Introduction

Description:

Run specific commands in Oracle in order to make the size reduction take effect.

Solution:

You might notice that the Oracle task persistence database size remains unchanged after running the Garbage Collection.

The Garbage Collection is supposed to remove much data from the database so its size is expected to decrease.

On Oracle systems it is necessary to also execute some Oracle commands if you wish to reduce the amount of disk space after doing a clean up submitted tasks or garbage collection.

The commands to run are after the execution of the garbage collection are:

- ALTER TABLE OBJECT12_5 ENABLE ROW MOVEMENT;       
Table altered 
- commit;
Commit complete
- ALTER TABLE OBJECT12_5 MODIFY LOB (OBJECT) (SHRINK SPACE);
- commit;

Environment

Release:
Component: IDMGR