Db2 Sql Error Sqlcode=-911 Sqlstate=40001 Sqlerrmc=68
Contents |
administering Portal SQLCODE: -911; SQLSTATE: 40001; SQLERRMC: 68; db2 sql error sqlcode=-911 sqlstate=40001 sqlerrmc=2 -911; 911; 40001; 68 Technote (troubleshooting) Problem(Abstract) While performing
Db2 Sql Error Sqlcode=-1218 Sqlstate=57011
an administrative task in WebSphere Portal (either with XMLAccess, thru the Portal Adminstration Pages,
Db2 Sqlstate 40001
or a WPSconfig/ConfigEngine script), a DB2 exception with SQLCODE: -911, SQLSTATE: 40001, SQLERRMC: 68 appears. Symptom The exception will resemble the following (taken from
Db2 Sqlcode 911
an XMLAccess script): ==============================
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site db2 sql error sqlerrmc 68 About Us Learn more about Stack Overflow the company Business Learn more about sqlcode 911 sqlstate 40001 sqlerrmc 2 hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join sqlstate=40001 reason code 68 the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up DB2 deadlock timeout Sqlstate: http://www-01.ibm.com/support/docview.wss?uid=swg21440972 40001, reason code 68 due to update statements called from servlet using SQL up vote 6 down vote favorite 3 I am calling update statements one after the other from a servlet to DB2. I am getting error sqlstate 40001, reason code 68 which i found it is due to deadlock timeout. How can I resolve this issue? Can it be resolved by setting query timeout? http://stackoverflow.com/questions/7957887/db2-deadlock-timeout-sqlstate-40001-reason-code-68-due-to-update-statements-ca If yes then how to use it with update statements in servlet or where to use it? db2 share|improve this question edited Nov 22 '11 at 22:28 Adam Wagner 8,61742858 asked Oct 31 '11 at 18:18 user1022467 31112 add a comment| 1 Answer 1 active oldest votes up vote 9 down vote The reason code 68 already tells you this is due to a lock timeout (deadlock is reason code 2) It could be due to other users running queries at the same time that use the same data you are accessing, or your own multiple updates. Begin by running db2pd -db locktest -locks show detail from a db2 command line to see where the locks are. You'll then need to run something like: select tabschema, tabname, tableid, tbspaceid from syscat.tables where tbspaceid = # and tableid = # filling in the # symbols with the ID number you get from the db2pd command output. Once you see where the locks are, here are some tips: ◦Deadlock frequency can sometimes be reduced by ensuring that all applications access their common data in the same order – meaning, for example, that they access (and
be sure to check out the FAQ by clicking the link above. You may have to register before you can post: http://www.dbforums.com/showthread.php?1629947-DB2-SQL-Error-SQLSTATE-40001-SQLERRMC-68 click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 2 of 2 https://bytes.com/topic/db2/answers/180485-sql-error-911-a Thread: DB2 SQL Error: SQLSTATE: 40001, SQLERRMC: 68 Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid db2 sql Mode Switch to Threaded Mode 05-01-08,18:15 #1 Priya M View Profile View Forum Posts Registered User Join Date May 2008 Posts 1 Unanswered: DB2 SQL Error: SQLSTATE: 40001, SQLERRMC: 68 Hi, I am getting the following exception when there are multiple instances of EJB that try to update the same row in the database. I have a sequence number db2 sql error stored in a properties table and two nodes in a cluster have EJBs running that want to increment this sequence number. The exception is occuring when the code does a save on the hiberate DAO object, to update the row. Could someone please tell me what do I need to do to avoid this error? I would really appreciate your help. Caused by: com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -911, SQLSTATE: 40001, SQLERRMC: 68 at com.ibm.db2.jcc.b.rc.b(rc.java:3180) at com.ibm.db2.jcc.a.eb.i(eb.java:227) at com.ibm.db2.jcc.a.eb.a(eb.java:183) at com.ibm.db2.jcc.a.eb.a(eb.java:34) at com.ibm.db2.jcc.a.s.a(s.java:30) at com.ibm.db2.jcc.a.h.Gb(h.java:325) at com.ibm.db2.jcc.b.rc.R(rc.java:3022) at com.ibm.db2.jcc.a.d.f(d.java:1070) at com.ibm.db2.jcc.b.r.a(r.java:191) at com.ibm.db2.jcc.b.rc.c(rc.java:302) at com.ibm.db2.jcc.b.rc.next(rc.java:277) at com.ibm.ws.rsadapter.jdbc.WSJdbcResultSet.next(WSJ dbcResultSet.java:2419) at org.hibernate.loader.Loader.doQuery(Loader.java:68 5) at org.hibernate.loader.Loader.doQueryAndInitializeNo nLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:221 1) ... 29 more Thanks, Priya Reply With Quote 05-01-08,21:24 #2 Marcus_A View Profile View Forum Posts Registered User Join Date May 2003 Location USA Posts 5,737 You are getting a locktimeout. That means that one of the applications is holding a lock on a resource (probably a row) and another application is trying to acquire an incompatible lock on the same resource. The amount of time the
get tips & solutions from a community of 418,478 IT Pros & Developers. It's quick & easy. sql error 911 P: n/a xixi i am using db2 udb v8.1 on windows 64 bit i am issue below query by doing sqlStr = INSERT INTO NJIPD.OELTOHY8_OEFTOH VALUES (xx,xxx,xxx, default) insertStatement = conn.createStatement(); insertStatement.executeUpdate(sqlStr); com.ibm.db2.jcc.a.SqlException: DB2 SQL error: SQLCODE: -911, SQLSTATE: 40001, SQLERRMC: 68 somehow i get the record lock error so why i just do the execute update and will this error happened? thanks Nov 12 '05 #1 Post Reply Share this Question 1 Reply P: n/a Mark A "xixi"