Reviewing the Output Files Generated by the Task 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