Hello,
For me this would be best raised in a support case, so that they can investigate at more depth.
They would need a full description of the exact process you completed in the UI.
Then a list of the database tables you are seeing the exclusive locks in.
Though feel free to add to the forum as well.
Can you confirm the current version of QRadar as well.
Regards,
------------------------------
Comghall Morgan
QRadar Support Architect
IBM
------------------------------
Original Message:
Sent: Thu May 16, 2024 05:25 PM
From: Vishnu Gopal Singhal
Subject: IBM QRadar - Postgres DSM - Select doing xclusive Lock
Yes lock remained on the database table for longer period of time.
Original Message:
Sent: 5/16/2024 11:36:00 AM
From: Comghall Morgan
Subject: RE: IBM QRadar - Postgres DSM - Select doing xclusive Lock
Hello,
When you create information like this that has to be populated to the Database, for me it is reasonable that an exclusive lock is used. Therefore ensuring that as the new information is populated that the table is not being writtten to or viewed by any other source.
This limits the chance of teh tables becoming out of sync or corrupted. It also means that the dat being viewed is up to date.
Though these exclusive locks should be momentary as new data is written.
An issue would be if the exclusive locks remained on the database table.
Regards,
------------------------------
Comghall Morgan
QRadar Support Architect
IBM
Original Message:
Sent: Mon May 06, 2024 02:45 AM
From: Vishnu Gopal Singhal
Subject: IBM QRadar - Postgres DSM - Select doing xclusive Lock
Hi Team,
In my integration setup of PostgreSQL JDBC DSM with QRadar, I've noticed that QRadar is imposing exclusive locks on the tables I've configured for select queries. Is there a method to circumvent these exclusive locks? Additionally, could you provide insight into why QRadar acquires these exclusive locks?
------------------------------
Vishnu Gopal Singhal
------------------------------