Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 46156 invoked from network); 14 May 2009 10:25:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 May 2009 10:25:24 -0000 Received: (qmail 37144 invoked by uid 500); 14 May 2009 10:25:24 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 37108 invoked by uid 500); 14 May 2009 10:25:24 -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 37100 invoked by uid 99); 14 May 2009 10:25:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2009 10:25:24 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.6.24] (HELO gmp-eb-inf-2.sun.com) (192.18.6.24) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2009 10:25:12 +0000 Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n4EAOqR7013591 for ; Thu, 14 May 2009 10:24:52 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KJM00800OCB1M00@fe-emea-09.sun.com> for derby-user@db.apache.org; Thu, 14 May 2009 11:24:52 +0100 (BST) Received: from [129.159.139.223] ([unknown] [129.159.139.223]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KJM00JLJQ8Z8I40@fe-emea-09.sun.com> for derby-user@db.apache.org; Thu, 14 May 2009 11:24:36 +0100 (BST) Date: Thu, 14 May 2009 12:23:28 +0200 From: Kristian Waagan Subject: Re: Unexplained exception: temp file cannot be found In-reply-to: Sender: Kristian.Waagan@Sun.COM To: Derby Discussion Message-id: <4A0BF120.5040702@Sun.COM> References: User-Agent: Thunderbird 2.0.0.21 (X11/20090323) X-Virus-Checked: Checked by ClamAV on apache.org Tim Dudgeon wrote: > Dag H. Wanvik wrote: >> >> It looks as if the creating of a temporary file failed. Does the path >> exist >> (C:\Users\Csizi\Documents\IJCProjects\ijc-project\.config\localdb\db\tmp), >> >> and if so, is it writable for this account? >> >> Dag >> > > Yes, the user has confirmed that this directory does not now exist: > C:\Users\Csizi\Documents\IJCProjects\ijc-project\.config\localdb\db\tmp > > but that its parent directory does exist, and does have write access > (but this is Vista so strange things could be happening!). > > I would imagine that the tmp directory would be created automatically > by Derby when it needed it. It is not normally present. I think Derby will create the tmp directory when the database is booted. Unless you have specified a different directory, it is called 'tmp' and is located in the database directory (on the same level as 'seg0'). If you shut down the database properly (using 'shutdown=true' in the connection URL), the directory will be deleted. If you don't properly shut down the database, the tmp directory will be cleaned on the next boot. This is what I see on my system. > > What would the cause of generating the temporary file? For instance an external sort, or a 4KB+ Blob/Clob created with Connection.create[BC]lob or modified through the java.sql.[BC]lob interface. To be sure, make the lob a bit bigger :) Since forcing an external sort requires a little more work, I'd go for the lob approach to test this. Regards, -- Kristian > > Tim >