Discussion

71
Views
ISHITADAS Member since 2011 1 post
Ernst & Young LLP
Posted: 4 months ago
Last activity: 4 months ago

There was a problem getting a list: code: -206 SQLState: 42703 Message: PXCOVERINSKEY IS NOT VALID IN THE CONTEXT WHERE IT IS USE

HI All,

I am facing an issue while creating a child case from a parent case. I am getting the following error.

 

 

 

 There was a problem getting a list: code: -206 SQLState: 42703 Message: PXCOVERINSKEY IS NOT VALID IN THE CONTEXT WHERE IT IS USED. SQLCODE=-206, SQLSTATE=42703, DRIVER=4.22.37 
Detailed exception:      [MSG][Error retrieving top level cover key for: abcd-WORK 20205255 in abcd-Work-Request][STACK][com.pega.pegarules.pub.database.DatabaseException: There was a problem getting a list: code: -206 SQLState: 42703 Message: PXCOVERINSKEY IS NOT VALID IN THE CONTEXT WHERE IT IS USED. SQLCODE=-206, SQLSTATE=42703, DRIVER=4.22.37 DatabaseException caused by prior exception: com.ibm.websphere.ce.cm.StaleConnectionException: PXCOVERINSKEY IS NOT VALID IN THE CONTEXT WHERE IT IS USED. SQLCODE=-206, SQLSTATE=42703, DRIVER=4.22.37 | SQL Code: -206 | SQL State: 42703 DatabaseException caused by prior exception: com.ibm.db2.jcc.am.SqlSyntaxErrorException: PXCOVERINSKEY IS NOT VALID IN THE CONTEXT WHERE IT IS USED. SQLCODE=-206, SQLSTATE=42703, DRIVER=4.22.37 | SQL Code: -206 | SQL State: 42703 DatabaseException caused by prior exception: com.ibm.db2.jcc.am.SqlException: THE DESCRIBE STATEMENT DOES NOT SPECIFY A PREPARED STATEMENT. SQLCODE=-516, SQLSTATE=26501, DRIVER=4.22.37 | SQL Code: -516 | SQL State: 26501 DatabaseException caused by prior exception: com.ibm.db2.jcc.am.SqlException: THE CURSOR SQL_CURLH200C5 IS NOT IN A PREPARED STATE. SQLCODE=-514, SQLSTATE=26501, DRIVER=4.22.37 | SQL Code: -514 | SQL State: 26501 From: (H49C1484EEAC90F0A83FCF535E63FAC6B:10.205.104.253) SQL: select pxCoverInsKey as "pxCoverInsKey", pxObjClass as "pxObjClass" from DTPEGASD.project_WORK where pzInsKey = ? Caused by SQL Problems. Problem #1, SQLState 42703, Error code -206: com.ibm.websphere.ce.cm.StaleConnectionException: PXCOVERINSKEY IS NOT VALID IN THE CONTEXT WHERE IT IS USED. SQLCODE=-206, SQLSTATE=42703, DRIVER=4.22.37 Problem #2, SQLState 42703, Error code -206: com.ibm.db2.jcc.am.SqlSyntaxErrorException: PXCOVERINSKEY IS NOT VALID IN THE CONTEXT WHERE IT IS USED. SQLCODE=-206, SQLSTATE=42703, DRIVER=4.22.37 Problem #3, SQLState 26501, Error code -516: com.ibm.db2.jcc.am.SqlException: THE DESCRIBE STATEMENT DOES NOT SPECIFY A PREPARED STATEMENT. SQLCODE=-516, SQLSTATE=26501, DRIVER=4.22.37 Problem #4, SQLState 26501, Error code -514: com.ibm.db2.jcc.am.SqlException: THE CURSOR SQL_CURLH200C5 IS NOT IN A PREPARED STATE. SQLCODE=-514, SQLSTATE=26501, DRIVER=4.22.37 at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:262) at

 

 

Getting this error from activity pzLoadCaseHierarchyWrapper step 5 Java

ParameterPage newParamsPage = new ParameterPage(); newParamsPage.putString("AlwaysBuildTheTree",tools.getParamValue("AlwaysBuildTheTree"));

try{     // Build for existing work objects     pega_processengine_workutilities.pzMapCases(tools.findPage("pyTopCaseMap"), myStepPage, newParamsPage);

} catch(Throwable t){     throw new com.pega.pegarules.pub.PRRuntimeException("exception with pzmapcases", t);          } try{     // Add current work object       pega_processengine_workutilities.pzAddCaseToMap(tools.findPage("pyTopCaseMap"), myStepPage); } catch(Throwable t){     throw new com.pega.pegarules.pub.PRRuntimeException("pzaddmapcasetomap", t); }  

Pega Platform 7.2.2
Share this page LinkedIn