An Sql Error 913 Occurred During Processing
Contents |
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
Db2 Sql Error Sqlcode=-104
Resources Overview DB2 SQL Error Codes White Papers Case Studies Educational Videos PARTNERS Partners Overview oracle sql error codes Partner List Becoming a Partner Register a Prospect NEWS News Releases SUPPORT Support Overview Support Login Product Compatibility BLOG Baseline Posts important db2 sql codes 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 http://www.ibm.com/support/knowledgecenter/SSEPEK_10.0.0/codes/src/tpc/n913.html 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 https://www.softbase.com/error_codes.php 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 not successful. If SQLCODE = 100, "no data" was found. For example, a FETCH statement returned no data because the cursor was positioned after the last row of the
Management Accounting Operating System Operating System Android iOS Microsoft Coding Programming J2EE Languages Database Database Data Warehousing Oracle http://www.geekinterview.com/question_details/33960 Applications Applications Clarify CRM Oracle Apps Peoplesoft Siebel Software Testing Testing Testing Tools Miscelleanous Helpdesk Mainframe Networking SAP R/3 Web Interview Coaching Career Counseling Job Interview Interview eBooks Accounting eBook C eBook Citrix eBook Job Interview eBook Career Advice Career Change Jobs Help Projects Requests Resume Help Training Advice Engineering Chemical Engineering sql error Civil Engineering Electrical Engineering Electronics Engineering Micro Processor Mechanical Engineering By Company Ask Question Home Interview QuestionsMainframeDB2 What is difference between 911 and 913 error code in DB2 ? Interview Candidate Sep 1st, 2006 4 20832 DB2 Answer First Prev Next Last Showing Answers 1 - 4 of 4 Answers Sam db2 sql error Sep 8th, 2006 The unit of work has been rolled back due to dead lock or commit-----SQL code 911 Was this answer useful?Yes Reply jayakumar Sep 10th, 2006 ABEND -911:A deadlock has occured and the rollback is done sucessfullyABEND -913A deadlock has occured ,but the rollback was unsucessfulcheers,jai Was this answer useful?Yes 1 Reply bnirmalraj Sep 26th, 2006 911 - THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO DEADLOCK OR TIMEOUT. REASON reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name913-UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON reason-code, TYPE OF RESOURCE resource-type, ANDRESOURCE NAME resource-name
Was this answer useful?Yes Reply sangramkc Nov 27th, 2006 for both -911 or -913 , you can check further SQLERRD(3) also contains the reason-code which indicates whether a deadlock or timeout occurred. The most common reason codes are: o 00C90088 - deadlock o 00C9008E - timeout Thanks,Sa