Question
BIX extract running Slow with PEGA0005 Alert on PR_LOG table
Hi
We are running BIX from command Line and 8 extracts run in parallel.
It was working fine and good a week back but suddenly we are seeing slowness with below alert.
2019-05-03 09:09:45,564 GMT*8*PEGA0005*803*500*5da4d68558f1ffc3ce98c44314c09676*NA*NA*ACF90C73BC251EF05571F588F357F60CD*ANTHEMNAVBIXUser*Anthem-Claims-NAV-Work*null*04fa9a8c270b65441e60dfa478b8b46d*Y*0*ACF90C73BC251EF05571F588F357F60CD*401*naswaspega04*STANDARD*com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl*NA*NA*Rule-Obj-Activity:pzLoadAuthenticationPolicies*DATA-ADMIN-OPERATOR-ID UPDATEOPERATORID #20131010T173711.855 GMT Step: 1 Circum: 0******NA*NA*NA*NA*NA*NA*NA*Database batch execution took more than the threshold of 500 ms: 803 ms SQL: MERGE INTO NEWSDATA.pr_log t USING (VALUES (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?)) AS inputs ("pzInsKey" , "pxCreateDateTime" , "pxCreateOperator" , "pxCreateOpName" , "pxCreateSystemID" , "pxInsName" , "pxObjClass" , "pxSaveDateTime" , "pyAppContext" , "pyClassName" , "pyFileName" , "pyItemId" , "pyLabel" , "pyMessage" , "pyProperties" , "pyServerName" , "pySystemName" , "pyUserIdentifier" , "pyUserName" , "PYREMOTEADDR" , "PYREMOTEHOST" , "pzPVStream") ON (t.pzInsKey = inputs."pzInsKey") WHEN MATCHED THEN UPDATE SET PXCREATEDATETIME = inputs."pxCreateDateTime" , PXCREATEOPERATOR = inputs."pxCreateOperator" , PXCREATEOPNAME = inputs."pxCreateOpName" , PXCREATESYSTEMID = inputs."pxCreateSystemID" , PXINSNAME = inputs."pxInsName" , PXOBJCLASS = inputs."pxObjClass" , PXSAVEDATETIME = inputs."pxSaveDateTime" , PYAPPCONTEXT = inputs."pyAppContext" , PYCLASSNAME = inputs."pyClassName" , PYFILENAME = inputs."pyFileName" , PYITEMID = inputs."pyItemId" , PYLABEL = inputs."pyLabel" , PYMESSAGE = inputs."pyMessage" , PYPROPERTIES = inputs."pyProperties" , PYSERVERNAME = inputs."pyServerName" , PYSYSTEMNAME = inputs."pySystemName" , PYUSERIDENTIFIER = inputs."pyUserIdentifier" , PYUSERNAME = inputs."pyUserName" , PYREMOTEADDR = inputs.PYREMOTEADDR , PYREMOTEHOST = inputs.PYREMOTEHOST , pzPVStream = inputs."pzPVStream" , pxCommitDateTime = CURRENT_TIMESTAMP WHEN NOT MATCHED THEN INSERT (pzInsKey , pxCommitDateTime , PXCREATEDATETIME , PXCREATEOPERATOR , PXCREATEOPNAME , PXCREATESYSTEMID , PXINSNAME , PXOBJCLASS , PXSAVEDATETIME , PYAPPCONTEXT , PYCLASSNAME , PYFILENAME , PYITEMID , PYLABEL , PYMESSAGE , PYPROPERTIES , PYSERVERNAME , PYSYSTEMNAME , PYUSERIDENTIFIER , PYUSERNAME , PYREMOTEADDR , PYREMOTEHOST , pzPVStream) VALUES (inputs."pzInsKey" , CURRENT_TIMESTAMP , inputs."pxCreateDateTime" , inputs."pxCreateOperator" , inputs."pxCreateOpName" , inputs."pxCreateSystemID" , inputs."pxInsName" , inputs."pxObjClass" , inputs."pxSaveDateTime" , inputs."pyAppContext" , inputs."pyClassName" , inputs."pyFileName" , inputs."pyItemId" , inputs."pyLabel" , inputs."pyMessage" , inputs."pyProperties" , inputs."pyServerName" , inputs."pySystemName" , inputs."pyUserIdentifier" , inputs."pyUserName" , inputs."PYREMOTEADDR" , inputs."PYREMOTEHOST" , inputs."pzPVStream")*
We see only 3000 odd records in the table and it is not big table as well.
please suggest any thing we can do.
Hi Arvind,
Which version of Bix are you using?.
Could you please enable debug logs for below class and run the extract. Please provide us PegaRules,PegaAlerts and PegaBix logs after running the extract.
"com.pega.pegarules.data.internal.access.ExtractImpl"
The above class will log the extract information along with the query which is formed to fetch the data in PegaBix log. You can run the same query against database and check if you can see if the query is taking more time.
Regards,
Waseem khan