If you have enabled user history, details for all login attempts using a risk-policy or a device fingerprint policy are recorded in the database. This might result in huge data and occupy a large space. It is recommended to delete the entries periodically after you complete the analysis.
Deleting Entries from MS SQL Server
Go to Start > All Programs > Microsoft SQL Server 2016 > SQL Server Management Studio.
Connect to the database engine.
Expand Databases, you can see the netiq_risk database.
Click New Query.
To check the number of entries in the usrtransaction table, select the following command and click Execute.
Select * from dbo.risk_usrtransaction;
To delete entries, select the following command and click Execute:
Delete from dbo.usrtransaction;
NOTE:This command deletes all entries in the table. If you want to delete a specific range of entries, use the appropriate SQL command.
Perform step 5 and 6 for the device fingerprint table (device_fingerprint) also.
Deleting Entries from MySQL Server
Connect to MySQL Server installed on Linux by using the MySQL client:
mysql -u root -p password
Connect to the use netiq_risk database.
use netiq_risk;
List the tables. The usrtransaction table is listed in the list of tables.
show tables;
Delete entries.
delete from usrtransaction;
NOTE:This command deletes all entries in the table. If you want to delete a specific range of entries, use the appropriate SQL command.
Perform step 4 for the device fingerprint table (device_fingerprint) also.
Deleting Entries from Oracle Server
Open Oracle SQL Developer.
Right-click Connections and select New Connection.
Connect to the database engine.
Expand Connections, you can see the netiq_risk database under.
To check the number of entries in the usrtransaction table, select the following command and execute:
Select * from usrtransaction;
To delete entries, select the following command and execute:
Delete from usrtransaction;
NOTE:This command deletes all entries in the table. If you want to delete a specific range of entries, use the appropriate command.
Perform step 5 and 6 for the device fingerprint table (device_fingerprint) also.