Db2 Error Code 913
Contents |
Technote (troubleshooting) Problem(Abstract) You receive deadlocks on z/OS when db2 sql error sqlcode=-913 running WebSphere Business Events V6.2.1 with time-based context expiration. Symptom reason code 00c90088 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 reason code 00c9008e db2 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
Sqlstate 428f5
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 sqlstate 42826 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 About Us ibm db2 error code Learn more about Stack Overflow the company Business Learn more about hiring developers or
Db2 Error Code 803
posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow
Db2 Error Code 104
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 up vote 3 down vote http://www-01.ibm.com/support/docview.wss?uid=swg21386398 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 while, I get a rollback and http://stackoverflow.com/questions/16530919/timeout-updating-db2-table 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 through the code from the beginning of the request to where it gets 'stuck'
Samples & SAS Notes Focus Areas SUPPORT License Assistance Manage My Software Account Downloads & Hot Fixes TRAINING & BOOKS Books Training Certification SAS Global Academic http://support.sas.com/kb/50803 Program SAS OnDemand For Academics USERS GROUPS Advanced Search support.sas.com Knowledge Base Support Training & Books Store Support Communities Knowledge Base Products & Solutions System Requirements Install https://www.softbase.com/error_codes.php Center Third-Party Software Reference Documentation Papers Samples & SAS Notes Browse by Topic Search Samples Search Usage Notes Search Installation Notes Search Problem Notes Focus Areas Problem Note db2 error 50803: The occurrence of a -913 error from DB2 might not stop subsequent steps from processing Subsequent steps might still be executed when you are running a query in a z/OS operating environment when the following conditions exist: The DB2 query results in a deadlock and a -913 error is issued. The system option DB2RRS is specified. db2 error code In addition, to the job continuing to process, the job return code might still be 0. The DB2 error might look similar to the following: DB2 ERROR: RESULT OF SQL STATEMENT: DSN00913E UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON CODE 00C9008E, TYPE OF RESOURCE 00000D01, AND RESOURCE NAME 00000285.00013904 A DUMP OF THE SQLCA FOR THE GET DIAGNOSTICS REQUEST FOLLOWS: ROW NUMBER: 0 ERROR CONDITION: 1 REASON CODE: 13172878 SQLCODE: -913 SQLSTATE: 57033 SQLERRP: DSNXRUP2 There is no workaround for this issue other than not using the system option DB2RRS. Operating System and Release InformationProduct FamilyProductSystemSAS ReleaseReportedFixed*SAS SystemSAS/ACCESS Interface to DB2z/OS9.2 TS2M3* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed. A fix for this issue for SAS/ACCESS Interface to DB2 9.3_M2 is available at:http://ftp.sas.com/techsup/download/hotfix/HF2/J41.html#50803 Type:Problem NotePriority:highDate Modified:2013-09-16 09:28:34Date Created:2013-08-19 17:12:10 This content is presented in an iframe, which your browser does not support. To view the RateIT tab, click here.
Programmers For Administrators For DBA Managers PRODUCTS Products Overview TestBase TestBase Slice Batch Healthcare - Attach Facility Batch Healthcare - Attach Facility's MRF Feature Batch Healthcare - Batch Analyzer Batch Healthcare - Checkpoint Facility Batch Healthcare - Deadlock Advisor SoftDate RESOURCES Resources Overview DB2 SQL Error Codes White Papers Case Studies Educational Videos PARTNERS Partners Overview Partner List Becoming a Partner Register a Prospect NEWS News Releases SUPPORT Support Overview Support Login Product Compatibility BLOG Baseline Posts Baseline Videos ABOUT US About SoftBase People Careers Legal Privacy Area Info Contact Info Contact Us Home Resources DB2 SQL Error Codes DB2 SQL Error Codes SQL return codes provided by DB2 UDB for OS/390 and z/OS can be confusing and often reference manuals are not available or close at hand when you really need them. This reference will review SQL return code processing and common SQL error condition codes you may encounter in DB2. SQL Error Code Lookup Retrieving SQL Return Code Information & Messages COBOL programs executing SQL statements communicate with DB2 via a Working Storage area called the SQL Communications Area (SQLCA). When DB2 executes SQL statements, it returns the results of the operation into the SQLCODE and SQLSTATE fields in the SQLCA. SQLCODE provides key information about the success or failure of SQL statement execution. If the SQLWARNO field in the SQLCA contains 'W', DB2 has set at least one of the SQL warning flags (SQLWARN1 through SQLWARNA). These flags provide additional info about execution of specific types of SQL. Prior to DB2 V8, COBOL programs could call a subroutine called DSNTIAR that would convert a SQLCODE in the SQLCA into more a detailed text message with diagnostics about the return code. New with DB2 V8, COBOL programs can now execute a GET DIAGNOSTICS statement that will return all previous SQLCA values and provide additional information about new DB2 V8 extended object names and new SQL functions. The new GET DIAGNOSTICS function replaces existing SQLCA processing now found in most DB2 COBOL programs. GET DIAGNOSTICS also passes a text message about SQLCODE directly to programs. SQLCODE Overview If SQLCODE = 0, execution was successful. If SQLCODE > 0, execution was successful with a warning. If SQLCODE < 0, execution was n