Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <108682672.1237861550591.JavaMail.jira@brutus>
Date: Mon, 23 Mar 2009 19:25:50 -0700 (PDT)
From: "Trejkaz (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Issue Comment Edited: (DERBY-4111) ASSERT FAILED No page at
 pagenumber: 9; ContainerHandle = BaseContainerHandle:(Container(0, 1393))
In-Reply-To: <1768739060.1237847030402.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-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688509#action_12688509 ] 

Trejkaz edited comment on DERBY-4111 at 3/23/09 7:25 PM:
---------------------------------------------------------

More information:

* The database was originally created under Derby 10.2 or possibly 10.1.  The tables have been migrated but the Derby store itself would still be the original format.
* Other inserts into the same table work fine until a BLOB from some other table has been copied out.  There is nothing about this other BLOB or its associated query in the logs so it seemingly completes successfully.
* Accessing the database directly with the embedded driver seems to dodge the problem (very interesting.)


      was (Author: trejkaz):
    More information: the database was originally created under Derby 10.2 or possibly 10.1.  The tables have been migrated but the Derby store itself would still be the original format.


> ASSERT FAILED No page at pagenumber: 9; ContainerHandle = BaseContainerHandle:(Container(0, 1393))
> --------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4111
>                 URL: https://issues.apache.org/jira/browse/DERBY-4111
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.4.1.3
>            Reporter: Trejkaz
>
> A user is seeing an error like this when using the application client-server.  The client just sees they have been disconnected and no further queries work.  The server sees the following stack trace:
> org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED No page at pagenumber: 9; ContainerHandle = 
> BaseContainerHandle:(Container(0, 1393)) 
> at org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:162) 
> at org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:147) 
> at org.apache.derby.impl.store.access.btree.ControlRow.get(ControlRow.java:838) 
> at org.apache.derby.impl.store.access.btree.ControlRow.get(ControlRow.java:820) 
> at org.apache.derby.impl.store.access.btree.BranchControlRow.getChildPageAtSlot(BranchControlRow.java:1423) 
> at org.apache.derby.impl.store.access.btree.BranchControlRow.search(BranchControlRow.java:284) 
> at org.apache.derby.impl.store.access.btree.BTreeController.doIns(BTreeController.java:634) 
> at org.apache.derby.impl.store.access.btree.BTreeController.insert(BTreeController.java:1264) 
> at org.apache.derby.impl.store.access.btree.index.B2IController.insert(B2IController.java:210) 
> at org.apache.derby.impl.sql.execute.IndexChanger.insertAndCheckDups(IndexChanger.java:439) 
> at org.apache.derby.impl.sql.execute.IndexChanger.doInsert(IndexChanger.java:383) 
> at org.apache.derby.impl.sql.execute.IndexChanger.insert(IndexChanger.java:589) 
> at org.apache.derby.impl.sql.execute.IndexSetChanger.insert(IndexSetChanger.java:268) 
> at org.apache.derby.impl.sql.execute.RowChangerImpl.insertRow(RowChangerImpl.java:453) 
> at org.apache.derby.impl.sql.execute.InsertResultSet.normalInsertCore(InsertResultSet.java:1011) 
> at org.apache.derby.impl.sql.execute.InsertResultSet.open(InsertResultSet.java:487) 
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:372) 
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1235) 
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(EmbedPreparedStatement.java:1652) 
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(EmbedPreparedStatement.java:1307) 
> at org.apache.derby.impl.drda.DRDAStatement.execute(DRDAStatement.java:672) 
> at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTTobjects(DRDAConnThread.java:4197) 
> at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTT(DRDAConnThread.java:4001) 
> at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:991) 
> at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:278) 
> At first glance this appears to be identical to DERBY-3487 but apparently it's a new issue.
> It would be good to know if any corruption has occurred or if the assertion has avoided that happening.

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