Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 53726 invoked from network); 4 Oct 2010 10:18:28 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 Oct 2010 10:18:28 -0000 Received: (qmail 99095 invoked by uid 500); 4 Oct 2010 10:18:28 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 98900 invoked by uid 500); 4 Oct 2010 10:18:25 -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 98893 invoked by uid 99); 4 Oct 2010 10:18:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Oct 2010 10:18:24 +0000 X-ASF-Spam-Status: No, hits=-2.3 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 [148.87.113.121] (HELO rcsinet10.oracle.com) (148.87.113.121) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Oct 2010 10:18:17 +0000 Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o94AHsTE021953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 4 Oct 2010 10:17:55 GMT Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o94AHrbe027106; Mon, 4 Oct 2010 10:17:54 GMT Received: from abhmt007.oracle.com by acsmt353.oracle.com with ESMTP id 651546061286187466; Mon, 04 Oct 2010 03:17:46 -0700 Received: from [129.159.139.223] (/129.159.139.223) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 04 Oct 2010 03:17:46 -0700 Message-ID: <4CA9A9DE.2070500@oracle.com> Date: Mon, 04 Oct 2010 12:18:06 +0200 From: Kristian Waagan User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.7) Gecko/20100830 Thunderbird/3.1.1 MIME-Version: 1.0 To: Derby Discussion CC: Mamatha Kodigehalli Venkatesh , avinash.bhat@nsn.com Subject: Re: Problem inserting a record with derby 10.6.1.0 References: <8130F649786FB040B748FED34D3F8D5C01F5CB80@SGSIEXC008.nsn-intra.net> <4C934739.3070109@oracle.com> <411849.99421.qm@web65704.mail.ac4.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 01.10.10 09:44, Mamatha Kodigehalli Venkatesh wrote: > > Hello all, > > I too upgraded derby from 10.5.3.0 to 10.6.1.0, I am getting below > exception > > When I tried to insert a record into the table using a prepared statement. > > java.sql.SQLException: Java exception: > 'org.apache.derby.iapi.sql.execute.Result > > SetFactory.getProjectRestrictResultSet(Lorg/apache/derby/iapi/sql/execute/NoPutR > > esultSet;Lorg/apache/derby/iapi/services/loader/GeneratedMethod;Lorg/apache/derb > > y/iapi/services/loader/GeneratedMethod;ILorg/apache/derby/iapi/services/loader/G > > eneratedMethod;IZZDD)Lorg/apache/derby/iapi/sql/execute/NoPutResultSet;: > java.la > > ng.NoSuchMethodError'. > > at > org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknow > > n Source) > > at > org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) > > at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source) > > at > org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException > > (Unknown Source) > > at > org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Un > > known Source) > > at > org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown So > > urce) > > at > org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown So > > urce) > > at > org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown So > > urce) > > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Un > > known Source) > > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unkno > > wn Source) > > However Iam able to insert a record into table through ij editor. > Hi Mamatha, Looks like Derby is using some old generated code or something, and that the referred method no longer exists. If that's the case, there is a bug in the Derby upgrade logic. Did you boot the database with "upgrade=true", or did you do a soft upgrade [1]? Also, I'm assuming that you ran with the released Derby jars and not a custom build. Regards, -- Kristian [1] http://wiki.apache.org/db-derby/UpgradingTen > Thanks > > Mamatha > > ------------------------------------------------------------------------ > > *From:* Lily Wei [mailto:lilywei@yahoo.com] > *Sent:* Tuesday, September 21, 2010 1:49 AM > *To:* Derby Discussion > *Cc:* avinash.bhat@nsn.com > *Subject:* Re: Problem! > > Hi Avinash: > You can find the changes from 10.5.3.0 to 10.6.1.0 in here: > http://wiki.apache.org/db-derby/DerbyTenSixOneRelease > > Does your application change behavior because of new features? As > Kristian point out, the trace will give us more information in turn of > which part of Derby the problem occurs along with what operation is > performed to upgrade derby from 10.5.3.0 to 10.6.1.0. > > > Hope this help, > Lily > > ------------------------------------------------------------------------ > > *From:* Kristian Waagan > *To:* derby-user@db.apache.org > *Sent:* Fri, September 17, 2010 3:47:21 AM > *Subject:* Re: Problem! > > On 17.09.10 12:11, Bhat, Avinash (NSN - IN/Bangalore) wrote: > > > > Hi, > > > > This is avinash bhat, I am facing a problem in derby upgrade. > Currently I have 10.5.0.3 version installed in my system and when I > tried upgrading it to 10.6.0.1 my software is not able to load it is > throwing null pointer exception. But it is able to create databases > for the first time and if database already exist it says Null pointer > exception. > > > > Can I know what is the problem which I am facing? Or do I know what > major difference that you people have made between 10.5.0.3 and 10.6.0.1? > > > > Hi Avinash, > > I don't know why you get this error. > Can you post the stack trace you get when hitting the problem? > ( written to the console, or to derby.log ) > Also, are you doing a hard upgrade (specifying upgrade=true in the > connection URL), or are you doing a soft upgrade (no special > attributes in the connection URL)? > > The trace may tell us in which part of Derby the problem occurs. > > > Regards, > -- Kristian > > > With regards, > > Avinash Bhat > > >