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

BIX extract failure caused by pr_perf_stats column error



While extracting data the following error was thrown.

Error Messages

00:59:01,901 [egaRULES UsageDaemon] ( internal.access.Saver) ERROR - Encountered an error when saving instance "LOG-USAGE ABE97A1786796041EB9AFE1387594D50C!20161118T055900.023 GMT!DF74D9FFFF82ED50AD0258C709A3FB0C!INTERVAL" of class Log-Usage
java.sql.SQLDataException: ORA-01438: value larger than specified precision allowed for this column

00:59:01,905 [egaRULES UsageDaemon] ( internal.access.DatabaseImpl) ERROR - Encountered problem when performing a Commit Database-General Problem writing an instance to the database 1438 22003 ORA-01438: value larger than specified precision allowed for this column

Steps to Reproduce

Run a BIX extract.

Root Cause

A defect in Pegasystems’ code or rules .

Some pr_perf_stats columns are inappropriately sized.


Perform the following local-change:

alter table V717DATA.pr_perf_stats 
modify ( pxDecryptCount numeric(18,6),
         pxDecryptCPU numeric(18,6),
         pxDecryptElapsed numeric(18,6),
         pxEncryptElapsed numeric(18,6),
         pxEncryptCPU numeric(18,6),
         pxEncryptCount numeric(18,6)



Suggest Edit

Published November 26, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

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.

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