911 Db2 Error
Contents |
deadlock; hang; PersistentLockManager; SQLCODE: -911 Technote (troubleshooting) Problem(Abstract)
Sqlcode=-911 Sqlstate=40001 Sqlerrmc=2
DB2 database deadlocks and SQLCODE -911 occur in the PersistentLockManager calls. Symptom The following exception
Db2 Sqlcode=-911 Sqlstate=40001
is written in the profileRoot/profileName/logs/serverName/SystemOut.log file: PersistentLoc E com.ibm.wbiserver.sequencing.lkmgr.PersistentLockManagerBean unlockAndGrantNext Error in unlock and grant next com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -911, SQLSTATE: 40001, SQLERRMC: 2 at com.ibm.db2.jcc.b.yg.b(yg.java:3046) at com.ibm.db2.jcc.c.eb.h(eb.java:268) db2 sqlcode=-911 sqlstate=40001 sqlerrmc=68 at com.ibm.db2.jcc.c.eb.a(eb.java:229) at com.ibm.db2.jcc.c.eb.c(eb.java:33) at com.ibm.db2.jcc.c.u.a(u.java:34) at com.ibm.db2.jcc.c.j.Ib(j.java:257) at com.ibm.db2.jcc.b.yg.Q(yg.java:2896) at com.ibm.db2.jcc.c.d.g(d.java:1444) at com.ibm.db2.jcc.b.eb.a(eb.java:191) at com.ibm.db2.jcc.b.yg.c(yg.java:274) at com.ibm.db2.jcc.b.yg.next(yg.java:238) at com.ibm.ws.rsadapter.jdbc.WSJdbcResultSet.next(WSJdbcResultSet.java:2468) at com.ibm.wbiserver.sequencing.lkmgr.PersistentLockManagerBean .unlockAndGrantNext(PersistentLockManagerBean.java:299) at com.ibm.wbiserver.sequencing.lkmgr.PersistentLockManagerBean .unlock(PersistentLockManagerBean.java:225) at com.ibm.wbiserver.sequencing.lkmgr.EJSLocalStatelessPersistent LockManager_19c5d0a6.unlock(Unknown Source) at com.ibm.wbiserver.sequencing.wcc.UnlockUtil.unlockOnly(UnlockUtil.java:103) at com.ibm.wbiserver.sequencing.wcc.UnlockUtil.unlock(UnlockUtil.java:75) The error indicates that a deadlock occurred in the DB2 database server. Following is the deadlock data that is captured from the DB2 database. This data comes from the formatted output of the DB2DETAILDEADLOCK event monitor, which is created and active by default for every DB2 database: Deadlock ID: 889 (Deadlock detection time: 10/22/2009 11
administering Portal SQLCODE: -911; SQLSTATE: 40001; SQLERRMC: sqlcode 911 68; -911; 911; 40001; 68 Technote (troubleshooting) Problem(Abstract) While db2 811 error performing an administrative task in WebSphere Portal (either with XMLAccess, thru the Portal Adminstration db2 911 68 Pages, or a WPSconfig/ConfigEngine script), a DB2 exception with SQLCODE: -911, SQLSTATE: 40001, SQLERRMC: 68 appears. Symptom The exception will resemble the following http://www-01.ibm.com/support/docview.wss?uid=swg21410155 (taken from 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 About Us Learn more about Stack Overflow the company Business Learn http://stackoverflow.com/questions/12463493/db2-sql-error-sqlcode-911-sqlstate-40001-sqlerrmc-68 more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like https://en.wikipedia.org/wiki/DB2_SQL_return_codes you, helping each other. Join them; it only takes a minute: Sign up DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68 up vote 0 down vote favorite I am getting this error when I ran: alter table tablename add column db2 sql columnname varchar(1) default 'N'; DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68 How to solve it? db2 share|improve this question edited Nov 7 '13 at 15:21 Benjamin 11.3k1692171 asked Sep 17 '12 at 16:31 Naga 1442311 add a comment| 4 Answers 4 active oldest votes up vote 1 down vote The alter statement wants to get an X lock on this row in SYSIBM.SYSTABLES. There is an open transaction that has this row/index value in an incompatible lock db2 sqlcode=-911 sqlstate=40001 state. This lock that caused the timeout could even be from an open cursor that reads this row with an RS or RR isolation level. Terminate any other SQL currently trying to query SYSTABLES and any utilities that may be trying to update SYSTABLES like reorg and runstats then try the alter again. share|improve this answer answered Apr 23 '15 at 13:55 Bill Peck 362 Run "db2 get snapshot for locks on
feature of DB2 programs is the error processing. The error diagnostic containing the SQL Return Code is held in the field SQLCODE within the DB2 SQLCA block. SQLCODE is no longer part of the SQL-standard. The SQL-standard replaced SQLCODE by the more detailed SQLSTATE. Contents 1 SQLCA 2 SQLCODE 2.1 Zero (Successful) 2.2 Negative values (Errors) 2.3 Positive Values (Warnings) 3 References SQLCA[edit] The SQL communications area (SQLCA) structure is used within the DB2 program to return error information to the application program. This information in the SQLCA and the SQLCODE field is updated after every API call for the SQL statement... SQLCA contains ERROR HANDLING data SQLCODE[edit] The SQLCODE field contains the SQL return code. The code can be zero (0), negative or positive. 0 means successful execution. Negative means unsuccessful with an error. An example is -911 which means a timeout has occurred with a rollback. Positive means successful execution with a warning. An example is +100 which means no rows found or end of table Here is a more comprehensive list of the SQLCODEs for DB2: Zero (Successful)[edit] 0 Successful Negative values (Errors)[edit] -007 The specified 'character' is not a valid character in SQL statements. -010 THE string constant beginning with string is not terminated properly. -029 INTO Clause required. -060 INVALID type SPECIFICATION: spec -084 Unacceptable SQL statement. -101 The statement is too long or too complex. -102 String constant is too long. -104 Illegal symbol encountered in the SQL statement. -117 The number of values in the INSERT does not match the number of columns. -122 Column or Expression in the Select List is not valid -180 Bad data in Date/Time/Timestamp. -181 Bad data in Date/Time/Timestamp. -188 The host variable in a DESCRIBE statement is not a valid string representation of a name. -199 Illegal use of the specified keyword. -204 Object not defined to DB