[
https://issues.apache.org/jira/browse/DERBY-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl-Erik Kopseng updated DERBY-2639:
-------------------------------------
Attachment: crashderby_src.zip
This exact bug has been driving me nuts for two days. I find it hard to
understand why practically no one else seems to have come across this. After
long hours of trying to debug this I have stripped the code to the bare minimum
to expose the bug consistently.
The code in crashderby_src.zip contains a Java source code file along with two
sql files. It is a JUnit test case and needs the junit4.jar as well as the
derby.jar.
Example (Linux): java -cp .:`locate /java/junit4.jar`:`locate lib/derby.jar`
org.junit.runner.JUnitCore CrashDerby
> Bulk data load utility should indicate when it is finished.
> -----------------------------------------------------------
>
> Key: DERBY-2639
> URL: https://issues.apache.org/jira/browse/DERBY-2639
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.2.2.0
> Environment: Java Version: 1.5.0_06
> Java Vendor: Sun Microsystems Inc.
> OS name: Windows XP
> IDE: Eclipse
> Derby: 10.2.2, running Embedded
> Reporter: Patty Parker
> Attachments: crashderby_src.zip, DerbyProblem.jar
>
>
> The bulk load CALL SYSCS_UTIL.SYSCS_IMPORT_DATA appears to be finished (i.e.
> the statement returns), but it is not entirely
> finishing before I try to query the table it is populating. I would expect
> to get a locking exception, or something of that nature, but
> the error I get is either SQLERROR XSCB1 or SQLERROR XSCBH1, Container
> <containerName> not found. It has given me both at different times.
> An improvement I would suggest is having SYSCS_UTIL.SYSCS_IMPORT_DATA
> indicate when it is done loading. As it stands now, the thread I have
> running it finishes before the utility finishes, and I have no elegant way of
> knowing when the load is done, other than trying to use the table and
> trapping for I listed above.
> For more information, please see the post "SQL Exception: Container xxx not
> found" in derby-user mail list.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
