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

Arithmetic Overflow while inserting into pr_perf_stats table

SA-19810

Summary



Arithmetic Overflow occurs while inserting into pr_perf_stats table

Error Messages



Caused by:
com.microsoft.sqlserver.jdbc.SQLServerException: Arithmetic overflow error converting numeric to data type numeric.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:197)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1493)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:390)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:340)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4575)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1400)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:179)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:154)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(SQLServerPreparedStatement.java:308)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteUpdate(WSJdbcPreparedStatement.java:1156)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeUpdate(WSJdbcPreparedStatement.java:797)
at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.executeUpdate(DatabasePreparedStatementImpl.java:476)
at com.pega.pegarules.data.internal.access.Saver.executeUpdate(Saver.java:1617)
at com.pega.pegarules.data.internal.access.Saver.insertInstance
(Saver.java:1072)
... 40 more


Steps to Reproduce



Not Applicable


Root Cause



A defect in Pegasystems’ code or rules

The following columns are not created with the correct precision. Depending on whether the system is upgraded or is a fresh install the data type will either be numeric or decimal.

 

Resolution



Apply the following hot fix HFix-26027
 

alter table <PegaDataSchema>.pr_perf_stats alter column pxDecryptCount numeric(18,6);

alter table <PegaDataSchema>.pr_perf_stats alter column pxDecryptCPU numeric(18,6);

alter table <PegaDataSchema>.pr_perf_stats alter column pxDecryptElapsed numeric(18,6);

alter table <PegaDataSchema>.pr_perf_stats alter column pxEncryptElapsed numeric(18,6);

alter table <PegaDataSchema>.pr_perf_stats alter column pxEncryptCPU numeric(18,6);

alter table <PegaDataSchema>.pr_perf_stats alter column pxEncryptCount numeric(18,6);

 

 

Suggest Edit

Published February 13, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

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