db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mayuresh Nirhali <Mayuresh.Nirh...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables
Date Sun, 10 Dec 2006 05:25:59 GMT
Thanks everyone who helped me get through this one.

This was indeed a great experience for me and I thoroughly enjoyed 
working on this one...
...and the itch is beginning to get stronger... :-p


Special Thanks to Suresh...

Mayuresh


Suresh Thalamati (JIRA) wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-606?page=comments#action_12456988 ]

>             
> Suresh Thalamati commented on DERBY-606:
> ----------------------------------------
> 
> Committed     derby606_impl-v6.diff and derby606_upgrade-v7.diff   to trunk,  revision
484797.  Thanks Mayuresh. 
> 
> 
> 
>>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.
> 
> 


Mime
View raw message