SQL return codes - Revision history

wikademia>Wikademia: 63 revisions

2009-05-11T20:56:40Z

63 revisions

← Older revision	Revision as of 20:56, 11 May 2009
(No difference)

wikademia>Adrignola: Added DDC/LOC classifications. Added to category that wasn't a book category for another book.

2009-05-02T06:09:52Z

Added DDC/LOC classifications. Added to category that wasn't a book category for another book.

← Older revision		Revision as of 06:09, 2 May 2009
Line 725:		Line 725:
	* A [http://www.theamericanprogrammer.com/programming/sqlcodes.shtml more extensive list] of the codes		* A [http://www.theamericanprogrammer.com/programming/sqlcodes.shtml more extensive list] of the codes

	~~[[category:SQL]]~~		{{Subject\|Database systems}}
	{{Alphabetical\|S}}		{{Alphabetical\|S}}
			{{DDC\|600}}
			{{LOC\|QA76.75}}

wikademia>Van der Hoorn: typo fixes

2009-03-25T12:24:08Z

typo fixes

← Older revision		Revision as of 12:24, 25 March 2009
Line 11:		Line 11:

	Negative means unsuccessful execution with an error.		Negative means unsuccessful execution with an error.
	An example is -911 which means a timeout has ~~occured~~ with a rollback.		An example is -911 which means a timeout has occurred with a rollback.

	Positive means successful execution with a warning.		Positive means successful execution with a warning.
Line 692:		Line 692:
	+807 THE RESULT OF DECIMAL MULTIPLICATION MAY CAUSE OVERFLOW		+807 THE RESULT OF DECIMAL MULTIPLICATION MAY CAUSE OVERFLOW
	+863 THE CONNECTION WAS SUCCESSFUL BUT ONLY SBCS WILL BE SUPPORTED		+863 THE CONNECTION WAS SUCCESSFUL BUT ONLY SBCS WILL BE SUPPORTED
	+883 ROLLBACK TO SAVEPOINT ~~OCCURED~~ WHEN THERE WERE OPERATIONS THAT CANNOT BE UNDONE, OR AN OPERATION THAT CANNOT BE		+883 ROLLBACK TO SAVEPOINT OCCURRED WHEN THERE WERE OPERATIONS THAT CANNOT BE UNDONE, OR AN OPERATION THAT CANNOT BE
	UNDONE OCCURRED WHEN THERE WAS A SAVEPOINT OUTSTANDING		UNDONE OCCURRED WHEN THERE WAS A SAVEPOINT OUTSTANDING
	+2000 TYPE 1 INDEXES WITH SUBPAGES GREATER THAN 1 CANNOT BECOME GROUP BUFFER POOL DEPENDENT IN A DATA SHARING		+2000 TYPE 1 INDEXES WITH SUBPAGES GREATER THAN 1 CANNOT BECOME GROUP BUFFER POOL DEPENDENT IN A DATA SHARING

wikademia>Kubakocoj at 07:44, 26 February 2009

2009-02-26T07:44:07Z

← Older revision		Revision as of 07:44, 26 February 2009
Line 707:		Line 707:
	=== Letter SQL Codes ===		=== Letter SQL Codes ===

	If you have a code in the type of SQL-0000##A these are still valid but ~~hard~~ to decipher.		If you have a code in the type of SQL-0000##A these are still valid but a bit harder to decipher.
	Use the chart below to map the letter to the last number of the value.		Use the chart below to map the letter to the last number of the value.
	This was created when SQL Codes where only able to be unsigned.		This was created when SQL Codes where only able to be unsigned.

wikademia>JohnsonCharlesD: /* Positive Values (Warnings) */

2009-02-25T18:46:52Z

Positive Values (Warnings)

← Older revision		Revision as of 18:46, 25 February 2009
Line 644:		Line 644:
	+231 FETCH after a BEFORE or AFTER but not on a valid row.		+231 FETCH after a BEFORE or AFTER but not on a valid row.
	+236 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 ARE REQUIRED FOR integer3 COLUMNS		+236 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 ARE REQUIRED FOR integer3 COLUMNS
	+237 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 ARE REQUIRED BECAUSE AT LEAST ONE OF THE COLUMNS BEING DESCRIBED IS A DISTINCT TYPE		+237 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 ARE REQUIRED BECAUSE AT LEAST ONE OF THE COLUMNS BEING
	+238 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 SQLVAR ENTRIES ARE NEEDED FOR integer3 COLUMNS BECAUSE AT LEAST ONE OF THE COLUMNS BEING DESCRIBED IS A LOB		DESCRIBED IS A DISTINCT TYPE
	+239 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 ARE REQUIRED FOR integer3 COLUMNS BECAUSE AT LEAST ONE OF THE COLUMNS BEING DESCRIBED IS A DISTINCT TYPE		+238 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 SQLVAR ENTRIES ARE NEEDED FOR integer3 COLUMNS BECAUSE AT
			LEAST ONE OF THE COLUMNS BEING DESCRIBED IS A LOB
			+239 SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 ARE REQUIRED FOR integer3 COLUMNS BECAUSE AT LEAST ONE OF THE
			COLUMNS BEING DESCRIBED IS A DISTINCT TYPE
	+304 Value cannot be assigned to this host variable because it is out of range.		+304 Value cannot be assigned to this host variable because it is out of range.
	+331 THE NULL VALUE HAS BEEN ASSIGNED TO A HOST VARIABLE BECAUSE THE STRING CANNOT BE TRANSLATED. REASON reason-code, CHARACTER code-point, HOST VARIABLE position-number		+331 THE NULL VALUE HAS BEEN ASSIGNED TO A HOST VARIABLE BECAUSE THE STRING CANNOT BE TRANSLATED. REASON reason-code,
	+335 DB2 CONVERTED A HOST VARIABLE, PARAMETER, OR COLUMN NUMBER var-num var-name-or-num TO COLUMN NAME,HOST VARIABLE, OR EXPRESSION NUMBER col-name-or-num FROM from ccsid TO to-ccsid, AND RESULTING IN SUBSTITUTION CHARACTERS.		CHARACTER code-point, HOST VARIABLE position-number
			+335 DB2 CONVERTED A HOST VARIABLE, PARAMETER, OR COLUMN NUMBER var-num var-name-or-num TO COLUMN NAME,HOST VARIABLE,
			OR EXPRESSION NUMBER col-name-or-num FROM from ccsid TO to-ccsid, AND RESULTING IN SUBSTITUTION CHARACTERS.
	+339 THE SQL STATEMENT HAS BEEN SUCCESSFULLY EXECUTED, BUT THERE MAY BE SOME CHARACTER CONVERSION INCONSISTENCIES		+339 THE SQL STATEMENT HAS BEEN SUCCESSFULLY EXECUTED, BUT THERE MAY BE SOME CHARACTER CONVERSION INCONSISTENCIES
	+394 USER SPECIFIED OPTIMIZATION HINTS USED DURING ACCESS PATH SELECTION		+394 USER SPECIFIED OPTIMIZATION HINTS USED DURING ACCESS PATH SELECTION
Line 657:		Line 662:
	+434 OPTION keyword IS A DEPRECATED FEATURE		+434 OPTION keyword IS A DEPRECATED FEATURE
	+445 VALUE value HAS BEEN TRUNCATED		+445 VALUE value HAS BEEN TRUNCATED
	+462 EXTERNAL FUNCTION OR PROCEDURE name (SPECIFIC NAME specific-name) HAS RETURNED A WARNING SQLSTATE, WITH DIAGNOSTIC TEXT text		+462 EXTERNAL FUNCTION OR PROCEDURE name (SPECIFIC NAME specific-name) HAS RETURNED A WARNING SQLSTATE, WITH DIAGNOSTIC
			TEXT text
	+464 PROCEDURE proc RETURNED num QUERY RESULT SETS, WHICH EXCEEDS THE DEFINED LIMIT integer		+464 PROCEDURE proc RETURNED num QUERY RESULT SETS, WHICH EXCEEDS THE DEFINED LIMIT integer
	+466 PROCEDURE proc RETURNED num QUERY RESULTS SETS		+466 PROCEDURE proc RETURNED num QUERY RESULTS SETS
	+494 NUMBER OF RESULT SETS IS GREATER THAN NUMBER OF LOCATORS		+494 NUMBER OF RESULT SETS IS GREATER THAN NUMBER OF LOCATORS
	+495 ESTIMATED PROCESSOR COST OF estimate-amount1 PROCESSOR SECONDS (estimate-amount2 SERVICE UNITS) IN COST CATEGORY cost-category EXCEEDS A RESOURCE LIMIT WARNING THRESHOLD OF limit- amount SERVICE UNITS		+495 ESTIMATED PROCESSOR COST OF estimate-amount1 PROCESSOR SECONDS (estimate-amount2 SERVICE UNITS) IN COST CATEGORY
			cost-category EXCEEDS A RESOURCE LIMIT WARNING THRESHOLD OF limit- amount SERVICE UNITS
	+535 THE RESULT OF THE POSITIONED UPDATE OR DELETE MAY DEPEND ON THE ORDER OF THE ROWS		+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		+541 THE REFERENTIAL OR UNIQUE CONSTRAINT name HAS BEEN IGNORED BECAUSE IT IS A DUPLICATE
Line 674:		Line 681:
	+645 WHERE NOT NULL IS IGNORED BECAUSE THE INDEX KEY CANNOT CONTAIN NULL VALUES		+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		+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		+653 TABLE table-name IN PARTITIONED TABLESPACE tspace-name IS NOT AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS
			NOT BEEN CREATED
	+655 STOGROUP stogroup_name HAS BOTH SPECIFIC AND NON-SPECIFIC VOLUME IDS. IT WILL NOT BE ALLOWED IN FUTURE RELEASES		+655 STOGROUP stogroup_name HAS BOTH SPECIFIC AND NON-SPECIFIC VOLUME IDS. IT WILL NOT BE ALLOWED IN FUTURE RELEASES
	+658 THE SUBPAGES VALUE IS IGNORED FOR THE CATALOG INDEX index-name		+658 THE SUBPAGES VALUE IS IGNORED FOR THE CATALOG INDEX index-name
Line 684:		Line 692:
	+807 THE RESULT OF DECIMAL MULTIPLICATION MAY CAUSE OVERFLOW		+807 THE RESULT OF DECIMAL MULTIPLICATION MAY CAUSE OVERFLOW
	+863 THE CONNECTION WAS SUCCESSFUL BUT ONLY SBCS WILL BE SUPPORTED		+863 THE CONNECTION WAS SUCCESSFUL BUT ONLY SBCS WILL BE SUPPORTED
	+883 ROLLBACK TO SAVEPOINT OCCURED WHEN THERE WERE OPERATIONS THAT CANNOT BE UNDONE, OR AN OPERATION THAT CANNOT BE UNDONE OCCURRED WHEN THERE WAS A SAVEPOINT OUTSTANDING		+883 ROLLBACK TO SAVEPOINT OCCURED WHEN THERE WERE OPERATIONS THAT CANNOT BE UNDONE, OR AN OPERATION THAT CANNOT BE
	+2000 TYPE 1 INDEXES WITH SUBPAGES GREATER THAN 1 CANNOT BECOME GROUP BUFFER POOL DEPENDENT IN A DATA SHARING ENVIRONMENT		UNDONE OCCURRED WHEN THERE WAS A SAVEPOINT OUTSTANDING
			+2000 TYPE 1 INDEXES WITH SUBPAGES GREATER THAN 1 CANNOT BECOME GROUP BUFFER POOL DEPENDENT IN A DATA SHARING
			ENVIRONMENT
	+20002 THE GBPCACHE SPECIFICATION IS IGNORED, bpname DOES NOT ALLOW CACHING		+20002 THE GBPCACHE SPECIFICATION IS IGNORED, bpname DOES NOT ALLOW CACHING
	+20007 USE OF OPTIMIZATION HINTS IS DISALLOWED BY A DB2 SUBSYSTEM PARAMETER. THE SPECIAL REGISTER ’OPTIMIZATION HINT’ IS SET TO THE DEFAULT VALUE OF BLANKS.		+20007 USE OF OPTIMIZATION HINTS IS DISALLOWED BY A DB2 SUBSYSTEM PARAMETER. THE SPECIAL REGISTER ’OPTIMIZATION HINT’
			IS SET TO THE DEFAULT VALUE OF BLANKS.
	+20122 DEFINE NO OPTION IS NOT APPLICABLE IN THE CONTEXT SPECIFIED		+20122 DEFINE NO OPTION IS NOT APPLICABLE IN THE CONTEXT SPECIFIED
	+20141 TRUNCATION OF VALUE WITH LENGTH length OCCURRED FOR hv-or-parm-number		+20141 TRUNCATION OF VALUE WITH LENGTH length OCCURRED FOR hv-or-parm-number
	+20267 OPTION clause IS NOT SUPPORTED IN THE CONTEXT IN WHICH IT WAS SPECIFIED		+20267 OPTION clause IS NOT SUPPORTED IN THE CONTEXT IN WHICH IT WAS SPECIFIED
	+30100 OPERATION COMPLETED SUCCESSFULLY BUT A DISTRIBUTION PROTOCOL VIOLATION HAS BEEN DETECTED. ORIGINAL SQLCODE=original-sqlcode AND ORIGINAL SQLSTATE=original-sqlstate		+30100 OPERATION COMPLETED SUCCESSFULLY BUT A DISTRIBUTION PROTOCOL VIOLATION HAS BEEN DETECTED. ORIGINAL
			SQLCODE=original-sqlcode AND ORIGINAL SQLSTATE=original-sqlstate

	=== Letter SQL Codes ===		=== Letter SQL Codes ===

wikademia>JohnsonCharlesD: /* Negative (Greater than -991) */

2009-02-25T18:45:45Z

Negative (Greater than -991)

← Older revision		Revision as of 18:45, 25 February 2009
Line 543:		Line 543:
	=== Negative (Greater than -991) ===		=== Negative (Greater than -991) ===
	-1760 CREATE PROCEDURE FOR procedure-name MUST HAVE VALID LANGUAGE AND EXTERNAL CLAUSES		-1760 CREATE PROCEDURE FOR procedure-name MUST HAVE VALID LANGUAGE AND EXTERNAL CLAUSES
	-2001 THE NUMBER OF HOST VARIABLE PARAMETERS FOR A STORED PROCEDURE IS NOT EQUAL TO THE NUMBER OF EXPECTED HOST VARIABLE PARAMETERS. ACTUAL NUMBER sqldanum, EXPECTED NUMBER opnum		-2001 THE NUMBER OF HOST VARIABLE PARAMETERS FOR A STORED PROCEDURE IS NOT EQUAL TO THE NUMBER OF EXPECTED HOST
			VARIABLE PARAMETERS. ACTUAL NUMBER sqldanum, EXPECTED NUMBER opnum
	-5012 HOST VARIABLE host-variable IS NOT EXACT NUMERIC WITH SCALE ZERO		-5012 HOST VARIABLE host-variable IS NOT EXACT NUMERIC WITH SCALE ZERO
	-20003 GBPCACHE NONE CANNOT BE SPECIFIED FOR TABLESPACE OR INDEX IN GRECP		-20003 GBPCACHE NONE CANNOT BE SPECIFIED FOR TABLESPACE OR INDEX IN GRECP
Line 552:		Line 553:
	-20070 AUXILIARY TABLE table-name CANNOT BE CREATED BECAUSE COLUMN column-name IS NOT A LOB COLUMN		-20070 AUXILIARY TABLE table-name CANNOT BE CREATED BECAUSE COLUMN column-name IS NOT A LOB COLUMN
	-20071 WLM ENVIRONMENT NAME MUST BE SPECIFIED function-name		-20071 WLM ENVIRONMENT NAME MUST BE SPECIFIED function-name
	-20072 csect-name bind-type bind-subtype ERROR USING auth-id AUTHORITY OPERATION IS NOT ALLOWED ON A TRIGGER PACKAGE package-name		-20072 csect-name bind-type bind-subtype ERROR USING auth-id AUTHORITY OPERATION IS NOT ALLOWED ON A TRIGGER PACKAGE
			package-name
	-20073 THE FUNCTION function-name CANNOT BE ALTERED BECAUSE IT IS REFERENCED IN EXISTING VIEW DEFINITIONS		-20073 THE FUNCTION function-name CANNOT BE ALTERED BECAUSE IT IS REFERENCED IN EXISTING VIEW DEFINITIONS
	-20074 THE OBJECT object-name CANNOT BE CREATED BECAUSE THE FIRST THREE CHARACTERS ARE RESERVED FOR SYSTEM OBJECTS		-20074 THE OBJECT object-name CANNOT BE CREATED BECAUSE THE FIRST THREE CHARACTERS ARE RESERVED FOR SYSTEM OBJECTS
	-20091 A VIEW NAME WAS SPECIFIED AFTER LIKE IN ADDITION TO THE INCLUDING IDENTITY COLUMN ATTRIBUTES CLAUSE		-20091 A VIEW NAME WAS SPECIFIED AFTER LIKE IN ADDITION TO THE INCLUDING IDENTITY COLUMN ATTRIBUTES CLAUSE
	-20092 A VIEW WAS SPECIFIED FOR LIKE BUT IT INCLUDES A ROWID COLUMN		-20092 A VIEW WAS SPECIFIED FOR LIKE BUT IT INCLUDES A ROWID COLUMN
	-20100 AN ERROR OCCURRED WHEN BINDING A TRIGGERED SQL STATEMENT. INFORMATION RETURNED: SECTION NUMBER : section-number SQLCODE sqlerror, SQLSTATE sqlstate, AND MESSAGE TOKENS token-list		-20100 AN ERROR OCCURRED WHEN BINDING A TRIGGERED SQL STATEMENT. INFORMATION RETURNED: SECTION NUMBER : section-number
			SQLCODE sqlerror, SQLSTATE sqlstate, AND MESSAGE TOKENS token-list
	-20101 THE FUNCTION function FAILED WITH REASON rc		-20101 THE FUNCTION function FAILED WITH REASON rc
	-20102 CREATE OR ALTER STATEMENT FOR ROUTINE routine-name SPECIFIED THE option OPTION WHICH IS NOT ALLOWED FOR THE TYPE OF ROUTINE		-20102 CREATE OR ALTER STATEMENT FOR ROUTINE routine-name SPECIFIED THE option OPTION WHICH IS NOT ALLOWED FOR THE TYPE
			OF ROUTINE
	-20104 AN ATTEMPT TO ALTER A CCSID FROM from-ccsid TO to-ccsid FAILED		-20104 AN ATTEMPT TO ALTER A CCSID FROM from-ccsid TO to-ccsid FAILED
	-20106 THE CCSID FOR TABLE SPACE OR DATABASE CANNOT BE CHANGED BECAUSE THE TABLE SPACE OR DATABASE ALREADY CONTAINS A TABLE THAT IS REFERENCED IN EXISTING VIEW DEFINITIONS		-20106 THE CCSID FOR TABLE SPACE OR DATABASE CANNOT BE CHANGED BECAUSE THE TABLE SPACE OR DATABASE ALREADY CONTAINS A
			TABLE THAT IS REFERENCED IN EXISTING VIEW DEFINITIONS
	-20107 HOST VARIABLE OR PARAMETER NUMBER position-number CANNOT BE USED AS SPECIFIED BECAUSE REASON reason		-20107 HOST VARIABLE OR PARAMETER NUMBER position-number CANNOT BE USED AS SPECIFIED BECAUSE REASON reason
	-20108 A RESULT SET CONTAINS AN UNSUPPORTED DATA TYPE IN POSITION NUMBER position-number FOR CURSOR cursor-name OPENED BY STORED PROCEDURE procedure-name		-20108 A RESULT SET CONTAINS AN UNSUPPORTED DATA TYPE IN POSITION NUMBER position-number FOR CURSOR cursor-name OPENED
			BY STORED PROCEDURE procedure-name
	-20110 CANNOT IMPLICITLY CONNECT TO A REMOTE SITE WITH A SAVEPOINT OUTSTANDING		-20110 CANNOT IMPLICITLY CONNECT TO A REMOTE SITE WITH A SAVEPOINT OUTSTANDING
	-20111 CANNOT ISSUE SAVEPOINT, RELEASE SAVEPOINT, ROLLBACK TO SAVEPOINT FROM A TRIGGER, FROM A USER-DEFINED FUNCTION, OR FROM A GLOBAL TRANSACTION		-20111 CANNOT ISSUE SAVEPOINT, RELEASE SAVEPOINT, ROLLBACK TO SAVEPOINT FROM A TRIGGER, FROM A USER-DEFINED FUNCTION,
	-20123 CALL TO STORED PROCEDURE procedure FAILED BECAUSE THE RESULT SET RETURNED FOR CURSOR cursor IS SCROLLABLE, BUT THE CURSOR IS NOT POSITIONED BEFORE THE FIRST ROW		OR FROM A GLOBAL TRANSACTION
			-20123 CALL TO STORED PROCEDURE procedure FAILED BECAUSE THE RESULT SET RETURNED FOR CURSOR cursor IS SCROLLABLE, BUT
			THE CURSOR IS NOT POSITIONED BEFORE THE FIRST ROW
	-20124 OPEN CURSOR cursor FAILED BECAUSE THE CURSOR IS SCROLLABLE BUT THE CLIENT DOES NOT SUPPORT THIS		-20124 OPEN CURSOR cursor FAILED BECAUSE THE CURSOR IS SCROLLABLE BUT THE CLIENT DOES NOT SUPPORT THIS
	-20125 CALL TO STORED PROCEDURE procedure FAILED BECAUSE THE RESULT SET FOR CURSOR cursor IS SCROLLABLE, BUT THE CLIENT DOES NOT SUPPORT THIS		-20125 CALL TO STORED PROCEDURE procedure FAILED BECAUSE THE RESULT SET FOR CURSOR cursor IS SCROLLABLE, BUT THE CLIENT
			DOES NOT SUPPORT THIS
	-20126 CURSOR cursor IS DEFINED AS SCROLLABLE, BUT THE ENVIRONMENT INVOLVES A HOP SITE		-20126 CURSOR cursor IS DEFINED AS SCROLLABLE, BUT THE ENVIRONMENT INVOLVES A HOP SITE
	-20127 VALUE SPECIFIED ON FETCH STATEMENT FOR ABSOLUTE OR RELATIVE IS TOO LARGE FOR DRDA		-20127 VALUE SPECIFIED ON FETCH STATEMENT FOR ABSOLUTE OR RELATIVE IS TOO LARGE FOR DRDA
Line 575:		Line 584:
	-20201 THE INSTALL_JAR, REPLACE_JAR, OR REMOVE_JAR PROCEDURE FOR jar-name FAILED AS THE JAR NAME IS INVALID		-20201 THE INSTALL_JAR, REPLACE_JAR, OR REMOVE_JAR PROCEDURE FOR jar-name FAILED AS THE JAR NAME IS INVALID
	-20202 THE REPLACE_JAR OR REMOVE_JAR PROCEDURE FOR jar-name FAILED AS class IS IN USE		-20202 THE REPLACE_JAR OR REMOVE_JAR PROCEDURE FOR jar-name FAILED AS class IS IN USE
	-20203 USER DEFINED FUNCTION OR PROCEDURE name HAS A JAVA METHOD WITH AN INVALID SIGNATURE. THE ERROR IS AT OR NEAR PARAMETER number. THE SIGNATURE IS signature		-20203 USER DEFINED FUNCTION OR PROCEDURE name HAS A JAVA METHOD WITH AN INVALID SIGNATURE. THE ERROR IS AT OR NEAR
			PARAMETER number. THE SIGNATURE IS signature
	-20204 THE USER-DEFINED FUNCTION OR PROCEDURE routine-name WAS UNABLE TO MAP TO A SINGLE JAVA METHOD		-20204 THE USER-DEFINED FUNCTION OR PROCEDURE routine-name WAS UNABLE TO MAP TO A SINGLE JAVA METHOD
	-20207 THE INSTALL_JAR OR REMOVE_JAR PROCEDURE FOR jar-name SPECIFIED THE USE OF A DEPLOYMENT DESCRIPTOR		-20207 THE INSTALL_JAR OR REMOVE_JAR PROCEDURE FOR jar-name SPECIFIED THE USE OF A DEPLOYMENT DESCRIPTOR
	-20210 THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT WAS AT A LEVEL THAT IS INCOMPATIBLE WITH THE CURRENT VALUE OF THE ENCODING BIND OPTION OR SPECIAL REGISTER		-20210 THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT WAS AT A LEVEL THAT IS INCOMPATIBLE WITH THE CURRENT VALUE OF
	-20212 USER-DEFINED ROUTINE name ENCOUNTERED AN EXCEPTION ATTEMPTING TO LOAD JAVA CLASS class-name FROM JAR jar-name. ORIGINAL EXCEPTION: exception-string.		THE ENCODING BIND OPTION OR SPECIAL REGISTER
	-20213 STORED PROCEDURE procedure-name HAS RETURNED A DYNAMIC RESULT SET OF AN INVALID CLASS. PARAMETER number IS NOT A DB2 RESULT SET		-20212 USER-DEFINED ROUTINE name ENCOUNTERED AN EXCEPTION ATTEMPTING TO LOAD JAVA CLASS class-name FROM JAR jar-name.
	-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)		ORIGINAL EXCEPTION: exception-string.
			-20213 STORED PROCEDURE procedure-name HAS RETURNED A DYNAMIC RESULT SET OF AN INVALID CLASS. PARAMETER number IS NOT A
			DB2 RESULT SET
			-30000 EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR THAT WILL NOT AFFECT THE SUCCESSFUL EXECUTION OF
			SUBSEQUENT COMMANDS OR SQL STATEMENTS: REASON reason-code (sub-code)
	-30002 THE SQL STATEMENT CANNOT BE EXECUTED DUE TO A PRIOR CONDITION IN A CHAIN OF STATEMENTS		-30002 THE SQL STATEMENT CANNOT BE EXECUTED DUE TO A PRIOR CONDITION IN A CHAIN OF STATEMENTS
	-30020 EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION: REASON <reason-code (sub-code)>		-30020 EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION: REASON
	-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		<reason-code (sub-code)>
	-30030 COMMIT REQUEST WAS UNSUCCESSFUL, A DISTRIBUTION PROTOCOL VIOLATION HAS BEEN DETECTED, THE CONVERSATION HAS BEEN DEALLOCATED. ORIGINAL SQLCODE=original-sqlcode AND ORIGINAL SQLSTATE=original-sqlstate		-30021 EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR THAT WILL AFFECT THE SUCCESSFUL EXECUTION OF SUBSEQUENT
	-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		COMMANDS OR SQL STATEMENTS: MANAGER manager AT LEVEL level NOT SUPPORTED ERROR
	-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>		-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		-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		-30051 BIND PROCESS WITH SPECIFIED PACKAGE NAME AND CONSISTENCY TOKEN NOT ACTIVE

