You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Brett Bergquist (JIRA)" <ji...@apache.org> on 2011/08/17 21:47:27 UTC
[jira] [Updated] (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:all-tabpanel ]
Brett Bergquist updated DERBY-5387:
-----------------------------------
Attachment: dbcopy.zip
Netbeans 6.5.1 project containing the utility source code.
> 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
>
>
> 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