Manually Remove Executions in AIQ

1. First, you must obtain the execution ID from AIQ.

2. From the AIQ homepage, click Analyze.

   

3. Then click Analyze link located at the right side of the execution which it is the desired one to remove, every single related data of executions older or equal to this one will be removed.

   

4. The execution number can be taken from the URL.

   

Oracle Instructions

1. Using an Oracle client, connect to your AIQ Oracle results database using the aiq user.

2. On the oracle client type: 'execute rexecuntil(0000000);' , replacing the 0000000 with the execution id of the first result that you want to delete. The process will delete that execution and will continue to delete all executions that are older than the specified one.

MySQL Instructions

1. Using any MySQL client, connect to your AIQ MySQL results database using the aiq user.

2. On the MySQL client type: ‘call rexecuntil(0000000);’ , replacing the 0000000 with the execution id of the first result that you want to delete. The process will delete that execution and will continue to delete all executions that are older than the specified one.

Important warning for the MySQL procedure

If saving space on the disk is what you are looking for, the previous procedure will not be enough, you'll get available space to persist new data but the size of the physical file will still the same, so, to achieve a shrunk file size perform as below.

• Backing up only data
  mysqldump --no-create-info -u username -hhostname -p dbname > backupsql.gz

• Restore procedure

• drop/create user and schema if needed using MySQLInitial.sql query file.

• Recreate all the AIQ’s database objects by performing MySQLAppvance.sql query file.

• truncate hashcodereference table ‘truncate hashcodereference;’

• Finally restore data by issuing as below
  mysql -u [user] -p [database_name] < [filename].sql

Troubleshooting

Error Code: 1419. You do not have the SUPER privilege and binary logging is enabled

If you get the above error while running the MySQLAppvance.sql script on AWS RDS, make sure that the RDS parameter group has the value 1 (ON) for the log_bin_trust_function_creators parameter. The RDS database MUST be rebooted for parameter changes to take effect.