wikademia>JohnsonCharlesD: /* Negative (-802 to -991) */

2009-02-25T18:44:02Z

Negative (-802 to -991)

Show changes

wikademia>JohnsonCharlesD: /* Negative (-500 to -798) */

2009-02-25T18:41:43Z

Negative (-500 to -798)

Show changes

wikademia>JohnsonCharlesD: /* Negative (-300 to -499) */

2009-02-25T18:39:01Z

Negative (-300 to -499)

← Older revision		Revision as of 18:39, 25 February 2009
Line 138:		Line 138:
	=== Negative (-300 to -499) ===		=== Negative (-300 to -499) ===
	-300 THE STRING CONTAINED IN HOST VARIABLE OR PARAMETER position-number IS NOT NUL-TERMINATED		-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		-301 THE VALUE OF INPUT HOST VARIABLE OR PARAMETER NUMBER position-number CANNOT BE USED AS SPECIFIED BECAUSE OF ITS
	-302 THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER position-number IS INVALID OR TOO LARGE FOR THE TARGET COLUMN OR THE TARGET VALUE		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		-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		-304 A VALUE WITH DATA TYPE data-type1 CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE
	-305 THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER position-number BECAUSE NO INDICATOR VARIABLE IS SPECIFIED		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		-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		-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		-311 THE LENGTH OF INPUT HOST VARIABLE NUMBER position-number IS NEGATIVE OR GREATER THAN THE MAXIMUM
	-312 variable-name IS AN UNDEFINED OR UNUSABLE HOST VARIABLE OR IS USED IN A DYNAMIC SQL STATEMENT OR A TRIGGER DEFINITION		-312 variable-name IS AN UNDEFINED OR UNUSABLE HOST VARIABLE OR IS USED IN A DYNAMIC SQL STATEMENT OR A TRIGGER
			DEFINITION
	-313 THE NUMBER OF HOST VARIABLES SPECIFIED IS NOT EQUAL TO THE NUMBER OF PARAMETER MARKERS		-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		-314 THE STATEMENT CONTAINS AN AMBIGUOUS HOST VARIABLE REFERENCE
	-327 THE ROW CANNOT BE INSERTED BECAUSE IT IS OUTSIDE THE BOUND OF THE PARTITION RANGE FOR THE LAST PARTITION		-327 THE ROW CANNOT BE INSERTED BECAUSE IT IS OUTSIDE THE BOUND OF THE PARTITION RANGE FOR THE LAST PARTITION
	-330 A STRING CANNOT BE USED BECAUSE IT CANNOT BE TRANSLATED. REASON reason-code, CHARACTER code-point, HOST VARIABLE position-number		-330 A STRING CANNOT BE USED BECAUSE IT CANNOT BE TRANSLATED. REASON reason-code, CHARACTER code-point, HOST VARIABLE
	-331 A STRING CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE IT CANNOT BE TRANSLATED. REASON reason-code, CHARACTER code-point, POSITION position-number		position-number
			-331 A STRING CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE IT CANNOT BE TRANSLATED. REASON reason-code, CHARACTER
			code-point, POSITION position-number
	-332 CHARACTER CONVERSION BETWEEN CCSID from-ccsid TO to-ccsid REQUESTED BY reason-code IS NOT SUPPORTED		-332 CHARACTER CONVERSION BETWEEN CCSID from-ccsid TO to-ccsid REQUESTED BY reason-code IS NOT SUPPORTED
	-333 THE SUBTYPE OF A STRING VARIABLE IS NOT THE SAME AS THE SUBTYPE KNOWN AT BIND TIME AND THE DIFFERENCE CANNOT BE RESOLVED BY TRANSLATION		-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		-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		-339 THE SQL STATEMENT CANNOT BE EXECUTED FROM AN ASCII BASED DRDA APPLICATION REQUESTOR TO A V2R2 DB2 SUBSYSTEM
