We have a requirement not to creating duplicate objects (instances of custom Data Class). To implement this we have created a constraint at the DB level for the particular column. So, when system (via agent) is trying to create a duplicate object (or in other words - inserting a duplicate row in the DB table), we are getting a Unique Constraint Error from DB. This is very well expected and working fine.

The point is - we have a huge log file full of this kind of errors. We know this is our design but wanted to know if by any ways we can stop this logging.

Sample error:

2019-04-08 06:19:37,379 [fault (self-tuning)'] [ STANDARD] [ ] [ CLSBL:01.01] (rrorHandling._baseclass.Action) ERROR - Error in commit()
com.pega.pegarules.pub.database.DuplicateKeyException: ORA-00001: unique constraint (PEGA_GENE_DATA_USR.LICENSE_OWNER_UNIQUE) violated

DatabaseException caused by prior exception: java.sql.BatchUpdateException: ORA-00001: unique constraint (PEGA_GENE_DATA_USR.LICENSE_OWNER_UNIQUE) violated

***Edited by Moderator Marissa to update platform capability tags****