000038168 - How to manage database growth in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jan 2, 2020
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000038168
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: All
 
IssueOver time the RSA Identity Governance & Lifecycle Oracle database can grow significantly in size and become fragmented which can have a negative effect on overall database performance and disk space usage. Factors contributing to database growth and fragmentation are database modifications (inserts, updates, deletes), little to no data purging, and poor design or misconfiguration.

This RSA Knowledge Base Article explains how to manage the RSA Identity Governance & Lifecycle Oracle database growth and fragmentation with the use of Oracle tools and RSA Identity Governance & Lifecycle application features.

Here are a few of the reasons why this management is recommended:
  • To coalesce data. When there are deletes on a table, the rows become spread out in a data block in the table. This honey-combing will hurt performance during inserts as Oracle will try to find any existing space that can be used prior to allocating new space.
  • When data is removed from a table in Oracle, the database retains the space that had stored the deleted data. As a result, after removing data, the system may not see a significant change in performance, because some SQL statements scan the empty blocks. Further, no disk space is reclaimed since it is still retained by the tablespace. This is particularly true when using the data purging and archiving features in RSA Identity Governance & Lifecycle which remove large amounts of data.
  • Oracle uses b-tree indexes and similar to a table, when data is deleted, the leaf blocks of the index will be maintained even though they may be empty. They will only be reused if there is data that matches that leaf.. So a primary key will never have another value that matches the leaves since it is unique. Therefore you have data blocks that will never be reused. An additional problem with this is that a full index scan will have to go through and read the empty blocks.
  • Improve performance in the user interface.
  • Reduce the size of a database backup and the time it takes to perform a backup or a restore of the database.
  • Reduce the time it takes to perform database statistics.
ResolutionDatabase size and performance can be controlled by:
  • Removing unnecessary data
  • Reclaiming unused database space
  • Reducing fragmentation
How these tasks are accomplished in RSA Identity Governance & Lifecycle depends on your RSA Identity Governance & Lifecycle version. 
 

7.1.0, 7.1.1



  • Data Archiving (Admin > System > Data Management tab > Archiving)

Starting in 7.1.0, RSA introduced a new administrative feature called Data Archiving. From the online help:


You create a data archive to remove older data from active use within the RSA Identity Governance and Lifecycle system, while retaining a backup of the data to adhere to internal data retention policies or for auditing purposes. Archiving data reduces the size of the database and the resources needed by the database. When you create a data archive, data that meets the archive criteria is backed up to an Oracle Data Pump backup file and then purged from the system. As part of the archive process, archived data is completely removed from the system and cannot be accessed or seen anywhere within the RSA Identity Governance and Lifecycle user interface.

Benefits: Use of this feature frees up space but no space is actually reclaimed until segment advisor is run. (See below.)



  • Data Purging (Admin > System > Data Management tab > Purging)

Starting in 7.0.1, RSA introduced a new administrative feature called Data Purging which deletes unneeded data.

Benefits: Use of this feature frees up space but no space is actually reclaimed until segment advisor is run. (See below.)


  • Segment Advisor

If you are on RSA Identity Governance & Lifecycle 7.1.0 or above, please see the section entitled Database Segment Maintenance on page 32 of the RSA Identity Governance & Lifecycle Database Setup and Management Guide for V7.1.1 for instructions on running segment advisor. (Note: Even if you are on 7.1.0, use the 7.1.1 guide.)

Benefits: Use of this feature reduces fragmentation and reclaims unused space. No data is removed.


  • Database export followed by a database import.

For more information on performing a database export/import, please see RSA Knowledge Base Article 000038174 -- How to backup (export) and restore (import) an RSA Identity Governance & Lifecycle Oracle database.

Benefits: all fragmentation and reclaim all unused space in the database. No data is removed.


7.0.1, 7.0.2



  • Upgrade

It is recommended that you upgrade to the latest version of RSA Identity Governance & Lifecycle to take advantage of both Data Archiving and Database Segment Maintenance both available in RSA Identity Governance & Lifecycle 7.1.0 and up.


  • Data Purging (Admin > System > Data Management tab > Purging)

Starting in 7.0.1, RSA introduced a new administrative feature called Data Purging which deletes unneeded data.

Benefits: Use of this feature frees up space but no space is actually reclaimed until segment advisor is run. (See below.)


  • Segment Advisor

Please see RSA Knowledge Base Article 000038301 -- How to run Segment Advisor in versions 7.0.2 or earlier of RSA Identity Governance & Lifecycle for information on how to run segment advisor in these versions.

Benefits: Use of this feature reduces fragmentation and reclaims unused space. No data is removed.


  • Database export followed by a database import.

For more information on performing a database export/import, please see RSA Knowledge Base Article 000038174 -- How to backup (export) and restore (import) an RSA Identity Governance & Lifecycle Oracle database.

Benefits: all fragmentation and reclaim all unused space in the database. No data is removed.


7.0.0 and below



  • Upgrade

It is recommended that you upgrade to the latest version of RSA Identity Governance & Lifecycle to take advantage of both Data Archiving, Data Purging, and Database Segment Maintenance all available in RSA Identity Governance & Lifecycle 7.1.0 and up.


  • Data Purging

Please see RSA Knowledge Base Article 000031223 -- How to purge table data prior to version 7.0.1 in RSA Identity Governance & Lifecycle for ways to purge data from the RSA Identity Governance & Lifecycle Oracle database.


  • Segment Advisor

Please see RSA Knowledge Base Article 000038301 -- How to run Segment Advisor in versions 7.0.2 or earlier of RSA Identity Governance & Lifecycle for information on how to run segment advisor in these versions.

Benefits: Use of this feature reduces fragmentation and reclaims unused space. No data is removed.


  • Database export followed by a database import.

For more information on performing a database export/import, please see RSA Knowledge Base Article 000038174 -- How to backup (export) and restore (import) an RSA Identity Governance & Lifecycle Oracle database.

Benefits: all fragmentation and reclaim all unused space in the database. No data is removed.

 
 

Attachments

    Outcomes