Line 182:		Line 190:
	-413 OVERFLOW OCCURRED DURING NUMERIC DATA TYPE CONVERSION		-413 OVERFLOW OCCURRED DURING NUMERIC DATA TYPE CONVERSION
	-414 A LIKE PREDICATE IS INVALID BECAUSE THE FIRST OPERAND IS NOT A STRING		-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		-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		-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		-417 A STATEMENT STRING TO BE PREPARED INCLUDES PARAMETER MARKERS AS THE OPERANDS OF THE SAME OPERATOR
Line 200:		Line 209:
	-443 ROUTINE routine-name (SPECIFIC NAME specific-name) HAS RETURNED AN ERROR SQLSTATE WITH DIAGNOSTIC TEXT msg-text		-443 ROUTINE routine-name (SPECIFIC NAME specific-name) HAS RETURNED AN ERROR SQLSTATE WITH DIAGNOSTIC TEXT msg-text
	-444 USER PROGRAM name COULD NOT BE FOUND		-444 USER PROGRAM name COULD NOT BE FOUND
	-449 CREATE OR ALTER STATEMENT FOR FUNCTION OR PROCEDURE routine-name CONTAINS AN INVALID FORMAT OF THE EXTERNAL NAME CLAUSE OR IS MISSING THE		-449 CREATE OR ALTER STATEMENT FOR FUNCTION OR PROCEDURE routine-name CONTAINS AN INVALID FORMAT OF THE EXTERNAL NAME
	-450 USER-DEFINED FUNCTION OR STORED PROCEDURE name, PARAMETER NUMBER parmnum, OVERLAYED STORAGE BEYOND ITS DECLARED LENGTH.		CLAUSE OR IS MISSING THE
	-451 THE data-item DEFINITION, IN THE CREATE FUNCTION FOR function-name CONTAINS DATA TYPE type WHICH IS NOT APPROPRIATE FOR AN EXTERNAL FUNCTION WRITTEN IN THE GIVEN LANGUAGE		-450 USER-DEFINED FUNCTION OR STORED PROCEDURE name, PARAMETER NUMBER parmnum, OVERLAYED STORAGE BEYOND ITS DECLARED
			LENGTH.
			-451 THE data-item DEFINITION, IN THE CREATE FUNCTION FOR function-name CONTAINS DATA TYPE type WHICH IS NOT
			APPROPRIATE FOR AN EXTERNAL FUNCTION WRITTEN IN THE GIVEN LANGUAGE
	-453 THERE IS A PROBLEM WITH THE RETURNS CLAUSE IN THE CREATE FUNCTION STATEMENT FOR function-name		-453 THERE IS A PROBLEM WITH THE RETURNS CLAUSE IN THE CREATE FUNCTION STATEMENT FOR function-name
	-454 THE SIGNATURE PROVIDED IN THE CREATE FUNCTION STATEMENT FOR function-name MATCHES THE SIGNATURE OF SOME OTHER FUNCTION ALREADY EXISTING IN THE SCHEMA		-454 THE SIGNATURE PROVIDED IN THE CREATE FUNCTION STATEMENT FOR function-name MATCHES THE SIGNATURE OF SOME OTHER
	-455 IN CREATE FUNCTION FOR function-name, THE SCHEMA NAME schema-name1 PROVIDED FOR THE SPECIFIC NAME DOES NOT MATCH THE SCHEMA NAME schema-name2 OF THE FUNCTION		FUNCTION ALREADY EXISTING IN THE SCHEMA
			-455 IN CREATE FUNCTION FOR function-name, THE SCHEMA NAME schema-name1 PROVIDED FOR THE SPECIFIC NAME DOES NOT MATCH
			THE SCHEMA NAME schema-name2 OF THE FUNCTION
	-456 IN CREATE FUNCTION FOR function-name, THE SPECIFIC NAME specific-name ALREADY EXISTS IN THE SCHEMA		-456 IN CREATE FUNCTION FOR function-name, THE SPECIFIC NAME specific-name ALREADY EXISTS IN THE SCHEMA
	-457 A FUNCTION OR DISTINCT TYPE CANNOT BE CALLED name SINCE IT IS RESERVED FOR SYSTEM USE		-457 A FUNCTION OR DISTINCT TYPE CANNOT BE CALLED name SINCE IT IS RESERVED FOR SYSTEM USE
	-458 IN A REFERENCE TO FUNCTION function-name BY SIGNATURE, A MATCHING FUNCTION COULD NOT BE FOUND		-458 IN A REFERENCE TO FUNCTION function-name BY SIGNATURE, A MATCHING FUNCTION COULD NOT BE FOUND
	-461 A VALUE WITH DATA TYPE source-data-type CANNOT BE CAST TO TYPE target-data-type		-461 A VALUE WITH DATA TYPE source-data-type CANNOT BE CAST TO TYPE target-data-type
	-463 EXTERNAL ROUTINE routine-name (SPECIFIC NAME specific-name) HAS RETURNED AN INVALID SQLSTATE sqlstate, WITH DIAGNOSTIC TEXT text		-463 EXTERNAL ROUTINE routine-name (SPECIFIC NAME specific-name) HAS RETURNED AN INVALID SQLSTATE sqlstate, WITH
			DIAGNOSTIC TEXT text
	-469 SQL CALL STATEMENT MUST SPECIFY AN OUTPUT HOST VARIABLE FOR PARAMETER number		-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.		-470 SQL CALL STATEMENT SPECIFIED A NULL VALUE FOR INPUT PARAMETER number, BUT THE STORED PROCEDURE DOES NOT SUPPORT
			NULL VALUES.
	-471 INVOCATION OF FUNCTION OR PROCEDURE name FAILED DUE TO REASON rc		-471 INVOCATION OF FUNCTION OR PROCEDURE name FAILED DUE TO REASON rc
	-472 CURSOR cursor-name WAS LEFT OPEN BY EXTERNAL FUNCTION function-name (SPECIFIC NAME specific-name)		-472 CURSOR cursor-name WAS LEFT OPEN BY EXTERNAL FUNCTION function-name (SPECIFIC NAME specific-name)
	-473 A USER DEFINED DATA TYPE CANNOT BE CALLED THE SAME NAME AS A SYSTEM PREDEFINED TYPE (BUILT-IN TYPE)		-473 A USER DEFINED DATA TYPE CANNOT BE CALLED THE SAME NAME AS A SYSTEM PREDEFINED TYPE (BUILT-IN TYPE)
	-475 THE RESULT TYPE type -1 OF THE SOURCE FUNCTION CANNOT BE CAST TO THE RETURNS TYPE type -2 OF THE USER-DEFINED FUNCTION function-name		-475 THE RESULT TYPE type -1 OF THE SOURCE FUNCTION CANNOT BE CAST TO THE RETURNS TYPE type -2 OF THE USER-DEFINED
			FUNCTION function-name
	-476 REFERENCE TO FUNCTION function-name WAS NAMED WITHOUT A SIGNATURE, BUT THE FUNCTION IS NOT UNIQUE WITHIN ITS SCHEMA		-476 REFERENCE TO FUNCTION function-name WAS NAMED WITHOUT A SIGNATURE, BUT THE FUNCTION IS NOT UNIQUE WITHIN ITS SCHEMA
	-478 DROP OR REVOKE ON OBJECT TYPE type1 CANNOT BE PROCESSED BECAUSE OBJECT name OF TYPE type2 IS DEPENDENT ON IT		-478 DROP OR REVOKE ON OBJECT TYPE type1 CANNOT BE PROCESSED BECAUSE OBJECT name OF TYPE type2 IS DEPENDENT ON IT
	-480 THE PROCEDURE procedure-name HAS NOT YET BEEN CALLED		-480 THE PROCEDURE procedure-name HAS NOT YET BEEN CALLED
	-482 The procedure returned no locators.		-482 The procedure returned no locators.
	-483 IN CREATE FUNCTION FOR function-name STATEMENT, THE NUMBER OF PARAMETERS DOES NOT MATCH THE NUMBER OF PARAMETERS OF THE SOURCE FUNCTION		-483 IN CREATE FUNCTION FOR function-name STATEMENT, THE NUMBER OF PARAMETERS DOES NOT MATCH THE NUMBER OF PARAMETERS
	-487 object-type object-name ATTEMPTED TO EXECUTE AN SQL STATEMENT WHEN THE DEFINITION OF THE FUNCTION OR PROCEDURE DID NOT SPECIFY THIS ACTION		OF THE SOURCE FUNCTION
	-490 NUMBER number DIRECTLY SPECIFIED IN AN SQL STATEMENT IS OUTSIDE THE RANGE OF ALLOWABLE VALUES IN THIS CONTEXT (minval, maxval)		-487 object-type object-name ATTEMPTED TO EXECUTE AN SQL STATEMENT WHEN THE DEFINITION OF THE FUNCTION OR PROCEDURE DID
	-491 CREATE STATEMENT FOR USER-DEFINED FUNCTION function-name MUST HAVE A RETURNS CLAUSE AND: THE EXTERNAL CLAUSE WITH OTHER REQUIRED KEYWORDS; THE RETURN STATEMENT AND PARAMETER NAMES; OR THE SOURCE CLAUSE		NOT SPECIFY THIS ACTION
	-492 THE CREATE FUNCTION FOR function-name HAS A PROBLEM WITH PARAMETER NUMBER number. IT MAY INVOLVE A MISMATCH WITH A SOURCE FUNCTION		-490 NUMBER number DIRECTLY SPECIFIED IN AN SQL STATEMENT IS OUTSIDE THE RANGE OF ALLOWABLE VALUES IN THIS CONTEXT
	-495 ESTIMATED PROCESSOR COST OF estimate-amount1 PROCESSOR SECONDS (estimate-amount2 SERVICE UNITS) IN COST CATEGORY cost-category EXCEEDS A RESOURCE LIMIT ERROR THRESHOLD OF limit- amount SERVICE UNITS		(minval, maxval)
			-491 CREATE STATEMENT FOR USER-DEFINED FUNCTION function-name MUST HAVE A RETURNS CLAUSE AND: THE EXTERNAL CLAUSE WITH
			OTHER REQUIRED KEYWORDS; THE RETURN STATEMENT AND PARAMETER NAMES; OR THE SOURCE CLAUSE
			-492 THE CREATE FUNCTION FOR function-name HAS A PROBLEM WITH PARAMETER NUMBER number. IT MAY INVOLVE A MISMATCH WITH A
			SOURCE FUNCTION
			-495 ESTIMATED PROCESSOR COST OF estimate-amount1 PROCESSOR SECONDS (estimate-amount2 SERVICE UNITS) IN COST CATEGORY
			cost-category EXCEEDS A RESOURCE LIMIT ERROR THRESHOLD OF limit- amount SERVICE UNITS
	-496 THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT REFERENCES A RESULT SET THAT WAS NOT CREATED BY THE CURRENT SERVER		-496 THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT REFERENCES A RESULT SET THAT WAS NOT CREATED BY THE CURRENT SERVER
	-497 THE MAXIMUM LIMIT OF INTERNAL IDENTIFIERS HAS BEEN EXCEEDED FOR DATABASE database-name		-497 THE MAXIMUM LIMIT OF INTERNAL IDENTIFIERS HAS BEEN EXCEEDED FOR DATABASE database-name

