SQL Error Codes

Post on 13-Dec-2015

164 Views

Category:

Documents

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

SQL Error Codes

Transcript

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 1/42

SQL error codes

SQL return codes that are preceded by a minus sign (­) indicate that the SQL statement execution wasunsuccessful.

­007STATEMENT CONTAINS THE ILLEGAL CHARACTER invalid­character

­010THE STRING CONSTANT BEGINNING string IS NOT TERMINATED

­011COMMENT NOT CLOSED

­029INTO CLAUSE REQUIRED

­051identifier­name (sql­type) WAS PREVIOUSLY DECLARED OR REFERENCED

­056AN SQLSTATE OR SQLCODE VARIABLE DECLARATION IS IN A NESTED COMPOUND STATEMENT

­057THE RETURN STATEMENT IN AN SQL FUNCTION MUST RETURN A VALUE.

­058VALUE SPECIFIED ON RETURN STATEMENT MUST BE AN INTEGER

­060INVALID specification­type SPECIFICATION : specification­value

­078PARAMETER NAMES MUST BE SPECIFIED FOR ROUTINE routine­name

­079QUALIFIER FOR OBJECT name WAS SPECIFIED AS qualifier1 but qualifier2 IS REQUIRED

­084UNACCEPTABLE SQL STATEMENT

­087A NULL VALUE WAS SPECIFIED IN A CONTEXT WHERE A NULL IS NOT ALLOWED

­096VARIABLE variable­name DOES NOT EXIST OR IS NOT SUPPORTED BY THE SERVER AND ADEFAULT VALUE WAS NOT PROVIDED

­097THE USE OF LONG VARCHAR OR LONG VARGRAPHIC IS NOT ALLOWED IN THIS CONTEXT

­101THE STATEMENT IS TOO LONG OR TOO COMPLEX

­102STRING CONSTANT IS TOO LONG. STRING BEGINS string

­103constant IS AN INVALID NUMERIC CONSTANT

­104ILLEGAL SYMBOL "token". SOME SYMBOLS THAT MIGHT BE LEGAL ARE: token­list

­105INVALID STRING

­107

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 2/42

THE NAME name­value IS TOO LONG. MAXIMUM ALLOWABLE SIZE IS maximum­size

­108THE NAME name IS QUALIFIED INCORRECTLY

­109clause­type CLAUSE IS NOT PERMITTED

­110INVALID HEXADECIMAL CONSTANT BEGINNING constant

­112THE OPERAND OF AN AGGREGATE FUNCTION INCLUDES AN AGGREGATE FUNCTION, AN OLAPSPECIFICATION, OR A SCALAR FULLSELECT

­113INVALID CHARACTER FOUND IN: string, REASON CODE nnn

­114THE LOCATION NAME location DOES NOT MATCH THE CURRENT SERVER

­115A PREDICATE IS INVALID BECAUSE THE COMPARISON OPERATOR operator IS FOLLOWED BY APARENTHESIZED LIST OR BY ANY OR ALL WITHOUT A SUBQUERY

­117THE NUMBER OF VALUES ASSIGNED IS NOT THE SAME AS THE NUMBER OF SPECIFIED ORIMPLIED COLUMNS

­118THE OBJECT TABLE OR VIEW OF THE DELETE OR UPDATE STATEMENT IS ALSO IDENTIFIED INA FROM CLAUSE

­119A COLUMN OR EXPRESSION IN A HAVING CLAUSE IS NOT VALID

­120AN AGGREGATE FUNCTION OR OLAP SPECIFICATION IS NOT VALID IN THE CONTEXT IN WHICHIT WAS INVOKED

­121THE COLUMN name IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE OPERATIONOR SET TRANSITION VARIABLE STATEMENT

­122COLUMN OR EXPRESSION IN THE SELECT LIST IS NOT VALID

­123THE PARAMETER IN POSITION n IN THE FUNCTION name MUST BE A CONSTANT OR KEYWORD

­125AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A COLUMN OF THE RESULT

­126THE SELECT STATEMENT CONTAINS BOTH AN UPDATE CLAUSE AND AN ORDER BY CLAUSE

­127DISTINCT IS SPECIFIED MORE THAN ONCE IN A SUBSELECT

­128INVALID USE OF NULL IN A PREDICATE

­129THE STATEMENT CONTAINS TOO MANY TABLE NAMES

­130THE ESCAPE CLAUSE CONSISTS OF MORE THAN ONE CHARACTER, OR THE STRING PATTERNCONTAINS AN INVALID OCCURRENCE OF THE ESCAPE CHARACTER

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 3/42

­131STATEMENT WITH LIKE PREDICATE HAS INCOMPATIBLE DATA TYPES

­132AN OPERAND OF value IS NOT VALID

­133AN AGGREGATE FUNCTION IN A SUBQUERY OF A HAVING CLAUSE IS INVALID BECAUSE ALLCOLUMN REFERENCES IN ITS ARGUMENT ARE NOT CORRELATED TO THE GROUP BY RESULTTHAT THE HAVING CLAUSE IS APPLIED TO

­134IMPROPER USE OF A STRING, LOB, OR XML VALUE

­136SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH TOO LONG

­137THE LENGTH RESULTING FROM operation IS GREATER THAN maximum­length

­138THE SECOND OR THIRD ARGUMENT OF THE SUBSTR OR SUBSTRING FUNCTION IS OUT OFRANGE

­142THE SQL STATEMENT IS NOT SUPPORTED

­144INVALID SECTION NUMBER number

­147ALTER FUNCTION function­name FAILED BECAUSE SOURCE FUNCTIONS OR SPATIAL FUNCTIONSCANNOT BE ALTERED

­148THE SOURCE TABLE OR TABLESPACE source­name CANNOT BE ALTERED, REASON reason­code

­150THE OBJECT OF THE INSERT, DELETE, UPDATE, MERGE, OR TRUNCATE STATEMENT IS AVIEW, SYSTEM­MAINTAINED MATERIALIZED QUERY TABLE, OR TRANSITION TABLE FOR WHICHTHE REQUESTED OPERATION IS NOT PERMITTED

­151THE UPDATE OPERATION IS INVALID BECAUSE THE CATALOG DESCRIPTION OF COLUMNcolumn­name INDICATES THAT IT CANNOT BE UPDATED

­152THE DROP clause CLAUSE IN THE ALTER STATEMENT IS INVALID BECAUSE constraint­name IS Aconstraint­type

­153THE STATEMENT IS INVALID BECAUSE THE VIEW OR TABLE DEFINITION DOES NOT INCLUDE AUNIQUE NAME FOR EACH COLUMN

­154THE STATEMENT FAILED BECAUSE VIEW OR TABLE DEFINITION IS NOT VALID

­156THE STATEMENT DOES NOT IDENTIFY A TABLE

­157ONLY A TABLE NAME CAN BE SPECIFIED IN A FOREIGN KEY CLAUSE. object­name IS NOT THENAME OF A TABLE.

­158THE NUMBER OF COLUMNS SPECIFIED FOR name IS NOT THE SAME AS THE NUMBER OFCOLUMNS IN THE RESULT TABLE.

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 4/42

­159THE STATEMENT REFERENCES object­name WHICH IDENTIFIES AN actual­type RATHER THAN ANexpected­type

­160THE WITH CHECK OPTION CLAUSE IS NOT VALID FOR THE SPECIFIED VIEW

­161THE INSERT OR UPDATE IS NOT ALLOWED BECAUSE A RESULTING ROW DOES NOT SATISFYTHE VIEW DEFINITION

­164authorization­id DOES NOT HAVE THE PRIVILEGE TO CREATE A VIEW WITH QUALIFICATIONqualifier­name

­170THE NUMBER OF ARGUMENTS SPECIFIED FOR function­name IS INVALID

­171THE DATA TYPE, LENGTH, OR VALUE OF ARGUMENT argument­position OF function­name ISINVALID

­173UR IS SPECIFIED ON THE WITH CLAUSE BUT THE CURSOR IS NOT READ­ONLY

­180THE DATE, TIME, OR TIMESTAMP VALUE value IS INVALID

­181THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID DATETIME VALUE

­182AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE IS INVALID

­183AN ARITHMETIC OPERATION ON A DATE OR TIMESTAMP HAS A RESULT THAT IS NOT WITHINTHE VALID RANGE OF DATES

­184AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE CONTAINS A PARAMETER MARKER

­185THE LOCAL FORMAT OPTION HAS BEEN USED WITH A DATE OR TIME AND NO LOCAL EXIT HASBEEN INSTALLED

­186THE LOCAL DATE LENGTH OR LOCAL TIME LENGTH HAS BEEN INCREASED AND EXECUTINGPROGRAM RELIES ON THE OLD LENGTH

­187A REFERENCE TO A CURRENT DATETIME SPECIAL REGISTER IS INVALID BECAUSE THE MVSTOD CLOCK IS BAD OR THE MVS PARMTZ IS OUT OF RANGE

­188THE STRING REPRESENTATION OF A NAME IS INVALID

­189CCSID ccsid IS INVALID

­190THE ATTRIBUTES SPECIFIED FOR THE COLUMN table­name.column­name ARE NOT COMPATIBLEWITH THE EXISTING COLUMN DEFINITION

­191A STRING CANNOT BE USED BECAUSE IT IS INVALID MIXED DATA

­197A QUALIFIED COLUMN NAME IS NOT ALLOWED IN THE ORDER BY CLAUSE WHEN A SET

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 5/42

OPERATOR IS ALSO SPECIFIED

­198THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE STATEMENT IS BLANK OR EMPTY

­199ILLEGAL USE OF KEYWORD keyword. TOKEN token­list WAS EXPECTED

­203A REFERENCE TO COLUMN column­name IS AMBIGUOUS

­204name IS AN UNDEFINED NAME

­205column­name IS NOT A COLUMN OF TABLE table­name

­206object­name IS NOT VALID IN THE CONTEXT WHERE IT IS USED

­208THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN column­name IS NOT PART OF THERESULT TABLE

­212name IS SPECIFIED MORE THAN ONCE IN THE REFERENCING CLAUSE OF A TRIGGERDEFINITION

­214AN EXPRESSION IN THE FOLLOWING POSITION, OR STARTING WITH position­or­expression­start INTHE clause­type CLAUSE IS NOT VALID. REASON CODE = reason­code

­216THE NUMBER OF ELEMENTS ON EACH SIDE OF A PREDICATE OPERATOR DOES NOT MATCH.PREDICATE OPERATOR IS operator.

­219THE REQUIRED EXPLANATION TABLE table­name DOES NOT EXIST

­220THE COLUMN column­name IN EXPLANATION TABLE table­name IS NOT DEFINED PROPERLY

­221"SET OF OPTIONAL COLUMNS" IN EXPLANATION TABLE table­name IS INCOMPLETE. OPTIONALCOLUMN column­name IS MISSING

­222AN UPDATE OR DELETE OPERATION WAS ATTEMPTED AGAINST A HOLE USING CURSOR cursor­name

­224THE RESULT TABLE DOES NOT AGREE WITH THE BASE TABLE USING cursor­name

­225FETCH STATEMENT FOR cursor­name IS NOT VALID FOR THE DECLARATION OF THE CURSOR

­227FETCH fetch­orientation IS NOT ALLOWED, BECAUSE CURSOR cursor­name HAS AN UNKNOWNPOSITION (sqlcode,sqlstate)

­228FOR UPDATE CLAUSE SPECIFIED FOR READ­ONLY CURSOR cursor­name

­229THE LOCALE locale SPECIFIED IN A SET LC_CTYPE OR OTHER STATEMENT THAT IS LOCALESENSITIVE WAS NOT FOUND

­240

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 6/42

THE PARTITION CLAUSE OF A LOCK TABLE STATEMENT IS INVALID

­242THE OBJECT NAMED object­name OF TYPE object­type WAS SPECIFIED MORE THAN ONCE IN THELIST OF OBJECTS, OR THE NAME IS THE SAME AS AN EXISTING OBJECT

­243SENSITIVE CURSOR cursor­name CANNOT BE DEFINED FOR THE SPECIFIED SELECTSTATEMENT

­244SENSITIVITY sensitivity SPECIFIED ON THE FETCH IS NOT VALID FOR CURSOR cursor­name

­245THE INVOCATION OF FUNCTION routine­name IS AMBIGUOUS

­246STATEMENT USING CURSOR cursor­name SPECIFIED NUMBER OF ROWS num­rows WHICH IS NOTVALID WITH dimension

­247A HOLE WAS DETECTED ON A MULTIPLE ROW FETCH STATEMENT USING CURSOR cursor­name,BUT INDICATOR VARIABLES WERE NOT PROVIDED TO DETECT THE CONDITION

­248A POSITIONED DELETE OR UPDATE STATEMENT FOR CURSOR cursor­name SPECIFIED ROW nOF A ROWSET, BUT THE ROW IS NOT CONTAINED WITHIN THE CURRENT ROWSET

­249DEFINITION OF ROWSET ACCESS FOR CURSOR cursor­name IS INCONSISTENT WITH THE FETCHORIENTATION CLAUSE clause SPECIFIED

­250THE LOCAL LOCATION NAME IS NOT DEFINED WHEN PROCESSING A THREE­PART OBJECTNAME

­251TOKEN name IS NOT VALID

­253A NON­ATOMIC statement STATEMENT SUCCESSFULLY COMPLETED FOR SOME OF THEREQUESTED ROWS, POSSIBLY WITH WARNINGS, AND ONE OR MORE ERRORS

­254A NON­ATOMIC statement STATEMENT ATTEMPTED TO PROCESS MULTIPLE ROWS OF DATA,BUT ERRORS OCCURRED

­270FUNCTION NOT SUPPORTED

­300THE STRING CONTAINED IN HOST VARIABLE OR PARAMETER position­number IS NOT NUL­TERMINATED

­301THE VALUE OF INPUT HOST VARIABLE OR PARAMETER NUMBER position­number CANNOT BEUSED AS SPECIFIED BECAUSE OF ITS DATA TYPE

­302THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER position­number IS INVALID OR TOOLARGE FOR THE TARGET COLUMN OR THE TARGET VALUE

­303A VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER position­numberBECAUSE THE DATA TYPES ARE NOT COMPARABLE

­304

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 7/42

A VALUE WITH DATA TYPE data­type1 CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSETHE VALUE IS NOT WITHIN THE RANGE OF THE HOST VARIABLE IN POSITION position­numberWITH DATA TYPE data­type2

­305THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER position­numberBECAUSE NO INDICATOR VARIABLE IS SPECIFIED

­309A PREDICATE IS INVALID BECAUSE A REFERENCED HOST VARIABLE HAS THE NULL VALUE

­310DECIMAL HOST VARIABLE OR PARAMETER number CONTAINS NON­DECIMAL DATA

­311THE LENGTH OF INPUT HOST VARIABLE NUMBER position­number IS NEGATIVE OR GREATERTHAN THE MAXIMUM

­312VARIABLE variable­name IS NOT DEFINED OR NOT USABLE

­313THE NUMBER OF HOST VARIABLES SPECIFIED IS NOT EQUAL TO THE NUMBER OF PARAMETERMARKERS

­314THE STATEMENT CONTAINS AN AMBIGUOUS HOST VARIABLE REFERENCE

­327THE ROW CANNOT BE INSERTED BECAUSE IT IS OUTSIDE THE BOUND OF THE PARTITIONRANGE FOR THE LAST PARTITION

­330A STRING CANNOT BE USED BECAUSE IT CANNOT BE PROCESSED. REASON reason­code,CHARACTER code­point, HOST VARIABLE position­number

­331CHARACTER CONVERSION CANNOT BE PERFORMED BECAUSE A STRING, POSITION position­number, CANNOT BE CONVERTED FROM source­ccsid TO target­ccsid, REASON reason­code

­332CHARACTER CONVERSION BETWEEN CCSID from­ccsid TO to­ccsid REQUESTED BY reason­code ISNOT SUPPORTED

­333THE SUBTYPE OF A STRING VARIABLE IS NOT THE SAME AS THE SUBTYPE KNOWN AT BINDTIME AND THE DIFFERENCE CANNOT BE RESOLVED BY CHARACTER CONVERSION

­336THE SCALE OF THE DECIMAL NUMBER MUST BE ZERO

­338AN ON CLAUSE IS INVALID

­340THE COMMON TABLE EXPRESSION name HAS THE SAME IDENTIFIER AS ANOTHEROCCURRENCE OF A COMMON TABLE EXPRESSION DEFINITION WITHIN THE SAME STATEMENT

­341A CYCLIC REFERENCE EXISTS BETWEEN THE COMMON TABLE EXPRESSIONS name1 ANDname2

­342THE COMMON TABLE EXPRESSION name MUST NOT USE SELECT DISTINCT AND MUST USEUNION ALL BECAUSE IT IS RECURSIVE

­343

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 8/42

THE COLUMN NAMES ARE REQUIRED FOR THE RECURSIVE COMMON TABLE EXPRESSION name

­344THE RECURSIVE COMMON TABLE EXPRESSION name HAS MISMATCHED DATA TYPES ORLENGTHS OR CODE PAGE FOR COLUMN column­name

­345THE FULLSELECT OF THE RECURSIVE COMMON TABLE EXPRESSION name MUST BE A UNIONALL AND MUST NOT INCLUDE AGGREGATE FUNCTIONS, GROUP BY CLAUSE, HAVING CLAUSE,OR AN EXPLICIT JOIN INCLUDING AN ON CLAUSE

­346AN INVALID REFERENCE TO COMMON TABLE EXPRESSION name OCCURS IN THE FIRSTFULLSELECT, AS A SECOND OCCURRENCE IN THE SAME FROM CLAUSE, OR IN THE FROMCLAUSE OF A SUBQUERY

­348sequence­expression CANNOT BE SPECIFIED IN THIS CONTEXT

­350column­name WAS IMPLICITLY OR EXPLICITLY REFERENCED IN A CONTEXT IN WHICH IT CANNOTBE USED

­351AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION position­number OF THE SELECT­LIST

­352AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION position­number OF THE INPUT­LIST

­353FETCH IS NOT ALLOWED, BECAUSE CURSOR cursor­name HAS AN UNKNOWN POSITION

­354A ROWSET FETCH STATEMENT MAY HAVE RETURNED ONE OR MORE ROWS OF DATA.HOWEVER, ONE OR MORE NON­TERMINATING ERROR CONDITIONS WERE ENCOUNTERED. USETHE GET DIAGNOSTICS STATEMENT FOR MORE INFORMATION REGARDING THE CONDITIONSTHAT WERE ENCOUNTERED

­355A LOB COLUMN IS TOO LARGE TO BE LOGGED

­356KEY EXPRESSION expression­number IS NOT VALID, REASON CODE = reason­code

­359THE RANGE OF VALUES FOR THE IDENTITY COLUMN OR SEQUENCE IS EXHAUSTED

­363THE EXTENDED INDICATOR VARIABLE VALUE FOR PARAMETER position­number IS OUT OFRANGE.

­365USE OF THE VALUE OF EXTENDED INDICATOR VARIABLE IN POSITION value­position IS NOTVALID.

­372ONLY ONE ROWID, IDENTITY, ROW CHANGE TIMESTAMP, ROW BEGIN, ROW END,TRANSACTION START ID, OR SECURITY LABEL COLUMN IS ALLOWED IN A TABLE

­373DEFAULT CANNOT BE SPECIFIED FOR COLUMN OR SQL VARIABLE name

­374THE CLAUSE clause HAS NOT BEEN SPECIFIED IN THE CREATE OR ALTER FUNCTIONSTATEMENT FOR LANGUAGE SQL FUNCTION function­name BUT AN EXAMINATION OF THE

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 9/42

FUNCTION BODY REVEALS THAT IT SHOULD BE SPECIFIED

­390THE FUNCTION function­name, SPECIFIC NAME specific­name, IS NOT VALID IN THE CONTEXTWHERE IT IS USED

­392SQLDA PROVIDED FOR CURSOR cursor­name HAS BEEN CHANGED FROM THE PREVIOUS FETCH(reason­code)

­393THE CONDITION OR CONNECTION NUMBER IS INVALID

­396object­type object­name ATTEMPTED TO EXECUTE AN SQL STATEMENT DURING FINAL CALLPROCESSING

­397GENERATED IS SPECIFIED AS PART OF A COLUMN DEFINITION, BUT IT IS NOT VALID FOR THEDEFINITION OF THE COLUMN

­398A LOCATOR WAS REQUESTED FOR HOST VARIABLE NUMBER position­number BUT THEVARIABLE IS NOT A LOB

­399INVALID VALUE ROWID WAS SPECIFIED

­400THE CATALOG HAS THE MAXIMUM NUMBER OF USER DEFINED INDEXES

­401THE DATA TYPES OF THE OPERANDS OF AN OPERATION ARE NOT COMPATIBLE

­402AN ARITHMETIC FUNCTION OR OPERATOR function­operator IS APPLIED TO CHARACTER ORDATETIME DATA

­404THE SQL STATEMENT SPECIFIES A STRING THAT IS TOO LONG

­405THE NUMERIC CONSTANT constant CANNOT BE USED AS SPECIFIED BECAUSE IT IS OUT OFRANGE

­406A CALCULATED OR DERIVED NUMERIC VALUE IS NOT WITHIN THE RANGE OF ITS OBJECTCOLUMN

­407AN UPDATE, INSERT, OR SET VALUE IS NULL, BUT THE OBJECT COLUMN column­name CANNOTCONTAIN NULL VALUES

­408THE VALUE IS NOT COMPATIBLE WITH THE DATA TYPE OF ITS TARGET. TARGET NAME IS name

­409INVALID OPERAND OF A COUNT FUNCTION

­410A NUMERIC VALUE value IS TOO LONG, OR IT HAS A VALUE THAT IS NOT WITHIN THE RANGE OFITS DATA TYPE

­412THE SELECT CLAUSE OF A SUBQUERY SPECIFIES MULTIPLE COLUMNS

­413OVERFLOW OR UNDERFLOW OCCURRED DURING NUMERIC DATA TYPE CONVERSION

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 10/42

­414A LIKE PREDICATE IS INVALID BECAUSE THE FIRST OPERAND IS NOT A STRING

­415THE CORRESPONDING COLUMNS, column­number, OF THE OPERANDS OF A SET OPERATOR ARENOT COMPATIBLE

­416AN OPERAND OF A SET OPERATOR CONTAINS A LONG STRING COLUMN

­417A STATEMENT STRING TO BE PREPARED INCLUDES PARAMETER MARKERS AS THEOPERANDS OF THE SAME OPERATOR

­418A STATEMENT STRING TO BE PREPARED CONTAINS AN INVALID USE OF PARAMETERMARKERS

­419THE DECIMAL DIVIDE OPERATION IS INVALID BECAUSE THE RESULT WOULD HAVE A NEGATIVESCALE

­420THE VALUE OF A STRING ARGUMENT WAS NOT ACCEPTABLE TO THE function­name FUNCTION

­421THE OPERANDS OF A SET OPERATOR DO NOT HAVE THE SAME NUMBER OF COLUMNS

­423INVALID VALUE FOR LOCATOR IN POSITION position­#

­426DYNAMIC COMMIT NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOTALLOWED

­427DYNAMIC ROLLBACK NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOTALLOWED

­430routine­type routine­name (SPECIFIC NAME specific­name) HAS ABNORMALLY TERMINATED

­431ROUTINE routine­name (SPECIFIC NAME specific­name) OF TYPE routine­type HAS BEENINTERRUPTED BY THE USER

­433VALUE value IS TOO LONG

­435AN INVALID SQLSTATE sqlstate IS SPECIFIED IN A RAISE_ERROR FUNCTION, RESIGNALSTATEMENT, OR SIGNAL STATEMENT

­438APPLICATION RAISED ERROR WITH DIAGNOSTIC TEXT: text

­440NO AUTHORIZED routine­type BY THE NAME routine­name HAVING COMPATIBLE ARGUMENTS WASFOUND

­441INVALID USE OF 'DISTINCT' OR 'ALL' WITH FUNCTION function­name

­443ROUTINE routine­name (SPECIFIC NAME specific­name) HAS RETURNED AN ERROR SQLSTATEWITH DIAGNOSTIC TEXT msg­text

­444

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 11/42

USER PROGRAM name COULD NOT BE FOUND

­449CREATE OR ALTER STATEMENT FOR FUNCTION OR PROCEDURE routine­name CONTAINS ANINVALID FORMAT OF THE EXTERNAL NAME CLAUSE OR IS MISSING THE EXTERNAL NAMECLAUSE

­450USER­DEFINED FUNCTION OR STORED PROCEDURE name, PARAMETER NUMBER parmnum,OVERLAYED STORAGE BEYOND ITS DECLARED LENGTH.

­451THE data­item DEFINITION IN THE CREATE OR ALTER STATEMENT FOR routine­name CONTAINSDATA TYPE type WHICH IS NOT SUPPORTED FOR THE TYPE AND LANGUAGE OF THE ROUTINE

­452UNABLE TO ACCESS THE FILE REFERENCED BY HOST VARIABLE variable­position. REASONCODE: reason­code

­453THERE IS A PROBLEM WITH THE RETURNS CLAUSE IN THE CREATE FUNCTION STATEMENTFOR function­name

­454THE SIGNATURE PROVIDED IN THE CREATE FUNCTION STATEMENT FOR function­nameMATCHES THE SIGNATURE OF SOME OTHER FUNCTION ALREADY EXISTING IN THE SCHEMA

­455IN CREATE FUNCTION FOR function­name, THE SCHEMA NAME schema­name1 PROVIDED FOR THESPECIFIC NAME DOES NOT MATCH THE SCHEMA NAME schema­name2 OF THE FUNCTION

­456IN CREATE FUNCTION FOR function­name, THE SPECIFIC NAME specific­name ALREADY EXISTS INTHE SCHEMA

­457A FUNCTION OR DISTINCT TYPE CANNOT BE CALLED name SINCE IT IS RESERVED FORSYSTEM USE

­458IN A REFERENCE TO FUNCTION function­name BY SIGNATURE, A MATCHING FUNCTION COULDNOT BE FOUND

­461A VALUE WITH DATA TYPE source­data­type CANNOT BE CAST TO TYPE target­data­type

­469SQL CALL STATEMENT MUST SPECIFY AN OUTPUT HOST VARIABLE FOR PARAMETER number

­470SQL CALL STATEMENT SPECIFIED A NULL VALUE FOR INPUT PARAMETER number, BUT THESTORED PROCEDURE DOES NOT SUPPORT NULL VALUES.

­471INVOCATION OF FUNCTION OR PROCEDURE name FAILED DUE TO REASON rc

­472CURSOR cursor­name WAS LEFT OPEN BY EXTERNAL FUNCTION function­name (SPECIFIC NAMEspecific­name)

­473A USER DEFINED DATA TYPE CANNOT BE CALLED THE SAME NAME AS A SYSTEMPREDEFINED TYPE (BUILT­IN TYPE)

­475THE RESULT TYPE type­1 OF THE SOURCE FUNCTION CANNOT BE CAST TO THE RETURNS TYPEtype­2 OF THE USER­DEFINED FUNCTION function­name

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 12/42

­476REFERENCE TO FUNCTION function­name WAS NAMED WITHOUT A SIGNATURE, BUT THEFUNCTION IS NOT UNIQUE WITHIN ITS SCHEMA

­478DROP OR REVOKE ON OBJECT TYPE object­type CANNOT BE PROCESSED BECAUSE OBJECTdependent­object OF TYPE dependent­type IS DEPENDENT ON IT

­480THE PROCEDURE procedure­name HAS NOT YET BEEN CALLED

­482THE PROCEDURE procedure­name RETURNED NO LOCATORS

­483IN CREATE FUNCTION FOR function­name STATEMENT, THE NUMBER OF PARAMETERS DOESNOT MATCH THE NUMBER OF PARAMETERS OF THE SOURCE FUNCTION

­487object­type object­name ATTEMPTED TO EXECUTE AN SQL STATEMENT WHEN THE DEFINITION OFTHE FUNCTION OR PROCEDURE DID NOT SPECIFY THIS ACTION

­490NUMBER number DIRECTLY SPECIFIED IN AN SQL STATEMENT IS OUTSIDE THE RANGE OFALLOWABLE VALUES IN THIS CONTEXT (minval, maxval)

­491CREATE STATEMENT FOR USER­DEFINED FUNCTION function­name MUST HAVE A RETURNSCLAUSE AND: THE EXTERNAL CLAUSE WITH OTHER REQUIRED KEYWORDS; THE PARAMETERNAMES; OR THE SOURCE CLAUSE

