Cleaning LOCKDATA Database Table

This article details the steps to clean the LOCKDATA table for Infogix Assure

Please note, though this article details the proper steps to clean the LOCKDATA table, this process should not be followed unless explicitly advised to by Infogix

The LOCKDATA table is an Infogix Assure database table where entries will continuously be coming and going, lasting no more than a couple minutes. When something gets "stuck" we may clean this table, though this should only be performed after engaging Infogix support.

Cleaning this table will need to be done with assistance from your DBA ( or someone with appropriate access to the database tables, capable of performing delete statements ). A couple things to be aware of prior to removing any entries from this table.

1 ) Since the LOCKDATA table is constantly being written to, the JVM / cluster should be fully offline prior to any updates performed against the table. This will avoid any corruptions, or impact to running controls.

2 ) When the JVM / cluster is fully offline, ideally this table should already be clean. If there are items remaining in the table, despite the application being offline, this is a strong indicator that one or more of your controls had an issue during execution ( and may or may not currently be in -1 status due to this ).

With the JVM / cluster fully offline, and partnering with both Infogix support and your DBA, the "clean up" process may be performed ( simply remove any lingering items from this table ).

Please note, It may be advised to take a screenshot of the "stuck" items prior to removal. This will allow a record of item(s) that may need to be follow up on with the team, ensuring what caused the issue does not resurface.

Sometimes, after clearing the LOCKDATA table a control will still show the "-1" status in Results By Control Point. This does not mean that the control is still running. See this article for more information: Controls stuck in -1 status stay in -1 status after a restart