SQL return codes: Difference between revisions
No edit summary |
wikademia>Wikademia m 63 revisions |
||
| (22 intermediate revisions by 4 users not shown) | |||
| Line 11: | Line 11: | ||
Negative means unsuccessful execution with an error. | Negative means unsuccessful execution with an error. | ||
An example is -911 which means a timeout has | An example is -911 which means a timeout has occurred with a rollback. | ||
Positive means successful execution with a warning. | Positive means successful execution with a warning. | ||
An example is +100 which means no rows found. | An example is +100 which means no rows found. | ||
If you have an SQL code with a letter in it look at Letter Codes below. | |||
Here is a more comprehensive list of the SQLCODEs for DB2: | Here is a more comprehensive list of the SQLCODEs for DB2: | ||
| Line 22: | Line 26: | ||
=== Zero (Successful) === | === Zero (Successful) === | ||
0 Successful | 0 Successful | ||
=== Negative (through -251) === | |||
-007 STATEMENT CONTAINS THE ILLEGAL CHARACTER character | |||
-010 String constant beginning string is NOT TERMINATED. | |||
-029 INTO Clause Required. | |||
-060 Invalid type Specification: "Spec" | |||
-079 QUALIFIER FOR DECLARED GLOBAL TEMPORARY TABLE table-name MUST BE SESSION, NOT qualifier | |||
-084 Unacceptable SQL Statement. | |||
-097 THE USE OF LONG VARCHAR OR LONG VARGRAPHIC IS NOT ALLOWED IN THIS CONTEXT | |||
-101 Statement is Too Long, or Too Complex. | |||
-102 String constant is too long. | |||
-103 Literal is an invalid Numeric Literal. | |||
-104 Illegal Symbol token. | |||
-105 Invalid String. | |||
-107 The Name, "NAME" is Too Long, Maximum Allowable size is "SIZE". | |||
-108 THE NAME name IS QUALIFIED INCORRECTLY | |||
-109 "CLAUSE" clause is not permitted. | |||
-110 Invalid Hexadecimal Literal Beginning "STRING" | |||
-111 A Column Function does not include a column name. | |||
-112 The Operand of a Column function is Another Column Function. | |||
-113 Invalid Character found in Name: "NAME", Reason Code- "REASON-CODE". | |||
-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" with out a Sub-query | |||
-117 The number of values in the INSERT does not match the number of columns. | |||
-118 THE OBJECT TABLE OR VIEW OF THE DELETE OR UPDATE STATEMENT IS ALSO IDENTIFIED IN A FROM CLAUSE | |||
-119 A COLUMN IDENTIFIED IN A HAVING CLAUSE IS NOT INCLUDED IN THE GROUP BY CLAUSE | |||
-120 A WHERE CLAUSE, SET CLAUSE, VALUES CLAUSE, OR A SET HOST-VARIABLE STATEMENT INCLUDES A COLUMN FUNCTION | |||
-121 THE COLUMN name IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE OR SET TRANSITION VARIABLE STATEMENT | |||
-122 A SELECT STATEMENT WITH NO GROUP BY CLAUSE CONTAINS A COLUMN NAME AND A COLUMN FUNCTION IN THE SELECT CLAUSE OR A | |||
COLUMN NAME IS CONTAINED IN THE SELECT CLAUSE BUT NOT IN THE GROUP BY CLAUSE | |||
-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 IDENTIFY 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 A COLUMN FUNCTION IN A SUBQUERY OF A HAVING 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 LONG STRING COLUMN column-name OR AN EXPRESSION THAT RESOLVES TO A LONG STRING | |||
-136 SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS GREATER THAN 4000 BYTES | |||
-137 THE LENGTH RESULTING FROM operation IS GREATER THAN maximum-length | |||
-138 THE SECOND OR THIRD ARGUMENT OF THE SUBSTR 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 CANNOT BE ALTERED | |||
-148 THE SOURCE TABLE source-name CANNOT BE RENAMED OR ALTERED | |||
-150 THE OBJECT OF THE INSERT, DELETE, OR UPDATE STATEMENT IS A VIEW OR TRANSITION TABLE FOR WHICH THE REQUESTED | |||
OPERATION IS NOT PERMITTED | |||
-151 THE UPDATE STATEMENT 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 THE VIEW IS NOT THE SAME AS THE NUMBER OF COLUMNS SPECIFIED BY THE SELECT | |||
CLAUSE, OR THE NUMBER OF COLUMNS SPECIFIED IN THE CORRELATION CLAUSE IN A FROM CLAUSE IS NOT THE SAME AS THE | |||
NUMBER OF COLUMNS IN THE CORRESPONDING TABLE, VIEW, TABLE EXPRESSION, OR TABLE FUNCTION | |||
-159 DROP OR COMMENT ON object IDENTIFIES A(N) object-type1 RATHER THAN A(N) object-type2 | |||
-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 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 OPERATION 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 RELIES 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 UNKNOWN OR INVALID FOR THE DATA TYPE OR SUBTYPE | |||
-190 ATTRIBUTES OF COLUMN column-name IN TABLE table-name ARE NOT COMPATIBLE WITH THE EXISTING COLUMN | |||
-191 A STRING CANNOT BE USED BECAUSE IT IS INVALID MIXED DATA | |||
-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 the specified keyword. | |||
-203 A REFERENCE TO COLUMN column-name IS AMBIGUOUS | |||
-204 Object not defined to DB2. | |||
-205 Column name not in table. | |||
-206 Column does not exist in any table of the SELECT. | |||
-208 THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN name IS NOT PART OF THE RESULT 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 Not the same number of expressions on both sides of the comparison in a SELECT . | |||
-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-name | |||
-223 AN UPDATE OR DELETE OPERATION WAS ATTEMPTED AGAINST AN UPDATE HOLE USING cursor-name | |||
-224 FETCH cannot make an INSENSITIVE cursor SENSITIVE. | |||
-225 FETCH STATEMENT FOR cursor-name IS NOT VALID BECAUSE THE CURSOR IS NOT DEFINED AS SCROLL | |||
-228 FOR UPDATE CLAUSE SPECIFIED FOR READ-ONLY CURSOR cursor-name | |||
-229 The locale specified in a SET LOCALE statement was not found. | |||
-240 THE PART CLAUSE OF A LOCK TABLE STATEMENT IS INVALID | |||
-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 | |||
-250 THE LOCAL LOCATION NAME IS NOT DEFINED WHEN PROCESSING A THREE-PART OBJECT NAME | |||
-251 TOKEN name IS NOT VALID | |||
=== Negative (-300 to -499) === | |||
-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 POSITION 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-name IS AN UNDEFINED OR UNUSABLE HOST VARIABLE OR IS USED IN A DYNAMIC SQL STATEMENT OR A TRIGGER | |||
DEFINITION | |||
-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 TRANSLATED. REASON reason-code, CHARACTER code-point, HOST VARIABLE | |||
position-number | |||
-331 A STRING CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE IT CANNOT BE TRANSLATED. REASON reason-code, CHARACTER | |||
code-point, POSITION position-number | |||
-332 CHARACTER CONVERSION BETWEEN CCSID from-ccsid TO to-ccsid REQUESTED BY reason-code IS NOT SUPPORTED | |||
-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 TRANSLATION | |||
-338 AN ON CLAUSE IS INVALID | |||
-339 THE SQL STATEMENT CANNOT BE EXECUTED FROM AN ASCII BASED DRDA APPLICATION REQUESTOR TO A V2R2 DB2 SUBSYSTEM | |||
-350 INVALID SPECIFICATION OF A LARGE OBJECT COLUMN | |||
-351 AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION position-number OF THE SELECT-LIST | |||
-352 AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION position-number OF THE INPUT-LIST | |||
-355 A LOB COLUMN IS TOO LARGE TO BE LOGGED | |||
-359 THE RANGE OF VALUES FOR THE IDENTITY COLUMN IS EXHAUSTED | |||
-372 ONLY ONE ROWID OR IDENTITY COLUMN IS ALLOWED IN A TABLE | |||
-373 DEFAULT CANNOT BE SPECIFIED FOR IDENTITY COLUMN column-name | |||
-390 THE FUNCTION function-name, SPECIFIC NAME specific-name, IS NOT VALID IN THE CONTEXT IN WHICH IT OCCURS | |||
-392 SQLDA PROVIDED FOR CURSOR cursor HAS BEEN CHANGED FROM THE PREVIOUS FETCH | |||
-396 object-type object-name ATTEMPTED TO EXECUTE AN SQL STATEMENT DURING FINAL CALL PROCESSING | |||
-397 THE OPTION GENERATED IS SPECIFIED WITH A COLUMN THAT IS NOT A ROW ID OR DISTINCT TYPE BASED ON A ROW ID | |||
-399 INVALID VALUE ROWID WAS SPECIFIED | |||
-400 THE CATALOG 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 IS NULL, BUT THE OBJECT COLUMN column-name CANNOT CONTAIN NULL VALUES | |||
-408 THE VALUE IS NOT COMPATIBLE WITH THE DATA TYPE OF ITS TARGET | |||
-409 INVALID OPERAND OF A COUNT FUNCTION | |||
-410 THE FLOATING POINT LITERAL literal CONTAINS MORE THAN 30 CHARACTERS | |||
-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 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 UNION OR A UNION ALL DO NOT HAVE COMPARABLE COLUMN | |||
DESCRIPTIONS | |||
-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 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 | |||
-433 VALUE value IS TOO LONG | |||
-435 AN INVALID SQLSTATE sqlstate IS SPECIFIED IN THE FUNCTION RAISE_ERROR OR IN A SIGNAL SQLSTATE STATEMENT | |||
-438 APPLICATION RAISED ERROR WITH DIAGNOSTIC TEXT: text | |||
-440 NO routine-type BY THE NAME routine-name HAVING COMPATIBLE ARGUMENTS WAS FOUND | |||
-441 INVALID USE OF ’DISTINCT’ OR ’ALL’ WITH SCALAR FUNCTION function-name | |||
-443 ROUTINE routine-name (SPECIFIC NAME specific-name) HAS RETURNED AN ERROR SQLSTATE WITH DIAGNOSTIC TEXT msg-text | |||
-444 USER PROGRAM name COULD NOT BE FOUND | |||
-449 CREATE OR ALTER STATEMENT FOR FUNCTION OR PROCEDURE routine-name CONTAINS AN INVALID FORMAT OF THE EXTERNAL NAME | |||
CLAUSE OR IS MISSING THE | |||
-450 USER-DEFINED FUNCTION OR STORED PROCEDURE name, PARAMETER NUMBER parmnum, OVERLAYED STORAGE BEYOND ITS DECLARED | |||
LENGTH. | |||
-451 THE data-item DEFINITION, IN THE CREATE FUNCTION FOR function-name CONTAINS DATA TYPE type WHICH IS NOT | |||
APPROPRIATE FOR AN EXTERNAL FUNCTION WRITTEN IN THE GIVEN LANGUAGE | |||
-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 THE SCHEMA | |||
-455 IN CREATE FUNCTION FOR function-name, THE SCHEMA NAME schema-name1 PROVIDED FOR THE 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 FUNCTION 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 WITH DATA TYPE source-data-type CANNOT BE CAST TO TYPE target-data-type | |||
-463 EXTERNAL ROUTINE routine-name (SPECIFIC NAME specific-name) HAS RETURNED AN INVALID SQLSTATE sqlstate, WITH | |||
DIAGNOSTIC TEXT text | |||
-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 FUNCTION OR 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 function-name | |||
-476 REFERENCE TO FUNCTION function-name WAS NAMED WITHOUT A SIGNATURE, BUT THE FUNCTION IS NOT UNIQUE WITHIN ITS SCHEMA | |||
-478 DROP OR REVOKE ON OBJECT TYPE type1 CANNOT BE PROCESSED BECAUSE OBJECT name OF TYPE type2 IS DEPENDENT ON IT | |||
-480 THE PROCEDURE procedure-name HAS NOT YET BEEN CALLED | |||
-482 The procedure 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 AN SQL STATEMENT WHEN THE DEFINITION OF THE FUNCTION OR 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 database-name | |||
-499 CURSOR cursor-name HAS ALREADY BEEN ASSIGNED TO THIS OR ANOTHER RESULT SET FROM PROCEDURE procedure-name. | |||
=== Negative (-500 to -697) === | |||
-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 Opening cursor that is already open. | |||
-503 Updating column needs to be specified. | |||
-504 THE CURSOR NAME cursor-name IS NOT DEFINED | |||
-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 | |||
-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 STATEMENT DOES NOT SPECIFY 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 IN 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 RESTRICTS 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 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 TO PERFORM OPERATION operation | |||
-553 auth-id SPECIFIED IS NOT ONE OF THE VALID AUTHORIZATION IDS | |||
-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 | |||
-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 NAMES | |||
-574 THE SPECIFIED DEFAULT VALUE OR IDENTITY ATTRIBUTE VALUE CONFLICTS WITH THE DEFINITION OF COLUMN column-name | |||
-577 object-type object-name ATTEMPTED TO MODIFY DATA WHEN THE DEFINITION OF THE FUNCTION OR PROCEDURE DID NOT SPECIFY | |||
THIS ACTION | |||
-579 object-type object-name ATTEMPTED TO READ DATA WHEN THE DEFINITION OF THE FUNCTION OR 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 CANNOT BE A QUANTIFIED PREDICATE, IN PREDICATE, OR AN EXISTS | |||
PREDICATE. | |||
-583 THE USE OF FUNCTION function-name IS INVALID BECAUSE IT IS NOT DETERMINISTIC OR HAS AN EXTERNAL ACTION | |||
-585 THE SCHEMA NAME schema-name CANNOT APPEAR MORE THAN ONCE IN THE CURRENT PATH | |||
-586 THE TOTAL LENGTH OF THE CURRENT PATH SPECIAL REGISTER CANNOT EXCEED 254 CHARACTERS | |||
-587 A LIST OF item-references ARE NOT IN THE SAME FAMILY | |||
-590 PARAMETER NAME parameter-name IS NOT UNIQUE IN THE CREATE FOR ROUTINE routine-name | |||
-592 NOT AUTHORIZED TO CREATE FUNCTIONS OR PROCEDURES IN WLM ENVIRONMENT env-name | |||
-593 NOT NULL MUST BE SPECIFIED FOR ROWID OR DISTINCT TYPE COLUMN column-name | |||
-601 THE NAME OF THE OBJECT TO BE CREATED OR THE TARGET OF A RENAME STATEMENT IS IDENTICAL TO THE EXISTING NAME name OF | |||
THE OBJECT TYPE obj-type | |||
-602 TOO MANY COLUMNS SPECIFIED IN A CREATE INDEX | |||
-603 A UNIQUE INDEX CANNOT BE CREATED BECAUSE THE TABLE CONTAINS ROWS WHICH ARE DUPLICATES WITH RESPECT TO THE VALUES | |||
OF THE IDENTIFIED COLUMNS | |||
-604 A DATA TYPE DEFINITION SPECIFIES AN INVALID LENGTH, PRECISION, OR SCALE ATTRIBUTE | |||
-607 OPERATION OR OPTION operation IS NOT DEFINED FOR THIS OBJECT | |||
-611 ONLY LOCKMAX 0 CAN BE SPECIFIED WHEN THE LOCK SIZE OF THE TABLESPACE IS TABLESPACE OR TABLE | |||
-612 column-name IS A DUPLICATE COLUMN NAME | |||
-613 THE PRIMARY KEY OR A UNIQUE CONSTRAINT IS TOO LONG OR HAS TOO MANY COLUMNS | |||
-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 | |||
-617 A TYPE 1 INDEX IS NOT VALID FOR TABLE table-name | |||
-618 OPERATION operation IS NOT ALLOWED ON SYSTEM DATABASES | |||
-619 OPERATION DISALLOWED BECAUSE THE DATABASE IS NOT STOPPED | |||
-620 KEYWORD keyword IN stmt type STATEMENT IS NOT PERMITTED FOR A space type SPACE IN THE database type DATABASE | |||
-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 A CLUSTERING INDEX ALREADY EXISTS ON TABLE table-name | |||
-624 TABLE table-name ALREADY HAS A PRIMARY KEY OR UNIQUE KEY CONSTRAINT WITH SPECIFIED COLUMNS | |||
-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 PAGESET 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 | |||
-630 THE WHERE NOT NULL SPECIFICATION IS INVALID FOR TYPE 1 INDEXES | |||
-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 THE PARTITIONING KEYS FOR PARTITION part-num ARE NOT SPECIFIED IN ASCENDING OR DESCENDING ORDER | |||
-637 DUPLICATE keyword KEYWORD | |||
-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 | |||
-640 LOCKSIZE ROW CANNOT BE SPECIFIED BECAUSE TABLE IN THIS TABLESPACE HAS TYPE 1 INDEX | |||
-643 CHECK CONSTRAINT EXCEEDS MAXIMUM ALLOWABLE LENGTH | |||
-644 INVALID VALUE SPECIFIED FOR KEYWORD keyword IN stmt-type STATEMENT | |||
-646 TABLE table-name CANNOT BE CREATED IN SPECIFIED TABLE SPACE table-space-name BECAUSE IT ALREADY CONTAINS A TABLE | |||
-647 BUFFERPOOL bp-name CANNOT BE SPECIFIED BECAUSE IT 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 proc-name | |||
-653 TABLE table-name IN PARTITIONED TABLE SPACE 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 TABLE SPACE tspace-name BECAUSE KEY LIMITS ARE NOT | |||
SPECIFIED | |||
-661 INDEX index-name CANNOT BE CREATED ON PARTITIONED TABLE SPACE tspace-name BECAUSE THE NUMBER OF PART | |||
SPECIFICATIONS IS NOT EQUAL TO THE NUMBER OF PARTITIONS OF THE TABLE SPACE | |||
-662 A PARTITIONED INDEX CANNOT BE CREATED ON A NON-PARTITIONED TABLE SPACE tspace-name | |||
-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 TABLE SPACE CANNOT BE EXPLICITLY DROPPED | |||
-668 THE COLUMN CANNOT BE ADDED TO THE TABLE BECAUSE THE TABLE HAS AN EDIT PROCEDURE | |||
-669 THE OBJECT CANNOT BE EXPLICITLY DROPPED. REASON reason-code | |||
-670 THE RECORD LENGTH OF THE TABLE EXCEEDS THE PAGE SIZE LIMIT | |||
-671 THE BUFFERPOOL ATTRIBUTE OF THE TABLE SPACE CANNOT BE ALTERED AS SPECIFIED BECAUSE IT WOULD CHANGE THE PAGE SIZE | |||
OF THE TABLE SPACE | |||
-672 OPERATION DROP NOT ALLOWED ON TABLE table_name | |||
-676 ONLY A 4K PAGE BUFFERPOOL CAN BE USED FOR AN INDEX | |||
-677 INSUFFICIENT VIRTUAL STORAGE FOR BUFFERPOOL EXPANSION | |||
-678 THE LITERAL literal 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: reason-code, MSG: | |||
message-token | |||
-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, msgno | |||
-689 TOO MANY COLUMNS DEFINED FOR A DEPENDENT TABLE | |||
-690 THE STATEMENT IS REJECTED BY DATA DEFINITION CONTROL SUPPORT. REASON reason-code | |||
-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 | |||
-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 CORRELATION 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. | |||
=== Negative (-713 to -991) === | |||
-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 FALLBACK HAS OCCURRED | |||
-718 REBIND OF PACKAGE package-name FAILED BECAUSE IBMREQD OF ibmreqd IS INVALID | |||
-719 BIND ADD ERROR USING auth-id AUTHORITY PACKAGE package-name ALREADY EXISTS | |||
-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 IT 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-name. INFORMATION RETURNED: SQLCODE: sqlerror, SQLSTATE: | |||
sqlstate, MESSAGE TOKENS token-list, SECTION NUMBER section-number | |||
-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 | |||
-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 DATASET dsname MUST BE DEFINED WITH SHAREOPTIONS(1,3) | |||
-732 THE DATABASE IS DEFINED ON THIS SUBSYSTEM WITH THE ROSHARE READ ATTRIBUTE BUT THE TABLE SPACE OR INDEX SPACE HAS | |||
NOT BEEN DEFINED ON THE OWNING SUBSYSTEM | |||
-733 THE DESCRIPTION OF A TABLE SPACE, 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 TABLE SPACE NOT ALLOWED | |||
-739 CREATE OR 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 database-type 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 table-name | |||
-750 THE SOURCE TABLE source-name CANNOT BE RENAMED BECAUSE IT IS REFERENCED IN EXISTING VIEW DEFINITIONS OR TRIGGER | |||
DEFINITIONS | |||
-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 TABLE SPACE NAME | |||
-764 A LOB TABLE SPACE AND ITS ASSOCIATED BASE TABLE SPACE MUST BE IN THE SAME DATABASE | |||
-765 TABLE IS NOT COMPATIBLE WITH DATABASE | |||
-766 THE OBJECT OF A STATEMENT IS AN AUXILIARY 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 COLUMN | |||
-771 INVALID SPECIFICATION OF A ROWID COLUMN | |||
-797 ATTEMPT to CREATE TRIGGER trigger-name WITH AN UNSUPPORTED TRIGGERED SQL STATEMENT | |||
-798 YOU CANNOT INSERT A VALUE INTO A COLUMN THAT IS DEFINED WITH THE OPTION GENERATED ALWAYS COLUMN column-name | |||
-802 EXCEPTION ERROR exception-type HAS OCCURRED DURING operation-type OPERATION ON data-type DATA, POSITION | |||
position-number | |||
-803 Duplicate key on insert or update. | |||
-804 AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT PARAMETERS FOR THE SQL STATEMENT, REASON reason | |||
-805 DBRM or package not found in plan. | |||
-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 More than one row retrieved in SELECT INTO. | |||
-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 PACKAGE NAME FOR PROGRAM program-name consistency-token USING PLAN plan | |||
-815 A GROUP BY OR HAVING CLAUSE IS IMPLICITLY OR EXPLICITLY SPECIFIED IN A SUBSELECT OF A BASIC PREDICATE OR THE SET | |||
CLAUSE OF AN UPDATE STATEMENT | |||
-817 THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE STATEMENT WILL RESULT IN A PROHIBITED UPDATE OPERATION. | |||
-818 Plan and program: timestamp mismatch. | |||
-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 | |||
-846 INVALID SPECIFICATION OF AN IDENTITY COLUMN | |||
-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 DATA ENCODED WITH DIFFERENT ENCODING SCHEMES CANNOT BE REFERENCED IN THE SAME SQL STATEMENT | |||
-874 THE ENCODING SCHEME SPECIFIED FOR THE object-type MUST BE THE SAME AS THE CONTAINING TABLE SPACE OR OTHER | |||
PARAMETERS | |||
-875 operand CANNOT BE USED WITH THE ASCII DATA REFERENCED | |||
-876 'object' CANNOT BE CREATED, REASON 'reason' | |||
-877 CCSID ASCII OR CCSID UNICODE IS NOT ALLOWED FOR THIS DATABASE OR TABLE SPACE | |||
-878 THE PLAN_TABLE USED FOR EXPLAIN CANNOT BE ASCII OR UNICODE | |||
-879 CREATE or ALTER STATEMENT FOR obj-name CANNOT DEFINE A COLUMN, DISTINCT TYPE, FUNCTION OR STORED PROCEDURE | |||
PARAMETER 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 Unavailable resource. Someone else is locking your data. | |||
-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 | |||
-908 bind-type ERROR USING auth-id AUTHORITY. BIND, REBIND OR AUTO-REBIND OPERATION IS NOT ALLOWED | |||
-909 THE OBJECT HAS BEEN DELETED | |||
-910 THE SQL STATEMENT CANNOT ACCESS AN OBJECT ON WHICH A DROP OR ALTER IS PENDING | |||
-911 Rollback has been done due to Deadlock or timeout. | |||
-913 Deadlock or timeout has ocurred. | |||
-917 BIND PACKAGE FAILED | |||
-918 THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE A CONNECTION HAS BEEN LOST | |||
-919 A ROLLBACK OPERATION IS REQUIRED | |||
-922 AUTHORIZATION FAILURE: error-type ERROR. REASON reason-code (Authorization needed). | |||
-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, CICS OR RRSAF ENVIRONMENT | |||
-926 ROLLBACK NOT VALID IN IMS, CICS OR RRSAF ENVIRONMENT | |||
-927 The language interface was called but no connection had been made. | |||
-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 DEFINED 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 | |||
-981 THE SQL STATEMENT FAILED BECAUSE THE RRSAF CONNECTION IS NOT IN A STATE THAT ALLOWS SQL OPERATIONS, REASON | |||
reason-code. | |||
-991 CALL ATTACH WAS UNABLE TO ESTABLISH AN IMPLICIT CONNECT OR OPEN TO DB2. RC1= rc1 RC2= rc2 | |||
=== Negative | === Negative (Greater than -991) === | ||
-1760 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 sqldanum, EXPECTED NUMBER opnum | |||
-5012 HOST VARIABLE host-variable IS NOT EXACT NUMERIC WITH SCALE ZERO | |||
-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 | |||
-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 csect-name bind-type bind-subtype ERROR USING auth-id AUTHORITY OPERATION IS NOT ALLOWED ON A TRIGGER PACKAGE | |||
package-name | |||
-20073 THE FUNCTION function-name CANNOT BE ALTERED BECAUSE IT IS REFERENCED IN EXISTING VIEW 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 A VIEW WAS SPECIFIED FOR LIKE BUT IT INCLUDES A ROWID COLUMN | |||
-20100 AN ERROR OCCURRED WHEN BINDING A TRIGGERED SQL STATEMENT. INFORMATION RETURNED: SECTION NUMBER : section-number | |||
SQLCODE sqlerror, SQLSTATE sqlstate, AND MESSAGE TOKENS token-list | |||
-20101 THE FUNCTION function FAILED WITH REASON rc | |||
-20102 CREATE OR ALTER STATEMENT FOR ROUTINE routine-name SPECIFIED THE option OPTION WHICH IS NOT ALLOWED FOR THE TYPE | |||
OF ROUTINE | |||
-20104 AN ATTEMPT TO ALTER A CCSID FROM from-ccsid TO to-ccsid FAILED | |||
-20106 THE CCSID FOR TABLE SPACE OR DATABASE CANNOT BE CHANGED BECAUSE THE TABLE SPACE OR DATABASE ALREADY CONTAINS A | |||
TABLE THAT IS REFERENCED IN EXISTING VIEW DEFINITIONS | |||
-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 CANNOT ISSUE SAVEPOINT, RELEASE SAVEPOINT, ROLLBACK TO SAVEPOINT FROM A TRIGGER, FROM A USER-DEFINED FUNCTION, | |||
OR FROM A GLOBAL TRANSACTION | |||
-20123 CALL TO 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 | |||
-20126 CURSOR cursor IS DEFINED AS SCROLLABLE, BUT THE ENVIRONMENT INVOLVES A HOP SITE | |||
-20127 VALUE SPECIFIED ON FETCH STATEMENT FOR ABSOLUTE OR RELATIVE IS TOO LARGE FOR DRDA | |||
-20129 LOCAL SPECIAL REGISTER IS NOT VALID AS USED | |||
-20200 THE INSTALL_JAR OR REPLACE_JAR PROCEDURE FOR jar-id FAILED AS url COULD NOT BE LOCATED. | |||
-20201 THE INSTALL_JAR, REPLACE_JAR, OR REMOVE_JAR PROCEDURE FOR jar-name FAILED AS THE JAR NAME IS INVALID | |||
-20202 THE REPLACE_JAR OR REMOVE_JAR PROCEDURE FOR 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_JAR OR REMOVE_JAR PROCEDURE FOR jar-name SPECIFIED THE USE OF A DEPLOYMENT DESCRIPTOR | |||
-20210 THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT WAS AT A LEVEL THAT IS INCOMPATIBLE WITH THE CURRENT VALUE OF | |||
THE ENCODING BIND OPTION OR SPECIAL REGISTER | |||
-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 RETURNED A DYNAMIC RESULT SET OF AN INVALID CLASS. PARAMETER number IS NOT A | |||
DB2 RESULT SET | |||
-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 | |||
-30020 EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION: REASON | |||
<reason-code (sub-code)> | |||
-30021 EXECUTION FAILED DUE 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 | |||
-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> | |||
-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 AUTHORIZATION FAILURE | |||
-30060 RDB AUTHORIZATION FAILURE | |||
-30061 RDB NOT FOUND | |||
-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 option2 | |||
=== Positive Values (Warnings) === | === Positive Values (Warnings) === | ||
+012 THE UNQUALIFIED COLUMN NAME column-name WAS INTERPRETED AS A CORRELATED REFERENCE | |||
+098 A DYNAMIC SQL STATEMENT ENDS WITH A SEMICOLON. | |||
+100 Row not found or end of cursor. | |||
+111 THE SUBPAGES OPTION IS NOT SUPPORTED FOR TYPE 2 INDEXES | |||
+117 THE NUMBER OF INSERT VALUES IS NOT THE SAME AS THE NUMBER OF OBJECT COLUMNS | |||
+162 TABLESPACE database-name.tablespace-name HAS BEEN PLACED IN CHECK PENDING | |||
+203 THE QUALIFIED COLUMN NAME column-name WAS RESOLVED USING A NON-UNIQUE OR UNEXPOSED NAME | |||
+204 name IS AN UNDEFINED NAME | |||
+206 column-name IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED TABLE, OR ANY TABLE IDENTIFIED IN A FROM CLAUSE | |||
+218 THE SQL STATEMENT REFERENCING A REMOTE OBJECT CANNOT BE EXPLAINED | |||
+219 THE REQUIRED EXPLANATION TABLE table-name DOES NOT EXIST | |||
+220 THE COLUMN column-name IN EXPLANATION TABLE table-name IS NOT DEFINED PROPERLY | |||
+222 Trying to fetch a row within a DELETE statement. | |||
+223 Trying to fetch a row within an UPDATE statement. | |||
+231 FETCH after a BEFORE or AFTER but not on a valid row. | |||
+236 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 ARE REQUIRED FOR integer3 COLUMNS | |||
+237 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 ARE REQUIRED BECAUSE AT LEAST ONE OF THE COLUMNS BEING | |||
DESCRIBED IS A DISTINCT TYPE | |||
+238 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 SQLVAR ENTRIES ARE NEEDED FOR integer3 COLUMNS BECAUSE AT | |||
LEAST ONE OF THE COLUMNS BEING DESCRIBED IS A LOB | |||
+239 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 ARE REQUIRED FOR integer3 COLUMNS BECAUSE AT LEAST ONE OF THE | |||
COLUMNS BEING DESCRIBED IS A DISTINCT TYPE | |||
+304 Value cannot be assigned to this host variable because it is out of range. | |||
+331 THE NULL VALUE HAS BEEN ASSIGNED TO A HOST VARIABLE BECAUSE THE STRING CANNOT BE TRANSLATED. REASON reason-code, | |||
CHARACTER code-point, HOST VARIABLE position-number | |||
+335 DB2 CONVERTED A HOST VARIABLE, PARAMETER, OR COLUMN NUMBER var-num var-name-or-num TO COLUMN NAME,HOST VARIABLE, | |||
OR EXPRESSION NUMBER col-name-or-num FROM from ccsid TO to-ccsid, AND RESULTING IN SUBSTITUTION CHARACTERS. | |||
+339 THE SQL STATEMENT HAS BEEN SUCCESSFULLY EXECUTED, BUT THERE MAY BE SOME CHARACTER CONVERSION INCONSISTENCIES | |||
+394 USER SPECIFIED OPTIMIZATION HINTS USED DURING ACCESS PATH SELECTION | |||
+395 USER SPECIFIED OPTIMIZATION HINTS ARE INVALID (REASON CODE = reason-code). THE OPTIMIZATION HINTS ARE IGNORE | |||
+402 LOCATION location IS UNKNOWN | |||
+403 THE LOCAL OBJECT REFERENCED BY THE CREATE ALIAS STATEMENT DOES NOT EXIST | |||
+434 OPTION keyword IS A DEPRECATED FEATURE | |||
+445 VALUE value HAS BEEN TRUNCATED | |||
+462 EXTERNAL FUNCTION OR PROCEDURE name (SPECIFIC NAME specific-name) HAS RETURNED A WARNING SQLSTATE, WITH DIAGNOSTIC | |||
TEXT text | |||
+464 PROCEDURE proc RETURNED num QUERY RESULT SETS, WHICH EXCEEDS THE DEFINED LIMIT integer | |||
+466 PROCEDURE proc RETURNED num QUERY RESULTS SETS | |||
+494 NUMBER OF RESULT SETS IS GREATER THAN NUMBER OF LOCATORS | |||
+495 ESTIMATED PROCESSOR COST OF estimate-amount1 PROCESSOR SECONDS (estimate-amount2 SERVICE UNITS) IN COST CATEGORY | |||
cost-category EXCEEDS A RESOURCE LIMIT WARNING THRESHOLD OF limit- amount SERVICE UNITS | |||
+535 THE RESULT OF THE POSITIONED UPDATE OR DELETE MAY DEPEND ON THE ORDER OF THE ROWS | |||
+541 THE REFERENTIAL OR UNIQUE CONSTRAINT name HAS BEEN IGNORED BECAUSE IT IS A DUPLICATE | |||
+551 auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION operation ON OBJECT object-name | |||
+552 auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION operation | |||
+558 THE WITH GRANT OPTION IS IGNORED | |||
+561 THE ALTER, INDEX, REFERENCES, AND TRIGGER PRIVILEGES CANNOT BE GRANTED PUBLIC AT ALL LOCATIONS | |||
+562 A GRANT OF A PRIVILEGE WAS IGNORED BECAUSE THE GRANTEE ALREADY HAS THE PRIVILEGE FROM THE GRANTOR | |||
+585 THE SCHEMA NAME schema-name APPEARS MORE THAN ONCE IN THE CURRENT PATH | |||
+599 COMPARISON FUNCTIONS ARE NOT CREATED FOR A DISTINCT TYPE BASED ON A LONG STRING DATA TYPE | |||
+610 A CREATE/ALTER ON OBJECT object-name HAS PLACED OBJECT IN utility PENDING | |||
+645 WHERE NOT NULL IS IGNORED BECAUSE THE INDEX KEY CANNOT CONTAIN NULL VALUES | |||
+650 THE TABLE BEING CREATED OR ALTERED CANNOT BECOME A DEPENDENT TABLE | |||
+653 TABLE table-name IN PARTITIONED TABLESPACE tspace-name IS NOT AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS | |||
NOT BEEN CREATED | |||
+655 STOGROUP stogroup_name HAS BOTH SPECIFIC AND NON-SPECIFIC VOLUME IDS. IT WILL NOT BE ALLOWED IN FUTURE RELEASES | |||
+658 THE SUBPAGES VALUE IS IGNORED FOR THE CATALOG INDEX index-name | |||
+664 THE INTERNAL LENGTH OF THE LIMIT-KEY FIELDS FOR THE PARTITIONED INDEX index-name EXCEEDS THE LENGTH IMPOSED BY DB2 | |||
+738 DEFINITION CHANGE OF object object_name MAY REQUIRE SIMILAR CHANGE ON READ-ONLY SYSTEMS | |||
+799 A SET STATEMENT REFERENCES A SPECIAL REGISTER THAT DOES NOT EXIST AT THE SERVER SITE | |||
+802 The null indicator was set to -2 as an arithmetic statement didn't work. | |||
+806 BIND ISOLATION LEVEL RR CONFLICTS WITH TABLESPACE LOCKSIZE PAGE OR LOCKSIZE ROW AND LOCKMAX 0 | |||
+807 THE RESULT OF DECIMAL MULTIPLICATION MAY CAUSE OVERFLOW | |||
+863 THE CONNECTION WAS SUCCESSFUL BUT ONLY SBCS WILL BE SUPPORTED | |||
+883 ROLLBACK TO SAVEPOINT OCCURRED WHEN THERE WERE OPERATIONS THAT CANNOT BE UNDONE, OR AN OPERATION THAT CANNOT BE | |||
UNDONE OCCURRED WHEN THERE WAS A SAVEPOINT OUTSTANDING | |||
+2000 TYPE 1 INDEXES WITH SUBPAGES GREATER THAN 1 CANNOT BECOME GROUP BUFFER POOL DEPENDENT IN A DATA SHARING | |||
ENVIRONMENT | |||
+20002 THE GBPCACHE SPECIFICATION IS IGNORED, bpname DOES NOT ALLOW CACHING | |||
+20007 USE OF OPTIMIZATION HINTS IS DISALLOWED BY A DB2 SUBSYSTEM PARAMETER. THE SPECIAL REGISTER ’OPTIMIZATION HINT’ | |||
IS SET TO THE DEFAULT VALUE OF BLANKS. | |||
+20122 DEFINE NO OPTION IS NOT APPLICABLE IN THE CONTEXT SPECIFIED | |||
+20141 TRUNCATION OF VALUE WITH LENGTH length OCCURRED FOR hv-or-parm-number | |||
+20267 OPTION clause IS NOT SUPPORTED IN THE CONTEXT IN WHICH IT WAS SPECIFIED | |||
+30100 OPERATION COMPLETED SUCCESSFULLY BUT A DISTRIBUTION PROTOCOL VIOLATION HAS BEEN DETECTED. ORIGINAL | |||
SQLCODE=original-sqlcode AND ORIGINAL SQLSTATE=original-sqlstate | |||
=== Letter SQL Codes === | |||
If you have a code in the type of SQL-0000##A these are still valid but a bit harder to decipher. | |||
Use the chart below to map the letter to the last number of the value. | |||
This was created when SQL Codes where only able to be unsigned. | |||
Example SQL-000010} => This translates to SQL CODE: 100. | |||
Example SQL-000010N => This translates to SQL CODE: -105. | |||
Example SQL-000092P => This translates to SQL CODE: -927. | |||
<nowiki> | |||
0 1 2 3 4 5 6 7 8 9 | |||
} A B C D E F G H I | |||
------------------------------------------ | |||
-1 -2 -3 -4 -5 -6 -7 -8 -9 | |||
J K L M N O P Q R | |||
</nowiki> | |||
==External links== | ==External links== | ||
* A [http://www.theamericanprogrammer.com/programming/sqlcodes.shtml more extensive list] of the codes | * A [http://www.theamericanprogrammer.com/programming/sqlcodes.shtml more extensive list] of the codes | ||
{{Subject|Database systems}} | |||
{{Alphabetical|S}} | {{Alphabetical|S}} | ||
{{DDC|600}} | |||
{{LOC|QA76.75}} | |||