­492THE CREATE FUNCTION FOR function­name HAS A PROBLEM WITH PARAMETER NUMBER number.IT MAY INVOLVE A MISMATCH WITH A SOURCE FUNCTION

­495ESTIMATED PROCESSOR COST OF estimate­amount1 PROCESSOR SECONDS (estimate­amount2SERVICE UNITS) IN COST CATEGORY cost­category EXCEEDS A RESOURCE LIMIT ERRORTHRESHOLD OF limit­ amount SERVICE UNITS

­496THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT REFERENCES A RESULT SET THATWAS NOT CREATED BY THE CURRENT SERVER

­497THE MAXIMUM LIMIT OF INTERNAL IDENTIFIERS HAS BEEN EXCEEDED FOR DATABASEdatabase­name

­499CURSOR cursor­name HAS ALREADY BEEN ASSIGNED TO THIS OR ANOTHER RESULT SET FROMPROCEDURE procedure­name.

­500THE IDENTIFIED CURSOR WAS CLOSED WHEN THE CONNECTION WAS DESTROYED

­501THE CURSOR IDENTIFIED IN A FETCH OR CLOSE STATEMENT IS NOT OPEN

­502THE CURSOR IDENTIFIED IN AN OPEN STATEMENT IS ALREADY OPEN

­503A COLUMN CANNOT BE UPDATED BECAUSE IT IS NOT IDENTIFIED IN THE UPDATE CLAUSE OFTHE SELECT STATEMENT OF THE CURSOR

­504CURSOR NAME cursor­name IS NOT DECLARED

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 13/42

­507THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT OPEN

­508THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT POSITIONED ON AROW OR ROWSET THAT CAN BE UPDATED OR DELETED

­509THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT THE SAME TABLEDESIGNATED BY THE CURSOR

­510THE TABLE DESIGNATED BY THE CURSOR OF THE UPDATE OR DELETE STATEMENT CANNOTBE MODIFIED

­511THE FOR UPDATE CLAUSE CANNOT BE SPECIFIED BECAUSE THE RESULT TABLE DESIGNATEDBY THE SELECT STATEMENT CANNOT BE MODIFIED

­512STATEMENT REFERENCE TO REMOTE OBJECT IS INVALID

­513THE ALIAS alias­name MUST NOT BE DEFINED ON ANOTHER LOCAL OR REMOTE ALIAS

­514THE CURSOR cursor­name IS NOT IN A PREPARED STATE

­516THE DESCRIBE STATEMENT DOES NOT SPECIFY A PREPARED STATEMENT

­517CURSOR cursor­name CANNOT BE USED BECAUSE ITS STATEMENT NAME DOES NOT IDENTIFY APREPARED SELECT STATEMENT

­518THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID PREPARED STATEMENT

­519THE PREPARE STATEMENT IDENTIFIES THE SELECT STATEMENT OF THE OPENED CURSORcursor­name

­525THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT WAS IN ERROR AT BIND TIME FORSECTION = sectno PACKAGE = pkgname CONSISTENCY TOKEN = contoken

­526THE REQUESTED OPERATION OR USAGE DOES NOT APPLY TO table­type TEMPORARY TABLEtable­name

­530THE INSERT OR UPDATE VALUE OF FOREIGN KEY constraint­name IS INVALID

­531PARENT KEY IN A PARENT ROW CANNOT BE UPDATED BECAUSE IT HAS ONE OR MOREDEPENDENT ROWS IN RELATIONSHIP constraint­name

­532THE RELATIONSHIP constraint­name RESTRICTS THE DELETION OF ROW WITH RID X rid­number

­533INVALID MULTIPLE­ROW INSERT

­534THE PRIMARY KEY CANNOT BE UPDATED BECAUSE OF MULTIPLE­ROW UPDATE

­536THE DELETE STATEMENT IS INVALID BECAUSE TABLE table­name CAN BE AFFECTED BY THE

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 14/42

OPERATION

­537THE PRIMARY KEY, FOREIGN KEY, UNIQUE, OR PARTITIONING KEY CLAUSE IDENTIFIESCOLUMN column­name MORE THAN ONCE

­538FOREIGN KEY name DOES NOT CONFORM TO THE DESCRIPTION OF A PARENT KEY OF TABLEtable­name

­539TABLE table­name DOES NOT HAVE A PRIMARY KEY

­540THE DEFINITION OF TABLE table­name IS INCOMPLETE BECAUSE IT LACKS A PRIMARY INDEXOR A REQUIRED UNIQUE INDEX

­542column­name CANNOT BE A COLUMN OF A HASH KEY, PRIMARY KEY, A UNIQUE CONSTRAINT,OR A PARENT KEY BECAUSE IT CAN CONTAIN NULL VALUES

­543A ROW IN A PARENT TABLE CANNOT BE DELETED BECAUSE THE CHECK CONSTRAINT check­constraint RESTRICTS THE DELETION

­544THE CHECK CONSTRAINT SPECIFIED IN THE ALTER TABLE STATEMENT CANNOT BE ADDEDBECAUSE AN EXISTING ROW VIOLATES THE CHECK CONSTRAINT

­545THE REQUESTED OPERATION IS NOT ALLOWED BECAUSE A ROW DOES NOT SATISFY THECHECK CONSTRAINT check­constraint

­546THE CHECK CONSTRAINT constraint­name IS INVALID

­548A CHECK CONSTRAINT THAT IS DEFINED WITH column­name IS INVALID

­549THE statement STATEMENT IS NOT ALLOWED FOR object_type1 object_name BECAUSE THE BINDOPTION DYNAMICRULES(RUN) IS NOT IN EFFECT FOR object_type2

­551auth­id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION operation ON OBJECT object­name

­552authorization­id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION operation

­553authorization­id SPECIFIED IS NOT ONE OF THE VALID AUTHORIZATION IDS FOR REQUESTEDOPERATION

­554AN AUTHORIZATION ID OR ROLE CANNOT GRANT A PRIVILEGE TO ITSELF

­555AN AUTHORIZATION ID OR ROLE CANNOT REVOKE A PRIVILEGE FROM ITSELF

­556revoke­target CANNOT HAVE THE privilege PRIVILEGE object­name REVOKED BY revoker­id BECAUSETHE REVOKEE DOES NOT POSSESS THE PRIVILEGE OR THE REVOKER DID NOT MAKE THEGRANT

­557INCONSISTENT GRANT/REVOKE KEYWORD keyword. PERMITTED KEYWORDS ARE keyword­list

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 15/42

­559ALL AUTHORIZATION FUNCTIONS HAVE BEEN DISABLED

­562THE SPECIFIED PRIVILEGES CANNOT BE GRANTED TO PUBLIC.

­567bind­type AUTHORIZATION ERROR USING auth­id AUTHORITY PACKAGE = package­namePRIVILEGE = privilege

­571THE STATEMENT WOULD RESULT IN A MULTIPLE SITE UPDATE

­573TABLE table­name DOES NOT HAVE A UNIQUE KEY WITH THE SPECIFIED COLUMN NAMES

­574THE SPECIFIED DEFAULT VALUE OR IDENTITY ATTRIBUTE VALUE CONFLICTS WITH THEDEFINITION OF COLUMN column­name

­575OBJECT object­name (OBJECT TYPE object­type) CANNOT BE REFERENCED EXPLICITLY ORIMPLICITLY

­577object­type object­name ATTEMPTED TO MODIFY DATA WHEN THE DEFINITION OF THE FUNCTIONOR PROCEDURE DID NOT SPECIFY THIS ACTION

­578THE RETURN STATEMENT WAS NOT EXECUTED FOR SQL FUNCTION function­name.

­579object­type object­name ATTEMPTED TO READ DATA WHEN THE DEFINITION OF THE FUNCTION ORPROCEDURE DID NOT SPECIFY THIS ACTION

­580THE RESULT­EXPRESSIONS OF A CASE EXPRESSION CANNOT ALL BE NULL

­581THE DATA TYPES OF THE RESULT­EXPRESSIONS OF A CASE EXPRESSION ARE NOTCOMPATIBLE

­582THE SEARCH­CONDITION IN A SEARCHED­WHEN­CLAUSE OF A CASE IS NOT VALID IN THECONTEXT IN WHICH IT WAS SPECIFIED. THE SEARCH CONDITION CONTAINS A QUANTIFIEDPREDICATE OR AN IN PREDICATE THAT INCLUDES A FULLSELECT, AND THESE ARE NOTALLOWED IN THE SPECIFIED CONTEXT.

­583THE USE OF FUNCTION OR EXPRESSION name IS INVALID BECAUSE IT IS NOT DETERMINISTICOR HAS AN EXTERNAL ACTION

­584INVALID USE OF NULL

­585THE COLLECTION collection­id APPEARS MORE THAN ONCE IN THE SET special­registerSTATEMENT

­586THE TOTAL LENGTH OF THE CURRENT PATH SPECIAL REGISTER CANNOT EXCEED 2048CHARACTERS

­589A POSITIONED DELETE OR UPDATE STATEMENT FOR CURSOR cursor­name SPECIFIED A ROWOF A ROWSET, BUT THE CURSOR IS NOT POSITIONED ON A ROWSET

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 16/42

­590NAME name IS NOT UNIQUE IN THE CREATE OR ALTER FOR ROUTINE routine­name

­592NOT AUTHORIZED TO CREATE FUNCTIONS OR PROCEDURES IN WLM ENVIRONMENT env­name

­593NOT NULL MUST BE SPECIFIED FOR column­name BECAUSE IT IS DEFINED AS A ROWID (ORDISTINCT TYPE FOR ROWID), ROW CHANGE TIMESTAMP COLUMN, ROW BEGIN COLUMN, ROWEND COLUMN, OR COLUMN OF A PERIOD column­name

­594ATTEMPT TO CREATE A NULLABLE ROWID OR DISTINCT TYPE COLUMN column­name

­601THE NAME (VERSION OR VOLUME SERIAL NUMBER) OF THE OBJECT TO BE DEFINED OR THETARGET OF A RENAME STATEMENT IS IDENTICAL TO THE EXISTING NAME (VERSION ORVOLUME SERIAL NUMBER) object­name OF THE OBJECT TYPE object­type

­602TOO MANY COLUMNS, PERIODS, OR KEY­EXPRESSIONS SPECIFIED IN A CREATE INDEX ORALTER INDEX STATEMENT

­603A UNIQUE INDEX CANNOT BE CREATED BECAUSE THE TABLE CONTAINS ROWS WHICH AREDUPLICATES WITH RESPECT TO THE VALUES OF THE IDENTIFIED COLUMNS AND PERIODS

­604A DATA TYPE DEFINITION SPECIFIES AN INVALID LENGTH, PRECISION, OR SCALE ATTRIBUTE

­607OPERATION OR OPTION operation IS NOT DEFINED FOR THIS OBJECT

­611ONLY LOCKMAX 0 CAN BE SPECIFIED WHEN THE LOCK SIZE OF THE TABLESPACE ISTABLESPACE OR TABLE

­612identifier IS A DUPLICATE NAME

­613THE PRIMARY KEY OR A HASH KEY OR A UNIQUE CONSTRAINT IS TOO LONG OR HAS TOOMANY COLUMNS AND PERIODS

­614THE INDEX CANNOT BE CREATED OR ALTERED, OR THE LENGTH OF A COLUMN CANNOT BECHANGED BECAUSE THE SUM OF THE INTERNAL LENGTHS OF THE COLUMNS FOR THE INDEXIS GREATER THAN THE ALLOWABLE MAXIMUM

­615operation­type IS NOT ALLOWED ON A PACKAGE IN USE

­616obj­type1 obj­name1 CANNOT BE DROPPED BECAUSE IT IS REFERENCED BY obj­type2 obj­name2

­618OPERATION operation IS NOT ALLOWED ON SYSTEM DATABASES

­619OPERATION DISALLOWED BECAUSE THE DATABASE IS NOT STOPPED

­620KEYWORD keyword IN stmt­type STATEMENT IS NOT PERMITTED FOR A space­type SPACE IN THEdatabase­type DATABASE

­621DUPLICATE DBID dbid WAS DETECTED AND PREVIOUSLY ASSIGNED TO database­name

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 17/42

­622FOR MIXED DATA IS INVALID BECAUSE THE MIXED DATA INSTALL OPTION IS NO

­623CLUSTER IS NOT VALID FOR table­name

­624TABLE table­name ALREADY HAS A PRIMARY KEY OR UNIQUE CONSTRAINT WITH SPECIFIEDCOLUMNS AND PERIODS

­625TABLE table­name DOES NOT HAVE AN INDEX TO ENFORCE THE UNIQUENESS OF THE PRIMARYOR UNIQUE KEY

­626THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE THE PAGE SET IS NOT STOPPED

­627THE ALTER STATEMENT IS INVALID BECAUSE THE TABLE SPACE OR INDEX HAS USER­MANAGED DATA SETS

­628THE CLAUSES ARE MUTUALLY EXCLUSIVE

­629SET NULL CANNOT BE SPECIFIED BECAUSE FOREIGN KEY name CANNOT CONTAIN NULLVALUES

­631FOREIGN KEY name IS TOO LONG OR HAS TOO MANY COLUMNS

­632THE TABLE CANNOT BE DEFINED AS A DEPENDENT OF table­name BECAUSE OF DELETE RULERESTRICTIONS

­633THE DELETE RULE MUST BE delete­rule

­634THE DELETE RULE MUST NOT BE CASCADE

­635THE DELETE RULES CANNOT BE DIFFERENT OR CANNOT BE SET NULL

­636RANGES SPECIFIED FOR PARTITION part­num ARE NOT VALID

­637DUPLICATE keyword­name KEYWORD OR CLAUSE

­638TABLE table­name CANNOT BE CREATED BECAUSE COLUMN DEFINITION IS MISSING

­639A NULLABLE COLUMN OF A FOREIGN KEY WITH A DELETE RULE OF SET NULL CANNOT BE ACOLUMN OF THE KEY OF A PARTITIONED INDEX

­640LOCKSIZE ROW CANNOT BE SPECIFIED BECAUSE TABLE IN THIS TABLESPACE HAS TYPE 1INDEX

­643A CHECK CONSTRAINT OR THE VALUE OF AN EXPRESSION FOR A COLUMN OF AN INDEXEXCEEDS THE MAXIMUM ALLOWABLE LENGTH KEY EXPRESSION

­644INVALID VALUE SPECIFIED FOR KEYWORD OR CLAUSE keyword­or­clause IN STATEMENTstatement­type

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 18/42

­646TABLE table­name CANNOT BE CREATED IN SPECIFIED TABLE SPACE table­space­name BECAUSEIT ALREADY CONTAINS A TABLE

­647BUFFERPOOL bp­name FOR IMPLICIT OR EXPLICIT TABLESPACE OR INDEXSPACE name HASNOT BEEN ACTIVATED

­650THE ALTER STATEMENT CANNOT BE EXECUTED, REASON reason­code

­651TABLE DESCRIPTION EXCEEDS MAXIMUM SIZE OF OBJECT DESCRIPTOR.

­652VIOLATION OF INSTALLATION DEFINED EDIT OR VALIDATION PROCEDURE proc­name

­653TABLE table­name IN PARTITIONED TABLE SPACE tspace­name IS NOT AVAILABLE BECAUSE ITSPARTITIONED INDEX HAS NOT BEEN CREATED

­655THE CREATE OR ALTER STOGROUP IS INVALID BECAUSE THE STORAGE GROUP WOULD HAVEBOTH SPECIFIC AND NON­SPECIFIC VOLUME IDS

­658A object­type CANNOT BE DROPPED USING THE statement STATEMENT

­660INDEX index­name CANNOT BE CREATED OR ALTERED ON PARTITIONED TABLE SPACE tspace­name BECAUSE KEY LIMITS ARE NOT SPECIFIED

­661object­type object­name CANNOT BE CREATED ON PARTITIONED TABLE SPACE tspace­nameBECAUSE THE NUMBER OF PARTITION SPECIFICATIONS IS NOT EQUAL TO THE NUMBER OFPARTITIONS OF THE TABLE SPACE

­662A PARTITIONED INDEX CANNOT BE CREATED ON A TABLE SPACE, OR A TABLE SPACE CANNOTBE INDEX­CONTROLLED. TABLE SPACE tspace­name, REASON reason­code

­663THE NUMBER OF KEY LIMIT VALUES IS EITHER ZERO, OR GREATER THAN THE NUMBER OFCOLUMNS IN THE KEY OF INDEX index­name

­665THE PARTITION CLAUSE OF AN ALTER STATEMENT IS OMITTED OR INVALID

­666stmt­verb object CANNOT BE EXECUTED BECAUSE function IS IN PROGRESS

­667THE CLUSTERING INDEX FOR A PARTITIONED TABLE SPACE CANNOT BE EXPLICITLY DROPPED

­668THE COLUMN CANNOT BE ADDED TO THE TABLE BECAUSE THE TABLE HAS AN EDITPROCEDURE DEFINED WITH ROW ATTRIBUTE SENSITIVITY

­669THE OBJECT CANNOT BE EXPLICITLY DROPPED. REASON reason­code

­670THE RECORD LENGTH OF THE TABLE EXCEEDS THE PAGE SIZE LIMIT

­671THE BUFFERPOOL ATTRIBUTE OF THE TABLE SPACE CANNOT BE ALTERED AS SPECIFIEDBECAUSE IT WOULD CHANGE THE PAGE SIZE OF THE TABLE SPACE

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 19/42

­672OPERATION DROP NOT ALLOWED ON TABLE table_name

­676THE PHYSICAL CHARACTERISTICS OF THE INDEX ARE INCOMPATIBLE WITH RESPECT TO THESPECIFIED STATEMENT. THE STATEMENT HAS FAILED. REASON reason­code

­677INSUFFICIENT VIRTUAL STORAGE FOR BUFFERPOOL EXPANSION

­678THE CONSTANT constant SPECIFIED FOR THE INDEX LIMIT KEY MUST CONFORM TO THE DATATYPE data­type OF THE CORRESPONDING COLUMN column­name

­679THE OBJECT name CANNOT BE CREATED BECAUSE A DROP IS PENDING ON THE OBJECT

­680TOO MANY COLUMNS SPECIFIED FOR A TABLE, VIEW OR TABLE FUNCTION

­681COLUMN column­name IN VIOLATION OF INSTALLATION DEFINED FIELD PROCEDURE. RT: return­code, RS: reason­code, MSG: message­token

­682FIELD PROCEDURE procedure­name COULD NOT BE LOADED

­683THE SPECIFICATION FOR COLUMN, DISTINCT TYPE, FUNCTION, OR PROCEDURE data­itemCONTAINS INCOMPATIBLE CLAUSES

­684THE LENGTH OF CONSTANT LIST BEGINNING string IS TOO LONG

­685INVALID FIELD TYPE, column­name

­686COLUMN DEFINED WITH A FIELD PROCEDURE CAN NOT COMPARE WITH ANOTHER COLUMNWITH DIFFERENT FIELD PROCEDURE

­687FIELD TYPES INCOMPARABLE

­688INCORRECT DATA RETURNED FROM FIELD PROCEDURE, column­name, msgno

­689TOO MANY COLUMNS DEFINED FOR A DEPENDENT TABLE

­690THE STATEMENT IS REJECTED BY DATA DEFINITION CONTROL SUPPORT. REASON reason­code

­691THE REQUIRED REGISTRATION TABLE table­name DOES NOT EXIST

­692THE REQUIRED UNIQUE INDEX index­name FOR DDL REGISTRATION TABLE table­name DOES NOTEXIST

­693THE COLUMN column­name IN DDL REGISTRATION TABLE OR INDEX name IS NOT DEFINEDPROPERLY

­694THE SCHEMA STATEMENT CANNOT BE EXECUTED BECAUSE A DROP IS PENDING ON THE DDLREGISTRATION TABLE table­name

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 20/42

­695INVALID VALUE seclabel SPECIFIED FOR SECURITY LABEL COLUMN OF TABLE table­name

­696THE DEFINITION OF TRIGGER trigger­name INCLUDES AN INVALID USE OF CORRELATION NAMEOR TRANSITION TABLE NAME name. REASON CODE=reason­code

­697OLD OR NEW CORRELATION NAMES ARE NOT ALLOWED IN A TRIGGER DEFINED WITH THE FOREACH STATEMENT CLAUSE. OLD_TABLE OR NEW_TABLE NAMES ARE NOT ALLOWED IN ATRIGGER WITH THE BEFORE CLAUSE.

­713THE REPLACEMENT VALUE FOR special­register IS INVALID

­715PROGRAM program­name WITH MARK release­dependency­mark FAILED BECAUSE IT DEPENDS ONFUNCTIONS OF THE RELEASE FROM WHICH FALLBACK HAS OCCURRED

­716PROGRAM program­name PRECOMPILED WITH INCORRECT LEVEL FOR THIS RELEASE

­717bind­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

­718REBIND OF PACKAGE package­name FAILED BECAUSE IBMREQD OF ibmreqd IS INVALID

­719BIND ADD ERROR USING auth­id AUTHORITY PACKAGE package­name ALREADY EXISTS

­720BIND ERROR, ATTEMPTING TO REPLACE PACKAGE = package_name WITH version= version2 BUTTHIS VERSION ALREADY EXISTS

­721BIND ERROR FOR PACKAGE = pkg­id CONTOKEN = contoken'X IS NOT UNIQUE SO IT CANNOT BECREATED

­722bind­type ERROR USING auth­id AUTHORITY PACKAGE package­name DOES NOT EXIST

­723AN ERROR OCCURRED IN A TRIGGERED SQL STATEMENT IN trigger­name. INFORMATIONRETURNED: SQLCODE: sql­code, SQLSTATE: sql­state, MESSAGE TOKENS token­list, SECTIONNUMBER section­number

­724THE ACTIVATION OF THE object­type OBJECT object­name WOULD EXCEED THE MAXIMUM LEVELOF INDIRECT SQL CASCADING

­725THE SPECIAL REGISTER register AT LOCATION location WAS SUPPLIED AN INVALID VALUE

­726BIND ERROR ATTEMPTING TO REPLACE PACKAGE = package­name. THERE ARE ENABLE ORDISABLE ENTRIES CURRENTLY ASSOCIATED WITH THE PACKAGE

­729A STORED PROCEDURE SPECIFYING COMMIT ON RETURN CANNOT BE THE TARGET OF ANESTED CALL STATEMENT

­730THE PARENT OF A TABLE IN A READ­ONLY SHARED DATABASE MUST ALSO BE A TABLE IN AREAD­ONLY SHARED DATABASE

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 21/42

­731USER­DEFINED DATASET dsname MUST BE DEFINED WITH SHAREOPTIONS(1,3)

­732THE DATABASE IS DEFINED ON THIS SUBSYSTEM WITH THE ROSHARE READ ATTRIBUTE BUTTHE TABLE SPACE OR INDEX SPACE HAS NOT BEEN DEFINED ON THE OWNING SUBSYSTEM

­733THE DESCRIPTION OF A TABLE SPACE, INDEX SPACE, OR TABLE IN A ROSHARE READDATABASE MUST BE CONSISTENT WITH ITS DESCRIPTION IN THE OWNER SYSTEM

­734THE ROSHARE ATTRIBUTE OF A DATABASE CANNOT BE ALTERED FROM ROSHARE READ

­735DATABASE dbid CANNOT BE ACCESSED BECAUSE IT IS NO LONGER A SHARED DATABASE

­736INVALID OBID obid SPECIFIED

­737IMPLICIT TABLE SPACE NOT ALLOWED

­739CREATE OR ALTER FUNCTION function­name FAILED BECAUSE FUNCTIONS CANNOT MODIFYDATA WHEN THEY ARE PROCESSED IN PARALLEL.

­740FUNCTION name IS DEFINED WITH THE OPTION MODIFIES SQL DATA WHICH IS NOT VALID INTHE CONTEXT IN WHICH IT WAS INVOKED

­741A database­type DATABASE IS ALREADY DEFINED FOR MEMBER member­name

­742DSNDB07 IS THE IMPLICIT WORK FILE DATABASE

­746THE SQL STATEMENT IN FUNCTION, TRIGGER, OR IN STORED PROCEDURE name VIOLATES THENESTING SQL RESTRICTION

­747TABLE table­name IS NOT AVAILABLE UNTIL THE AUXILIARY TABLES AND INDEXES FOR ITSEXTERNALLY STORED COLUMNS HAVE BEEN CREATED

­748AN INDEX index­name ALREADY EXISTS ON AUXILIARY TABLE table­name

­750THE SOURCE TABLE table­name CANNOT BE RENAMED OR ALTERED BECAUSE IT ISREFERENCED IN AN EXISTING VIEW, MATERIALIZED QUERY TABLE, OR IS A CLONE TABLE, ORHAS A CLONE TABLE DEFINED FOR IT.

­751object­type object­name (SPECIFIC NAME specific name) ATTEMPTED TO EXECUTE AN SQLSTATEMENT sql­statement THAT IS NOT ALLOWED

­752THE CONNECT STATEMENT IS INVALID BECAUSE THE PROCESS IS NOT IN THE CONNECTABLESTATE

­763INVALID TABLE SPACE NAME space­name

­764A LOB TABLE SPACE AND ITS ASSOCIATED BASE TABLE SPACE MUST BE IN THE SAMEDATABASE

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 22/42

­765TABLE IS NOT COMPATIBLE WITH DATABASE

­766THE OBJECT OF A STATEMENT IS A TABLE FOR WHICH THE REQUESTED OPERATION IS NOTPERMITTED

­767MISSING OR INVALID COLUMN SPECIFICATION FOR INDEX index­name

­768AN AUXILIARY TABLE ALREADY EXISTS FOR THE SPECIFIED COLUMN OR PARTITION

­769SPECIFICATION OF CREATE AUX TABLE DOES NOT MATCH THE CHARACTERISTICS OF THEBASE TABLE

­770TABLE table­name CANNOT HAVE A LOB COLUMN UNLESS IT ALSO HAS A ROWID, OR AN XMLCOLUMN UNLESS IT ALSO HAS A DOCID COLUMN

­771INVALID SPECIFICATION OF A ROWID COLUMN

­773CASE NOT FOUND FOR CASE STATEMENT

­775STATEMENT SPECIFIED IN SQL ROUTINE IS NOT ALLOWED WITHIN A COMPOUND STATEMENT.

­776USE OF CURSOR cursor­name IS NOT VALID

­778ENDING LABEL label­name DOES NOT MATCH THE BEGINNING LABEL

­779LABEL label SPECIFIED ON A GOTO, ITERATE, OR LEAVE STATEMENT IS NOT VALID

­780UNDO SPECIFIED FOR A HANDLER

­781CONDITION condition­name IS NOT DEFINED OR THE DEFINITION IS NOT IN SCOPE

­782A CONDITION OR SQLSTATE condition­value SPECIFIED IS NOT VALID

­783SELECT LIST FOR CURSOR cursor­name IN FOR STATEMENT IS NOT VALID. COLUMN column­nameIS NOT UNIQUE

­784CONSTRAINT constraint­name CANNOT BE DROPPED.

­785USE OF SQLCODE OR SQLSTATE IS NOT VALID

­787RESIGNAL STATEMENT ISSUED OUTSIDE OF A HANDLER

­797THE TRIGGER trigger­name IS DEFINED WITH AN UNSUPPORTED TRIGGERED SQL STATEMENT

­798A VALUE CANNOT BE SPECIFIED FOR COLUMN column­name WHICH IS DEFINED AS GENERATEDALWAYS

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 23/42

­802EXCEPTION ERROR exception­type HAS OCCURRED DURING operation­type OPERATION ON data­type DATA, POSITION position­number

­803AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE THE INDEX IN INDEX SPACEindexspace­name CONSTRAINS COLUMNS OF THE TABLE SO NO TWO ROWS CAN CONTAINDUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X record­id

­804AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT PARAMETERS FOR THE SQLSTATEMENT, REASON reason

­805DBRM OR PACKAGE NAME location­name.collection­id.dbrm­name.consistency­token NOT FOUND INPLAN plan­name. REASON reason­code

­807ACCESS DENIED: PACKAGE package­name IS NOT ENABLED FOR ACCESS FROM connection­typeconnection­name

­808THE CONNECT STATEMENT IS NOT CONSISTENT WITH THE FIRST CONNECT STATEMENT

­811THE RESULT OF AN EMBEDDED SELECT STATEMENT OR A SUBSELECT IN THE SET CLAUSE OFAN UPDATE STATEMENT IS A TABLE OF MORE THAN ONE ROW, OR THE RESULT OF ASUBQUERY OF A BASIC PREDICATE IS MORE THAN ONE VALUE

­812THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE A BLANK COLLECTION­ID WASFOUND IN THE CURRENT PACKAGESET SPECIAL REGISTER WHILE TRYING TO FORM AQUALIFIED PACKAGE NAME FOR PROGRAM program­name.consistency­token USING PLAN plan­name

­817THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE STATEMENT WILL RESULT IN APROHIBITED DATA CHANGE OPERATION.

­818THE PRECOMPILER­GENERATED TIMESTAMP x IN THE LOAD MODULE IS DIFFERENT FROM THEBIND TIMESTAMP y BUILT FROM THE DBRM z

­819THE VIEW CANNOT BE PROCESSED BECAUSE THE LENGTH OF ITS PARSE TREE IN THECATALOG IS ZERO

­820THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE catalog­table CONTAINS A VALUETHAT IS NOT VALID IN THIS RELEASE

­822THE SQLDA CONTAINS AN INVALID DATA ADDRESS OR INDICATOR VARIABLE ADDRESS

­840TOO MANY ITEMS RETURNED IN A SELECT OR INSERT LIST

­842A CONNECTION TO location­name ALREADY EXISTS

­843THE SET CONNECTION OR RELEASE STATEMENT MUST SPECIFY AN EXISTING CONNECTION

­845A PREVIOUS VALUE EXPRESSION CANNOT BE USED BEFORE THE NEXT VALUE EXPRESSIONGENERATES A VALUE IN THE CURRENT APPLICATION PROCESS FOR SEQUENCE sequence­name

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 24/42

­846INVALID SPECIFICATION OF AN IDENTITY COLUMN OR SEQUENCE OBJECT object­type object­name. REASON CODE = reason­code

­867INVALID SPECIFICATION OF A ROWID COLUMN

­870THE NUMBER OF HOST VARIABLES IN THE STATEMENT IS NOT EQUAL TO THE NUMBER OFDESCRIPTORS

­872A VALID CCSID HAS NOT YET BEEN SPECIFIED FOR THIS SUBSYSTEM

­873THE STATEMENT REFERENCED DATA ENCODED WITH DIFFERENT ENCODING SCHEMES ORCCSIDS IN AN INVALID CONTEXT

­874THE ENCODING SCHEME SPECIFIED FOR THE object­type MUST BE THE SAME AS THECONTAINING TABLE SPACE OR OTHER PARAMETERS

­875operand CANNOT BE USED WITH THE ASCII DATA REFERENCED

­876object­type CANNOT BE CREATED OR ALTERED, REASON reason­code

­877CCSID ASCII OR CCSID UNICODE IS NOT ALLOWED FOR THIS DATABASE OR TABLE SPACE

­878THE explain­object USED FOR EXPLAIN MUST BE ENCODED IN UNICODE. IT CANNOT BE IN ASCIIOR EBCDIC.

­879CREATE or ALTER STATEMENT FOR object­name CANNOT DEFINE A COLUMN, DISTINCT TYPE,FUNCTION OR STORED PROCEDURE PARAMETER AS MIXED OR GRAPHIC WITH ENCODINGSCHEME encoding­scheme

­880SAVEPOINT savepoint­name DOES NOT EXIST OR IS INVALID IN THIS CONTEXT

­881A SAVEPOINT WITH NAME savepoint­name ALREADY EXISTS, BUT THIS SAVEPOINT NAMECANNOT BE REUSED

­882SAVEPOINT DOES NOT EXIST

­900THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE APPLICATION PROCESS IS NOTCONNECTED TO A SERVER

­901UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT DOES NOT PRECLUDE THESUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS

­902POINTER TO THE ESSENTIAL CONTROL BLOCK (CT/RDA) HAS VALUE 0, REBIND REQUIRED

­904UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON reason­code,TYPE OF RESOURCE resource­type, AND RESOURCE NAME resource­name

­905UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED, RESOURCE NAME =

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 25/42

resource­name LIMIT = limit­amount1 CPU SECONDS (limit­amount2 SERVICE UNITS) DERIVED FROMlimit­source

­906THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THIS FUNCTION IS DISABLED DUE TOA PRIOR ERROR

­908bind­type ERROR USING auth­id AUTHORITY. BIND, REBIND OR AUTO­REBIND OPERATION IS NOTALLOWED

­909THE OBJECT HAS BEEN DELETED OR ALTERED

­910THE SQL STATEMENT CANNOT ACCESS AN OBJECT ON WHICH UNCOMMITTED CHANGES AREPENDING

­911THE 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

­913UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON CODE reason­code,TYPE OF RESOURCE resource­type, AND RESOURCE NAME resource­name

­917BIND PACKAGE FAILED

­918THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE A CONNECTION HAS BEEN LOST

­919A ROLLBACK OPERATION IS REQUIRED

­922AUTHORIZATION FAILURE: error­type ERROR. REASON reason­code

­923CONNECTION NOT ESTABLISHED: DB2 condition REASON reason­code, TYPE resource­type, NAMEresource­name

­924DB2 CONNECTION INTERNAL ERROR, function­code,return­code,reason­code

­925COMMIT NOT VALID IN IMS, CICS OR RRSAF ENVIRONMENT

­926ROLLBACK NOT VALID IN IMS, CICS OR RRSAF ENVIRONMENT

­927THE LANGUAGE INTERFACE (LI) WAS CALLED WHEN THE CONNECTING ENVIRONMENT WASNOT ESTABLISHED. THE PROGRAM SHOULD BE INVOKED UNDER THE DSN COMMAND

­929FAILURE IN A DATA CAPTURE EXIT: token

­939ROLLBACK REQUIRED DUE TO UNREQUESTED ROLLBACK OF A REMOTE SERVER

­947THE SQL STATEMENT FAILED BECAUSE IT WILL CHANGE A TABLE DEFINED WITH DATACAPTURE CHANGES, BUT THE DATA CANNOT BE PROPAGATED

­948DISTRIBUTED OPERATION IS INVALID

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 26/42

­950THE LOCATION NAME SPECIFIED IN THE CONNECT STATEMENT IS INVALID OR NOT LISTED INTHE COMMUNICATIONS DATABASE

­951OBJECT object­name OBJECT TYPE object­type IS IN USE AND CANNOT BE THE TARGET OF THESPECIFIED ALTER STATEMENT

­952PROCESSING WAS INTERRUPTED BY A CANCEL REQUEST FROM A CLIENT PROGRAM

­981THE SQL STATEMENT FAILED BECAUSE THE RRSAF CONNECTION IS NOT IN A STATE THATALLOWS SQL OPERATIONS, REASON reason­code.

­989AFTER TRIGGER trigger­name ATTEMPTED TO MODIFY A ROW IN TABLE table­name THAT WASMODIFIED BY AN SQL DATA CHANGE STATEMENT WITHIN A FROM CLAUSE

­991CALL ATTACH WAS UNABLE TO ESTABLISH AN IMPLICIT CONNECT OR OPEN TO DB2. RC1= rc1RC2= rc2

­992PACKAGE package­name CANNOT BE EXECUTED OR DEPLOYED ON LOCATION location­name

­1403THE USERNAME AND/OR PASSWORD SUPPLIED IS INCORRECT

­1760CREATE PROCEDURE FOR procedure­name MUST HAVE VALID LANGUAGE AND EXTERNALCLAUSES

­2001THE NUMBER OF HOST VARIABLE PARAMETERS FOR A STORED PROCEDURE IS NOT EQUALTO THE NUMBER OF EXPECTED HOST VARIABLE PARAMETERS. ACTUAL NUMBER sqldanum,EXPECTED NUMBER opnum

­4302JAVA STORED PROCEDURE OR USER­DEFINED FUNCTION routine­name (SPECIFIC NAME specific­name) HAS EXITED WITH AN EXCEPTION exception­string

­4700ATTEMPT TO USE NEW FUNCTION BEFORE NEW FUNCTION MODE

­4701THE NUMBER OF PARTITIONS, OR THE COMBINATION OF THE NUMBER OF TABLE SPACEPARTITIONS AND THE CORRESPONDING LENGTH OF THE PARTITIONING LIMIT KEY EXCEEDSTHE SYSTEM LIMIT; OR THE COMBINATION OF THE NUMBER OF TABLE SPACE PARTITIONSEXCEEDS THE MAXPARTITIONS FOR PARTITION BY GROWTH TABLE SPACE.

­4704AN UNSUPPORTED DATA TYPE WAS ENCOUNTERED AS AN INCLUDE COLUMN

­4705option SPECIFIED ON ALTER STATEMENT FOR routine­name (routine­type) IS NOT VALID

­4706ALTER STATEMENT FOR AN SQL ROUTINE CANNOT BE PROCESSED BECAUSE THE OPTIONSCURRENTLY IN EFFECT (ENVID current­envid) ARE NOT THE SAME AS THE ONES THAT WERE INEFFECT (ENVID defined­envid) WHEN THE ROUTINE OR VERSION WAS FIRST DEFINED

­4709EXPLAIN MONITORED STMTS FAILED WITH REASON CODE = yyyyy

­4710EXCHANGE DATA STATEMENT SPECIFIED table1 and table2 BUT THE TABLES DO NOT HAVE A

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 27/42

DEFINED CLONE RELATIONSHIP

­4727SYSTEM PARAMETER system­parameter VALUE parameter­value IS INCONSISTENT WITH CLAUSEclause SPECIFIED ON statement­name STATEMENT.

­4730INVALID SPECIFICATION OF XML COLUMN table­name.column­name IS NOT DEFINED IN THE XMLVERSIONING FORMAT, REASON reason­code

­4731THE NATIVE SQL ROUTINE STATEMENT FOR PACKAGE location­name.collection­id.program­name.consistency­token STATEMENT NUMBER statement­number CANNOT BE PROCESSED.

­4732THE MAXIMUM NUMBER OF ALTERS ALLOWED HAS BEEN EXCEEDED FOR object­type

­4733THE ALTER TABLE STATEMENT CANNOT BE EXECUTED BECAUSE COLUMN column­name ISMIXED DATA, OR THE DATA TYPE OR LENGTH SPECIFIED DOES NOT AGREE WITH THEEXISTING DATA TYPE OR LENGTH

­4734THE LOAD MODULE FOR THE PROCEDURE ASSUMES A PARAMETER VARCHAR OPTION THAT ISNOT CONSISTENT WITH THE OPTION SPECIFIED ON THE CREATE PROCEDURE STATEMENTFOR procedure­name

­4735INVALID TABLE REFERENCE FOR TABLE LOCATOR

­4736A PERIOD SPECIFICATION OR PERIOD CLAUSE IS NOT SUPPORTED AS SPECIFIED FOR OBJECTobject­name. REASON CODE = reason­code.

­4737STATEMENT statement IS NOT ALLOWED WHEN USING A TRUSTED CONNECTION

­4738TABLE table­name CANNOT BE DEFINED AS SPECIFIED IN THE statement STATEMENT IN ACOMMON CRITERIA ENVIRONMENT

­4739ENVIRONMENT SETTINGS (IDENTIFIED BY envid1) USED BY object­name ARE NOT THE SAME ASTHE ONES THAT WERE IN EFFECT (IDENTIFIED BYenvid2) WHEN OTHER COLUMN MASKS ANDROW PERMISSIONS WERE DEFINED FOR TABLE table­name

­4742THE STATEMENT CANNOT BE EXECUTED BY DB2 OR IN THE ACCELERATOR (REASON reason­code)

­4746THE STATEMENT CANNOT BE PROCESSED FOR AN ACCELERATED QUERY. REASON CODEreason­code.

­4747THE CREATE OR ALTER TABLE STATEMENT FAILED BECAUSE SOME FUNCTIONALITY WASSPECIFIED IN THE TABLE DEFINITION THAT IS NOT SUPPORTED WITH THE TABLE TYPE.UNSUPPORTED FUNCTIONALITY:functionality­keyword.

­4751bind­type FOR PACKAGE = package­name FAILED BECAUSE OF THE USE OF keyword. ONE ORMORE STATEMENTS WERE NOT SUCCESSFULLY PROCESSED.

­5001TABLE table­name IS NOT VALID

­5012

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 28/42

HOST VARIABLE host­variable IS NOT EXACT NUMERIC WITH SCALE ZERO

­7008object­name NOT VALID FOR OPERATION (reason­code)

­16000AN XQUERY EXPRESSION CANNOT BE PROCESSED BECAUSE THE context­componentCOMPONENT OF THE STATIC CONTEXT HAS NOT BEEN ASSIGNED. ERROR QNAME =err:XPST0001

­16001AN XQUERY EXPRESSION STARTING WITH TOKEN token CANNOT BE PROCESSED BECAUSETHE FOCUS COMPONENT OF THE DYNAMIC CONTEXT HAS NOT BEEN ASSIGNED. ERRORQNAME = err:XPDY0002

­16002AN XQUERY EXPRESSION HAS AN UNEXPECTED TOKEN token FOLLOWING text. EXPECTEDTOKENS MAY INCLUDE: token­list. ERROR QNAME= ERR:XPST0003

­16003AN EXPRESSION OF DATA TYPE value­type CANNOT BE USED WHEN THE DATA TYPE expected­type IS EXPECTED IN THE CONTEXT. ERROR QNAME= err:XPTY0004

­16005AN XQUERY EXPRESSION REFERENCES AN ELEMENT NAME, ATTRIBUTE NAME, TYPE NAME,FUNCTION NAME, NAMESPACE PREFIX, OR VARIABLE NAME undefined­name THAT IS NOTDEFINED WITHIN THE STATIC CONTEXT. ERROR QNAME= ERR:XPST0008

­16007­16007 THE XQUERY PATH EXPRESSION REFERENCES AN AXIS axis­type THAT IS NOTSUPPORTED. ERROR QNAME = err:XQST0010

­16009AN XQUERY FUNCTION NAMED function­name WITH number­of­parms PARAMETERS IS NOTDEFINED IN THE STATIC CONTEXT. ERROR QNAME= err:XPST0017

