Found an unmanaged process that is causing long transaction

Explanation

The transaction sentry determines that an outside process, such as a database replication issue, maintenance script, auto update, or command line process, or a transaction is causing a database lock. Most processes cannot run for more than an hour. Repeated occurrences with the same process need to be investigated.

User response

Select one of the following options:

• Review the /var/log/qradar.log file for the word TxSentry to determine the process identifier that is causing your transaction issues.
• Wait to see whether the process completes the transaction and releases the database lock.
• Manually release the database lock by restarting the process identifier.