[
https://issues.apache.org/jira/browse/DERBY-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008486#comment-13008486
]
Kathey Marsden commented on DERBY-5121:
---------------------------------------
Hi Mamta, for the IBM JVM's there is a tool tool that you can use to analyze
heap dumps and memory issues , the .phd file that is generated when you get an
out of memory.
http://www.alphaworks.ibm.com/tech/heapanalyzer
You run it like java -Xmx1200m -jar ha21.jar <phd file>
And in a box that comes up on the first screen it shows the heap size. The
menu options allow you to identify leak suspects and it has other features.
I don't know how the heap size could be changed at runtime though.
> Data corruption when executing an UPDATE trigger
> ------------------------------------------------
>
> Key: DERBY-5121
> URL: https://issues.apache.org/jira/browse/DERBY-5121
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1, 10.8.0.0
> Reporter: Rick Hillegas
> Assignee: Mamta A. Satoor
> Labels: derby_triage10_8
> Attachments: DummyProc.java, derby5121_patch1_diff.txt,
> triggerBug.sql, triggerBug.sql, triggeredBug2.sql, triggeredCorruption.sql
>
>
> When executing an UPDATE trigger, the following error is raised. I will
> attach a test case:
> ERROR XCL12: An attempt was made to put a data value of type
> 'org.apache.derby.impl.jdbc.EmbedClob' into a data value of type 'INTEGER'.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