­16011THE RESULT OF AN INTERMEDIATE STEP EXPRESSION IN AN XQUERY PATH EXPRESSIONCONTAINS AN ATOMIC VALUE. ERROR QNAME = err:XPTY0019

­16012THE CONTEXT ITEM IN AN AXIS STEP MUST BE A NODE. ERROR QNAME = err:XPTY0020

­16015AN ELEMENT CONSTRUCTOR CONTAINS AN ATTRIBUTE NODE NAMED attribute­name THATFOLLOWS AN XQUERY NODE THAT IS NOT AN ATTRIBUTE NODE. ERROR QNAME = err:error­name

­16016THE ATTRIBUTE NAME attribute­name CANNOT BE USED MORE THAN ONCE IN AN ELEMENTCONSTRUCTOR. ERROR QNAME = err:XQTY0025

­16020THE CONTEXT NODE IN A PATH EXPRESSION THAT BEGINS WITH AN INITIAL "/" OR "//" DOESNOT HAVE AN XQUERY DOCUMENT NODE ROOT. ERROR QNAME = err:XPDY0050

­16022OPERANDS OF TYPES xquery­data­types ARE NOT VALID FOR OPERATOR operator­name . ERRORQNAME = err:XPTY0004

­16023THE XQUERY PROLOG CANNOT CONTAIN MULTIPLE DECLARATIONS FOR THE SAMENAMESPACE PREFIX ns­prefix. ERROR QNAME = err:XQST0033

­16024THE NAMESPACE PREFIX prefix­name CANNOT BE REDECLARED OR CANNOT BE BOUND TO THESPECIFIED URI. ERROR QNAME = err:XQST0070

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 29/42

­16026THE NAME attribute­name IS USED FOR MORE THAN ONE ATTRIBUTE IN THE CONSTRUCTOR FORTHE ELEMENT NAMED element­name. ERROR QNAME=err:XQST0040

­16029TWO OR MORE NAMESPACES WITHIN THE SAME XQUERY ELEMENT CONSTRUCTOR USE THESAME NAMESPACE PREFIX prefix­name. ERROR QNAME=err:XQST0071

­16031XQUERY LANGUAGE FEATURE USING SYNTAX string IS NOT SUPPORTED

­16032THE STRING string IS NOT A VALID URI. ERROR QNAME = err:XQST0046

­16033THE TARGET DATA TYPE type­name OF A CASTABLE EXPRESSION IS NOT AN ATOMIC DATATYPE DEFINED FOR THE IN­SCOPE XML SCHEMA TYPES OR IS A DATA TYPE THAT CANNOT BEUSED IN A CASTABLE EXPRESSION. ERROR QNAME=err:XPST0080

­16036THE URI THAT IS SPECIFIED IN A NAMESPACE DECLARATION CANNOT BE A ZERO­LENGTHSTRING

­16038THE ARGUMENTS OF FN:DATETIME HAVE DIFFERENT TIMEZONES. ERRORQNAME=ERR:FORG0008.

­16041AN IMPLICIT OR EXPLICIT INVOCATION OF THE fn:boolean FUNCTION IN THE XQUERYEXPRESSION COULD NOT COMPUTE THE EFFECTIVE BOOLEAN VALUE OF THE SEQUENCE.ERROR QNAME=err:FORG0006

­16046A NUMERIC XQUERY EXPRESSION ATTEMPTED TO DIVIDE BY ZERO. ERROR QNAME =err:FOAR0001

­16047AN XQUERY EXPRESSION RESULTED IN ARITHMETIC OVERFLOW OR UNDERFLOW. ERRORQNAME= err:FOAR0002

­16048AN XQUERY PROLOG CANNOT CONTAIN MORE THAN ONE declaration­type DECLARATION. ERRORQNAME = error­qname

­16049THE LEXICAL VALUE value IS NOT VALID FOR THE type­name DATA TYPE IN THE FUNCTION ORCAST. ERROR QNAME= err:FOCA0002

­16051THE VALUE value OF DATA TYPE source­type IS OUT OF RANGE FOR AN IMPLICIT OR EXPLICITCAST TO TARGET DATA TYPE target­type. ERROR QNAME = err:error­qname

­16052NAN CANNOT BE USED AS A FLOAT OR DOUBLE VALUE IN A DATETIME OPERATION. ERRORQNAME=ERR:FOCA0005.

­16055AN ARITHMETIC OPERATION INVOLVING A DATETIME VALUE RESULTED IN OVERFLOW. ERRORQNAME=ERR:FODT0001.

­16056AN ARITHMETIC OPERATION INVOLVING A DURATION VALUE RESULTED IN OVERFLOW. ERRORQNAME=ERR:FODT0002.

­16057A TIMEZONE VALUE IS NOT VALID. ERROR QNAME=ERR:FODT0003.

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 30/42

­16061THE VALUE value CANNOT BE CONSTRUCTED AS, OR CAST (USING AN IMPLICIT OR EXPLICITCAST) TO THE DATA TYPE data­type. ERROR QNAME = err:FORG0001

­16065AN EMPTY SEQUENCE CANNOT BE CAST TO THE DATA TYPE data­type, ERROR QNAME =err:FORG0006

­16066THE ARGUMENT PASSED TO THE AGGREGATE FUNCTION function­name IS NOT VALID. ERRORQNAME = err:FORG0006

­16067THE FLAGS ARGUMENT VALUE PASSED TO THE FUNCTION function­name IS NOT VALID. ERRORQNAME= err:FORX0001

­16068THE REGULAR EXPRESSION ARGUMENT VALUE PASSED TO THE FUNCTION function­name ISNOT VALID. ERROR QNAME= err:FORX0002

­16069A REGULAR EXPRESSION ARGUMENT value PASSED TO THE FUNCTION function­name MATCHESA ZERO­LENGTH STRING. ERROR QNAME= err:FORX0003

­16075THE SEQUENCE TO BE SERIALIZED CONTAINS AN ITEM THAT IS AN ATTRIBUTE NODE. ERRORQNAME = err:SENR0001

­16080AN XQUERY EXPRESSION INCLUDES ONE OR MORE expression­type EXPRESSIONS OUTSIDE THEXQUERY­UPDATE­CONSTANT OF AN XMLMODIFY FUNCTION. ERROR QNAME=err:XUST0001.

­16081THE XQUERY­UPDATE­CONSTANT IN THE XMLMODIFY FUNCTION IS NOT AN UPDATINGEXPRESSION OR AN EMPTY SEQUENCE EXPRESSION. ERROR QNAME=err:XUST0002.

­16085THE TARGET NODE OF AN XQUERY expression­type EXPRESSION IS NOT VALID. ERRORQNAME=err:error­name.

­16086THE REPLACEMENT SEQUENCE OF A REPLACE EXPRESSION CONTAINS INVALID NODES FORTHE SPECIFIED TARGET NODE. ERROR QNAME=err:error­name.

­16087THE RESULT OF APPLYING THE UPDATING EXPRESSIONS IN THE XMLMODIFY FUNCTION ISNOT A VALID INSTANCE OF THE XQUERY AND XPATH DATA MODEL. ADDITIONAL INFORMATION:information­1, information­2. ERROR QNAME=err:XUDY0021.

­16088AN expression­type EXPRESSION HAS A BINDING OF A NAMESPACE PREFIX prefix­string TONAMESPACE URI uri­string, INTRODUCED TO AN ELEMENT NAMED element­name, THATCONFLICTS WITH AN EXISTING NAMESPACE BINDING OF THE SAME PREFIX TO A DIFFERENTURI IN THE IN­SCOPE NAMESPACES OF THAT ELEMENT NODE. ERROR QNAME=err:XUDY0023.

­16089AN expression­type EXPRESSION AND POSSIBLY OTHER UPDATING EXPRESSIONS IN ANXMLMODIFY FUNCTION INTRODUCE CONFLICTING NAMESPACE BINDINGS INTO AN ELEMENTNAMED element­name. THE PREFIX prefix­string IS BOUND TO uri­string WHILE ANOTHER BINDINGOF THE SAME PREFIX USES A DIFFERENT NAMESPACE URI. ERROR QNAME=err:XUDY0024.

­16246INCOMPLETE ANNOTATION MAPPING AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri.REASON CODE = reason­code.

­16247SOURCE XML TYPE source­data­type CANNOT BE MAPPED TO TARGET SQL TYPE target­data­type

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 31/42

IN THE ANNOTATION AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri

­16248UNKNOWN ANNOTATION annotation­name AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri

­16249THE db2­xdb:expression ANNOTATION expression AT OR NEAR LINE lineno IN XML SCHEMADOCUMENT uri IS TOO LONG.

­16250THE db2­xdb:defaultSQLSchema WITH VALUE schema­name AT OR NEAR LINE lineno IN XMLSCHEMA DOCUMENT uri CONFLICTS WITH ANOTHER db2­xdb:defaultSQLSchema SPECIFIED INONE OF THE XML SCHEMA DOCUMENTS WITHIN THE SAME XML SCHEMA.

­16251DUPLICATE ANNOTATION DEFINED FOR object­name AT OR NEAR location IN XML SCHEMADOCUMENT uri

­16252THE db2­xdb:rowSet NAME rowset­name SPECIFIED AT OR NEAR LINE lineno IN THE XML SCHEMADOCUMENT uri IS ALREADY ASSOCIATED WITH ANOTHER TABLE

­16253THE db2­xdb:condition ANNOTATION condition AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENTuri IS TOO LONG.

­16254A db2­xdb:locationPath locationpath AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENT uri IS NOTVALID WITH REASON CODE reason­code.

­16255A db2­xdb:rowSet VALUE rowset­name USED AT OR NEAR LINE lineno IN XML SCHEMA DOCUMENTuri CONFLICTS WITH A db2­xdb:table ANNOTATION WITH THE SAME NAME.

­16257XML SCHEMA FEATURE feature SPECIFIED IS NOT SUPPORTED FOR DECOMPOSITION.

­16258THE XML SCHEMA CONTAINS A RECURSIVE ELEMENT WHICH IS AN UNSUPPORTED FEATUREFOR DECOMPOSITION. THE RECURSIVE ELEMENT IS IDENTIFIED AS elementnamespace :elementname OF TYPE typenamespace : typename.

­16259INVALID MANY­TO­MANY MAPPINGS DETECTED IN XML SCHEMA DOCUMENT uri1 NEAR LINElineno1 AND IN XML SCHEMA DOCUMENT uri2 NEAR LINE lineno2.

­16260XML SCHEMA ANNOTATIONS INCLUDE NO MAPPINGS TO ANY COLUMN OF ANY TABLE.

­16262THE ANNOTATED XML SCHEMA HAS NO COLUMNS MAPPED FOR ROWSET rowsetname.

­16265THE XML DOCUMENT CANNOT BE DECOMPOSED USING XML SCHEMA xsrobject­name WHICH ISNOT ENABLED OR IS INOPERATIVE FOR DECOMPOSITION.

­16266AN SQL ERROR OCCURRED DURING DECOMPOSITION OF DOCUMENT docid WHILE ATTEMPTINGTO INSERT DATA. INFORMATION RETURNED FOR THE ERROR INCLUDES SQLCODE sqlcode,SQLSTATE sqlstate, AND MESSAGE TOKENS token­list.

­20003GBPCACHE NONE CANNOT BE SPECIFIED FOR TABLESPACE OR INDEX IN GRECP

­200048K or 16K BUFFERPOOL PAGESIZE INVALID FOR A WORKFILE OBJECT

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 32/42

­20005THE INTERNAL ID LIMIT OF limit HAS BEEN EXCEEDED FOR OBJECT TYPE object­type

­20008ATTEMPT TO USE AN UNSUPPORTED FEATURE ON OBJECT object­name. REASON CODE: reason­code

­20016THE VALUE OF THE INLINE LENGTH ASSOCIATED WITH object­name IS TOO BIG OR THE INLINELENGTH CLAUSE IS NOT ALLOWED IN THE CONTEXT.

­20019THE RESULT TYPE RETURNED FROM THE FUNCTION BODY CANNOT BE ASSIGNED TO THEDATA TYPE DEFINED IN THE RETURNS CLAUSE

­20046THE SELECTIVITY CLAUSE FOLLOWING predicate­string CAN ONLY SPECIFIED FOR A SPATIALPREDICATE FUNCTION.

­20058THE FULLSELECT SPECIFIED FOR MATERIALIZED QUERY TABLE table­name IS NOT VALID.

­20060UNSUPPORTED DATA TYPE data­type ENCOUNTERED IN SQL object­type object­name

­20070AUXILIARY TABLE table­name CANNOT BE CREATED BECAUSE COLUMN column­name IS NOT ALOB COLUMN

­20071WLM ENVIRONMENT NAME MUST BE SPECIFIED function­name

­20072bind­type bind­subtype ERROR USING authorization­id AUTHORITY. OPERATION IS NOT ALLOWED ONA package­type PACKAGE package­name

­20073THE FUNCTION function­name CANNOT BE ALTERED BECAUSE IT IS REFERENCED IN EXISTINGVIEW OR MATERIALIZED QUERY TABLE DEFINITIONS

­20074THE OBJECT object­name CANNOT BE CREATED BECAUSE THE FIRST THREE CHARACTERS ARERESERVED FOR SYSTEM OBJECTS

­20091A VIEW NAME WAS SPECIFIED AFTER LIKE IN ADDITION TO THE INCLUDING IDENTITY COLUMNATTRIBUTES CLAUSE

­20092A TABLE OR VIEW WAS SPECIFIED IN THE LIKE CLAUSE, BUT THE OBJECT CANNOT BE USED INTHIS CONTEXT

­20093THE 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.

­20094THE COLUMN column­name IS A GENERATED COLUMN AND CANNOT BE USED IN THE BEFORETRIGGER trigger­name.

­20100AN ERROR OCCURRED WHEN BINDING A TRIGGERED SQL STATEMENT. INFORMATIONRETURNED: SECTION NUMBER : section­number SQLCODE sqlerror, SQLSTATE sqlstate, ANDMESSAGE TOKENS token­list

­20101

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 33/42

THE FUNCTION function­name FAILED WITH REASON reason­code

­20102CREATE OR ALTER STATEMENT FOR ROUTINE routine­name SPECIFIED THE option OPTIONWHICH IS NOT ALLOWED FOR THE TYPE OF ROUTINE

­20104AN ATTEMPT TO ALTER A CCSID FROM from­ccsid TO to­ccsid FAILED