wikademia>JohnsonCharlesD: /* Negative (through -251) */

2009-02-25T18:36:57Z

Negative (through -251)

← Older revision		Revision as of 18:36, 25 February 2009
Line 47:		Line 47:
	-113 Invalid Character found in Name: "NAME", Reason Code- "REASON-CODE".		-113 Invalid Character found in Name: "NAME", Reason Code- "REASON-CODE".
	-114 THE LOCATION NAME location DOES NOT MATCH THE CURRENT SERVER		-114 THE LOCATION NAME location DOES NOT MATCH THE CURRENT SERVER
	-115 A PREDICATE Is Invalid because the comparison operator "OPERATOR" is followed by a 'parenthesized list' or "By Any" or "All" with out a Sub-query		-115 A PREDICATE Is Invalid because the comparison operator "OPERATOR" is followed by a 'parenthesized list' or "By Any"
			or "All" with out a Sub-query
	-117 The number of values in the INSERT does not match the number of columns.		-117 The number of values in the INSERT does not match the number of columns.
	-118 THE OBJECT TABLE OR VIEW OF THE DELETE OR UPDATE STATEMENT IS ALSO IDENTIFIED IN A FROM CLAUSE		-118 THE OBJECT TABLE OR VIEW OF THE DELETE OR UPDATE STATEMENT IS ALSO IDENTIFIED IN A FROM CLAUSE
