SQL Negative Return Codes

The SQL return codes are listed here numerically, you may browse through them or you may enter the code you are looking for and press the enter key to go directly to the return code description.

The codes are broken up into numeric ranges to make the HTML documents smaller and thus load faster. They are basically divided into the groups by the hundreds digit, (ie 0-99, 100-199 and etc.). However each section has the index for all the negative return codes.

-007 -010 -029 -060 -084 -101 -102 -103 -104 -105 -107 -109 -110 -111 -112 -113 -115 -117 -118 -119 -120 -121 -122 -125 -126 -127 -128 -129 -130 -131 -132 -133 -134 -136 -137 -138 -144 -150 -151 -153 -154 -156 -157 -158 -159 -160 -161 -164 -170 -171 -180 -181 -182 -183 -184 -185 -186 -187 -188 -189 -191 -198 -199 -203 -204 -205 -206 -207 -208 -219 -220 -221 -250 -251 -301 -302 -303 -304 -305 -309 -311 -312 -313 -314 -330 -331 -332 -333 -401 -402 -404 -405 -406 -407 -408 -409 -410 -411 -412 -414 -415 -416 -417 -418 -419 -421 -426 -427 -501 -502 -503 -504 -507 -508 -509 -510 -511 -512 -513 -514 -516 -517 -518 -519 -525 -530 -531 -532 -533 -534 -535 -536 -537 -538 -539 -540 -542 -551 -552 -553 -554 -555 -556 -557 -558 -559 -567 -571 -601 -602 -603 -604 -607 -612 -613 -614 -615 -616 -618 -619 -620 -621 -622 -623 -624 -625 -626 -627 -628 -629 -631 -932 -633 -634 -635 -636 -637 -638 -639 -644 -646 -647 -652 -653 -660 -661 -662 -663 -665 -666 -667 -668 -669 -670 -671 -676 -677 -678 -679 -680 -681 -682 -683 -684 -685 -686 -687 -688 -689 -690 -691 -692 -693 -694 -715 -716 -717 -718 -719 -720 -721 -722 -726 -730 -731 -732 -733 -734 -735 -736 -737 -752 -802 -803 -804 -805 -807 -811 -812 -815 -817 -818 -819 -820 -822 -840 -900 -901 -902 -904 -905 -906 -907 -908 -909 -910 -911 -913 -917 -918 -922 -923 -924 -925 -926 -927 -950
-30000 -30020 -30021 -30030 -30040 -30041 -30050 -30051 -30052 -30053 -30060 -30061 -30070 -30071 -30072 -30073 -30074 -30080 -30090

SQL Code -007

Explanation: The specified 'character' is not a valid character in SQL statements.

System Action: The statement cannot be executed.

Programmer Response: Correct the syntax and resubmit the statement. Refer to Chapter 3 of SQL Reference for information about the valid SQL character set.

SQLSTATE: 37501


SQL Code -010 THE STRING CONSTANT BEGINNING string IS NOT TERMINATED

Explanation: The statement contains a string constant, beginning with 'string', that is not terminated properly.

System Action: The statement cannot be executed.

Programmer Response: Examine the statement for missing quotation marks or apostrophes in the indicated string constant.

SQLSTATE: 37503


SQL Code -029 INTO CLAUSE REQUIRED

Explanation: SELECT statements embedded in an application program must have an INTO clause to denote where the results of the SELECT are to be placed. Dynamic SELECT statements do not permit the INTO clause.

System Action: The statement cannot be executed.

Programmer Response: Add the INTO clause to the SELECT statement and precompile the application program again. precompile the application program again.

SQLSTATE: 37501


SQL Code -060 INVALID type SPECIFICATION : spec

Explanation: 'type' is either LENGTH or SCALE. 'spec' is the specified length or scale. Length or scale must be specified by an unsigned integer constant and the value must be in the range allowed by the data type.

System Action: The statement cannot be executed.

Programmer Response: Correct the statement. Refer to Chapter 4 of SQL Reference for rules for length and scale.

SQLSTATE: 53015


SQL Code -084 UNACCEPTABLE SQL STATEMENT

Explanation: This SQL statement is unacceptable to DB2. One of the following has occurred:

  • An attempt has been made to PREPARE or EXECUTE IMMEDIATE a SQL statement that cannot be prepared; refer to the proper SQL statement in SQL Reference
  • The embedded SQL statement is not an SQL statement supported by DB2.

System Action: The statement cannot be executed.

Programmer Response: If the situation involves an SQL statement that cannot be prepared, the problem is in the source of the SQL statement, not the application program. Thus, no action is necessary unless the source of the SQL statement is the application program itself.

If the situation involves a SQL statement that is not supported by DB2, remove it from the application program and precompile again.

SQLSTATE: 37512