7.10 Refreshing Temporary Tables

Some behavior detection patterns use the temporary tables as part of the detection process.

Logs

The log.category.REFRESH_TEMP_TABLE.location property in the <OFSAAI Installed Directory>/database/db_tools/mantas_cfg/categories.cfg file controls logging for this process. The system writes log information for this process to the following location:

<OFSAAI Installed Directory>/database/db_tools/logs/refresh_temp_table.log

Using Refreshing Temporary Tables

The BD ATOMIC schema defines these tables; the tables have corresponding views that are used to populate them. Prior to running these patterns, run the refresh_temp_table.sh script.

The script has the following calling signature: refresh_temp_table.sh <table_name> <view_name>

Where:

• table_name identifies the name of the table to populate.
• view_name identifies the name of the view to run to populate the table.

This procedure deletes all records in the target table prior to running the view to populate it. It then estimates statistics for the newly populated table. This procedure logs into the database with the user that the utils.miner.user property identifies in the <OFSAAI Installed Directory>/database/db_tools/mantas_cfg/install.cfg file.

Populating Temporary Tables for Scenarios

Scenarios typically depend on data management to complete processing. However the following scenarios depend on population of Temp Tables to populate data.

• IML/CU) Hidden Relationships
• (ML/AC) Networks of Accounts, Entities, and Customers
• (FR/AC) Networks of Accounts, Entities, and Customers
• (CST/AC) Customers Who Have Experienced a Large Loss Recently
• (CST/HH) Customers Who Have Experienced a Large Loss Recently

The Link Analysis scenario also depends on the network job creation before the sequence matcher part of the scenario runs.