Question

8
Replies
296
Views
solol Member since 2011 8 posts
PEGA
Posted: 3 years ago
Last activity: 3 years 2 months ago
Closed

Seeking PR_DATA_ADMIN tuning advices

We are encountering long wait times during startup on locks happening on the PR_DATA_ADMIN table.

We are looking on advice for tuning the access to this table (mainly during the startup of the JVMs).

To be more specific the query that leads to most of the locks is the following:

UPDATE <SCHEMA_NAME>.pr_data_admin SET PXCREATEDATETIME = :1 , PXCREATEOPERATOR = :2 , PXCREATEOPNAME = :3 , PXCREATESYSTEMID = :4 , PXINSNAME = :5 , PXOBJCLASS = :6 , PXSAVEDATETIME = :7 , PXUPDATEDATETIME = :8 , PXUPDATEOPERATOR = :9 , PXUPDATEOPNAME = :10 , PXUPDATESYSTEMID = :11 , PYACCESSGROUP = :12 , PYDEFAULTAPPNAME = :13 , PYDEFAULTAPPVERSION = :14 , PYLABEL = :15 , PYMANAGER = :16 , PYNAME = :17 , PYORGANIZATION = :18 , PYORGDIVISION = :19 , PYORGUNIT = :20 , PYOWNER = :21 , PYRULESETNAME = :22 , PYSETTING = :23 , PYSYSTEMNAME = :24 , PYWORKBASKET = :25 , PYWORKGROUP = :26 , PYWORKPOOL = :27 , PXPRODUCTNAME = :28 , PXPRODUCTPATCHVERSION = :29 , PXPRODUCTVERSION = :30 , PXSYSTEMNAMESETFROMFILE = :31 , PYEXPIRATION = :32 , PYNODENAME = :33 , PYPURPOSE = :34 , PYTIMESTAMP = :35 , PYWORKGROUPNAME = :36 , pxCommitDateTime = CURRENT_TIMESTAMP , pzPVStream = :37 WHERE PZINSKEY = :38

A last note is that we had an SR raised (SR-B69134), but were redirected here due to the category of the request.

***Updated by moderator: Lochan to add SR details***

System Administration Data Integration SR Exists
Moderation Team has archived post
Share this page LinkedIn