Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <114633744.1207639404684.JavaMail.jira@brutus>
Date: Tue, 8 Apr 2008 00:23:24 -0700 (PDT)
From: "Gerald Khin (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3009) Out of memory error when creating a
 very large table
In-Reply-To: <18776276.1187168371080.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586691#action_12586691 ] 

Gerald Khin commented on DERBY-3009:
------------------------------------

I just came across the same effect as Andrew Brown mentioned in his comment: A couple of ALTER TABLE ADD CONSTRAINT FOREIGN KEY statements on a couple of non-empty tables (the biggest of about 150k rows) caused an OOME. And the OOME doesn't happen when restarting the database process before each ALTER TABLE statement.

But it seems to me that this effect doesn't match the description of this JIRA entry. So my question is: Is this effect already known and honoured in a separate JIRA entry?


> Out of memory error when creating a very large table
> ----------------------------------------------------
>
>                 Key: DERBY-3009
>                 URL: https://issues.apache.org/jira/browse/DERBY-3009
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.2.2.0
>         Environment: Win XP Pro
>            Reporter: Nick Williamson
>         Attachments: DERBY-3009.zip
>
>
> When creating an extremely large table (c.50 indexes, c.50 FK constraints), IJ crashes with an out of memory error. The table can be created successfully if it is done in stages, each one in a different IJ session.
> From Kristian Waagan:
> "With default settings on my machine, I also get the OOME.
> A brief investigation revealed a few things:
>   1) The OOME occurs during constraint additions (with ALTER TABLE ... 
> ADD CONSTRAINT). I could observe this by monitoring the heap usage.
>   2) The complete script can be run by increasing the heap size. I tried with 256 MB, but the monitoring showed usage peaked at around 150 MB.
>   3) The stack traces produced when the OOME occurs varies (as could be expected).
>   4) It is the Derby engine that "produce" the OOME, not ij (i.e. when I ran with the network server, the server failed).
> I have not had time to examine the heap content, but I do believe there is a bug in Derby. It seems some resource is not freed after use."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.