­20106THE CCSID FOR THE TABLE SPACE OR DATABASE CANNOT BE CHANGED BECAUSE THE TABLESPACE OR DATABASE ALREADY CONTAINS A TABLE THAT IS REFERENCED IN EXISTING VIEW,OR MATERIALIZED QUERY TABLE DEFINITIONS OR AN EXTENDED INDEX

­20107HOST VARIABLE OR PARAMETER NUMBER position­number CANNOT BE USED AS SPECIFIEDBECAUSE REASON reason

­20108A RESULT SET CONTAINS AN UNSUPPORTED DATA TYPE IN POSITION NUMBER position­numberFOR CURSOR cursor­name OPENED BY STORED PROCEDURE procedure­name

­20110CANNOT IMPLICITLY CONNECT TO A REMOTE SITE WITH A SAVEPOINT OUTSTANDING

­20111CANNOT ISSUE SAVEPOINT, RELEASE SAVEPOINT, ROLLBACK TO SAVEPOINT FROM ATRIGGER, FROM A USER­DEFINED FUNCTION, OR FROM A GLOBAL TRANSACTION

­20117A WINDOW SPECIFICATION FOR AN OLAP SPECIFICATION IS NOT VALID. REASON CODE =reason­code.

­20120AN SQL TABLE FUNCTION MUST RETURN A TABLE RESULT.

­20123CALL TO STORED PROCEDURE procedure­name FAILED BECAUSE THE RESULT SET RETURNEDFOR CURSOR cursor­name IS SCROLLABLE, BUT THE CURSOR IS NOT POSITIONED BEFORE THEFIRST ROW

­20124OPEN CURSOR cursor FAILED BECAUSE THE CURSOR IS SCROLLABLE BUT THE CLIENT DOESNOT SUPPORT THIS

­20125CALL TO STORED PROCEDURE procedure­name FAILED BECAUSE THE RESULT SET FOR CURSORcursor­name IS SCROLLABLE, BUT THE CLIENT DOES NOT SUPPORT THIS, REASON reason­code.

­20127VALUE SPECIFIED ON FETCH STATEMENT FOR ABSOLUTE OR RELATIVE IS TOO LARGE FORDRDA

­20129LOCAL SPECIAL REGISTER IS NOT VALID AS USED

­20142SEQUENCE sequence­name CANNOT BE USED AS SPECIFIED

­20143THE ENCRYPTION OR DECRYPTION FUNCTION FAILED, BECAUSE THE ENCRYPTION PASSWORDVALUE IS NOT SET

­20144THE ENCRYPTION IS INVALID BECAUSE THE LENGTH OF THE PASSWORD WAS LESS THAN 6BYTES OR GREATER THAN 127 BYTES

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 34/42

­20146THE DECRYPTION FAILED. THE DATA IS NOT ENCRYPTED

­20147THE ENCRYPTION FUNCTION FAILED. MULTIPLE PASS ENCRYPTION IS NOT SUPPORTED

­20148A RETURN STATEMENT DOES NOT EXIST OR WAS NOT INVOKED DURING THE EXECUTION OFROUTINE routine­name WITH SPECIFIC NAME specific­name.

­20163HEXADECIMAL CONSTANT GX IS NOT ALLOWED

­20165AN SQL DATA CHANGE STATEMENT WITHIN A FROM CLAUSE IS NOT ALLOWED IN THECONTEXT IN WHICH IT WAS SPECIFIED

­20166AN SQL DATA CHANGE STATEMENT WITHIN A SELECT SPECIFIED A VIEW view­name WHICH ISNOT A SYMMETRIC VIEW OR COULD NOT HAVE BEEN DEFINED AS A SYMMETRIC VIEW

­20177SET DATA TYPE CLAUSE ON ALTER TABLE SPECIFIED FLOATING POINT, BUT THIS CHANGE ISDISALLOWED

­20178VIEW view­name ALREADY HAS AN INSTEAD OF operation TRIGGER DEFINED

­20179THE INSTEAD OF TRIGGER CANNOT BE CREATED BECAUSE THE VIEW view­name IS DEFINEDUSING THE WITH CHECK OPTION

­20180COLUMN column­name IN TABLE table­name CANNOT BE ALTERED AS SPECIFIED

­20181COLUMN CANNOT BE ADDED TO INDEX index­name

­20182PARTITIONING CLAUSE clause ON stmt­type STATEMENT FOR index­name IS NOT VALID

­20183THE PARTITIONED, ADD PARTITION, ADD PARTITIONING KEY, ALTER PARTITION, ROTATEPARTITION, OR PARTITION BY RANGE CLAUSE SPECIFIED ON CREATE OR ALTER FOR table­name IS NOT VALID

­20185CURSOR cursor­name IS NOT DEFINED TO ACCESS ROWSETS, BUT A CLAUSE WAS SPECIFIEDTHAT IS VALID ONLY WITH ROWSET ACCESS

­20186A CLAUSE SPECIFIED FOR THE DYNAMIC SQL STATEMENT BEING PROCESSED IS NOT VALID

­20200THE INSTALL OR REPLACE OF jar­id WITH URL url FAILED DUE TO REASON reason­code­(reason­string).

­20201THE INSTALL, REPLACE, REMOVE, OR ALTER OF jar­name FAILED DUE TO REASON reason­code­(reason­string)

­20202THE REMOVE OF jar­name FAILED AS class IS IN USE

­20203USER­DEFINED FUNCTION OR PROCEDURE name HAS A JAVA METHOD WITH AN INVALIDSIGNATURE. THE ERROR IS AT OR NEAR PARAMETER number. THE SIGNATURE IS signature.

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 35/42

­20204THE USER­DEFINED FUNCTION OR PROCEDURE routine­name WAS UNABLE TO MAP TO A SINGLEJAVA METHOD

­20207THE INSTALL OR REMOVE OF jar­name SPECIFIED THE USE OF A DEPLOYMENT DESCRIPTOR.

­20210THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT WAS PRECOMPILED AT A LEVELTHAT IS INCOMPATIBLE WITH THE CURRENT VALUE OF THE ENCODING BIND OPTION ORSPECIAL REGISTER

­20211THE SPECIFICATION ORDER BY OR FETCH FIRST N ROWS ONLY IS INVALID

­20212USER­DEFINED ROUTINE name ENCOUNTERED AN EXCEPTION ATTEMPTING TO LOAD JAVACLASS class­name FROM JAR jar­name. ORIGINAL EXCEPTION: exception­string

­20213STORED PROCEDURE procedure­name HAS RETURNED A DYNAMIC RESULT SET, PARAMETERnumber, THAT IS NOT VALID

­20223THE ENCRYPT_TDES OR DECRYPT FUNCTION FAILED. ENCRYPTION FACILITY NOT AVAILABLEreturn­code, reason­code

­20224ENCRYPTED DATA THAT WAS ORIGINALLY A BINARY STRING CANNOT BE DECRYPTED TO ACHARACTER STRING

­20227REQUIRED CLAUSE IS MISSING FOR ARGUMENT number OF expression

­20228A STACKED DIAGNOSTICS AREA IS NOT AVAILABLE

­20232CHARACTER 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

­20235THE COLUMN column­name CANNOT BE ADDED OR ALTERED BECAUSE table­name IS AMATERIALIZED QUERY TABLE

­20240INVALID SPECIFICATION OF A SECURITY LABEL COLUMN table­name.column­name REASON CODEreason­code

­20248ATTEMPTED TO EXPLAIN ALL CACHED STATEMENTS OR A CACHED STATEMENT WITH STMTIDOR STMTTOKEN ID­token BUT THE REQUIRED EXPLAIN INFORMATION IS NOT ACCESSIBLE.REASON reason­code

­20249THE PACKAGE package­name NEEDS TO BE REBOUND IN ORDER TO BE SUCCESSFULLYEXECUTED (required­maintenance)

­20252DIAGNOSTICS AREA FULL. NO MORE ERRORS CAN BE RECORDED FOR THE NOT ATOMICSTATEMENT

­20257FINAL TABLE IS NOT VALID WHEN THE TARGET VIEW view­name OF THE SQL DATA CHANGESTATEMENT IN A FULLSELECT HAS AN INSTEAD OF TRIGGER DEFINED

­20258

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 36/42

INVALID USE OF INPUT SEQUENCE ORDERING

­20260THE ASSIGNMENT CLAUSE OF THE UPDATE OPERATION AND THE VALUES CLAUSE OF THEINSERT OPERATION MUST SPECIFY AT LEAST ONE COLUMN THAT IS NOT AN INCLUDE COLUMN

­20264FOR TABLE table­name, primary­auth­id WITH SECURITY LABEL primary­auth­id­seclabel IS NOTAUTHORIZED TO PERFORM operation ON A ROW WITH SECURITY LABEL row­seclabel. THERECORD IDENTIFIER (RID) OF THIS ROW IS rid­number.

­20265SECURITY LABEL IS reason FOR primary­auth­id

­20266ALTER VIEW FOR view­name FAILED

­20275The XML NAME xml­name IS NOT VALID. REASON CODE = reason­code

­20281primary­auth­id DOES NOT HAVE THE MLS WRITE­DOWN PRIVILEGE

­20283A DYNAMIC CREATE STATEMENT CANNOT BE PROCESSED WHEN THE VALUE OF CURRENTSCHEMA DIFFERS FROM CURRENT SQLID

­20286DB2 CONVERTED STRING token­type tokenFROM from­ccsid TO to­ccsid, AND RESULTED INSUBSTITUTION CHARACTERS

­20289INVALID STRING UNIT unit SPECIFIED FOR FUNCTION function­name

­20295THE EXECUTION OF A BUILT IN FUNCTION function RESULTED IN AN ERROR REASON CODEreason­code

­20300THE LIST OF COLUMNS SPECIFIED FOR THE clause CLAUSE IS NOT ALLOWED IN COMBINATIONWITH THE LIST OF COLUMNS FOR THE PARTITIONING KEY FOR THE TABLE.

­20304INVALID INDEX DEFINITION INVOLVING AN XMLPATTERN CLAUSE OR A COLUMN OF DATA TYPEXML. REASON CODE = reason­code

­20305AN XML VALUE CANNOT BE INSERTED OR UPDATED BECAUSE OF AN ERROR DETECTED WHENINSERTING OR UPDATING THE INDEX IDENTIFIED BY index­id ON TABLE table­name. REASONCODE = reason­code

­20306AN INDEX ON AN XML COLUMN CANNOT BE CREATED BECAUSE OF AN ERROR DETECTEDWHEN INSERTING THE XML VALUES INTO THE INDEX. REASON CODE = reason­code

­20310THE REMOVE OF jar­name1 FAILED, AS IT IS IN USE BY jar­name2

­20311THE VALUE PROVIDED FOR THE NEW JAVA PATH IS ILLEGAL

­20312THE ALTER OF JAR jar­id FAILED BECAUSE THE SPECIFIED PATH REFERENCES ITSELF

­20313DEBUG MODE OPTION FOR ROUTINE routine­name CANNOT BE CHANGED

­20314

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 37/42

THE PARAMETER LIST (OR AN OPTION) DOES NOT MATCH THE PARAMETER LIST (OR OPTION)FOR ALL OTHER VERSIONS OF ROUTINE routine­name

­20315THE CURRENTLY ACTIVE VERSION FOR ROUTINE routine­name (routine­type) CANNOT BEDROPPED

­20327THE DEPTH OF AN XML DOCUMENT EXCEEDS THE LIMIT OF 128 LEVELS

­20328THE DOCUMENT WITH TARGET NAMESPACE namespace AND SCHEMA LOCATION location HASALREADY BEEN ADDED FOR THE XML SCHEMA IDENTIFIED BY schema name

­20329THE COMPLETION CHECK FOR THE XML SCHEMA FAILED BECAUSE ONE OR MORE XMLSCHEMA DOCUMENTS IS MISSING. ONE MISSING XML SCHEMA DOCUMENT IS IDENTIFIED BYuri­type AS uri

­20330THE object­type IDENTIFIED BY XML uri­type1 uri1 AND XML uri­type2 uri2 IS NOT FOUND IN THE XMLSCHEMA REPOSITORY

­20331THE XML COMMENT VALUE string IS NOT VALID

­20332THE XML PROCESSING INSTRUCTION VALUE string IS NOT VALID

­20335MORE THAN ONE xsrobject­type EXISTS IDENTIFIED BY XML uri­type1 uri1 AND uri­type2 uri2 EXISTSIN THE XML SCHEMA REPOSITORY.

­20338THE DATA TYPE OF EITHER THE SOURCE OR TARGET OPERAND OF AN XMLCASTSPECIFICATION MUST BE XML

­20339XML SCHEMA name IS NOT IN THE CORRECT STATE TO PERFORM OPERATION operation

­20340XML SCHEMA xmlschema­name INCLUDES AT LEAST ONE XML SCHEMA DOCUMENT INNAMESPACE namespace THAT IS NOT CONNECTED TO THE OTHER XML SCHEMA DOCUMENTS

­20345THE XML VALUE IS NOT A WELL­FORMED DOCUMENT WITH A SINGLE ROOT ELEMENT

­20353AN OPERATION INVOLVING COMPARISON CANNOT USE OPERAND name DEFINED AS DATATYPE type­name

­20354INVALID SPECIFICATION OF A ROW CHANGE TIMESTAMP COLUMN FOR TABLE table­name

­20355THE STATEMENT COULD NOT BE PROCESSED BECAUSE ONE OR MORE IMPLICITLY CREATEDOBJECTS ARE INVOLVED reason­code

­20356THE TABLE WITH DBID = dbid AND OBID = obid CANNOT BE TRUNCATED BECAUSE DELETETRIGGERS EXIST FOR THE TABLE, OR THE TABLE IS THE PARENT TABLE IN A REFERENTIALCONSTRAINT

­20361AUTHORIZATION ID authorization­name IS NOT DEFINED FOR THE TRUSTED CONTEXT context­name

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 38/42

­20362ATTRIBUTE attribute­name WITH VALUE value CANNOT BE DROPPED BECAUSE IT IS NOT PARTOF THE DEFINITION OF TRUSTED CONTEXT context­name

­20363ATTRIBUTE attribute­name WITH VALUE value IS NOT A UNIQUE SPECIFICATION FOR TRUSTEDCONTEXT context­name

