Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Astha Varshney (AsthaV80)
Tsys

Tsys
IN
AsthaV80 Member since 2016 5 posts
Tsys
Posted: Nov 20, 2018
Last activity: Nov 22, 2018
Posted: 20 Nov 2018 4:17 EST
Last activity: 22 Nov 2018 5:07 EST
Closed

Error saving Data-Agent-Queue instance for: Pega-ProCom

Hi All,

I am getting below Exception:

Error saving Data-Agent-Queue instance for: Pega-ProCom on node 840e9bbc17ce4dabd327d6e815450f36 com.pega.pegarules.pub.database.DuplicateKeyException: Database-Saver-UpdateInsertfail Index-Reference 1 23000 ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated DatabaseException caused by prior exception: com.ibm.websphere.ce.cm.DuplicateKeyException: ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated | SQL Code: 1 | SQL State: 23000 DatabaseException caused by prior exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated

Show More

Hi All,

I am getting below Exception:

Error saving Data-Agent-Queue instance for: Pega-ProCom on node 840e9bbc17ce4dabd327d6e815450f36 com.pega.pegarules.pub.database.DuplicateKeyException: Database-Saver-UpdateInsertfail Index-Reference 1 23000 ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated DatabaseException caused by prior exception: com.ibm.websphere.ce.cm.DuplicateKeyException: ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated | SQL Code: 1 | SQL State: 23000 DatabaseException caused by prior exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated

Error code 1: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated<CR><CR> at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:293)<CR>

Can anyone help as what is the cause of this exception and what might be the resolution.


Show Less
To see attachments, please log in.
Low-Code App Development
Dev/Designer Studio

Posted: 6 years ago
Posted: 20 Nov 2018 5:22 EST
Marc Lasserre (MarcLasserre_GCS)
PEGA
Technical Account Manager
Pegasystems Inc.
FR

Hello,

I think you will have to investigate the log files to fully understand where this issue is coming from.

Now having said that you could just try to stop and restart the agent to check if the error remains.

To see attachments, please log in.
Posted: 6 years ago
Posted: 20 Nov 2018 6:10 EST
Astha Varshney (AsthaV80)
Tsys

Tsys
IN

Log States as follows:

 

Show More

Log States as follows:

 

