[
https://issues.apache.org/jira/browse/DERBY-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124422#comment-13124422
]
Myrna van Lunteren commented on DERBY-5450:
-------------------------------------------
Unfortunately, I did not stop the process as soon as I saw the error, but let
it run past the weekend.
The database is now definitely too big...(even jar-ed up).
But contact me directly and I can probably arrange for you to access the
machine.
> in nstest: XSLA6: Cannot recover from database & and 40XT4 errors in nstest
> (sane jars) after ASSERT FAILED
> org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED
> inconsistency in space management during insert
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5450
> URL: https://issues.apache.org/jira/browse/DERBY-5450
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.8.2.2
> Environment: SUSE Linux 10, ibm 1.6 SR9 FP1. 2 CPU machine, but
> hyperthreading on
> Reporter: Myrna van Lunteren
> Attachments: d5450_derbylog.jar
>
>
> With the 10.8 (10.8.2.2) tree sync-ed up to revision: 1179754, I ran NsTest
> Embedded with sane jars, but no derby.properties file.
> I saw the following AssertFailure:
> org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED
> inconsistency in space management during insert: slot = 146
> getSlotOffset(slot) = 3206 dataWritten = 19 freeSpace = -15 firstFreeByte =
> 3149 page = ---------------------------------------------------
> page id: Page(378,Container(0, 1153)) Overflow: false PageVersion: 895
> SlotsInUse: 159 DeletedRowCount: 93 PageStatus: 1 NextId: 317 firstFreeByte:
> 3149 freeSpace: -15 totalSpace: 4028 spareSpace: 0% minimumRecordSize : 1
> PageSize: 4096
> This was followed by:
> ------------ BEGIN SHUTDOWN ERROR STACK -------------
> ERROR XSLA6: Cannot recover the database.
> and somewhat later:
> ERROR 40XT4: An attempt was made to close a transaction that was still
> active. The transaction has been aborted.
> But after a while we get back to the errors always seen with this test (ERROR
> 22003 and XBM06).
> I will attach the derby.log, in case someone likes to look at puzzling
> behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
