From derby-user-return-10414-apmail-db-derby-user-archive=db.apache.org@db.apache.org Wed Jan 28 20:48:50 2009 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 57685 invoked from network); 28 Jan 2009 20:48:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Jan 2009 20:48:50 -0000 Received: (qmail 10790 invoked by uid 500); 28 Jan 2009 20:48:49 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 10763 invoked by uid 500); 28 Jan 2009 20:48:49 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 10754 invoked by uid 99); 28 Jan 2009 20:48:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jan 2009 12:48:49 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jan 2009 20:48:40 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LSHKd-0001SD-JF for derby-user@db.apache.org; Wed, 28 Jan 2009 12:48:19 -0800 Message-ID: <21714590.post@talk.nabble.com> Date: Wed, 28 Jan 2009 12:48:19 -0800 (PST) From: jrgchip To: derby-user@db.apache.org Subject: Re: Record not found in some SQL - Bug? In-Reply-To: <4980BB45.4040203@sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: chip@datamology.com References: <21700110.post@talk.nabble.com> <21708823.post@talk.nabble.com> <4980BB45.4040203@sun.com> X-Virus-Checked: Checked by ClamAV on apache.org oysteing wrote: > > Have you tried to run the Derby consistency checker? > Yes...it reports all 44 tables as OK per SYSCS_CHECK_TABLE. Kristian Waagan-4 wrote: > > Be aware that 10.3.1.4 and 10.3.2.1 had a corruption bug, mostly (or > only) seen on Windows. > Can you point me to information about that corruption bug? Derby-3 wrote: > > If you reload the data, the problem goes away. This would imply that it's > a data issue. > The data is from an ASCII file (with no special chars) and is loaded with SYSCS_IMPORT_TABLE. But I conclude the load, itself, is not the problem because the data is retrievable after initial load. It is only after the DB is used for a while that something becomes unreadable...in this case the HG15497 record noted in my post. Derby-3 wrote: > > Since your database is in a 'broken' state, what happens if you create a > copy of the table and select the rows that match your like 'xxxx%' clause > and insert them in to your temp duplicate table. > I am able to copy the table and select the "bad" row from the copy per the following sequence... ij> CREATE TABLE app."ProductCopy" AS SELECT * FROM app."Product" WITH NO DATA; 0 rows inserted/updated/deleted ij> insert into app."ProductCopy" select * from app."Product"; 34536 rows inserted/updated/deleted ij> select "Num" from app."Product" where "Num" = 'HG15497'; Num ---------------- 0 rows selected ij> select "Num" from app."ProductCopy" where "Num" = 'HG15497'; Num ---------------- HG15497 1 row selected -- View this message in context: http://www.nabble.com/Record-not-found-in-some-SQL---Bug--tp21700110p21714590.html Sent from the Apache Derby Users mailing list archive at Nabble.com.