prpcUtil.sh to print SQL bind variables during Imports

General
1

Hi,

I’m using prpcUtils.sh to install CSFS JARs as part of an upgrade activity. During the import process, a few JARs are failing with primary key constraint violations.

The logs show the SQL INSERT statements being executed, but they do not include the bind variable values that are being inserted. Because of this, it’s difficult to determine which specific record is causing the conflict.

This becomes especially challenging with larger JARs such as PegaCRM.jar, where a significant number of records are being imported, making it impractical to manually identify the conflicting entry.

I looked through the available prpcUtils.properties options but could not find any setting that enables logging of bind parameter values during import.

I also tried adding the following settings in a custom prconfig.xml:

My questions are:

  1. Is there a supported way to enable logging of bind variable values for SQL statements executed by prpcUtils.sh during JAR import?
  2. Are there any specific logging categories or other settings that can help identify the exact record causing the primary key violation?
  3. Has anyone encountered a similar issue during CSFS or application JAR imports, and if so, how did you identify the conflicting records?

Any guidance would be appreciated.

Sample Error from prpcUtil.sh run:

2026-08-31 16:35:36,887 INFO AntScriptWrapper - [java] DatabaseException caused by prior exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SSWMSR26.PR4_FIELDVALUE_PK) violated
2026-08-31 16:35:36,887 INFO AntScriptWrapper - [java]
2026-08-31 16:35:36,887 INFO AntScriptWrapper - [java] Database - ORA-00001 - unique constraint (constraint_schema.constraint_name) violated on table table_schema.table_name columns (column_names)
2026-08-31 16:35:36,887 INFO AntScriptWrapper - [java] | SQL Code: 1 | SQL State: 23000
2026-08-31 16:35:36,887 INFO AntScriptWrapper - [java]
2026-08-31 16:35:36,887 INFO AntScriptWrapper - [java] From: (ACT7BWY14WSKYDLY2MPBY2MS35KVRED8NA:Deployment)
2026-08-31 16:35:36,887 INFO AntScriptWrapper - [java] SQL: INSERT INTO SSWMSR26.pr4_fieldvalue (pzInsKey , pxCommitDateTime , “PXCREATEDATETIME” , “PXCREATEOPERATOR” , “PXCREATEOPNAME” , “PXCREATESYSTEMID” , “PXHOSTID” , “PXINSID” , “PXINSNAME” , “PXINSTANCELOCKEDBY” , “PXINSTANCELOCKEDDATETIME” , “PXINSTANCELOCKEDKEY” , “PXMERGESYNCHRONIZED” , “PXOBJCLASS” , “PXSAVEDATETIME” , “PXUPDATEDATETIME” , “PXUPDATEOPERATOR” , “PXUPDATEOPNAME” , “PXUPDATESYSTEMID” , “PYBASERULE” , “PYCIRCUMSTANCEDATE” , “PYCIRCUMSTANCEDATEPROP” , “PYCIRCUMSTANCEPROP” , “PYCIRCUMSTANCETYPE” , “PYCIRCUMSTANCEVAL” , “PYCLASSNAME” , “PYFIELDNAME” , “PYFIELDVALUE” , “PYINTERFACE” , “PYLABEL” , “PYLOCALIZEDVALUE” , “PYMETHODSTATUS” , “PYRULEAVAILABLE” , “PYRULEENDS” , “PYRULENAME” , “PYRULESET” , “PYRULESETVERSION” , “PYRULESTARTS” , “PYSORTDATECIRCUMWITHINRSMAJOR” , “PZRULESETVERSIONMAJOR” , “PZRULESETVERSIONMINOR” , “PZRULESETVERSIONPATCH” , “PZUCSHORTINSID” , pzPVStream , pzChecksum) VALUES (? , CURRENT_TIMESTAMP , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?)
2026-08-31 16:35:36,887 INFO AntScriptWrapper - [java]
2026-08-31 16:35:36,887 INFO AntScriptWrapper - [java] Caused by SQL Problems.
2026-08-31 16:35:36,887 INFO AntScriptWrapper - [java] Problem 1, SQLState 23000, Error code 1: java.sql.BatchUpdateException: ORA-00001: unique constraint (SSWMSR26.PR4_FIELDVALUE_PK) violated

2

Hi Madhava, primary key constraint validations were introduced from Pega Infinity '25 version…

For the primary key validation, I would strongly recommend to run this Upgrade preparation utility - Pegasystems Documentation This will already give you enough information on the primary key constraint issues and help with your preparations, so that there wont be any surprises during your actual upgrade script run…

3

Hi @Premkumar ,

We did ran the utility, this tables didn’t show any primary key conflicts or missing primary key. Also, there are no duplicate records.
The issue is coming from newly inserted records from PegaCRM.jar package, it has records which matches with existing table records.

thanks,

Madhav