A large collection of error messages in the IBM DB2 database!

This article mainly describes the summary of errors in the IBM DB2 database. If you are curious about the errors in the IBM DB2 database, the following articles will unveil its secrets. The following is a detailed description of the article. I hope you can learn from it.

IBM, database, summary IBM, database, summary

Sqlcode sqlstate description

00000 SQL statement completed successfully

01xxx SQL statement completed successfully, but warning

+ 012 01545 undefined column names are interpreted as a reference with mutual relations.

+ 098 01568 use a semicolon to end a dynamic SQL statement

+ 100 02000 No rows meeting SQL statements found

+ 110 01561 update operations on tables defined by data capture cannot be sent to the original Subsystem

+ 111 01590 set the SUBPAGES statement for the 2-type index

+ 117 01525 the number of values to be inserted is not equal to the number of columns in the inserted Table

+ 162 01514 the specified tablespace is set to check the pending status.

+ 203 01552 use a non-unique name to solve the naming restriction Column

+ 204 the objects named in 01532 are not defined in DB2

+ 206 the column named in 01533 does not exist in any table specified in the SQL statement.

Error message of the IBM DB2 database + 218 01537 because the SQL statement references a remote object, the SQL statement cannot be executed to EXPLAIN

+ 219 The plan table named in 01532 does not exist.

+ 220 01546 incorrectly define the plan table and check the definition of the named Column

+ 236 the value of SQLN in SQLDA should be at least as large as the number of columns described.

+ 237 01594 at least one described column should be of the single value type. Therefore, the extended SQLVAR entry requires additional space.

+ 238 01005 at least one descriptive column should be a LOB, so the extended SQLVAR entry requires additional space.

+ 239 01005 at least one descriptive column should be of the single value type. Therefore, the extended SQLVAR entry requires additional space.

+ 304 01515 the value cannot be assigned to the host variable because it is no longer within the range of data types

+ 331 01520 a string that cannot be translated, so it is set to NULL

+ 339 01569 due to the connectivity with the DB2 2.2 subsystem, character conversion problems may exist.

+ 394 01629 use the optimization prompt to select the access path

+ 395 01628 an invalid optimization prompt is set. The cause code specifies the reason and ignores the optimization prompt.

+ 402 unknown location

+ 403 01522 the creat alias object does not exist locally

+ 434 01608 in the future releases of DB2, the specified features will not be supported. IBM recommends that you stop using these features.

+ 445 01004 value intercepted by the CAST Function

+ 462 01Hxx warning issued by user-defined functions or stored procedures

+ 464 the Stored Procedure named in 01609 exceeds the limit on the number of query result sets it may return.

+ 466 01610 specify the number of query result sets returned by the named stored procedure. Completed Successfully

+ 494 01614 the number of result sets returned by stored procedures exceeds the number of result set LOCATORS specified by the associate locators statement.

+ 495 01616 warning is issued because the cost estimate of the SQL collapsed exceeds the warning threshold specified in ELST

+ 535 01591 request a primary key for location update, or request a deletion operation for a table using self-extracting Constraints

IBM DB2 database error message + 541 01543 naming rules is a duplicate reference Constraint

+ 551 the authorization ID named in 01548 lacks the permission to perform the naming operation on the named DB2 object.

+ 552 the authorization ID named in 01542 does not have the permission to perform the naming operation

+ 558 01516 the PUBLIC account has been authorized, so the with grant option is unavailable.

+ 561 01523 For alter references index and TRIGGER privileges, public at all location is invalid

+ 562 01560 one or more privileges are ignored because GRANTEE already has these privileges

+ 585 01625 the mode name is specified more than once

+ 599 01596 is not a comparison function for long character data types BLOB, CLOB, and DBCLOB.

+ 610 01566 because an index specified as defer yes is created, the specified object is in the PENDING state, or

Alter index changes the range of key values, so the specified object is in PENDING state.

+ 625 01518 because the primary index is deleted, the table definition is marked incomplete.

+ 626 01529 deleted the index with enhanced UNIQUE constraints, and the uniqueness is not enhanced