Line 53:		Line 54:
	-120 A WHERE CLAUSE, SET CLAUSE, VALUES CLAUSE, OR A SET HOST-VARIABLE STATEMENT INCLUDES A COLUMN FUNCTION		-120 A WHERE CLAUSE, SET CLAUSE, VALUES CLAUSE, OR A SET HOST-VARIABLE STATEMENT INCLUDES A COLUMN FUNCTION
	-121 THE COLUMN name IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE OR SET TRANSITION VARIABLE STATEMENT		-121 THE COLUMN name IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE OR SET TRANSITION VARIABLE STATEMENT
	-122 A SELECT STATEMENT WITH NO GROUP BY CLAUSE CONTAINS A COLUMN NAME AND A COLUMN FUNCTION IN THE SELECT CLAUSE OR A COLUMN NAME IS CONTAINED IN THE SELECT CLAUSE BUT NOT IN THE GROUP BY CLAUSE		-122 A SELECT STATEMENT WITH NO GROUP BY CLAUSE CONTAINS A COLUMN NAME AND A COLUMN FUNCTION IN THE SELECT CLAUSE OR A
			COLUMN NAME IS CONTAINED IN THE SELECT CLAUSE BUT NOT IN THE GROUP BY CLAUSE
	-123 THE PARAMETER IN POSITION n IN THE FUNCTION name MUST BE A CONSTANT OR KEYWORD		-123 THE PARAMETER IN POSITION n IN THE FUNCTION name MUST BE A CONSTANT OR KEYWORD
	-125 AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A COLUMN OF THE RESULT		-125 AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A COLUMN OF THE RESULT
