(This article is part of our Db2 Guide. Use the right-hand menu to navigate.)
| -007 | STATEMENT CONTAINS THE ILLEGAL CHARACTER character |
| -010 | THE STRING CONSTANT BEGINNING string IS NOT TERMINATED |
| -011 | COMMENT NOT CLOSED |
| -029 | INTO CLAUSE REQUIRED |
| -051 | Identifier-name (sqltype) WAS PREVIOUSLY DECLARED OR REFERENCED |
| -056 | AN SQLSTATE OR SQLCODE VARIABLE DECLARATION IS IN A NESTED COMPOUND STATEMENT |
| -057 | THE RETURN STATEMENT IS AN SQL FUNCTION MUST RETURN A VALUE |
| -058 | VALUE SPECIFIED ON RETURN STATEMENT MUST BE AN INTEGER |
| -060 | INVALID type SPECIFICATION: spec |
| -078 | PARAMETER NAMES MUST BE SPECIFIED FOR ROUTINE routine-name |
| -079 | QUALIFIER FOR OBJECT name WAS SPECIFIED AS qualifier1 but qualifier2 IS REQUIRED |
| -084 | UNACCEPTABLE SQL STATEMENT |
| -087 | A NULL VALUE WAS SPECIFIED IN A CONTEXT WHERE A NULL IS NOT ALLOWED |
| -096 | VARIABLE variable-name DOES NOT EXIST OR IS NOT SUPPORTED BY THE SERVER AND A DEFAULT VALUE WAS NOT PROVIDED |
| -097 | THE USE OF LONG VARCHAR OR LONG VARGRAPHIC IS NOT ALLOWED IN THIS CONTEXT |
| -101 | THE STATEMENT IS TOO LONG OR TOO COMPLEX |
| -102 | LITERAL STRING IS LOO LONG, STRING BEGINS string |
| -103 | Constant IS AN INVALID NUMERIC CONSTANT |
| -104 | ILLEGAL SYMBOL ‘token’. SOME SYMBOLS THAT MIGHT BE LEGAL ARE: token-list |
| -105 | INVALID STRING |
| -107 | THE NAME name IS TOO LONG. MAXIMUM ALLOWABLE SIZE IS |
| -108 | THE NAME name IS QUALIFIED INCORRECTLY |
| -109 | Clause CLAUSE IS NOT PERMITTED |
| -110 | INVALID HEXADECIMAL LITERAL BEGINNING string |
| -111 | AN AGGREGATE FUNCTION DOES NOT INCLUDE A COLUMN NAME |
| -112 | THE OPERAND OF AN AGGREGATE FUNCTION INCLUDES AN AGGREGATE FUNCTION, AND OLAP SPECIFICATION, OR SCALAR FULLSELECT |
| -113 | INVALID CHARACTER FOUND IN string, REASON CODE nnn |
| -114 | THE LOCATION NAME location DOES NOT MATCH THE CURRENT SERVER |
| -115 | A PREDICATE IS INVALID BECAUSE THE COMPARISON OPERATOR operator IS FOLLOWED BY A PARENTHESIZED LIST OR BY ANY OR ALL WITHOUT A SUBQUERY |
| -117 | THE NUMBER OF VALUES ASSIGNED IS NOT THE SAME AS THE NUMBER OF SPECIFIED OR IMPLIED COLUMNS |
| -118 | THE OBJECT TABLE OR VIEW OF THE DELETE OR UPDATE STATEMENT IS ALSO IDENTIFIED IN A FROM CLAUSE |
| -119 | A COLUMN OR EXPRESSION IN A HAVING CLAUSE IS NOT VALID |
| -120 | AN AGGREGATE FUNCTION OR OLAP SPECIFICATION IS NOT VALID IN THE CONTEXT IN WHICH IS INVOKED |
| -121 | THE COLUMN name IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE OR SET TRANSITION VARIABLE STATEMENT |
| -122 | COLUMN OR EXPRESSION IN THE SELECT LIST IS NOT VALID |
| -123 | THE PARAMETER IN POSITION n IN THE FUNCTION name MUST BE A CONSTANT OR KEYWORD |
| -125 | AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENFITY A COLUMN OF THE RESULT |
| -126 | THE SELECT STATEMENT CONTAINS BOTH AN UPDATE CLAUSE AND AN ORDER BY CLAUSE |
| -127 | DISTINCT IS SPECIFIED MORE THAN ONCE IN A SUBSELECT |
| -128 | INVALID USE OF NULL IN A PREDICATE |
| -129 | THE STATEMENT CONTAINS TOO MANY TABLE NAMES |
| -130 | THE ESCAPE CLAUSE CONSISTS OF MORE THAN ONE CHARACTER, OR THE STRING PATTERN CONTAINS AN INVALID OCCURRENCE OF THE ESCAPE CHARACTER |
| -131 | STATEMENT WITH LIKE PREDICATE HAS INCOMPATIBLE DATA TYPES |
| -132 | AN OPERAND OF value IS NOT VALID |
| -133 | AN AGGREGATE FUNCTION IN A SUBQUERY OF HAVING A CLAUSE IS INVALID BECAUSE ALL COLUMN REFERENCES IN ITS ARGUMENT ARE NOT CORRELATED TO THE GROUP BY RESULT THAT THE HAVING CLAUSE IS APPLIED TO |
| -134 | IMPROPER USE OF STRING, LOB, XML, OR ARRAY VALUE |
| -136 | SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS TOO LONG |
| -137 | THE LENGTH RESULTING FROM operation IS GREATER THAN maximum-length |
| -138 | THE SECOND OR THIRD ARGUMENT OF THE SUBSTRI OR SUBSTRING FUNCTION IS OUT OF RANGE |
| -142 | THE SQL STATEMENT IS NOT SUPPORTED |
| -144 | INVALID SECTION NUMBER number |
| -147 | ALTER FUNCTION function-name FAILED BECAUSE SOURCE FUNCTIONS OR NOT FENCED EXTERNAL FUNCTION CANNOT BE ALTERED |
| -148 | THE SOURCE TABLE source-name CANNOT BE RENAMED OR ALTERED, REASON reason-code |
| -150 | THE OBJECT OF THE INSERT, DELETE, UPDATE, MERGE, OR TRUNCATE STATEMENT IS A VIEW, SYSTEM-MAINTAINED MATERIALIZED QUERY TABLE, OR TRANSITION TABLE FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED |
| -151 | THE UPDATE OPERATION IS INVALID BECAUSE THE CATALOG DESCRIPTION OF COLUMN column-name INDICATES THAT IT CANNOT BE UPDATED |
| -152 | THE DROP clause CLAUSE IN THE ALTER STATEMENT IS INVALID BECAUSE constraint-name IS A constraint-type |
| -153 | THE STATEMENT IS INVALID BECAUSE THE VIEW OR TABLE DEFINITION DOES NOT INCLUDE A UNIQUE NAME FOR EACH COLUMN |
| -154 | THE STATEMENT FAILED BECAUSE VIEW OR TABLE DEFINITION IS NOT VALID |
| -156 | THE STATEMENT DOES NOT IDENTIFY A TABLE |
| -157 | ONLY A TABLE NAME CAN BE SPECIFIED IN A FOREIGN KEY CLAUSE. object-name IS NOT THE NAME OF A TABLE |
| -158 | THE NUMBER OF COLUMNS SPECIFIED FOR name IS NOT THE SAME AS THE NUMBER OF COLUMNS IN THE RESULT TABLE |
| -159 | THE STATEMENT REFERENCES object-name WHICH IDENTIFIES AN object-type RATHER THAN AN expected-object-type |
| -160 | THE WITH CHECK OPTION CANNOT BE USED FOR THE SPECIFIED VIEW |
| -161 | THE INSERT OR UPDATE IS NOT ALLOWED BECAUSE A RESULTING ROW DOES NOT SATISFY THE VIEW DEFINITION |
| -164 | auth-id1 DOES NOT HAVE THE PRIVILEGE TO CREATE A VIEW WITH QUALIFICATION authorization ID |
| -170 | THE NUMBER OF ARGUMENTS SPECIFIED FOR function-name IS INVALID |
| -171 | THE DATA TYPE, LENGTH, OR VALUE OF ARGUMENT nn OF ARGUMENT nn OR function-name IS INVALID |
| -173 | UR IS SPECIFIED ON THE WITH CLAUSE BUT THE CURSOR IS NOT READ-ONLY |
| -180 | THE DATE, TIME, OR TIMESTAMP VALUE value is INVALID |
| -181 | THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID DATETIME VALUE |
| -182 | AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE IS INVALID |
| -183 | AN ARITHMETIC EXPRESSION ON A DATE OR TIMESTAMP HAS A RESULT THAT IS NOT WITHIN THE VALID RANGE OF DATES |
| -184 | AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE CONTAINS A PARAMETER MARKER |
| -185 | THE LOCAL FORMAT OPTION HAS BEEN USED WITH A DATE OR TIME AND NO LOCAL EXIT HAS BEEN INSTALLED |
| -186 | THE LOCAL DATE LENGTH OR LOCAL TIME LENGTH HAS BEEN INCREASED AND EXECUTING PROGRAM RELIED ON THE OLD LENGTH |
| -187 | A REFERENCE TO A CURRENT DATE/TIME SPECIAL REGISTER IS INVALID BECAUSE THE MVS TOD CLOCK IS BAD OR THE MVS PARMTZ IS OUT OF RANGE |
| -188 | THE STRING REPRESENTATION OF A NAME IS INVALID |
| -189 | CCSID ccsid IS INVALID |
| -190 | THE ATTRIBUTES SPECIFIED FOR THE COLUMN table-name.column-name ARE NOT COMPATIBLE WITH THE EXISTING COLUMN DEFINITION |
| -191 | A STRING CANNOT BE USED BECAUSE IT IS INVALID MIXED DATA |
| -195 | LAST COLUMN OF table-name CANNOT BE DROPPED |
| -197 | QUALIFIED COLUMN NAMES IN ORDER BY CLAUSE NOT PERMITTED WHEN UNION OR UNION ALL SPECIFIED |
| -198 | THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE STATEMENT IS BLANK OR EMPTY |
| -199 | ILLEGAL USE OF KEYWORD keyword TOKEN token-list WAS EXPECTED |
| -203 | A REFERENCE TO COLUMN column-name IS AMBIGUOUS |
| -204 | name IS AN UNDEFINED NAME |
| -205 | column-name IS NOT A COLUMN OF TABLE table-name |
| -206 | name IS NOT VALID IN THE CONTEXT WHERE IT IS USED |
| -208 | THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN name IS NOT, PART OF THE RESUT TABLE |
| -212 | name IS SPECIFIED MORE THAN ONCE IN THE REFERENCING CLAUSE OF A TRIGGER DEFINITION |
| -214 | AN EXPRESSION IN THE FOLLOWING POSITION, OR STARTING WITH position-or-expression-start IN THE clause-type CLAUSE IS NOT VALID. REASON CODE = reason-code |
| -216 | THE NUMBER OF ELEMENTS ON EACH SIDE OF A PREDICATE OPERATOR DOES NOT MATCH. PREDICATE OPERATOR IS operator |
| -219 | THE REQUIRED EXPLANATION TABLE table-name DOES NOT EXIST |
| -220 | THE COLUMN column-name IN EXPLANATION TABLE table-name IS NOT DEFINED PROPERLY |
| -221 | ‘SET OF OPTIONAL COLUMNS’ IN EXPLANATION TABLE table-name IS INCOMPLETE OPTIONAL COLUMN column-name IS MISSING |
| -222 | AN UPDATE OR DELETE OPERATION WAS ATTEMPTED AGAINST A HOLE USING CURSOR cursor-name |
| -224 | THE RESULT TABLE DOES NOT AGREE WITH THE BASE TABLE USING cursor-name |
| -225 | FETCH STATEMENT FOR cursor-name IS NOT VALID FOR THE DECLARATION OF THE CURSOR |
| -227 | FETCH fetch-orientatin IS NOT ALLOWED, BECAUSE CURSOR cursor-name HAS AN UNKNOWN POSITION (sqlcode,sqlstate) |
| -228 | FOR UPDATE CLAUSE SPECIFIED FOR READ-ONLY CURSOR cursor-name |
| -229 | THE LOCALE locale SPECIFIED IN A SET LOCALE OR OTHER STATEMENT THAT IS LOCALE SENSITIVE WAS NOT FOUND |
| -240 | THE PARTITION CLAUSE OF A LOCK TABLE STATEMENT IS INVALID |
| -242 | THE OBJECT NAMED object-name OF TYPE object-type WAS SPECIFIED MORE THAN ONCE IN THE LIST OF OBJECTS, OR THE NAME IS THE SAME AS AN EXISTING OBJECT |
| -243 | SENSITIVE CURSOR cursor-name CANNOT BE DEFINED FOR THE SPECIFIED SELECT STATEMENT |
| -244 | SENSITIVITY sensitivity SPECIFIED ON THE FETCH IS NOT VALID FOR CURSOR cursor-name |
| -245 | THE INVOCATION OF FUNCTION routine-name IS AMBIGUOUS |
| -246 | STATEMENT USING CURSOR cursor-name SPECIFIED NUMBER OF ROWS num-rows WHICH IS NOT VALID WITH dimension |
| -247 | A HOLE WAS DETECTED ON A MULTIPLE ROW FETCH STATEMENT USING CURSOR cursor-name, BUT INDICATOR VARIABLES WERE NOT PROVIDED TO DETECT THE CONDITION |
| -248 | A POSITIONED DELETE OR UPDATE STATEMENT FOR CURSOR cursor-name SPECIFIED ROW n OF A ROWSET, BUT THE ROW IS NOT CONTAINED WITHIN THE CURRENT ROWSET |
| -249 | DEFINITION OF ROWSET ACCESS FOR CURSOR cursor-name IS INCONSISTENT WITH THE FETCH ORIENTATION CLAUSE clause SPECIFIED |
| -250 | THE LOCAL LOCATION NAME IS NOT DEFINED WHEN PROCESSING A THREE-PART OBJECT NAME |
| -251 | TOKEN name IS NOT VALID |
| -253 | A NON-ATOMIC statement STATEMENT SUCCESSFULLY COMPLETED FOR SOME OF THE REQUESTED ROWS, POSSIBLY WITH WARNINGS, AND ONE OR MORE ERRORS |
| -254 | A NON-ATOMIC statement STATEMENT ATTEMPTED TO PROCESS MULTIPLES ROWS OF DATA, BUT ERRORS OCCURRED |
| -270 | FUNCTION NOT SUPPORTED |
| -300 | THE STRING CONTAINED IN HOST VARIABLE OR PARAMETER position-number IS NOT NUL-TERMINATED |
| -301 | THE VALUE OF INPUT HOST VARIABLE OR PARAMETER NUMBER position-number CANNOT BE USED AS SPECIFIED BECAUSE OF ITS DATA TYPE |
| -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 |
| -304 | A VALUE WITH DATA TYPE data-type1 CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE OF THE HOST VARIABLE IN POSTION position-number WITH DATA TYPE data-type2 |
| -305 | THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER position-number BECAUSE NO INDICATOR VARIABLE IS SPECIFIED |
| -309 | A PREDICATE IS INVALID BECAUSE A REFERENCED HOST VARIABLE HAS THE NULL VALUE |
| -310 | DECIMAL HOST VARIABLE OR PARAMETER number CONTAINS NON-DECIMAL DATA |
| -311 | THE LENGTH OF INPUT HOST VARIABLE NUMBER position-number IS NEGATIVE OR GREATER THAN THE MAXIMUM |
| -312 | VARIABLE variable-name IS NOT DEFINED OR NOT USABLE |
| -313 | THE NUMBER OF HOST VARIABLES SPECIFIED IS NOT EQUAL TO THE NUMBER OF PARAMETER MARKERS |
| -314 | THE STATEMENT CONTAINS AN AMBIGUOUS HOST VARIABLE REFERENCE |
| -327 | THE ROW CANNOT BE INSERTED BECAUSE IT IS OUTSIDE THE BOUND OF THE PARTITION RANGE FOR THE LAST PARTITION |
| -330 | A STRING CANNOT BE USED BECAUSE IT CANNOT BE PROCESSED, REASON reason-code, CHARACTER code-point, HOST VARIABLE position-nuumber |
| -331 | CHARACTER CONVERSION CANNOT BE PERFORMED BECAUSE A STRING, POSITION position-number, CANNOT BE CONVERTED FROM source-ccsid TO target-ccsid, REASON reason-code |
| -332 | CHARACTER CONVERSION BETWEEN CCSID from-ccsid TO to-ccsid, REASON reason-code |
| -333 | THE SUBTYPE OF A STRING VARIABLE IS NOT THE SAME AS THE SUBTYPE KNOWN AT BIND TIME AND THE DIFFERENCE CANNOT BE RESOLVED BY CHARACTER CONVERSION |
| -336 | THE SCALE OF THE DECIMAL NUMBER MUST BE ZERO |
| -338 | AN ON CLAUSE IS INVALID |
| -340 | THE COMMON TABLE EXPRESSION name HAS THE SAME IDENTIFIER AS ANOTHER OCCURRENCE OF A COMMON TABLE EXPRESSION DEFINITION WITHIN THE SAME STATEMENT |
| -341 | A CYCLIC REFERENCE EXISTS BETWEEN THE COMMON TABLE EXPRESSIONS name1 AND name2 |
| -342 | THE COMMON TABLE EXPRESSION name MUST NOT USE SELECT DISTINCT AND MUST USE UNION ALL BECAUSE IT IS RECURSIVE |
| -343 | THE COLUMN NAMES ARE REQUIRED FOR THE RECURSIVE COMMON TABLE EXPRESSION name |
| -344 | THE RECURSIVE COMMON TABLE EXPRESSION name HAS MISMATCHED DATA TYPES OR LENGTHS OR CODE PAGE FOR COLUMN column-name |
| -345 | THE FULLSELECT OF THE RECURSIVE COMMON TABLE EXPRESSION name MUST BE A UNION ALL AND MUST NOT INCLUDE AGGREGATE FUNCTIONS, GROUP BY, HAVING, ORDER BY, OFFSET, FETCH FIRST, OR AN EXPLICIT JOIN INCLUDING AN ON CLAUSE |
| -346 | AN INVALID REFERENCE TO COMMON TABLE EXPRESSION name OCCURS IN THE FIRST FULL SELECT, AS A SECOND OCCURRENCE IN THE SAME FROM CLOSE, OR IN THE FROM CLAUSE OF A SUBQUERY |
| -348 | Sequence-expression CANNOT BE SPECIFIED IN THIS CONTEXT |
| -350 | column-name WAS IMPLICITLY OR EXPLICITLY REFERENCED IN A CONTEXT IN WHICH IT CANNOT BE USED |
| -351 | AN UNSUPPORTED SQL TYPE WAS ENCOUNTERED IN POSITION position-number OF THE SELECT-LIST |
| -352 | AN UNSUPPORTED SQL TYPE WAS ENCOUNTERED IN POSITION position-number OF THE INPUT-LIST |
| -353 | FETCH IS NOT ALLOWED BECAUSE CURSOR cursor-name HAS AN UNKNOWN POSITION |
| -354 | A ROWSET FETCH STATEMENT MAY HAVE RETURNED ONE OR MORE ROWS OF DATA. HOWEVER, ONE OR MORE NON-TERMINATING ERROR CONDITIONS WERE ENCOUNTERED. USE THE GATE DIAGNOSTICS STATEMENT FOR MORE INFORMATION REGARDING THE CONDITIONS THAT WERE ENCOUNTERED |
| -355 | A LOB COLUMN IS TOO LARGE TO BE LOGGED |
| -356 | COLUMN OR KEY EXPRESSION expression-number IS NOT VALID, REASON CODE = reason-code |
| -359 | THE RANGE OF VALUES FOR THE IDENTITY COLUMN IS EXHAUSTED |
| -363 | THE EXTENDED INDICATOR VARIABLE VALUE FOR PARAMETER position-number IS OUT OF RANGE |
| -365 | USE OF THE VALUE OF EXTENDED INDICATOR VARIABLE AND POSITION value-position IS NOT VALID |
| -372 | ONLY ONE ROWID, IDENTITY, ROW CHANGE TIMESTAMP, ROW BEGIN, ROW END, TRANSACTION START ID, OR SECURITY LABEL COLUMN IS ALLOWED IN THE TABLE |
| -373 | DEFAULT CANNOT BE SPECIFIED FOR COLUMN OR SQL VARIABLE name |
| -374 | THE CLAUSE clause HAS NOT BEEN SPECIFIED IN THE CREATe OR ALTER FUNCTION STATEMENT FOR LANGUAGE SQL FUNCTION function-name BUT AN EXAMINATION OF THE FUNCTION BODY REVEALS THAT IT SHOULD BE SPECIFIED |
| -390 | THE FUNCTION function-name SPECIFIC NAME specific-name IS NOT VALID IN THE CONTEXT WHERE IT IS USED |
| -392 | SQLDA PROVIDED FOR CURSOR cursor HAS BEEN CHANGED FROM THE PREVIOUS FETCH |
| -393 | THE CONDITION OR CONNECTION NUMBER IS INVALID |
| -396 | Object-type object-name ATTEMPTED TO EXECUTE AN SQL STATEMENT DURING FINAL CALL PROCESSING |
| -397 | GENERATED IS SPECIFIED AS PART OF A COLUMN DEFINITION, BUT IT IS NOT VALID FOR THE DEFINITION OF THE COLUMN |
| -398 | A LOCATER WAS REQUESTED FOR HOST VARIABLE NUMBER position-number FOR THE VARIABLE IS NOT A LOB |
| -399 | INVALID VALUE ROWID WAS SPECIFIED |
| -400 | THE CATALOGUE HAS THE MAXIMUM NUMBER OF USER DEFINED INDEXES |
| -401 | THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE NOT COMPARABLE |
| -402 | AN ARITHMETIC FUNCTION OR OPERATOR arith-fop IS APPLIED TO CHARACTER OR DATETIME DATA |
| -404 | THE SQL STATEMENT SPECIFIES A STRING THAT IS TOO LONG |
| -405 | THE NUMERIC LITERAL literal CANNOT BE USED AS SPECIFIED BECAUSE IT IS OUT OF RANGE |
| -406 | A CALCULATED OR DERIVED NUMERIC VALUE IS NOT WITHIN THE RANGE OF ITS OBJECT COLUMN |
| -407 | AN UPDATE, INSERT, OR SET VALUE WAS NULL, BUT THE OBJECT COLUMN column-name CANNOT CONTAIN NULL VALUES |
| -408 | THE VALUE IS NOT COMPATIBLE WITH THE DATA TYPE OF THE TARGET. TARGET NAME IS name |
| -409 | INVALID OPERAND OF A COUNT FUNCTION |
| -410 | A NUMERIC VALUE value IS TOO LONG, ORIT HAS A VALUE THAT IS NOT WITHIN THE RANGE OF ITS DATA TYPE |
| -411 | CURRENT SQLID CANNOT BE USED IN A STATEMENT THAT REFERENCES REMOTE OBJECTS |
| -412 | THE SELECT CLAUSE OF A SUBQUERY SPECIFIES MULTIPLE COLUMNS |
| -413 | OVERFLOW OR UNDERFLOW OCCURRED DURING NUMERIC DATA TYPE CONVERSION |
| -414 | A LIKE PREDICATE IS INVALID BECAUSE THE FIRST OPERAND IS NOT A STRING |
| -415 | THE CORRESPONDING COLUMNS, column-number, OF THE OPERANDS OF A SET OPERATOR ARE NOT COMPATIBLE |
| -416 | AN OPERAND OF A UNION CONTAINS A LONG STRING COLUMN |
| -417 | A STATEMENT STRING TO BE PREPARED INCLUDES PARAMETER MARKERS AS THE OPERANDS OF THE SAME OPERATOR |
| -418 | A STATEMENT STRING TO BE PREPARED CONTAINS AN INVALID USE OF PARAMETER MARKERS |
| -419 | THE DECIMAL DIVIDE OPERATION IS INVALID BECAUSE THE RESULT WOULD HAVE A NEGATIVE SCALE |
| -420 | THE VALUE OF A CHARACTER STRING ARGUMENT WAS NOT ACCEPTABLE TO THE function-name FUNCTION |
| -421 | THE OPERANDS OF A UNION OR UNION ALL DO NOT HAVE THE SAME NUMBER OF COLUMNS |
| -423 | INVALID VALUE FOR LOCATOR IN POSITION position-# |
| -426 | DYNAMIC COMMIT NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOT ALLOWED |
| -427 | DYNAMIC ROLLBACK NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOT ALLOWED |
| -430 | routine-type routine-name (SPECIFIC NAME specific-name) HAS ABNORMALLY TERMINATED |
| -431 | ROUTINE routine-name (SPECIFIC NAME specific-name) OF TYPE routine-type HAS BEEN INTERRUPTED BY USER |
| -433 | VALUE value IS TOO LONG |
| -435 | AN INVALID SQLSTATE sqlstate IS SPECIFIED IN A RAISE_ERROR FUNCTION, RESIGNAL STATEMENT, OR SIGNAL STATEMENT |
| -438 | APPLICATION RAISED ERROR WITH DIAGNOSTIC TEXT: text |
| -440 | NO routine-type BY THE NAME routine-name HAVING COMPATIBLE ARGUMENTS WAS FOUND IN THE CURRENT PATH |
| -441 | INVALID USE OF ‘DISTINCT’ OR ‘ALL’ WITH FUNCTION function-name |
| -443 | ROUTINE routine-name (SPECIFIC NAME specific-name) HAS RETURNED AN ERROR SQLSTATE WITH DIAGNOSTIC TEXT msg-txt |
| -444 | USER PROGRAM name COULD NOT BE FOUND |
| -449 | CREATE OR ALTER STATEMENT FOR FUNCTION AND PROCEDURE routine-name CONTAINS AN INVALID FORMAT OF THE EXTERNAL NAME CLAUSE OR IS MISSING THE EXTERNAL NAME CLAUSE |
| -450 | USER-DEFINED FUNCTION OF STORED PROCEDURE name, PARAMETER NUMBER paranum, OVERLAYED STORAGE BEYOND ITS DECLARED LENGTH |
| -451 | THE data-item DEFINITION IN THE CREATE OR ALTER STATEMENT FOR routine-name CONTAINS DATA TYPE type WHICH IS NOT SUPPORTED FOR THE TYPE AND LANGUAGE OF THE ROUTINE |
| -452 | UNABLE TO ACCESS THE FILE REFERENCED BY HOST VARIABLE variable-position. REASON CODE: reason-code |
| -453 | THERE IS A PROBLEM WITH THE RETURNS CLAUSE IN THE CREATE FUNCTION STATEMENT FOR function-name |
| -454 | THE SIGNATURE PROVIDED IN THE CREATE FUNCTION STATEMENT FOR function-name MATCHES THE SIGNATURE OF SOME OTHER FUNCTION ALREADY EXISTING IN SCHEMA |
| -455 | IN CREATE FUNCTION FOR function-name, THE SCHEMA NAME schema-name PROVIDED SPECIFIC NAME DOES NOT MATCH THE SCHEMA NAME schema-name2 OF THE FUNCTION |
| -456 | IN CREATE FUNCTION FOR function-name, THE SPECIFIC NAME specific-name ALREADY EXISTS IN THE SCHEMA |
| -457 | A FUNCTIONS OR DISTINCT TYPE CANNOT BE CALLED name SINCE IT IS RESERVED FOR SYSTEM USE |
| -458 | IN A REFERENCE TO FUNCTION function-name BY SIGNATURE, A MATCHING FUNCTION COULD NOT BE FOUND |
| -461 | A VALUE OF DATA TYPE source-data-type CANNOT BE CAST TO TYPE target-data-type |
| -469 | SQL CALL STATEMENT MUST SPECIFY AN OUTPUT HOST VARIABLE FOR PARAMETER number |
| -470 | SQL CALL STATEMENT SPECIFIED A NULL VALUE FOR INPUT PARAMETER number, BUT THE STORED PROCEDURE DOES NOT SUPPORT NULL VALUES |
| -471 | INVOCATION OF FUNCTIONAL PROCEDURE name FAILED DUE TO REASON rc |
| -472 | CURSOR cursor-name WAS LEFT OPEN BY EXTERNAL FUNCTION function-name (SPECIFIC NAME specific-name) |
| -473 | A USER DEFINED DATA TYPE CANNOT BE CALLED THE SAME NAME AS A SYSTEM PREDEFINED TYPE (BUILT-IN TYPE) |
| -475 | THE RESULT TYPE type-1 OF THE SOURCE FUNCTION CANNOT BE CAST TO THE RETURNS TYPE type-2 OF THE USER-DEFINED FUNCTION |
| -476 | REFERENCE TO FUNCTION function-name WAS NAMED WITHOUT A SIGNATURE, BUT THE FUNCTION IS NOT UNIQUE WITHIN ITS SCHEMA |
| -478 | ALTER, DROP OR REVOKE AFFECTING OBJECT TYPE object-type CANNOT BE PROCESSED BECAUSE OBJECT dependent-object OF TYPE dependent-type IS DEPENDENT ON IT |
| -480 | THE PROCEDURE procedure-name HAS NOT YET BEEN CALLED |
| -481 | THE GROUP BY CLAUSE CONTAINS element-1 NESTLED WITHIN element-2 |
| -482 | PROCEDURE procedure-name RETURNED NO LOCATORS |
| -483 | IN CREATE FUNCTION FOR function-name STATEMENT, THE NUMBER OF PARAMETERS DOES NOT MATCH THE NUMBER OF PARAMETERS OF THE SOURCE FUNCTION |
| -487 | Object-type object-name ATTEMPTED TO EXECUTE SQL STATEMENT WHEN THE DEFINITION OF THE FUNCTION OF PROCEDURE DID NOT SPECIFY THIS ACTION |
| -490 | NUMBER number DIRECTLY SPECIFIED IN AN SQL STATEMENT IS OUTSIDE THE RANGE OF ALLOWABLE VALUES IN THIS CONTEXT (minval,maxval) |
| -491 | CREATE STATEMENT FOR USER-DEFINED FUNCTION function-name MUST HAVE A RETURNS CLAUSE AND: THE EXTERNAL CLAUSE WITH OTHER REQUIRED KEYWORDS; THE RETURN STATEMENT AND PARAMETER NAMES; OR THE SOURCE CLAUSE |
| -492 | THE CREATE FUNCTION FOR function-name HAS A PROBLEM WITH PARAMETER NUMBER number. IT MAY INVOLVE A MISMATCH WITH A SOURCE FUNCTION |
| -495 | ESTIMATED PROCESSOR COST OF estimate-amount1 PROCESSOR SECONDS (estimate-amount2 SERVICE UNITS) IN COST CATEGORY cost-category EXCEEDS A RESOURCE LIMIT ERROR THRESHOLD OF limit-amount SERVICE UNITS |
| -496 | THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT REFERENCES A RESULT SET THAT WAS NOT CREATED BY THE CURRENT SERVER |
| -497 | THE MAXIMUM LIMIT OF INTERNAL IDENTIFIERS HAS BEEN EXCEEDED FOR DATABASE |
| -499 | CURSOR cursor-name HAS ALREADY BEEN ASSIGNED TO THIS OR ANOTHER RESULT SET FROM PROCEDURE procedure-name |
| -500 | THE IDENTIFIED CURSOR WAS CLOSED WHEN THE CONNECTION WAS DESTROYED |
| -501 | THE CURSOR IDENTIFIED IN A FETCH OR CLOSE STATEMENT IS NOT OPEN |
| -502 | THE CURSOR IDENTIFIED IN AN OPEN STATEMENT IS ALREADY OPEN |
| -503 | A COLUMN CANNOT BE UPDATED BECAUSE IT IS NOT IDENTIFIED IN THE UPDATE CLAUSE OF THE SELECT STATEMENT OF THE CURSOR |
| -504 | THE CURSOR NAME cursor-name IS NOT DECLARED |
| -507 | THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT OPEN |
| -508 | THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT POSITIONED ON A ROW OR ROWSET THAT CAN BE UPDATED OR DELETED |
| -509 | THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT THE SAME TABLE DESIGNATED BY THE CURSOR |
| -510 | THE TABLE DESIGNATED BY THE CURSOR OF THE UPDATE OR DELETE STATEMENT CANNOT BE MODIFIED |
| -511 | THE FOR UPDATE CLAUSE CANNOT BE SPECIFIED BECAUSE THE TABLE DESIGNATED BY THE CURSOR CANNOT BE MODIFIED |
| -512 | STATEMENT REFERENCE TO REMOTE OBJECT IS INVALID |
| -513 | THE ALIAS alias-name MUST NOT BE DEFINED ON ANOTHER LOCAL OR REMOTE ALIAS |
| -514 | THE CURSOR cursor-name IS NOT IN A PREPARED STATE |
| -516 | THE DESCRIBE FOR STATIC STATEMENT NOT IDENTIFY A PREPARED STATEMENT |
| -517 | CURSOR cursor-name CANNOT BE USED BECAUSE ITS STATEMENT NAME DOES NOT IDENTIFY A PREPARED SELECT STATEMENT |
| -518 | THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID PREPARED STATEMENT |
| -519 | THE PREPARE STATEMENT IDENTIFIES THE SELECT STATEMENT OF THE OPENED CURSOR cursor-name |
| -525 | THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT WAS AN ERROR AT BIND TIME FOR SECTION = sectno PACKAGE = pkgname CONSISTENCY TOKEN = X’contoken’ |
| -526 | THE REQUESTED OPERATION OR USAGE DOES NOT APPLY TO table-type TEMPORARY TABLE table-name |
| -530 | THE INSERT OR UPDATE VALUE OF FOREIGN KEY constraint-name IS INVALID |
| -531 | PARENT KEY IN A PARENT ROW CANNOT BE UPDATED BECAUSE IT HAS ONE OR MORE DEPENDENT ROWS IN RELATIONSHIP constraint-name |
| -532 | THE RELATIONSHIP constraint-name RESTRICT THE DELETION OF ROW WITH RID X rid-number |
| -533 | INVALID MULTIPLE-ROW INSERT |
| -534 | THE PRIMARY KEY CANNOT BE UPDATED BECAUSE OF MULTIPLE-ROW UPDATE |
| -536 | THE DELETE STATEMENT IS INVALID BECAUSE TABLE table-name CAN BE AFFECTED BY THE OPERATION |
| -537 | THE PRIMARY KEY CLAUSE, A FOREIGN KEY CLAUSE, OR A UNIQUE CLAUSE IDENTIFIES COLUMN column-name MORE THAN ONCE |
| -538 | FOREIGN KEY name DOES NOT CONFORM TO THE DESCRIPTION OF A PARENT KEY OF TABLE table name |
| -539 | TABLE table-name DOES NOT HAVE A PRIMARY KEY |
| -540 | THE DEFINITION OF TABLE table-name IS INCOMPLETE BECAUSE IT LACKS A PRIMARY INDEX OR A REQUIRED UNIQUE INDEX |
| -542 | Column-name CANNOT BE A COLUMN OF A HASH KEY, PRIMARY KEY, A UNIQUE CONSTRAINT, OR A PARENT KEY BECAUSE IT CAN CONTAIN NULL VALUES |
| -543 | A ROW IN A PARENT TABLE CANNOT BE DELETED BECAUSE THE CHECK CONSTRAINT check-constraint RESTRICTS THE DELETION |
| -544 | THE CHECK CONSTRAINT SPECIFIED IN THE ALTER TABLE STATEMENT CANNOT BE ADDED BECAUSE AN EXISTING ROW VIOLATES THE CHECK CONSTRAINT |
| -545 | THE REQUESTED OPERATION IS NOT ALLOWED BECAUSE A ROW DOES NOT SATISFY THE CHECK CONSTRAINT check-constraint |
| -546 | THE CHECK CONSTRAINT constraint-name IS INVALID |
| -548 | A CHECK CONSTRAINT THAT IS DEFINED WITH column-name IS INVALID |
| -549 | THE statement STATEMENT IS NOT ALLOWED FOR object_type1 object_name BECAUSE THE BIND OPTION DYNAMICRULES(RUN) IS NOT IN EFFECT FOR object_type2 |
| -551 | auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION operation ON OBJECT object-name |
| -552 | auth-id DOES NOT HAVE THE PRIVILEGE HOME OPERATION operation |
| -553 | auth-id SPECIFIED IS NOT ONE OF THE VALID AUTHORIZATION IDS FOR REQUESTED OPERATION |
| -554 | AN AUTHORIZATION ID CANNOT GRANT A PRIVILEGE TO ITSELF |
| -555 | AN AUTHORIZATION ID CANNOT REVOKE A PRIVILEGE FROM ITSELF |
| -556 | authid2 CANNOT HAVE THE privilege PRIVILEGE on_object REVOKED BY authid1 BECAUSE THE REVOKEE DOES NOT POSSESS THE PRIVILEGE OR THE REVOKER DID NOT MAKE THE GRANT |
| -557 | INCONSISTENT GRANT/REVOKE KEYWORD keyword. PERMITTED KEYWORDS ARE keyword-list |
| -558 | INVALID CLAUSE OR COMBINATION OF CLAUSES ON A GRANT OR REVOKE |
| -559 | ALL AUTHORIZATION FUNCTIONS HAVE BEEN DISABLED |
| -562 | THE SPECIFIED PRIVILEGES CANNOT BE GRANTED TO PUBLIC |
| -567 | bind-type AUTHORIZATION ERROR USING auth-id AUTHORITY PACKAGE= package-name PRIVILEGE= privilege |
| -571 | THE STATEMENT WOULD RESULT IN A MULTIPLE SITE UPDATE |
| -573 | TABLE table-name DOES NOT HAVE A UNIQUE KEY WITH THE SPECIFIED COLUMN NAME |
| -574 | THE SPECIFIED DEFAULT VALUE OR IDENTITY ATTRIBUTE VALUE CONFLICTS WITH THE DEFINITION OF COLUMN column-name |
| -575 | OBJECT object-name (OBJECT TYPE object-type) CANNOT BE REFERENCED EXPLICITLY OR IMPLICITLY |
| -577 | object-type object-name ATTEMPTED TO MODIFY DATA WHEN THE DEFINITION OF THE FUNCTION OR PROCEDURE DID NOT SPECIFY THIS ACTION |
| -578 | THE RETURN STATEMENT WAS NOT EXECUTED FOR SQL FUNCTION function-name |
| -579 | Object-type object-name ATTEMPTED TO READ OR MODIFY DATA WHEN THE DEFINITION OF THE FUNCTION OF PROCEDURE DID NOT SPECIFY THIS ACTION |
| -580 | THE RESULT- EXPRESSIONS OF A CASE EXPRESSION CANNOT ALL BE NULL |
| -581 | THE DATA TYPES OF THE RESULT-EXPRESSIONS OF A CASE EXPRESSION ARE NOT COMPATIBLE |
| -582 | THE SEARCH-CONDITION IN A SEARCHED-WHEN-CLAUSE OF A CASE IS NOT VALID IN THE CONTEXT IN WHICH IT WAS SPECIFIED. THE SEARCH CONDITION CONTAINS A QUANTIFIED PREDICATE ON AN IN PREDICATE THAT INCLUDES A FULLSELECT, AND THESE ARE NOT ALLOWED IN THE SPECIFIED CONTEXT |
| -583 | THE USE OF FUNCTION EXPRESSION name IS INVALID BECAUSE IT IS NOT DETERMINISTIC OR HAS AN EXTERNAL ACTION |
| -584 | INVALID USE OF NULL OR DEFAULT |
| -585 | THE COLLECTION collection-id APPEARS MORE THAN ONCE IN THE SET special-register STATEMENT |
| -586 | THE TOTAL LENGTH OF THE CURRENT PATH SPECIAL REGISTER ANNOT EXCEED 2048 CHARACTERS |
| -589 | A POSITIONED DELETE OR UPDATE STATEMENT FOR CURSOR cursor-name SPECIFIED A ROW OR ROWSET, BUT THE CURSOR IS NOT POSITIONED ON A ROWSET |
| -590 | NAME name IS NOT UNIQUE IN THE CREATE OR ALTER FOR ROUTINE OR TRIGGER object-name |
| -592 | NOT AUTHORISED TO CREATE FUNCTIONS OR PROCEDURES IN WLM ENVIRONMENT |
| -593 | NOT NULL MUST BE SPECIFIED FOR column-name BECAUSE IT IS DEFINED AS A ROWID (OR DISTINCT TYPE FOR ROWID), ROW CHANGE TIMESTAMP COLUMN, ROW BEGIN COLUMN, ROW END COLUMN, OR COLUMN OF A PERIOD column-name |
| -594 | ATTEMPT TO CREATE A NULLABLE ROWID OR DISTINCT TYPE COLUMN column-name |
| -601 | THE NAME (VERSION OR VOLUME SERIAL NUMBER) OF THE OBJECT TO BE DEFINED OR THE TARGET OF A RENAME STATEMENT IS IDENTICAL TO THE EXISTING NAME (VERSION OR VOLUME SERIAL NUMBER) name OF THE OBJECT TYPE obj-type |
| -602 | TOO MANY COLUMNS, PERIODS, OR KEY-EXPRESSIONS SPECIFIED IN A CREATE INDEX OR ALTER INDEX STATEMENT |
| -603 | A UNIQUE INDEX CANNOT BE CREATED BECAUSE THE TABLE CONTAINS ROWS WHICH ARE DUPLICATES WITH RESPECT TO THE VALUES OF THE IDENTIFIED COLUMNS AND PERIODS |
| -604 | A DATA TYPE DEFINITION SPECIFIES AN INVALID LENGTH, PRECISION, OR SCALE ATTRIBUTE |
| -607 | OPERATION OR OPTION operation IS NOT DEFINED FOR THIS SUBJECT |
| -611 | ONLY LOCKMAX 0 CAN BE SPECIFIED WHEN THE LOCK SIZE OF THE TABLESPACE IS TABLESPACE OR TABLE |
| -612 | identifier IS A DUPLICATE NAME |
| -613 | THE PRIMARY KEY OR A UNIQUE CONSTRAINT IS TOO LONG AS TOO MANY COLUMNS AND PERIODS |
| -614 | THE INDEX CANNOT BE CREATED OR THE LENGTH OF A COLUMN CANNOT BE CHANGED BECAUSE THE SUM OF THE INTERNAL LENGTHS OF THE IDENTIFIED COLUMNS IS GREATER THAN THE ALLOWABLE MAXIMUM |
| -615 | operation-type IS NOT ALLOWED ON A PACKAGE IN USE |
| -616 | obj-type1 obj-name1 CANNOT BE DROPPED BECAUSE IT IS REFERENCED BY obj-type2 obj-name2 |
| -618 | OPERATION operation IS NOT ALLOWED ON SYSTEM DATABASES |
| -619 | OPERATION DISALLOWED AS THE WORK FILE DATABASE IS NOT STOPPED |
| -620 | KEYWORD keyword IN stmt-type STATEMENT IS NOT PERMITTED FOR A space-type SPACE IN THE database-type DATABASEv |
| -621 | DUPLICATE DBID dbid WAS DETECTED AND PREVIOUSLY ASSIGNED TO database-name |
| -622 | FOR MIXED DATA IS INVALID BECAUSE THE MIXED DATA INSTALL OPTION IS NO |
| -623 | CLUSTER IS NOT VALID FOR table-name |
| -624 | TABLE table-name ALREADY HAS A PRIMARY KEY OR UNIQUE CONSTRAINT WITH SPECIFIED COLUMNS AND PERIODS |
| -625 | TABLE table-name DOES NOT HAVE AN INDEX TO ENFORCE THE UNIQUENESS OF THE PRIMARY OR UNIQUE KEY |
| -626 | THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE THE PAGE SET IS NOT STOPPED |
| -627 | THE ALTER STATEMENT IS INVALID BECAUSE THE TABLE SPACE OR INDEX HAS USER-MANAGED DATA SETS |
| -628 | THE CLAUSES ARE MUTUALLY EXCLUSIVE |
| -629 | SET NULL CANNOT BE SPECIFIED BECAUSE FOREIGN KEY name CANNOT CONTAIN NULL VALUES |
| -631 | FOREIGN KEY name IS TOO LONG OR HAS TOO MANY COLUMNS |
| -632 | THE TABLE CANNOT BE DEFINED AS A DEPENDENT OF table-name BECAUSE OF DELETE RULE RESTRICTIONS |
| -633 | THE DELETE RULE MUST BE delete-rule |
| -634 | THE DELETE RULE MUST NOT BE CASCADE |
| -635 | THE DELETE RULES CANNOT BE DIFFERENT OR CANNOT BE SET NULL |
| -636 | RANGES SPECIFIED FOR PARTITION part-num ARE NOT VALID |
| -637 | DUPLICATE keyword KEYWORD OR CLAUSE |
| -638 | TABLE table-name CANNOT BE CREATED BECAUSE COLUMN DEFINITION IS MISSING |
| -639 | A NULLABLE COLUMN OF A FOREIGN KEY WITH A DELETE RULE OF SET NULL CANNOT BE A COLUMN OF THE KEY OF A PARTITIONED INDEX |
| -642 | TOO MANY COLUMNS IN UNIQUE CONSTRAINTS |
| -643 | A CHECK CONSTRAINT OR THE VALUE OF AN EXPRESSION FOR A COLUMN OF AN INDEX EXCEEDS THE MAXIMUM ALLOWABLE LENGTH KEY EXPRESSION |
| -644 | INVALID VALUE SPECIFIED FOR KEYWORD keyword IN OR CLAUSE keyword-or-clause IN STATEMENT stmt-type |
| -646 | TABLE table-name CANNOT BE CREATED IN SPECIFIED TABLE SPACE table-space-name BECAUSE IT ALREADY CONTAINS A TABLE |
| -647 | BUFFERPOOL bp-name FOR IMPLICIT OR EXPLICIT TABLESPACE OR INDEXSPACE name HAS NOT BEEN ACTIVATED |
| -650 | THE ALTER INDEX CANNOT BE EXECUTED, REASON reason |
| -651 | TABLE DESCRIPTION EXCEEDS MAXIMUM SIZE OF OBJECT DESCRIPTOR |
| -652 | VIOLATION OF INSTALLATION DEFINED EDIT OR VALIDATION PROCEDURE |
| -653 | TABLE table-name IN PARTITIONED TABLESPACE tspace-name IS NOT AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS NOT BEEN CREATED |
| -655 | THE CREATE OR ALTER STOGROUP IS INVALID BECAUSE THE STORAGE GROUP WOULD HAVE BOTH SPECIFIC AND NON-SPECIFIC VOLUME IDS |
| -658 | A object-type CANNOT BE DROPPED USING THE statement STATEMENT |
| -660 | INDEX index-name CANNOT BE CREATED OR ALTERED ON PARTITIONED TABLESPACE tspace-name BECAUSE KEY LIMITS ARE NOT SPECIFIED |
| -661 | Object-type index-name CANNOT BE CREATED ON PARTITIONED TABLE SPACE tspace-name BECAUSE THE NUMBER OF PARTITION SPECIFICATIONS IS NOT EQUAL TO THE NUMBER OF PARTITIONS OF THE TABLE SPACE |
| -662 | A PARTITIONED INDEX CANNOT BE CREATED ON A TABLE SPACE, OR A TABLE SPACE CANNOT BE INDEX-CONTROLLED. TABLE SPACE tspace-name, REASON reason-code |
| -663 | THE NUMBER OF KEY LIMIT VALUES IS EITHER ZERO, OR GREATER THAN THE NUMBER OF COLUMNS IN THE KEY OF INDEX index-name |
| -665 | THE PART CLAUSE OF AN ALTER STATEMENT IS OMITTED OR INVALID |
| -666 | Stmt-verb object CANNOT BE EXECUTED BECAUSE function IS IN PROGRESS |
| -667 | THE CLUSTERING INDEX FOR A PARTITIONED TABLESPACE CANNOT BE EXPLICITLY DROPPED |
| -668 | THE COLUMN CANNOT BE ADDED TO THE TABLE BECAUSE THE TABLE HAS AN EDIT PROCEDURE DEFINED WITH ROW ATTRIBUTE SENSITIVITY |
| -669 | THE OBJECT CAN BE EXPLICITLY DROPPED. REASON reason-code |
| -670 | THE RECORD LENGTH OF THE TABLE EXCEEDS THE PAGE SIZE LIMIT |
| -671 | THE BUFFERPOOL ATTRIBUTE OF THE TABLESPACE CANNOT BE ALTERED AS SPECIFIED BECAUSE IT WOULD CHANGE THE PAGE SIZE OF THE TABLESPACE |
| -672 | OPERATION DROP NOT ALLOWED ON TABLE table-name |
| -676 | THE PHYSICAL CHARACTERISTICS OF THE INDEX ARE INCOMPATIBLE WITH RESPECT TO THE SPECIFIED STATEMENT. THE STATEMENT HAS FAILED. REASON reason-code |
| -677 | INSUFFICIENT VIRTUAL STORAGE FOR BUFFERPOOL XPANSION_REASON |
| -678 | THE CONSTANT constant SPECIFIED FOR THE INDEX LIMIT KEY MUST CONFORM TO THE DATA TYPE data-type OF THE CORRESPONDING COLUMN column-name |
| -679 | THE OBJECT name CANNOT BE CREATED BECAUSE A DROP IS PENDING ON THE OBJECT |
| -680 | TOO MANY COLUMNS SPECIFIED FOR A TABLE, VIEW or TABLE FUNCTION |
| -681 | COLUMN column-name IN VIOLATION OF INSTALLATION DEFINED FIELD PROCEDURE. RT: return-code, RS: |
| -682 | FIELD PROCEDURE procedure-name COULD NOT BE LOADED |
| -683 | THE SPECIFICATION FOR COLUMN, DISTINCT TYPE, FUNCTION, OR PROCEDURE data-item CONTAINS INCOMPATIBLE CLAUSES |
| -684 | THE LENGTH OF LITERAL LIST BEGINNING string IS TOO LONG |
| -685 | INVALID FIELD TYPE, column-name |
| -686 | COLUMN DEFINED WITH A FIELD PROCEDURE CAN NOT COMPARE WITH ANOTHER COLUMN WITH DIFFERENT FIELD PROCEDURE |
| -687 | FIELD TYPES INCOMPARABLE |
| -688 | INCORRECT DATA RETURNED FROM FIELD PROCEDURE, column-name |
| -689 | TOO MANY COLUMNS DEFINED FOR A DEPENDENT TABLE |
| -690 | THE STATEMENT IS REJECTED BY DATA DEFINITION CONTROL SUPPORT |
| -691 | THE REQUIRED REGISTRATION TABLE table-name DOES NOT EXIST |
| -692 | THE REQUIRED UNIQUE INDEX index-name FOR DDL REGISTRATION TABLE table-name DOES NOT EXIST |
| -693 | THE COLUMN column-name IN DDL REGISTRATION TABLE OR INDEX table-name (index-name) IS NOT DEFINED PROPERLY |
| -694 | THE SCHEMA STATMENT CANNOT BE EXECUTED BECAUSE A DROP IS PENDING ON THE DDL REGISTRATION TABLE table-name |
| -695 | INVALID VALUE seclabel SPECIFIED SECURITY LABEL COLUMN OF TABLE table-name |
| -696 | THE DEFINITION OF TRIGGER trigger-name INCLUDES AN INVALID USE OF CORRELATION NAME OR TRANSITION TABLE NAME name. REASON CODE= reason-code |
| -697 | OLD OR NEW CORONATION NAMES ARE NOT ALLOWED IN A TRIGGER DEFINED WITH THE FOR EACH STATEMENT CLAUSE. OLD_TABLE OR NEW_TABLE NAMES ARE NOT ALLOWED IN A TRIGGER WITH THE BEFORE CLAUSE |
| -713 | THE REPLACEMENT VALUE value FOR special-register IS INVALID |
| -715 | PROGRAM program-name WITH MARK release-dependency-mark FAILED BECAUSE IT DEPENDS ON FUNCTIONS OF THE RELEASE FROM WHICH FALLBACK HAS OCCURRED |
| -716 | PROGRAM program-name PRECOMPILED WITH INCORRECT LEVEL FOR THIS RELEASE |
| -717 | Bind-type FOR object-type object-name WITH MARK release-dependency-mark FAILED BECAUSE object-type DEPENDS ON FUNCTIONS OF THE RELEASE FROM WHICH THE FALLBACK OCCURRED |
| -718 | REBIND OF PACKAGE package-name FAILED BECAUSE IBMREQD OF ibmreqd IS INVALID |
| -719 | BIND ADD ERROR USING auth-id AUTHORITY PACKAGE |
| -720 | BIND ERROR, ATTEMPTING TO REPLACE PACKAGE= package_name WITH VERSION= version2 BUT THIS VERSION ALREADY EXISTS |
| -721 | BIND ERROR FOR PACKAGE= pkg-id CONTOKEN= ‘contoken’X IS NOT UNIQUE SO CANNOT BE CREATED |
| -722 | Bind-type ERROR USING auth-id AUTHORITY PACKAGE package-name DOES NOT EXIST |
| -723 | AN ERROR OCCURRED IN A TRIGGERED SQL STATEMENT IN TRIGGER trigger-name, SECTION NUMBER section-number, INFORMATION RETURNED: SQLCODE sqlerror, SQLSTATE sqlstate, AND MESSAGE TOKENS token-list |
| -724 | THE ACTIVATION OF THE object-type OBJECT object-name WOULD EXCEED THE MAXIMUM LEVEL OF INDIRECT SQL CASCADING |
| -725 | THE SPECIAL REGISTER register AT LOCATION location WAS SUPPLIED AN INVALID VALUE |
| -726 | BIND ERROR ATTEMPTING TO REPLACE PACKAGE = <package_name>. THERE ARE ENABLE OR DISABLE ENTRIES CURRENTLY ASSOCIATED WITH THE PACKAGE |
| -727 | AN ERROR OCCURRED DURING IMPLICIT SYSTEM ACTION TYPE ation-type. INFORMATION RETURNED FOR THE ERROR INCLUDES SQLCODE sqlcode SQLSTATE sqlstate AND MESSAGE TOKENS token-list |
| -728 | DATA TYPE data-type IS NOT ALLOWED IN DB2 PRIVATE PROTOCOL PROCESSING |
| -729 | A STORED PROCEDURE SPECIFYING COMMIT ON RETURN CANNOT BE THE TARGET OF A NESTED CALL STATEMENT |
| -730 | THE PARENT OF A TABLE IN A READ-ONLY SHARED DATABASE MUST ALSO BE A TABLE IN A READ-ONLY SHARED DATABASE |
| -731 | USER-DEFINED DATA SET dsname MUST BE DEFINED WITH SHAREOPTIONS(1,3) |
| -732 | THE DATABASE IS DEFINED ON THIS SUB SYSTEM WITH THE ROSHARE READ ATTRIBUTE BUT THE TABLESPACE OR INDEX SPACE HAS NOT BEEN DEFINED ON THE OWNING SUBSYSTEM |
| -733 | THE DESCRIPTION OF TABLESPACE, INDEX SPACE, OR TABLE IN A ROSHARE READ DATABASE MUST BE CONSISTENT WITH ITS DESCRIPTION IN THE OWNER SYSTEM |
| -734 | THE ROSHARE ATTRIBUTE OF A DATABASE CANNOT BE ALTERED FROM ROSHARE READ |
| -735 | DATABASE dbid CANNOT BE ACCESSED BECAUSE IT IS NO LONGER A SHARED DATABASE |
| -736 | INVALID OBID obid SPECIFIED |
| -737 | IMPLICIT TABLESPACE NOT ALLOWED |
| -739 | ALTER FUNCTION function-name FAILED BECAUSE FUNCTIONS CANNOT MODIFY DATA WHEN THEY ARE PROCESSED IN PARALLEL |
| -740 | FUNCTION name IS DEFINED WITH THE OPTION MODIFIES SQL DATA WHICH IS NOT VALID IN THE CONTEXT IN WHICH IT WAS INVOKED |
| -741 | A WORK FILE DATABASE IS ALREADY DEFINED FOR MEMBER member-name |
| -742 | DSNDB07 IS THE IMPLICIT WORK FILE DATABASE |
| -746 | THE SQL STATEMENT IN AN EXTERNAL FUNCTION, TRIGGER, OR IN STORED PROCEDURE name VIOLATES THE NESTING SQL RESTRICTION |
| -747 | TABLE table-name IS NOT AVAILABLE UNTIL THE AUXILIARY TABLES AND INDEXES FOR ITS EXTERNALLY STORED COLUMNS HAVE BEEN CREATED |
| -748 | AN INDEX ALREADY EXISTS ON AUXILIARY TABLE |
| -750 | THE SOURCE TABLE source-name CANNOT BE RENAMED OR ALTERED AS SPECIFIED |
| -751 | Object-type object-name (SPECIFIC NAME specific name) ATTEMPTED TO EXECUTE AN SQL STATEMENT statement THAT IS NOT ALLOWED |
| -752 | THE CONNECT STATEMENT IS INVALID BECAUSE THE PROCESS IS NOT IN THE CONNECTABLE STATE |
| -763 | INVALID TABLESPACE NAME table-space-name |
| -764 | A LOB TABLESPACE AND ITS ASSOCIATED BASE TABLESPACE MUST BE IN THE SAME DATABASE |
| -765 | TABLE IS NOT COMPATIBLE WITH DATABASE |
| -766 | THE OBJECT OF A STATEMENT IS A TABLE FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED |
| -767 | MISSING OR INVALID COLUMN SPECIFICATION FOR INDEX |
| -768 | AN AUXILIARY TABLE ALREADY EXISTS FOR THE SPECIFIED COLUMN OR PARTITION |
| -769 | SPECIFICATION OF CREATE AUX TABLE DOES NOT MATCH THE CHARACTERISTICS OF THE BASE TABLE |
| -770 | TABLE table-name CANNOT HAVE A LOB COLUMN UNLESS IT ALSO HAS A ROWID, OR AN XML COLUMN UNLESS IT ALSO HAS A DOCID COLUMN |
| -771 | INVALID SPECIFICATION OF A ROWID COLUMN |
| -773 | CASE NOT FOUND FOR CASE STATEMENT |
| -775 | STATEMENT SPECIFIED IN SQL ROUTINE IN NOT ALLOWED WITHIN A COMPOUND STATEMENT |
| -776 | USE OF CURSOR cursor-name IS NOT VALID |
| -778 | ENDING LABEL label DOES NOT MATCH THE BEGINNING LABEL |
| -779 | LABEL label SPECIFIED ON A GOTO, ITERATE, OR LEAVE STATEMENT IS NOT VALID |
| -780 | UNDO SPECIFIED FOR A HANDLER |
| -781 | CONDITION condition-name IS NOT DEFINED OR THE DEFINITION IS NOT IN SCOPE |
| -782 | A CONDITION OR SQLSTATE value SPECIFIED IS NOT VALID |
| -783 | SELECT LIST FOR CURSOR cursor-name IN FOR STATEMENT IS NOT VALID. COLUMN column-name IS NOT UNIQUE |
| -784 | CONSTRAINT constraint-name CANNOT BE DROPPED |
| -785 | USE OF SQLCODE OR SQLSTATE IS NOT VALID |
| -787 | RESIGNAL STATEMENT ISSUED OUTSIDE OF A HANDLER |
| -788 | OWNERSHIP TRANSFER WAS IGNORED BECAUSE auth-id IS ALREADY THE OWNER OF THE OBJECT |
| -789 | THE DATA TYPE OR OTHER ATTRIBUTES FOR PARAMETER OR SQL VARIABLE name ARE NOT SUPPORTED IN THE ROUTINE |
| -797 | THE TRIGGER trigger-name IS DEFINED WITH AN UNSUPPORTED TRIGGERED SQL STATEMENT |
| -798 | A VALUE CANNOT BE SPECIFIED FOR COLUMN column-name WHICH IS DEFINED AS GENERATED ALWAYS |
| -802 | EXCEPTION ERROR ‘exception-type’ HAS OCCURRED DURING ‘operation-type’ OPERATION ON ‘data-type’ DATA, POSITION ‘position-number’ |
| -803 | AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE THE INDEX IN INDEX SPACE indexspace-name CONSTRAINS COLUMNS OF THE TABLE SO NO TWO ROWS CAN CONTAIN DUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X’rid’ |
| -804 | AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT PARAMETERS FOR THE SQL STATEMENT, REASON reason |
| -805 | DBRM OR PACKAGE NAME location-name.collection-id.dbrm-name-consistency-token NOT FOUND IN PLAN plan-name. REASON reason |
| -807 | ACCESS DENIED: PACKAGE package-name IS NOT ENABLED FOR ACCESS FROM connection-type connection-name |
| -808 | THE CONNECT STATEMENT IS NOT CONSISTENT WITH THE FIRST CONNECT STATEMENT |
| -811 | THE RESULT OF AN EMBEDDED SELECT STATEMENT IS A TABLE OF MORE THAN ONE ROW, OR THE RESULT OF THE SUBQUERY OF A BASIC PREDICATE IS MORE THAN ONE VALUE |
| -812 | THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE A BLANK COLLECTION-ID WAS FOUND IN THE CURRENT PACKAGESET SPECIAL REGISTER WHILE TRYING TO FORM A QUALIFIED PACKAGING NAME FOR PROGRAM program-name.consistency-token USING PLAN plan-name |
| -817 | THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE STATEMENT WILL RESULT IN A PROHIBITED UPDATE OPERATION |
| -818 | THE PRECOMPILER-GENERATED TIMESTAMP x IN THE LOAD MODULE IS DIFFERENT FROM THE BIND TIMESTAMP y BUILT FROM THE DBRM z |
| -819 | THE VIEW CANNOT BE PROCESSED BECAUSE THE LENGTH OF ITS PARSE TREE IN THE CATALOG IS ZERO |
| -820 | THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE catalog-table CONTAINS A VALUE THAT IS NOT VALID IN THIS RELEASE |
| -822 | THE SQLDA CONTAINS AN INVALID DATA ADDRESS OR INDICATOR VARIABLE ADDRESS |
| -840 | TOO MANY ITEMS RETURNED IN A SELECT OR INSERT LIST |
| -842 | A CONNECTION TO location-name ALREADY EXISTS |
| -843 | THE SET CONNECTION OR RELEASE STATEMENT MUST SPECIFY AN EXISTING CONNECTION |
| -845 | A PREVIOUS VALUE EXPRESSION CANNOT BE USED BEFORE THE NEXT VALUE EXPRESSION GENERATES A VALUE IN THE CURRENT APPLICATION PROCESS FOR SEQUENCE sequence-name |
| -846 | INVALID SPECIFICATION OF AN IDENTITY COLUMN OR SEQUENCE OBJECT object-type object-name. REASON CODE = reason code |
| -867 | INVALID SPECIFICATION OF A ROWID COLUMN |
| -870 | THE NUMBER OF HOST VARIABLES IN THE STATEMENT IS NOT EQUAL TO THE NUMBER OF DESCRIPTORS |
| -872 | A VALID CCSID HAS NOT YET BEEN SPECIFIED FOR THIS SUBSYSTEM |
| -873 | THE STATEMENT REFERENCED DATA ENCODED WITH DIFFERENT ENCODING SCHEMES OR CCSIDS IN AN INVALID CONTEXT |
| -874 | THE ENCODING SCHEME SPECIFIED FOR THE object-type MUST BE THE SAME AS THE CONTAINING TABLESPACE OF OTHER PARAMETERS |
| -875 | operand CANNOT BE USED WITH THE ASCII DATA REFERENCED |
| -876 | object CANNOT BE CREATED OR ALTERED, REASON reason |
| -877 | CCSID ASCII IS NOT ALLOWED FOR THIS DATABASE OR TABLE SPACE |
| -878 | THE explain-object USED FOR EXPLAIN MUST BE ENCODED IN UNICODE.IT CANNOT BE IN ASCII OR EBCDIC |
| -879 | CREATE or ALTER STATEMENT FOR object-name CANNOT DEFINE A COLUMN, TYPE, VARIABLE, FUNCTION OR STORED PROCEDURE PARAMETER AS MIXED OR GRAPHIC WITH ENCODING SCHEME encoding-scheme |
| -880 | SAVEPOINT savepoint-name DOES NOT EXIST OR IS INVALID IN THIS CONTEXT |
| -881 | A SAVEPOINT WITH NAME savepoint-name ALREADY EXISTS, BUT THIS SAVEPOINT NAME CANNOT BE REUSED |
| -882 | SAVEPOINT DOES NOT EXIST |
| -900 | THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE APPLICATION PROCESS IS NOT CONNECTED TO AN APPLICATION SERVER |
| -901 | UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT DOES NOT PRECLUDE THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS |
| -902 | POINTER TO THE ESSENTIAL CONTROL BLOCK (CT/RDA) HAS VALUE 0, REBIND REQUIRED |
| -904 | UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON reason-code, TYPE OR RESOURCE resource-type, AND RESOURCE NAME resource-name |
| -905 | UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED, RESOURCE NAME= resource-name LIMIT= limit-amount1 CPU SECONDS (limit-amount2 SERVICE UNITS) DERIVED FROM limit-source |
| -906 | THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THIS FUNCTION IS DISABLED DUE TO A PRIOR ERROR |
| -907 | AN ATTEMPT WAS MADE TO MODIFY THE TARGET TABLE, table-name, OF THE MERGE STATEMENT BY CONSTRAINT OR TRIGGER trigger-name |
| -908 | bind-type ERROR USING auth-id AUTHORITY. BIND, REBIND OR AUTO-REBIND OPERATION IS NOT ALLOWED |
| -909 | THE OBJECT HAS BEEN DELETED OR ALTERED |
| -910 | THE SQL STATEMENT CANNOT ACCESS AN OBJECT ON WHICH A DROP OR ALTER IS PENDING |
| -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-name |
| -913 | UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON CODE reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name |
| -917 | BIND PACKAGE FAILED |
| -918 | THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE A CONNECTION HAS BEEN LOST |
| -919 | A ROLLBACK OPERATION IS REQUIRED |
| -922 | AUTHORISATION FAILURE: error-type ERROR. REASON reason-code |
| -923 | CONNECTION NOT ESTABLISHED: DB2 condition REASON reason-code, TYPE resource-type, NAME resource-name |
| -924 | DB2 CONNECTION INTERNAL ERROR, function-code, return-code, reason-code |
| -925 | COMMIT NOT VALID IN IMS OR CICS ENVIRONMENT |
| -926 | ROLLBACK NOT VALID IN IMS, CICS OR RRSAF ENVIRONMENT |
| -927 | THE LANGUAGE INTERFACE (LI) WAS CALLED WHEN THE CONNECTING ENVIRONMENT WAS NOT ESTABLISHED. THE PROGRAM SHOULD BE INVOKED UNDER THE DSN COMMAND |
| -929 | FAILURE IN A DATA CAPTURE EXIT: token |
| -939 | ROLLBACK REQUIRED DUE TO UNREQUESTED ROLLBACK OF A REMOTE SERVER |
| -947 | THE SQL STATEMENT FAILED BECAUSE IT WILL CHANGE A TABLE DEFNED WITH DATA CAPTURE CHANGES, BUT THE DATA CANNOT BE PROPAGATED |
| -948 | DISTRIBUTED OPERATION IS INVALID |
| -950 | THE LOCATION NAME SPECIFIED IN THE CONNECT STATEMENT IS INVALID OR NOT LISTED IN THE COMMUNICATIONS DATABASE |
| -951 | OBJECT object-name OBJECT TYPE object-type IS IN USE AND CANNOT BE THE TARGET OF THE SPECIFIED ALTER STATEMENT |
| -952 | PROCESSING WAS INTERRUPTED BY A CANCEL REQUEST FROM A CLIENT PROGRAM |
| -981 | THE SQL STATEMENT FAILED BECAUSE THE RRSAF CONNECTION IS NOT IN A STATE THAT ALLOWS SQL OPERATIONS, REASON reason-code |
| -989 | AFTER TRIGGER trigger-name ATTEMPTED TO MODIFY A ROW IN TABLE table-name THAT WAS MODIFIED BY AN SQL DATA CHANGE STATEMENT WITHIN A FROM CLAUSE |
| -991 | CALL ATTACH WAS UNABLE TO ESTABLISH AN IMPLICIT CONNECT OR OPEN TO DB2. RC1= rc1 RC2= rc2 |
| -992 | PACKAGE package-name CANNOT BE EXECUTED OR DEPLOYED ON LOCATION location-name |
| -1403 | THE USERNAME AND/OR PASSWORD SUPPLIED IS INCORRECT |
| -1706 | CREATE PROCEDURE FOR procedure-name MUST HAVE VALID LANGUAGE AND EXTERNAL CLAUSES |
| -2001 | THE NUMBER OF HOST VARIABLE PARAMETERS FOR A STORED PROCEDURE IS NOT EQUAL TO THE NUMBER OF EXPECTED HOST VARIABLE PARAMETERS. ACTUAL NUMBER |
| -4302 | JAVA STORED PROCEDURE USER DEFINED FUNCTION routine-name (SPECIFIC NAME specificname)HAS EXITED WITH AN EXCEPTION exception-string |
| -4700 | ATTEMPT TO USE NEW FUNCTION BEFORE FUNCTION IS ACTIVATED |
| -4701 | THE NUMBER OF PARTITIONS, OR THE COMBINATION OF THE NUMBER OF TABLE SPACE PARTITIONS AND THE CORRESPONDING LENGTH OF THE PARTITIONING LIMIT KEY EXCEEDS THE SYSTEM LIMIT; OR THE COMBINATION OF THE NUMBER OF TABLE SPACE PARTITIONS EXCEEDS THE MAXPARTITIONS FOR PARTITION BY GROWTH TABLE SPACE |
| -4702 | THE MAXIMUM NUMBER OF ALTERS ALLOWED TO BEEN EXCEEDED FOR object-type |
| -4703 | THE ALTER TABLE STATEMENT CANNOT BE EXECUTED BECAUSE COLUMN column-name IS MIXED DATA, OR THE DATE OF TYPE OR LENGTH SPECIFIED DOES NOT AGREE WITH THE EXISTING DATA TYPE OF LENGTH |
| -4704 | AN UNSUPPORTED DATA TYPE WAS ENCOUNTERED AS AN INCLUDE COLUMN |
| -4705 | option SPECIFIED ON ALTER STATEMENT FOR routine-name routine-type IS NOT VALID |
| -4706 | ALTER STATEMENT FOR AND SQL ROUTINE OR ADVANCED TRIGGER CANNOT BE PROCESSED BECAUSE THE OPTIONS CURRENTLY IN EFFECT (ENVID current-envid) ARE NOT THE SAME AS THE ONES THAT WERE IN EFFECT (ENVID defined-envid) WHEN OBJECT OR VERSION WAS FIRST DEFINED |
| -4707 | STATEMENT statement IS NOT ALLOWED WHEN USING A TRUSTED CONNECTION |
| -4708 | TABLE table-name CANNOT BE DEFINED AS SPECIFIED IN THE statement STATEMENT IN A COMMON CRITERIA ENVIRONMENT |
| -4709 | EXPLAIN MONITORED STMTS FAILED WITH REASON CODE = yyyyy |
| -4710 | EXCHANGE DATA STATEMENT SPECIFIED table1 AND table2 BUT THE TABLES DO NOT HAVE A DEFINED CLONE RELATIONSHIP |
| -4727 | SYSTEM PARAMETER system-parameter VALUE parameter-value IS INCONSISTENT WITH CLAUSE clause SPECIFIED ON statement-name STATEMENT |
| -4728 | ANOTHER VERSION OF ROUTINE routine-name EXISTS AND IS DEFINED WITH AN INCOMPATIBLE OPTION. THE OPTION IS option-name |
| -4730 | INVALID SPECIFICATION OF XML COLUMN table-name.column-name IS NOT DEFINED IN THE XML VERSIONING FORMAT, REASON reason-code |
| -4731 | THE NATIVE SQL ROUTINE STATEMENT FOR PACKAGE location-name.collection-id.programname. consistency-token STATEMENT NUMBER statement-number CANNOT BE PROCESSED |
| -4732 | THE MAXIMUM NUMBER OF ALTERS ALLOWED BEEN EXCEEDED FOR object-type |
| -4733 | THE ALTER TABLE STATEMENT CANNOT BE EXECUTED BECAUSE COLUMN column-name IS MIXED DATA, OR THE DATA TYPE OR LENGTH SPECIFIED DOES NOT AGREE WITH THE EXISTING DATA TYPE OR LENGTH |
| -4734 | THE LOAD MODULE FOR THE PROCEDURE ASSUMES A PARAMETER VARCHAR OPTION THAT IS NOT CONSISTENT WITH THE OPTION SPECIFIED ON THE CREATE PROCEDURE STATEMENT FOR procedure-name |
| -4735 | INVALID TABLE REFERENCE FOR TABLE LOCATOR |
| -4736 | A PERIOD SPECIFICATION OR PERIOD CLAUSE IS NOT SUPPORTED AS SPECIFIED FOR OBJECT object-name. REASON CODE = reason-code |
| -4737 | STATEMENT statement IS NOT ALLOWED WHEN USING A TRUSTED CONNECTION |
| -4738 | TABLE table-name CANNOT BE DEFINED AS SPECIFIED IN THE statement STATEMENT IN A COMMON CRITERIA ENVIRONMENT |
| -4739 | ENVIRONMENT SETTINGS (IDENTIFIED BY envid1) USED BY object-name ARE NOT THE SAME AS THE ONES THAT WERE IN EFFECT (IDENTIFIED BY envid2) WHEN OTHER COLUMNS MASKS AND ROW PERMISSIONS WERE DEFINED FOR TABLE table-name |
| -4743 | ATTEMPT TO USE NEW FUNCTION WHEN THE APPLICATION COMPATIBILITY SETTING IS SET FOR A PREVIOUS LEVEL |
| -4744 | THE STATEMENT EXPLICITLY OR IMPLICITLY REFERENCED TEMPORAL TABLE table-name IN AN UNSUPPORTED CONTEXT. REASON CODE reason-code |
| -4749 | PACKAGE = package-name bind-type ERROR WITH APREUSESOURCE(copy-type), THE copy-type COPY DOES NOT EXIST |
| -4750 | Csect-name PACKAGE package-name SWITCH TO THE copy-indicator COPY FAILED. THIS COPY IS NOT EXECUTABLE WITHOUT AN EXPLICIT REBIND OR AUTOBIND (REASON = reason-code) |
| -4753 | Csect-name PACKAGE package-name SWITCH TO THE copy-indicator COPY FAILED. THIS COPY IS NOT EXECUTABLE WITHOUT AN EXPLICIT REBIND OR AUTOBIND (REASON = reason-code) |
| -5001 | TABLE table-name IS NOT VALID |
| -5012 | HOST VARIABLE host-variable IS NOT EXACT NUMERIC WITH SCALE ZERO |
| -7008 | Object-name NOT VALID FOR OPERATION (reason-code) |
| -16000 | AN XQUERY EXPRESSION CANNOT BE PROCESSED BECAUSE THE context-component COMPONENT OF THE STATIC CONTEXT HAS NOT BEEN ASSIGNED. ERROR QNAME = err:XPST0001 |
| -16001 | AN XQUERY EXPRESSION STARTING WITH TOKEN token CANNOT BE PROCESSED BECAUSE THE FOCUS COMPONENT OF THE DYNAMIC CONTEXT HAS NOT BEING ASSIGNED. ERROR QNAME = err:XPDY0002 |
| -16002 | AN XQUERY EXPRESSION HAS AN UNEXPECTED TOKEN token FOLLOWING text. EXPECTED TOKENS MAY INCLUDE: token-list. ERROR QNAME= ERR:XPST0003 |
| -16003 | AN EXPRESSION OF DATA TYPE value-type CANNOT BE USED WHEN THE DATA TYPE expected-type IS EXPECTED IN THE CONTEXT. ERROR QNAME= err:XPTY0004 |
| -16005 | AN XQUERY EXPRESSION REFERENCES AN ELEMENT NAME, ARRIBUTE NAME, TYPE NAME, FUNCTION NAME, NAMESPACE PREFIX, OR VARIABLE NAME undefined-name THAT IS NOT DEFINED WITHIN THE STATIC CONTEXT. ERROR QNAME= ERR:XPST008 |
| -16007 | THE XQUERY PATH EXPRESSION REFERENCES AN AXIS axis-type THAT IS NOT SUPPORTED. ERROR QNAME= err:XQST0010 |
| -16009 | AN XQUERY FUNCTION NAMED function-name WITH number-of-parms PARAMETERS IS NOT DEFINED IN THE STATIC CONTEXT. ERROR QNAME= err:XPST0017 |
| -16011 | THE RESULT OF AN INTERMEDIATE STEP EXPRESSION IN AN XQUERY PATH EXPRESSION CONTAINS AN ATOMIC VALUE. ERROR QNAME= err:XPTY0019 |
| -16012 | THE CONTEXT ITEM IN AN AXIS STEP MUST BE A NODE. ERROR QNAME= err:XPTY0020 |
| -16015 | AN ELEMENT CONSTRUCTOR CONTAINS AN ATTRIBUTE NODE NAMED attribute-name THAT FOLLOWS AN XQUERY NODE THAT IS NOT AN ATTRIBUTE NODE. ERROR QNAME= ERR:XQTY0024 |
| -16016 | THE ATTRIBUTE NAME attribute-name CANNOT BE USED MORE THAN ONCE IN AN ELEMENT CONSTRUCTOR. ERROR QNAME= err:XQTY0025 |
| -16020 | THE CONTENT NODE IN A PATH EXPRESSION THAT BEGINS WITH AN INITIAL ‘I’ OR ‘II’ DOES NOT HAVE AN XQUERY DOCUMENT NODE ROOT. ERROR QNAME= err:XPDY0050 |
| -16022 | OPERANDS OF TYPES xquery-data-types ARE NOT VALID FOR OPERATOR operator-name. ERROR QNAME= err:XPTY0004 |
| -16023 | THE XQUERY PROLOG CANNOT CONTAIN MULTIPLE DECLARATIONS FOR THE SAME NAMESPACE PREFIX ns-prefix. ERROR QNAME= err:XQST0033 |
| -16024 | THE NAMESPACE PREFIX prefix-name CANNOT BE REDECLARED OR CANNOT BE BOUND TO SPECIFIED URI. ERROR QNAME= err:XQST0070 |
| -16031 | XQUERY LANGUAGE FEATURE USING SYNTAX string IS NOT SUPPORTED |
| -16032 | THE STRING string IS NOT A VALID URI. ERROR QNAME= err:XQST0046 |
| -16036 | THE URI THAT IS SPECIFIED IN A NAMESPACE DECLARATION CANNOT BE A ZERO-LENGTH STRING |
| -16038 | THE ARGUMENTS OF FN:DATETIME HAVE DIFFERENT TIMEZONES. ERROR QNAME-ERR:FORG0008 |
| -16046 | A NUMERIC XQUERY EXPRESSION ATTEMPTED TO DIVIDE BY ZERO. ERROR QNAME= err:FOAR0001 |
| -16047 | AN XQUERY EXPRESSION RESULTED IN ARITHMETIC OVERFLOW OR UNDERFLOW. ERROR QNAME= err:FOAR0002 |
| -16048 | AN XQUERY PROLOG CANNOT CONTAIN MORE THAN ONE decl-type DECLARATION. ERROR QNAME= error-qname |
| -16049 | THE LEXICAL VALUE value IS NOT VALID FOR THE type-name DATA TYPE IN THE FUNCTION OR CAST. ERROR QNAME= err:FOCA0002 |
| -16051 | THE VALUE value OF DATA TYPES source-type IS OUT OF RANGE FOR AN IMPLICIT OR EXPLICIT CAST TO TARGET DATA TYPE target-type. ERROR QNAME= err:error-qname |
| -16052 | NAN CANNOT BE USED AS A FLOAT OR DOUBLE VALUE IN A DATETIME OPERATION. ERROR QNAME=ERR:FOCA0005 |
| -16055 | AN ARITHMETIC OPERATION INVOLVING A DATETIME VALUE RESULTED IN OVERFLOW. ERROR QNAME=ERR:FODT0001 |
| -16056 | AN ARITHMETIC OPERATION INVOLVING A DATETIME VALUE RESULTED IN OVERFLOW. ERROR QNAME=ERR:FODT0002 |
| -16057 | A TIMEZONE VALUE IS NOT VALID. ERROR QNAME=ERR:FODR0003 |
| -16061 | THE VALUE value CANNOT BE CONSTRUCTED AS, OR CAST (USING AN IMPLICIT EXPLICIT CAST) TO THE DATA TYPE data-type. ERROR QNAME= err:FORG0001 |
| -16065 | A EMPTY SEQUENCE CANNOT BE CAST TO THE DATA TYPE data-type, ERROR QNAME= err:FORG0006 |
| -16066 | THE ARGUMENT PASSED THE AGGREGATE FUNCTION function-name IS NOT VALID. ERROR QNAME= err:FORG0006 |
| -16067 | THE FLAGS ARGUMENT VALUE PASSED TO THE FUNCTION function-name IS NOT VALID. ERROR QNAME=err:FORX001 |
| -16068 | THE REGULAR EXPRESSION ARGUMENT VALUE PASSED TO THE FUNCTION function-name IS NOT VALID. ERROR QNAME=err:FORX0002 |
| -16069 | A REGULAR EXPRESSION ARGUMENT value PASSED TO THE FUNCTION function-name MATCHES A ZERO-LENGTH STRING. ERROR QNAME= err:FORX0003 |
| -16075 | THE SEQUENCE TO BE SERIALIZED CONTAINS AN ITEM THAT IS AN ATTRIBUTE NODE. ERROR QNAME= err:SENR0001 |
| -16080 | AN XAN XQUERY expression-type UPDATING EXPRESSION IS USED IN AN INVALID CONTEXT. ERROR QNAME=err:XUST0001 |
| -20211 | THE SPECIFICATION ORDER BY, OFFSET, OR FETCH FIRST IN ROWS ONLY IS VALID |
| -20223 | THE OPERATION FAILED. ENCRYPTION FACILITY NOT AVAILABLE return-code, reason-code |
| -20248 | ATTEMPTED TO EXPLAIN STATEMENT WITH STMTID OR STMTTOKEN ID-token BUT THE REQUIRED EXPLANATION INFORMATION IS NOT ACCESSIBLE. REASON reason-code |
| -20342 | INCOMPATIBLE EXPRESSION-TYPE EXPRESSIONS EXIST IN THE XQUERY-UPDATE-CONSTANT IN THE XMLMODIFY FUNCTION. QNAME=err:error-name |
| -20379 | AN AUTHORIZATION ID OR A ROLE CANNOT USE ITS SECADM AUTHORITY TO TRANSFER THE OWNERSHIP OF AN OBJECT TO ITSELF |
| -20433 | AN UNTYPED EXPRESSION WAS SPECIFIED, BUT AN ASSUMED DATA TYPE CANNOT BE DETERMINED FROM ITS USE |
| -20435 | THE SELECT CLAUSE INCLUDES MULTIPLE INVOCATIONS OF THE ARRAY_AGG FUNCTION. ALL INVOCATIONS THAT EXPLICITLY SPECIFY AN ORDER BY CLAUSE MUST SPECIFY THE SAME ORDER |
| -20439 | AN ARRAY INDEX VALUE, value IS NULL OR OUT OF RANGE, OR AN ARRAY ELEMENT WITH THAT INDEX VALUE DOES NOT EXIST |
| -20467 | THE STATEMENT WAS NOT EXECUTED BECAUSE AN EXPRESSION IS NOT A CONSTANT OR VARIABLE. THE INVALID EXPRESSION IS IN THE STATEMENT NEAR THE SYNTAX ELEMENT syntax-element |
| -20529 | THE ARGUMENT OF THE WRAP FUNCTION OR CREATE_WRAPPED PROCEDURE IS NOT VALID |
| -16081 | THE XQUERY-UPDATE-CONSTANT IN THE XMLMODIFY FUNCTION IS NOT AN UPDATING EXPRESSION ON EMPTY SEQUENCE EXPRESSION. ERROR QNAME=err:XUST0002 |
| -16085 | THE TARGET NODE OF AN XQUERY expression-type EXPRESSION IS NOT VALID. ERROR QNAME=err:error-name |
| -16086 | THE REPLACEMENT SEQUENCE OF A REPLACE EXPRESSION CONTAINS INVALID NODES FOR THE SPECIFIED TARGET NODE. ERROR QNAME=err:error-name |
| -16087 | THE RESULT OF APPLYING THE UPDATING EXPRESSIONS IN XMLMODIFY FUNCTION IS NOT A VALID INSTANCE OF THE XQUERY AND XPATH DATA MODEL. ADDITIONAL INFORMATION: information-1, information-2. ERROR QNAME=err:XUDY0021 |
| -16088 | AN expression-type EXPRESSION HAS A BINDING OF A NAMESPACE PREFIX prefix-string TO NAMESPACE URI uri-string, INTRODUCED TO AN ELEMENT NAMED element-name, THAT CONFLICTS WITH AN EXISTING NAMESPACE BINDING OF THE SAME PREFIX TO A DIFFERENT URL IN THE IN-SCOPE NAMESPACES OF THAT ELEMENT NODE. ERROR QNAME=err:XUDY0023 |
| -16089 | AN expression-type EXPRESSION AND POSSIBLY OTHER UPDATING EXPRESSIONS IN AN XML MODIFY FUNCTION INTRODUCE CONFLICTING NAMESPACE BINDINGS INTO AN ELEMENT NAMED element-name. THE PREFIX prefix-string IS BOUND TO uri-string WHILE ANOTHER BINDING OF THE SAME PREFIX USES A DIFFERENT NAMESPACE URI. ERROR QNAME=ee:XUDY0024 |
| -16246 | INCOMPLETE ANNOTATION MAPPING AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri. REASON CODE= reason-code |
| -16247 | SOURCE XML TYPE source-data-type CANNOT BE MAPPED TO TARGET SQL TYPE target-data-type IN THE ANNOTATION AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri |
| -16248 | UNKNOWN ANNOTATION annotation-name AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri |
| -16249 | THE db2-xdb:expression ANNOTATION expression AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri IS TOO LONG |
| -16250 | THE db2-xdb:defaultSQLSchema WITH VALUE schema-name AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri CONFLICTS WITH ANOTHER db2-xdb:defaultSQLSchema SPECIFIED IN ONE OF THE XML SCHEMA DOCUMENTS WITHIN THE SAME XML SCHEMA |
| -16251 | DUPLICATE ANNOTATION DEFINED FOR object-name AT OR NEAR location IN XML SCHEMA DOCUMENT uri |
| -16252 | THE db2-xdb:rowset NAME rowset-name SPECIFIED AT OR NEAR LINE lineno IN THE XML SCHEMA DOCUMENT uri IS ALREADY ASSOCIATED WITH ANOTHER TABLE |
| -16253 | THE db2-xdb:condition ANNOTATION condition AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri IS TOO LONG |
| -16254 | A db2-xdb:locationPath locationpath AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri IS NOT VALID WITH REASON CODE reason-code |
| -16255 | A db2-xdb:rowset VALUE rowset-name USED AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri CONFLICTS WITH A db2-xdb:table ANNOTATION WITH THE SAME NAME |
| -16257 | XML SCHEMA FEATURE feature SPECIFIED IS NOT SUPPORTED FOR DECOMPOSITION |
| -16258 | THE XML SCHEMA CONTAINS A RECURSIVE ELEMENT WHICH IS AN UNSUPPORTED FEATURE FOR DECOMPOSITION. THE RECURSIVE ELEMENT IS IDENTIFIED AS elementnamespace:elementname OF TYPE typenamespace:typename |
| -16259 | INVALID MANY-TO-MANY MAPPINGS DETECTED IN XML SCHEMA DOCUMENT uri1 NEAR LINE lineno1 AND IN XML SCHEMA DOCUMENT uri2 NEAR LINE lineno2 |
| -16260 | XML SCHEMA ANNOTATIONS INCLUDE NO MAPPINGS TO ANY COLUMN OF ANY TABLE |
| -16262 | THE ANNOTATED XML SCHEMA HAS NO COLUMNS MAPPED FOR ROWSET rowsetname |
| -16265 | THE XML DOCUMENT CANNOT BE DECOMPOSED USING XML SCHEMA xsrobject-name WHICH IS NOT ENABLED OR IS INOPERATIVE FOR DECOMPOSITION |
| -16266 | AN SQL ERROR OCCURRED DURING DECOMPOSITION OF DOCUMENT docid WHILE ATTEMPTING TO INSERT DATA. INFORMATION RETURNED FOR THE ERROR INCLUDES SQLCODE sqlcode, SQLSTATE sqlstate, AND MESSAGE TOKENS token-list |
| -20003 | GBPCACHE NONE CANNOT BE SPECIFIED FOR TABLESPACE OR INDEX IN GRECP |
| -20004 | 8K OR 16K BUFFERPOOL PAGESIZE INVALID FOR A WORKFILE OBJECT |
| -20005 | THE INTERNAL ID LIMIT OF limit HAS BEEN EXCEEDED FOR OBJECT TYPE object-type |
| -20006 | LOBS CANNOT BE SPECIFIED AS PARAMETERS WHEN NO WLM ENVIRONMENT IS SPECIFIED |
| -20008 | UNSUPPORTED OPTION keyword SPECIFIED |
| -20016 | THE VALUE OF THE INLINE LENGTH ASSOCIATED WITH object-name IS TOO BIG OR THE INLINE LENGTH CLAUSE IS NOT ALLOWED IN THE CONTEXT |
| -20019 | THE RESULT TYPE RETURNED FROM THE FUNCTION BODY CANNOT BE ASSIGNED TO THE DATA TYPE DEFINED IN THE RETURNS CLAUSE |
| -20046 | THE SELECTIVITY CLAUSE FOLLOWING predicate-string CAN ONLY SPECIFIED FOR A SPATIAL PREDICATE FUNCTION |
| -20058 | THE FULLSELECT SPECIFIED FOR MATERIALIZED QUERY TABLE table-name IS NOT VALID |
| -20060 | UNSUPPORTED DATA TYPE data-type ENCOUNTERED IN SQL object-type object-name |
| -20070 | AUXILIARY TABLE table-name CANNOT BE CREATED BECAUSE COLUMN column-name IS NOT A LOB COLUMN |
| -20071 | WLM ENVIRONMENT NAME MUST BE SPECIFIED function-name |
| -20072 | bind-type bind-subtype ERROR USING auth-id AUTHORITY OPERATION IS NOT ALLOWED ON A package-type PACKAGE package-name |
| -20073 | THE FUNCTION function-name CANNOT BE ALTERED BECAUSE IT IS REFERENCED IN EXISTING VIEW OR MATERIALIZED QUERY TABLE DEFINITIONS |
| -20074 | THE OBJECT object-name CANNOT BE CREATED BECAUSE THE FIRST THREE CHARACTERS ARE RESERVED FOR SYSTEM OBJECTS |
| -20091 | A VIEW NAME WAS SPECIFIED AFTER LIKE IN ADDITION TO THE INCLUDING IDENTITY COLUMN ATTRIBUTES CLAUSE |
| -20092 | THE TABLE OR VIEW WAS SPECIFIED IN THE LIKE CLAUSE, BUT THE OBJECT CANNOT BE USED IN THIS CONTEXT |
| -20093 | THE TABLE table-name CANNOT BE CONVERTED TO OR FROM A MATERIALIZED QUERY TABLE, OR THE MATERIALIZED QUERY TABLE PROPERTY CANNOT BE ALTERED. REASON CODE = reason-code |
| -20094 | THE COLUMN column-name IS A GENERATED COLUMN AND CANNOT BE USED IN THE BEFORE TRIGGER trigger-name |
| -20100 | AN ERROR OCCURRED WHEN BINDING A TRIGGERED SQL STATEMENT. INFORMATION RETURNED: SECTION NUMBER: section-number SQLCODE sqlerror, SQLSTATE sqlstate, AND MESSAGE TOKENS |
| -20101 | THE FUNCTION function FAILED WITH REASON rc |
| -20102 | CREATE OR ALTER STATEMENT FOR USER-DEFINED FUNCTION function-name SPECIFIED THE option OPTION WHICH IS NOT ALLOWED FOR THE TYPE OF ROUTINE |
| -20104 | AN ATTEMPT TO ALTER A CCSID FROM from-ccside TO to-ccsid FAILED |
| -20106 | THE CCSID FOR THE TABLE SPACE OR DATABASE CANNOT BE CHANGED BECAUSE THE TABLE SPACE OR DATABASE ALREADY CONTAINS A TABLE THAT IS REFERENCED IN EXISTING VIEW, OR MATERIALIZED QUERY TABLE DEFINITIONS OR AN EXTENDED INDEX |
| -20107 | HOST VARIABLE OR PARAMETER NUMBER position-number CANNOT BE USED AS SPECIFIED BECAUSE REASON reason |
| -20108 | A RESULT SET CONTAINS AN UNSUPPORTED DATA TYPE IN POSITION NUMBER position-number FOR CURSOR cursor-name OPENED BY STORED PROCEDURE procedure-name |
| -20110 | CANNOT IMPLICITLY CONNECT TO A REMOTE SITE WITH A SAVEPOINT OUTSTANDING |
| -20111 | CAN ISSUE SAVEPOINT, RELEASE SAVEPOINT, ROLLBACK TO A SAVEPOINT FROM A TRIGGER, FROM A USER DEFINED FUNCTION, OR FROM A GLOBAL TRANSACTION |
| -20117 | A WINDOW SPECIFICATION FOR AN OLAP SPECIFICATION IS NOT VALID. REASON CODE = reason-code |
| -20120 | AN SQL TABLE FUNCTION MUST RETURN A TABLE RESULT |
| -20123 | CALL A STORED PROCEDURE procedure FAILED BECAUSE THE RESULT SET RETURNED FOR CURSOR cursor IS SCROLLABLE, BUT THE CURSOR IS NOT POSITIONED BEFORE THE FIRST ROW |
| -20124 | OPEN CURSOR cursor FAILED BECAUSE THE CURSOR IS SCROLLABLE BUT THE CLIENT DOES NOT SUPPORT THIS |
| -20125 | CALL TO STORED PROCEDURE procedure FAILED BECAUSE THE RESULT SET FOR CURSOR cursor IS SCROLLABLE, BUT THE CLIENT DOES NOT SUPPORT THIS |
| -20127 | VALUE SPECIFIED ON FETCH STATEMENT FOR ABSOLUTE OR RELATIVE IS TOO LARGE FOR DRDA |
| -20129 | SPECIAL REGISTERS IS NOT VALID AS USED |
| -20142 | SEQUENCE sequence-name CANNOT BE USED AS SPECIFIED |
| -20143 | THE ENCRYPTION OR DECRYPTION FUNCTION FAILED, BECAUSE THE ENCRYPTION PASSWORD VALUE IS NOT SET |
| -20144 | THE ENCRYPTION IS INVALID BECAUSE THE LENGTH OF THE PASSWORD WAS LESS THAN 6 BYTES OF GREATER THAN 127 BYTES |
| -20146 | DECRYPTION FAILED. THE DATA IS NOT ENCRYPTED |
| -20147 | THE ENCRYPTION FUNCTION FAILED. MULTIPLE PASS ENCRYPTION IS NOT SUPPORTED |
| -20148 | A RETURN STATEMENT DOES NOT EXIST OR WAS NOT INVOKED DURING THE EXECUTION OF ROUTINE routine-name WITH SPECIFIC NAME specific-name |
| -20163 | HEXADECIMAL CONSTANT GX IS NOT ALLOWED |
| -20165 | AN SQL DATA CHANGE STATEMENT WITHIN A FROM CLAUSE IS NOT ALLOWED IN THE CONTEXT IN WHICH IT WAS SPECIFIED |
| -20166 | AN SQL DATA CHANGE STATEMENT WITHIN A SELECT SPECIFIED A VIEW view-name WHICH IS NOT A SYMMETRIC VIEW OR COULD NOT HAVE BEEN IDENTIFIED AS A SYMMETRIC VIEW |
| -20177 | SET DATA TYPE CLAUSE ON ALTER TABLE SPECIFIED FLOATING POINT, BUT THIS CHANGE IS DISALLOWED |
| -20178 | VIEW view-name ALREADY HAS AN INSTEAD OF operation TRIGGER DEFINED |
| -20179 | THE INSTEAD OF TRIGGER CANNOT BE CREATED BECAUSE THE VIEW view-name IS DEFINED USING THE WITH CHECK OPTION |
| -20180 | COLUMN column-name IN TABLE table-name CANNOT BE ALTERED AS SPECIFIED |
| -20181 | COLUMN CANNOT BE ADDED TO THE INDEX index-name |
| -20182 | PARTITIONING CLAUSE clause ON stmt-type STATEMENT FOR index-name IS NOT VALID |
| -20183 | THE PARTITIONED, ADD PARTITION, ADD PARTITIONING KEY, ALTER PARTITION, ROTATE PARTITION, OR PARTITION BY RANGE CLAUSE SPECIFIED ON CREATE OR ALTER FOR name IS NOT VALID |
| -20185 | CURSOR cursor-name IS NOT DEFINED TO ACCESS ROWSETS, BUT A CLAUSE WAS SPECIFIED THAT IS VALID ONLY WITH ROWSET ACCESS |
| -20186 | A CLAUSE SPECIFIED FOR THE DYNAMIC SQL STATEMENT BEING PROCESSED IS NOT VALID |
| -20200 | THE INSTALL OR REPLACE OF jar-id WITH URL url FAILED DUE TO REASON reason-code (reason-string) |
| -20201 | THE INSTALL, REPLACE, REMOVE, OR ALTER OF jar-name FAILED DUE TO REASON reason-code (reason-string) |
| -20202 | THE REMOVE OF jar-name FAILED AS class IS IN USE |
| -20203 | USER-DEFINED FUNCTION OR PROCEDURE name HAS A JAVA METHOD WITH AN INVALID SIGNATURE. THE ERROR IS AT OR NEAR PARAMETER number. THE SIGNATURE IS signature |
| -20204 | THE USER-DEFINED FUNCTION OR PROCEDURE routine-name WAS UNABLE TO MAP TO A SINGLE JAVA METHOD |
| -20207 | THE INSTALL OR REMOVE OF jar-name SPECIFIED THE USE OF A DEPLOYMENT DESCRIPTOR |
| -20210 | THE SQL STATEMENT CANNOT BE EXECUTED AS IT WAS PRECOMPILED AT A LEVEL THAT IS INCOMPATIBLE WITH THE CURRENT VALUE OF THE ENCODING BIND OPTION OR SPECIAL REGISTER |
| -20211 | THE SPECIFICATION ORDER BY OR FETCH FIRST IN ROWS ONLY IS VALID |
| -20212 | USER-DEFINED ROUTINE name ENCOUNTERED AN EXCEPTION ATTEMPTING TO LOAD JAVA CLASS class-name FROM JAR jar-name. ORIGINAL EXCEPTION: exception-string |
| -20213 | STORED PROCEDURE procedure-name HAS RETAINED A DYNAMIC RESULT SET, PARAMETER number, THAT IS NOT VALID |
| -20223 | THE ENCRYPT_TDES OR DECRYPT FUNCTION FAILED. ENCRYPTION FACILITY NOT AVAILABLE return-code, reason-code |
| -20224 | ENCRYPTION DATA THAT WAS ORIGINALLY A BINARY STRING CANNOT BE DECRYPTED TO A CHARACTER STRING |
| -20227 | REQUIRED CLAUSE IS MISSING FOR ARGUMENT number OF expression |
| -20232 | CHARACTER CONVERSION FROM CCSID from-ccsid TO to-ccsid FAILED WITH ERROR CODE error-code FOR TABLE dbid.obid COLUMN column-number REQUESTED BY csect-name |
| -20235 | THE COLUMN column-name CANNOT BE ADDED, ALTERED OR DROPPED BECAUSE table-name IS A MATERIALIZED QUERY TABLE |
| -20240 | INVALID SPECIFICATION OF A SECURITY TABLE COLUMN column-name REASON CODE reason-code |
| -20248 | ATTEMPTED TO EXPLAIN ALL CACHED STATEMENTS OR A CACHED STATEMENT WITH STMTID OR STMTTOKEN ID-token BUT THE REQUIRED EXPLAIN INFORMATION IS NOT ACCESSIBLE |
| -20249 | THE PACKAGE package-name NEEDS TO BE REBOUND IN ORDER TO BE SUCCESSFULLY EXECUTED (token) |
| -20252 | DIAGNOSTICS AREA FULL. NO MORE ERRORS CAN BE RECORDED FOR THE NOT ATOMIC STATEMENT |
| -20257 | FINAL TABLE IS NOT VALID WHEN THE TARGET VIEW view-name OF THE SQL DATA CHANGE STATEMENT IN A FULLSELECT HAS AN INSTEAD OF TRIGGER DEFINED |
| -20258 | INVALID USE OF INPUT SEQUENCE ORDERING |
| -20260 | THE ASSIGNMENT CLAUSE OF THE UPDATE OPERATION AND THE VALUES CLAUSE OF THE INSERT OPERATION MUST SPECIFY AT LEAST ONE COLUMN THAT IS NOT AN INCLUDE COLUMN |
| -20264 | FOR TABLE table-name, primary-auth-id WITH SECURITY LABEL primary-auth-id-seclabel IS NOT AUTHORIZED TO PERFORM operation ON A ROW WITH SECURITY LABEL row-seclabel. THE RECORD IDENTIFIER (RID) OF THIS ROW IS rid-number |
| -20265 | SECURITY LABEL IS reason FOR primary-auth-id |
| -20266 | ALTER VIEW FOR view-name FAILED |
| -20267 | THE FUNCTION function-name (SPECIFIC specific-name) MODIFIES SQL DATA AND IS INVOKED IN AN ILLEGAL CONTEXT. REASON CODE reason-code |
| -20275 | THE XML name IS NOT VALID. REASON CODE reason-code |
| -20281 | Primary-auth-id DOES NOT HAVE THE MLS WRITE DOWN PRIVILEGE |
| -20283 | A DYNAMIC CREATE STATEMENT CANNOT BE PROCESSED WHEN THE VALUE OF CURRENT SCHEMA DIFFERS FROM CURRENT SQLID |
| -20286 | DB2 CONVERTED STRING token-type token FROM from-ccsid TO to-ccsid, AND RESULTED IN SUBSTITUTION CHARACTER |
| -20289 | INVALID STRING UNIT unit SPECIFIED FOR FUNCTION function-name |
| -20295 | THE EXECUTION OF A BUILT-IN FUNCTION function RESULTED IN AN ERROR REASON CODE reason-code |
| -20300 | THE LIST OF COLUMNS SPECIFIED FOR THE clause CLAUSE NOT ALLOWED IN COMBINATION WITH THE LIST OF COLUMNS FOR THE PARTITIONING KEY FOR THE TABLE |
| -20304 | INVALID INDEX DEFINITION INVOLVING AN XMLPATTERN CLAUSE OR A COLUMN OF DATA TYPE XML. REASON CODE = reason code |
| -20305 | AN XML VALUE CANNOT BE INSERTED OR UPDATED BECAUSE OF AN DETECTED WHEN INSERTING INDEX OR UPDATING THE INDEX IDENTIFIED BY index-id ON TABLE table-name. REASON CODE = reason code |
| -20306 | AN INDEX ON AN XML COLUMN CANNOT BE CREATED BECAUSE OF AN ERROR DETECTED WHEN INSERTING THE XML VALUES INTO THE INDEX. REASON CODE = reason-code |
| -20310 | THE REMOVE OF jar-name1 FAILED, AS IT IS IN USE BY jar-name2 |
| -20311 | THE VALUE PROVIDED FOR THE NEW JAVA PATH IS ILLEGAL |
| -20312 | THE ALTAR OF JAR jar-id FAILED BECAUSE THE SPECIFIED PATH REFERENCES ITSELF |
| -20313 | DEBUG MODE OPTION FOR ROUTINE routine-name CANNOT BE CHANGED |
| -20314 | THE PARAMETER LIST DOES NOT MATCH THE PARAMETER LIST FOR ALL OTHER VERSIONS OF ROUTINE routine-name |
| -20315 | THE CURRENTLY ACTIVE VERSION FOR ROUTINE routine-name (routine-type) CANNOT BE DROPPED |
| -20316 | THE CURRENTLY ACTIVE VERSION FOR ROUTINE routine-name (type) CANNOT BE DROPPED |
| -20327 | THE DEPTH OF AN XML DOCUMENT EXCEEDS LIMIT OF 128 LEVELS |
| -20328 | THE DOCUMENT WITH TARGET NAMESPACE namespace AND SCHEMA LOCATION location HAS ALREADY BEEN ADDED FOR THE XML SCHEMA IDENTIFIED BY schema name |
| -20329 | THE COMPLETION CHECK FOR THE XML SCHEMA FAILED BECAUSE ONE OR MORE XML SCHEMA DOCUMENTS IS MISSING. ONE MISSING XML SCHEMA DOCUMENT IS IDENTIFIED BY uri-type AS uri |
| -20330 | THE xsrobject-type IDENTIFIED BY XML uri-type1 uri1 AND XML uri-type2 uri2 IS NOT FOUND IN THE XML SCHEMA REPOSITORY |
| -20331 | THE XML COMMENT VALUE string IS NOT VALID |
| -20332 | THE XML PROCESSING INSTRUCTION VALUE string IS NOT VALID |
| -20337 | MORE THAN ONE xsrobject-type EXISTS IDENTIFIED BY XML uri-type1 uri1 AND uri-type2 uri2 EXISTS IN THE XML SCHEMA REPOSITORY |
| -20338 | THE DATA TYPE OF EITHER THE SOURCE OR TARGET OPERAND OF AN XMLCAST SPECIFICATION MUST BE XML |
| -20339 | XML SCHEMA name IS NOT IN THE CORRECT STATE TO PERFORM OPERATION operation |
| -20340 | XML SCHEMA xmlschema-name INCLUDES AT LEAST ONE XML SCHEMA DOCUMENT IN NAMESPACE namespace THAT IS NOT CONNECTED TO THE OTHER XML SCHEMA DOCUMENTS |
| -20345 | THE XML VALUE IS NOT A WELL-FORMED DOCUMENT WITH A SINGLE ROOT ELEMENT |
| -20353 | AN OPERATION INVOLVING COMPARISON CANNOT USE OPERAND name DEFINED AS STAT TYPE type-name |
| -20354 | INVALID SPECIFICATION OF A ROW CHANGE TIMESTAMP COLUMN FOR TABLE table-name |
| -20355 | THE STATEMENT COULD NOT BE PROCESSED BECAUSE ONE OF MORE IMPLICITLY CREATED OBJECTS ARE INVOLVED reason-code |
| -20356 | THE TABLE WITH DBID = dbid AND OBID = obid CANNOT BE TRUNCATED BECAUSE DELETE TRIGGERS EXIST FOR THE TABLE, OR THE TABLE IS THE PARENT TABLE IN A REFERENTIAL CONSTRAINT |
| -20361 | AUTHORIZATION ID authorization-name IS NOT DEFINED THE TRUSTED CONTEXT context-name |
| -20362 | ATTRIBUTE attribute-name WITH VALUE value CANNOT BE DROPPED BECAUSE IT IS NOT PART OF THE DEFINITION OF TRUSTED CONTEXT context-name |
| -20363 | ATTRIBUTE attribute-name WITH VALUE value IS NOT A UNIQUE SPECIFICATION FOR TRUSTED CONTEXT context-name |
| -20365 | A SIGNALING NAN WAS ENCOUNTERED, OR AN EXCEPTION OCCURRED IN AN ARITHMETIC OPERATION OR FUNCTION INVOLVING A DECFLOAT |
| -20366 | TABLE WITH DBID=dbid.obid AND OBID= obid CANNOT BE TRUNCATED BECAUSE UNCOMMITTED UPDATES EXIST ON THE TABLE WITH ‘IMMEDIATE’ OPTION SPECIFIED IN THE STATEMENT |
| -20369 | AN ALTER TRUSTED CONTEXT STATEMENT FOR context-name ATTEMPTED TO REMOVE THE LAST CONNECTION TRUST ATTRIBUTE ASSOCIATE WITH THE TRUSTED CONTEXT |
| -20372 | THE SYSTEM AUTHID CLAUSE OF A CREATE OR ALTER TRUSTED CONTEXT STATEMENT FOR context-name SPECIFIED authorization-name, BUT ANOTHER TRUSTED CONTEXT IS ALREADY DEFINED FOR THAT AUTHORIZATION ID |
| -20373 | A CREATE OR ALTER TRUSTED CONTEXT STATEMENT SPECIFIED authorization-name MORE THAN ONCE OR THE TRUSTED CONTEXT IS ALREADY DEFINED TO BE USED BY THIS AUTHORISATION ID OR PUBLIC |
| -20374 | AN ALTER TRUSTED CONTEXT STATEMENT FOR context-name SPECIFIED authorization-name BUT THE TRUSTED CONTEXT IS NOT CURRENTLY DEFINED TO BE USED BY THIS AUTHORISATION ID OR PUBLIC |
| -20377 | AN ILLEGAL XML CHARACTER hex-char WAS FOUND IN AN SQL/XML EXPRESSION OR FUNCTION ARGUMENT THAT BEGINS WITH STRING start-string |
| -20380 | ALTER INDEX WITH REGENERATE OPTION FOR index-name FAILED. INFORMATION RETURNED: SQLCODE sqlcode, SQLSTATE sqlstate, MESSAGE TOKENS token-list |
| -20381 | ALTER INDEX WITH REGENERATE OPTION IS NOT VALID FOR index-name |
| -20382 | CONTACTS ITEM CANNOT BE A SEQUENCE WITH MORE THAN ONE ITEM |
| -29385 | THE STATEMENT CANNOT BE PROCESSED BECAUSE THERE ARE PENDING DEFINITION CHANGES FOR OBJECT object-name OF TYPE object-type (REASON reason-code) |
| -20398 | ERROR ENCOUNTERED DURING XML PARSING AT LOCATION n text |
| -20399 | ERROR ENCOUNTERED DURING XML VALIDATION: LOCATION n; TEXT: text XSRID schema-ID |
| -20400 | XML SCHEMA ERROR n text |
| -20409 | AN XML DOCUMENT OR CONSTRUCTED XML VALUE CONTAINS A COMBINATION OF XML NODES THAT CAUSES AN INTERNAL IDENTIFIER LIMIT TO BE EXCEEDED |
| -20410 | THE NUMBER OF CHILDREN NODES OF AN XML NODE IN AN XML VALUE HAS EXCEEDED THE LIMIT NUMBER OF CHILDREN NODES |
| -20411 | A FETCH CURRENT CONTINUE OPERATION WAS REQUESTED FOR cursor-name BUT THERE IS NO PRESERVED, TRUNCATED DATA TO RETURN |
| -20412 | SPECIALIZATION OF AN XML VALUE RESULTED IN CHARACTERS THAT COULD NOT BE REPRESENTED IN THE TARGET ENCODING |
| -20422 | A CREATE TABLE, OR DECLARE GLOBAL TEMPORARY TABLE STATEMENT FOR table-name ATTEMPTED TO CREATE A TABLE WITH ALL THE COLUMNS DEFINED AS HIDDEN |
| -20423 | ERROR OCCURRED DURING TEXT SEARCH PROCESSING (server, index-name, text) |
| -20424 | TEXT SEARCH SUPPORT IS AVAILABLE reason-code |
| -20425 | Column-name (IN table-name) WAS SPECIFIED AS AN ARGUMENT TO A TEXT SEARCH FUNCTION, BUT A TEXT INDEX DOES NOT EXIST FOR THE COLUMN |
| -20426 | CONFLICTING TEXT SEARCH ADMINISTRATION STORED PROCEDURE RUNNING ON THE SAME INDEX |
| -20427 | ERROR OCCURRED DURING TEXT SEARCH ADMINISTRATION STORED PROCEDURE error |
| -20428 | URI SPECIFIED IN THE XMLSCHEMA CLAUSE IS AN EMPTY STRING |
| -20430 | GLOBAL VARIABLE variable-name CANNOT BE SET IN THIS CONTEXT |
| -20433 | AN UNTYPED PARAMETER MARKER WAS SPECIFIED, BUT AN ASSUMED DATA TYPE CANNOT BE DETERMINED FROM ITS USE |
| -20434 | AN UPDATE OPERATION HAS SET ALL OF ITS TARGET COLUMNS TO UNASSIGNED |
| -20435 | THE SELECT CLAUSE WITH MULTIPLE INVOCATIONS OF THE ARRAY_AGG FUNCTION AND ALL INVOCATIONS DO NOT SPECIFY THE SAME SORT KEYS |
| -20436 | THE DATA TYPE SPECIFIED FOR AN ARRAY TYPE IS NOT VALID |
| -20437 | AN ARRAY INDEX CANNOT BE APPLIED TO AN OBJECT THAT IS NOT AN ARRAY |
| -20438 | THE DATA TYPE OF THE EXPRESSION FOR AN ARRAY INDEX VALUE IS NOT CASTABLE TO THE DATA TYPE OF THE ARRAY INDEX |
| -20439 | AN ARRAY INDEX WITH VALUE value IS NULL, OUT OF RANGE OR DOES NOT EXIST |
| -20440 | AN ARRAY VALUE WITH CARDINALITY cardinality HAS TOO MANY ELEMENTS FOR THE REQUESTED OPERATION. THE MAXIMUM NUMBER OF ELEMENTS ALLOWED FOR THE REQUESTED OPERATION IS value |
| -20441 | Type-name TYPE IS NOT VALID WHERE SPECIFIED. REASON CODE reason-code |
| -20442 | THERE IS NOT ENOUGH STORAGE TO REPRESENT THE ARRAY VALUE |
| -20444 | AN ERROR OCCURRED IN A KEY-EXPRESSION EVALUATION IN index-name INFORMATION RETURNED: SQLCODE: sqlcode, SQLSTATE: sqlstate, MESSAGE TOKEN token-list AND RID X rid |
| -20447 | FORMAT STRING format-string IS NOT VALID FOR THE function-name FUNCTION |
| -20448 | String-expression CANNOT BE INTERPRETED USING FORMAT STRING format-string FOR THE TIMESTAMP_FORMAT FUNCTION |
| -20457 | THE PROCEDURE procedure-name HAS ENCOUNTERED AN UNSUPPORTED VERSION, version FOR PARAMETER number |
| -20465 | THE BINARY XML VALUE IS INCOMPLETE OR CONTAINS UNRECOGNISED DATA AT LOCATION position WITH THE HEX DATA text |
| -20467 | THE STATEMENT WAS NOT EXECUTED BECAUSE AN EXPRESSION IS NOT A CONSTANT OR VARIABLE. THE INVALID EXPRESSION IS IN THE STATEMENT NEAR THE SYNTAX ELEMENT syntax-element |
| -20469 | ROW OR COLUMN ACCESS CONTROL CANNOT BE ACTIVATED FOR TABLE table-name FOR A REASON reason-code. Object-type object-name IS NOT IN A VALID STATE FOR ACTIVATING ACCESS CONTROL FOR THIS TABLE |
| -20470 | Object-type1 object-name1 MUST BE DEFINED AS SECURE BECAUSE object-type2 object-name2 IS DEPENDENT ON IT |
| -20471 | THE INSERT OR UPDATE IS NOT ALLOWED BECAUSE THE RESULTING ROW DOES NOT SATISFY ROW PERMISSIONS |
| -20472 | PERMISSION OR MASK object-name CANNOT BE ALTERED AS SPECIFIED. REASON CODE reason-code |
| -20473 | THE INPUT ARGUMENT OF FUNCTION function-name THAT IS DEFINED WITH THE NOT-SECURED OPTION MUST NOT REFERENCE COLUMN column-name FOR WHICH A COLUMN MASK IS ENABLED AND THE COLUMN ACCESS CONTROL IS ACTIVATED FOR THE TABLE |
| -20474 | PERMISSION OR MASK CANNOT BE CREATED FOR THE object-name OBJECT OF THE object-type TYPE. REASON CODE reason-code |
| -20475 | A COLUMN MASK IS ALREADY DEFINED FOR THE COLUMN column-name IN TABLE table-name (EXISTING MASK NAME mask-name) |
| -20476 | THE function-name FUNCTION IS NOT ABLE TO USE FORMAT STRING format-string TO INTERPRET THE ARGUMENT string-expression |
| -20478 | THE STATEMENT CANNOT BE PROCESSED BECAUSE COLUMN MASK mask-name (DEFINED FOR COLUMN column-name) EXISTS AND THE COLUM MASK CANNOT BE APPLIED OR THE DEFINITION OF THE MASK CONFLICTS WITH THE REQUESTED STATEMENT. REASON CODE reason-code |
| -20479 | THE SOURCE TABLE table-name CANNOT BE ALTERED AS SPECIFIED BECAUSE THE TABLE IS INVOLVED IN ROW OR COLUMN ACCESS CONTROLS. REASON CODE reason-code |
| -20487 | HASH ORGANISATION CLAUSE IS NOT VALID FOR table-name |
| -20488 | SPECIFIED HASH SPACE IS TOO LARGE FOR THE IMPLICITLY CREATED TABLE SPACE. REASON reason-code. (PARTITION partition-number) |
| -20490 | A VERSIONING CLAUSE WAS SPECIFIED FOR TABLE table-name, BUT THE TABLE CANNOT BE USED AS A SYSTEM PERIOD TEMPORAL TABLE. REASON CODE= reason-code |
| -20491 | INVALID SPECIFICATION OF PERIOD period-name. REASON CODE= reason-code |
| -20493 | A TIMESTAMP WITHOUT TIME ZONE VALUE CANNOT BE ASSIGNED TO A TIMESTAMP WITH TIME ZONE TARGET |
| -20494 | A PUBLIC ALIAS NAME name, CAN ONLY BE QUALIFIED WITH SYSPUBLIC AND NOT SCHEMA NAME sechema-name |
| -20497 | A STRING REPRESENTATION OF A DATETIME VALUE THAT CONTAINS A TIME ZONE CANNOT BE IMPLICITLY CAST TO A TARGET DEFINED AS DATETIME WITHOUT TIME ZONE |
| -20505 | THE WITH ORDINALITY CLAUSE IS NOT VALID WITH UNNET OF AN ASSOCIATIVE ARRAY |
| -20517 | XMLMODIFY ATTEMPTED TO UPDATE A COLUMN WHICH WAS NOT SPECIFIED IN THE UPDATE SET CLAUSE |
| -20522 | INVALID SPECIFICATION OF WITHOUT OVERLAPS CLAUSE. REASON CODE reason-code |
| -20523 | TABLE table-name WAS SPECIFIED AS A HISTORY TABLE, BUT THE TABLE DEFINITION IS NOT VALID FOR A HISTORY TABLE. REASON CODE= reason-code |
| -20524 | INVALID PERIOD SPECIFICATION OR PERIOD CLAUSE FOR PERIOD period-name. REASON CODE= reason-code |
| -20525 | THE REQUESTED ACTION IS NOT VALID FOR TABLE table-name BECAUSE THE TABLE IS THE WRONG TYPE OF TABLE. REASON CODE= reason-code |
| -20527 | Period-name IS NOT A PERIOD IN TABLE table-name |
| -20528 | THE TARGET OF THE DATA CHANGE OPERATION IS A TABLE table-name, WHICH INCLUDES A PERIOD period-name. A ROW THAT THIS DATA CHANGE OPERATION ATTEMPTED TO MODIFY WAS ALSO MODIFIED BY ANOTHER TRANSACTION |
| -20529 | THE ARGUMENT OF THE WRAP FUNCTION OR CREATE_WRAPPED PROCEDURE IS NOT VALID |
| -20530 | AN OBFUSCATED STATEMENT IS NOT VALID. REASON CODE= reason-code |
| -20531 | THE VERION NUMBER actualversion SPECIFIED IN A BINARY XML VALUE IS NOT SUPPORTED. THE HIGHEST SUPPORTERED VERSION IS supported-version |
| -20535 | THE DATE OF CHANGE OPERATION operation IS NOT SUPPORTED FOR THE TARGET OBJECT object-name BECAUSE OF AN IMPLICIT OR EXPLICIT SYSTEM PERIOD SPECIFICATION INVOLVING period-name. REASON CODE: reason-code |
| -20547 | THE QUERY FAILED BECAUSE A NEGATIVE VALUE OR THE NULL VALUE WAS USED IN THE clause CLAUSE |
| -20550 | AN ARGUMENT, OR COMBINATION OF ARGUMENTS, SPECIFIED FOR THE operator-name OPERATOR ARE NOT VALID |
| -20551 | CONSTRUCTING AN ASSOCIATIVE ARRAY FAILED BECAUSE THE INPUT DATA INCLUDES AT LEAST ONE DUPLICATE ARRAY INDEX VALUE. DUPLICATED INDEX VALUE: value |
| -20553 | AN ENABLE ARCHIVE CLAUSE WAS SPECIFIED FOR TABLE table-name, BUT THE TABLE CANNOT BE USED AS AN ARCHIVE ENABLED TABLE. REASON CODE= reason-code |
| -20554 | TABLE table-name WAS SPECIFIED AS AN ARCHIVE TABLE, BUT THE TABLE DEFINITIONS IS NOT VALID FOR AN ARCHIVE TABLE. REASON CODE= reason-code |
| -20555 | AN ARCHIVE-ENABLED TABLE IS NOT ALLOWED IN THE SPECIFIED CONTEXT. REASON CODE= reason-code |
| -20565 | THE REPLACEMENT VALUE FOR built-in-global-var IS INVALID |
| -30000 | EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR THAT WILL NOT AFFECT THE SUCCESSFUL EXECUTION OF SUBSEQUENT COMMANDS OR SQL STATEMENTS: REASON reason-code (sub-code) |
| -30002 | THE SQL STATEMENT CANNOT BE EXECUTED DUE TO A PRIOR CONDITION IN A CHAIN OF STATEMENTS |
| -30005 | EXECUTION FAILED BECAUSE FUNCTION NOT SUPPORTED BY THE SERVER: LOCATION location-name PRODUCT ID product-identifier REASON reason-code (sub-code) |
| -30020 | EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION: REASON <reason-code (sub-code)> |
| -30021 | EXECUTION FAILED DUT TO A DISTRIBUTION PROTOCOL ERROR THAT WILL AFFECT THE SUCCESSFUL EXECUTION OF SUBSEQUENT COMMANDS OR SQL STATEMENTS: MANAGER manager AT LEVEL level NOT SUPPORTED ERROR |
| -30025 | EXECUTION FAILED BECAUSE FUNCTION IS NOT SUPPORTED BY THE SERVER WHICH CAUSED TERMINATION OF THE CONNECTION: LOCATION location PRODUCT ID pppvvrr REASON reason-code (sub-code) |
| -30030 | COMMIT REQUEST WAS UNSUCCESSFUL, A DISTRIBUTION PROTOCOL VIOLATION HAS BEEN DETECTED, THE CONVERSATION HAS BEEN DEALLOCATED. ORIGINAL SQLCODE=original-sqlcode AND ORIGINAL SQLSTATE= original-sqlstate |
| -30040 | EXECUTION FAILED DUE TO UNAVAILABLE RESOURCES THAT WILL NOT AFFECT THE SUCCESSFUL EXECUTION OF SUBSEQUENT COMMANDS OR SQL STATEMENTS. REASON <reason-code> TYPE OF RESOURCE <resource-type> RESOURCE NAME <resource-name> PRODUCT ID <pppvvrrm> RDBNAME <rdbname> |
| -30041 | EXECUTION FAILED DUE TO UNAVAILABLE RESOURCES THAT WILL AFFECT THE SUCCESSFUL EXECUTION OF SUBSEQUENT COMMANDS AND SQL STATEMENTS. REASON <reason-code> TYPE OF RESOURCE <resource-type> RESOURCE NAME <resource-name> PRODUCT ID <pppvvrrm> RDBNAME <rdbname> |
| -30045 | EXECUTION FAILED BECAUSE THE DEFINITION OF OBJECT object-name OF TYPE object-type BEING ACCESSED AT server-name-1 DIFFERS FROM THE DEFINITION OF THE OBJECT AT server-name2 |
| -30047 | STATEMENT FAILED BECAUSE OBJECT OF TYPE object-type CANNOT BE ACCESSED USING DIFFERENT DISTRIBUTED PROTOCOLS oN A CONNECTION FROM server-name-1 TO server-name-2 |
| -30050 | <command-or-SQL-statement-type> COMMAND OR SQL STATEMENT INVALID WHILE BIND PROCESS IN PROGRESS |
| -30051 | BIND PROCESS WITH SPECIFIED PACKAGE NAME AND CONSISTENCY TOKEN NOT ACTIVE |
| -30052 | PROGRAM PREPARATION ASSUMPTIONS ARE INCORRECT |
| -30053 | OWNER AUTHORISATION FAILURE |
| -30060 | RDB AUTHORISATION FAILURE |
| -30061 | RDB NOT FOUND |
| -30062 | RDB ACCESS FAILURE |
| -30070 | <command> COMMAND NOT SUPPORTED ERROR |
| -30071 | <object-type> OBJECT NOT SUPPORTED ERROR |
| -30072 | <parameter>:<subcode> PARAMETER NOT SUPPORTED ERROR |
| -30073 | <parameter>:<subcode> PARAMETER VALUE NOT SUPPORTED ERROR |
| -30074 | REPLY MESSAGE WITH codepoint (svrcod) NOT SUPPORTED ERROR |
| -30080 | COMMUNICATION ERROR CODE (subcode) |
| -30081 | prot COMMUNICATION ERROR DETECTED. API= api, LOCATION= loc, FUNCTION= func, ERROR CODES= rc1, rc2, rc3 |
| -30082 | CONNECTION FAILED FOR SECURITY REASON reason-code (reason-string) |
| -30090 | REMOTE OPERATION INVALID FOR APPLICATION EXECUTION ENVIRONMENT |
| -30104 | ERROR IN BIND OPTION option AND BIND VALUE value |
| -30105 | BIND OPTION option1 IS NOT ALLOWED WITH BIND OPTION |
| -30106 | INVALID INPUT DATA DETECTED FOR A MULTIPLE ROW INSERT OPERATION. INSERT PROCESSING IS TERMINATED |
Resource Types
| Type code | Type of Resource | Name, Content, Format |
| 00000100 | Database | DB |
| 00000200 | Table space | DB.SP |
| 00000201 | Index space | DB.SP |
| 00000202 | Table space | RD.DB.TS |
| 00000205 | Compression Dictionary | DB.SP |
| 00000210 | Partition | DB.SP.PT |
| 00000220 | Data set | DSN |
| 00000230 | Temporary file | SZ |
| 00000240 | Database procedure | DBP |
| 00000300 | Page | DB.SP.PG |
| 00000301 | Index minipage | DB.SP.PG.MP |
| 00000302 | Table space page | DB.SP.PG |
| 00000303 | Index space page | DB.SP.PG |
| 00000304 | Table space RID | DB.SP.RID |
| 00000305 | Index access/table space RID | DB.SP.RID |
| 00000306 | Index access/table space page | DB.SP.PG |
| 00000307 | Index space EOF | DB.SP.01 |
| 00000308 | Table space page | DB.SP.PT.PG |
| 00000309 | Index space page | DB.SP.PT.PG |
| 0000030A | Table space RID | DB.SP.PT.RID |
| 00000400 | ICF catalog | IC |
| 00000401 | Authorization function | |
| 00000402 | Security Server | SAF/RACF return/reason codes |
| 00000500 | Storage group | SG |
| 00000600 | EDM pool space | |
| 00000602 | EDM DBD space | |
| 00000603 | EDM DYNAMIC STATEMENT space | |
| 00000604 | EDM skeleton storage | |
| 00000605 | EDM above-the-bar | |
| 00000606 | EDM below-the-bar | |
| 00000700 | Buffer pool space | BP |
| 00000701 | Group buffer pool | GBP |
| 00000800 | Plan | PL |
| 00000801 | Package | COLLECTION.PACKAGE.CONTOKEN |
| 00000802 | BINDLOCK01 through BINDLOCK20 | BINDOCK01 through BINDLOCK20 |
| 00000900 | 32KB data area | |
| 00000901 | Sort storage | |
| 00000903 | Hash anchor | DB.SP.PG.AI |
| 00000904 | RIDLIST storage | |
| 00000905 | IRLM storage | |
| 00000906 | DB2 | MEMBER |
| 00000907 | Data Space | MEMBER |
| 00000908 | Basic Floating Point Extensions Facility | |
| 00000909 | Extended Time-of-Day (TOD) Clock | |
| 0000090A | XML storage | |
| 00000A00 | Table | RD.CR.TB |
| 00000A10 | Alias | RELDEP. OWNER. ALIAS. RD.CR.AL |
| 00000A11 | Distinct type | SC.DT |
| 00000A12 | User-defined function | SC.SN |
| 00000A13 | Stored procedure | SC.SN |
| 00000A14 | Sequence | |
| 00000B00 | View | RD.CR.VW |
| 00000C00 | Index | RD.CR.IX |
| 00000C01 | Index | CR.IX |
| 00000D00 | DBID/OBID | RD.DI.OI |
| 00000D01 | DBID/OBID | DI.OI |
| 00000D02 | OBID | OI |
| 00000E00 | SU limit exceeded | CN |
| 00000F00 | Auxiliary column | DI.OI.ROWID.COLN DI.OI.DOCID.COLN |
| 00000F01 | LOB lock | DIX.PIX.ROWID.VRSN |
| 00000F81 | XML lock | DIX.PIX.DOCID |
| 00001000 | DDF | LOCATION or SUBSYSTEM ID |
| 00001001 | System conversation | LU.MODE. RTNCD. FDBK2. RCPRI. RCSEC. SENSE |
| 00001002 | Agent conversation | LU.MODE. RTNCD. FDBK2. RCPRI. RCSEC. SENSE |
| 00001003 | CNOS processing | LU.MODE. RTNCD. FDBK2. RCPRI. RCSEC. SENSE |
| 00001004 | CDB (Communication database) | LOCATION.AUTHORIZATION ID.PL |
| 00001005 | DB access agent | LOCATION |
| 00001007 | TCP/IP domain name | LINKNAME.DOMAIN.ERRNO |
| 00001008 | TCP/IP service name | LOCATION.SERVICE.ERRNO |
| 00001080 | ACCEL | SERVER.DOMAIN |
| 00001102 | Bootstrap data set (BSDS) | MEMBER |
| 00002000 | Table space CS-claim class | DB.SP |
| 00002001 | Table space RR-claim class | DB.SP |
| 00002002 | Table space write-claim class | DB.SP |
| 00002003 | Index space CS-claim class | DB.SP |
| 00002004 | Index space RR-claim class | DB.SP |
| 00002005 | Index space write-claim class | DB.SP |
| 00002006 | Table space partition CS-claim class | DB.SP.PT |
| 00002007 | Table space partition RR-claim class | DB.SP.PT |
| 00002008 | Table space partition write-claim class | DB.SP.PT |
| 00002009 | Index space partition CS-claim class | DB.SP.PT |
| 00002010 | Index space partition RR-claim class | DB.SP.PT |
| 00002011 | Index space partition write-claim class | DB.SP.PT |
| 00002100 | Table space DBET entry | DB.SP |
| 00002101 | Index space DBET entry | DB.SP |
| 00002102 | Table space partition DBET entry | DB.SP.PT |
| 00002103 | Index space partition DBET entry | DB.SP.PT |
| 00002104 | DBET hash chain lock timeout | INTERNAL LOCK NN |
| 00002105 | Logical partition DBET entry | DB.SP.PT |
| 00002200 | Routine Parameter Storage | DBP |
| 00002201 | Debug Agent Storage | DBP |
| 00002300 | ICSF encryption and decryption facilities | |
| 00003000 | Code (release maintenance level or system parameter) | REL, APAR, ZPARM |
| 00003002 | Number of Stored Procedures | |
| 00003072 | Index | |
| 00003073 | Index | |
| 00003328 | Release dependency | |
| 00003329 | DBID/OBID | DI.OI |
| 00003330 | OBID limit exceeded | |
| 00003840 | LOB column | |
| 00004000 | Profile exception threshold exceeded | PID.PTYPE.PNAME |
Disclaimer: This Db2® 12 for z/OS Reference Guide was developed to help users in their daily activities in administrating and programming in Db2 for z/OS. There are no guarantees expressed or implied with the contents in this guide. We want to provide a quality and useful reference for users. Please notify us of any mistakes or errors in this reference guide at blogs@bmc.com. Db2 is a registered trademark of the IBM Corporation.
