Problem: Fail to run session data integrity check for *nix sessions generated before DB rotation
1. In a new an installation, were the active Audit Store DB has the "Session integrity check" feature enabled, configure Audit Management Server and one Unix agent and verify they are working well.
2. Log into the Unix agent with root as well as a normal AD user and generate some "Completed" sessions, and generate some "In Progress" sessions.
3. Without restarting the Audit Management Server, create a new active Audit Store DB and enable the "Session integrity check" feature.
4. Continue to run some commands in the terminal of the "In progress" sessions, then exit the session.
5. Restart Audit Management Server or wait about 15 minutes, then check session data integrity on any of the sessions.
Cause: This issue is intermittent. When calculating the signature of a session (using thumbprint or thumbprints), the Audit Manager retrieves the sessions in bulk. The SELECT query that does this only orders the results by SessionId. In most cases, when the results are returned, they're sorted correctly but there's no guarantee that all records/rows returned for a session will be in a specific sorted order (e.g. by Id column). The order used to compute the signature may not match the order used to verify the signature thus resulting in a data integrity check failure.
"It will pop up a dialog with the message "Session data integrity check failed because the computed signature does not match the signature in the database."
Resolution: It is fixed on suite 2017.3.