Db2 Sql Error Sqlcode=-913 Sqlstate=57033
Contents |
with a mandatory word, e.g. keyword2 keyword1 +keyword2 Questions excluding a
Sqlcode 913
word, e.g. keyword2 keyword1 -keyword2 Questions with a specific db2 sql error sqlcode 913 sqlstate 57033 sqlerrmc 00c9008e tag and keyword(s) +[tag1] keyword1 Questions with two or more specific tags and db2 sql error sqlcode 204 sqlstate 42704 keyword(s) +[tag1] +[tag2] keyword1 To search for all posts by a user or all posts with a specific tag, start typing and
Db2 Sql Error Sqlcode 302 Sqlstate 22001
choose from the suggestion list. Tags Spaces API Connect Appsecdev BPM Blockchain Bluemix CICS Cloud Analytics Cloud marketplace Content Services (ECM) Continuous Testing Courses DB2 LUW DataPower Decision Optimization DevOps Services Digital Experience Hadoop IBM Design IIDR ITOA InformationServer Integration Bus Internet of Things
Db2 Sql Error Sqlcode 803 Sqlstate 23505
LinuxONE Mainframe Messaging Node.js ODM Open Predictive Analytics PureData for Analytics Push Run Book Automation Storage Streamsdev Swift UrbanCode WASdev WSRR Watson dW Answers Help dW Premium developerWorks Team Watson Health More Users Badges Ask a question Why am I getting a SQLCODE=-913, SQLSTATE=57033 error-message when executing a WebSphere batch-job? Question by Ayron Fears ( 1822) | Mar 31, 2015 at 07:22 AM waswebsphere application serverwebspherewebsphere batch I am getting SQLCODE=-913, SQLSTATE=57033 error-messages when executing a WebSphere batch-job. The detailed exception stack-trace was: StepManagerIm E com.ibm.ws.gridcontainer.batch.impl.StepManagerImpl executeStep ERROR-->exception during job execution: com.ibm.batch.api.BatchContainerRuntimeException: CWLRB1520E: [Long Running Job Container [Batch Data Stream outputStream] [job
Technote (troubleshooting) Problem(Abstract) You receive deadlocks on z/OS when db2 sql error sqlcode 104 sqlstate 42601 running WebSphere Business Events V6.2.1 with time-based context expiration. Symptom
Db2 Sql Error Sqlcode 206 Sqlstate 42703
DB2 on z/OS reports deadlock exceptions similar to the following: com.ibm.db2.jcc.t2zos.cb: [IBM/DB2][T2zos/3.6.67]T2zosResultSet.readFetch_:nativeFetch:2950: DB2 engine db2 sql error sqlcode 551 sqlstate 42501 SQL error, SQLCODE = -913, SQLSTATE = 57033, error tokens = 00C90088;00000302;WBE621 .TSNAME5 .X'000002' Trace: 2009/04/20 09:22:00.358 01 t=9C1B58 c=UNK key=P8 (13007002) ThreadId: 00000044 https://developer.ibm.com/answers/questions/183297/why-am-i-getting-a-sqlcode-913-sqlstate57033-error.html FunctionName: com.ibm.wbe.db.DataSourceDB SourceId: com.ibm.wbe.db.DataSourceDB Category: SEVERE ExtendedMessage: BEER0886E: An error occurred while processing a result set: com.ibm.db2.jcc.t2zos.cb: [IBM/DB2][T2zos/3.6.67]T2zo sResultSet.readFetch_:nativeFetch:2950: DB2 engine SQL error, SQLCODE = -913, SQLSTATE = 57033, error tokens = 00C90088;00000302;WBE 621 .TSNAME5 .X'000002' See attached file for complete stack. Cause These exceptions http://www-01.ibm.com/support/docview.wss?uid=swg21386398 are the result of the steps table daemon attempting to execute deletes against the steps table at the same time as regular complex filter evaluation is accessing the steps table in read mode. Resolving the problem Disable automated context expiration clean-up on z/OS. Refer to the Pruning the WebSphere Business Events steps table automatically topic in the WebSphere Business Events information center for instructions. If clean-up is required on the steps table, it should be performed manually. Refer to the Pruning the WebSphere Business Events steps table manually topic in the WebSphere Business Events information center for instructions. Document information More support for: WebSphere Business Events Usability Software version: 6.2.1 Operating system(s): z/OS Reference #: 1386398 Modified date: 2009-06-09 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
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 http://stackoverflow.com/questions/16530919/timeout-updating-db2-table About Us Learn more about Stack Overflow the company Business Learn 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 you, helping each other. Join them; it only takes a minute: Sign up Timeout updating DB2 table db2 sql up vote 3 down vote favorite 1 I am doing an update to a DB2 table like this (java code): // Some code ripped out for brevity... sql.append("UPDATE " + TABLE_THREADS + " "); sql.append("SET STATUS = ? "); sql.append("WHERE ID = ?"); conn = getConn(); pstmt = conn.prepareStatement(sql.toString()); int idx1 = 0; pstmt.setInt(++idx1, status); pstmt.setInt(++idx1, id); int rowsUpdated = pstmt.executeUpdate(); return rowsUpdated; After a long db2 sql error while, I get a rollback and an error message: UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON CODE 00C9008E, TYPE OF RESOURCE 00000302, AND RESOURCE NAME SOME.THING.X'000002'. SQLCODE=-913, SQLSTATE=57033, DRIVER=3.57.82 The documentation for error -913 says this REASON CODE means it is a timeout. The resource type, 00000302 is a table space page, and I do not recognize the resource name at all. When I run the SQL by itself, it works fine: UPDATE MY.THREADS SET STATUS = 1 WHERE ID = 156 I can SELECT and see the status has been updated. (Although when I run this SQL during the long wait period before the timeout, I have the same issue. It takes forever and I just cancel it). There are several things happening in the transaction and I don't see any other updates to this table or record. There are create/delete triggers on the table, but no update triggers. I don't see any selects with cursors, or weird isolation level changes. I don't see much else in the transaction that would cause this. Why am I getting this error? What else should I look for in the transaction? EDIT: I stepped t