Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <491AE134.7090806@sun.com>
Date: Wed, 12 Nov 2008 13:59:16 +0000
From: Alan Burlison <Alan.Burlison@sun.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20081014)
MIME-Version: 1.0
To: derby-user@db.apache.org
Subject: btree overflow during insert
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

We are doing inserts with Derby 10.4.2.0 into a table that has an index 
on it, and during the insert we get the following errors:

*** Appending local Error for batch element #84: Limitation: Record of a 
btree secondary index cannot be updated or inserted due to lack of space 
on the page.  Use the parameters derby.storage.pageSize and/or 
derby.storage.pageReservedSpace to work around this limitation.***
*** Next Exception java.sql.SQLException: Error for batch element #155: 
Limitation: Record of a btree secondary index cannot be updated or 
inserted due to lack of space on the page.  Use the parameters 
derby.storage.pageSize and/or derby.storage.pageReservedSpace to work 
around this limitation.***
Appending nestedError for batch element #84: Limitation: Record of a 
btree secondary index cannot be updated or inserted due to lack of space 
on the page.  Use the parameters derby.storage.pageSize and/or 
derby.storage.pageReservedSpace to work around this limitation.

We've tried removing the index and re-adding it after the inserts, but 
the result is the same.  To stop this happening we have to up the 
derby.storage.pageSize parameter to 16k, which is too big for what is 
effectively an OLTP database, and the documentation for 
derby.storage.pageReservedSpace says that it only applies to tables, bot 
indexes.

Is this a bug, and if not, what should we do to avoid it, other than 
increasing the DB page size to 16K?

Thanks,

-- 
Alan Burlison
--