You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2008/05/14 07:09:55 UTC
[jira] Closed: (DERBY-719) Calling SYSCS_INPLACE_COMPRESS_TABLE on
SYS.SYSTABLES results in a lock timeout, with only a single connection
active
[ https://issues.apache.org/jira/browse/DERBY-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor closed DERBY-719.
---------------------------------
Resolution: Fixed
Fix Version/s: 10.5.0.0
Fixing DERBY-1062 has fixed this jira entry too. When I run the provided IJ reproducible test case in 10.4 codeline, I get lock time out errors (10.4 does not have the fix for DERBY-1062) but the same IJ test case works find on 10.5 codeline (the fix for DERBY-1062 went into 10.5 codeline).
> Calling SYSCS_INPLACE_COMPRESS_TABLE on SYS.SYSTABLES results in a lock timeout, with only a single connection active
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-719
> URL: https://issues.apache.org/jira/browse/DERBY-719
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.2.1.6
> Environment: sane mode
> Reporter: Daniel John Debrunner
> Assignee: Mike Matrigali
> Priority: Minor
> Fix For: 10.5.0.0
>
>
> ij version 10.2
> ij> connect 'jdbc:derby:css;create=true';
> ij> call SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE('SYS', 'SYSTABLES', 1, 1, 1);
> ERROR 40XL1: A lock could not be obtained within the time requested
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.