Sql error 212

You try to create an index but the sql fails with these errors: -212 Cannot add index. -131 ISAM error: no free disk space.

Problem

You try to create an index but the sql fails with these errors:

-212 Cannot add index.

-131 ISAM error: no free disk space.

Symptom

You try to create an index but the sql fails with these errors:

-212 Cannot add index.

-131 ISAM error: no free disk space.

Cause

There is not sufficient disk space in the dbspace or dbspaces to create the index.

Diagnosing The Problem

Determine in which dbspace or dbspaces the index will be created. If a table is not fragmented, then an index will be created in the same dbspace as the table. If a table is fragmented, then an index will follow the table’s fragmentation schema. If an index is fragmented, then check the CREATE INDEX sql used to determine which dbspaces are used. onstat -d output will help you determine which dbspace or dbspaces do not have enough disk space for the creation of the index.

See the Related information section for help.

Resolving The Problem

  • Add more space to the dbspace or dbspaces.
  • Choose another dbspace or dbspaces using the IN clause in the CREATE INDEX syntax.

See the Related information section for several links to information that will assist you in successfully creating an index when dealing with errors 212 and 131.

[{«Product»:{«code»:»SSGU8G»,»label»:»Informix Servers»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:null,»Platform»:[{«code»:»PF002″,»label»:»AIX»},{«code»:»PF010″,»label»:»HP-UX»},{«code»:»PF016″,»label»:»Linux»},{«code»:»PF022″,»label»:»OS X»},{«code»:»PF027″,»label»:»Solaris»},{«code»:»PF033″,»label»:»Windows»}],»Version»:»11.5;11.7;12.1″,»Edition»:»»,»Line of Business»:{«code»:»»,»label»:»»}}]



DB2/ Negative SQLCODEs


SQL return codes that are preceded by a minus sign (-) indicate that the SQL statement execution was unsuccessful.


DB2 SQL-Error: -007 SQLState: 42601
Short Description: STATEMENT CONTAINS THE ILLEGAL CHARACTER
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 2 of DB2 SQL Reference for information about the valid SQL character set.


DB2 SQL-Error: -010 SQLState: 42603
Short Description: THE STRING CONSTANT BEGINNING IS NOT TERMINATED
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.


DB2 SQL-Error: -029 SQLState: 42601
Short Description: INTO CLAUSE REQUIRED
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.


SQL0051 SQLCODE -51 SQLSTATE 3C000
Explanation: Cursor or procedure &1 previously declared.


DB2 SQL-Error: -58 SQLState: 428F2
Short Description: A RETURN SQL T RETURN SQL INTEGER
A RETURN statement is specified in the SQL procedure with a value or expression that is not of the INTEGER data type. System action: The statement cannot be processed. User response: Specify a value on the RETURN statement that has a data type of INTEGER.




SQL0060 SQLCODE -60 SQLSTATE 42815
Explanation: Value &3 for argument &1 of &2 function not valid.


SQL0078 SQLCODE -78 SQLSTATE 42629
Explanation: Parameter name required for routine &1 in &2.


SQL0080 SQLCODE -80 SQLSTATE 42978
Explanation: Indicator variable &1 not SMALLINT type.


SQL0084 SQLCODE -84 SQLSTATE 42612
Explanation: SQL statement not allowed.


SQL0090 SQLCODE -90 SQLSTATE 42618
Explanation: Host variable not permitted here.


SQL0097 SQLCODE -97 SQLSTATE 42601
Explanation: Use of data type not valid.


SQL0099 SQLCODE -99 SQLSTATE 42992
Explanation: Operator in join condition not valid.


SQL0101 SQLCODE -101 SQLSTATE 54001, 54010, 54011
Explanation: SQL statement too long or complex.


SQL0102 SQLCODE -102 SQLSTATE 54002
Explanation: String constant beginning with &1 too long.


SQL0103 SQLCODE -103 SQLSTATE 42604
Explanation: Numeric constant &1 not valid.


SQL0104 SQLCODE -104 SQLSTATE 42601
Explanation: Token &1 was not valid. Valid tokens: &2.


SQL0105 SQLCODE -105 SQLSTATE 42604
Explanation: Mixed or graphic string constant not valid.


SQL0106 SQLCODE -106 SQLSTATE 42611
Explanation: Precision specified for FLOAT column not valid.


SQL0107 SQLCODE -107 SQLSTATE 42622
Explanation: &1 too long. Maximum &2 characters.


SQL0109 SQLCODE -109 SQLSTATE 42601
Explanation: &1 clause not allowed.


SQL0110 SQLCODE -110 SQLSTATE 42606
Explanation: Hexadecimal constant beginning with &1 not valid.


SQL0112 SQLCODE -112 SQLSTATE 42607
Explanation: Argument of function &1 is another function.


SQL0113 SQLCODE -113 SQLSTATE 28000, 2E000, 42602
Explanation: Name &1 not allowed.


SQL0114 SQLCODE -114 SQLSTATE 42961
Explanation: Relational database &1 not the same as current server &2.


SQL0115 SQLCODE -115 SQLSTATE 42601
Explanation: Comparison operator &1 not valid.


SQL0117 SQLCODE -117 SQLSTATE 42802
Explanation: Statement inserts wrong number of values.


SQL0118 SQLCODE -118 SQLSTATE 42902
Explanation: Table &1 in &2 also specified in a FROM clause.


SQL0119 SQLCODE -119 SQLSTATE 42803
Explanation: Column &1 in HAVING clause not in GROUP BY.


SQL0120 SQLCODE -120 SQLSTATE 42903
Explanation: Use of column function &2 not valid.


SQL0121 SQLCODE -121 SQLSTATE 42701
Explanation: Duplicate column name &1 in INSERT or UPDATE.


SQL0122 SQLCODE -122 SQLSTATE 42803
Explanation: Column specified in SELECT list not valid.


SQL0125 SQLCODE -125 SQLSTATE 42805
Explanation: ORDER BY column number &1 not valid.


SQL0128 SQLCODE -128 SQLSTATE 42601
Explanation: Use of NULL is not valid.


SQL0129 SQLCODE -129 SQLSTATE 54004
Explanation: Too many tables in SQL statement.


SQL0130 SQLCODE -130 SQLSTATE 22019, 22025
Explanation: Escape character &1 or LIKE pattern not valid.


SQL0131 SQLCODE -131 SQLSTATE 42818
Explanation: Operands of LIKE not compatible or not valid.


SQL0132 SQLCODE -132 SQLSTATE 42824
Explanation: LIKE predicate not valid.


SQL0133 SQLCODE -133 SQLSTATE 42906
Explanation: Operator on correlated column in SQL function not valid.


SQL0134 SQLCODE -134 SQLSTATE 42907
Explanation: Argument of function too long.


SQL0136 SQLCODE -136 SQLSTATE 54005
Explanation: ORDER BY or GROUP BY columns too long.


SQL0137 SQLCODE -137 SQLSTATE 54006
Explanation: Result too long.


SQL0138 SQLCODE -138 SQLSTATE 22011
Explanation: Argument &1 of SUBSTR function not valid.


SQL0144 SQLCODE -144 SQLSTATE 58003
Explanation: Section number not valid.


SQL0145 SQLCODE -145 SQLSTATE 55005
Explanation: Recursion not supported for an application server other than the AS/400 system.


SQL0150 SQLCODE -150 SQLSTATE 42807
Explanation: View or logical file &1 in &2 read-only.


SQL0151 SQLCODE -151 SQLSTATE 42808
Explanation: Column &1 in table &2 in &3 read-only.


SQL0152 SQLCODE -152 SQLSTATE 42809
Explanation: Constraint type not valid for constraint &1 in &2.


SQL0153 SQLCODE -153 SQLSTATE 42908
Explanation: Column list required for CREATE VIEW.


SQL0154 SQLCODE -154 SQLSTATE 42909
Explanation: UNION and UNION ALL for CREATE VIEW not valid.


SQL0156 SQLCODE -156 SQLSTATE 42809
Explanation: &1 in &2 not a table.


SQL0157 SQLCODE -157 SQLSTATE 42810
Explanation: View &1 in &2 not valid in FOREIGN KEY clause.


SQL0158 SQLCODE -158 SQLSTATE 42811
Explanation: Number of columns specified not consistent.


SQL0159 SQLCODE -159 SQLSTATE 42809
Explanation: &1 in &2 not correct type.


SQL0160 SQLCODE -160 SQLSTATE 42813
Explanation: WITH CHECK OPTION not allowed for view &1 in &2.


SQL0161 SQLCODE -161 SQLSTATE 44000
Explanation: INSERT/UPDATE not allowed due to WITH CHECK OPTION.


SQL0170 SQLCODE -170 SQLSTATE 42605
Explanation: Number of arguments for function &1 not valid.


SQL0171 SQLCODE -171 SQLSTATE 42815
Explanation: Argument &1 of function &2 not valid.


SQL0175 SQLCODE -175 SQLSTATE 58028
Explanation: COMMIT failed.


SQL0180 SQLCODE -180 SQLSTATE 22007
Explanation: Syntax of date, time, or timestamp value not valid.


SQL0181 SQLCODE -181 SQLSTATE 22007
Explanation: Value in date, time, or timestamp string not valid.


SQL0182 SQLCODE -182 SQLSTATE 42816
Explanation: A date, time, or timestamp expression not valid.


SQL0183 SQLCODE -183 SQLSTATE 22008
Explanation: The result of a date or timestamp expression not valid.


SQL0184 SQLCODE -184 SQLSTATE 42610
Explanation: Parameter marker not valid in expression.


SQL0187 SQLCODE -187 SQLSTATE 42816
Explanation: Use of labeled duration is not valid.


SQL0188 SQLCODE -188 SQLSTATE 22503, 28000, 2E000
Explanation: &1 is not a valid string representation of an authorization name or a relational database name.


SQL0189 SQLCODE -189 SQLSTATE 22522
Explanation: Coded Character Set Identifier &1 is not valid.


SQL0190 SQLCODE -190 SQLSTATE 42837
Explanation: Attributes of column &3 in &1 in &2 not compatible.


SQL0191 SQLCODE -191 SQLSTATE 22504
Explanation: MIXED data not properly formed.


SQL0192 SQLCODE -192 SQLSTATE 42937
Explanation: Argument of TRANSLATE function not valid.


SQL0194 SQLCODE -194 SQLSTATE 42848
Explanation: KEEP LOCKS not allowed.


SQL0195 SQLCODE -195 SQLSTATE 42814
Explanation: Last column of &1 in &2 cannot be dropped.


SQL0196 SQLCODE -196 SQLSTATE 42817
Explanation: Column &3 in &1 in &2 cannot be dropped with RESTRICT.


SQL0197 SQLCODE -197 SQLSTATE 42877
Explanation: Column &1 cannot be qualified.


SQL0198 SQLCODE -198 SQLSTATE 42617
Explanation: SQL statement empty or blank.


SQL0199 SQLCODE -199 SQLSTATE 42601
Explanation: Keyword &1 not expected. Valid tokens: &2.


SQL0203 SQLCODE -203 SQLSTATE 42702
Explanation: Column &1 is ambiguous.


SQL0204 SQLCODE -204 SQLSTATE 42704
Explanation: &1 in &2 type *&3 not found.


SQL0205 SQLCODE -205 SQLSTATE 42703
Explanation: Column &1 not in table &2.


SQL0206 SQLCODE -206 SQLSTATE 42703
Explanation: Column &1 not in specified tables.


SQL0208 SQLCODE -208 SQLSTATE 42707
Explanation: ORDER BY column &1 not in results table.


SQL0212 SQLCODE -212 SQLSTATE 42712
Explanation: Duplicate table designator &1 not valid.


SQL0214 SQLCODE -214 SQLSTATE 42822
Explanation: ORDER BY expression is not valid.


SQL0221 SQLCODE -221 SQLSTATE 42873
Explanation: Number of rows &2 not valid.


SQL0225 SQLCODE -225 SQLSTATE 42872
Explanation: FETCH not valid; cursor &1 not declared with SCROLL.


SQL0226 SQLCODE -226 SQLSTATE 24507
Explanation: Current row deleted or moved for cursor &1.


SQL0227 SQLCODE -227 SQLSTATE 24513
Explanation: FETCH not valid, cursor &1 in unknown position.


SQL0228 SQLCODE -228 SQLSTATE 42620
Explanation: FOR UPDATE OF clause not valid with SCROLL for cursor &1.


SQL0231 SQLCODE -231 SQLSTATE 22006
Explanation: Position of cursor &1 not valid for FETCH of current row.


SQL0250 SQLCODE -250 SQLSTATE 42718
Explanation: Local relational database not defined in the directory.


SQL0251 SQLCODE -251 SQLSTATE 2E000, 42602
Explanation: Character in relational database name &1 is not valid.


SQL0255 SQLCODE -255 SQLSTATE 42999
Explanation: DB2 Multisystem query error.


SQL0256 SQLCODE -256 SQLSTATE 42998
Explanation: Constraint &1 in &2 not allowed on distributed file.


SQL0270 SQLCODE -270 SQLSTATE 42997
Explanation: Unique index not allowed.


SQL0301 SQLCODE -301 SQLSTATE 07006,42895
Explanation: Input host variable &2 or argument &1 not valid.


SQL0302 SQLCODE -302 SQLSTATE 22001, 22003, 22023, 22024
Explanation: Conversion error on input host variable &2.


SQL0303 SQLCODE -303 SQLSTATE 22001, 42806
Explanation: Host variable &1 not compatible with SELECT item.


SQL0304 SQLCODE -304 SQLSTATE 22003, 22023, 22504
Explanation: Conversion error in assignment to host variable &2.


SQL0305 SQLCODE -305 SQLSTATE 22002
Explanation: Indicator variable required.


SQL0306 SQLCODE -306 SQLSTATE 42863
Explanation: Undefined host variable in REXX.


SQL0311 SQLCODE -311 SQLSTATE 22501
Explanation: Length in a varying-length host variable not valid.


SQL0312 SQLCODE -312 SQLSTATE 42618
Explanation: Host variable &1 not defined or not usable.


SQL0313 SQLCODE -313 SQLSTATE 07001, 07004
Explanation: Number of host variables not valid.


SQL0328 SQLCODE -328 SQLSTATE 42996
Explanation: Column &1 not allowed in partitioning key.


SQL0329 SQLCODE -329 SQLSTATE 0E000
Explanation: The SET PATH name list is not valid.


SQL0330 SQLCODE -330 SQLSTATE 22021
Explanation: Character conversion cannot be performed.


SQL0331 SQLCODE -331 SQLSTATE 22021
Explanation: Character conversion cannot be performed.


SQL0332 SQLCODE -332 SQLSTATE 57017
Explanation: Character conversion between CCSID &1 and CCSID &2 not valid.


SQL0334 SQLCODE -334 SQLSTATE 22524
Explanation: Character conversion has resulted in truncation.


SQL0338 SQLCODE -338 SQLSTATE 42972
Explanation: JOIN expression not valid.


SQL0340 SQLCODE -340 SQLSTATE 42726
Explanation: Duplicate name &1 for common table expression.


SQL0341 SQLCODE -341 SQLSTATE 42835
Explanation: Cyclic references between common table expressions.


SQL0346 SQLCODE -346 SQLSTATE 42836
Explanation: Recursion not allowed for common table expressions.


SQL0350 SQLCODE -350 SQLSTATE 42962
Explanation: Column &1 is not valid as key field for index or constraint.


SQL0351 SQLCODE -351 SQLSTATE 56084
Explanation: The AR is not at the same level and DB2/400 cannot transform the data type to a compatible type.


SQL0352 SQLCODE -352 SQLSTATE 56084
Explanation: The AS is not at the same level and DB2/400 cannot transform the data type to a compatible type.


SQL0357 SQLCODE -357 SQLSTATE 57050
Explanation: File server &1 used in DataLink not currently available.


SQL0358 SQLCODE -358 SQLSTATE 428D1
Explanation: Error &1 occurred using DataLink data type.


SQL0392 SQLCODE -392 SQLSTATE 42855
Explanation: Assignment of LOB to specified host variable not allowed.


SQL0398 SQLCODE -398 SQLSTATE 428D2
Explanation: AS LOCATOR cannot be specified for a non-LOB parameter.


SQL0401 SQLCODE -401 SQLSTATE 42818
Explanation: Comparison operator &1 operands not compatible.


SQL0402 SQLCODE -402 SQLSTATE 42819
Explanation: &1 use not valid.


SQL0404 SQLCODE -404 SQLSTATE 22001
Explanation: Value for column &1 too long.


SQL0405 SQLCODE -405 SQLSTATE 42820
Explanation: Numeric constant &1 out of range.


SQL0406 SQLCODE -406 SQLSTATE 22003, 22023, 22504
Explanation: Conversion error on assignment to column &2.


SQL0407 SQLCODE -407 SQLSTATE 23502
Explanation: Null values are not allowed in column &1.


SQL0408 SQLCODE -408 SQLSTATE 42821
Explanation: INSERT or UPDATE value for column &1 not compatible.


SQL0410 SQLCODE -410 SQLSTATE 42820
Explanation: Floating point literal &1 not valid.


SQL0412 SQLCODE -412 SQLSTATE 42823
Explanation: Subquery with more than one result column not valid.


SQL0414 SQLCODE -414 SQLSTATE 42824
Explanation: Column &1 not valid in LIKE predicate.


SQL0415 SQLCODE -415 SQLSTATE 42825
Explanation: UNION operands not compatible.


SQL0417 SQLCODE -417 SQLSTATE 42609
Explanation: Combination of parameter markers not valid.


SQL0418 SQLCODE -418 SQLSTATE 42610
Explanation: Use of parameter marker is not valid.


SQL0419 SQLCODE -419 SQLSTATE 42911
Explanation: Negative scale not valid.


SQL0420 SQLCODE -420 SQLSTATE 22018
Explanation: Character in CAST argument not valid.


SQL0421 SQLCODE -421 SQLSTATE 42826
Explanation: Number of UNION operands not equal.


SQL0423 SQLCODE -423 SQLSTATE 0F001
Explanation: LOB locator &1 not valid.


SQL0428 SQLCODE -428 SQLSTATE 25501
Explanation: SQL statement cannot be run.


SQL0429 SQLCODE -429 SQLSTATE 54028
Explanation: The maximum number of concurrent LOB locators has been reached.


SQL0432 SQLCODE -432 SQLSTATE 42841
Explanation: A parameter marker cannot have the user-defined type name &1.


SQL0433 SQLCODE -433 SQLSTATE 22001
Explanation: Significant digits truncated during CAST from numeric to character.


SQL0440 SQLCODE -440 SQLSTATE 42884
Explanation: Number of arguments on CALL must match procedure.


SQL0441 SQLCODE -441 SQLSTATE 42601
Explanation: Clause or keyword &1 not valid where specified.


SQL0442 SQLCODE -442 SQLSTATE 54023
Explanation: Maximum # of parameters on CALL exceeded.


SQL0443 SQLCODE -443 SQLSTATE 2Fxxx, 38501
Explanation: Trigger program or external procedure detected on error.


SQL0444 SQLCODE -444 SQLSTATE 42724
Explanation: External program &4 in &1 not found.


SQL0446 SQLCODE -446 SQLSTATE 22003
Explanation: Conversion error in assignment of argument &2.


SQL0448 SQLCODE -448 SQLSTATE 54023
Explanation: Maximum parameters on DECLARE PROCEDURE exceeded.


SQL0449 SQLCODE -449 SQLSTATE 42878
Explanation: External program name for procedure &1 in &2 not valid.


SQL0451 SQLCODE -451 SQLSTATE 42815
Explanation: Attributes of parameter &1 not valid for procedure.


SQL0452 SQLCODE -452 SQLSTATE 428A1
Explanation: Unable to access a file that is referred to by a file reference variable.


SQL0453 SQLCODE -453 SQLSTATE 42880
Explanation: Return type for function &1 in &2 not compatible with CAST TO type.


SQL0454 SQLCODE -454 SQLSTATE 42723
Explanation: Function &1 in &2 with the same signature already exists.


SQL0455 SQLCODE -455 SQLSTATE 42882
Explanation: Specific name not same as procedure name.


SQL0456 SQLCODE -456 SQLSTATE 42710
Explanation: Specific name &3 in &2 already exists.


SQL0457 SQLCODE -457 SQLSTATE 42939
Explanation: Name &1 in &2 not allowed for function.


SQL0458 SQLCODE -458 SQLSTATE 42883
Explanation: Function &1 in &2 not found with matching signature.


SQL0461 SQLCODE -461 SQLSTATE 42846
Explanation: Cast from &1 to &2 not supported.


SQL0463 SQLCODE -463 SQLSTATE 39001
Explanation: SQLSTATE &4 returned from routine &1 in &2 not valid..


SQL0469 SQLCODE -469 SQLSTATE 42886
Explanation: IN, OUT, INOUT not valid for parameter &4 in procedure &1 in &2.


SQL0470 SQLCODE -470 SQLSTATE 39002
Explanation: NULL values not allowed for parameter &4 in procedure.


SQL0473 SQLCODE -473 SQLSTATE 42918
Explanation: User-defined type &1 cannot be created.


SQL0475 SQLCODE -475 SQLSTATE 42866
Explanation: RETURNS data type for function &3 in &4 not valid.


SQL0476 SQLCODE -476 SQLSTATE 42725
Explanation: Function &1 in &2 not unique.


SQL0478 SQLCODE -478 SQLSTATE 42893
Explanation: Object &1 in &2 of type &3 cannot be dropped.


SQL0483 SQLCODE -483 SQLSTATE 42885
Explanation: Parameters for function &1 in &2 not same as sourced function.


SQL0484 SQLCODE -484 SQLSTATE 42733
Explanation: Routine &1 in &2 already exists.


SQL0487 SQLCODE -487 SQLSTATE 38001
Explanation: SQL statements not allowed.


SQL0490 SQLCODE -490 SQLSTATE 428B7
Explanation: Numeric value &1 not valid.


SQL0491 SQLCODE -491 SQLSTATE 42601
Explanation: RETURNS clause required on CREATE FUNCTION statement.


SQL0492 SQLCODE -492 SQLSTATE 42879
Explanation: Data type for function &1 in &2 not valid for source type.


SQL0501 SQLCODE -501 SQLSTATE 24501
Explanation: Cursor &1 not open.


SQL0502 SQLCODE -502 SQLSTATE 24502
Explanation: Cursor &1 already open.


SQL0503 SQLCODE -503 SQLSTATE 42912
Explanation: Column &3 cannot be updated.


SQL0504 SQLCODE -504 SQLSTATE 34000
Explanation: Cursor &1 not declared.


SQL0507 SQLCODE -507 SQLSTATE 24501
Explanation: Cursor &1 not open.


SQL0508 SQLCODE -508 SQLSTATE 24504
Explanation: Cursor &1 not positioned on locked row.


SQL0509 SQLCODE -509 SQLSTATE 42827
Explanation: Table &2 in &3 not same as table in cursor &1.


SQL0510 SQLCODE -510 SQLSTATE 42828
Explanation: Cursor &1 for file &2 is read-only.


SQL0511 SQLCODE -511 SQLSTATE 42829
Explanation: FOR UPDATE OF clause not valid.


SQL0513 SQLCODE -513 SQLSTATE 42924
Explanation: Alias &1 in &2 cannot reference another alias.


SQL0514 SQLCODE -514 SQLSTATE 26501
Explanation: Prepared statement &2 not found.


SQL0516 SQLCODE -516 SQLSTATE 26501
Explanation: Prepared statement &2 not found.


SQL0517 SQLCODE -517 SQLSTATE 07005
Explanation: Prepared statement &2 not SELECT statement.


SQL0518 SQLCODE -518 SQLSTATE 07003
Explanation: Prepared statement &1 not found.


SQL0519 SQLCODE -519 SQLSTATE 24506
Explanation: Prepared statement &2 in use.


SQL0520 SQLCODE -520 SQLSTATE 42828
Explanation: Cannot UPDATE or DELETE on cursor &1.


SQL0525 SQLCODE -525 SQLSTATE 51015
Explanation: Statement not valid on application server.


SQL0527 SQLCODE -527 SQLSTATE 42874
Explanation: ALWCPYDTA(*NO) specified but temporary result required for &1.


SQL0530 SQLCODE -530 SQLSTATE 23503
Explanation: Insert or UPDATE value not allowed by referential constraint.


SQL0531 SQLCODE -531 SQLSTATE 23001, 23504
Explanation: Update prevented by referential constraint.


SQL0532 SQLCODE -532 SQLSTATE 23001, 23504
Explanation: Delete prevented by referential constraint.


SQL0536 SQLCODE -536 SQLSTATE 42914
Explanation: Delete not allowed because table referenced in subquery can be affected.


SQL0537 SQLCODE -537 SQLSTATE 42709
Explanation: Duplicate column name in definition of key.


SQL0538 SQLCODE -538 SQLSTATE 42830
Explanation: Foreign key attributes do not match parent key.


SQL0539 SQLCODE -539 SQLSTATE 42888
Explanation: Table does not have primary key.


SQL0541 SQLCODE -541 SQLSTATE 42891
Explanation: Duplicate UNIQUE constraint already exists.


SQL0543 SQLCODE -543 SQLSTATE 23511
Explanation: Constraint &1 conflicts with SET NULL or SET DEFAULT rule.


SQL0544 SQLCODE -544 SQLSTATE 23512
Explanation: CHECK constraint &1 cannot be added.


SQL0545 SQLCODE -545 SQLSTATE 23513
Explanation: INSERT or UPDATE not allowed by CHECK constraint.


SQL0546 SQLCODE -546 SQLSTATE 42621
Explanation: CHECK condition of constraint &1 not valid.


SQL0551 SQLCODE -551 SQLSTATE 42501
Explanation: Not authorized to object &1 in &2 type *&3.


SQL0552 SQLCODE -552 SQLSTATE 42502
Explanation: Not authorized to &1.


SQL0557 SQLCODE -557 SQLSTATE 42852
Explanation: Privilege not valid for table or view &1 in &2.


SQL0573 SQLCODE -573 SQLSTATE 42890
Explanation: Table does not have matching parent key.


SQL0574 SQLCODE -574 SQLSTATE 42894
Explanation: Default value not valid.


SQL0577 SQLCODE -577 SQLSTATE 38002, 2F002
Explanation: Modifying SQL data not permitted.


SQL0578 SQLCODE -578 SQLSTATE 2F005
Explanation: RETURN statement not executed for SQL function &1 in &2.


SQL0579 SQLCODE -579 SQLSTATE 38004, 2F004
Explanation: Reading SQL data not permitted.


SQL0580 SQLCODE -580 SQLSTATE 42625
Explanation: At least one result in CASE expression must be not NULL.


SQL0581 SQLCODE -581 SQLSTATE 42804
Explanation: The results in a CASE expression are not compatible.


SQL0583 SQLCODE -583 SQLSTATE 42845
Explanation: Use of function &1 in &2 not valid.


SQL0585 SQLCODE -585 SQLSTATE 42732
Explanation: Library &1 is used incorrectly on the SET PATH statement


SQL0590 SQLCODE -590 SQLSTATE 42734
Explanation: Name &1 specified in &2 not unique.


SQL0601 SQLCODE -601 SQLSTATE 42710
Explanation: Object &1 in &2 type *&3 already exists.


SQL0602 SQLCODE -602 SQLSTATE 54008
Explanation: More than 120 columns specified for CREATE INDEX.


SQL0603 SQLCODE -603 SQLSTATE 23515
Explanation: Unique index cannot be created because of duplicate keys.


SQL0604 SQLCODE -604 SQLSTATE 42611
Explanation: Attributes of column not valid.


SQL0607 SQLCODE -607 SQLSTATE 42832
Explanation: Operation not allowed on system table &1 in &2.


SQL0612 SQLCODE -612 SQLSTATE 42711
Explanation: &1 is a duplicate column name.


SQL0613 SQLCODE -613 SQLSTATE 54008
Explanation: Primary or unique key constraint too long.


SQL0614 SQLCODE -614 SQLSTATE 54008
Explanation: Length of columns for CREATE INDEX too long.


SQL0615 SQLCODE -615 SQLSTATE 55006
Explanation: Object &1 in &2 type *&3 not dropped. It is in use.


SQL0616 SQLCODE -616 SQLSTATE 42893
Explanation: &1 in &2 type &3 cannot be dropped with RESTRICT.


SQL0624 SQLCODE -624 SQLSTATE 42889
Explanation: Table already has primary key.


SQL0628 SQLCODE -628 SQLSTATE 42613
Explanation: Clauses are mutually exclusive.


SQL0629 SQLCODE -629 SQLSTATE 42834
Explanation: SET NULL not allowed for referential constraint.


SQL0631 SQLCODE -631 SQLSTATE 54008
Explanation: Foreign key for referential constraint too long.


SQL0637 SQLCODE -637 SQLSTATE 42614
Explanation: Duplicate &1 keyword.


SQL0642 SQLCODE -642 SQLSTATE 54021
Explanation: Maximum number of constraints exceeded.


SQL0658 SQLCODE -658 SQLSTATE 42917
Explanation: Function cannot be dropped.


SQL0666 SQLCODE -666 SQLSTATE 57005
Explanation: Estimated query processing time exceeds limit.


SQL0667 SQLCODE -667 SQLSTATE 23520
Explanation: Foreign key does not match a value in the parent key.


SQL0675 SQLCODE -675 SQLSTATE 42892
Explanation: Specified delete rule not allowed with existing trigger.


SQL0679 SQLCODE -679 SQLSTATE 57006
Explanation: Object &1 in &2 type *&3 not created due to pending operation.


SQL0683 SQLCODE -683 SQLSTATE 42842
Explanation: FOR DATA or CCSID clause not valid for specified type.


SQL0707 SQLCODE -707 SQLSTATE 42939
Explanation: Name &1 in &2 not allowed for distinct type.


SQL0713 SQLCODE -713 SQLSTATE 42815
Explanation: Host variable for &2 is NULL.


SQL0724 SQLCODE -724 SQLSTATE 54038
Explanation: Too many cascaded trigger programs.


SQL0751 SQLCODE -751 SQLSTATE 42987
Explanation: SQL statement &1 not allowed in stored procedure or trigger.


SQL0752 SQLCODE -752 SQLSTATE 0A001
Explanation: Connection cannot be changed. Reason code is &1.


SQL0773 SQLCODE -773 SQLSTATE 20000
Explanation: Case not found for CASE statement.


SQL0774 SQLCODE -774 SQLSTATE 2D522
Explanation: Statement cannot be executed within a compound SQL statement.


SQL0775 SQLCODE -775 SQLSTATE 42910
Explanation: Statement not allowed in a compound SQL statement.


SQL0776 SQLCODE -776 SQLSTATE 428D4
Explanation: Cursor &1 specified in FOR statement not allowed.


SQL0777 SQLCODE -777 SQLSTATE 42919
Explanation: Nested compound statements not allowed.


SQL0778 SQLCODE -778 SQLSTATE 428D5
Explanation: End label &1 not same as begin label.


SQL0779 SQLCODE -779 SQLSTATE 42736
Explanation: Label &1 specified on LEAVE statement not valid.


SQL0780 SQLCODE -780 SQLSTATE 428D6
Explanation: UNDO specified for a handler and ATOMIC not specified.


SQL0781 SQLCODE -781 SQLSTATE 42737
Explanation: Condition &1 specified in handler not defined.


SQL0782 SQLCODE -782 SQLSTATE 428D7
Explanation: Condition value &1 specified in handler not valid.


SQL0783 SQLCODE -783 SQLSTATE 42738
Explanation: Select list for cursor &1 in FOR statement not valid.


SQL0784 SQLCODE -784 SQLSTATE 42860
Explanation: Check constraint &1 cannot be dropped.


SQL0785 SQLCODE -785 SQLSTATE 428D8
Explanation: Use of SQLCODE or SQLSTATE not valid.


SQL0802 SQLCODE -802 SQLSTATE 22003, 22012, 22023, 22504
Explanation: Data conversion or data mapping error.


SQL0803 SQLCODE -803 SQLSTATE 23505
Explanation: Duplicate key value specified.


SQL0804 SQLCODE -804 SQLSTATE 07002
Explanation: SQLDA not valid.


SQL0805 SQLCODE -805 SQLSTATE 51002
Explanation: SQL package &1 in &2 not found.


SQL0811 SQLCODE -811 SQLSTATE 21000
Explanation: Result of SELECT INTO or subquery more than one row.


SQL0818 SQLCODE -818 SQLSTATE 51003
Explanation: Consistency tokens do not match.


SQL0822 SQLCODE -822 SQLSTATE 51004
Explanation: Address in SQLDA not valid.


SQL0827 SQLCODE -827 SQLSTATE 42862
Explanation: &1 in &2 type *SQLPKG cannot be accessed.


SQL0840 SQLCODE -840 SQLSTATE 54004
Explanation: Number of selected items exceeds 8000.


SQL0842 SQLCODE -842 SQLSTATE 08002
Explanation: Connection already exists.


SQL0843 SQLCODE -843 SQLSTATE 08003
Explanation: Connection does not exist.


SQL0858 SQLCODE -858 SQLSTATE 08501
Explanation: Cannot disconnect relational database due to LU 6.2 protected conversation.


SQL0862 SQLCODE -862 SQLSTATE 55029
Explanation: Local program attempted to connect to a remote relational database.


SQL0871 SQLCODE -871 SQLSTATE 54019
Explanation: Too many CCSID values specified.


SQL0900 SQLCODE -900 SQLSTATE 08003
Explanation: Application process not in a connected state.


SQL0901 SQLCODE -901 SQLSTATE 58004
Explanation: SQL system error.


SQL0904 SQLCODE -904 SQLSTATE 57011
Explanation: Resource limit exceeded.


SQL0906 SQLCODE -906 SQLSTATE 24514
Explanation: Operation not performed because of previous error.


SQL0907 SQLCODE -907 SQLSTATE 27000
Explanation: Attempt to change same row twice.


SQL0910 SQLCODE -910 SQLSTATE 57007
Explanation: Object &1 in &2 type *&3 has a pending change.


SQL0913 SQLCODE -913 SQLSTATE 57033
Explanation: Row or object &1 in &2 type *&3 in use.


SQL0917 SQLCODE -917 SQLSTATE 42969
Explanation: Package not created.


SQL0918 SQLCODE -918 SQLSTATE 51021
Explanation: Rollback required.


SQL0950 SQLCODE -950 SQLSTATE 42705
Explanation: Relational database &1 not in relational database directory.


SQL0951 SQLCODE -951 SQLSTATE 55007
Explanation: Object &1 in &2 not altered. It is in use.


SQL0952 SQLCODE -952 SQLSTATE 57014
Explanation: Processing of the SQL statement ended by ENDRDBRQS command.


SQL0969 SQLCODE -969 SQLSTATE 58033
Explanation: Unexpected client driver error.


SQL0971 SQLCODE -971 SQLSTATE 57011
Explanation: Referential constraint &4 in check pending state.


SQL5001 SQLCODE -5001 SQLSTATE 42703
Explanation: Column qualifier &2 undefined.


SQL5002 SQLCODE -5002 SQLSTATE 42812
Explanation: Collection must be specified for table &1.


SQL5003 SQLCODE -5003 SQLSTATE 42922
Explanation: Cannot perform operation under commitment control.


SQL5005 SQLCODE -5005 SQLSTATE 42815
Explanation: Operator &4 not consistent with operands.


SQL5012 SQLCODE -5012 SQLSTATE 42618
Explanation: Host variable not a numeric with zero scale.


SQL5016 SQLCODE -5016 SQLSTATE 42833
Explanation: Object name &1 not valid for naming option.


SQL5021 SQLCODE -5021 SQLSTATE 42930
Explanation: FOR UPDATE OF column &1 also in ORDER BY.


SQL5023 SQLCODE -5023 SQLSTATE 26510
Explanation: Duplicate statement name in DECLARE CURSOR.


SQL5024 SQLCODE -5024 SQLSTATE 42618
Explanation: Host variable &1 not character.


SQL5047 SQLCODE -5047 SQLSTATE 42616
Explanation: Error processing SRTSEQ or LANGID parameter.


SQL5051 SQLCODE -5051 SQLSTATE 42875
Explanation: Incorrect qualifier.


SQL7001 SQLCODE -7001 SQLSTATE 42858
Explanation: File &1 in &2 not database file.


SQL7002 SQLCODE -7002 SQLSTATE 42847
Explanation: Override parameter not valid.


SQL7003 SQLCODE -7003 SQLSTATE 42857
Explanation: File &1 in &2 has more than one format.


SQL7006 SQLCODE -7006 SQLSTATE 55018
Explanation: Cannot drop collection &1.


SQL7007 SQLCODE -7007 SQLSTATE 51009
Explanation: COMMIT or ROLLBACK not valid.


SQL7008 SQLCODE -7008 SQLSTATE 55019
Explanation: &1 in &2 not valid for operation.


SQL7010 SQLCODE -7010 SQLSTATE 42850
Explanation: Logical file &1 in &2 not valid for CREATE VIEW.


SQL7011 SQLCODE -7011 SQLSTATE 42851
Explanation: &1 in &2 not table, view, or physical file.


SQL7017 SQLCODE -7017 SQLSTATE 42971
Explanation: Commitment control is already active to a DDM target.


SQL7018 SQLCODE -7018 SQLSTATE 42970
Explanation: COMMIT HOLD or ROLLBACK HOLD not allowed.


SQL7021 SQLCODE -7021 SQLSTATE 57043
Explanation: Local program attempting to run on application server.


SQL7022 SQLCODE -7022 SQLSTATE 42977
Explanation: User &1 not the same as current user &2 for connect to local relational database.


SQL7024 SQLCODE -7024 SQLSTATE 42876
Explanation: Index cannot be created because of CCSID incompatibility.


SQL7026 SQLCODE -7026 SQLSTATE 42896
Explanation: Auxiliary storage pool not found.


SQL7027 SQLCODE -7027 SQLSTATE 42984
Explanation: Unable to grant to a view.


SQL7028 SQLCODE -7028 SQLSTATE 42944
Explanation: Unable to CHGOBJOWN for primary group.


SQL7029 SQLCODE -7029 SQLSTATE 428B8
Explanation: New name &3 is not valid.


SQL7031 SQLCODE -7031 SQLSTATE 54044
Explanation: Sort sequence table &1 too long.


SQL7032 SQLCODE -7032 SQLSTATE 42904
Explanation: SQL procedure &1 in &2 not created.


SQL7033 SQLCODE -7033 SQLSTATE 42923
Explanation: Alias name &1 in &2 not allowed.


SQL7034 SQLCODE -7034 SQLSTATE 42926
Explanation: LOB locators are not allowed with COMMIT(*NONE).


SQL7037 SQLCODE -7037 SQLSTATE 42835
Explanation: Data in a distributed file &1 in &2 cannot be redistributed.


SQL7038 SQLCODE -7038 SQLSTATE 429B7
Explanation: Delete cascade not valid for &1 in &2.


SQL7941 SQLCODE -7941 SQLSTATE 42981
Explanation: Application process not at commit boundary.


SQL9012 SQLCODE -9012 SQLSTATE 42968
Explanation: DB2 UDB Query Manager and SQL Development Kit not available.


SQ30000 SQLCODE -30000 SQLSTATE 58008
Explanation: Distributed Relational Database Architecture (DRDA) protocol error.


SQ30001 SQLCODE -30001 SQLSTATE 57042
Explanation: Call to distributed SQL program not allowed.


SQ30020 SQLCODE -30020 SQLSTATE 58009
Explanation: Distributed Relational Database Architecture (DRDA) protocol error.


SQ30021 SQLCODE -30021 SQLSTATE 58010
Explanation: Distributed relational database not supported by the remote system.


SQ30040 SQLCODE -30040 SQLSTATE 57012
Explanation: DDM resource &2 at relational database &1 not available.


SQ30041 SQLCODE -30041 SQLSTATE 57013
Explanation: DDM resources at relational database &1 not available.


SQ30050 SQLCODE -30050 SQLSTATE 58011
Explanation: DDM command &1 is not valid while bind process is in progress.


SQ30051 SQLCODE -30051 SQLSTATE 58012
Explanation: Bind process for specified package name and consistency token not active.


SQ30052 SQLCODE -30052 SQLSTATE 42932
Explanation: Program preparation assumptions not correct.


SQ30053 SQLCODE -30053 SQLSTATE 42506
Explanation: Not authorized to create package for owner &1.


SQ30060 SQLCODE -30060 SQLSTATE 08004
Explanation: User not authorized to relational database &1.


SQ30061 SQLCODE -30061 SQLSTATE 08004
Explanation: Relational database &1 not found.


SQ30070 SQLCODE -30070 SQLSTATE 58014
Explanation: Distributed Data Management (DDM) command &1 not supported.


SQ30071 SQLCODE -30071 SQLSTATE 58015
Explanation: Distributed Data Management (DDM) object &1 not supported.


SQ30072 SQLCODE -30072 SQLSTATE 58016
Explanation: Distributed Data Management (DDM) parameter &1 not supported.


SQ30073 SQLCODE -30073 SQLSTATE 58017
Explanation: Distributed Data Management (DDM) parameter value &1 not supported.


SQ30074 SQLCODE -30074 SQLSTATE 58018
Explanation: Distributed Data Management (DDM) reply message &1 not supported.


SQ30080 SQLCODE -30080 SQLSTATE 08001
Explanation: Communication error occurred during distributed database processing.


SQ30089 SQLCODE -30089 SQLSTATE 08001
Explanation: Communication error occurred during DB2 Multisystem processing.


SQ30090 SQLCODE -30090 SQLSTATE 25000, 2D528, 2D529
Explanation: Change request not valid for read-only application server.

DB2 SQL-Error: -007 SQLState: 42601 Short Description: STATEMENT CONTAINS THE ILLEGAL CHARACTER 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 2 of DB2 SQL Reference for information about the valid SQL character set. DB2 SQL-Error: -010 SQLState: 42603 Short Description: THE STRING CONSTANT BEGINNING IS NOT TERMINATED 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. DB2 SQL-Error: -029 SQLState: 42601 Short Description: INTO CLAUSE REQUIRED 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. SQL0051 SQLCODE -51 SQLSTATE 3C000 Explanation: Cursor or procedure &1 previously declared. DB2 SQL-Error: -58 SQLState: 428F2 Short Description: A RETURN SQL T RETURN SQL INTEGER A RETURN statement is specified in the SQL procedure with a value or expression that is not of the INTEGER data type. System action: The statement cannot be processed. User response: Specify a value on the RETURN statement that has a data type of INTEGER. SQL0060 SQLCODE -60 SQLSTATE 42815 Explanation: Value &3 for argument &1 of &2 function not valid. SQL0078 SQLCODE -78 SQLSTATE 42629 Explanation: Parameter name required for routine &1 in &2. SQL0080 SQLCODE -80 SQLSTATE 42978 Explanation: Indicator variable &1 not SMALLINT type. SQL0084 SQLCODE -84 SQLSTATE 42612 Explanation: SQL statement not allowed. SQL0090 SQLCODE -90 SQLSTATE 42618 Explanation: Host variable not permitted here. SQL0097 SQLCODE -97 SQLSTATE 42601 Explanation: Use of data type not valid. SQL0099 SQLCODE -99 SQLSTATE 42992 Explanation: Operator in join condition not valid. SQL0101 SQLCODE -101 SQLSTATE 54001, 54010, 54011 Explanation: SQL statement too long or complex. SQL0102 SQLCODE -102 SQLSTATE 54002 Explanation: String constant beginning with &1 too long. SQL0103 SQLCODE -103 SQLSTATE 42604 Explanation: Numeric constant &1 not valid. SQL0104 SQLCODE -104 SQLSTATE 42601 Explanation: Token &1 was not valid. Valid tokens: &2. SQL0105 SQLCODE -105 SQLSTATE 42604 Explanation: Mixed or graphic string constant not valid. SQL0106 SQLCODE -106 SQLSTATE 42611 Explanation: Precision specified for FLOAT column not valid. SQL0107 SQLCODE -107 SQLSTATE 42622 Explanation: &1 too long. Maximum &2 characters. SQL0109 SQLCODE -109 SQLSTATE 42601 Explanation: &1 clause not allowed. SQL0110 SQLCODE -110 SQLSTATE 42606 Explanation: Hexadecimal constant beginning with &1 not valid. SQL0112 SQLCODE -112 SQLSTATE 42607 Explanation: Argument of function &1 is another function. SQL0113 SQLCODE -113 SQLSTATE 28000, 2E000, 42602 Explanation: Name &1 not allowed. SQL0114 SQLCODE -114 SQLSTATE 42961 Explanation: Relational database &1 not the same as current server &2. SQL0115 SQLCODE -115 SQLSTATE 42601 Explanation: Comparison operator &1 not valid. SQL0117 SQLCODE -117 SQLSTATE 42802 Explanation: Statement inserts wrong number of values. SQL0118 SQLCODE -118 SQLSTATE 42902 Explanation: Table &1 in &2 also specified in a FROM clause. SQL0119 SQLCODE -119 SQLSTATE 42803 Explanation: Column &1 in HAVING clause not in GROUP BY. SQL0120 SQLCODE -120 SQLSTATE 42903 Explanation: Use of column function &2 not valid. SQL0121 SQLCODE -121 SQLSTATE 42701 Explanation: Duplicate column name &1 in INSERT or UPDATE. SQL0122 SQLCODE -122 SQLSTATE 42803 Explanation: Column specified in SELECT list not valid. SQL0125 SQLCODE -125 SQLSTATE 42805 Explanation: ORDER BY column number &1 not valid. SQL0128 SQLCODE -128 SQLSTATE 42601 Explanation: Use of NULL is not valid. SQL0129 SQLCODE -129 SQLSTATE 54004 Explanation: Too many tables in SQL statement. SQL0130 SQLCODE -130 SQLSTATE 22019, 22025 Explanation: Escape character &1 or LIKE pattern not valid. SQL0131 SQLCODE -131 SQLSTATE 42818 Explanation: Operands of LIKE not compatible or not valid. SQL0132 SQLCODE -132 SQLSTATE 42824 Explanation: LIKE predicate not valid. SQL0133 SQLCODE -133 SQLSTATE 42906 Explanation: Operator on correlated column in SQL function not valid. SQL0134 SQLCODE -134 SQLSTATE 42907 Explanation: Argument of function too long. SQL0136 SQLCODE -136 SQLSTATE 54005 Explanation: ORDER BY or GROUP BY columns too long. SQL0137 SQLCODE -137 SQLSTATE 54006 Explanation: Result too long. SQL0138 SQLCODE -138 SQLSTATE 22011 Explanation: Argument &1 of SUBSTR function not valid. SQL0144 SQLCODE -144 SQLSTATE 58003 Explanation: Section number not valid. SQL0145 SQLCODE -145 SQLSTATE 55005 Explanation: Recursion not supported for an application server other than the AS/400 system. SQL0150 SQLCODE -150 SQLSTATE 42807 Explanation: View or logical file &1 in &2 read-only. SQL0151 SQLCODE -151 SQLSTATE 42808 Explanation: Column &1 in table &2 in &3 read-only. SQL0152 SQLCODE -152 SQLSTATE 42809 Explanation: Constraint type not valid for constraint &1 in &2. SQL0153 SQLCODE -153 SQLSTATE 42908 Explanation: Column list required for CREATE VIEW. SQL0154 SQLCODE -154 SQLSTATE 42909 Explanation: UNION and UNION ALL for CREATE VIEW not valid. SQL0156 SQLCODE -156 SQLSTATE 42809 Explanation: &1 in &2 not a table. SQL0157 SQLCODE -157 SQLSTATE 42810 Explanation: View &1 in &2 not valid in FOREIGN KEY clause. SQL0158 SQLCODE -158 SQLSTATE 42811 Explanation: Number of columns specified not consistent. SQL0159 SQLCODE -159 SQLSTATE 42809 Explanation: &1 in &2 not correct type. SQL0160 SQLCODE -160 SQLSTATE 42813 Explanation: WITH CHECK OPTION not allowed for view &1 in &2. SQL0161 SQLCODE -161 SQLSTATE 44000 Explanation: INSERT/UPDATE not allowed due to WITH CHECK OPTION. SQL0170 SQLCODE -170 SQLSTATE 42605 Explanation: Number of arguments for function &1 not valid. SQL0171 SQLCODE -171 SQLSTATE 42815 Explanation: Argument &1 of function &2 not valid. SQL0175 SQLCODE -175 SQLSTATE 58028 Explanation: COMMIT failed. SQL0180 SQLCODE -180 SQLSTATE 22007 Explanation: Syntax of date, time, or timestamp value not valid. SQL0181 SQLCODE -181 SQLSTATE 22007 Explanation: Value in date, time, or timestamp string not valid. SQL0182 SQLCODE -182 SQLSTATE 42816 Explanation: A date, time, or timestamp expression not valid. SQL0183 SQLCODE -183 SQLSTATE 22008 Explanation: The result of a date or timestamp expression not valid. SQL0184 SQLCODE -184 SQLSTATE 42610 Explanation: Parameter marker not valid in expression. SQL0187 SQLCODE -187 SQLSTATE 42816 Explanation: Use of labeled duration is not valid. SQL0188 SQLCODE -188 SQLSTATE 22503, 28000, 2E000 Explanation: &1 is not a valid string representation of an authorization name or a relational database name. SQL0189 SQLCODE -189 SQLSTATE 22522 Explanation: Coded Character Set Identifier &1 is not valid. SQL0190 SQLCODE -190 SQLSTATE 42837 Explanation: Attributes of column &3 in &1 in &2 not compatible. SQL0191 SQLCODE -191 SQLSTATE 22504 Explanation: MIXED data not properly formed. SQL0192 SQLCODE -192 SQLSTATE 42937 Explanation: Argument of TRANSLATE function not valid. SQL0194 SQLCODE -194 SQLSTATE 42848 Explanation: KEEP LOCKS not allowed. SQL0195 SQLCODE -195 SQLSTATE 42814 Explanation: Last column of &1 in &2 cannot be dropped. SQL0196 SQLCODE -196 SQLSTATE 42817 Explanation: Column &3 in &1 in &2 cannot be dropped with RESTRICT. SQL0197 SQLCODE -197 SQLSTATE 42877 Explanation: Column &1 cannot be qualified. SQL0198 SQLCODE -198 SQLSTATE 42617 Explanation: SQL statement empty or blank. SQL0199 SQLCODE -199 SQLSTATE 42601 Explanation: Keyword &1 not expected. Valid tokens: &2. SQL0203 SQLCODE -203 SQLSTATE 42702 Explanation: Column &1 is ambiguous. SQL0204 SQLCODE -204 SQLSTATE 42704 Explanation: &1 in &2 type *&3 not found. SQL0205 SQLCODE -205 SQLSTATE 42703 Explanation: Column &1 not in table &2. SQL0206 SQLCODE -206 SQLSTATE 42703 Explanation: Column &1 not in specified tables. SQL0208 SQLCODE -208 SQLSTATE 42707 Explanation: ORDER BY column &1 not in results table. SQL0212 SQLCODE -212 SQLSTATE 42712 Explanation: Duplicate table designator &1 not valid. SQL0214 SQLCODE -214 SQLSTATE 42822 Explanation: ORDER BY expression is not valid. SQL0221 SQLCODE -221 SQLSTATE 42873 Explanation: Number of rows &2 not valid. SQL0225 SQLCODE -225 SQLSTATE 42872 Explanation: FETCH not valid; cursor &1 not declared with SCROLL. SQL0226 SQLCODE -226 SQLSTATE 24507 Explanation: Current row deleted or moved for cursor &1. SQL0227 SQLCODE -227 SQLSTATE 24513 Explanation: FETCH not valid, cursor &1 in unknown position. SQL0228 SQLCODE -228 SQLSTATE 42620 Explanation: FOR UPDATE OF clause not valid with SCROLL for cursor &1. SQL0231 SQLCODE -231 SQLSTATE 22006 Explanation: Position of cursor &1 not valid for FETCH of current row. SQL0250 SQLCODE -250 SQLSTATE 42718 Explanation: Local relational database not defined in the directory. SQL0251 SQLCODE -251 SQLSTATE 2E000, 42602 Explanation: Character in relational database name &1 is not valid. SQL0255 SQLCODE -255 SQLSTATE 42999 Explanation: DB2 Multisystem query error. SQL0256 SQLCODE -256 SQLSTATE 42998 Explanation: Constraint &1 in &2 not allowed on distributed file. SQL0270 SQLCODE -270 SQLSTATE 42997 Explanation: Unique index not allowed. SQL0301 SQLCODE -301 SQLSTATE 07006,42895 Explanation: Input host variable &2 or argument &1 not valid. SQL0302 SQLCODE -302 SQLSTATE 22001, 22003, 22023, 22024 Explanation: Conversion error on input host variable &2. Muze znamenat data length over limit. SQL0303 SQLCODE -303 SQLSTATE 22001, 42806 Explanation: Host variable &1 not compatible with SELECT item. SQL0304 SQLCODE -304 SQLSTATE 22003, 22023, 22504 Explanation: Conversion error in assignment to host variable &2. SQL0305 SQLCODE -305 SQLSTATE 22002 Explanation: Indicator variable required. SQL0306 SQLCODE -306 SQLSTATE 42863 Explanation: Undefined host variable in REXX. SQL0311 SQLCODE -311 SQLSTATE 22501 Explanation: Length in a varying-length host variable not valid. SQL0312 SQLCODE -312 SQLSTATE 42618 Explanation: Host variable &1 not defined or not usable. SQL0313 SQLCODE -313 SQLSTATE 07001, 07004 Explanation: Number of host variables not valid. SQL0328 SQLCODE -328 SQLSTATE 42996 Explanation: Column &1 not allowed in partitioning key. SQL0329 SQLCODE -329 SQLSTATE 0E000 Explanation: The SET PATH name list is not valid. SQL0330 SQLCODE -330 SQLSTATE 22021 Explanation: Character conversion cannot be performed. SQL0331 SQLCODE -331 SQLSTATE 22021 Explanation: Character conversion cannot be performed. SQL0332 SQLCODE -332 SQLSTATE 57017 Explanation: Character conversion between CCSID &1 and CCSID &2 not valid. SQL0334 SQLCODE -334 SQLSTATE 22524 Explanation: Character conversion has resulted in truncation. SQL0338 SQLCODE -338 SQLSTATE 42972 Explanation: JOIN expression not valid. SQL0340 SQLCODE -340 SQLSTATE 42726 Explanation: Duplicate name &1 for common table expression. SQL0341 SQLCODE -341 SQLSTATE 42835 Explanation: Cyclic references between common table expressions. SQL0346 SQLCODE -346 SQLSTATE 42836 Explanation: Recursion not allowed for common table expressions. SQL0350 SQLCODE -350 SQLSTATE 42962 Explanation: Column &1 is not valid as key field for index or constraint. SQL0351 SQLCODE -351 SQLSTATE 56084 Explanation: The AR is not at the same level and DB2/400 cannot transform the data type to a compatible type. SQL0352 SQLCODE -352 SQLSTATE 56084 Explanation: The AS is not at the same level and DB2/400 cannot transform the data type to a compatible type. SQL0357 SQLCODE -357 SQLSTATE 57050 Explanation: File server &1 used in DataLink not currently available. SQL0358 SQLCODE -358 SQLSTATE 428D1 Explanation: Error &1 occurred using DataLink data type. SQL0392 SQLCODE -392 SQLSTATE 42855 Explanation: Assignment of LOB to specified host variable not allowed. SQL0398 SQLCODE -398 SQLSTATE 428D2 Explanation: AS LOCATOR cannot be specified for a non-LOB parameter. SQL0401 SQLCODE -401 SQLSTATE 42818 Explanation: Comparison operator &1 operands not compatible. SQL0402 SQLCODE -402 SQLSTATE 42819 Explanation: &1 use not valid. SQL0404 SQLCODE -404 SQLSTATE 22001 Explanation: Value for column &1 too long. SQL0405 SQLCODE -405 SQLSTATE 42820 Explanation: Numeric constant &1 out of range. SQL0406 SQLCODE -406 SQLSTATE 22003, 22023, 22504 Explanation: Conversion error on assignment to column &2. SQL0407 SQLCODE -407 SQLSTATE 23502 Explanation: Null values are not allowed in column &1. SQL0408 SQLCODE -408 SQLSTATE 42821 Explanation: INSERT or UPDATE value for column &1 not compatible. SQL0410 SQLCODE -410 SQLSTATE 42820 Explanation: Floating point literal &1 not valid. SQL0412 SQLCODE -412 SQLSTATE 42823 Explanation: Subquery with more than one result column not valid. SQL0414 SQLCODE -414 SQLSTATE 42824 Explanation: Column &1 not valid in LIKE predicate. SQL0415 SQLCODE -415 SQLSTATE 42825 Explanation: UNION operands not compatible. SQL0417 SQLCODE -417 SQLSTATE 42609 Explanation: Combination of parameter markers not valid. SQL0418 SQLCODE -418 SQLSTATE 42610 Explanation: Use of parameter marker is not valid. SQL0419 SQLCODE -419 SQLSTATE 42911 Explanation: Negative scale not valid. SQL0420 SQLCODE -420 SQLSTATE 22018 Explanation: Character in CAST argument not valid. SQL0421 SQLCODE -421 SQLSTATE 42826 Explanation: Number of UNION operands not equal. SQL0423 SQLCODE -423 SQLSTATE 0F001 Explanation: LOB locator &1 not valid. SQL0428 SQLCODE -428 SQLSTATE 25501 Explanation: SQL statement cannot be run. SQL0429 SQLCODE -429 SQLSTATE 54028 Explanation: The maximum number of concurrent LOB locators has been reached. SQL0432 SQLCODE -432 SQLSTATE 42841 Explanation: A parameter marker cannot have the user-defined type name &1. SQL0433 SQLCODE -433 SQLSTATE 22001 Explanation: Significant digits truncated during CAST from numeric to character. SQL0440 SQLCODE -440 SQLSTATE 42884 Explanation: Number of arguments on CALL must match procedure. SQL0441 SQLCODE -441 SQLSTATE 42601 Explanation: Clause or keyword &1 not valid where specified. SQL0442 SQLCODE -442 SQLSTATE 54023 Explanation: Maximum # of parameters on CALL exceeded. SQL0443 SQLCODE -443 SQLSTATE 2Fxxx, 38501 Explanation: Trigger program or external procedure detected on error. SQL0444 SQLCODE -444 SQLSTATE 42724 Explanation: External program &4 in &1 not found. SQL0446 SQLCODE -446 SQLSTATE 22003 Explanation: Conversion error in assignment of argument &2. SQL0448 SQLCODE -448 SQLSTATE 54023 Explanation: Maximum parameters on DECLARE PROCEDURE exceeded. SQL0449 SQLCODE -449 SQLSTATE 42878 Explanation: External program name for procedure &1 in &2 not valid. SQL0451 SQLCODE -451 SQLSTATE 42815 Explanation: Attributes of parameter &1 not valid for procedure. SQL0452 SQLCODE -452 SQLSTATE 428A1 Explanation: Unable to access a file that is referred to by a file reference variable. SQL0453 SQLCODE -453 SQLSTATE 42880 Explanation: Return type for function &1 in &2 not compatible with CAST TO type. SQL0454 SQLCODE -454 SQLSTATE 42723 Explanation: Function &1 in &2 with the same signature already exists. SQL0455 SQLCODE -455 SQLSTATE 42882 Explanation: Specific name not same as procedure name. SQL0456 SQLCODE -456 SQLSTATE 42710 Explanation: Specific name &3 in &2 already exists. SQL0457 SQLCODE -457 SQLSTATE 42939 Explanation: Name &1 in &2 not allowed for function. SQL0458 SQLCODE -458 SQLSTATE 42883 Explanation: Function &1 in &2 not found with matching signature. SQL0461 SQLCODE -461 SQLSTATE 42846 Explanation: Cast from &1 to &2 not supported. SQL0463 SQLCODE -463 SQLSTATE 39001 Explanation: SQLSTATE &4 returned from routine &1 in &2 not valid.. SQL0469 SQLCODE -469 SQLSTATE 42886 Explanation: IN, OUT, INOUT not valid for parameter &4 in procedure &1 in &2. SQL0470 SQLCODE -470 SQLSTATE 39002 Explanation: NULL values not allowed for parameter &4 in procedure. SQL0473 SQLCODE -473 SQLSTATE 42918 Explanation: User-defined type &1 cannot be created. SQL0475 SQLCODE -475 SQLSTATE 42866 Explanation: RETURNS data type for function &3 in &4 not valid. SQL0476 SQLCODE -476 SQLSTATE 42725 Explanation: Function &1 in &2 not unique. SQL0478 SQLCODE -478 SQLSTATE 42893 Explanation: Object &1 in &2 of type &3 cannot be dropped. SQL0483 SQLCODE -483 SQLSTATE 42885 Explanation: Parameters for function &1 in &2 not same as sourced function. SQL0484 SQLCODE -484 SQLSTATE 42733 Explanation: Routine &1 in &2 already exists. SQL0487 SQLCODE -487 SQLSTATE 38001 Explanation: SQL statements not allowed. SQL0490 SQLCODE -490 SQLSTATE 428B7 Explanation: Numeric value &1 not valid. SQL0491 SQLCODE -491 SQLSTATE 42601 Explanation: RETURNS clause required on CREATE FUNCTION statement. SQL0492 SQLCODE -492 SQLSTATE 42879 Explanation: Data type for function &1 in &2 not valid for source type. SQL0501 SQLCODE -501 SQLSTATE 24501 Explanation: Cursor &1 not open. SQL0502 SQLCODE -502 SQLSTATE 24502 Explanation: Cursor &1 already open. SQL0503 SQLCODE -503 SQLSTATE 42912 Explanation: Column &3 cannot be updated. SQL0504 SQLCODE -504 SQLSTATE 34000 Explanation: Cursor &1 not declared. SQL0507 SQLCODE -507 SQLSTATE 24501 Explanation: Cursor &1 not open. SQL0508 SQLCODE -508 SQLSTATE 24504 Explanation: Cursor &1 not positioned on locked row. SQL0509 SQLCODE -509 SQLSTATE 42827 Explanation: Table &2 in &3 not same as table in cursor &1. SQL0510 SQLCODE -510 SQLSTATE 42828 Explanation: Cursor &1 for file &2 is read-only. SQL0511 SQLCODE -511 SQLSTATE 42829 Explanation: FOR UPDATE OF clause not valid. SQL0513 SQLCODE -513 SQLSTATE 42924 Explanation: Alias &1 in &2 cannot reference another alias. SQL0514 SQLCODE -514 SQLSTATE 26501 Explanation: Prepared statement &2 not found. SQL0516 SQLCODE -516 SQLSTATE 26501 Explanation: Prepared statement &2 not found. SQL0517 SQLCODE -517 SQLSTATE 07005 Explanation: Prepared statement &2 not SELECT statement. SQL0518 SQLCODE -518 SQLSTATE 07003 Explanation: Prepared statement &1 not found. SQL0519 SQLCODE -519 SQLSTATE 24506 Explanation: Prepared statement &2 in use. SQL0520 SQLCODE -520 SQLSTATE 42828 Explanation: Cannot UPDATE or DELETE on cursor &1. SQL0525 SQLCODE -525 SQLSTATE 51015 Explanation: Statement not valid on application server. SQL0527 SQLCODE -527 SQLSTATE 42874 Explanation: ALWCPYDTA(*NO) specified but temporary result required for &1. SQL0530 SQLCODE -530 SQLSTATE 23503 Explanation: Insert or UPDATE value not allowed by referential constraint. SQL0531 SQLCODE -531 SQLSTATE 23001, 23504 Explanation: Update prevented by referential constraint. SQL0532 SQLCODE -532 SQLSTATE 23001, 23504 Explanation: Delete prevented by referential constraint. SQL0536 SQLCODE -536 SQLSTATE 42914 Explanation: Delete not allowed because table referenced in subquery can be affected. SQL0537 SQLCODE -537 SQLSTATE 42709 Explanation: Duplicate column name in definition of key. SQL0538 SQLCODE -538 SQLSTATE 42830 Explanation: Foreign key attributes do not match parent key. SQL0539 SQLCODE -539 SQLSTATE 42888 Explanation: Table does not have primary key. SQL0541 SQLCODE -541 SQLSTATE 42891 Explanation: Duplicate UNIQUE constraint already exists. SQL0543 SQLCODE -543 SQLSTATE 23511 Explanation: Constraint &1 conflicts with SET NULL or SET DEFAULT rule. SQL0544 SQLCODE -544 SQLSTATE 23512 Explanation: CHECK constraint &1 cannot be added. SQL0545 SQLCODE -545 SQLSTATE 23513 Explanation: INSERT or UPDATE not allowed by CHECK constraint. SQL0546 SQLCODE -546 SQLSTATE 42621 Explanation: CHECK condition of constraint &1 not valid. SQL0551 SQLCODE -551 SQLSTATE 42501 Explanation: Not authorized to object &1 in &2 type *&3. SQL0552 SQLCODE -552 SQLSTATE 42502 Explanation: Not authorized to &1. SQL0557 SQLCODE -557 SQLSTATE 42852 Explanation: Privilege not valid for table or view &1 in &2. SQL0573 SQLCODE -573 SQLSTATE 42890 Explanation: Table does not have matching parent key. SQL0574 SQLCODE -574 SQLSTATE 42894 Explanation: Default value not valid. SQL0577 SQLCODE -577 SQLSTATE 38002, 2F002 Explanation: Modifying SQL data not permitted. SQL0578 SQLCODE -578 SQLSTATE 2F005 Explanation: RETURN statement not executed for SQL function &1 in &2. SQL0579 SQLCODE -579 SQLSTATE 38004, 2F004 Explanation: Reading SQL data not permitted. SQL0580 SQLCODE -580 SQLSTATE 42625 Explanation: At least one result in CASE expression must be not NULL. SQL0581 SQLCODE -581 SQLSTATE 42804 Explanation: The results in a CASE expression are not compatible. SQL0583 SQLCODE -583 SQLSTATE 42845 Explanation: Use of function &1 in &2 not valid. SQL0585 SQLCODE -585 SQLSTATE 42732 Explanation: Library &1 is used incorrectly on the SET PATH statement SQL0590 SQLCODE -590 SQLSTATE 42734 Explanation: Name &1 specified in &2 not unique. SQL0601 SQLCODE -601 SQLSTATE 42710 Explanation: Object &1 in &2 type *&3 already exists. SQL0602 SQLCODE -602 SQLSTATE 54008 Explanation: More than 120 columns specified for CREATE INDEX. SQL0603 SQLCODE -603 SQLSTATE 23515 Explanation: Unique index cannot be created because of duplicate keys. SQL0604 SQLCODE -604 SQLSTATE 42611 Explanation: Attributes of column not valid. SQL0607 SQLCODE -607 SQLSTATE 42832 Explanation: Operation not allowed on system table &1 in &2. SQL0612 SQLCODE -612 SQLSTATE 42711 Explanation: &1 is a duplicate column name. SQL0613 SQLCODE -613 SQLSTATE 54008 Explanation: Primary or unique key constraint too long. SQL0614 SQLCODE -614 SQLSTATE 54008 Explanation: Length of columns for CREATE INDEX too long. SQL0615 SQLCODE -615 SQLSTATE 55006 Explanation: Object &1 in &2 type *&3 not dropped. It is in use. SQL0616 SQLCODE -616 SQLSTATE 42893 Explanation: &1 in &2 type &3 cannot be dropped with RESTRICT. SQL0624 SQLCODE -624 SQLSTATE 42889 Explanation: Table already has primary key. SQL0628 SQLCODE -628 SQLSTATE 42613 Explanation: Clauses are mutually exclusive. SQL0629 SQLCODE -629 SQLSTATE 42834 Explanation: SET NULL not allowed for referential constraint. SQL0631 SQLCODE -631 SQLSTATE 54008 Explanation: Foreign key for referential constraint too long. SQL0637 SQLCODE -637 SQLSTATE 42614 Explanation: Duplicate &1 keyword. SQL0642 SQLCODE -642 SQLSTATE 54021 Explanation: Maximum number of constraints exceeded. SQL0658 SQLCODE -658 SQLSTATE 42917 Explanation: Function cannot be dropped. SQL0666 SQLCODE -666 SQLSTATE 57005 Explanation: Estimated query processing time exceeds limit. SQL0667 SQLCODE -667 SQLSTATE 23520 Explanation: Foreign key does not match a value in the parent key. SQL0675 SQLCODE -675 SQLSTATE 42892 Explanation: Specified delete rule not allowed with existing trigger. SQL0679 SQLCODE -679 SQLSTATE 57006 Explanation: Object &1 in &2 type *&3 not created due to pending operation. SQL0683 SQLCODE -683 SQLSTATE 42842 Explanation: FOR DATA or CCSID clause not valid for specified type. SQL0707 SQLCODE -707 SQLSTATE 42939 Explanation: Name &1 in &2 not allowed for distinct type. SQL0713 SQLCODE -713 SQLSTATE 42815 Explanation: Host variable for &2 is NULL. SQL0724 SQLCODE -724 SQLSTATE 54038 Explanation: Too many cascaded trigger programs. SQL0751 SQLCODE -751 SQLSTATE 42987 Explanation: SQL statement &1 not allowed in stored procedure or trigger. SQL0752 SQLCODE -752 SQLSTATE 0A001 Explanation: Connection cannot be changed. Reason code is &1. SQL0773 SQLCODE -773 SQLSTATE 20000 Explanation: Case not found for CASE statement. SQL0774 SQLCODE -774 SQLSTATE 2D522 Explanation: Statement cannot be executed within a compound SQL statement. SQL0775 SQLCODE -775 SQLSTATE 42910 Explanation: Statement not allowed in a compound SQL statement. SQL0776 SQLCODE -776 SQLSTATE 428D4 Explanation: Cursor &1 specified in FOR statement not allowed. SQL0777 SQLCODE -777 SQLSTATE 42919 Explanation: Nested compound statements not allowed. SQL0778 SQLCODE -778 SQLSTATE 428D5 Explanation: End label &1 not same as begin label. SQL0779 SQLCODE -779 SQLSTATE 42736 Explanation: Label &1 specified on LEAVE statement not valid. SQL0780 SQLCODE -780 SQLSTATE 428D6 Explanation: UNDO specified for a handler and ATOMIC not specified. SQL0781 SQLCODE -781 SQLSTATE 42737 Explanation: Condition &1 specified in handler not defined. SQL0782 SQLCODE -782 SQLSTATE 428D7 Explanation: Condition value &1 specified in handler not valid. SQL0783 SQLCODE -783 SQLSTATE 42738 Explanation: Select list for cursor &1 in FOR statement not valid. SQL0784 SQLCODE -784 SQLSTATE 42860 Explanation: Check constraint &1 cannot be dropped. SQL0785 SQLCODE -785 SQLSTATE 428D8 Explanation: Use of SQLCODE or SQLSTATE not valid. SQL0802 SQLCODE -802 SQLSTATE 22003, 22012, 22023, 22504 Explanation: Data conversion or data mapping error. SQL0803 SQLCODE -803 SQLSTATE 23505 Explanation: Duplicate key value specified. SQL0804 SQLCODE -804 SQLSTATE 07002 Explanation: SQLDA not valid. SQL0805 SQLCODE -805 SQLSTATE 51002 Explanation: SQL package &1 in &2 not found. SQL0811 SQLCODE -811 SQLSTATE 21000 Explanation: Result of SELECT INTO or subquery more than one row. SQL0818 SQLCODE -818 SQLSTATE 51003 Explanation: Consistency tokens do not match. SQL0822 SQLCODE -822 SQLSTATE 51004 Explanation: Address in SQLDA not valid. SQL0827 SQLCODE -827 SQLSTATE 42862 Explanation: &1 in &2 type *SQLPKG cannot be accessed. SQL0840 SQLCODE -840 SQLSTATE 54004 Explanation: Number of selected items exceeds 8000. SQL0842 SQLCODE -842 SQLSTATE 08002 Explanation: Connection already exists. SQL0843 SQLCODE -843 SQLSTATE 08003 Explanation: Connection does not exist. SQL0858 SQLCODE -858 SQLSTATE 08501 Explanation: Cannot disconnect relational database due to LU 6.2 protected conversation. SQL0862 SQLCODE -862 SQLSTATE 55029 Explanation: Local program attempted to connect to a remote relational database. SQL0871 SQLCODE -871 SQLSTATE 54019 Explanation: Too many CCSID values specified. SQL0900 SQLCODE -900 SQLSTATE 08003 Explanation: Application process not in a connected state. SQL0901 SQLCODE -901 SQLSTATE 58004 Explanation: SQL system error. SQL0904 SQLCODE -904 SQLSTATE 57011 Explanation: Resource limit exceeded. SQL0906 SQLCODE -906 SQLSTATE 24514 Explanation: Operation not performed because of previous error. SQL0907 SQLCODE -907 SQLSTATE 27000 Explanation: Attempt to change same row twice. SQL0910 SQLCODE -910 SQLSTATE 57007 Explanation: Object &1 in &2 type *&3 has a pending change. SQL0913 SQLCODE -913 SQLSTATE 57033 Explanation: Row or object &1 in &2 type *&3 in use. SQL0917 SQLCODE -917 SQLSTATE 42969 Explanation: Package not created. SQL0918 SQLCODE -918 SQLSTATE 51021 Explanation: Rollback required. SQL0950 SQLCODE -950 SQLSTATE 42705 Explanation: Relational database &1 not in relational database directory. SQL0951 SQLCODE -951 SQLSTATE 55007 Explanation: Object &1 in &2 not altered. It is in use. SQL0952 SQLCODE -952 SQLSTATE 57014 Explanation: Processing of the SQL statement ended by ENDRDBRQS command. SQL0969 SQLCODE -969 SQLSTATE 58033 Explanation: Unexpected client driver error. SQL0971 SQLCODE -971 SQLSTATE 57011 Explanation: Referential constraint &4 in check pending state. SQL5001 SQLCODE -5001 SQLSTATE 42703 Explanation: Column qualifier &2 undefined. SQL5002 SQLCODE -5002 SQLSTATE 42812 Explanation: Collection must be specified for table &1. SQL5003 SQLCODE -5003 SQLSTATE 42922 Explanation: Cannot perform operation under commitment control. SQL5005 SQLCODE -5005 SQLSTATE 42815 Explanation: Operator &4 not consistent with operands. SQL5012 SQLCODE -5012 SQLSTATE 42618 Explanation: Host variable not a numeric with zero scale. SQL5016 SQLCODE -5016 SQLSTATE 42833 Explanation: Object name &1 not valid for naming option. SQL5021 SQLCODE -5021 SQLSTATE 42930 Explanation: FOR UPDATE OF column &1 also in ORDER BY. SQL5023 SQLCODE -5023 SQLSTATE 26510 Explanation: Duplicate statement name in DECLARE CURSOR. SQL5024 SQLCODE -5024 SQLSTATE 42618 Explanation: Host variable &1 not character. SQL5047 SQLCODE -5047 SQLSTATE 42616 Explanation: Error processing SRTSEQ or LANGID parameter. SQL5051 SQLCODE -5051 SQLSTATE 42875 Explanation: Incorrect qualifier. SQL7001 SQLCODE -7001 SQLSTATE 42858 Explanation: File &1 in &2 not database file. SQL7002 SQLCODE -7002 SQLSTATE 42847 Explanation: Override parameter not valid. SQL7003 SQLCODE -7003 SQLSTATE 42857 Explanation: File &1 in &2 has more than one format. SQL7006 SQLCODE -7006 SQLSTATE 55018 Explanation: Cannot drop collection &1. SQL7007 SQLCODE -7007 SQLSTATE 51009 Explanation: COMMIT or ROLLBACK not valid. SQL7008 SQLCODE -7008 SQLSTATE 55019 Explanation: &1 in &2 not valid for operation. SQL7010 SQLCODE -7010 SQLSTATE 42850 Explanation: Logical file &1 in &2 not valid for CREATE VIEW. SQL7011 SQLCODE -7011 SQLSTATE 42851 Explanation: &1 in &2 not table, view, or physical file. SQL7017 SQLCODE -7017 SQLSTATE 42971 Explanation: Commitment control is already active to a DDM target. SQL7018 SQLCODE -7018 SQLSTATE 42970 Explanation: COMMIT HOLD or ROLLBACK HOLD not allowed. SQL7021 SQLCODE -7021 SQLSTATE 57043 Explanation: Local program attempting to run on application server. SQL7022 SQLCODE -7022 SQLSTATE 42977 Explanation: User &1 not the same as current user &2 for connect to local relational database. SQL7024 SQLCODE -7024 SQLSTATE 42876 Explanation: Index cannot be created because of CCSID incompatibility. SQL7026 SQLCODE -7026 SQLSTATE 42896 Explanation: Auxiliary storage pool not found. SQL7027 SQLCODE -7027 SQLSTATE 42984 Explanation: Unable to grant to a view. SQL7028 SQLCODE -7028 SQLSTATE 42944 Explanation: Unable to CHGOBJOWN for primary group. SQL7029 SQLCODE -7029 SQLSTATE 428B8 Explanation: New name &3 is not valid. SQL7031 SQLCODE -7031 SQLSTATE 54044 Explanation: Sort sequence table &1 too long. SQL7032 SQLCODE -7032 SQLSTATE 42904 Explanation: SQL procedure &1 in &2 not created. SQL7033 SQLCODE -7033 SQLSTATE 42923 Explanation: Alias name &1 in &2 not allowed. SQL7034 SQLCODE -7034 SQLSTATE 42926 Explanation: LOB locators are not allowed with COMMIT(*NONE). SQL7037 SQLCODE -7037 SQLSTATE 42835 Explanation: Data in a distributed file &1 in &2 cannot be redistributed. SQL7038 SQLCODE -7038 SQLSTATE 429B7 Explanation: Delete cascade not valid for &1 in &2. SQL7941 SQLCODE -7941 SQLSTATE 42981 Explanation: Application process not at commit boundary. SQL9012 SQLCODE -9012 SQLSTATE 42968 Explanation: DB2 UDB Query Manager and SQL Development Kit not available. SQ30000 SQLCODE -30000 SQLSTATE 58008 Explanation: Distributed Relational Database Architecture (DRDA) protocol error. SQ30001 SQLCODE -30001 SQLSTATE 57042 Explanation: Call to distributed SQL program not allowed. SQ30020 SQLCODE -30020 SQLSTATE 58009 Explanation: Distributed Relational Database Architecture (DRDA) protocol error. SQ30021 SQLCODE -30021 SQLSTATE 58010 Explanation: Distributed relational database not supported by the remote system. SQ30040 SQLCODE -30040 SQLSTATE 57012 Explanation: DDM resource &2 at relational database &1 not available. SQ30041 SQLCODE -30041 SQLSTATE 57013 Explanation: DDM resources at relational database &1 not available. SQ30050 SQLCODE -30050 SQLSTATE 58011 Explanation: DDM command &1 is not valid while bind process is in progress. SQ30051 SQLCODE -30051 SQLSTATE 58012 Explanation: Bind process for specified package name and consistency token not active. SQ30052 SQLCODE -30052 SQLSTATE 42932 Explanation: Program preparation assumptions not correct. SQ30053 SQLCODE -30053 SQLSTATE 42506 Explanation: Not authorized to create package for owner &1. SQ30060 SQLCODE -30060 SQLSTATE 08004 Explanation: User not authorized to relational database &1. SQ30061 SQLCODE -30061 SQLSTATE 08004 Explanation: Relational database &1 not found. SQ30070 SQLCODE -30070 SQLSTATE 58014 Explanation: Distributed Data Management (DDM) command &1 not supported. SQ30071 SQLCODE -30071 SQLSTATE 58015 Explanation: Distributed Data Management (DDM) object &1 not supported. SQ30072 SQLCODE -30072 SQLSTATE 58016 Explanation: Distributed Data Management (DDM) parameter &1 not supported. SQ30073 SQLCODE -30073 SQLSTATE 58017 Explanation: Distributed Data Management (DDM) parameter value &1 not supported. SQ30074 SQLCODE -30074 SQLSTATE 58018 Explanation: Distributed Data Management (DDM) reply message &1 not supported. SQ30080 SQLCODE -30080 SQLSTATE 08001 Explanation: Communication error occurred during distributed database processing. SQ30089 SQLCODE -30089 SQLSTATE 08001 Explanation: Communication error occurred during DB2 Multisystem processing. SQ30090 SQLCODE -30090 SQLSTATE 25000, 2D528, 2D529 Explanation: Change request not valid for read-only application server.

List of error messages between 1 and 999 in SQL Server 2017.

These error messages are all available by querying the sys.messages catalog view on the master database.

message_id severity is_event_logged text 21 20 0 Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator. 101 15 0 Query not allowed in Waitfor. 102 15 0 Incorrect syntax near ‘%.*ls’. 103 15 0 The %S_MSG that starts with ‘%.*ls’ is too long. Maximum length is %d. 104 15 0 ORDER BY items must appear in the select list if the statement contains a UNION, INTERSECT or EXCEPT operator. 105 15 0 Unclosed quotation mark after the character string ‘%.*ls’. 106 16 0 Too many table names in the query. The maximum allowable is %d. 107 15 0 The column prefix ‘%.*ls’ does not match with a table name or alias name used in the query. 108 15 0 The ORDER BY position number %ld is out of range of the number of items in the select list. 109 15 0 There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. 110 15 0 There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. 111 15 0 ‘%ls’ must be the first statement in a query batch. 112 15 0 Variables are not allowed in the %ls statement. 113 15 0 Missing end comment mark ‘*/’. 114 15 0 Browse mode is invalid for a statement that assigns values to a variable. 115 15 0 The FOR UPDATE clause is invalid for statements containing set operators. 116 15 0 Only one expression can be specified in the select list when the subquery is not introduced with EXISTS. 117 15 0 The %S_MSG name ‘%.*ls’ contains more than the maximum number of prefixes. The maximum is %d. 119 15 0 Must pass parameter number %d and subsequent parameters as ‘@name = value’. After the form ‘@name = value’ has been used, all subsequent parameters must be passed in the form ‘@name = value’. 120 15 0 The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match the number of INSERT columns. 121 15 0 The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match the number of INSERT columns. 122 15 0 The %ls option is allowed only with %ls syntax. 123 15 0 Batch/procedure exceeds maximum length of %d characters. 124 15 0 CREATE PROCEDURE contains no statements. 125 15 0 Case expressions may only be nested to level %d. 126 15 0 Invalid pseudocolumn «%.*ls». 127 15 0 A TOP N or FETCH rowcount value may not be negative. 128 15 0 The name «%.*s» is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted. 129 15 0 Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100. 130 16 0 Cannot perform an aggregate function on an expression containing an aggregate or a subquery. 131 15 0 The size (%d) given to the %S_MSG ‘%.*ls’ exceeds the maximum allowed for any data type (%d). 132 15 0 The label ‘%.*ls’ has already been declared. Label names must be unique within a query batch or stored procedure. 133 15 0 A GOTO statement references the label ‘%.*ls’ but the label has not been declared. 134 15 0 The variable name ‘%.*ls’ has already been declared. Variable names must be unique within a query batch or stored procedure. 135 15 0 Cannot use a BREAK statement outside the scope of a WHILE statement. 136 15 0 Cannot use a CONTINUE statement outside the scope of a WHILE statement. 137 15 0 Must declare the scalar variable «%.*ls». 138 15 0 Correlation clause in a subquery not permitted. 139 15 0 Cannot assign a default value to a local variable. 140 15 0 Can only use IF UPDATE within a CREATE TRIGGER statement. 141 15 0 A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations. 142 15 0 Incorrect syntax for definition of the ‘%ls’ constraint. 144 15 0 Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause. 145 15 0 ORDER BY items must appear in the select list if SELECT DISTINCT is specified. 146 15 0 Could not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded. 147 15 0 An aggregate may not appear in the WHERE clause unless it is in a subquery contained in a HAVING clause or a select list, and the column being aggregated is an outer reference. 148 15 0 Incorrect time syntax in time string ‘%.*ls’ used with WAITFOR. 149 15 0 Time value ‘%.*ls’ used with WAITFOR is not a valid value. Check date/time syntax. 150 15 0 Time value %d used with MAX_DURATION is not a valid value; MAX_DURATION wait time must be greater or equal to 0 and less or equal to %d. 151 15 0 ‘%.*ls’ is an invalid money value. 152 15 0 The same large data placement option «%.*ls» has been specified twice. 153 15 0 Invalid usage of the option %.*ls in the %ls statement. 154 15 0 %S_MSG is not allowed in %S_MSG. 155 15 0 ‘%.*ls’ is not a recognized %ls option. 156 15 0 Incorrect syntax near the keyword ‘%.*ls’. 157 15 0 An aggregate may not appear in the set list of an UPDATE statement. 158 15 0 An aggregate may not appear in the OUTPUT clause. 159 15 0 Must specify the table name and index name for the DROP INDEX statement. 160 15 0 Rule does not contain a variable. 161 15 0 Rule contains more than one variable. 162 15 0 Invalid expression in a TOP or OFFSET clause. 164 15 0 Each GROUP BY expression must contain at least one column that is not an outer reference. 165 16 0 Privilege %ls may not be granted or revoked. 166 15 0 ‘%ls’ does not allow specifying the database name as a prefix to the object name. 167 15 0 Cannot create %S_MSG on a temporary object. 168 15 0 The floating point value ‘%.*ls’ is out of the range of computer representation (%d bytes). 169 15 0 A column has been specified more than once in the order by list. Columns in the order by list must be unique. 171 15 0 Browse mode cannot be used with INSERT, SELECT INTO, or UPDATE statements. 172 15 0 Cannot use HOLDLOCK in browse mode. 173 15 0 The definition for column ‘%.*ls’ must include a data type. 174 15 0 The %.*ls function requires %d argument(s). 175 15 0 An aggregate may not appear in a computed column expression or check constraint. 176 15 0 The FOR BROWSE clause is no longer supported in views. 177 15 0 The IDENTITY function can only be used when the SELECT statement has an INTO clause. 178 15 0 A RETURN statement with a return value cannot be used in this context. 179 15 0 Cannot use the OUTPUT option when passing a constant to a stored procedure. 180 15 0 There are too many parameters in this %ls statement. The maximum number is %d. 181 15 0 Cannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement. 182 15 0 Table and column names must be supplied for the READTEXT or WRITETEXT utility. 183 15 0 The scale (%d) for column ‘%.*ls’ must be within the range %d to %d. 184 16 0 DEFAULT cannot be specified more than once for filegroups of the same content type. 185 15 0 Data stream is invalid for WRITETEXT statement in bulk form. 186 15 0 Data stream missing from WRITETEXT statement. 187 16 0 The valid range for MAX_QUEUE_READERS is 0 to 32767. 188 15 0 Cannot specify a log file in a CREATE DATABASE statement without also specifying at least one data file. 189 15 0 The %ls function requires %d to %d arguments. 190 15 0 An invalid date or time was specified in the statement. 191 15 0 Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries. 192 16 0 The scale must be less than or equal to the precision. 193 15 0 The object or column name starting with ‘%.*ls’ is too long. The maximum length is %d characters. 194 15 0 A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable. 195 15 0 ‘%.*ls’ is not a recognized %S_MSG. 196 15 0 SELECT INTO must be the first query in a statement containing a UNION, INTERSECT or EXCEPT operator. 197 15 0 EXECUTE cannot be used as a source when inserting into a table variable. 198 15 0 Browse mode is invalid for statements containing a UNION, INTERSECT or EXCEPT operator. 199 15 0 An INSERT statement cannot contain a SELECT statement that assigns values to a variable. 201 16 0 Procedure or function ‘%.*ls’ expects parameter ‘%.*ls’, which was not supplied. 202 16 0 Invalid type ‘%s’ for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports the INT and SMALLINT data types. 203 16 0 The name ‘%.*ls’ is not a valid identifier. 204 20 1 Normalization error in node %ls. 205 16 0 All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists. 206 16 0 Operand type clash: %ls is incompatible with %ls 207 16 0 Invalid column name ‘%.*ls’. 208 16 0 Invalid object name ‘%.*ls’. 209 16 0 Ambiguous column name ‘%.*ls’. 210 16 0 Conversion failed when converting datetime from binary/varbinary string. 211 23 1 Corruption in database ID %I64d, object ID %ld possibly due to schema or catalog inconsistency. Run DBCC CHECKCATALOG. 212 16 0 Expression result length exceeds the maximum. %d max, %d found. 213 16 0 Column name or number of supplied values does not match table definition. 214 16 0 Procedure expects parameter ‘%ls’ of type ‘%ls’. 215 16 0 Parameters supplied for object ‘%.*ls’ which is not a function. If the parameters are intended as a table hint, a WITH keyword is required. 216 16 0 Parameters were not supplied for the function ‘%.*ls’. 217 16 0 Maximum stored procedure, function, trigger, or view nesting level exceeded (limit %d). 218 16 0 Could not find the type ‘%.*ls’. Either it does not exist or you do not have the necessary permission. 219 16 0 The type ‘%.*ls’ already exists, or you do not have permission to create it. 220 16 0 Arithmetic overflow error for data type %ls, value = %ld. 221 10 0 FIPS Warning: Implicit conversion from %ls to %ls. 222 16 0 The base type «%.*ls» is not a valid base type for the alias data type. 223 11 0 Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default. 224 11 0 Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default. 225 16 0 The parameters supplied for the %ls «%.*ls» are not valid. 226 16 0 %ls statement not allowed within multi-statement transaction. 227 15 0 «%.*ls» is not a valid function, property, or field. 228 15 0 Method ‘%.*ls’ of type ‘%.*ls’ in assembly ‘%.*ls’ does not return any value. 229 14 0 The %ls permission was denied on the object ‘%.*ls’, database ‘%.*ls’, schema ‘%.*ls’. 230 14 0 The %ls permission was denied on the column ‘%.*ls’ of the object ‘%.*ls’, database ‘%.*ls’, schema ‘%.*ls’. 231 11 0 No such default. ID = %ld, database ID = %d. 232 16 0 Arithmetic overflow error for type %ls, value = %f. 233 16 0 The column ‘%.*ls’ in table ‘%.*ls’ cannot be null. 234 16 0 There is insufficient result space to convert a money value to %ls. 235 16 0 Cannot convert a char value to money. The char value has incorrect syntax. 236 16 0 The conversion from char data type to money resulted in a money overflow error. 237 16 0 There is insufficient result space to convert a money value to %ls. 239 16 0 Duplicate common table expression name ‘%.*ls’ was specified. 240 16 0 Types don’t match between the anchor and the recursive part in column «%.*ls» of recursive query «%.*ls». 241 16 0 Conversion failed when converting date and/or time from character string. 242 16 0 The conversion of a %ls data type to a %ls data type resulted in an out-of-range value. 243 16 0 Type %.*ls is not a defined system type. 244 16 0 The conversion of the %ls value ‘%.*ls’ overflowed an %hs column. Use a larger integer column. 245 16 0 Conversion failed when converting the %ls value ‘%.*ls’ to data type %ls. 246 16 0 No anchor member was specified for recursive query «%.*ls». 247 16 0 An anchor member was found in the recursive part of recursive query «%.*ls». 248 16 0 The conversion of the %ls value ‘%.*ls’ overflowed an int column. 249 16 0 The type «%ls» is not comparable. It cannot be used in the %ls clause. 251 16 0 Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded. 252 16 0 Recursive common table expression ‘%.*ls’ does not contain a top-level UNION ALL operator. 253 16 0 Recursive member of a common table expression ‘%.*ls’ has multiple recursive references. 254 16 0 Prefixed columns are not allowed in the column list of a PIVOT operator. 255 16 0 Pseudocolumns are not allowed in the column list of a PIVOT operator. 256 16 0 The data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary. 257 16 0 Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query. 258 15 0 Cannot call methods on %ls. 259 16 0 Ad hoc updates to system catalogs are not allowed. 260 16 0 Disallowed implicit conversion from data type %ls to data type %ls, table ‘%.*ls’, column ‘%.*ls’. Use the CONVERT function to run this query. 261 16 0 ‘%.*ls’ is not a recognized function. 262 16 0 %ls permission denied in database ‘%.*ls’. 263 16 0 Must specify table to select from. 264 16 0 The column name ‘%.*ls’ is specified more than once in the SET clause or column list of an INSERT. A column cannot be assigned more than one value in the same clause. Modify the clause to make sure that a column is updated only once. If this statement updates or inserts columns into a view, column aliasing can conceal the duplication in your code. 265 16 0 The column name «%.*ls» specified in the %ls operator conflicts with the existing column name in the %ls argument. 266 16 0 Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %ld, current count = %ld. 267 16 0 Object ‘%.*ls’ cannot be found. 268 16 0 Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option. 270 16 0 Object ‘%.*ls’ cannot be modified. 271 16 0 The column «%.*ls» cannot be modified because it is either a computed column or is the result of a UNION operator. 272 16 0 Cannot update a timestamp column. 273 16 0 Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column. 275 16 0 Prefixes are not allowed in value or pivot columns of an UNPIVOT operator. 276 16 0 Pseudocolumns are not allowed as value or pivot columns of an UNPIVOT operator. 277 16 0 The column «%.*ls» is specified multiple times in the column list of the UNPIVOT operator. 278 16 0 The text, ntext, and image data types cannot be used in a GROUP BY clause. 279 16 0 The text, ntext, and image data types are invalid in this subquery or aggregate expression. 280 16 0 Only base table columns are allowed in the TEXTPTR function. 281 16 0 %d is not a valid style number when converting from %ls to a character string. 282 10 0 The ‘%.*ls’ procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead. 283 16 0 READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger. 284 16 0 Rules cannot be bound to text, ntext, or image data types. 285 16 0 The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions. 286 16 0 The logical tables INSERTED and DELETED cannot be updated. 287 16 0 The %ls statement is not allowed within a trigger. 288 16 0 The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only. 289 16 0 Cannot construct data type %ls, some of the arguments have values which are not valid. 290 16 0 Invalid EXECUTE statement using object «%ls», method «%ls». 291 16 0 CAST or CONVERT: invalid attributes specified for type ‘%.*ls’ 292 16 0 There is insufficient result space to convert a smallmoney value to %ls. 293 16 0 Cannot convert char value to smallmoney. The char value has incorrect syntax. 294 16 0 The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error. 295 16 0 Conversion failed when converting character string to smalldatetime data type. 297 16 0 The user does not have permission to perform this action. 300 14 0 %ls permission was denied on object ‘%.*ls’, database ‘%.*ls’. 301 16 0 Query contains an outer-join request that is not permitted. 302 16 0 The newsequentialid() built-in function can only be used in a DEFAULT expression for a column of type ‘uniqueidentifier’ in a CREATE TABLE or ALTER TABLE statement. It cannot be combined with other operators to form a complex scalar expression. 303 16 0 The table ‘%.*ls’ is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular join clause. 304 16 0 ‘%I64d’ is out of range for index/statistics option ‘%.*ls’. See sp_configure option ‘%ls’ for valid values. 305 16 0 The XML data type cannot be compared or sorted, except when using the IS NULL operator. 306 16 0 The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator. 307 16 0 Index ID %d on table ‘%.*ls’ (specified in the FROM clause) does not exist. 308 16 0 Index ‘%.*ls’ on table ‘%.*ls’ (specified in the FROM clause) does not exist. 309 16 0 Cannot use index «%.*ls» on table «%.*ls» in a hint. XML indexes are not allowed in hints. 310 15 0 The value %d specified for the MAXRECURSION option exceeds the allowed maximum of %d. 311 16 0 Cannot use text, ntext, or image columns in the ‘inserted’ and ‘deleted’ tables. 312 16 0 Cannot reference text, ntext, or image columns in a filter stored procedure. 313 16 0 An insufficient number of arguments were supplied for the procedure or function %.*ls. 314 16 0 Cannot use GROUP BY ALL with the special tables INSERTED or DELETED. 315 16 0 Index «%.*ls» on table «%.*ls» (specified in the FROM clause) is disabled or resides in a filegroup which is not online. 316 16 0 The index ID %d on table «%.*ls» (specified in the FROM clause) is disabled or resides in a filegroup which is not online. 317 16 0 Table-valued function ‘%.*ls’ cannot have a column alias. 318 16 0 The table (and its columns) returned by a table-valued method need to be aliased. 319 16 0 Incorrect syntax near the keyword ‘with’. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon. 320 16 0 The compile-time variable value for ‘%.*ls’ in the OPTIMIZE FOR clause must be a literal. 321 15 0 «%.*ls» is not a recognized table hints option. If it is intended as a parameter to a table-valued function or to the CHANGETABLE function, ensure that your database compatibility mode is set to 90. 322 15 0 The variable «%.*ls» is specified in the OPTIMIZE FOR clause, but is not used in the query. 324 15 0 The ‘ALL’ version of the %.*ls operator is not supported. 325 15 0 Incorrect syntax near ‘%.*ls’. You may need to set the compatibility level of the current database to a higher value to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE. 326 16 0 Multi-part identifier ‘%.*ls’ is ambiguous. Both columns ‘%.*ls’ and ‘%.*ls’ exist. 327 16 0 Function call ‘%.*ls’ is ambiguous: both a user-defined function and a method call with this name exist. 328 16 0 A cursor plan could not be generated for the given statement because the textptr() function was used on a LOB column from one of the base tables. 329 16 0 Each GROUP BY expression must contain at least one column reference. 330 15 0 The target ‘%.*ls’ of the OUTPUT INTO clause cannot be a view or common table expression. 331 15 0 The target table ‘%.*ls’ of the OUTPUT INTO clause cannot have any enabled triggers. 332 15 0 The target table ‘%.*ls’ of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. Found reference constraint ‘%ls’. 333 15 0 The target table ‘%.*ls’ of the OUTPUT INTO clause cannot have any enabled check constraints or any enabled rules. Found check constraint or rule ‘%ls’. 334 15 0 The target table ‘%.*ls’ of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause. 335 16 0 Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name ‘%.*ls’ without parameters instead. 336 15 0 Incorrect syntax near ‘%.*ls’. If this is intended to be a common table expression, you need to explicitly terminate the previous statement with a semi-colon. 337 10 0 Warning: the floating point value ‘%.*ls’ is too small. It will be interpreted as 0. 338 16 0 READEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views, remote tables, and inserted or deleted tables inside triggers. 339 16 0 DEFAULT or NULL are not allowed as explicit identity values. 340 16 0 Cannot create the trigger «%.*ls» on view «%.*ls». AFTER triggers cannot be created on views. 341 16 0 Replication filter procedures may not contain columns of large object, large value, XML or CLR type. 342 16 0 Column «%.*ls» is not allowed in this context, and the user-defined function or aggregate «%.*ls» could not be found. 343 15 0 Unknown object type ‘%.*ls’ used in a CREATE, DROP, or ALTER statement. 344 16 0 Remote function reference ‘%.*ls’ is not allowed, and the column name ‘%.*ls’ could not be found or is ambiguous. 345 16 0 Function ‘%.*ls’ is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform this access. A function is assumed by default to perform data access if it is not schemabound. 346 15 0 The parameter «%.*ls» can not be declared READONLY since it is not a table-valued parameter. 347 16 0 The table-valued parameter «%.*ls» cannot be declared as an OUTPUT parameter. 348 16 0 The table variable «%.*ls» can not be passed to a stored procedure with the OUTPUT option. 349 16 0 The procedure «%.*ls» has no parameter named «%.*ls». 350 16 0 The column «%.*ls» does not have a valid data type. A column cannot be of a user-defined table type. 351 16 0 Column, parameter, or variable %.*ls. : Cannot find data type %.*ls. 352 15 0 The table-valued parameter «%.*ls» must be declared with the READONLY option. 353 16 0 Function ‘%.*ls’ is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. This is because the function performs user or system data access, or is assumed to perform this access. By default, a function is assumed to perform data access if it is not schema-bound. 354 16 0 The target ‘%.*ls’ of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 355 16 0 The target table ‘%.*ls’ of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 356 16 0 The target table ‘%.*ls’ of the INSERT statement cannot be on either side of a (primary key, foreign key) relationship when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found reference constraint ‘%ls’. 357 16 0 The target table ‘%.*ls’ of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found rule ‘%ls’. 358 16 0 The target table ‘%.*ls’ of the MERGE statement cannot have any enabled rules. Found rule ‘%ls’. 359 16 0 The target ‘%.*ls’ of an OUTPUT INTO clause has an index with the ignore_dup_key option and cannot be used when an OUTPUT clause is also used. 360 16 0 The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that contains the sparse column. Rewrite the statement to include either the sparse column or the column set, but not both. 361 16 0 The number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %d. This total number includes identity, timestamp, and columns that have default values. To correct this error, change the query to target a sparse column set instead of single sparse columns. 362 16 0 The query processor could not produce a query plan because the name ‘%.*ls’ in the FORCESEEK hint on table or view ‘%.*ls’ did not match the key column names of the index ‘%.*ls’. 363 16 0 The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ cannot be used with the %S_MSG specified by index ‘%.*ls’. 364 16 0 The query processor could not produce a query plan because the FORCESEEK hint on view ‘%.*ls’ is used without a NOEXPAND hint. Resubmit the query with the NOEXPAND hint or remove the FORCESEEK hint on the view. 365 16 0 The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ specified more seek columns than the number of key columns in index ‘%.*ls’. 366 16 0 The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ cannot be used with the column store index ‘%.*ls’. 367 16 0 The hint ‘%.*ls’ is valid only with memory optimized tables. 369 16 0 This operation is not supported on Windows Azure SQL Database with the TRCFLG_AUTO_PARTITION_REPLICATE traceflag turned on. 401 16 0 Unimplemented statement or expression %ls. 402 16 0 The data types %s and %s are incompatible in the %s operator. 403 16 0 Invalid operator for data type. Operator equals %ls, type equals %ls. 404 16 0 The column reference «%ls.%.*ls» is not allowed because it refers to a base table that is not being modified in this statement. 405 16 0 A remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement. 406 16 0 %ls cannot be used in the PIVOT operator because it is not invariant to NULLs. 407 16 0 Internal error. The string routine in file %hs, line %d failed with HRESULT 0x%x. 408 16 0 A constant expression was encountered in the ORDER BY list, position %i. 412 16 0 The column «%.*ls» is not updatable because it is derived or constant. 413 16 0 Correlated parameters or sub-queries are not supported by the inline function «%.*ls». 414 16 0 UPDATE is not allowed because the statement updates view «%.*ls» which participates in a join and has an INSTEAD OF UPDATE trigger. 415 16 0 DELETE is not allowed because the statement updates view «%.*ls» which participates in a join and has an INSTEAD OF DELETE trigger. 416 16 0 The service queue «%.*ls» cannot be directly updated. 417 16 0 TOP is not allowed in an UPDATE or DELETE statement against a partitioned view. 418 16 0 Objects exposing CLR type columns are not allowed in distributed queries. Use a pass-through query to access the remote object ‘%.*ls’. 421 16 0 The %ls data type cannot be selected as DISTINCT because it is not comparable. 422 16 0 Common table expression defined but not used. 423 16 0 Xml data type methods are not supported in check constraints. Create a scalar user-defined function to wrap the method invocation. The error occurred at table «%.*ls». 424 16 0 Xml data type methods are not supported in computed column definitions of table variables and return tables of table-valued functions. The error occurred at column «%.*ls», table «%.*ls», in the %ls statement. 425 16 0 Data type %ls of receiving variable is not equal to the data type %ls of column ‘%.*ls’. 426 16 0 The length %d of the receiving variable is less than the length %d of the column ‘%.*ls’. 427 20 1 Could not load the definition for constraint ID %d in database ID %d. Run DBCC CHECKCATALOG to verify the integrity of the database. 428 16 0 Insert bulk cannot be used in a multi-statement batch. 432 16 0 Xml data type methods are not supported in check constraints anymore. Please drop the constraint or create a scalar user-defined function to wrap the method invocation. The error occurred at table «%.*ls». 434 16 0 Function ‘%ls’ is not allowed in the OUTPUT clause. 435 16 0 Xml data type methods are not supported in computed column definitions. Create a scalar user-defined function to wrap the method invocation. The error occurred at column «%.*ls», table «%.*ls», in the %ls statement. 438 16 0 Xml data type methods are not allowed in rules. The error occurred at table «%.*ls». 440 16 0 Internal query compilation error. The stack overflow could not be handled. 441 16 0 Cannot use the ‘%ls’ function on a remote data source. 442 16 0 The NEST argument must be a column reference. Expressions are not allowed. 443 16 0 Invalid use of a side-effecting operator ‘%s’ within a function. 444 16 0 Select statements included within a function cannot return data to a client. 446 16 0 Cannot resolve collation conflict between «%ls» and «%ls» in %ls operator for %ls operation. 447 16 0 Expression type %ls is invalid for COLLATE clause. 448 16 0 Invalid collation ‘%.*ls’. 449 16 0 Collation conflict caused by collate clauses with different collation ‘%.*ls’ and ‘%.*ls’. 450 16 0 Code page translations are not supported for the text data type. From: %d To: %d. 451 16 0 Cannot resolve collation conflict between «%ls» and «%ls» in %ls operator occurring in %ls statement column %d. 452 16 0 COLLATE clause cannot be used on user-defined data types. 453 16 0 Collation ‘%.*ls’ is supported on Unicode data types only and cannot be set at the database or server level. 454 16 0 The UNNEST argument must be a nested table column. 455 16 0 The last statement included within a function must be a return statement. 456 16 0 Implicit conversion of %ls value to %ls cannot be performed because the resulting collation is unresolved due to collation conflict between «%ls» and «%ls» in %ls operator. 457 16 0 Implicit conversion of %ls value to %ls cannot be performed because the collation of the value is unresolved due to a collation conflict between «%ls» and «%ls» in %ls operator. 458 16 0 Cannot create the SELECT INTO target table «%.*ls» because the xml column «%.*ls» is typed with a schema collection «%.*ls» from database «%.*ls». Xml columns cannot refer to schemata across databases. 459 16 0 Collation ‘%.*ls’ is supported on Unicode data types only and cannot be applied to char, varchar or text data types. 460 16 0 DISTINCT operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 461 16 0 The TOP or OFFSET operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 462 16 0 Outer join is not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 463 16 0 Functions with parameters are not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 464 16 0 Functions with side effects are not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 465 16 0 Recursive references are not allowed in subqueries. 466 16 0 UNION operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 467 16 0 GROUP BY, HAVING, or aggregate functions are not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 468 16 0 Cannot resolve the collation conflict between «%.*ls» and «%.*ls» in the %ls operation. 469 16 0 An explicit column list must be specified for target table ‘%.*ls’ when table hint KEEPIDENTITY is used and the table contains an identity column. 470 16 0 The synonym «%.*ls» referenced synonym «%.*ls». Synonym chaining is not allowed. 471 16 0 Only one of the three options, SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB, can be specified. 472 16 0 Either a format file or one of the three options SINGLE_BLOB, SINGLE_CLOB, or SINGLE_NCLOB must be specified. 473 16 0 The incorrect value «%.*ls» is supplied in the PIVOT operator. 474 16 0 Unable to load the computed column definitions for table «%.*ls». 475 16 0 Invalid SAMPLE clause. Only table names in the FROM clause of SELECT, UPDATE, and DELETE queries may be sampled. 476 16 0 Invalid PERCENT tablesample size «%f» for table «%.*ls». The PERCENT tablesample size must be between 0 and 100. 477 16 0 Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table «%.*ls». The value or seed must be an integer. 478 16 0 The TABLESAMPLE clause cannot be used in a view definition or inline table function definition. 479 16 0 Invalid ROWS value or REPEATABLE seed «%I64d» in the TABLESAMPLE clause for table «%.*ls». The value or seed must be greater than 0. 480 16 0 The TABLESAMPLE clause cannot be used with the table function «%.*ls». 481 16 0 The TABLESAMPLE clause cannot be used with the linked server table «%.*ls». 482 16 0 Non-constant or invalid expression is in the TABLESAMPLE or the REPEATABLE clause. 483 16 0 The OUTPUT clause cannot be used in an INSERT…EXEC statement. 484 16 0 Cannot declare more than %d local variables. 485 16 0 Views and inline functions cannot return xml columns that are typed with a schema collection registered in a database other than current. Column «%.*ls» is typed with the schema collection «%.*ls», which is registered in database «%.*ls». 486 16 0 «%.*ls» does not allow specifying a schema name as a prefix to the assembly name. 487 16 0 An invalid option was specified for the statement «%.*ls». 488 16 0 %s columns must be comparable. The type of column «%.*ls» is «%s», which is not comparable. 489 16 0 The OUTPUT clause cannot be specified because the target view «%.*ls» is a partitioned view. 490 16 0 The resync functionality is temporarily disabled. 491 16 0 A correlation name must be specified for the bulk rowset in the from clause. 492 16 0 Duplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name «%.*ls» is a duplicate. 493 16 0 The column ‘%.*ls’ that was returned from the nodes() method cannot be used directly. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks. 494 16 0 The TABLESAMPLE clause can only be used with local tables. 495 16 0 The return table column «%.*ls» is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata. 496 16 0 The parameter «%.*ls» is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata. 497 16 0 Variables are not allowed in the TABLESAMPLE or REPEATABLE clauses. 498 16 0 Invalid value in the TABLESAMPLE or the REPEATABLE clause. 499 16 0 Invalid parameter for the getchecksum function. 500 16 0 Trying to pass a table-valued parameter with %d column(s) where the corresponding user-defined table type requires %d column(s). 505 16 0 The current user account was invoked with SETUSER or SP_SETAPPROLE. Changing databases is not allowed. 506 16 0 The invalid escape character «%.*ls» was specified in a %ls predicate. 507 16 0 Invalid argument for SET ROWCOUNT. Must be a non-null non-negative integer. 509 11 0 User name ‘%.*ls’ not found. 510 16 0 Cannot create a worktable row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint. 511 16 0 Cannot create a row of size %d which is greater than the allowable maximum row size of %d. 512 16 0 Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. 513 16 0 A column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. The conflict occurred in database ‘%.*ls’, table ‘%.*ls’, column ‘%.*ls’. 515 16 0 Cannot insert the value NULL into column ‘%.*ls’, table ‘%.*ls’; column does not allow nulls. %ls fails. 517 16 0 Adding a value to a ‘%ls’ column caused an overflow. 518 16 0 Cannot convert data type %ls to %ls. 522 16 0 The WAITFOR thread was evicted. 523 16 0 A trigger returned a resultset and/or was running with SET NOCOUNT OFF while another outstanding result set was active. 524 16 0 A trigger returned a resultset and the server option ‘disallow results from triggers’ is true. 525 16 0 The column that was returned from the nodes() method cannot be converted to the data type %ls. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks. 526 16 0 %ls of XML types constrained by different XML schema collections and/or DOCUMENT/CONTENT option is not allowed. Use the CONVERT function to run this query. 527 16 0 Implicit conversion between XML types constrained by different XML schema collections is not allowed. Use the CONVERT function to run this query. 529 16 0 Explicit conversion from data type %ls to %ls is not allowed. 530 16 0 The statement terminated. The maximum recursion %d has been exhausted before statement completion. 531 10 0 Cannot set NOCOUNT to OFF inside the trigger execution because the server option «disallow_results_from_triggers» is true or we are inside LOGON trigger execution. 532 16 0 The timestamp (changed to %S_TS) shows that the row has been updated by another user. 533 15 0 Cannot set XACT ABORT to OFF inside the trigger execution. 534 16 0 ‘%.*ls’ failed because it is not supported in the edition of this SQL Server instance ‘%.*ls’. See books online for more details on feature support in different SQL Server editions. 535 16 0 The %.*ls function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use %.*ls with a less precise datepart. 536 16 0 Invalid length parameter passed to the %ls function. 537 16 0 Invalid length parameter passed to the LEFT or SUBSTRING function. 539 16 0 Schema changed after the target table was created. Rerun the Select Into query. 540 16 1 There is insufficient system memory to run RAISERROR. 541 16 0 There is not enough stack to execute the statement 542 16 0 An invalid datetime value was encountered. Value exceeds the year 9999. 543 16 0 Creation of a return table failed for the table valued function ‘%.*ls’. 544 16 0 Cannot insert explicit value for identity column in table ‘%.*ls’ when IDENTITY_INSERT is set to OFF. 545 16 0 Explicit value must be specified for identity column in table ‘%.*ls’ either when IDENTITY_INSERT is set to ON or when a replication user is inserting into a NOT FOR REPLICATION identity column. 547 16 0 The %ls statement conflicted with the %ls constraint «%.*ls». The conflict occurred in database «%.*ls», table «%.*ls»%ls%.*ls%ls. 548 16 0 The insert failed. It conflicted with an identity range check constraint in database ‘%.*ls’, replicated table ‘%.*ls’%ls%.*ls%ls. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent. 549 16 0 The collation ‘%.*ls’ of receiving variable is not equal to the collation ‘%.*ls’ of column ‘%.*ls’. 550 16 0 The attempted insert or update failed because the target view either specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTION and one or more rows resulting from the operation did not qualify under the CHECK OPTION constraint. 552 16 0 CryptoAPI function ‘%ls’ failed. Error 0x%x: %ls 555 16 0 User-defined functions are not yet enabled. 556 16 0 INSERT EXEC failed because the stored procedure altered the schema of the target table. 557 16 0 Only functions and some extended stored procedures can be executed from within a function. 558 16 0 Remote function calls are not allowed within a function. 561 16 0 Failed to access file ‘%.*ls’ 562 16 0 Failed to access file ‘%.*ls’. Files can be accessed only through shares 563 14 0 The transaction for the INSERT EXEC statement has been rolled back. The INSERT EXEC operation will be terminated. 564 16 0 Attempted to create a record with a fixed length of ‘%d’. Maximum allowable fixed length is ‘%d’. 565 18 0 A stack overflow occurred in the server while compiling the query. Please simplify the query. 566 21 1 An error occurred while writing an audit trace. SQL Server is shutting down. Check and correct error conditions such as insufficient disk space, and then restart SQL Server. If the problem persists, disable auditing by starting the server at the command prompt with the «-f» switch, and using SP_CONFIGURE. 567 16 0 File ‘%.*ls’ is not a recognizable trace file. 568 16 0 Encountered an error or an unexpected end of trace file ‘%.*ls’. 569 16 0 The handle that was passed to %ls was invalid. 570 15 0 INSTEAD OF triggers do not support direct recursion. The trigger execution failed. 571 16 0 The specified attribute value for %ls is invalid. 572 16 0 Invalid regular expression «%.*ls» near the offset %d. 573 16 0 Evaluation of the regular expression is too complex: ‘%.*ls’. 574 16 0 %ls statement cannot be used inside a user transaction. 575 16 0 A LOGON trigger returned a resultset. Modify the LOGON trigger to not return resultsets. 576 16 0 Cannot create a row that has sparse data of size %d which is greater than the allowable maximum sparse data size of %d. 577 16 0 The value provided for the timeout is not valid. Timeout must be a valid integer between 0 and 2147483647. 578 16 0 Insert Exec not allowed in WAITFOR queries. 579 16 0 Can not execute WAITFOR query with snapshot isolation level. 582 16 0 Offset is greater than the length of the column to be updated in write. 583 16 0 Negative offset or length in write. 584 16 0 Select Into not allowed in WAITFOR queries. 585 16 0 Changing database context is not allowed when populating the resource database. 586 16 0 The prepared statement handle %d is not valid in this context. Please verify that current database, user default schema, and ANSI_NULLS and QUOTED_IDENTIFIER set options are not changed since the handle is prepared. 587 16 0 An invalid delayed CLR type fetch token is provided. 588 16 0 Multiple tasks within the session are using the same delayed CLR type fetch token at the same time. 589 16 0 This statement has attempted to access data whose access is restricted by the assembly. 590 16 0 RPC was aborted without execution. 591 16 0 %ls: The formal parameter «%ls» was defined as OUTPUT, but the actual parameter was not declared as OUTPUT. 592 16 0 Cannot find %S_MSG ID %d in database ID %d. 593 10 0 fn_trace_gettable: XML conversion of trace data for event 165 failed. 594 10 0 fn_trace_gettable: XML conversion of trace data is not supported in fiber mode. 595 16 0 Bulk Insert with another outstanding result set should be run with XACT_ABORT on. 596 16 0 Cannot continue the execution because the session is in the kill state. 597 16 0 The execution of in-proc data access is being terminated due to errors in the User Datagram Protocol (UDP). 598 16 0 An error occurred while executing CREATE/ALTER DB. Please look at the previous error for more information. 599 16 0 %.*ls: The length of the result exceeds the length limit (2GB) of the target large type. 601 12 0 Could not continue scan with NOLOCK due to data movement. 602 21 1 Could not find an entry for table or index with partition ID %I64d in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB. 603 21 1 Could not find an entry for table or index with object ID %d (partition ID %I64d) in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB. 605 21 1 Attempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d. 606 21 1 Metadata inconsistency. Filegroup id %ld specified for table ‘%.*ls’ does not exist. Run DBCC CHECKDB or CHECKCATALOG. 608 16 1 No catalog entry found for partition ID %I64d in database %d. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption. 609 16 0 BTree is not empty when waking up on RowsetBulk. 610 16 1 Invalid header value from a page. Run DBCC CHECKDB to check for a data corruption. 611 16 0 Cannot insert or update a row because total variable column size, including overhead, is %d bytes more than the limit. 613 21 0 Could not find an entry for worktable rowset with partition ID %I64d in database %d. 614 16 0 Could not locate bookmark due to data movement. 615 21 1 Could not find database ID %d, name ‘%.*ls’. The database may be offline. Wait a few minutes and try again. 617 20 1 Descriptor for object ID %ld in database ID %d not found in the hash table during attempt to unhash it. A work table is missing an entry. Rerun the query. If a cursor is involved, close and reopen the cursor. 622 16 0 The filegroup «%.*ls» has no files assigned to it. Tables, indexes, text columns, ntext columns, and image columns cannot be populated on this filegroup until a file is added. 627 16 0 Cannot use SAVE TRANSACTION within a distributed transaction. 628 16 0 Cannot issue SAVE TRANSACTION when there is no active transaction. 650 16 0 You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels. 651 16 0 Cannot use the %ls granularity hint on the table «%.*ls» because locking at the specified granularity is inhibited. 652 16 0 The index «%.*ls» for table «%.*ls» (RowsetId %I64d) resides on a read-only filegroup («%.*ls»), which cannot be modified. 657 16 0 Could not disable support for %ls in database ‘%.*ls’ because %S_MSG. 658 16 0 Could not enable support for %ls in database ‘%.*ls’ because %S_MSG. 661 16 0 Cannot enable support for %ls in database ‘%.*ls’ because support for %ls is enabled and both are mutually exclusive. 666 16 0 The maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %I64d. Dropping and re-creating the index may resolve this; otherwise, use another clustering key. 667 16 0 The index «%.*ls» for table «%.*ls» (RowsetId %I64d) resides on a filegroup («%.*ls») that cannot be accessed because it is offline, is being restored, or is defunct. 669 22 0 The row object is inconsistent. Please rerun the query. 670 16 0 Large object (LOB) data for table «%.*ls» resides on an offline filegroup («%.*ls») that cannot be accessed. 671 16 0 Large object (LOB) data for table «%.*ls» resides on a read-only filegroup («%.*ls»), which cannot be modified. 672 10 0 Failed to queue cleanup packets for orphaned rowsets in database «%.*ls». Some disk space may be wasted. Cleanup will be attempted again on database restart. 674 10 1 Exception occurred in destructor of RowsetNewSS 0x%p. This error may indicate a problem related to releasing pre-allocated disk blocks used during bulk-insert operations. Restart the server to resolve this problem. 675 10 1 Worktable with partition ID %I64d was dropped successfully after %d repeated attempts. 676 10 1 Error occurred while attempting to drop worktable with partition ID %I64d. 677 10 1 Unable to drop worktable with partition ID %I64d after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required. 678 10 1 Active rowset for partition ID %I64d found at the end of the batch. This error may indicate incorrect exception handling. Use the current activity window in SQL Server Management Studio or the Transact-SQL KILL statement to terminate the server process identifier (SPID) responsible for generating the error. 679 16 0 One of the partitions of index ‘%.*ls’ for table ‘%.*ls'(partition ID %I64d) resides on a filegroup («%.*ls») that cannot be accessed because it is offline, restoring, or defunct. This may limit the query result. 680 10 1 Error [%d, %d, %d] occurred while attempting to drop allocation unit ID %I64d belonging to worktable with partition ID %I64d. 681 16 0 Attempting to set a non-NULL-able column’s value to NULL. 682 16 0 Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption. 683 22 0 An internal error occurred while trying to convert between variable-length and fixed-length decimal formats. Run DBCC CHECKDB to check for any database corruption. 684 22 0 An internal error occurred while attempting to convert between compressed and uncompressed storage formats. Run DBCC CHECKDB to check for any corruption. 685 22 0 An internal error occurred while attempting to retrieve a backpointer for a heap forwarded record. 686 22 0 The maximum level of the B-Tree for rowset %I64d has been reached. SQL Server only supports upto 255 levels. 687 16 0 Cannot compress a nchar or nvarchar column that has an odd number of bytes. 688 16 0 Operation not allowed due to an active online index build. 689 16 0 Operation not allowed because of pending cleanup of online index build. Wait for cleanup to complete and re-run the operation. 691 16 1 An internal error occurred. Error code %X. 692 16 0 Internal error. Buffer provided to write a fixed column value is too large. Run DBCC CHECKDB to check for any corruption. 694 16 0 Internal error. Unable to create a block blob in Azure storage. 695 16 0 Internal error. Unable to delete a block blob in Azure storage. 696 16 0 Internal error. Unable to gain access to the tombstone table. 697 16 0 Internal error. Unable to get a blob storage container. 701 19 1 There is insufficient system memory in resource pool ‘%ls’ to run this query. 708 10 1 Server is running low on virtual address space or machine is running low on virtual memory. Reserved memory used %d times since startup. Cancel query and re-run, decrease server load, or cancel other applications. 801 20 1 A buffer was encountered with an unexpected status of 0x%x. 802 17 0 There is insufficient memory available in the buffer pool. 803 10 1 simulated failure (DEBUG only) 805 10 1 restore pending 806 10 1 audit failure (a page read from disk failed to pass basic integrity checks) 807 10 1 (no disk or the wrong disk is in the drive) 808 10 1 Insufficient bytes transferred. Common causes are backup configuration, insufficient disk space, or other problems with the storage subsystem such as corruption or hardware failure. Check errorlogs/application-logs for detailed messages and correct error conditions. 821 20 1 Could not unhash buffer at 0x%p with a buffer page number of %S_PGID and database ID %d with HASHED status set. The buffer was not found. %S_PAGE. Contact Technical Support. 822 21 1 Could not start I/O operation for request %S_BLKIOPTR. Contact Technical Support. 823 24 1 The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log and operating system error log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. 824 24 1 SQL Server detected a logical consistency-based I/O error: %ls. It occurred during a %S_MSG of page %S_PGID in database ID %d at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log or operating system error log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. 825 10 1 A read of the file ‘%ls’ at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and operating system error log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. 826 10 1 incorrect pageid (expected %d:%d; actual %d:%d) 829 21 1 Database ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore. 830 10 0 stale page (a page read returned a log sequence number (LSN) (%u:%u:%u) that is older than the last one that was written (%u:%u:%u)) 831 20 0 Unable to deallocate a kept page. 832 24 1 A page that should have been constant has changed (expected checksum: %08x, actual checksum: %08x, database %d, file ‘%ls’, page %S_PGID). This usually indicates a memory failure or other hardware or OS corruption. 833 10 0 SQL Server has encountered %d occurrence(s) of I/O requests taking longer than %d seconds to complete on file [%ls] in database id %d. The OS file handle is 0x%p. The offset of the latest long I/O is: %#016I64x 835 16 0 The operating system returned error %ls to SQL Server. It failed creating event for a %S_MSG at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log and operating system error log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. 844 10 0 Time out occurred while waiting for buffer latch — type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit id: %I64d%ls, task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Continuing to wait. 845 17 0 Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d. 846 10 0 A time-out occurred while waiting for buffer latch — type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit Id: %I64d%ls, task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Not continuing to wait. 847 10 1 Timeout occurred while waiting for latch: class ‘%ls’, id %p, type %d, Task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Continuing to wait. 848 10 1 Using large pages in the memory manager. 849 10 1 Using locked pages in the memory manager. 850 10 1 %I64u MB of large page memory allocated. 851 10 0 the page is in an OFFLINE file which cannot be read 852 10 1 Using conventional memory in the memory manager. 853 10 0 Latch acquire failed due to too many concurrent latches. type %d, Task 0x%p : %d 854 10 1 Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption. 855 10 1 Uncorrectable hardware memory corruption detected. Your system may become unstable. Please check the operating system error log for more details. 856 10 1 SQL Server has detected hardware memory corruption in database ‘%ls’, file ID: %u, page ID; %u, memory address: 0x%I64x and has successfully recovered the page. 857 10 0 Buffer pool extension «%.*ls» has been initialized successfully with size is %I64d MB. 858 10 0 Failed to create buffer pool extension of size %I64d MB on path «%.*ls». 859 10 1 Buffer pool extension configuration «%.*ls» is in wrong format. The format should be «<extension directory>,<size in GB>». 860 10 1 %ls. BUF address 0x%x. Bufno %u. Extension offset %1I64d. Error code %d. Database file id %u. Database file offset %2I64d. 861 10 1 Buffer pool extension size must be larger than the physical memory size %I64d MB. Buffer pool extension is not enabled. 862 10 1 Attempt to disable buffer pool extension when in state %ls is not allowed. 863 10 1 Attempt to enable buffer pool extension when in state %ls is not allowed. 864 10 1 Attempted to initialize buffer pool extension of size %1ld KB, but maximum allowed size is %2ld KB. 865 10 1 Buffer pool extension is only supported on Standard and Enterprise Editions of SQL Server. 866 10 1 Buffer pool extension is not supported on the %ls architecture. 867 10 0 Buffer pool extension has been disabled successfully. Deleting buffer pool extension «%.*ls». 868 10 1 Buffer pool extension size must be larger than the current memory allocation threshold %I64d MB. Buffer pool extension is not enabled. 869 10 1 Buffer pool extension «%.*ls» cannot be closed because %ld asynchronous I/Os are outstanding. 870 10 1 BPE feature switch is on! 871 10 1 Buffer pool extension size from RG Setting is %d GB (%I64d bytes). 872 10 1 Buffer pool extension is already enabled. No action is necessary. 873 10 1 Buffer pool extension is already disabled. No action is necessary. 874 10 0 Failed to initialize resilient buffer pool extension of size %I64d MB on path «%.*ls». 875 10 0 Resilient buffer pool extension «%.*ls» has been started successfully with size is %I64d MB. 876 10 0 Failed to startup resilient buffer pool extension of size %I64d MB on path «%.*ls». 877 10 0 Resilient buffer pool extension «%.*ls» has been enabled successfully with size %I64d MB. 878 10 0 Failed to create resilient buffer pool extension of size %I64d MB on path «%.*ls». 879 10 0 Failed to start resilient buffer pool extension because database %d is not memory optimized. 880 10 0 Failed to find the metadata of resilient buffer pool extension in database %d. 881 10 1 Resilient buffer pool extension is already disabled. No action is necessary. 882 22 0 The schema of a table created by InternalBaseTable is corrupt. 883 16 0 Could not create the Write Page Recorder table: wpr_bucket_table for database %ls. 884 16 0 Could not persist a bucket to the Write Page Recorder table: wpr_bucket_table for database %ls. 885 16 1 An internal error occurred. Error code %X. Context: «%ls::%d». 886 10 1 Resilient buffer pool extension is already enabled. No action is necessary. 891 10 1 Buffer pool extension is not supported on %ls platform. 902 16 0 To change the %ls, the database must be in state in which a checkpoint can be executed. 904 16 0 Database %ld cannot be autostarted during server shutdown or startup. 905 21 1 Database ‘%.*ls’ cannot be started in this edition of SQL Server because it contains a partition function ‘%.*ls’. Only Enterprise edition of SQL Server supports partitioning. 907 16 0 The database «%ls» has inconsistent database or file metadata. 908 10 1 Filegroup %ls in database %ls is unavailable because it is %ls. Restore or alter the filegroup to be available. 909 21 1 Database ‘%.*ls’ cannot be started in this edition of SQL Server because part or all of object ‘%.*ls’ is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterprise Edition. 910 10 0 Database ‘%.*ls’ is upgrading script ‘%.*ls’ from level %d to level %d. 911 16 0 Database ‘%.*ls’ does not exist. Make sure that the name is entered correctly. 912 21 0 Script level upgrade for database ‘%.*ls’ failed because upgrade step ‘%.*ls’ encountered error %d, state %d, severity %d. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion. 913 22 1 Could not find database ID %d. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred. 914 21 0 Script level upgrade for database ‘%.*ls’ failed because upgrade step ‘%.*ls’ was aborted before completion. If the abort happened during upgrade of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion. 915 21 0 Unable to obtain the current script level for database ‘%.*ls’. If the error happened during startup of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that script upgrade may run to completion. 916 14 0 The server principal «%.*ls» is not able to access the database «%.*ls» under the current security context. 917 21 0 An upgrade script batch failed to execute for database ‘%.*ls’ due to compilation error. Check the previous error message for the line which caused compilation to fail. 918 21 0 Failed to load the engine script metadata from script DLL ‘%.*ls’. The error code reported by the operating system was %d. This is a serious error condition, which usually indicates a corrupt or incomplete installation. Repairing the SQL Server instance may help resolve this error. 919 10 0 User ‘%.*ls’ is changing database script level entry %d to a value of %d. 920 20 0 Only members of the sysadmin role can modify the database script level. 921 14 0 Database ‘%.*ls’ has not been recovered yet. Wait and try again. 922 14 0 Database ‘%.*ls’ is being recovered. Waiting until recovery is finished. 923 14 0 Database ‘%.*ls’ is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it. 924 14 0 Database ‘%.*ls’ is already open and can only have one user at a time. 925 19 1 Maximum number of databases used for each query has been exceeded. The maximum allowed is %d. 926 14 0 Database ‘%.*ls’ cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. 927 14 0 Database ‘%.*ls’ cannot be opened. It is in the middle of a restore. 928 20 1 During upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause. 929 20 1 Unable to close a database that is not currently open. The application should reconnect and try again. If this action does not correct the problem, contact your primary support provider. 930 21 1 Attempting to reference recovery unit %d in database ‘%ls’ which does not exist. Contact Technical Support. 931 21 1 Attempting to reference database fragment %d in database ‘%ls’ which does not exist. Contact Technical Support. 932 21 1 SQL Server cannot load database ‘%.*ls’ because change tracking is enabled. The currently installed edition of SQL Server does not support change tracking. Either disable change tracking in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports change tracking. 933 21 1 Database ‘%.*ls’ cannot be started because some of the database functionality is not available in the current edition of SQL Server. 934 21 1 SQL Server cannot load database ‘%.*ls’ because Change Data Capture is enabled. The currently installed edition of SQL Server does not support Change Data Capture. Either restore database without KEEP_CDC option, or upgrade the instance to one that supports Change Data Capture. 935 21 1 The script level for ‘%.*ls’ in database ‘%.*ls’ cannot be downgraded from %d to %d, which is supported by this server. This usually implies that a future database was attached and the downgrade path is not supported by the current installation. Install a newer version of SQL Server and re-try opening the database. 936 16 0 Database ‘%.*ls’ can not be used in this edition of SQL Server. 937 21 1 Database ‘%.*ls’ cannot be upgraded because ‘%.*ls’ functionality is not available in the current edition of SQL Server. 938 21 1 The target database version %d is not supported by the current code version %d. Change target version to a supported level and restart the server. 941 16 0 Database ‘%.*ls’ cannot be opened because it is not started. Retry when the database is started. 942 14 0 Database ‘%.*ls’ cannot be opened because it is offline. 943 14 0 Database ‘%.*ls’ cannot be opened because its version (%d) is later than the current server version (%d). 944 10 0 Converting database ‘%.*ls’ from version %d to the current version %d. 945 16 0 Database ‘%.*ls’ cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. 946 14 1 Cannot open database ‘%.*ls’ version %d. Upgrade the database to the latest version. 947 16 1 Error while closing database ‘%.*ls’. Check for previous additional errors and retry the operation. 948 20 1 The database ‘%.*ls’ cannot be opened because it is version %d. This server supports version %d and earlier. A downgrade path is not supported. 949 16 0 tempdb is skipped. You cannot run a query that requires tempdb 950 20 1 Database ‘%.*ls’ cannot be upgraded because its non-release version (%d) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database. 951 10 0 Database ‘%.*ls’ running the upgrade step from version %d to version %d. 952 16 0 Database ‘%.*ls’ is in transition. Try the statement later. 954 14 0 The database «%.*ls» cannot be opened. It is acting as a mirror database. 955 14 0 Database %.*ls is enabled for Database Mirroring, but the database lacks quorum: the database cannot be opened. Check the partner and witness connections if configured. 956 14 0 Database %.*ls is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again later. 957 17 0 Database ‘%.*ls’ is enabled for database mirroring or has joined an availability group. The name of the database cannot be changed. 958 10 1 The resource database build version is %.*ls. This is an informational message only. No user action is required. 959 20 1 The resource database version is %d and this server supports version %d. Restore the correct version or reinstall SQL Server. 960 10 0 Warning: User «sys» (principal_id = %d) in database «%.*ls» has been renamed to «%.*ls». «sys» is a reserved user or schema name in this version of SQL Server. 961 10 0 Warning: Index «%.*ls» (index_id = %d) on object ID %d in database «%.*ls» was renamed to «%.*ls» because its name is a duplicate of another index on the same object. 962 10 0 Warning: Primary key or Unique constraint «%.*ls» (object_id = %d) in database «%.*ls» was renamed to «%.*ls» because its index was renamed. 963 10 0 Warning: Database «%.*ls» was marked suspect because of actions taken during upgrade. See errorlog or eventlog for more information. Use ALTER DATABASE to bring the database online. The database will come online in restricted_user state. 964 10 0 Warning: System user ‘%.*ls’ was found missing from database ‘%.*ls’ and has been restored. This user is required for SQL Server operation. 965 10 0 Warning: A column nullability inconsistency was detected in the metadata of index «%.*ls» (index_id = %d) on object ID %d in database «%.*ls». The index may be corrupt. Run DBCC CHECKTABLE to verify consistency. 966 10 0 Warning: Assembly «%.*ls» in database «%.*ls» has been renamed to «%.*ls» because the name of the assembly conflicts with a system assembly in this version of SQL Server. 967 10 0 Warning: The index «%.*ls» on «%.*ls».»%.*ls» is disabled because the XML data bound to it may contain negative values for xs:date and xs:dateTime which are not longer supported. 968 10 0 Warning: The XML facet on type «%.*ls» in schema collection «%.*ls» is updated from «%.*ls» to «%.*ls» because Sql Server does not support negative years inside values of type xs:date or xs:dateTime. 969 10 0 Warning: The default or fixed value on XML element or attribute «%.*ls» in schema collection «%.*ls» is updated from «%.*ls» to «%.*ls» because Sql Server does not support negative years inside values of type xs:date or xs:dateTime. 970 10 0 Warning: The XML instances in the XML column «%.*ls.%.*ls.%.*ls» may contain negative simple type values of type xs:date or xs:dateTime. It will be impossible to run XQuery or build a primary or selective XML index on these XML instances. 971 10 0 The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at ‘%.*ls’ instead of the currently attached resource database at ‘%.*ls’. 972 17 0 Could not use database ‘%d’ during procedure execution. 974 10 0 Attaching the resource database in the same directory as sqlservr.exe at ‘%.*ls’ failed as the database files do not exist. 975 10 1 System objects could not be updated in database ‘%.*ls’ because it is read-only. 976 14 0 The target database, ‘%.*ls’, is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other databases in the availability group, enable read access to one or more secondary availability replicas in the group. For more information, see the ALTER AVAILABILITY GROUP statement in SQL Server Books Online. 977 10 0 Warning: Could not find associated index for the constraint ‘%.*ls’ on object_id ‘%d’ in database ‘%.*ls’. 978 14 0 The target database (‘%.*ls’) is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Online. 979 14 0 The target database (‘%.*ls’) is in an availability group and currently does not allow read only connections. For more information about application intent, see SQL Server Books Online. 980 21 1 SQL Server cannot load database ‘%.*ls’ because it contains a columnstore index. The currently installed edition of SQL Server does not support columnstore indexes. Either disable the columnstore index in the database by using a supported edition of SQL Server, or upgrade the instance of SQL Server to a version that supports columnstore index. 981 10 0 Database manager will be using %d target database version. 982 14 0 Unable to access the ‘%.*ls’ database because no online secondary replicas are enabled for read-only access. Check the availability group configuration to verify that at least one secondary replica is configured for read-only access. Wait for an enabled replica to come online, and retry your read-only operation. 983 14 0 Unable to access availability database ‘%.*ls’ because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later. 984 21 1 Failed to perform a versioned copy of sqlscriptdowngrade.dll from Binn to BinnCache folder. VerInstallFile API failed with error code %d. 985 10 1 Successfully installed the file ‘%ls’ into folder ‘%ls’. 986 10 0 Couldn’t get a clean bootpage for database ‘%.*ls’ after %d tries. This is an informational message only. No user action is required. 987 23 1 A duplicate key insert was hit when updating system objects in database ‘%.*ls’. 988 14 0 Unable to access database ‘%.*ls’ because it lacks a quorum of nodes for high availability. Try the operation again later. 989 16 0 Failed to take the host database with ID %d offline when one or more of its partition databases is marked as suspect. 990 16 0 Taking the host database with ID %d offline because one or more of its partition databases is marked as suspect. 991 16 0 Failed to take the host database ‘%.*ls’ offline when one or more of its partition databases is marked as suspect. 992 16 0 Failed to get the shared lock on database ‘%.*ls’. 993 10 0 Redo for database ‘%.*ls’ applied version upgrade step from %d to %d. 994 10 0 Warning: Index «%.*ls» on «%.*ls».»%.*ls» is disabled because it contains a computed column. 995 10 0 Warning: Index «%.*ls» on «%.*ls».»%.*ls» is disabled. It cannot be upgraded as it resides on a read-only filegroup. 996 10 0 Warning: Index «%.*ls» on «%.*ls».»%.*ls» is disabled. This columnstore index cannot be upgraded, likely because it exceeds the row size limit of ‘%d’ bytes.

Понравилась статья? Поделить с друзьями:
  • Sql error 1861 22008 ora 01861 литерал не соответствует формату строки
  • Sql error 17410
  • Sql error 1024
  • Spn 625 fmi 2 камаз 5490 ошибка
  • Something script error garrys mod