Db2 Sql Error 913
Contents |
Technote (troubleshooting) Problem(Abstract) You receive db2 sqlerror 913 deadlocks on z/OS when running WebSphere Business Events V6.2.1
Db2 Sql Error Sqlcode=-913 Sqlstate=57033
with time-based context expiration. Symptom DB2 on z/OS reports deadlock exceptions similar to the db2 error code 913 following: com.ibm.db2.jcc.t2zos.cb: [IBM/DB2][T2zos/3.6.67]T2zosResultSet.readFetch_:nativeFetch:2950: DB2 engine SQL error, SQLCODE = -913, SQLSTATE = 57033, error tokens = 00C90088;00000302;WBE621 .TSNAME5 .X'000002' Trace: 2009/04/20 09:22:00.358
Sqlcode=-913 Sqlstate=57033 Db2
01 t=9C1B58 c=UNK key=P8 (13007002) ThreadId: 00000044 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 reason code 00c9008e sqlstate 57033 .TSNAME5 .X'000002' See attached file for complete stack. Cause These exceptions 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
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
Sqlerrmc=00c9008e
Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation
Dsnt376i
Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like type 00000d01 you, helping each other. Join them; it only takes a minute: Sign up What is the difference between DB2 sql codes -913 and -904 with an example? [closed] up vote -3 down vote favorite What is the http://www-01.ibm.com/support/docview.wss?uid=swg21386398 difference between DB2 sql codes -913 and -904 with an example? db2 share|improve this question edited Jun 25 '13 at 14:09 Leons 1,186918 asked Jun 25 '13 at 12:50 Rahul khandelwal 112 closed as too broad by Andrew Barber Sep 4 '13 at 20:56 There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can http://stackoverflow.com/questions/17297845/what-is-the-difference-between-db2-sql-codes-913-and-904-with-an-example be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question. add a comment| 2 Answers 2 active oldest votes up vote 2 down vote An SQL code of -913 is UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON CODE reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name An SQL code of -904 is UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name A -913 is a deadlock, or two programs trying to get the same resource. The classic example is program 1 updating table B, then A; and program 2 updating table A, then B. Neither program can get to the second resource, so you have a deadlock. To prevent this, all of your programs must modify DB2 tables in the same order (A, then B). A -904 is an unavailable resource. A dropped table or a locked table. Both errors give you the name of the deadlocked resource or the unavailable resource. share|improve this answer answered Jun 25 '13 at 13:19 Gilbert Le Blanc 34.1k53272 add a comment| up vote 0 down vote -913 is SQL0913N Unsuccessful execution caused by deadlock or timeout. -904 is SQL0904N Unsuccessful execution caused by an unavailable resource. -904 is specific to DB2 for MVS. share|
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 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 sql 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 sql error 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.