Support Article
Rules import failed executing Pega command line util (prpcUtils)
Summary
Executing import of RAP file into db2zos database using command line utility but got SQL error (e.g. DB2 SQL Error: SQLCODE=-725, SQLSTATE=42721)
Example command line syntax used is as follows:
Command line executed: ./prpcUtils.sh import --driverClass com.ibm.db2.jcc.DB2Driver --driverJAR /path/db2jcc_license_cu.jar:/path/db2jcc4.jar:/path/db2jcc_license_cisuz.jar --dbType db2zos --dbURL jdbc:db2://host:port/database --dbUser username --dbPassword password --udbSchema schemaName --archivePath /path/archive.jar --noFailOnError false
Error Messages
Exception: Database-General Problem retrieving database information for database pegarules -725 42721 DB2 SQL Error: SQLCODE=-725, SQLSTATE=42721, SQLERRMC=CURRENT SQLID(schemaName) ;databaseName, DRIVER=4.14.88
[java] From: (unknown)
[java] Caused by SQL Problems.
[java] Problem #1, SQLState 42721, Error code -725: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-725, SQLSTATE=42721, SQLERRMC=CURRENT SQLID(schemaName) ;databaseName, DRIVER=4.14.88 [java] Problem #2, SQLState 42721, Error code -725: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-725, SQLSTATE=42721, SQLERRMC=CURRENT SQLID(*PRIOR FAILURE*);databaseName, DRIVER=4.14.88
[java] at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:167)
[java] at com.pega.pegarules.data.internal.access.DatabaseInformationMapImpl.lookupDBInfo(DatabaseInformationMapImpl.java:492)
[java] at com.pega.pegarules.data.internal.access.DatabaseInformationM
Steps to Reproduce
Attempted to import a jar file using command line utility: ./prpcUtils.sh importRoot Cause
The root cause of this problem is a defect in Pegasystems’ code/rules. The prpcUtils.xml script makes a wrong assumption that the currentSchema and SQLID are always the same. If they are not the same, as is the case in this environment, the attempt to connect to the database will fail with error code -725. Resolution
This issue is resolved through the following local change:
In line 336 of the prpcUtils.xml script you would change
From:
<entry key="currentSQLID" value="${db.schema}"/>
To:
<entry key="currentSQLID" value="${pega.jdbc.username}"/>
Published March 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.