web stats
HL7 Channel Failing to Write to SQL Database - Database Dispatcher Exception - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Thread Tools Display Modes
Old 05-19-2017, 08:07 AM
collin quinn collin quinn is offline
Mirth Newb
Join Date: Jun 2014
Posts: 22
collin quinn is on a distinguished road
Default HL7 Channel Failing to Write to SQL Database - Database Dispatcher Exception

I have an HL7 channel that began failing to write to a SQL database following an update a client applied to their HL7 feed. The client cannot identify what field(s) changed that would prove problematic and the processing error does not provide any details on what specifically is causing the problem. The error detail is as follows:

Database Writer error
ERROR MESSAGE: Failed to write to database
com.mirth.connect.connectors.jdbc.DatabaseDispatch erException: Failed to write to database
at com.mirth.connect.connectors.jdbc.DatabaseDispatch erQuery.send(DatabaseDispatcherQuery.java:133)
at com.mirth.connect.connectors.jdbc.DatabaseDispatch erQuery.send(DatabaseDispatcherQuery.java:127)
at com.mirth.connect.connectors.jdbc.DatabaseDispatch erQuery.send(DatabaseDispatcherQuery.java:81)
at com.mirth.connect.connectors.jdbc.DatabaseDispatch er.send(DatabaseDispatcher.java:107)
at com.mirth.connect.donkey.server.channel.Destinatio nConnector.handleSend(DestinationConnector.java:59 9)
at com.mirth.connect.donkey.server.channel.Destinatio nConnector.run(DestinationConnector.java:492)
at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.DataTruncation: Data truncation
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnos tic(SQLDiagnostic.java:386)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(Td sCore.java:2894)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCor e.java:2334)
at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(T dsCore.java:649)
at net.sourceforge.jtds.jdbc.JtdsStatement.processRes ults(JtdsStatement.java:614)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL (JtdsStatement.java:573)
at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.ex ecute(JtdsPreparedStatement.java:761)
at org.apache.commons.dbcp.DelegatingPreparedStatemen t.execute(DelegatingPreparedStatement.java:172)
at org.apache.commons.dbcp.DelegatingPreparedStatemen t.execute(DelegatingPreparedStatement.java:172)
at com.mirth.connect.connectors.jdbc.DatabaseDispatch erQuery.send(DatabaseDispatcherQuery.java:103)
... 6 more

Any thoughts on how to diagnose which field or fields are associated with the data truncation error?
Reply With Quote
Old 05-22-2017, 03:59 AM
Thoughts_Shared Thoughts_Shared is offline
OBX.2 Kenobi
Join Date: Dec 2016
Posts: 58
Thoughts_Shared is on a distinguished road

It looks like one (or more) HL7 field length exceeded the length assigned in the DB. It would not be possible to say which field caused the error by looking at the error code. You might want to compare the length of each DB field with the length of the respective incoming HL7 values.
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -8. The time now is 09:56 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Mirth Corporation