Loading Profile...
Twitter,
Facebook, or email.
Using EA4 I got this exception:
21.10.2009 12:17:04 [WARNING] [in] Unable to create drill-through table
org.apache.derby.client.am.BatchUpdateException: Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.
at org.apache.derby.client.am.Agent.endBatchedReadChain(Unknown Source)
at org.apache.derby.client.am.PreparedStatement.executeBatchRequestX(Unknown Source)
at org.apache.derby.client.am.PreparedStatement.executeBatchX(Unknown Source)
at org.apache.derby.client.am.PreparedStatement.executeBatch(Unknown Source)
at cz.adastra.cif.model.internal.modelimpl.ConnectionPool$_E.executeBatch(ConnectionPool.java:702)
at cz.adastra.cif.tasks.profiling.C.I.A(RollUpWrap.java:454)
at cz.adastra.cif.tasks.profiling.ProfilingAlgorithmInstance$_B.B(ProfilingAlgorithmInstance.java:358)
at cz.adastra.cif.tasks.profiling.ProfilingAlgorithmInstance$_B.access$400(ProfilingAlgorithmInstance.java:282)
at cz.adastra.cif.tasks.profiling.ProfilingAlgorithmInstance.run(ProfilingAlgorithmInstance.java:213)
at cz.adastra.cif.processor.internal.runner.B.E(ComplexStepNode.java:62)
at cz.adastra.cif.processor.internal.runner.F.run(Node.java:115)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.derby.client.am.SqlException: Error for batch element #9674: A truncation error was encountered trying to shrink VARCHAR 'proof of purchase:\u000d\u000a******************************&' to length 4000.
at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)
at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source)
at org.apache.derby.client.net.NetStatementReply.readExecute(Unknown Source)
at org.apache.derby.client.net.StatementReply.readExecute(Unknown Source)
at org.apache.derby.client.net.NetPreparedStatement.readExecute_(Unknown Source)
at org.apache.derby.client.am.PreparedStatement.readExecute(Unknown Source)
... 11 more
As a consequence, it later complained that the connection couldn't be closed.
The SQLServer field is defined as varchar(max), and DQA shows it as type 'text' of length 2147483647,
Creation of drill-down table fails on long field
Official
Response
-
EMPLOYEE
1Hi Alberto,
thanks again for the report. In EA6 build, which is now available for download, we have fixed the problem by truncating the values stored for drill-through. The actual statistics (frequency analysis, extremes, etc.), are, however, based on data before the truncation. Please let us know if the new build works for you and this scenario.
-
Hello Alberto,
thanks for your report.
I have reproduced the problem. It happens when you try to write a field longer then 4000 characters into a single field in our database for drill-through (and by the way to other databases too as it is common field constraint).
We'll look into it and try to make the column "wider", but we might have to truncate such values.Comment -
-
EMPLOYEE
1Hi Alberto,
thanks again for the report. In EA6 build, which is now available for download, we have fixed the problem by truncating the values stored for drill-through. The actual statistics (frequency analysis, extremes, etc.), are, however, based on data before the truncation. Please let us know if the new build works for you and this scenario. -
EMPLOYEE
