From derby-user-return-1472-apmail-db-derby-user-archive=db.apache.org@db.apache.org Fri Jul 01 00:49:32 2005 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 87523 invoked from network); 1 Jul 2005 00:49:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Jul 2005 00:49:31 -0000 Received: (qmail 31746 invoked by uid 500); 1 Jul 2005 00:49:30 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 31727 invoked by uid 500); 1 Jul 2005 00:49:30 -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 31713 invoked by uid 99); 1 Jul 2005 00:49:29 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jun 2005 17:49:29 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.110.129] (HELO e31.co.us.ibm.com) (32.97.110.129) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jun 2005 17:49:32 -0700 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e31.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j610nR8D444400 for ; Thu, 30 Jun 2005 20:49:27 -0400 Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j610nQIr285842 for ; Thu, 30 Jun 2005 18:49:26 -0600 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j610nQZ9020601 for ; Thu, 30 Jun 2005 18:49:26 -0600 Received: from [127.0.0.1] (Abrown.svl.ibm.com [9.30.40.146]) by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j610nPAg020583 for ; Thu, 30 Jun 2005 18:49:26 -0600 Message-ID: <42C49344.3040204@sbcglobal.net> Date: Thu, 30 Jun 2005 17:50:12 -0700 From: Army User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Discussion Subject: Re: derby query References: <49e90256050630141019eeffe4@mail.gmail.com> In-Reply-To: <49e90256050630141019eeffe4@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Wolverine wrote: > i m using cloudscape 10.0.1 on linux redhat 9. with unixODBC > apache n php > > i have created a table and in mytest.php m displaying the contents of the table. > i have successfully done it but if i go on refreshing the page several > times sometimes it gives the following error and again on the next > attempt it runs well. then again after sometime it gives the error > again. is there something wrong with my installation > > Warning: SQL error: [unixODBC][IBM][CLI Driver] SQL0902C A system > error (reason code = "") occurred. Subsequent SQL statements cannot be > processed. SQLSTATE=58005 , SQL state 58005 in SQLConnect in > mytest.php on line 5 This sounds like it could be related to some protocol chaining issues that existed in early 10.0.1 releases but were fixed in 10.0.2. The JIRA issue for this was DERBY-35 and the fix was checked into 10.0.2 codeline back in October of last year. If you can run: java org.apache.derby.tools.sysinfo and post the output here, that would allow us to check whether or not the jars you have include the fix for the problem. I'm guessing they don't since, as I said, the fix didn't go in until 10.0.2, but it wouldn't hurt to see your sysinfo, just in case. If this is a result of the problem that was fixed in DERBY-35, then I guess your best option would be to get a more recent set of jars--there are three sets of "snapshot" jars for 10.0.2 available from the Derby download site (http://incubator.apache.org/derby/derby_downloads.html), so you could just grab one of those and see if the problem goes away. If you get the 10.0.2 jars and still see the problem, then please post again and we can look at this more closely. Hope that helps, Army