7.6 Managing Data Retention Manager
Behavior Detection relies on Oracle partitioning for maintaining data for a desired retention period, providing performance benefits, and purging older data from the database.
The data retention period for business and market data is configurable. Range partitioning of the tables is by date.
The Data Retention Manager enables you to manage Oracle database partitions and indexes on a daily, weekly, and/or monthly basis (refer to Figure 7-1). This utility allows special processing for trade-related database tables to maintain open order, execution, and trade data prior to dropping old partitions. As administrator, you can customize these tables.
The utility accommodates daily, weekly, and monthly partitioning schemes. It also processes specially configured Mixed Date partitioned tables. The Mixed Date tables include partitions for Current Day, Previous Day, Last Day of Week for weeks between Current Day and Last Day of Previous Month, and Last Business Day of Previous Two Months.
The Data Retention Manager can:
- Perform any necessary database maintenance activities, such as rebuilding global indexes.
- Add and drop partitions, or both, to or from the date-partitioned tables.
Data Retention Manager provides a set of SQL procedures and process tables in the Behavior Detection database. A shell script and a configuration file that contain the various inputs set the environment that the utility uses.
Directory Structure
Table 7-16 Data Retention Manager Directory Structure
| Directory | Contents |
|---|---|
| bin/ | Executable files, including the run_drm_utility.shshell script. |
| lib/ | Required class files in .jarformat. |
| mantas_cfg/ | Configuration files , such as install.cfg and categories.cfg, in which you can configure properties and logging attributes. |
| logs/ | File <OFSAAI Installed Directory>/database/db_tools/ logs/DRM_Utility.log that the utility generates during execution. |
Logs
Oracle-stored procedures implement Data Retention Manager and conducts some logging on the database server. A configuration parameter in the install.cfg file controls the path to which you store the logs on the database server.
As the Data Retention Manager performs partitioning and indexing activities, it
generates a log that it enters in the <OFSAAI Installed
Directory>/database/db_tools/logs/DRM_Utility.log file (the logging
process time-stamps all entries). The log file contains relevant information such as
status of the various processes, results, and error records.
You can modify the current logging configuration for the Alert Purge Utility in the
<OFSAAI Installed Directory>/database/db_tools/log4j2.xml
files. For more information about logging in these configuration files, refer to
Managing Common Resources for Batch Processing Utilitiesand Appendix A - Logging.
Processing Flow
