db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <kristian.waa...@oracle.com>
Subject Re: [jira] [Commented] (DERBY-5387) Memory leak or unbounded consumption problem when running a utility to copy one database to another using SYSCS_EXPORT_TABLE and SYSCS_IMPORT_TABLE
Date Fri, 02 Sep 2011 04:50:55 GMT
On 02.09.11 03:50, Bergquist, Brett wrote:
> Finally with power restored here (hurricane Irene here on the east coast of the U.S.
put me out of commission for a while)   I fixed the connection leak and with a "-Xmx4096 -d64"
I was able to get this to work whereas before I fixed the connection leak with up to 24Gb
of memory it would always run out of memory.  So it looks like the connection leak was a triggering
factor.  Not sure this is completely fixed but I think it can be closed and re-opened later
if I find out more.

Thanks, Brett.

I have resolved the issue as invalid for now - please reopen it if you 
find out that Derby is the culprit after all.


Regards,
-- 
Kristian

>
> Brett
> ________________________________________
> From: Kristian Waagan (JIRA) [jira@apache.org]
> Sent: Tuesday, August 30, 2011 4:56 AM
> To: derby-dev@db.apache.org
> Subject: [jira] [Commented] (DERBY-5387) Memory leak or unbounded consumption problem
when running a utility to copy one database to another using SYSCS_EXPORT_TABLE and SYSCS_IMPORT_TABLE
>
>      [ https://issues.apache.org/jira/browse/DERBY-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093561#comment-13093561
]
>
> Kristian Waagan commented on DERBY-5387:
> ----------------------------------------
>
> Any more information on this problem?
> The deadline for fixes for 10.8.2 is getting close.
>
>> Memory leak or unbounded consumption problem when running a utility to copy one database
to another using SYSCS_EXPORT_TABLE and SYSCS_IMPORT_TABLE
>> ---------------------------------------------------------------------------------------------------------------------------------------------------
>>
>>                  Key: DERBY-5387
>>                  URL: https://issues.apache.org/jira/browse/DERBY-5387
>>              Project: Derby
>>           Issue Type: Bug
>>           Components: SQL
>>     Affects Versions: 10.8.1.2
>>          Environment: Solaris 10/9, Oracle Java 1.6.0_22, 1Gb heap space (also ran
with 8Gb heap space with no difference other than how long it takes to run out of memory).
>>             Reporter: Brett Bergquist
>>             Priority: Critical
>>          Attachments: dbcopy.zip, java_pid2364_Leak_Hunter.zip, java_pid2364_Leak_Suspects.zip
>>
>>
>> I have a utility that copies one database to another by using 'dblook" to export
the schema from the first which is then uses to create the copy's schema.  The tables are
exported from the first database using the SYSCS_EXPORT_TABLE and imported into the second
database using SYSCS_IMPORT_TABLE, processing each table before moving on to the next.  The
the constraints and indexes present in the schema generated by 'dblook' are applied to the
second database.  The utility runs out of memory regardless of the amount of memory given
when run on a very large database (one table has 75 million rows in it and the total database
size is 110Gb of disk storage).  The utility does complete on a smaller database.
>> I will attach the source code for the utility.  Also added the -XX:+HeapDumpOnOutOfMemory
flag and ran with -Xmx1024m heap.  I will attach the suspected leaks report generated by the
Eclipse MemoryAnalyzer tool.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
>


Mime
View raw message