Alan Burlison wrote:
This is an important issue for us, and is a potential risk to us
deploying on Derby. Should I raise a bug? I've looked at the source
where this error is coming from, and it's scattered with FIXME-type
comments that suggests it's a known problem.
Hi Alan,
I don't remember this issue coming up before.
If you can reproduce this, and maybe devote some time writing a repro, I
would just log a bug right away.
If not, I would suggest you wait for some more days in hope of a person
having a deeper knowledge about this issue pitching in.
FYI, issues/bug are logged at https://issues.apache.org/jira/browse/DERBY
regards,
--
Kristian
Thanks,
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?
