Successful Execution SQLCODE |
000 | SUCCESSFUL EXECUTION |
Warning SQLCODE |
+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 FOR FETCH, UPDATE OR DELETE, OR THE RESULT OF A QUERY IS AN EMPTY TABLE |
+110 | SQL UPDATE TO A DATA CAPTURE TABLE NOT SIGNALED TO ORIGINATING SUBSYSTEM |
+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 |
+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 |
+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 |
+339 | THE SQL STATEMENT HAS BEEN SUCCESSFULLY EXECUTED, BUT THERE MAY BE SOME CHARACTER CONVERSION INCONSISTENCIES |
+402 | LOCATION location IS UNKNOWN |
+403 | THE LOCAL OBJECT REFERENCED BY THE CREATE ALIAS STATEMENT DOES NOT EXIST |
+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, AND REFERENCES PRIVILEGES CANNOT BE GRANTED TO PUBLIC AT ALL LOCATIONS |
+562 | A GRANT OF A PRIVILEGE WAS IGNORED BECAUSE THE GRANTEE ALREADY HAS THE PRIVILEGE FROM THE GRANTOR |
+610 | INDEX index-name HAS BEEN PLACED IN RECOVER PENDING |
+625 | THE DEFINITION OF TABLE table-name HAS BEEN CHANGED TO INCOMPLETE |
+626 | DROPPING THE INDEX TERMINATES ENFORCEMENT OF THE UNIQUENESS OF A KEY THAT WAS DEFINED WHEN THE TABLE WAS CREATED |
+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 |
+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 THE INDEX MANAGER |
+738 | DEFINITION CHANGE OF object object_name MAY REQUIRE SIMILAR CHANGE ON READ-ONLY SYSTEMS |
+802 | EXCEPTION ERROR exception-type HAS OCCURRED DURING operation-type OPERATION ON data-type DATA, POSITION position-number |
+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 |
+2000 | TYPE 1 INDEXES WITH SUBPAGES GREATER THAN 1 CANNOT BECOME GROUP BUFFER POOL DEPENDENT IN A DATA SHARING ENVIRONMENT |
+30100 | OPERATION COMPLETED SUCCESSFULLY BUT A DISTRIBUTION PROTOCOL VIOLATION HAS BEEN DETECTED. ORIGINAL SQLCODE=original-sqlcode AND ORIGINAL SQLSTATE=original-sqlstate |
Error SQLCODE |
-007 | STATEMENT CONTAINS THE ILLEGAL CHARACTER character |
-010 | THE STRING CONSTANT BEGINNING string IS NOT TERMINATED |
-029 | INTO CLAUSE REQUIRED |
-060 | INVALID type SPECIFICATION : spec |
-084 | UNACCEPTABLE SQL STATEMENT |
-101 | THE STATEMENT IS TOO LONG OR TOO COMPLEX |
-102 | LITERAL STRING IS TOO LONG. STRING BEGINS string |
-103 | literal IS AN INVALID NUMERIC LITERAL |
-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 size |
-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 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 INSERT VALUES IS NOT THE SAME AS THE NUMBER OF OBJECT COLUMNS |
-118 | THE OBJECT TABLE OR VIEW OF THE INSERT, 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 OR SET CLAUSE INCLUDES A COLUMN FUNCTION |
-121 | THE COLUMN name IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE 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 |
-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 | A LIKE PREDICATE IS INVALID BECAUSE THE SECOND OPERAND IS NOT A STRING |
-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 A HOST VARIABLE OF MAXIMUM LENGTH GREATER THAN 254 |
-136 | SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS GREATER THAN 4000 BYTES |
-137 | RESULT OF CONCATENATION TOO LONG |
-138 | THE SECOND OR THIRD ARGUMENT OF THE SUBSTR FUNCTION IS OUT OF RANGE |
-144 | INVALID SECTION NUMBER number |
-150 | THE OBJECT OF THE INSERT, DELETE, OR UPDATE STATEMENT IS A VIEW 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 CREATE VIEW STATEMENT DOES NOT INCLUDE A REQUIRED COLUMN LIST |
-154 | THE CREATE VIEW FAILED BECAUSE THE VIEW DEFINITION CONTAINS A UNION, A UNION ALL, OR A REMOTE OBJECT |
-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 |
-159 | DROP OR COMMENT ON token IDENTIFIES A(N) token RATHER THAN A(N) token |
-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 STRING REPRESENTATION OF A DATETIME VALUE HAS INVALID SYNTAX |
-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 |
-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 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 | column-name IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED TABLE, OR ANY TABLE IDENTIFIED IN A FROM CLAUSE |
-208 | THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN name IS NOT PART OF THE RESULT TABLE |
-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 | column-name IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED TABLE, OR ANY TABLE IDENTIFIED IN A FROM CLAUSE |
-208 | THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN name IS NOT PART OF THE RESULT TABLE |
-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 |
-250 | THE LOCAL LOCATION NAME IS NOT DEFINED WHEN PROCESSING A THREE-PART OBJECT NAME |
-251 | TOKEN name IS NOT VALID |
-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 | UNDEFINED OR UNUSABLE HOST VARIABLE variable-name |
-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 |
-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 | SYSSTRINGS DOES NOT DEFINE A TRANSLATION FROM CCSID ccsid TO ccsid |
-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 |
-351 | AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION "" ON A PREPARE or DESCRIBE OPERATION |
-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 UPDATE OR INSERT STATEMENT SPECIFIES A STRING THAT IS TOO LONG column-name |
-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 OR INSERT VALUE IS NULL, BUT THE OBJECT COLUMN column-name CANNOT CONTAIN NULL VALUES |
-408 | AN UPDATE OR INSERT VALUE IS NOT COMPARABLE WITH THE DATA TYPE OF ITS OBJECT COLUMN column-name |
-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 |
-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 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 |
-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 |
-440 | THE NUMBER OF PARAMETERS IN THE PARAMETER LIST DOES NOT MATCH THE NUMBER OF PARAMETERS EXPECTED FOR STORED PROCEDURE name, AUTHID authid, LUNAME luname. number PARAMETERS WERE EXPECTED. |
-444 | USER PROGRAM name COULD NOT BE FOUND |
-450 | STORED PROCEDURE name, PARAMETER NUMBER number, OVERLAYED STORAGE BEYOND ITS DECLARED LENGTH |
-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 | SQL CALL FOR STORED PROCEDURE name FAILED DUE TO REASON rc |
-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 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 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 IN ERROR AT BIND TIME FOR SECTION = sectno PACKAGE = pkgname CONSISTENCY TOKEN = X'contoken' |
-530 | THE INSERT OR UPDATE VALUE OF FOREIGN KEY constraint-name IS INVALID |
-531 | THE PRIMARY 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 THE PRIMARY 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 OR A UNIQUE CONSTRAINT 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(BIND) IN THE object_type2 IS IN EFFECT |
-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 |
-574 | THE SPECIFIED DEFAULT VALUE CONFLICTS WITH THE COLUMN DEFINITION. |
-601 | THE NAME OF THE OBJECT TO BE CREATED 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 COLUMN 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 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 CANNOT BE DEFINED ON A TABLE IN A TABLE SPACE WITH LOCKSIZE ROW |
-618 | OPERATION operation IS NOT ALLOWED ON SYSTEM DATABASES |
-619 | OPERATION DISALLOWED BECAUSE THE WORK FILE DATABASE IS NOT STOPPED |
-620 | KEYWORD keyword IN stmt type STATEMENT IS NOT PERMITTED FOR A TABLE SPACE IN THE WORK FILE 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 |
-625 | TABLE table-name DOES NOT HAVE AN INDEX TO ENFORCE THE UNIQUENESS OF THE PRIMARY 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 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 |
-642 | TOO MANY COLUMNS IN UNIQUE CONSTRAINTS |
-643 | CHECK CONSTRAINT EXCEEDS MAXIMUM ALLOWABLE LENGTH |
-644 | INVALID VALUE SPECIFIED FOR KEYWORD keyword IN stmt-type TATEMENT |
-646 | TABLE table-name CANNOT BE CREATED IN PARTITIONED/DEFAULT TABLE SPACE tspace-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 |
-660 | INDEX index-name CANNOT BE CREATED 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 | A TABLE IN A PARTITIONED TABLE SPACE CANNOT BE EXPLICITLY DROPPED |
-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 | A 32K PAGE BUFFERPOOL MAY NOT 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 |
-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 | INVALID COLUMN TYPE FOR FIELDPROC, BIT DATA, SBCS DATA, OR MIXED DATA OPTION, column-name |
-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 |
-694 | THE DDL STATEMENT CANNOT BE EXECUTED BECAUSE A DROP IS PENDING ON THE DDL REGISTRATION TABLE table-name |
-713 | THE REPLACEMENT 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 FOR 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 |
-726 | BIND ERROR ATTEMPTING TO REPLACE PACKAGE = . THERE ARE ENABLE OR DISABLE ENTRIES CURRENTLY ASSOCIATED WITH THE PACKAGE |
-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 |
-741 | A WORK FILE DATABASE IS ALREADY DEFINED FOR MEMBER member-name |
-742 | DSNDB07 IS THE IMPLICIT WORK FILE DATABASE |
-751 | A STORED PROCEDURE HAS BEEN PLACED IN MUST_ROLLBACK STATE DUE TO SQL OPERATION name |
-752 | THE CONNECT STATEMENT IS INVALID BECAUSE THE PROCESS IS NOT IN THE CONNECTABLE STATE |
-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 PACKAGE NAME FOR PROGRAM program-name.consistency-token USING PLAN plan-name |
-815 | A GROUP BY OR HAVING CLAUSE IS IMPLICITLY OR EXPLICITLY SPECIFIED IN AN EMBEDDED SELECT STATEMENT OR A SUBQUERY OF A BASIC PREDICATE |
-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 |
-870 | THE NUMBER OF HOST VARIABLES IN THE STATEMENT IS NOT EQUAL TO THE NUMBER OF DESCRIPTORS |
-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 OF 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 |
-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 | 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 | AUTHORIZATION 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/VS OR CICS ENVIRONMENT |
-926 | ROLLBACK NOT VALID IN IMS/VS OR CICS 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 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 |
-965 | STORED PROCEDURE procname TERMINATED ABNORMALLY |
-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 |
-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) |
-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) |
-30090 | REMOTE OPERATION INVALID FOR APPLICATION EXECUTION ENVIRONMENT |
No comments
Post a Comment