+ 645 01528 The where not null is ignored because the created index does NOT contain NULL.

+ 650 01538 you cannot change or create a named table as a subordinate table

+ 653 01551 the specified partition index has not been created in the specified partition table space, so the partition index is not available

+ 655 01597 specify a specific or non-specific volume ID for the CREATE or alter stogroup statement. In a newer version of DB2, version 6

Later) They will not be supported

+ 658 01600 when a Directory Index is created, the SUBPAGES statement cannot be specified. SUBPAGES will be ignored and the default value is 1.

+ 664 01540 the limit keyword of the partition index exceeds the maximum value.

+ 738 01530 changes to named objects may be the same as changes to objects in Read-Only systems.

+ 799 if the specified register referenced in the SET statement does not exist, the SET Request is ignored.

+ 802 01519 data overflow or data exception errors caused by Division exceptions

+ 806 01553 ISOLATIONRR) conflict with LOCKSIZE PAGE

+ 807 01554 overflow caused by decimal Multiplication

+ 863 01539 successful connection, but only SBCS is supported

+ 2000 56094 if SUBPAGES are not equal to 1, the type 1 index cannot become a buffer pool group dependent in the data sharing environment.

+ 2002 01624 because the specified buffer pool does not allow ultra-high-speed caching, GNPCACHE is specified to be ignored

+ 2007 01602 because the "prompt (hiats)" is disabled for the DB2 subsystem parameters, the optimization prompt cannot be specified.

+ 30100 01558 distributed protocol error detected, providing the original SQLCODE and SQLSTATE

-007 42601 the SQL statement contains invalid characters.

-010 42603 The String constant is terminated abnormally. The missing quotation marks are checked.

-029 42601 the INTO statement is required.

-060 42815 the length or scalar specification of a specific data type is invalid

-084 42612 the SQL statement cannot be executed because it is invalid for dynamic SQL statements or for OS/390 DB2.

-097 42601 the long varchar or

LONGVARGRAPHIC

-101 54001 the SQL statement exceeds the defined DB2 limit. For example, the number of tables is too large and the number of bytes in the statement is too large.

-102 54002 The String constant is too long

-103 42604 invalid math text

-104 42601 the SQL statement encountered an invalid symbol.

-105 42604 invalid string format; Generally, an incorrect format is referenced.

-107 42622 the object name is too long

-108 The name specified in the 42601 RENAME statement is incorrect. You cannot use a qualified word.

-109 42601 an invalid statement is specified. For example, create view cannot contain an order by statement.

IBM DB2 database error message-110 42606 encountering invalid hexadecimal text

-111 42901 the specified column function does not provide a column name

-112 42607 the column function syntax is invalid. The column function cannot run on top of other column functions.

-113 42602 invalid characters

-114 42961 the location name of the statement must match the current server, but does not match

-115 42601 an invalid predicate is encountered because the comparison operator is not accompanied by an expression or list.

-117 42802 the number of values to be inserted is different from the number of columns in the inserted row.

-118 42902 invalid table and view names in data modification statements (UPDATE or DELETE) and FROM statements

-119 the column list in the HAVING statement does not match the column list in the group by statement.

-120 42903 do not allow WHERE statements, SET statements, VALUES statements, or set assignment statements to reference column Functions

-121 42701 in an INSERT or UPDATE statement, a column is illegally referenced twice.

-122 42803 the column function is invalid. Because all columns that are not used in a column function are no longer in the group by statement.

-123 42601 the parameter at a specific position must be a constant or a keyword

-In the 125 42805 order by statement, an invalid number is specified. The number must be smaller than 1 or greater than the selected number of columns.

-126 42829 the order by statement cannot be specified for an UPDATE statement

-127 42905 DISTINCT can be specified only once in sub-selection

-128 42601 improper use of NULL in SQL predicates

-129 54004 SQL statements contain more than 15 tables

-130 22019 the ESCAPE statement must be a character

The above content is a comprehensive summary of errors in the IBM DB2 database. I hope you will find some gains.