Hi, I have the same problem and after a Hard clean, with all issues that causes in connected systems, the issues stayed away for one month.
This time, second occasion, it came back almost instantly. It is definitely not an funny option to do a Hard Clean, especially not when you have connected systems indexing on Offence ID.....
------------------------------
Regards
Stefan
------------------------------
Original Message:
Sent: Thu May 28, 2020 01:53 PM
From: Juan Ignacio Leon Plaza
Subject: Magistrate encountered serious errors
Hi, please note there is an apar for 7.4.
https://www.ibm.com/support/pages/apar/IJ24334
Also please note the recommendation for temporarily resolving the issue was to execute a SIM Hard Clean, not a soft clean.
Greetings,
Juan.
------------------------------
Juan Ignacio Leon Plaza
------------------------------
Original Message:
Sent: Thu May 28, 2020 04:51 AM
From: Martin Heiz
Subject: Magistrate encountered serious errors
Same here. We updated to 7.4.0 FP2 more than two weeks ago after having observed the message with 7.3.3 FP3. According to IBM it is a known issue (IJ24819 Offense purging can fail in QRadar 7.4.0 FP1 IF01 OR 7.4.0 FP2 when the patching began at QRadar 7.3.3 FP3). Unfortunately, there is still no fix available (opened a PMR on 8th of May) and in our case it does not only have an impact on offense purging but also on offense generation.
------------------------------
Martin Heiz
InfoGuard AG
Baar
Original Message:
Sent: Wed May 27, 2020 04:11 PM
From: George Stan
Subject: Magistrate encountered serious errors
Updated to 7.4.0 FP2, I'm still seeing the warning, followed the recommended steps, but without success.
------------------------------
George Stan
Original Message:
Sent: Wed May 27, 2020 11:48 AM
From: George Stan
Subject: Magistrate encountered serious errors
Same issue on 7.4.0 FP1
------------------------------
George Valentin Stan