2018-11-20 07:36:03,967 GMT*8*EXCP0001*0*0*9c3fbe0f16067ca5aa741fb53a02ae1e*shared*shared*BAADC64B9135B65F6D66A745802F41D43*none*blank*COE-CAP:05.99.01*17b9c327b01b5ce3743e0fa5c2f26836*N*260*A0D43A82A1F9AB110DF983F0A4961CDD3*7584*WorkManager.PRPCWorkManager : 474*STANDARD*com.pega.pegarules.session.internal.async.AgentRuleUtils*NA*(Master For New Agents)*Rule-Declare-DecisionTable**NA****NA*NA*NA*NA*NA*NA*NA*NA*[MSG][Error saving Data-Agent-Queue instance for: Pega-ProCom on node 9c3fbe0f16067ca5aa741fb53a02ae1e][STACK][com.pega.pegarules.pub.database.DuplicateKeyException: Database-Saver-UpdateInsertfail Index-Reference 1 23000 ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated<CR><CR>DatabaseException caused by prior exception: com.ibm.websphere.ce.cm.DuplicateKeyException: ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated<CR><CR> | SQL Code: 1 | SQL State: 23000<CR><CR>DatabaseException caused by prior exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated<CR><CR> | SQL Code: 1 | SQL State: 23000<CR><CR>From: (BAADC64B9135B65F6D66A745802F41D43:(Master For New Agents)) <CR> SQL: INSERT INTO PEGA_RULES_1.pr_index_reference (pzInsKey , pzTenantId , pxCommitDateTime , "PXCREATEDATETIME" , "PXCREATEOPERATOR" , "PXCREATEOPNAME" , "PXCREATESYSTEMID" , "PXINDEXCOUNT" , "PXINDEXPURPOSE" , "PXINSINDEXEDCLASS" , "PXINSINDEXEDKEY" , "PXINSNAME" , "PXJAVACLASS" , "PXJAVAMETHODNAME" , "PXOBJCLASS" , "PXPAGENAME" , "PXREFERENCINGDESCRIPTION" , "PXREFERENCINGINSNAME" , "PXREFERENCINGRULESETNAME" , "PXREFERENCINGRULESETVERSION" , "PXRULECLASSNAME" , "PXRULEFAMILYNAME" , "PXRULEOBJCLASS" , "PXSAVEDATETIME" , "PXUPDATEDATETIME" , "PXUPDATEOPERATOR" , "PXUPDATEOPNAME" , "PXUPDATESYSTEMID" , "PYLABEL" , "PYRULENAME") VALUES (? , COALESCE((SELECT MAX(pzTenantId) FROM PEGA_RULES_1.pr_index_reference WHERE PZINSKEY = ? GROUP BY (PZINSKEY)), 'shared') , CURRENT_TIMESTAMP , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?)<CR> SQL Inserts: <INDEX-REFERENCE DATA-AGENT-QUEUE PEGA-PROCOM!9C3FBE0F16067CA5AA741FB53A02AE1E!26!RULEREFERENCE> <INDEX-REFERENCE DATA-AGENT-QUEUE PEGA-PROCOM!9C3FBE0F16067CA5AA741FB53A02AE1E!26!RULEREFERENCE> <<null>> <<null>> <<null>> <<null>> <26> <RuleReference> <Data-Agent-Queue> <DATA-AGENT-QUEUE PEGA-PROCOM!9C3FBE0F16067CA5AA741FB53A02AE1E> <DATA-AGENT-QUEUE PEGA-PROCOM!9C3FBE0F16067CA5AA741FB53A02AE1E!26!RULEREFERENCE> <<null>> <<null>> <Index-Reference> <<null>> <<null>> <PEGA-PROCOM!9C3FBE0F16067CA5AA741FB53A02AE1E> <<null>> <<null>> <<null>> <<null>> <Rule-Obj-Class> <<null>> <<null>> <<null>> <<null>> <<null>> <<null>> <Data-Corr-> <CR><CR>Caused by SQL Problems.<CR>Problem #1, SQLState 23000, Error code 1: com.ibm.websphere.ce.cm.DuplicateKeyException: ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated<CR><CR>Problem #2, SQLState 23000, Error code 1: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated<CR><CR> at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:293)<CR> at com.pega.pegarules.data.internal.access.DeferredOperationResult.throwSaveException(DeferredOperationResult.java:126)<CR> at com.pega.pegarules.data.internal.access.DeferredOperationResult.throwUpdateInsertfailException(DeferredOperationResult.java:96)<CR> at com.pega.pegarules.data.internal.access.Saver.saveInstance(Saver.java:935)<CR> at com.pega.pegarules.data.internal.access.Saver.saveInstance(Saver.java:803)<CR> at com.pega.pegarules.data.internal.access.UpdateProcessor.performOps(UpdateProcessor.java:1522)<CR> at com.pega.pegarules.data.internal.access.UpdateProcessor.action(UpdateProcessor.java:245)<CR> at com.pega.pegarules.data.internal.access.UpdateProcessor.action(UpdateProcessor.java:82)<CR> at com.pega.pegarules.data.internal.store.DataStoreManager.doInTransaction(DataStoreManager.java:235)<CR> at com.pega.pegarules.data.internal.access.UpdateProcessor.processUpdates(UpdateProcessor.java:178)<CR> at com.pega.pegarules.data.internal.access.Saver.save(Saver.java:682)<CR> at com.pega.pegarules.data.internal.access.Saver.save(Saver.java:1899)<CR> at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:2704)<CR> at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:2695)<CR> at com.pega.pegarules.session.internal.async.AgentRuleUtils.saveDataInstance(AgentRuleUtils.java:287)<CR> at com.pega.pegarules.session.internal.async.AgentRuleUtils.saveDataInstance(AgentRuleUtils.java:248)<CR> at com.pega.pegarules.session.internal.async.AgentRuleUtils.createDAQInstance(AgentRuleUtils.java:410)<CR> at com.pega.pegarules.session.internal.async.AgentRuleUtils.createOrUpdateDAQ(AgentRuleUtils.java:400)<CR> at com.pega.pegarules.session.internal.async.AgentRuleUtils.checkAndUseDataInstance(AgentRuleUtils.java:365)<CR> at com.pega.pegarules.session.internal.async.MasterForNewAgents.manageSchedules(MasterForNewAgents.java:379)<CR> at com.pega.pegarules.session.internal.async.MasterForNewAgents.run(MasterForNewAgents.java:291)<CR> at com.pega.pegarules.session.internal.async.Agent.runAgentTask(Agent.java:916)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.processAsyncTask(AsyncServant.java:222)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.invoke(AsyncServant.java:168)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:331)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:274)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:225)<CR> at sun.reflect.GeneratedMethodAccessor76.invoke(Unknown Source)<CR> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)<CR> at java.lang.reflect.Method.invoke(Method.java:508)<CR> at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370)<CR> at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:411)<CR> at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224)<CR> at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingException(AppServerBridgeToPega.java:246)<CR> at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.invokeEngine(EngineBeanBoot.java:168)<CR> at com.pega.pegarules.internal.etier.interfaces.EJSLocalStatelessEngineBMT_f2439d86.invokeEngine(Unknown Source)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRAsync.processRequest(PRAsync.java:155)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.AsyncTask.run(AsyncTask.java:64)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.RunnableWrapper.run(RunnableWrapper.java:71)<CR> at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:271)<CR> at java.security.AccessController.doPrivileged(AccessController.java:640)<CR> at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:797)<CR> at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)<CR> at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:206)<CR> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)<CR>Caused by: com.ibm.websphere.ce.cm.DuplicateKeyException: ORA-00001: unique constraint (PEGA_RULES_1.PR_INDEX_REFERENCE_PK) violated<CR><CR> at sun.reflect.GeneratedConstructorAccessor76.newInstance(Unknown Source)<CR> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)<CR> at java.lang.reflect.Constructor.newInstance(Constructor.java:437)<CR> at com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapExceptionHelper(GenericDataStoreHelper.java:627)<CR> at com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapException(GenericDataStoreHelper.java:686)<CR> at com.ibm.ws.rsadapter.AdapterUtil.mapException(AdapterUtil.java:2267)<CR> at com.ibm.ws.rsadapter.jdbc.WSJdbcUtil.mapException(WSJdbcUtil.java:1191)<CR> at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeUpdate(WSJdbcPreparedStatement.java:853)<CR> at com.pega.pegarules.data.internal.store.DatabasePreparedStatementImpl.executeUpdate(DatabasePreparedStatementImpl.java:458)<CR> at com.pega.pegarules.data.internal.access.Saver.executeUpdate(Saver.java:1530)<CR> at com.pega.pegarules.data.internal.access.Saver.insertInstance(Saver.java:1094)<CR> at com.pega.pegarules.data.internal.access.Saver.saveInstance(Saver.java:931)<CR> ... 41 more<CR>]*

 

 

Still I am not able to get what this implies.


Show Less
To see attachments, please log in.

Related content:

Discussion

Access Group for SLA Agent(Standard Type) in Pega-ProCom agents rule

Question Solved

How to configure the Pega-ProCom agents to run on specific node in multinode environment ?

Question

Procedure to update Rule-Connect-MQ ValidateInfrastructure activity residing in pega-procom Ruleset

Question

RD to get list of agents from Data-Agent-Queue class and the details of each agent from Embed-Rule-FutureQueue

Question Solved

Field values IN,OR in Pega-AppDefinition, Pega-ProCom rulesets forcing US States IN, OR to appear in small letters

Question

Queue-For-Agent Lock Error

Question

Max Attempts in Queue-For-Agent

Question

Agent Failure status not captured correctly in my activity for the class "Data-Agent-Queue"

Question Solved

Queue-For-Agent method

Question Solved

Queue-For-Agent FIFO?

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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