Line 60:		Line 62:
	-128 INVALID USE OF NULL IN A PREDICATE		-128 INVALID USE OF NULL IN A PREDICATE
	-129 THE STATEMENT CONTAINS TOO MANY TABLE NAMES		-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		-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		-131 STATEMENT WITH LIKE PREDICATE HAS INCOMPATIBLE DATA TYPES
	-132 AN OPERAND OF value IS NOT VALID		-132 AN OPERAND OF value IS NOT VALID
	-133 A COLUMN FUNCTION IN A SUBQUERY OF A HAVING CLAUSE IS INVALID BECAUSE ALL COLUMN REFERENCES IN ITS ARGUMENT ARE NOT CORRELATED TO THE GROUP BY RESULT THAT THE HAVING CLAUSE IS APPLIED TO		-133 A COLUMN FUNCTION IN A SUBQUERY OF A HAVING CLAUSE IS INVALID BECAUSE ALL COLUMN REFERENCES IN ITS ARGUMENT ARE
			NOT CORRELATED TO THE GROUP BY RESULT THAT THE HAVING CLAUSE IS APPLIED TO
	-134 IMPROPER USE OF LONG STRING COLUMN column-name OR AN EXPRESSION THAT RESOLVES TO A LONG STRING		-134 IMPROPER USE OF LONG STRING COLUMN column-name OR AN EXPRESSION THAT RESOLVES TO A LONG STRING
	-136 SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS GREATER THAN 4000 BYTES		-136 SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS GREATER THAN 4000 BYTES
