Contention Error Db2
Contents |
the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. db2 sqlcode -911 Results 1 to 4 of 4 Thread: db2 contention issue Tweet Thread Tools Show Printable db2 error codes list mainframe Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 12-15-03,07:26 #1 PSivadasan db2 sql error codes pdf View Profile View Forum Posts Registered User Join Date Dec 2003 Location India Posts 2 Unanswered: db2 contention issue We have a contention issues b/w 2 jobs job1 and job2. Job1 :- Has a program pgm1 which updates
Sql Server Error Codes
1 row of database at a time and commits it. Job2 :- It has a program pgm2 which opens a cursor with fetch only option and fetches a max of 4000 rows into an array and then closes the cursor. These 2 jobs use the same database. And we are pretty sure that they don't refer to same row (ie 4000 row selected by fetch in pgm2 are not the rows used by pgm1 for update). But contention db2 code happens closing the cursor in pgm2 and job2 abends. What could be the cause of this abend ? This abend happens very rarely only. We are using DB2 ver 7. Can this be prevented by : when ever contention happens we will call a delay of few seconds and then try opening the cursor again and populate the array again from the start. This can be allowed to happen for max of 10 times and even then if the fetch is not successful we will abend the job. or is there any other better method for solving the abend. Thanks a lot Praveen Reply With Quote 12-16-03,05:43 #2 Ravi View Profile View Forum Posts Registered User Join Date Jul 2001 Location Bangalore, India Posts 28 what is the error message? Reply With Quote 12-16-03,07:44 #3 PSivadasan View Profile View Forum Posts Registered User Join Date Dec 2003 Location India Posts 2 Hi, The cursor gets closed due to -913 and subsequent fect returns -501 and job abends. 000090 DSNT375I -DP21 PLAN=PGM2 WITH 515 000090 CORRELATION-ID=JOB2 000090 CONNECTION-ID=BATCH 000090 LUW-ID=NETPRG.PDB2DIST.BA0D47D1B8C4=152759 000090 THREAD-INFO=CA7:*:*:* 000090 IS DEADLOCKED WITH PLAN=PGM1 WITH 000090 CORRELATION-ID=JOB1 000090 CONNECTION-ID=BATCH 000090 LUW-ID=NETPRG.DP23DIST.BA0D47CEB8E8=86254 000090 THREAD-INFO=CA7:*:*:* 000090 ON MEMBER DP23 000090 000090 DSNT501I -DP21 DSNILMCL RESOURCE UNAVAILABLE 516 000090 CORRELATION-ID=JOB2 000090 CONNECTION-ID=BATCH 000090 LUW-ID=* 000090 REASON 00C90088 000090 TYPE 00000302 000090 NAME DPPFF.MBCG.X'00000D' SQL Error Timestamp. 2003-09-20-11.07.16.635712 Subsys.............. DP21 User............ CA7 Plan................ PG
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 db2 sql error sqlcode=-104 by the more detailed SQLSTATE. Contents 1 SQLCA 2 SQLCODE 2.1 Zero (Successful) 2.2 Negative values
Oracle Sql Error Codes
(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
Db2 Sql Error Sqlcode=-904
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 http://www.dbforums.com/showthread.php?974525-db2-contention-issue 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 https://en.wikipedia.org/wiki/DB2_SQL_return_codes 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 DB2. -205 Column name not in table. -206 Column does not exist in any table of the SELECT. -208 THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN column-name IS NOT PART OF THE RESULT TABLE -216 Not the same number of expressions on both sides of the comparison in a SELECT. -224 FETCH cannot make an INSENSITIVE cursor SENSITIVE. -229 The locale specified in a SET LOCALE statement was not found. -302 THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER position-number IS INVALID OR TOO LARGE FOR THE TARGET COLUMN OR THE TARGET VALUE -303 A VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER position-number BECAUSE THE DATA TYPES ARE NOT COMPARABLE -305 Null indicator needed. -311 Varchar,
+ productResults.length + resourceResults.length > 0 ? 'See all Search Results' : 'Full site search'}} > CA Support Online > KB Article How do I avoid contention on DB2 binds? How do I avoid contention on DB2 binds? Document ID:TEC476973 Last Modified Date:12/11/2008 ShowHide Technical Document Details Products http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec476973.aspx CA Alchemist CA TPX Session Management for z/OS Components ALCHEMIST Description: When we have two or more alchemist started tasks processing migrations and when they are processing DB2 Binds, we occasionally get http://mainframematerials.blogspot.com/2007/09/abends.html deadlocks on the DB2 Catalog SYSDBASE tablespace for the DB2 subsystem being updated. How can we cause the Binds to serialize across several Alchemist started tasks? We are using three external PX error codes engines and have multiple DB2 programs and get the following error: DSNT233I DB2P UNSUCCESSFUL BIND FOR ..:.According to our DBAs, this error occurs when two different processes are trying to bind the same resource at the same time. It appears that two different PX engines are binding the same resource at the same time. Re-releasing the request fixes the error, sometimes multiple times, at db2 sql error least until the bind doesn't hit something else. Solution: Ensure that you have fix SU02674 applied. Use IKJEFT1B. If your PCL is using IKJEFT01, you will need to change it to use IKJEFT1B.SU02674 DF20564 If DB2 binds are executing simultaneously, the following messagecould be issued: DSNT501I DSNP DSNXA03 RESOURCE UNAVAILABLE This PTF prevents simultaneous DB2 binds being done by Alchemist. However, it should be noted that this cannot prevent an external batch job from doing a bind at the same time as Alchemist. (This fix is available on from Support Online on the CA Alchemist Product Page. Use the link for "CA Alchemist 5.3.1 Solutions & Patches" under Recommended Reading. This fix is not available from the Download Center.) Not what you were looking for? Search Again> Product Information Support by Product> Product Documentation> Communities Join a Community> Education Find training by product> Please help us improve! Will this information enable you to resolve your issue? Yes No Please tell us what we can do better. Char: Share × Contact us Privacy Policy Legal Notices Data Transfers Site Map Copyright © 2016 CA. All rights reserved.
CICS codes CICSCD8. IMS codes IMSCD----------------------------------------------------------------------USECD - User codes----------------------------------------------------------------------U0001 - CHECK FOR WRONG BLOCKSIZE.U0002 - IMS PROBLEM - CALL OPERATION TO CHECK ON STATUS. IMS CRASHED.U0016 - IN UCC11 STEP - TRYING TO RESTART NON-RESTARTABLE STEP.IF JOB HAS STARTED AND HAS SORTWORKS IN THE STEP ABENDINGTRY INCREASING THE SORTWORKS & RESTARTING THE JOB.U0016 * PROBABLE SORT CAPACITY EXCEEDED. (MAX TO BOT OF JOBLOG)* IF EXECUTING SORT W/ PARM=MAXSORT AND JOB ABENDS WITH SORTOUXXDEVICE MIXING PROHIBITED, CHANGE THE SORTOU00 DD DSN'S TOUNIT=CTAPE AND RESTART. THIS ABEND CAN OCCUR UNTIL DASDCONVERSION IS COMPLETE, ABOUT THE 1ST OF NOV. 92.U0016 * BLOCKSIZE ON INPUT FILE SHOULD BE OMITTED.U0020 - IN UCC11 STEP - DATA SETS USED FOR RESTART DIFFER FROM PRODUCTIONRUN. TRY CANCELLING ABENDED JOB, DEMAND JOB IN ON HOLD, TYPE=RES, EDIT JCL, SATISFY HOLD REQUIREMENT TO RESTART. FOR I/PGDG CHANGE, USE BYPGDG: YES FIELD ON RESTART SCREEN.U0040 - IN UCC11 STEP - INCORRECT STEP RESTARTED, IMPROPER ORIMCOMPLETE STEP NAME.U0046 - PROBABLE PSB PROBLEM - READ VS UPDATE - CALL DBA ON CALL.U0064 - IN THE UCC11 STEP = CMT NOT CORRECT (GDG PROBLEM). THERE IS NOGDG BASE RECORD OR JOB IS CALLING ON A (0) GENERATION BUT THEREARE NO GENERATIONS CATALOGUED.ALSO CAN BE DEADLOCK, CHECK SQLCODE, TRY RESTARTING.U0102 - PROBABLE IMS PROBLEM, TRY RESTARTING.- 10/31/92 U0102 IMSLOGR DD STATEMENT MISSING - WHEN EXECUTINGCICSBTPH. DELETED STEPLIB DD PER KOSKI TO RUN. YOU COULDSUGGEST THIS TO DEV.U0109 - CHECK FOR SQL CODE.U0175 - DEADLOCK / CONTENTION.U0200 - CHECK SQL CODE IN ABENDED JOB.U0240 - A message processing application program exceeded theallowable execution time (set at IMS system definition) in a messageprocessing region. In the case of a BMP, this abend indicates that thevalue specified in "CPUTIME=" has been exceeded.System Action: A storage dump is taken and the dependent region programcontroller is reattached. In the case of a BMP step, the step isterminated.Programmer Response: Refer to the TRANSACT macro in IMS/ESA SystemDefinition Reference.U0246 - ???U0261 - INCORRECT PARM IN DL/I CALL.U0271 - I/O ERROR DETECTED WHILE PURGING BUFFERS DURING CKPOINT OPERATIONU0273 - I/O ERROR DETECTED WHILE REPOSITIONING A GSAM DATASET DURING RESTART.resolution: TRY BY GIVING OPTION AS COLD=COLD AT THE EXEC STEP.U0295 - SORT-X PROGRAM LOADED USING WRONG EXECUTE.U0304 - The caller passed a non-zero value in register 1.U0311 - A reserved field is not equal to 0 in one of the 20-bytedescription