Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Farooq Shaik (FarooqS0)
Aegon UK PLC

Aegon UK PLC
GB
FarooqS0 Member since 2019 1 post
Aegon UK PLC
Posted: Sep 25, 2019
Last activity: Sep 30, 2019
Posted: 25 Sep 2019 7:13 EDT
Last activity: 30 Sep 2019 1:53 EDT
Closed

Blocking on pr_sys_locks and pr_sys_locks_sla tables

I'm DBA managing PEGA databases, recently we've noticed increased blocking on our SQL server database on these two pr_sys_locks and pr_sys_locks_sla tables. The below delete command is running but not doing anything for long time blocking other transactions.

(@P0 varchar(8000))delete from dbo.pr_sys_queue_sla where pzInsKey = @P0

Any idea why it's holding locks for so long? shouldn't it delete the row immediately?

To see attachments, please log in.
Data Integration

Related content:

Question

purpose PXEXPIREDATETIME in PR_SYS_LOCKS

Question

DML list for pr_sys_locks etc

Question

Wrong date getting insert into pr_sys_locks table on the pxExpireDateTime value

Question

Defragmentation of pr_sys_locks while importing Application Jar

Question Solved

How to resolve Pega0005 alert due to pr_sys_locks

Support Doc

Application stops when TRUNCATE on pr_sys_locks and DefragSysLocksDaemon running

Question Solved

Lock cache, lock not present in pr_sys_locks while  performing  assignment (Pega v7.2)

Question

OLD entries not getting removed from PR_SYS_LOCK post the pxexpiredatetime is reached

Question

How to resolve PEGA0005 alert due to pr_sys_locks insert query

Question

INITRANS value(to allow multiple concurrent sessions to update the same data blocks ) for the Pega OOTB WORK and PR_SYS_LOCKS tables (current value 1 in our application)

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice