Defragmentation of pr_sys_locks while importing Application Jar
I am trying to import a large application jar in a PRPC 7.2.1 server. While the import was in progress, I got a log message - "Proceeding with the defragmentation of pr_sys_locks" and the import paused. There are no other errors in the logs. I stopped the import and restarted the application server so that all locks would be released. But the same log message is coming up again during the import. I was able to complete the import in another server with same configuration. I tried to search for any locks from Designer Studio -> Processes and Rules-> Tools -> Work Admin -> All Locks. I couldn't find any records. PR_SYS_LOCKS table also didn't have any rows. When I try to stop the import, the application hangs. Tried to reset PRPC and import but that didn't fix the import. Is there any way to stop the degragmentation or release any locks?
Defragmentation of pr_sys_locks happens every day @1:00 AM (App server time) by default. (feature introduced in 7.1.8)
This interval could be configured; more details @ https://pdn.pega.com/release-note/ability-periodically-defragment-prsys…
The defragmentation could be disabled by settinge the D-A-S-S "syslocks/defragEnabled" to false.
If I am correct, in PRPC we dont dont do any defragmentationk of tables. I understand it the underlying DB feature, where in DBA would periodically defragment their tables and rebuild their indexes to have the optimal peformance.
Can you confirm the the following points:
- What DB are you using in the problematic environment?
- Forward us the pega log files and pega alert log files for reviewing?
- Check with your DBA, whether the table defragmentation was occuring when you tried importing jar?
Please note that the above table stores instances of the System-Locks class, all locks held at any point of time. This table has a high Read, Insert, and Delete rate.