Delete tab, Archive Request Editor

Use this tab to provide the name of a control file and parameters for deleting archived data. This tab is not available if you select Defer Delete after Archive on the General tab.

Archive Request Editor with Delete as the active tab. The elements of the Delete tab are described as follows.

Control File

Enter the name of a control file. During the process, this file is used to track the deletion process and record the success or failure for each row in the archive file. Control files have a .cf extension by default. If you do not specify a path for the Control File, the process uses the default data directory defined in personal options. If the control file already exists, a dialog prompts you to confirm that you want to overwrite the file when you run the archive request. Use a personal option to disable this feature.

You can browse the contents of an archive or control file by clicking Utilities > Browse or by right-clicking and clicking Browse in the shortcut menu.

Delete Options

Lock Tables
Select this check box to lock database tables during processing. A table is locked until all rows for that table in the archive file are processed. Lock tables to ensure that other database activity does not contend with the delete process. Locking, however, prevents other users from accessing tables involved in the delete process. If a product option prevents you from locking tables, this option is disabled.
Compare Row Contents
Select this check box to compare rows of data in the Archive File with rows in the database prior to deletion. Rows are deleted from the database that exactly match rows in the Archive File, and rows that do not exactly match are discarded and noted in the Control File. If you clear this check box, the row comparison is not performed, and rows can be deleted from the database that do not exactly match rows in the Archive File. (This check box is selected by default.)
Include LOB columns in row comparison
This option is available only if Compare Row Contents is selected. Select this check box to include LOB columns in the row comparison. Clear this check box to exclude LOB columns from the row comparison. (This check box is selected by default.)
Note: Clearing the row comparison check boxes might improve performance significantly; however, you risk losing any updates to the data in the database since the archive was performed. Also, you are not warned if, for example, if a row in the archive file does not exist in the database.
Commit Frequency
Number of rows to delete before committing the changes to the database. Frequent commits keep locking to a minimum, but may slow the process. If the process ends abnormally, click Utilities > Restart/Retry to resume processing from the last commit point. The commit frequency is a number from 1 to the maximum limit specified in product options. To use the maximum limit, clear this box.
Generate Statistical Report
Select this check box to include statistical information for the delete process in the archive process report. (For details, see Statistical information.) Statistical information can indicate whether you can improve performance by overriding the default method (scan or key lookup) of accessing a table. (For details, see Table Access Strategy.)
Discard Row Limit
Enter the number of rows that can be discarded while deleting rows during an archive process. The process stops after the specified number is reached and all rows in the array are processed. To allow an unlimited number of rows to be discarded, specify zero (0) or leave blank.
Note: Discard Row Limit is an approximate value due to array processing for the delete process. For example, assume the discard limit is set to 50 and the array supports 200 rows for a given table. If the first 50 rows fail, the DBMS continues to process the remaining 150 rows in the array, before evaluating the discard limit. (The number of rows that can be deleted in one call to the DBMS depends on the size of the row.)
Database Connections
Increase the number of concurrent database connections for the archive process. Increasing database connections improves performance by allowing multiple threads to archive rows concurrently. This option is available only if Maximum Database Connections in product options is 2 or greater.

To increase the maximum number of connections, select an even number from 2 to the site maximum as specified in product options.



Feedback