prasadn1
(prasad nellinki)
March 17, 2023, 9:43am
1
I am getting com.pega.dsm.dnode.api.BatchRecordException exception while calling a customer details in cdh.
Below is the error iam getting. Can any one please help me to get this issue resolved.
Attached the stack trace.
(top level exception)
Type
com.pega.dsm.dnode.api.dataflow.StageException
Message
Exception in stage: Decision Results
BatchRecordException.docx (30.2 KB)
@prasadn1 can you please check the full logs?
Issues can occur when the member node leaving the cluster. You would need to investigate that. HZ logs would show “Member has left the cluster”. See our Troubleshooting document Troubleshooting Hazelcast cluster management .
If the stream/DDS nodes are not in the cluster, data flows won’t run and it will fail.
If you need fuerther help I would suggest you to raising a support ticket on the MSP for further investigation.
Please provide the INC id here so that we can help track it.
prasadn1
(prasad nellinki)
March 27, 2023, 11:25am
3
@MarijeSchillern
Hi Marije. I didnt see any thing related to BatchRecordException in those urls. Kindly please help me to avoid this exception.
@prasadn1 Please a support ticket on the MSP for further investigation.
Please provide the INC id here so that we can help track it.
prasadn1
(prasad nellinki)
April 7, 2023, 10:55am
5
@MarijeSchillern INC-268015 this is the incident raise to work on the exception. Please help me to resolve this kind of exceptions.
Hi @prasadn1
Thanks for sharing the Support Case number. I have linked this post to your ticket in MSP for the Support Engineer to review.
INC-268015 was resolved with the following information
Root cause description:
We are getting com.pega.dsm.dnode.api.BatchRecordException exception in procution.
Solution type: Explanation
below exception in PDC for dev test environment
Database column AccountConnectDt in database CustomerData, table customerdata.t_account has an unknown type: JDBC Type: DateFrom: (H1YJ3AUSG8IQN6JAEU0AE9M0SUETYBDRXA:120.29.234.193) SQL:
Upon checking the client confirmed that the application is not live in dev test and logged a new ticket for production issue.