­20365A SIGNALING NAN WAS ENCOUNTERED, OR AN EXCEPTION OCCURRED IN AN ARITHMETICOPERATION OR FUNCTION INVOLVING A DECFLOAT

­20366TABLE WITH DBID=database­id AND OBID=object­id CANNOT BE TRUNCATED BECAUSEUNCOMMITTED UPDATES EXIST ON THE TABLE WITH 'IMMEDIATE' OPTION SPECIFIED IN THESTATEMENT

­20369AN ALTER TRUSTED CONTEXT STATEMENT FOR context­name ATTEMPTED TO REMOVE THELAST CONNECTION TRUST ATTRIBUTE ASSOCIATED WITH THE TRUSTED CONTEXT

­20372THE SYSTEM AUTHID CLAUSE OF A CREATE OR ALTER TRUSTED CONTEXT STATEMENT FORcontext­name SPECIFIED authorization­name, BUT ANOTHER TRUSTED CONTEXT IS ALREADYDEFINED FOR THAT AUTHORIZATION ID.

­20373A CREATE OR ALTER TRUSTED CONTEXT STATEMENT SPECIFIED authorization­name MORETHAN ONCE OR THE TRUSTED CONTEXT IS ALREADY DEFINED TO BE USED BY THISAUTHORIZATION ID, PROFILE NAME, OR PUBLIC.

­20374AN ALTER TRUSTED CONTEXT STATEMENT FOR context­name SPECIFIED authorization­name BUTTHE TRUSTED CONTEXT IS NOT CURRENTLY DEFINED TO BE USED BY THIS AUTHORIZATIONID, PROFILE NAME, OR PUBLIC

­20377AN ILLEGAL XML CHARACTER hex­char WAS FOUND IN AN SQL/XML EXPRESSION OR FUNCTIONARGUMENT THAT BEGINS WITH STRING start­string

­20380ALTER INDEX WITH REGENERATE OPTION FOR index­name FAILED. INFORMATION RETURNED:SQLCODE sqlcode, SQLSTATE sqlstate, MESSAGE TOKENS token­list

­20381ALTER INDEX WITH REGENERATE OPTION IS NOT VALID FOR index­name

­20382CONTEXT ITEM CANNOT BE A SEQUENCE WITH MORE THAN ONE ITEM

­20385THE STATEMENT CANNOT BE PROCESSED BECAUSE THERE ARE PENDING DEFINITIONCHANGES FOR OBJECT object­name OF TYPE object­ type (REASON reason­code)

­20398ERROR ENCOUNTERED DURING XML PARSING AT LOCATION n text

­20399ERROR ENCOUNTERED DURING XML VALIDATION: LOCATION n; TEXT: text; XSRID schema­ID

­20400XML SCHEMA ERROR n text

­20409AN XML DOCUMENT OR CONSTRUCTED XML VALUE CONTAINS A COMBINATION OF XML NODESTHAT CAUSES AN INTERNAL IDENTIFIER LIMIT TO BE EXCEEDED

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 39/42

­20410THE NUMBER OF CHILDREN NODES OF AN XML NODE IN AN XML VALUE HAS EXCEEDED THELIMIT NUMBER OF CHILDREN NODES

­20411A FETCH CURRENT CONTINUE OPERATION WAS REQUESTED FOR cursor­name BUT THERE IS NOPRESERVED, TRUNCATED DATA TO RETURN

­20412SERIALIZATION OF AN XML VALUE RESULTED IN CHARACTERS THAT COULD NOT BEREPRESENTED IN THE TARGET ENCODING

­20422A CREATE TABLE, OR DECLARE GLOBAL TEMPORARY TABLE STATEMENT FOR table­nameATTEMPTED TO CREATE A TABLE WITH ALL THE COLUMNS DEFINED AS HIDDEN

­20423ERROR OCCURRED DURING TEXT SEARCH PROCESSING (server, index­name, text)

­20424TEXT SEARCH SUPPORT IS NOT AVAILABLE reason­code

­20425column­name (IN table­name) WAS SPECIFIED AS AN ARGUMENT TO A TEXT SEARCH FUNCTION,BUT A TEXT INDEX DOES NOT EXIST FOR THE COLUMN

­20426CONFLICTING TEXT SEARCH ADMINISTRATION STORED PROCEDURE RUNNING ON THE SAMEINDEX

­20427ERROR OCCURRED DURING TEXT SEARCH ADMINISTRATION STORED PROCEDURE error

­20428URI SPECIFIED IN THE XMLSCHEMA CLAUSE IS AN EMPTY STRING.

­20433AN UNTYPED EXPRESSION WAS SPECIFIED, BUT AN ASSUMED DATA TYPE CANNOT BEDETERMINED FROM ITS USE

­20434AN UPDATE OPERATION HAS SET ALL OF ITS TARGET COLUMNS TO UNASSIGNED

­20444AN ERROR OCCURRED IN A KEY­EXPRESSION EVALUATION IN index­name INFORMATIONRETURNED: SQLCODE: sqlcode, SQLSTATE: sqlstate, MESSAGE TOKEN token­list AND RID X rid

­20447FORMAT STRING format­string IS NOT VALID FOR THE function­name FUNCTION

­20448string­expression CANNOT BE INTERPRETED USING FORMAT STRING format­string FOR THETIMESTAMP_FORMAT FUNCTION.

­20457THE PROCEDURE procedure­name HAS ENCOUNTERED AN UNSUPPORTED VERSION, version, FORPARAMETER number

­20465THE BINARY XML VALUE IS INCOMPLETE OR CONTAINS UNRECOGNIZED DATA AT LOCATIONposition WITH THE HEX DATA text

­20469ROW OR COLUMN ACCESS CONTROL CANNOT BE ACTIVATED FOR TABLE table­name FORREASON reason­code. object­type object­name IS NOT IN A VALID STATE FOR ACTIVATING ACCESSCONTROL FOR THIS TABLE

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 40/42

­20470object­type1 object­name1 MUST BE DEFINED AS SECURE BECAUSE object­type2 object­name2 ISDEPENDENT ON IT.

­20471THE INSERT OR UPDATE IS NOT ALLOWED BECAUSE A RESULTING ROW DOES NOT SATISFYROW PERMISSIONS.

­20472PERMISSION OR MASK object­name CANNOT BE ALTERED AS SPECIFIED. REASON CODE reason­code.

­20473THE INPUT ARGUMENT OF FUNCTION function­name THAT IS DEFINED WITH THE NOT­SECUREDOPTION MUST NOT REFERENCE COLUMN column­name FOR WHICH A COLUMN MASK ISENABLED AND THE COLUMN ACCESS CONTROL IS ACTIVATED FOR THE TABLE

­20474PERMISSION OR MASK CANNOT BE CREATED FOR THE object­name OBJECT OF THE object­typeTYPE. REASON CODE reason­code.

­20475A COLUMN MASK IS ALREADY DEFINED FOR THE COLUMN column­name IN TABLE table­name(EXISTING MASK NAME mask­name)

­20476THE function­name FUNCTION WAS INVOKED WITH AN INVALID FORMAT STRING format­string.

­20477THE function­name FUNCTION IS NOT ABLE TO USE FORMAT STRING format­string TO INTERPRETTHE ARGUMENT string­expression.

­20478THE STATEMENT CANNOT BE PROCESSED BECAUSE COLUMN MASK mask­name (DEFINED FORCOLUMN column­name) EXISTS AND THE COLUMN MASK CANNOT BE APPLIED OR THEDEFINITION OF THE MASK CONFLICTS WITH THE REQUESTED STATEMENT. REASON CODEreason­code.

­20479THE SOURCE TABLE table­name CANNOT BE ALTERED AS SPECIFIED BECAUSE THE TABLE ISINVOLVED IN ROW OR COLUMN ACCESS CONTROLS. REASON CODE reason­codereason­code.

­20487HASH ORGANIZATION CLAUSE IS NOT VALID FOR table­name

­20488SPECIFIED HASH SPACE IS TOO LARGE FOR THE IMPLICITLY CREATED TABLE SPACE. REASONreason­code. (PARTITION partition­number)

­20490A VERSIONING CLAUSE WAS SPECIFIED FOR TABLE table­name, BUT THE TABLE CANNOT BEUSED AS A SYSTEM PERIOD TEMPORAL TABLE. REASON CODE = reason­code.

­20491INVALID SPECIFICATION OF PERIOD period­name. REASON CODE = reason­code.

­20493A TIMESTAMP WITHOUT TIME ZONE VALUE CANNOT BE ASSIGNED TO A TIMESTAMP WITHTIME ZONE TARGET

­20497A STRING REPRESENTATION OF A DATETIME VALUE THAT CONTAINS A TIME ZONE CANNOT BEIMPLICITLY OR EXPLICITLY CAST TO A TARGET DEFINED AS DATETIME WITHOUT TIME ZONE

­20517XMLMODIFY ATTEMPTED TO UPDATE A COLUMN WHICH WAS NOT SPECIFIED IN THE UPDATESET CLAUSE

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 41/42

­20522INVALID SPECIFICATION OF WITHOUT OVERLAPS CLAUSE. REASON CODE reason­code.

­20523TABLE table­name WAS SPECIFIED AS A HISTORY TABLE, BUT THE TABLE DEFINITION IS NOTVALID FOR A HISTORY TABLE. REASON CODE = reason­code.

­20524INVALID PERIOD SPECIFICATION OR PERIOD CLAUSE FOR PERIOD period­name. REASON CODE= reason­code.

­20525THE REQUESTED ACTION IS NOT VALID FOR TABLE table­name BECAUSE THE TABLE IS THEWRONG TYPE OF TABLE. REASON CODE = reason­code

­20527period­name IS NOT A PERIOD IN TABLE table­name

­20528THE TARGET OF THE DATA CHANGE OPERATION IS A TABLE table­name, WHICH INCLUDES APERIOD period­name. A ROW THAT THIS DATA CHANGE OPERATION ATTEMPTED TO MODIFYWAS ALSO MODIFIED BY ANOTHER TRANSACTION.

­20531THE VERSION NUMBER actual­version SPECIFIED IN A BINARY XML VALUE IS NOT SUPPORTED.THE HIGHEST SUPPORTED VERSION IS supported­version.

­20556THE OPERATION FAILED BECAUSE MULTIPLE RESULT VALUES CANNOT BE RETURNED FROM ASCALAR FUNCTION function­name.

­30000EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR THAT WILL NOT AFFECT THESUCCESSFUL EXECUTION OF SUBSEQUENT COMMANDS OR SQL STATEMENTS: REASONreason­code (sub­code)

­30002THE SQL STATEMENT CANNOT BE EXECUTED DUE TO A PRIOR CONDITION IN A CHAIN OFSTATEMENTS

­30005EXECUTION FAILED BECAUSE FUNCTION NOT SUPPORTED BY THE SERVER: LOCATION location­name PRODUCT ID product­identifier REASON reason­code (sub­code)

­30020EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATIONOF THE CONVERSATION: REASON reason­code (sub­code)

­30021EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR THAT WILL AFFECT THESUCCESSFUL EXECUTION OF SUBSEQUENT COMMANDS OR SQL STATEMENTS: MANAGERmanager AT LEVEL level NOT SUPPORTED ERROR

­30025EXECUTION FAILED BECAUSE FUNCTION IS NOT SUPPORTED BY THE SERVER WHICH CAUSEDTERMINATION OF THE CONNECTION: LOCATION location PRODUCT ID product­identifier REASONreason­code (sub­code)

­30030COMMIT REQUEST WAS UNSUCCESSFUL, A DISTRIBUTION PROTOCOL VIOLATION HAS BEENDETECTED, THE CONVERSATION HAS BEEN DEALLOCATED. ORIGINAL SQLCODE=original­sqlcodeAND ORIGINAL SQLSTATE=original­sqlstate

­30040EXECUTION FAILED DUE TO UNAVAILABLE RESOURCES THAT WILL NOT AFFECT THESUCCESSFUL EXECUTION OF SUBSEQUENT COMMANDS OR SQL STATEMENTS. REASONreason­code TYPE OF RESOURCE resource­type RESOURCE NAME resource­name PRODUCT ID

9/4/2015 DB2 10 ­ Codes ­ SQL error codes

https://www­304.ibm.com/support/knowledgecenter/api/content/nl/en­us/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/db2z_n.dita 42/42

product­identifier RDBNAME rdbname

­30041EXECUTION FAILED DUE TO UNAVAILABLE RESOURCES THAT WILL AFFECT THE SUCCESSFULEXECUTION OF SUBSEQUENT COMMANDS AND SQL STATEMENTS. REASON reason­code TYPEOF RESOURCE resource­type RESOURCE NAME resource­name PRODUCT ID product­identifierRDBNAME rdbname

­30050command­or­SQL­statement­type COMMAND OR SQL STATEMENT INVALID WHILE BIND PROCESSIN PROGRESS

­30051BIND PROCESS WITH SPECIFIED PACKAGE NAME AND CONSISTENCY TOKEN NOT ACTIVE

­30052PROGRAM PREPARATION ASSUMPTIONS ARE INCORRECT

­30053OWNER AUTHORIZATION FAILURE

­30060RDB AUTHORIZATION FAILURE

­30061RDB NOT FOUND

­30070command COMMAND NOT SUPPORTED ERROR

­30071object­type OBJECT NOT SUPPORTED ERROR

­30072parameter subcode PARAMETER NOT SUPPORTED ERROR

­30073parameter subcode PARAMETER VALUE NOT SUPPORTED ERROR

­30074REPLY MESSAGE WITH codepoint (svrcod) NOT SUPPORTED ERROR

­30080COMMUNICATION ERROR code (subcode)

­30081prot COMMUNICATIONS ERROR DETECTED. API=api, LOCATION=loc, FUNCTION=func, ERRORCODES=rc1 rc2 rc3

­30082CONNECTION FAILED FOR SECURITY REASON reason­code (reason­string)

­30090REMOTE OPERATION INVALID FOR APPLICATION EXECUTION ENVIRONMENT

­30104ERROR IN BIND OPTION option­name AND BIND VALUE option­value.

­30105BIND OPTION option1 IS NOT ALLOWED WITH BIND OPTION option2

­30106INVALID INPUT DATA DETECTED FOR A MULTIPLE ROW INSERT OPERATION. INSERTPROCESSING IS TERMINATED

Parent topic: SQL codes

top related