Understanding the Requests Archival Utility

Using the Archival Utilities 23-13 8. When prompted to specify the mode of running the utility, enter 1 if you want to run the utility in online mode. Otherwise, enter 2 to run the utility in offline mode. 9. Specify the batch size, when prompted. The utility archives the request data and provides an execution summary in a log file. 10. On Microsoft Windows platforms, reset the short date format to the date format for your region or locale after you run the utility. Use the Regional and Language Options command in Control Panel to reset the date format. 11. Because the data from active request tables are removed, your DBA must analyze the active request tables and their indexes in order to update the statistics. Perform this step only if you are using Oracle Database as the database for Oracle Identity Manager.

23.3.5 Log Files Generated by the Utility

All the logs are written to the logs directory created in the current folder. Table 23–5 lists the log files generated by the utility.

23.4 Using the Audit Archival and Purge Utility

This section describes how to use the Audit Archival and Purge utility. It contains the following topics: ■ Overview ■ Prerequisites for Using the Utility ■ Preparing the UPA Table for Archival and Purge ■ Archiving or Purging the UPA Table Note: Batch size is a value for the number of records to be processed in a single iteration of archivalpurge also an internal commit at the database level. You must provide the batch size as an input parameter value while starting the operation of Archival Utilities at run time. This batch size by default is 2000. A higher batch size can be opted for, but this might require more resources from the database, such as more space from the TEMP and UNDO tablespaces. Table 23–5 Logs Generated by the DB Archival Utility Log File Description oim_create_request_arch_ta bles.log Created when the utility fails to create the archival tables oim_request_archival.log Created when the utility fails to create the procedures required for archival validate_date.log Created when the input REQUEST_CREATION_DATE is invalid oim_request_archival_sum mary_TIMESTAMP.log Contains the summary of the run Err_DB_Conn_TIMESTAMP _ATTEMPTNUMBER.log Created when the utility is unable to connect to the database with the credentials provided 23-14 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager

23.4.1 Overview

Continuous data generation in the Oracle Identity Manager database schema and the audit data growth results in a gradual increase in the storage consumption of the database server. The audit data is populated in the UPA table. The growth of data in the UPA table can pose disk space and maintenance issues. Therefore, old audit data in the UPA table must be cleaned or archived. To keep this disk space consumption in control, you can use the Audit Archival and Purge utility. This utility controls the growth of the audit data by purging the data in a logical and consistent manner. Oracle recommends partitioning of the UPA table on the basis of calendar year, which allows you to archive or drop partitions. The advantage of partitioning is that the old partitions can be archived or purged because Oracle Identity Manager does not use old audit data lying in those partitions. Oracle Identity Manager uses the latest audit data and the current calendar year data. Therefore, the UPA table is partitioned based on date range-partitioning approach by calender year using EFF_TO_DATE column. After partitioning, the latest audit data where EFF_TO_DATE is NULL, can be grouped in one partition, and there will be one partition for each calendar year. Oracle Identity Manager do not read or write into any other partitions except the latest and current year partitions. For instance, if you are using Oracle Identity Manager audit feature since 2005 and implementing the audit archive and purge solution in calendar year 2011, then you will have seven partitions after this exercise, assuming that you create a partition for each calendar year. In those seven partitions, Oracle Identity Manager will only read or write the following partitions: ■ The latest partition ■ The partition for the current year, for example 2011 All the previous year partitions can be archived and then purged. If you do not want to archive, then you can purge those old partitions. You can reclaim the space by archiving and purging those old partitions. You must keep the latest and current year partitions untouched for Oracle Identity Manager to continue working.

23.4.2 Prerequisites for Using the Utility

The following prerequisites must be met before or when using the Audit Archival and Purge utility: ■ Database partitioning is supported only on Enterprise Edition of Oracle Database. Therefore, to implement the audit archival and purge solution, you must run Enterprise Edition of Oracle Database. ■ The UPA table must be range-partitioned on the basis of calendar year. Other modes of partition methods are not supported. Note: ■ The audit archival and purge solution is only applicable to the UPA table. It is not applicable to audit reporting tables, which are tables with the UPA_ prefix. ■ The utility is compatible with Oracle Identity Manager release 9.1.0 and later.