db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mayuresh Nirhali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables
Date Fri, 08 Dec 2006 05:54:23 GMT
     [ http://issues.apache.org/jira/browse/DERBY-606?page=all ]

Mayuresh Nirhali updated DERBY-606:
-----------------------------------

    Attachment: derby606_upgrade-v7.diff

Suresh pointed out that 10.1 to 10.3 upgrade test will be more appropriate at this time. I
think that is wise also because it will still exercise a relevant upgrade for this bug.

So, in the new attached patch, I have cleaned up 10.2-10.3 test related code and the patch
looks neat now. It  only has a added testcase to UpgradeTester with corresponding changes
to the out file.

please note that, we are not including 10.2-10.3 upgrade tests here, so the patch does not
include additional trunk settings to checkout 10.2 binaries. This will be added as a part
of fix to 1689, I feel.

thanks


> SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables
> --------------------------------------------------------------------
>
>                 Key: DERBY-606
>                 URL: http://issues.apache.org/jira/browse/DERBY-606
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.1.1.0
>         Environment: Java 1.5.0_04 on Windows Server 2003 Web Edition
>            Reporter: Jeffrey Aguilera
>         Assigned To: Mayuresh Nirhali
>             Fix For: 10.3.0.0
>
>         Attachments: A606Test.java, derby606-v2.diff, derby606-v3.diff, derby606_impl-v4.diff,
derby606_impl-v5.diff, derby606_impl-v6.diff, derby606_upgrade-v4.diff, derby606_upgrade-v5.diff,
derby606_upgrade-v6.diff, derby606_upgrade-v7.diff, derby606_v1.diff
>
>
> SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails with one of the following error messages
when applied to a very large table (>2GB):
> Log operation null encounters error writing itself out to the log stream, this could
be caused by an errant log operation or internal log buffer full due to excessively large
log operation. SQLSTATE: XJ001: Java exception: ': java.io.IOException'.
> or
> The exception 'java.lang.ArrayIndexOutOfBoundsException' was thrown while evaluating
an expression. SQLSTATE: XJ001: Java exception: ': java.lang.ArrayIndexOutOfBoundsException'.
> In either case, no entry is written to the console log or to derby.log.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message