Line 72:		Line 76:
	-147 ALTER FUNCTION function-name FAILED BECAUSE SOURCE FUNCTIONS CANNOT BE ALTERED		-147 ALTER FUNCTION function-name FAILED BECAUSE SOURCE FUNCTIONS CANNOT BE ALTERED
	-148 THE SOURCE TABLE source-name CANNOT BE RENAMED OR ALTERED		-148 THE SOURCE TABLE source-name CANNOT BE RENAMED OR ALTERED
	-150 THE OBJECT OF THE INSERT, DELETE, OR UPDATE STATEMENT IS A VIEW OR TRANSITION TABLE FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED		-150 THE OBJECT OF THE INSERT, DELETE, OR UPDATE STATEMENT IS A VIEW OR TRANSITION TABLE FOR WHICH THE REQUESTED
	-151 THE UPDATE STATEMENT IS INVALID BECAUSE THE CATALOG DESCRIPTION OF COLUMN column-name INDICATES THAT IT CANNOT BE UPDATED		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		-152 THE DROP clause CLAUSE IN THE ALTER STATEMENT IS INVALID BECAUSE constraint-name IS A constraint-type
	-153 THE STATEMENT IS INVALID BECAUSE THE VIEW OR TABLE DEFINITION DOES NOT INCLUDE A UNIQUE NAME FOR EACH COLUMN		-153 THE STATEMENT IS INVALID BECAUSE THE VIEW OR TABLE DEFINITION DOES NOT INCLUDE A UNIQUE NAME FOR EACH COLUMN
