Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Command Line import takes long duration

SA-33241

Summary



Out-of-the-box (OOTB) processes are taking more than expected time, thus resulting the import of file unnecessarily long.

Error Messages



PEGA0042, PEGA0005, PEGA0027 and PEGA0026 was frequently observed in the Pega Alerts log file.


Steps to Reproduce

Import the file physically located at remotely to the database.

Root Cause



An issue in the custom application code or rules, user is trying to import a file from a remotely located machine to the database.

Thus causing network latency which is causing delay in the execution of database query.

It was observed that mainly PEGA0042 is affecting the performance as it’s taking 95,883 ms which is much more than expected. As this query doesn’t have where clause thus scanning the whole table and returning all rows in the column which is 112,771 rows, again it’s much more than normal.

Below is an OOTB query running during import:

2017-08-25 09:46:21,313 GMT*7*PEGA0042*95883*500*12025ef671705efa9e6f18a9ec0fd722*NA*NA*BDBF8A34040CE50EF490DE029F6AC7704-none-XXXX-XXX-XXX-Work*null*<RequestorID>*N*0*4*XXXX.XX-XXX.XX.XXX.XZX*STANDARD*com.pega.pegarules.data.internal.access.DatabaseImpl*NA*(PREnvironment)Packaging of database query took more than threshold of 500 ms: 95,883 ms
SQL: select pxChangeType as "pxChangeType", pxChangeProperty AS "pxChangeProperty", pxChangePurpose as "pxChangePurpose", pxRuleObjClass as "pxRuleObjClass", pxChangeObjClass as "pxChangeObjClass", pxRuleKey as "pxRuleKey" from XXXX_RULES.pr_sys_decchg

This query is running on XXX_RULES.pr_sys_decchg table. The table pr_sys_decchg stores instances of the System-Declare-Changes class, to support execution of declarative expression rules.


Resolution

User moved the command line import from a machine in at remote location to a machine physically closer to the DB, the import was back to a normal speed.

Published March 15, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us