Line 79:		Line 85:
	-156 THE STATEMENT DOES NOT IDENTIFY A TABLE		-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.		-157 ONLY A TABLE NAME CAN BE SPECIFIED IN A FOREIGN KEY CLAUSE. object-name IS NOT THE NAME OF A TABLE.
	-158 THE NUMBER OF COLUMNS SPECIFIED FOR THE VIEW IS NOT THE SAME AS THE NUMBER OF COLUMNS SPECIFIED BY THE SELECT CLAUSE, OR THE NUMBER OF COLUMNS SPECIFIED IN THE CORRELATION CLAUSE IN A FROM CLAUSE IS NOT THE SAME AS THE NUMBER OF COLUMNS IN THE CORRESPONDING TABLE, VIEW, TABLE EXPRESSION, OR TABLE FUNCTION		-158 THE NUMBER OF COLUMNS SPECIFIED FOR THE VIEW IS NOT THE SAME AS THE NUMBER OF COLUMNS SPECIFIED BY THE SELECT
			CLAUSE, OR THE NUMBER OF COLUMNS SPECIFIED IN THE CORRELATION CLAUSE IN A FROM CLAUSE IS NOT THE SAME AS THE
			NUMBER OF COLUMNS IN THE CORRESPONDING TABLE, VIEW, TABLE EXPRESSION, OR TABLE FUNCTION
	-159 DROP OR COMMENT ON object IDENTIFIES A(N) object-type1 RATHER THAN A(N) object-type2		-159 DROP OR COMMENT ON object IDENTIFIES A(N) object-type1 RATHER THAN A(N) object-type2
	-160 THE WITH CHECK OPTION CANNOT BE USED FOR THE SPECIFIED VIEW		-160 THE WITH CHECK OPTION CANNOT BE USED FOR THE SPECIFIED VIEW
Line 94:		Line 102:
	-185 THE LOCAL FORMAT OPTION HAS BEEN USED WITH A DATE OR TIME AND NO LOCAL EXIT HAS BEEN INSTALLED		-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		-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		-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		-188 THE STRING REPRESENTATION OF A NAME IS INVALID
	-189 CCSID ccsid IS UNKNOWN OR INVALID FOR THE DATA TYPE OR SUBTYPE		-189 CCSID ccsid IS UNKNOWN OR INVALID FOR THE DATA TYPE OR SUBTYPE
Line 108:		Line 117:
	-208 THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN name IS NOT PART OF THE RESULT TABLE		-208 THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN name IS NOT PART OF THE RESULT TABLE
	-212 name IS SPECIFIED MORE THAN ONCE IN THE REFERENCING CLAUSE OF A TRIGGER DEFINITION		-212 name IS SPECIFIED MORE THAN ONCE IN THE REFERENCING CLAUSE OF A TRIGGER DEFINITION
	-214 AN EXPRESSION IN THE FOLLOWING POSITION, OR STARTING WITH position-or-expression-start IN THE clause-type CLAUSE IS NOT VALID. REASON CODE = reason-code		-214 AN EXPRESSION IN THE FOLLOWING POSITION, OR STARTING WITH position-or-expression-start IN THE clause-type CLAUSE
			IS NOT VALID. REASON CODE = reason-code
	-216 Not the same number of expressions on both sides of the comparison in a SELECT .		-216 Not the same number of expressions on both sides of the comparison in a SELECT .
	-219 THE REQUIRED EXPLANATION TABLE table-name DOES NOT EXIST		-219 THE REQUIRED EXPLANATION TABLE table-name DOES NOT EXIST