精华内容
下载资源
问答
  • sqlcode

    2013-05-19 13:53:38
    sqlcode
  • SQLCode

    千次阅读 2014-11-02 21:57:55
    SQLCode:数据库操作的返回码,其中0--成功;-1--失败;100--没有检索到数据。[1]  例如,IF SQLCA.SQLCode then MessgeBox("连接失败","不能连接数据库") RETURN END IF 另外SQLCODE经常与...
    SQLCode:数据库操作的返回码,其中0--成功;-1--失败;100--没有检索到数据。[1] 
    例如,IF SQLCA.SQLCode<>0 then
    MessgeBox("连接失败","不能连接数据库")
    RETURN
    END IF
    另外SQLCODE经常与SQLERRM连用
    例如:
    DBMS_OUTPUT.PUT_LINE(SQLCODE||'----'||SQLERRM);
    展开全文
  • 常见sqlCode

    2017-09-08 17:27:32
    文档整理了执行数据库sql是常见的sqlCode及对应的原因分析,对于初学者搞笑解决常常遇到的sql执行问题很有益处。
  • db2 sqlcode errorcode

    2019-12-16 10:40:43
    DB2错误信息 sqlcode error code DB2 SQL Error: SQLCODE SQLSTATE
  • db2 sqlcode大全

    2018-08-05 20:16:49
    提供db2 sqlcode大全,包括所有的报错代码信息。。。。
  • SqlCode错误参数大全

    2018-03-30 10:32:40
    SqlCode错误参数大全,遇到一些常见的数据库错误,可以在sqlcode中快速找到错误原因
  • informix数据库SQlCode

    2015-03-06 00:37:14
    informix所有的sqlcode详解,希望可以帮助大家~
  • db2 sqlcode

    2017-01-16 16:40:00
    DB2错误信息(按sqlcode排序) sqlcode sqlstate 说明 000 00000 SQL语句成功完成 01xxx SQL语句成功完成,但是有警告 +012 01545 未限定的列名被解释为一个有相互关系的引用 +098 01568 动态SQL语句用分号结束...

    DB2错误信息(按sqlcode排序)
      sqlcode sqlstate 说明
      000 00000 SQL语句成功完成
      01xxx SQL语句成功完成,但是有警告
      +012 01545 未限定的列名被解释为一个有相互关系的引用
      +098 01568 动态SQL语句用分号结束
      +100 02000 没有找到满足SQL语句的行
      +110 01561 用DATA CAPTURE定义的表的更新操作不能发送到原来的子系统
      +111 01590 为2型索引设置了SUBPAGES语句
      +117 01525 要插入的值的个数不等于被插入表的列数
      +162 01514 指定的表空间被置为检查挂起状态
      +203 01552 使用非唯一的名字来解决命名的限定列
      +204 01532 命名的对象未在DB2中定义
      +206 01533 命名的列不在SQL语句中指定的任何表中存在
      +218 01537 因为SQL语句引用一个远程对象,不能为该SQL语句执行EXPLAIN
      +219 01532 命名的PLAN TABLE不存在
      +220 01546 不正确定义PLAN TABLE,检查命名列的定义
      +236 01005 SQLDA中的SQLN的值至少应于所描述的列的个数一样大
      +237 01594 至少有一个被描述的列应该是单值类型,因此扩展的SQLVAR条目需要另外的空间
      +238 01005 至少应有一个被描述的列是一个LOB,因此扩展的SQLVAR条目需要另外的空间
      +239 01005 至少应有一个被描述的列应是单值类型,因此扩展的SQLVAR条目需要另外的空间
      +304 01515 该值不能被分配给宿主变量,因为该值不再数据类型的范围之内
      +331 01520 不能被翻译的字符串,因此被设置为NULL
      +339 01569 由于与DB2 2.2版本的子系统连接,所以可能存在字符转换问题
      +394 01629 使用优化提示来选择访问路径
      +395 01628 设置了无效的优化提示,原因代码指定了为什么,忽略优化提示
      +402 01521 未知的位置
      +403 01522 本地不存在CREAT ALIAS对象
      +434 01608 在DB2未来发布的版本中将不支持指定的特性,IBM建议你停止使用这些特性
      +445 01004 值被CAST函数截取
      +462 01Hxx 由用户定义的函数或存储过程发出的警告
      +464 01609 命名的存储过程超出了它可能返回的查询结果集的个数限制
      +466 01610 指定由命名的存储过程返回的查询结果集的个数。成功完成
      +494 01614
      由存储过程返回的结果集的个数超过了由ASSOCIATE LOCATORS语句指定的结果集定
      位器的个数
      +495 01616 因为倒台SQL的成本估算超出了在ELST中指定的警告阀值,所以发出警告
      +535 01591 请求一个主健的定位更新,或请求一个使用自我引出 约束的表的删除操作
      +541 01543 命名外健是一个重复的引用约束
      +551 01548 命名的授权ID缺少在命名的DB2对象上执行命名操作的权限
      +552 01542 命名的授权ID缺少执行命名操作的权限
      +558 01516 已经被授权该PUBLIC,因此WITH GRANT OPTION不可用
      +561 01523 对ALTER REFERENCES INDEX 和TRIGGER特权,PUBLIC AT ALL LOCATION无效
      +562 01560 因为GRANTEE已经拥有这些特权,所以一个或更多的特权被忽略
      +585 01625 模式名指定了不止一次
      +599 01596 没有为长字符数据类型(BLOB,CLOB和DBCLOB)建立比较函数
      +610 01566
      由于建立了一个指定为DEFER YES的索引,指定的对象处于PENDING状态,或者因为
      使用了ALTER INDEX改变关键值的范围,所以指定的对象处于PENDING状态
      +625 01518 因为删除了主健索引,所以表定义被标注为不完整
      +626 01529 删除了加强UNIQUE约束的索引,唯一性不在被加强
      +645 01528 因为建立的索引中没有包含NULL,所以WHERE NOT NULL被忽略
      +650 01538 不能更改或者建立已命名的表为从属表
      +653 01551 在已指定的分区表空间中尚没有建立指定的分区索引,所以分区索引不可得
      +655 01597
      为CREATE或ALTER STOGROUP语句指定特定或者非特定的卷ID,在DB2较新发布的
      版本中(版本6以后)将不再支持他们
      +658 01600 当建立目录索引时,不能指定SUBPAGES语句,SUBPAGES将被忽略,并缺省为1
      +664 01540 分区索引的限制关键字超出了最大值
      +738 01530 已命名的对象的更改可能像只读系统中对象的改变要求一样
      +799 0157 SET语句中引用的特定寄存器不存在,将忽略 SET请求
      +802 01519 数据溢出或者因除法异常而引起的数据异常错误
      +806 01553 ISOLATION(RR)与LOCKSIZE PAGE 冲突
      +807 01554 由于十进制乘法导致溢出
      +863 01539 连接成功,但是只支持SBCS
      +2000 56094 SUBPAGES不等于1的1型索引不能成为数据共享环境中的缓冲池组依赖者
      +2002 01624 因为指定的缓冲池不允许超高速缓存,GNPCACHE指定被忽略
      +2007 01602 因为DB2子系统的参数禁用“提示(hiats)”所以不能指定优化提示
      +30100 01558 分布式协议错误被检测到,提供原来的SQLCODE和SQLSTATE
      -007 42601 SQL语句中由非法字符
      -010 42603 字符串常量非正常终止;检查到有遗漏的引号标志
      -029 42601 需要INTO语句
      -060 42815 某特定数据类型的长度或者标量规范无效
      -084 42612 不能执行SQL语句,因为该语句对动态SQL无效或者对OS/390的DB2无效
      -097 42601
      在单位类型、用户自定义的函数以及过程中不能使用带有CAST的LONG VARCHAR或LONG
      VARGRAPHIC
      -101 54001 SQL语句超出了已确定的DB2限制:例如,表的数目太多,语句中的字节太多
      -102 54002 字符串常量太长
      -103 42604 无效数学文字
      -104 42601 SQL语句中遇到非法符号
      -105 42604 无效的字符串格式;通常引用一个格式不正确的图形字符串
      -107 42622 对象名太长
      -108 42601 RENAME语句中指定的名字有错误,不能使用限定词
      -109 42601 指定了无效语句;例如CREATE VIEW不能包含ORDER BY 语句
      -110 42606 遇到了无效的十六进制的文字
      -111 42901 指定的列函数没有给出列名
      -112 42607 无效的列函数语法;列函数不能运行与其他的列函数之上
      -113 42602 遇到无效字符
      -114 42961 该语句的位置名称必须与当前服务器匹配,但是却没有匹配
      -115 42601 因为比较运算符没有伴着一个表达式或者列表,遇到了无效谓词
      -117 42802 待插入的数值的个数于被插入的行中的列数不相等
      -118 42902 数据修改语句(UPDATE或DELETE)和FROM语句中的表和视图命名不合法
      -119 42803 HAVING语句中的列的列表与GROUP BY语句中的列列表不匹配
      -120 42903 不允许WHERE语句、SET语句、VALUES语句或者SET ASSIGNMENT语句引用列函数
      -121 42701 在INSERT或UPDATE语句中,某一列被非法引用了两次
      -122 42803 非法使用了列函数。因为没有用于一个列函数的所有列不再GROUP BY语句中
      -123 42601 特定位置的参数必须是一个常数或者一个关键词
      -125 42805 ORDER BY语句中指定了无效数字,该数字要么小于1要么大于选定的列数
      -126 42829 不能为一个UPDATE语句指定ORDER BY语句
      -127 42905 在子选择中DISTINCT只能指定一次
      -128 42601 SQL谓词中NULL使用不当
      -129 54004 SQL语句中包含的表多于15个
      -130 22019 ESCAPE语句必须为一个字符
      22025 无效的ESCAPE模式
      -131 42818 LIKE谓词只能用于字符数据
      -132 42824 LIKE语句、ESCAPE语句、LOCATE函数或POSSTR函数中有无效运算对象
      -133 42906 无效相关子查询引用
      -134 42907 大于255字节的列被不正确使用
      -136 54005 排序关键字的长度大于4000字节
      -137 54006 被连接的字符串太大;字符的最大值为32767;图形的最大值为16382
      -138 22011 SUBSTR列函数的第二个或第三个操作符无效
      -142 42612
      不支持的SQL语句。该语句可能在另外的RDBMS上有效,也有可能在其他的上下文中有效
      (例如,VALUES只能在触发器中出现)
      -144 58003 指定的段号无效
      -147 42809 某一源函数不能更改。要改变源函数,必须删除该源函数并重新建立他
      -148 42809
      RENAME和ALTER无法执行。RENAME不能对视图或者活动RI.ST表重新命名。ALTER不能用
      于改变列的长度,因为该列参与了RI、一个用户退出程序、全局的临时表或打开DATA
      CAPTURE CHANGES表的列
      -150 42807 触发活动的INSERT,UPDATE或DELETE语句中指定了无效的视图更新或一个无效的转换表
      -151 42808 试图更新一个不可更新的视图的列、一个DB2 CATALOG表的列或者一个ROWID列
      -152 42809 DROP CHECK试图删除一个参照约束,或者DROP FOREIGN试图删除一个检查约束
      -153 42908
      无效的视图建立请求,必须为旋转列表中列出的列出的未命名的列或者重复的列提供一
      个名字
      -154 42909 不能用UNION、UNION ALL或者一个远程表建立视图
      -156 42809
      在视图上建立索引是非法的,或者在ALTER TABLE,CREATE TRIGGER,DROP TABLE或
      LOCK TABLE语句上指定一个不是表的其他对象这是无效的
      -157 42810 必须在FOREIGN KEY语句中指定一个表名
      -158 42811 视图的列和选择列表中的列不相匹配
      -159 42089 无效DROP或COMMENT ON语句
      -160 42813 对该视图的WITH CHECK OPTION无效
      -161 44000 正被更新的视图WITH CHECK OPTION语句使得这行不能被插入或更新
      -164 42502 用户没有建立这个视图的权限
      -170 42605 标量函数指定了无效的参数个数
      -171 42815 标量函数指定了无效的数据类型长度或者无效数值
      -173 42801 在非只读型的游标上不能指定隔离级别UR
      -180 22007 DATE、TIME、TIMESTAMP值的字符串表示法的语法不对
      -181 22001 不是有效的DATE、TIME、TIMESTAMP值
      -182 42816 在算术表达式中的日期/时间值无效
      -183 22008 在算术表达式中返回的日期/时间值的结果不在有效值的范围内
      -184 42610 没有正确使用日期/时间值的参数标记
      -185 57008 没有定义本定的日期/时间出口
      -186 22505 改变本定的日期/时间出口引发这个程序的长度无效
      -187 22506 MVS返回无效的当前日期/时间
      -188 22503 字符串表示无效
      -189 22522 指定的编码字符集的ID无效或没有定义
      -190 42837 不能象所设定的那样改变(ALTER)列。只能改变(ALTER)VARCHAR列的长度
      -191 22504 字符串中包含了无效的混合数据
      -197 42877 当两个或多个表被联合在一起排序时,限定的列名不能在ORDER BY语句中使用
      -198 42617 试图对空的字符串发布一个PREPARE或EXECUTE IMMEDIATE语句
      -199 42601 SQL语句中使用了非法关键词
      -203 42702 模糊列引用
      -204 42704 没有定义的对象名
      -205 42703 指定的表的列名无效
      -206 42703 列名没有在FROM语句所引用的任何表中,或者没有在定义触发器所在的表中
      -208 42707 不能ORDER BY指定列,应为该列不在选择列表中
      -212 42712 指定的表名在触发器中不允许多次使用,只能使用一次
      -214 42822 DISTINCT、ORDER BY 引起的无效表达式
      -219 42704 因为PLAN_TABLE不存在,EXPLAIN无法执行
      -220 55002 遇到无效的PLAN_TABLE列
      -221 55002 如果为PLAN_TABLE定义了可供选择的列,那么,必须定义所有的列
      -229 42708 指定的现场找不到
      -240 428B4 LOCK TABLE语句的PART子句无效
      -250 42718 没有定义本地位置名
      -251 42602 记号无效
      -300 22024 宿主变量或参数中的字符串不是以NULL为终止
      -301 42895 无效的宿主变量数据类型
      -302 22001 输入的变量值对指定的列无效
      22003 输入的变量值对指定的列而言太大
      -303 42806 因为数据类型不兼容,不能分配数值
      -304 22003 因为数据超出了范围,不能分配数值
      -305 22002 没有NULL指示符变量
      -309 22512 因为引用的宿主变量被设置成NULL,所以谓词无效
      -310 22501 十进制的宿主变量或参数包含非十进制数据
      -311 22501 输入的宿主变量长度无效,或者时负值或者太大
      -312 42618 没有定义宿主变量或者宿主变量不可用
      -313 07001 宿主变量的个数不等于参数标识的个数
      -314 42714 模糊的宿主变量引用
      -327 22525 在最后分区的关键字范围内,不能插入行
      -330 22021 不能成功的翻译字符串
      -331 22021 字符串不能分配到宿主变量,因为其不能成功的被翻译
      -332 57017 不能为两个命名的编码字符集的ID定义翻译规则
      -333 56010 子类型无效导致翻译失败
      -338 42972 ON语句无效,必须引用连接的列
      -339 56082 访问DB2 2.2版本的子系统被拒绝,原因时ASCII到EBCDIC翻译不能进行
      -350 42962 无效的大对象规范
      -351 56084 SELECT列表中有不支持的数据类型
      -352 56084 输入列表中有不支持的数据类型
      -355 42993 LOB列太大,以至不能被记录在日志中
      -372 428C1 每个表只允许有一个ROWID列
      -390 42887 在上下文中指定的函数无效
      -392 42855 自从前一次FETCH以来,指定游标的SQLDA已被不恰当的改变
      -396 38505 在最后的访问过程中,视图执行SQL语句
      -397 428D3 在某一列上不恰当的指定了GENERATED因为该列不是ROWID数据类型
      -398 428D2 为某一个宿主变量请求LOCATOR,但是该宿主变量不是一个LOB
      -399 22511 在INSERT语句中为ROWID列指定的值无效
      -400 54027 在DB2编目中定义的用户自定义索引不能超过100个
      -401 42818 算术操作符或比较操作符的操作对象不是兼容的
      -402 42819 算术函数不能用于字符或日期时间数据
      -404 22001 SQL语句指定的字符串太长
      -405 42820 数值文字超出了范围
      -406 22003 计算出的或者倒出的数值超出了范围
      -407 23502 不能把NULL值插到定义为NOT NULL的列中
      -408 42821 数值不能被更新或插入,因为他与列的数据类型不兼容
      -409 42607 COUNT函数指定的运算对象无效
      -410 42820 浮点文字笔30个字符的最大允许长度长
      -411 56040 CURRENT SQLID使用无效
      -412 42823 在子查询的选择列表中遇到了多个列
      -413 22003 当转换为一个数字型数据类型时,数据溢出
      -414 42824 LIKE谓词不能运行于用数字或日期时间类型定义的列
      -415 42825 为UNION操作指定的选择列表不是联合兼容的
      -416 42907 包含UNION操作符的SQL语句不允许有长的字符串列
      -417 42609 两参数标识符作为运算对象被指定在同一谓词的两边
      -418 42610 参数标识符使用无效
      -419 42911 十进制除法无效
      -420 22018 字符串自变量值不符合函数的要求
      -421 42826 UNION操作的选择列表中没有提供相同数目的列
      -423 0F001 为LOB或结果集定位器指定的值无效
      -426 2D528 在不允许更新的应用服务器不允许执行COMMIT语句
      -427 2D529 在不允许更新的应用服务器不允许执行ROLLBACK语句
      -430 38503 在用户自定义的函数或存储过程中遇到了错误
      -433 22001 指定的值太长
      -435 428B3 无效的应用定义的SQLSTATE
      -438 xxxxx 使用了RAISE_ERROR函数的应用发出了一个错误
      -440 42884 存储过程或用户自定义函数的参数列表参数个数于预期的个数不匹配
      -441 42601 与标量函数一起使用DISTINCT或ALL是不正确的用法
      -443 42601 指定的外部函数返回错误的SQLSTATE
      -444 42724 与被称为存储过程或用户自定义函数有关的程序不能找到
      -449 42878
      对存储过程或用户自定义的 函数,CREATE或ALTER语句不正确(缺失EXTERNAL NAME 子
      句)
      -450 39501 存储过程或用户自定义函数写入存储器的值超过了参数声明的长度
      -451 42815 CREATE FUNCTION中指定了不正确的数据类型
      -453 42880 用户自定义函数中的RETURNS语句无效
      -454 42723 指定的函数识别标记与已存在的另一函数的识别标记冲突
      -455 42882 模式名不比配
      -456 42710 为用户自定义函数指定的函数名已经存在
      -457 42939 用户自定义函数或用户自定义类型正试图使用系统中定义的函数或者类型所用的名称
      -458 42883 没有找到函数
      -463 39001 特定的外部例程返回无效的SQLSTATE
      -469 42886 参数定义为OUT或INOUT的CALL语句必须提供宿主变量
      -470 39002 指定了NULL参数,但是该例程却不支持NULL 
      
      -471 55023 存储过程或用户自定义函数失败:提供原因代码 
      
      -472 24517 外部的函数程序使游标处于打开状态 
      
      -473 42918 用户自定义数据类型命名不能和系统定义的数据类型一样 
      
      -475 42866 结果类型不能被转换成RETURNS类型 
      
      -476 42725 在其模式中该函数不是独一无二的 
      
      -478 42893 不能DROP或REVOKE特定的对象,因为其他对象依赖于该对象 
      
      -480 51030 直到存储过程已经被CALL后,DESCRIBE PROCEDURE和ASSOCIATE LOCATORS才能被发布 
      
      -482 51030 存储过程不返回到任何一个定位器 
      
      -483 42885 CREATE FUNCTION语句中的参数个数与源函数中的参数个数不匹配 
      
      -487 38001 选择了NO SQL选项建立指定的存储过程或用户自定义函数,但却视图发布SQL语句 
       CREATE FUNCTION语句无效,因为该语句没有RETURNS语句或者因为该语句没有指定有效 
      -491 42601 的SOURCE或者EXTERNAL语句 
      
      -492 42879 指定函数的指定参数的个数有错误 
      
      -495 57051 语句的估计处理器成本超出了资源限制 
      
      -496 51033 语句无法执行,因为当前服务器与调用存储过程的服务器不同 
       指定的数据库超过了32767 OBID的上限,或者CREATE DATABASE语句使之达到了32511 
      -497 54041 DBID的上限 
      
      -499 24516 指定的游标已被分配到结果集,该结果集来自已经指定的存储过程 
      
      -500 24501 因为连接被破坏,WITH HOLD游标被关闭 
      
      -501 24501 在试图获取数据或关闭一个游标前必须打开一个游标 
      
      -502 24502 在没有关闭游标前不能再次打开游标 
       因为列在游标的FOR UPDATE OF语句中没有被指定,该游标用于获取该列,所以不能更 
      -503 42912 新该列 
      
      -504 34000 不能引用一个游标,因为他不是定义到程序里的 
      
      -507 24501 在试图更新或者删除WHERE CURRENT OF前,必须打开游标 
      
      -508 24504 因为被引用的游标当前不是处于数据行上,所以不能被更新或删除 
       除了在游标上指定的那个表(该表由WHERE CURRENT OF语句引用的)以外,再也不能从 
      -509 42827 别的表上更新数据 
      
      -510 42828 表或视图不能被修改 
      
      -511 42829 对不可修改的表或视图,FOR UPDATE OF语句无效 
      
      -512 56023 对远程对象的无效引用 
      
      -513 42924 一个别名不能再被定义成另外的别名 
      
      -514 26501 游标尚没有被准备 
      
      -516 26501 试图描述未准备好的SQL语句 
      
      -517 07005 因为SQL语句尚没有准备好,游标无效 
      
      -518 07003 试图执行尚没有准备好的SQL语句 
      
      -519 24506 当为游标的SQL语句发布一个准备语句是,游标不能是打开的 
      
      -525 51015 不能在已指定的程序包中执行SQL语句,因为在绑定时间内该程序包无效 
      
      -526 42995 在给定的上下文中,不能使用全局的临时表 
      
      -530 23503 对特定的约束名指定了无效的外健值 
       从版本5开始,父关键字的多行更新将试图删除一个外关键字依赖的父关键字值,在版 
      -531 23504 本5以前,当引用主关键值外健值当前存在时,试图更新该主健值 
      
      -532 23504 删除操作违反了已指定的参照约束 
      
      -533 21501 多行插入无效,试图将多行插到自我引用的表中 
      
      -534 21502 可改变主健列值的更新语句不能在同一时刻用于更新多行 
       当从自我引用表中删除数据或者更新主健列时,不能指定WHERE CURRENT OF。不是版本 
      -535 21502 5的子系统才调用该代码 
      
      -536 42914 因为某一特定表的参照约束存在,所以删除语句无效 
      
      -537 42709 在外健语句或主健语句的规范中,每个列的出现不能多于一次 
      -538 42830 无效的外健;不符合引用的表没有主健 
      
      -539 42888 不能定义外健,因为被引用的表没有主健 
       表定义不完整,直到为主健建立了唯一索引或UNIQUE语句、或者包含GENERATED BY 
      -540 57001 DEFAULT属性的ROWID列 
      
      -542 42831 可以为空的列不允许作为主健的一部分包含在内 
       因为该表是指定了SET NULL删除规则的参照约束的父表而且检查约束不允许NULL,所以 
      -543 23511 DELETE不能发生 
      
      -544 23512 不能用ALTER添加检查约束,因为已存在的某行与该检查约束冲突 
      
      -545 23513 INSERT或者UPDATE导致检查约束冲突 
      
      -546 42621 在CREATE或ALTER TABLE中指定的检查约束无效 
      
      -548 42621 因为指定的列而引起的检查约束无效 
      
      -549 42509 DYNAMICRULES(BIND)计划或程序包的无效SQL语句 
      
      -551 42501 用户试图对不拥有权限的特定的对象进行操作,或者表不存在 
      
      -552 42502 用户试图执行未被授权的操作 
      
      -553 42503 不能指定CURRENT SQLID,因为用户尚没有被允许改变那个ID 
      
      -554 42502 不能对你本身赋予一个权限 
      
      -555 42502 不能对你本身撤销一个权限 
      
      -556 42504 不能撤销用户没有拥有的权限 
      
      -557 42852 指定了不一致的授予或撤销关键词 
      
      -558 56025 为授予或撤销语句指定了无效的语句(一个或一组) 
      
      -559 57002 DB2权限机制已经禁用,授予或者撤销不能被发布 
      
      -567 42501 指定的权限ID缺少对指定的程序包的绑定权限 
      
      -571 25000 不允许多点更新 
      
      -573 42890 不能定义参照约束,因为已指定的父表中在指定的列上没有唯一健 
      
      -574 42864 指定的缺省与列定义冲突 
       试图修改用户自定义函数中的数据或者存储过程中的数据,但这些对象的建立没有选择 
      -577 38002 MODIFIES SQL DATA选项 
       试图修改用户自定义函数中的数据或者存储过程中的数据,但这些对象的建立没有选择 
      -579 38004 READ SQL DATA选项,也没有选择MODIFIES SQL DATA选项 
      
      -580 42625 CASE表达式中的结果表达式不能都是空的 
      
      -581 42804 CASE表达式中的结果表达式为不兼容的数据类型 
      
      -582 42625 SEARCHED-WHEN-CLAUSE中的查找条件指定了一个限定的、IN或EXISTS谓词 
      
      -583 42845 指定的函数失败,因为他不是决定性的,或者可能有外部动作 
      
      -585 42732 在当前路径中模式名不止一次出现 
      
      -586 42907 CURRENT PATH专用寄存器在长度上不能超过254字符 
      
      -587 428C6 项目引用的列表必须是同一个家族 
      
      -590 42734 在命名的存储过程或用户自定义的函数中的参数必须是独一无二的 
      
      -592 42510 没有授权权限,让你在WLM环境中建立的存储过程或者用户自定义函数 
      
      -601 42710 试图创建(或重命名)已经存在的对象 
      
      -602 54008 CREATE INDEX语句中指定的列太多 
      
      -603 23515 因为发现有重复值,所以不能建立唯一的索引 
      
      -604 42611 在CREATE或ALTER TABLE语句中的为数据类型指定的长度、精度以及标度无效 
       指定的INSERT、UPDATE或DELETE语句不能被发布,应为这些语句对DB2 CATLOG表执行写 
      -607 42832 操作 
      
      -611 53088 当LOCKSIZE是TABLE或者TABLESPACE时,LOCKMAX必须为0 
      
      -612 42711 在同一个表、索引或试图中不允许有重复列名 
      
      -613 54008 主健或UNIQUE约束太长或者包含了太多的列 
      
      -614 54008 已经超过了索引的内部健长度的最大长度(255)限制 
      
      -615 55006 不能删除这个程序包,因为该程序包目前正在执行 

    转载于:https://www.cnblogs.com/yelongsan/p/6290199.html

    展开全文
  • DB2 SQLCODE

    千次阅读 2016-06-01 10:00:27
    sqlcode sqlstate 说明  000 00000 SQL语句成功完成  01xxx SQL语句成功完成,但是有警告  +012 01545 未限定的列名被解释为一个有相互关系的引用  +098 01568 动态SQL语句用分号结束  +100 02000 没有...
    DB2错误信息
    sqlcode sqlstate 说明 
    000 00000 SQL语句成功完成 
    01xxx SQL语句成功完成,但是有警告 
    +012 01545 未限定的列名被解释为一个有相互关系的引用 
    +098 01568 动态SQL语句用分号结束 
    +100 02000 没有找到满足SQL语句的行 
    +110 01561 用DATA CAPTURE定义的表的更新操作不能发送到原来的子系统 
    +111 01590 为2型索引设置了SUBPAGES语句 
    +117 01525 要插入的值的个数不等于被插入表的列数 
    +162 01514 指定的表空间被置为检查挂起状态 
    +203 01552 使用非唯一的名字来解决命名的限定列 
    +204 01532 命名的对象未在DB2中定义 
    +206 01533 命名的列不在SQL语句中指定的任何表中存在 
    +218 01537 因为SQL语句引用一个远程对象,不能为该SQL语句执行EXPLAIN 
    +219 01532 命名的PLAN TABLE不存在 
    +220 01546 不正确定义PLAN TABLE,检查命名列的定义 
    +236 01005 SQLDA中的SQLN的值至少应于所描述的列的个数一样大 
    +237 01594 至少有一个被描述的列应该是单值类型,因此扩展的SQLVAR条目需要另外的空间 
    +238 01005 至少应有一个被描述的列是一个LOB,因此扩展的SQLVAR条目需要另外的空间 
    +239 01005 至少应有一个被描述的列应是单值类型,因此扩展的SQLVAR条目需要另外的空间 
    +304 01515 该值不能被分配给宿主变量,因为该值不再数据类型的范围之内 
    +331 01520 不能被翻译的字符串,因此被设置为NULL 
    +339 01569 由于与DB2 2.2版本的子系统连接,所以可能存在字符转换问题 
    +394 01629 使用优化提示来选择访问路径 
    +395 01628 设置了无效的优化提示,原因代码指定了为什么,忽略优化提示 
    +402 01521 未知的位置 
    +403 01522 本地不存在CREAT ALIAS对象 
    +434 01608 在DB2未来发布的版本中将不支持指定的特性,IBM建议你停止使用这些特性 
    +445 01004 值被CAST函数截取 
    +462 01Hxx 由用户定义的函数或存储过程发出的警告 
    +464 01609 命名的存储过程超出了它可能返回的查询结果集的个数限制 
    +466 01610 指定由命名的存储过程返回的查询结果集的个数。成功完成 
    +494 01614 由存储过程返回的结果集的个数超过了由ASSOCIATE LOCATORS语句指定的结果集定位器的个数 
    +495 01616 因为倒台SQL的成本估算超出了在ELST中指定的警告阀值,所以发出警告 
    +535 01591 请求一个主健的定位更新,或请求一个使用自我引出 约束的表的删除操作 
    +541 01543 命名外健是一个重复的引用约束 
    +551 01548 命名的授权ID缺少在命名的DB2对象上执行命名操作的权限 
    +552 01542 命名的授权ID缺少执行命名操作的权限 
    +558 01516 已经被授权该PUBLIC,因此WITH GRANT OPTION不可用 
    +561 01523 对ALTER REFERENCES INDEX 和TRIGGER特权,PUBLIC AT ALL LOCATION无效 
    +562 01560 因为GRANTEE已经拥有这些特权,所以一个或更多的特权被忽略 
    +585 01625 模式名指定了不止一次 
    +599 01596 没有为长字符数据类型(BLOB,CLOB和DBCLOB)建立比较函数 
    +610 01566 由于建立了一个指定为DEFER YES的索引,指定的对象处于PENDING状态,或者因为使用了ALTER INDEX改变关键值的范围,所以指定的对象处于PENDING状态 
    +625 01518 因为删除了主健索引,所以表定义被标注为不完整 
    +626 01529 删除了加强UNIQUE约束的索引,唯一性不在被加强 
    +645 01528 因为建立的索引中没有包含NULL,所以WHERE NOT NULL被忽略 
    +650 01538 不能更改或者建立已命名的表为从属表 
    +653 01551 在已指定的分区表空间中尚没有建立指定的分区索引,所以分区索引不可得 
    +655 01597 为CREATE或ALTER STOGROUP语句指定特定或者非特定的卷ID,在DB2较新发布的版本中(版本6以后)将不再支持他们 
    +658 01600 当建立目录索引时,不能指定SUBPAGES语句,SUBPAGES将被忽略,并缺省为1 
    +664 01540 分区索引的限制关键字超出了最大值 
    +738 01530 已命名的对象的更改可能像只读系统中对象的改变要求一样 
    +799 0157 SET语句中引用的特定寄存器不存在,将忽略 SET请求 
    +802 01519 数据溢出或者因除法异常而引起的数据异常错误 
    +806 01553 ISOLATION(RR)与LOCKSIZE PAGE 冲突 
    +807 01554 由于十进制乘法导致溢出 
    +863 01539 连接成功,但是只支持SBCS 
    +2000 56094 SUBPAGES不等于1的1型索引不能成为数据共享环境中的缓冲池组依赖者 
    +2002 01624 因为指定的缓冲池不允许超高速缓存,GNPCACHE指定被忽略 
    +2007 01602 因为DB2子系统的参数禁用“提示(hiats)”所以不能指定优化提示 
    +30100 01558 分布式协议错误被检测到,提供原来的SQLCODE和SQLSTATE 
    -007 42601 SQL语句中由非法字符 
    -010 42603 字符串常量非正常终止;检查到有遗漏的引号标志 
    -029 42601 需要INTO语句 
    -060 42815 某特定数据类型的长度或者标量规范无效 
    -084 42612 不能执行SQL语句,因为该语句对动态SQL无效或者对OS/390的DB2无效 
    -097 42601 在单位类型、用户自定义的函数以及过程中不能使用带有CAST的LONG VARCHAR或LONGVARGRAPHIC 
    -101 54001 SQL语句超出了已确定的DB2限制:例如,表的数目太多,语句中的字节太多 
    -102 54002 字符串常量太长 
    -103 42604 无效数学文字 
    -104 42601 SQL语句中遇到非法符号 
    -105 42604 无效的字符串格式;通常引用一个格式不正确的图形字符串 
    -107 42622 对象名太长 
    -108 42601 RENAME语句中指定的名字有错误,不能使用限定词 
    -109 42601 指定了无效语句;例如CREATE VIEW不能包含ORDER BY 语句 
    -110 42606 遇到了无效的十六进制的文字 
    -111 42901 指定的列函数没有给出列名 
    -112 42607 无效的列函数语法;列函数不能运行与其他的列函数之上 
    -113 42602 遇到无效字符 
    -114 42961 该语句的位置名称必须与当前服务器匹配,但是却没有匹配 
    -115 42601 因为比较运算符没有伴着一个表达式或者列表,遇到了无效谓词 
    -117 42802 待插入的数值的个数于被插入的行中的列数不相等 
    -118 42902 数据修改语句(UPDATE或DELETE)和FROM语句中的表和视图命名不合法 
    -119 42803 HAVING语句中的列的列表与GROUP BY语句中的列列表不匹配 
    -120 42903 不允许WHERE语句、SET语句、VALUES语句或者SET ASSIGNMENT语句引用列函数 
    -121 42701 在INSERT或UPDATE语句中,某一列被非法引用了两次 
    -122 42803 非法使用了列函数。因为没有用于一个列函数的所有列不再GROUP BY语句中 
    -123 42601 特定位置的参数必须是一个常数或者一个关键词 
    -125 42805 ORDER BY语句中指定了无效数字,该数字要么小于1要么大于选定的列数 
    -126 42829 不能为一个UPDATE语句指定ORDER BY语句 
    -127 42905 在子选择中DISTINCT只能指定一次 
    -128 42601 SQL谓词中NULL使用不当 
    -129 54004 SQL语句中包含的表多于15个 
    -130 22019 ESCAPE语句必须为一个字符 
     22025 无效的ESCAPE模式 
    -131 42818 LIKE谓词只能用于字符数据 
    -132 42824 LIKE语句、ESCAPE语句、LOCATE函数或POSSTR函数中有无效运算对象 
    -133 42906 无效相关子查询引用 
    -134 42907 大于255字节的列被不正确使用 
    -136 54005 排序关键字的长度大于4000字节 
    -137 54006 被连接的字符串太大;字符的最大值为32767;图形的最大值为16382 
    -138 22011 SUBSTR列函数的第二个或第三个操作符无效 
    -142 42612 不支持的SQL语句。该语句可能在另外的RDBMS上有效,也有可能在其他的上下文中有效(例如,VALUES只能在触发器中出现) 
    -144 58003 指定的段号无效 
    -147 42809 某一源函数不能更改。要改变源函数,必须删除该源函数并重新建立他 
    -148 42809 RENAME和ALTER无法执行。RENAME不能对视图或者活动RI.ST表重新命名。
               ALTER不能用于改变列的长度,因为该列参与了RI、一个用户退出程序、全局的临时表或打开DATACAPTURE CHANGES表的列 
    -150 42807 触发活动的INSERT,UPDATE或DELETE语句中指定了无效的视图更新或一个无效的转换表 
    -151 42808 试图更新一个不可更新的视图的列、一个DB2 CATALOG表的列或者一个ROWID列 
    -152 42809 DROP CHECK试图删除一个参照约束,或者DROP FOREIGN试图删除一个检查约束 
    -153 42908 无效的视图建立请求,必须为旋转列表中列出的列出的未命名的列或者重复的列提供一个名字 
    -154 42909 不能用UNION、UNION ALL或者一个远程表建立视图 
    -156 42809 在视图上建立索引是非法的,或者在ALTER TABLE,CREATE TRIGGER,DROP TABLE或LOCK TABLE语句上指定一个不是表的其他对象这是无效的 
    -157 42810 必须在FOREIGN KEY语句中指定一个表名 
    -158 42811 视图的列和选择列表中的列不相匹配 
    -159 42089 无效DROP或COMMENT ON语句 
    -160 42813 对该视图的WITH CHECK OPTION无效 
    -161 44000 正被更新的视图WITH CHECK OPTION语句使得这行不能被插入或更新 
    -164 42502 用户没有建立这个视图的权限 
    -170 42605 标量函数指定了无效的参数个数 
    -171 42815 标量函数指定了无效的数据类型长度或者无效数值 
    -173 42801 在非只读型的游标上不能指定隔离级别UR 
    -180 22007 DATE、TIME、TIMESTAMP值的字符串表示法的语法不对 
    -181 22001 不是有效的DATE、TIME、TIMESTAMP值 
    -182 42816 在算术表达式中的日期/时间值无效 
    -183 22008 在算术表达式中返回的日期/时间值的结果不在有效值的范围内 
    -184 42610 没有正确使用日期/时间值的参数标记 
    -185 57008 没有定义本定的日期/时间出口 
    -186 22505 改变本定的日期/时间出口引发这个程序的长度无效 
    -187 22506 MVS返回无效的当前日期/时间 
    -188 22503 字符串表示无效 
    -189 22522 指定的编码字符集的ID无效或没有定义 
    -190 42837 不能象所设定的那样改变(ALTER)列。只能改变(ALTER)VARCHAR列的长度 
    -191 22504 字符串中包含了无效的混合数据 
    -197 42877 当两个或多个表被联合在一起排序时,限定的列名不能在ORDER BY语句中使用 
    -198 42617 试图对空的字符串发布一个PREPARE或EXECUTE IMMEDIATE语句 
    -199 42601 SQL语句中使用了非法关键词 
    -203 42702 模糊列引用 
    -204 42704 没有定义的对象名 
    -205 42703 指定的表的列名无效 
    -206 42703 列名没有在FROM语句所引用的任何表中,或者没有在定义触发器所在的表中 
    -208 42707 不能ORDER BY指定列,应为该列不在选择列表中 
    -212 42712 指定的表名在触发器中不允许多次使用,只能使用一次 
    -214 42822 DISTINCT、ORDER BY 引起的无效表达式 
    -219 42704 因为PLAN_TABLE不存在,EXPLAIN无法执行 
    -220 55002 遇到无效的PLAN_TABLE列 
    -221 55002 如果为PLAN_TABLE定义了可供选择的列,那么,必须定义所有的列 
    -229 42708 指定的现场找不到 
    -240 428B4 LOCK TABLE语句的PART子句无效 
    -250 42718 没有定义本地位置名 
    -251 42602 记号无效 
    -300 22024 宿主变量或参数中的字符串不是以NULL为终止 
    -301 42895 无效的宿主变量数据类型 
    -302 22001 输入的变量值对指定的列无效 
     22003 输入的变量值对指定的列而言太大 
    -303 42806 因为数据类型不兼容,不能分配数值 
    -304 22003 因为数据超出了范围,不能分配数值 
    -305 22002 没有NULL指示符变量 
    -309 22512 因为引用的宿主变量被设置成NULL,所以谓词无效 
    -310 22501 十进制的宿主变量或参数包含非十进制数据 
    -311 22501 输入的宿主变量长度无效,或者时负值或者太大 
    -312 42618 没有定义宿主变量或者宿主变量不可用 
    -313 07001 宿主变量的个数不等于参数标识的个数 
    -314 42714 模糊的宿主变量引用 
    -327 22525 在最后分区的关键字范围内,不能插入行 
    -330 22021 不能成功的翻译字符串 
    -331 22021 字符串不能分配到宿主变量,因为其不能成功的被翻译 
    -332 57017 不能为两个命名的编码字符集的ID定义翻译规则 
    -333 56010 子类型无效导致翻译失败 
    -338 42972 ON语句无效,必须引用连接的列 
    -339 56082 访问DB2 2.2版本的子系统被拒绝,原因时ASCII到EBCDIC翻译不能进行 
    -350 42962 无效的大对象规范 
    -351 56084 SELECT列表中有不支持的数据类型 
    -352 56084 输入列表中有不支持的数据类型 
    -355 42993 LOB列太大,以至不能被记录在日志中 
    -372 428C1 每个表只允许有一个ROWID列 
    -390 42887 在上下文中指定的函数无效 
    -392 42855 自从前一次FETCH以来,指定游标的SQLDA已被不恰当的改变 
    -396 38505 在最后的访问过程中,视图执行SQL语句 
    -397 428D3 在某一列上不恰当的指定了GENERATED因为该列不是ROWID数据类型 
    -398 428D2 为某一个宿主变量请求LOCATOR,但是该宿主变量不是一个LOB 
    -399 22511 在INSERT语句中为ROWID列指定的值无效 
    -400 54027 在DB2编目中定义的用户自定义索引不能超过100个 
    -401 42818 算术操作符或比较操作符的操作对象不是兼容的 
    -402 42819 算术函数不能用于字符或日期时间数据 
    -404 22001 SQL语句指定的字符串太长 
    -405 42820 数值文字超出了范围 
    -406 22003 计算出的或者倒出的数值超出了范围 
    -407 23502 不能把NULL值插到定义为NOT NULL的列中 
    -408 42821 数值不能被更新或插入,因为他与列的数据类型不兼容 
    -409 42607 COUNT函数指定的运算对象无效 
    -410 42820 浮点文字笔30个字符的最大允许长度长 
    -411 56040 CURRENT SQLID使用无效 
    -412 42823 在子查询的选择列表中遇到了多个列 
    -413 22003 当转换为一个数字型数据类型时,数据溢出 
    -414 42824 LIKE谓词不能运行于用数字或日期时间类型定义的列 
    -415 42825 为UNION操作指定的选择列表不是联合兼容的 
    -416 42907 包含UNION操作符的SQL语句不允许有长的字符串列 
    -417 42609 两参数标识符作为运算对象被指定在同一谓词的两边 
    -418 42610 参数标识符使用无效 
    -419 42911 十进制除法无效 
    -420 22018 字符串自变量值不符合函数的要求 
    -421 42826 UNION操作的选择列表中没有提供相同数目的列 
    -423 0F001 为LOB或结果集定位器指定的值无效 
    -426 2D528 在不允许更新的应用服务器不允许执行COMMIT语句 
    -427 2D529 在不允许更新的应用服务器不允许执行ROLLBACK语句 
    -430 38503 在用户自定义的函数或存储过程中遇到了错误 
    -433 22001 指定的值太长 
    -435 428B3 无效的应用定义的SQLSTATE 
    -438 xxxxx 使用了RAISE_ERROR函数的应用发出了一个错误 
    -440 42884 存储过程或用户自定义函数的参数列表参数个数于预期的个数不匹配 
    -441 42601 与标量函数一起使用DISTINCT或ALL是不正确的用法 
    -443 42601 指定的外部函数返回错误的SQLSTATE 
    -444 42724 与被称为存储过程或用户自定义函数有关的程序不能找到 
    -449 42878 对存储过程或用户自定义的 函数,CREATE或ALTER语句不正确(缺失EXTERNAL NAME 子句) 
    -450 39501 存储过程或用户自定义函数写入存储器的值超过了参数声明的长度 
    -451 42815 CREATE FUNCTION中指定了不正确的数据类型 
    -453 42880 用户自定义函数中的RETURNS语句无效 
    -454 42723 指定的函数识别标记与已存在的另一函数的识别标记冲突 
    -455 42882 模式名不比配 
    -456 42710 为用户自定义函数指定的函数名已经存在 
    -457 42939 用户自定义函数或用户自定义类型正试图使用系统中定义的函数或者类型所用的名称 
    -458 42883 没有找到函数 
    -463 39001 特定的外部例程返回无效的SQLSTATE 
    -469 42886 参数定义为OUT或INOUT的CALL语句必须提供宿主变量 
    -470 39002 指定了NULL参数,但是该例程却不支持NULL 
    -471 55023 存储过程或用户自定义函数失败:提供原因代码 
    -472 24517 外部的函数程序使游标处于打开状态 
    -473 42918 用户自定义数据类型命名不能和系统定义的数据类型一样 
    -475 42866 结果类型不能被转换成RETURNS类型 
    -476 42725 在其模式中该函数不是独一无二的 
    -478 42893 不能DROP或REVOKE特定的对象,因为其他对象依赖于该对象 
    -480 51030 直到存储过程已经被CALL后,DESCRIBE PROCEDURE和ASSOCIATE LOCATORS才能被发布 
    -482 51030 存储过程不返回到任何一个定位器 
    -483 42885 CREATE FUNCTION语句中的参数个数与源函数中的参数个数不匹配 
    -487 38001 选择了NO SQL选项建立指定的存储过程或用户自定义函数,但却视图发布SQL语句 
    -491 42601 CREATE FUNCTION语句无效,因为该语句没有RETURNS语句或者因为该语句没有指定有效的SOURCE或者EXTERNAL语句 
    -492 42879 指定函数的指定参数的个数有错误 
    -495 57051 语句的估计处理器成本超出了资源限制 
    -496 51033 语句无法执行,因为当前服务器与调用存储过程的服务器不同 
    -497 54041 指定的数据库超过了32767 OBID的上限,或者CREATE DATABASE语句使之达到了32511DBID的上限 
    -499 24516 指定的游标已被分配到结果集,该结果集来自已经指定的存储过程 
    -500 24501 因为连接被破坏,WITH HOLD游标被关闭 
    -501 24501 在试图获取数据或关闭一个游标前必须打开一个游标 
    -502 24502 在没有关闭游标前不能再次打开游标 
    -503 42912 因为列在游标的FOR UPDATE OF语句中没有被指定,该游标用于获取该列,所以不能更新该列 
    -504 34000 不能引用一个游标,因为他不是定义到程序里的 
    -507 24501 在试图更新或者删除WHERE CURRENT OF前,必须打开游标 
    -508 24504 因为被引用的游标当前不是处于数据行上,所以不能被更新或删除 
    -509 42827 除了在游标上指定的那个表(该表由WHERE CURRENT OF语句引用的)以外,再也不能从别的表上更新数据 
    -510 42828 表或视图不能被修改 
    -511 42829 对不可修改的表或视图,FOR UPDATE OF语句无效 
    -512 56023 对远程对象的无效引用 
    -513 42924 一个别名不能再被定义成另外的别名 
    -514 26501 游标尚没有被准备 
    -516 26501 试图描述未准备好的SQL语句 
    -517 07005 因为SQL语句尚没有准备好,游标无效 
    -518 07003 试图执行尚没有准备好的SQL语句 
    -519 24506 当为游标的SQL语句发布一个准备语句是,游标不能是打开的 
    -525 51015 不能在已指定的程序包中执行SQL语句,因为在绑定时间内该程序包无效 
    -526 42995 在给定的上下文中,不能使用全局的临时表 
    -530 23503 对特定的约束名指定了无效的外健值 
    -531 23504 从版本5开始,父关键字的多行更新将试图删除一个外关键字依赖的父关键字值,在版本5以前,当引用主关键值外健值当前存在时,试图更新该主健值 
    -532 23504 删除操作违反了已指定的参照约束 
    -533 21501 多行插入无效,试图将多行插到自我引用的表中 
    -534 21502 可改变主健列值的更新语句不能在同一时刻用于更新多行 
    -535 21502 当从自我引用表中删除数据或者更新主健列时,不能指定WHERE CURRENT OF。不是版本5的子系统才调用该代码 
    -536 42914 因为某一特定表的参照约束存在,所以删除语句无效 
    -537 42709 在外健语句或主健语句的规范中,每个列的出现不能多于一次 
    -538 42830 无效的外健;不符合引用的表没有主健 
    -539 42888 不能定义外健,因为被引用的表没有主健 
    -540 57001 表定义不完整,直到为主健建立了唯一索引或UNIQUE语句、或者包含GENERATED BYDEFAULT属性的ROWID列 
    -542 42831 可以为空的列不允许作为主健的一部分包含在内 
    -543 23511 因为该表是指定了SET NULL删除规则的参照约束的父表而且检查约束不允许NULL,所以DELETE不能发生 
    -544 23512 不能用ALTER添加检查约束,因为已存在的某行与该检查约束冲突 
    -545 23513 INSERT或者UPDATE导致检查约束冲突 
    -546 42621 在CREATE或ALTER TABLE中指定的检查约束无效 
    -548 42621 因为指定的列而引起的检查约束无效 
    -549 42509 DYNAMICRULES(BIND)计划或程序包的无效SQL语句 
    -551 42501 用户试图对不拥有权限的特定的对象进行操作,或者表不存在 
    -552 42502 用户试图执行未被授权的操作 
    -553 42503 不能指定CURRENT SQLID,因为用户尚没有被允许改变那个ID 
    -554 42502 不能对你本身赋予一个权限 
    -555 42502 不能对你本身撤销一个权限 
    -556 42504 不能撤销用户没有拥有的权限 
    -557 42852 指定了不一致的授予或撤销关键词 
    -558 56025 为授予或撤销语句指定了无效的语句(一个或一组) 
    -559 57002 DB2权限机制已经禁用,授予或者撤销不能被发布 
    -567 42501 指定的权限ID缺少对指定的程序包的绑定权限 
    -571 25000 不允许多点更新 
    -573 42890 不能定义参照约束,因为已指定的父表中在指定的列上没有唯一健 
    -574 42864 指定的缺省与列定义冲突 
    -577 38002 试图修改用户自定义函数中的数据或者存储过程中的数据,但这些对象的建立没有选择MODIFIES SQL DATA选项 
    -579 38004 试图修改用户自定义函数中的数据或者存储过程中的数据,但这些对象的建立没有选择READ SQL DATA选项,也没有选择MODIFIES SQL DATA选项 
    -580 42625 CASE表达式中的结果表达式不能都是空的 
    -581 42804 CASE表达式中的结果表达式为不兼容的数据类型 
    -582 42625 SEARCHED-WHEN-CLAUSE中的查找条件指定了一个限定的、IN或EXISTS谓词 
    -583 42845 指定的函数失败,因为他不是决定性的,或者可能有外部动作 
    -585 42732 在当前路径中模式名不止一次出现 
    -586 42907 CURRENT PATH专用寄存器在长度上不能超过254字符 
    -587 428C6 项目引用的列表必须是同一个家族 
    -590 42734 在命名的存储过程或用户自定义的函数中的参数必须是独一无二的 
    -592 42510 没有授权权限,让你在WLM环境中建立的存储过程或者用户自定义函数 
    -601 42710 试图创建(或重命名)已经存在的对象 
    -602 54008 CREATE INDEX语句中指定的列太多 
    -603 23515 因为发现有重复值,所以不能建立唯一的索引 
    -604 42611 在CREATE或ALTER TABLE语句中的为数据类型指定的长度、精度以及标度无效 
    -607 42832 指定的INSERT、UPDATE或DELETE语句不能被发布,应为这些语句对DB2 CATLOG表执行写操作 
    -611 53088 当LOCKSIZE是TABLE或者TABLESPACE时,LOCKMAX必须为0 
    -612 42711 在同一个表、索引或试图中不允许有重复列名 
    -613 54008 主健或UNIQUE约束太长或者包含了太多的列 
    -614 54008 已经超过了索引的内部健长度的最大长度(255)限制 
    -615 55006 不能删除这个程序包,因为该程序包目前正在执行 
    -616 42893 指定的对象不能被删除,因为其他对象依赖于该对象 
    -617 56089 对于DB2版本6,1型索引无效。对于以前的版本,1型索引不能用LOCKSIZE ROW或LARGE表空间定义 
    -618 42832 对DB2 CATALOG表的请求操作时不允许的 
    -619 55011 DSNDB07不能修改,除非他先被停止了 
    -620 53001 对在DSNDB07中的表空间不允许指定该关键词 
    -621 58001 遇到了重复的DBID,遇到了系统问题 
    -622 56031 不能指定FOR MIXED DATA因为没有安装混合数据选项 
    -623 55012 不能为单一的表定义多个族索引 
    -624 42889 不能为单一的表定义多个主健 
    -625 55014 用主健定义的表要求唯一索引 
    -626 55015 不能发布ALTER语句来改变PRIQTY SECQTY或ERASE,除非先停止了表空间 
    -627 55016 不能发布ALTER语句来改变PRIQTY SECQTY或ERASE,除非先把表空间定义为使用存储器组的表空间 
    -628 42613 指定语句时相互排斥的(例如,不能分区一个分段的表空间) 
    -629 42834 因为该外健不能包含空值,所以SET NULL无效 
    -630 56089 不能为1型索引指定WHERE NOT NULL 
    -631 54008 无效的外健;要么是比254个字节长,要么包含的列数多于40 
    -632 42915 指定的删除规则禁止把这个表定义为已制定表的从属表 
    -633 42915 无效删除规则;必须使用特定的强制删除规则 
    -634 42915 在这种情况下,DELETE CASCADE不允许 
    -635 42915 删除规则不能有差异或者不能为SET NULL 
    -636 56016 在分区索引健的升序或降序规范中,分区所以必须与该规范一致 
    -637 42614 遇到重复的关键词 
    -638 42601 在CREATE TABLE语句中缺少列定义 
    -639 56027 带有SET NULL的删除规则的外健的可空列不能是分区索引的列 
    -640 56089 不能为这个表空间指定LOCKSIZE ROW,因为在该表空间中的表上定义了1型索引 
    -642 54021 唯一约束包含太多的列 
    -643 54024 检查约束超出了3800个字符的最大长度 
    -644 42615 在SQL语句中为关键词指定的值无效 
    -646 55017 在指定的分区表空间或者缺省表空间中不能创建表,因为指定的表空间已经包含了一个表 
    -647 57003 指定的缓冲池无效,因为他没有被激活 
    -650 56090 ALTER INDEX不能被执行;提供了原因代码 
    -651 54025 如果CREARE或ALTER TABLE被允许,表对象的描述词(object descriptor,OBD)将超过最大值(32KB) 
    -652 23506 遇到了EDITRPROC或VALIDPROC冲突 
    -653 57004 在分区表空间中的表不可用,因为分区索引尚未被创建 
    -655 56036 在卷的列表中,STOGROUP不能指定为特定的或不特定(“*”)的卷 
    -658 42917 当试图删除指定的对象时,无法删除该对象,该对象的删除必须通过删除与之相关联的对象完成 
    -660 53035 不正确的分区索引规范,必须为族索引定义有限制的关键字 
    -661 53036 分区索引没有指定恰当的分区数目 
    -662 53037 试图在未分区的表空间(分段的或简单的)上建立分区索引 
    -663 53038 为分区索引指定的关键字限制值是一个无效数字 
    -665 53039 为ALTER TABLESOACE语句指定了无效的PART语句 
    -666 57005 SQL语句不能被处理,因为指定的函数当前正处于进行过程中 
    -667 42917 不能明确的删除分区表空间的族索引,必须除去分区表空间来去掉分区索引 
    -668 56018 不能向用EDITPROC定义的表中添加列 
    -669 42917 不能显式的删除分区表空间中的表,必须删除分区表空间来删除表 
    -670 54010 表的记录长度超过了页面的大小 
    -671 53040 不能更改指定的表空间的缓冲池,因为这将改变表空间的页面大小 
    -672 55035 在命名的表上不允许DROP 
    -676 53041 只有4KB的缓冲池可被用于一个索引 
    -677 57011 缓冲池扩展失败,由于可用的虚拟内存的大小不足 
    -678 53045 为才分区索引中指定的限制健提供的值与数据类型不符 
    -679 57006 不能创建某一个特定对象,因为该对象的一个drop目前正在挂起 
    -680 54011 对DB2表不能超过750列 
    -681 23507 列违反了指定的FIELDPROC 
    -682 57010 不能载入FIELDPROC 
    -683 42842 列、单值类型、函数或者过程无效,因为不兼容语句。例如,指定的INTEGER具有FORBITDATA选项 
    -684 54012 指定的文字列表不能超过254个字节 
    -685 58002 FIELDPROC返回一个无效的域描述 
    -686 53043 用FIELDPROC定义的一个列不能与一个使用不同的FIELDPROC定义的列作比较 
    -687 53044 列不能与一个非兼容字段类型的列比较 
    -688 58002 返回不正确的数据 
    -689 54011 从属表定义了太多的列 
    -690 23508 数据定义的控制支持拒绝这个语句 
    -691 57018 命名的注册表不存在 
    -692 57018 命名的索引不存在,但命名的注册表需要该索引 
    -693 55003 命名的注册表/索引的命名列无效 
    -694 57023 DROP正在命名的注册表上挂起 
    -696 42898 由于相关的名字或者转换表的名字使用不正确,指定的触发器无效 
    -697 42899 FOR EACH语句被指定,因此与OLD合NEW相关的名字是不允许的,或者不能为一个BEFORE触发器指定OLD_TABLE和NEW_TABLE 
    -713 42815 指定的专用寄存器是无效的 
    -715 56064 命名的程序不能被运行,因为他依赖与你所安装的DB2版本的部件,但是你的数据中心没有安装这个部件 
    -716 56065 命名的程序使用这个版本的不正确的发行版本做了预编译 
    -717 56066 BIND失败,因为他依赖与你所安装的DB2版本的部件,但是你的数据中心没有安装这个部件 
    -718 56067 REBIND失败,因为IBMREQD列无效 
    -719 42710 不能BIND ADD一个已经存在的程序包 
    -720 42710 不能BIND REPLACE一个已经存在的程序包版本 
    -721 42710 程序包的一致性记号必须是独一无二的 
    -722 42704 绑定错误,因为指定的程序包不存在 
    -723 09000 一个触发的SQL语句接受到一个错误 
    -724 54038 达到了(16)级联间接的SQL语句的最大项目 
    -725 42721 对专门指定的寄存器提供了一个无效值 
    -726 55030 因为SYSPKSYSTEM条目,不能绑定这个程序包 
    -728 56080 指定的数据类型不能与私有协议发布一起使用 
    -729 429B1 用COMMIT ON RETURN定义的存储过程不能用作嵌套的CALL过程的目标 
    -730 56053 在只读的共享数据库中为表定义的参照完整性无效 
    -731 56054 VSAM数据集必须用SHAREOPTION(1.3)定义 
    -732 56055 被定义为只读型数据库却拥有没有定义空间或者索引空间的DB2子系统 
    -733 56056 只读共享数据库的定义不一致 
    -734 56057 一旦一个数据库被定义为ROSHARE READ,他将不能被更改为其他不同的ROSHARE状态 
    -735 55004 用DBID名称标识的数据库不再是一个只读共享数据库 
    -736 53014 命名的DBID无效 
    -737 53056 在这种状况下,不能建立一个隐含的表空间 
    -739 56088 因为同时指定了ALLOW PARALLEL和MODIELES SQL DATA这两个语句,因此已设定的函数将不能再被更改 
    -740 51034 在这种方式下不能用MODIELES SQL DATA定义指定的函数 
    -741 55030 已经为命名的共享组成员的数据定义了工作文件数据库 
    -742 53004 DSNDB07是隐含的工作文件数据库 
    -746 57053 在特定的触发器、存储过程或函数中的SQL语句违反嵌套SQL限制 
    -747 57054 指定的表是不可用的除非为LOB数据列建立起必须的辅助表 
    -748 54042 在指定的辅助表上已经有一个索引 
    -750 42986 不能对已指定的表重新命名,因为他至少在一个现存的视图或触发器中被引用 
    -751 42987 存储过程或用户自定义的函数试图执行一个不允许执行的SQL语句。DB2的线程被置于MUST_ROLLBACK状态 
    -752 0A001 无效CONNECT语句 
    -763 560A1 无效的表空间名 
    -764 560A2 LOB表空间必须与其相关的基表空间同在一个数据库中 
    -765 560A3 表和数据库不兼容 
    -766 560A4 不能对辅助表进行请求的操作 
    -767 42626 CREATE INDEX失败,因为在辅助表中为索引指定了列,或者因为没有为非辅助表的索引指定列 
    -768 560A50 不能为指定的列或者指定的分区建立辅助表,因为其辅助表已经存在 
    -769 53096 CREATE AUX TABLE的规格与基表不匹配 
    -770 530A6 指定的表必须有一个ROWID列,那么该表才可以包含一个LOB列 
    -771 428C7 无效的ROWID列规范 
    -797 42987 CREATE TRIGGER包含不被支持的语法 
    -798 428C9 不能把一个值插入到用GENERATED ALWAYS定义的ROWID列 
    -802 22012 某一特定操作发生了异常错误。被零除 
     22003 某一特定操作发生了异常错误。但不是被零除 
    -803 23505 不能插入行,因为这将违反唯一索引的约束 
    -804 07002 SQLDA的调用参数列表有误 
    -805 51002 在计划中没有发现DBRM或程序包名 
    -807 23509 对已指定的环境和连接,该程序包不可用 
    -808 08001 CONECT语句与程序中的第一个CONNECT语句不一致 
    -811 21000 当多行作为一内嵌的选择语句的返回结果是,必须使用游标 
    -812 22508 在CURRENT PACKAGESET中的ID集合是空白的,语句不能被执行 
    -815 42920 在一个内置选择语句或者一个基本谓词的子查询中,显式的或隐含的指定了GROUP BY或HAVING语句 
    -817 25000 执行SQL语句将可能导致禁止更新用户数据或DB2编目 
    -818 5103 计划<->载入组件的时间戳不匹配,在执行计划中没有从同一个预编译中建立DBRM,该预编译是作为组件载入的 
    -819 58004 视图不能重建,因为在DB2编目中存储的分析树长度为0 
    -820 58004 在这个DB2版本的DB2编目中遇到了无效值 
    -822 51004 在SQLDA中遇到了无效地址 
    -840 54004 在选择列表或插入列表中返回的项目太多 
    -842 08002 到指定位置的连接已经存在 
    -843 08003 SET CONNECTION或RELEASE语句无法执行,因为连接不存在 
    -870 58026 宿主变量描述符的个数不等于语句中宿主变量的个数 
    -872 51302 这个子系统已指定了有效的CCSID 
    -873 53090 同一SQL语句中,不能同时引用EBCDIC表中的定义的列和ASCII表中定义的列 
    -874 53901 指定对象的编码方案与其表空间的编码方案不匹配 
    -875 42988 指定的操作符不能用于ASCII数据 
    -876 53092 不能为指定的原因创建对象:提供了原因代码 
    -877 53093 数据库或表空间不允许用ASCII,必须使用EBCDIC 
    -878 53094 该PLAN——TABLE不能是ASCII,必须使用EBCDIC 
    -879 53095 指定对象的CREATE或ALTER语句不能将列、单值类型,某个存储过程或用户自定义函数的参数定义为以下类型:MAXED DATA,GRAPHIC,VARGRAPHIC,LONGVARGRAPHIC,因为系统没有为指定的编码方案定义相应的CCSID 
    -900 08003 应用处理没有连接到应用服务器,语句不能被执行 
    -901 58004 遇到时断时续的系统错误,该错误不能抑制后继的SQL语句的执行 
    -902 58005 内部控制块的指针错误,要求重新绑定 
    -904 57011 指定的资源不可用 
    -905 57014 超出了资源上限 
    -906 51005 因为重大错误,SQL语句无法执行 
    -908 23510 当前资源限制设施的规范或者自动重绑定的系统参数不允许BIND,REBIND,AUTOREBIND 
    -909 57007 对象已被删除 
    -910 57007 因为在该对象上挂起DROP,所以不能访问该对象 
    -911 40001 当前工作单元已被回滚 
    -913 57033 因为死锁或超时导致不成功执行 
    -917 42969 绑定程序包已经失败 
    -918 51021 SQL语句不能被执行,因为连接丢失 
    -919 56045 需要一个ROLLBACK 
    -922 42505 连接权限失败。试图从TSO、CICS或IMS访问DB2,同时相应的连接设施处于非活动的状态 
    -923 57015 因为DB2不可用,所以不能建立连接 
    -924 58006 遇到了DB2内部的连接错误:提供了原因代码 
    -925 2D521 SQL的COMMIT语句不能从CICS或IMS/TM发布 
    -926 2D521 SQL的ROLLBACK语句不能从CICS或IMS/TM发布 
    -927 51006 当正在连接的环境没有建立时,语言接口被调用。利用DSN命令激发该程序 
    -929 58002 数据获取退出已经失败(DPROP) 
    -939 51021 由于远程服务器的未请求的回滚,要求一个回滚 
    -947 56038 SQL语句失败,因为更新不能被传播(DPROP) 
    -948 56062 DDF没有启动,分布式操作无效 
    -950 42705 在SQL语句中指定的位置在SYSIBM.LOCATIONS中没有定义 
    -965 51021 存储过程非正常终止(在DB2 6之前的版本) 
    -981 57015 当前不是处于允许SQL的状态时,试图在RRSAF中执行SQL 
    -991 57015 调用连接不能建立一个到DB2的隐含或开放连接 
    -2001 53089 为储存过程指定的宿主变量参数的个数不等于预期的参数个数 
    -20003 560A7 不能为GRECP中的表空间或索引指定GBPCACHE NONE 
    -20004 560A8 对于WORKFILE对象。8KB或16Kb的缓冲池页面大小无效 
    -20005 54035 指定的对象类型超出了内部的ID极限 
    -20006 53097 当没有指定WLM环境时,LOB不能被指定为参数 
    -20070 53098 不能非LOB列建立一个辅助表 
    -20071 53099 必须指定WLM环境名 
    -20072 56052 指定的权限ID不拥有在触发器程序包上执行BIND所需的权限 
    -20073 42927 不能按照指定的要求更改命名的函数,因为在现存的视图定义中引用了该函数 
    -20074 42939 不能建立指定的对象,因为“SYS”是一个保留的前缀 
    -20100 56059 在被触发的SQL语句中有BIND错误,指定了错误的SQLCODE和SQLSTATE 
    -20101 56059 由于指定的原因代码,该函数失败 
    -20102 42849 在CREATE或ALTER FUNCTION语句中不能使用指定的选项 
    -20104 42856 更改一个CCSID失败 
    -20106 42945 不能改变表空间或数据库的CCSID,因为现存的试图引用 
    -30000 58008 DRDA分布协议错误;处理可以继续 
    -30002 57057 使用DRDA的分布式客户把OPEN语句连接到PREPARE,但PREPARE接受到一个SQLCODE为+495的警告 
    -30020 58009 DRDA分布协议错误;对话被解除 
    -30021 58010 DRDA分布协议错误;处理不能继续 
    -30030 58013 违反分布协议:COMMIT不成功,对话被解除(AS) 
    -30040 57012 因为不能得到资源,执行失败,处理可以继续(AS) 
    -30041 57013 因为不能得到资源,执行失败,处理不能成功的继续(AS) 
    -30050 58011 执行不成功,在BIND过程中不能执行语句 
    -30051 58012 特定的BIND过程不是处于活动状态(远程BIND),从而导致失败 
    -30052 42932 程序准备的假设错误 
    -30053 42506 程序包的拥有者遭遇授权失败 
    -30060 08004 RBD遭遇授权失败 
    -30061 08004 指定了无效或者没有存在的RDB 
    -30070 58014 目标子系统不支持这个命令 
    -30071 58015 目标子系统不支持这个对象 
    -30072 58016 目标子系统不支持这个参数 
    -30073 58017 目标子系统不支持这个参数值 
    -30074 58018 应答信息不被支持 
    -30080 08001 SNA通信错误 
    -30081 58019 TCP/IP通信错误 
    -30082 08001 由于安全冲突、通信失败:提供了原因代码 
    -30090 25000 指定的操作对远程执行失败 
    -30104 56095 在绑定选项与绑定值中有错误 
    -30105 56096 指定的绑定选项不兼容
    展开全文
  • DB2_sqlCode 报错代码

    2018-07-09 09:58:21
    DB2_sqlCode,罗列了DB2的报错代码,使用起来方便多了
  • DB2错误码sqlcode对应表.xlsx
  • DB2 sqlCode

    千次阅读 2014-11-23 16:11:06
    When running a program that uses SQL, DB2 gives you an SQLCODE that tells you whether your SQL worked or not. Scroll down to see ALL the SQLCODES there are in Version 10.  SQLCODES for DB2 ...
    
    

    When running a program that uses SQL, DB2 gives you an SQLCODE that tells you whether your SQL worked or not.

    Scroll down to see ALL the SQLCODES there are in Version 10. 

    SQLCODES for DB2 Version 8 from the IBM manual GC18-7422-0 04/06/05 
    Scroll down, or use your browser's FIND to find the desired SQLCODE. The SQLCODES are not all in numerical order.

    Compliments of Gabe Gargiulo, author of several recent books on programming and modern languages, available at Amazon.com. 

    SQLCODE +100 SQLSTATE 02000 Row not found or end of cursor 
    SQLCODE +222 Trying to FETCH a row that fell through a DELETE hole 
    SQLCODE +223 Trying to FETCH a row that fell through an UPDATE hole 
    SQLCODE +231 FETCH but you did a BEFORE or AFTER and you are not on a valid row 
    SQLCODE +304 Value cannot be assigned to this host variable because it is out of range 
    SQLCODE +802 The null indicator was set to -2 because an arithmetic statement didn't work. 
    SQLCODE 000, successful execution 
    SQLCODE -007 statement contains the illegal character character 
    SQLCODE -010 the string constant beginning string is not terminated 
    SQLCODE -011 comment not closed 
    SQLCODE -012, warning: the unqualified column name was interpreted as a correlated reference 
    SQLCODE -029 INTO clause required 
    SQLCODE -051 identifier-name (sql-type) was previously declared or referenced 
    SQLCODE -056 an SQLSTATE or SQLCODE variable declaration is in a nested compound statement 
    SQLCODE -057 the return statement in an sql function must return a value. 
    SQLCODE -058 value specified on return statement must be an integer 
    SQLCODE -060 invalid specification-type specification: specification-value 
    SQLCODE -078 parameter names must be specified for routine routine-name 
    SQLCODE -079 qualifier for object name was specified as qualifier1 but qualifier2 is required 
    SQLCODE -084 unacceptable SQL statement 
    SQLCODE -087 a null value was specified in a context where a null is not allowed 
    SQLCODE -096 variable variable-name does not exist or is not supported by the server and a default value was not provided 
    SQLCODE -097 the use of LONG VARCHAR or LONG VARGRAPHIC is not allowed in this context 
    SQLCODE -098, warning: a dynamic SQL statement ends with a semicolon 
    SQLCODE -100, not found:row not found for FETCH, UPDATE or DELETE, or the result of a query is an empty table 
    SQLCODE -101 the statement is too long or too complex 
    SQLCODE -102 String constant is too long copy right 2013 TheAmericanProgrammer.com Unauthorized copying prohibited 
    SQLCODE -103 constant is an invalid numeric constant 
    SQLCODE -104 illegal symbol "token". Some symbols that might be legal are:token-list 
    SQLCODE -105 invalid string 
    SQLCODE -107 the name name is too long. Maximum allowable size is size 
    SQLCODE -108 the name name is qualified incorrectly 
    SQLCODE -109 clause-type clause is not permitted 
    SQLCODE -110 invalid hexadecimal constant beginning constant -or- 
    SQLCODE -110, warning: SQL UPDATE to a data capture table not signaled to originating subsystem 
    SQLCODE -111, error: a column function does not include a column name copyright 2014 TheAmericanProgrammer.com Unauthorized copying prohibited -or- 
    SQLCODE -111, warning: the subpages option is not supported for type 2 indexes
    SQLCODE -112 the operand of an aggregate function includes an aggregate function, an OLAP specification, or a scalar fullselect -or- 
    SQLCODE -112, error: the operand of a column function is another column function 
    SQLCODE -113 invalid character found in: string, reason code nnn 
    SQLCODE -114 the location name location does not match the current server 
    SQLCODE -115 a predicate is invalid because the comparison operator operatoris followed by a parenthesized list or by ANY or ALL without a subquery 
    SQLCODE -117 The number of values you are trying to INSERT does not match the number of columns 
    SQLCODE -118 the object table or view of the DELETE or UPDATE statement is also identified in a FROM clause 
    SQLCODE -119 a column or expression in a HAVING clause is not valid 
    SQLCODE -120 an aggregate function or OLAP specification is not valid in the context in which it was invoked -or- 
    SQLCODE -120, error: a WHERE clause, SET clause, VALUES clause, or a SET assignment statement includes a column function 
    SQLCODE -121 the column name is identified more than once in the INSERT or UPDATE operation or set transition variable statement 
    SQLCODE -122 column or expression in the SELECT list is not valid 
    SQLCODE -123 the parameter in position n in the function name must be a constant or keyword 
    SQLCODE -125 an integer in the order by clause does not identify a column of the result 
    SQLCODE -126 the SELECT statement contains both an UPDATE clause and an ORDER BY clause 
    SQLCODE -127 DISTINCT is specified more than once in a subselect 
    SQLCODE -128 invalid use of null in a predicate 
    SQLCODE -128, error: invalid use of null in a predicate 
    SQLCODE -129 the statement contains too many table names 
    SQLCODE -130 the escape clause consists of more than one character, or the string pattern contains an invalid occurrence of the escape character 
    SQLCODE -131 statement with LIKE predicate has incompatible data types 
    SQLCODE -132 an operand of value is not valid 
    SQLCODE -133 an aggregate function in a subquery of a having clause is invalid because all column references in its argument are not correlated to the group by result that the having clause is applied to 
    SQLCODE -134 improper use of a string, LOB, or XML value 
    SQLCODE -136 sort cannot be executed because the sort key length too long 
    SQLCODE -137 the length resulting from operation is greater than maximum-length 
    SQLCODE -138 the second or third argument of the substr or substring function is out of range 
    SQLCODE -1403 the username and/or password supplied is incorrect 
    SQLCODE -142 the SQL statement is not supported 
    SQLCODE -144 invalid section number number Copy right 20 12 The American Programmer.com Unauthorized copying prohibited 
    SQLCODE -147 ALTER function function-name failed because source functions or spatial functions cannot be altered 
    SQLCODE -148 the source table or tablespace source-name cannot be altered or renamed, reason reason-code 
    SQLCODE -150 the object of the INSERT, DELETE, UPDATE, merge, or truncate statement is a view, system-maintained materialized query table, or transition table for which the requested operation is not permitted 
    SQLCODE -151 the UPDATE operation is invalid because the catalog description of column column-name indicates that it cannot be updated 
    SQLCODE -152 the DROP clause clause in the ALTER statement is invalid becauseconstraint-name is a constraint-type 
    SQLCODE -153 the statement is invalid because the view or table definition does not include a unique name for each column 
    SQLCODE -154 the statement failed because view or table definition is not valid 
    SQLCODE -156 the statement does not identify a table 
    SQLCODE -157 only a table name can be specified in a foreign key clause.Object-name is not the name of a table. 
    SQLCODE -158 the number of columns specified for name is not the same as the number of columns in the result table. 
    SQLCODE -159 the statement references object-name which identifies an actual-type rather than an expected-type 
    SQLCODE -160 the WITH CHECK OPTION clause is not valid for the specified view 
    SQLCODE -16000 an xquery expression cannot be processed because the context-component component of the static context has not been assigned. error qname = err:xpst0001 
    SQLCODE -16001 an xquery expression starting with token token cannot be processed because the focus component of the dynamic context has not been assigned. error qname = err:xpdy0002 
    SQLCODE -16002 an xquery expression has an unexpected token token following text. expected tokens may include: token-list. error qname= err:xpst0003 
    SQLCODE -16003 an expression of data type value-type cannot be used when the data type expected-type is expected in the context. error qname= err:xpty0004 
    SQLCODE -16005 an xquery expression references an element name, attribute name, type name, function name, namespace prefix, or variable name undefined-name that is not defined within the static context. error qname= err:xpst0008 
    SQLCODE -16007 the xquery path expression references an axis axis-type that is not supported. error qname = err:xqst0010 
    SQLCODE -16009 an xquery function named function-name with number-of-parms parameters is not defined in the static context. error qname= err:xpst0017 
    SQLCODE -16011 the result of an intermediate step expression in an xquery path expression contains an atomic value. error qname = err:xpty0019 
    SQLCODE -16012 the context item in an axis step must be a node. error qname = err:xpty0020 
    SQLCODE -16015 an element constructor contains an attribute node namedattribute-name that follows an xquery node that is not an attribute node. error qname = err:error-name 
    SQLCODE -16016 the attribute name attribute-name cannot be used more than once in an element constructor. error qname = err:xqty0025 
    SQLCODE -16020 the context node in a path expression that begins with an initial "/" or "//" does not have an xquery document node root. error qname = err:xpdy0050 
    SQLCODE -16022 operands of types xquery-data-types are not valid for operator operator-name . error qname = err:xpty0004 
    SQLCODE -16023 the xquery prolog cannot contain multiple declarations for the same namespace prefix ns-prefix. error qname = err:xqst0033 
    SQLCODE -16024 the namespace prefix prefix-name cannot be redeclared or cannot be bound to the specified uri. error qname = err:xqst0070 
    SQLCODE -16026 the name attribute-name is used for more than one attribute in the constructor for the element named element-name. error qname=err:xqst0040 
    SQLCODE -16029 two or more namespaces within the same xquery element constructor use the same namespace prefix prefix-name. error qname=err:xqst0071 
    SQLCODE -16031 xquery language feature using syntax string is not supported 
    SQLCODE -16032 the string string is not a valid uri. error qname = err:xqst0046 
    SQLCODE -16033 the target data type type-name of a castable expression is not an atomic data type defined for the in-scope XML schema types or is a data type that cannot be used in a castable expression. error qname=err:xpst0080 
    SQLCODE -16036 the uri that is specified in a namespace declaration cannot be a zero-length string 
    SQLCODE -16038 the arguments of fn:datetime have different timezones. error qname=err:forg0008. 
    SQLCODE -16041 an implicit or explicit invocation of the fn:boolean function in the xquery expression could not compute the effective boolean value of the sequence. error qname=err:forg0006 
    SQLCODE -16046 a numeric xquery expression attempted to divide by zero. error qname = err:foar0001 
    SQLCODE -16047 an xquery expression resulted in arithmetic overflow or underflow. error qname= err:foar0002 
    SQLCODE -16048 an xquery prolog cannot contain more than one declaration-type declaration. error qname = error-qname 
    SQLCODE -16049 the lexical value value is not valid for the type-name data type in the function or cast. error qname= err:foca0002 
    SQLCODE -16051 the value value of data type source-type is out of range for an implicit or explicit cast to target data type target-type. error qname = err:error-qname 
    SQLCODE -16052 nan cannot be used as a float or double value in a datetime operation. error qname=err:foca0005. 
    SQLCODE -16055 an arithmetic operation involving a datetime value resulted in overflow. error qname=err:fodt0001. 
    SQLCODE -16056 an arithmetic operation involving a duration value resulted in overflow. error qname=err:fodt0002. 
    SQLCODE -16057 a timezone value is not valid. error qname=err:fodt0003. [IEQ7f82Y] 
    SQLCODE -16061 the value value cannot be constructed as, or cast (using an implicit or explicit cast) to the data type data-type. error qname = err:forg0001 
    SQLCODE -16065 an empty sequence cannot be cast to the data type data-type, error qname = err:forg0006 
    SQLCODE -16066 the argument passed to the aggregate function function-name is not valid. error qname = err:forg0006 
    SQLCODE -16067 the flags argument value passed to the function function-nameis not valid. error qname= err:forx0001 
    SQLCODE -16068 the regular expression argument value passed to the functionfunction-name is not valid. error qname= err:forx0002 
    SQLCODE -16069 a regular expression argument value passed to the functionfunction-name matches a zero-length string. error qname= err:forx0003 
    SQLCODE -16075 the sequence to be serialized contains an item that is an attribute node. error qname = err:senr0001 
    SQLCODE -16080 an xquery expression includes one or more expression-type expressions outside the xquery-UPDATE-constant of an xmlmodify function. error qname=err:xust0001. 
    SQLCODE -16081 the xquery-UPDATE-constant in the xmlmodify function is not an updating expression or an empty sequence expression. error qname=err:xust0002.
    SQLCODE -16085 the target node of an xquery expression-type expression is not valid. error qname=err:error-name. 
    SQLCODE -16086 the replacement sequence of a replace expression contains invalid nodes for the specified target node. error qname=err:error-name. 
    SQLCODE -16087 the result of applying the updating expressions in the xmlmodify function is not a valid instance of the xquery and xpath data model. additional information: information-1, information-2. error qname=err:xudy0021. 
    SQLCODE -16088 an expression-type expression has a binding of a namespace prefix prefix-string to namespace uri uri-string, introduced to an element named element-name, that conflicts with an existing namespace binding of the same prefix to a different uri in the in-scope namespaces of that element node. error qname=err:xudy0023. 
    SQLCODE -16089 an expression-type expression and possibly other updating expressions in an xmlmodify function introduce conflicting namespace bindings into an element named element-name. the prefix prefix-string is bound to uri-string while another binding of the same prefix uses a different namespace uri. error qname=err:xudy0024. 
    SQLCODE -161 the INSERT or UPDATE is not allowed because a resulting row does not satisfy the view definition 
    SQLCODE -162, warning: table space . has been placed in check pending 
    SQLCODE -16246 incomplete annotation mapping at or near line lineno in XML schema document uri. reason code = reason-code. 
    SQLCODE -16247 source XML type source-data-type cannot be mapped to target SQL type target-data-type in the annotation at or near line lineno in XML schema document uri 
    SQLCODE -16248 unknown annotation annotation-name at or near line lineno in XML schema document uri 
    SQLCODE -16249 the DB2-xdb:expression annotation expression at or near linelineno in XML schema document uri is too long. 
    SQLCODE -16250 the DB2-xdb:defaultsqlschema with value schema-name at or near line lineno in XML schema document uri conflicts with another DB2-xdb:defaultsqlschema specified in one of the XML schema documents within the same XML schema. 
    SQLCODE -16251 duplicate annotation defined for object-name at or near location in XML schema document uri 
    SQLCODE -16252 the DB2-xdb:rowset name rowset-name specified at or near linelineno in the XML schema document uri is already associated with another table
    SQLCODE -16253 the DB2-xdb:condition annotation condition at or near linelineno in XML schema document uri is too long. 
    SQLCODE -16254 a DB2-xdb:locationpath locationpath at or near line lineno in XML schema document uri is not valid with reason code reason-code. 
    SQLCODE -16255 a DB2-xdb:rowset value rowset-name used at or near line linenoin XML schema document uri conflicts with a DB2-xdb:table annotation with the same name. 
    SQLCODE -16257 XML schema feature feature specified is not supported for decomposition. 
    SQLCODE -16258 the XML schema contains a recursive element which is an unsupported feature for decomposition. the recursive element is identified as elementnamespace : elementname of type typenamespace : typename. 
    SQLCODE -16259 invalid many-to-many mappings detected in XML schema document uri1 near line lineno1 and in XML schema document uri2 near line lineno2. 
    SQLCODE -16260 XML schema annotations include no mappings to any column of any table. 
    SQLCODE -16262 the annotated XML schema has no columns mapped for rowsetrowsetname
    SQLCODE -16265 the XML document cannot be decomposed using XML schema xsrobject-name which is not enabled or is inoperative for decomposition. 
    SQLCODE -16266 an SQL error occurred during decomposition of document docid while attempting to INSERT data. information returned for the error includes SQLCODE SQLCODE, SQLSTATEsqlstate, and message tokens token-list. 
    SQLCODE -164 authorization-id does not have the privilege to create a view with qualification qualifier-name 
    SQLCODE -170 the number of arguments specified for function-name is invalid 
    SQLCODE -171 the data type, length, or value of argument argument-position of function-name is invalid 
    SQLCODE -173 UR is specified on the WITH clause but the cursor is not read-only 
    SQLCODE -1760 create procedure for procedure-name must have valid language and external clauses 
    SQLCODE -180 SQLSTATE 22007 Bad data in Date/Time/Timestamp String representation of DATE, TIME, TIMESTAMP is invalid 
    SQLCODE -181, error: the string representation of a datetime value is not a valid datetime value -or- 
    SQLCODE -181 SQLSTATE 22007 Bad data in Date/Time/Timestamp Value for DATE, TIME, TIMESTAMP is invalid 
    SQLCODE -182 an arithmetic expression with a datetime value is invalid 
    SQLCODE -183 an arithmetic operation on a date or timestamp has a result that is not within the valid range of dates 
    SQLCODE -184 an arithmetic expression with a datetime value contains a parameter marker 
    SQLCODE -185 the local format option has been used with a date or time and no local exit has been installed 
    SQLCODE -186 the local date length or local time length has been increased and executing program relies on the old length 
    SQLCODE -187 a reference to a current datetime special register is invalid because the mvs tod clock is bad or the mvs parmtz is out of range 
    SQLCODE -188 the string representation of a name is invalid 
    SQLCODE -189 ccsid ccsid is invalid 
    SQLCODE -190 the attributes specified for the column table-name.column-name are not compatible with the existing column definition 
    SQLCODE -191 a string cannot be used because it is invalid mixed data 
    SQLCODE -197 a qualified column name is not allowed in the order by clause when a set operator is also specified 
    SQLCODE -198 the operand of the prepare or execute immediate statement is blank or empty 
    SQLCODE -199 Illegal use of the specified keyword. 
    SQLCODE -20003 gbpcache none cannot be specified for tablespace or index in grecp 
    SQLCODE -20004 8k or 16k bufferpool pagesize invalid for a workfile object 
    SQLCODE -20005 the internal id limit of limit has been exceeded for object type object-type 
    SQLCODE -20008 attempt to use an unsupported feature on object object-name. reason code: reason-code copyright 2014 TheAmericanProgrammer.com Unauthorized copying prohibited 
    SQLCODE -2001 the number of host variable parameters for a stored procedure is not equal to the number of expected host variable parameters. actual number sqldanum, expected number opnum 
    SQLCODE -20016 the value of the inline length associated with object-name is too big or the inline length clause is not allowed in the context. 
    SQLCODE -20019 the result type returned from the function body cannot be assigned to the data type defined in the returns clause 
    SQLCODE -20046 the selectivity clause following predicate-string can only specified for a spatial predicate function. 
    SQLCODE -20058 the fullselect specified for materialized query table table-name is not valid. 
    SQLCODE -20060 unsupported data type data-type encountered in SQL object-type object-name 
    SQLCODE -20070 auxiliary table table-name cannot be created because column column-name is not a LOB column 
    SQLCODE -20071 wlm environment name must be specified function-name 
    SQLCODE -20072 bind-type bind-subtype error using authorization-id authority operation is not allowed on a package-type package package-name 
    SQLCODE -20073 the function function-name cannot be altered because it is referenced in existing view or materialized query table definitions 
    SQLCODE -20074 the object object-name cannot be created because the first three characters are reserved for system objects 
    SQLCODE -20091 a view name was specified after like in addition to the including identity column attributes clause 
    SQLCODE -20092 a table or view was specified in the like clause, but the object cannot be used in this context 
    SQLCODE -20093 the table table-name cannot be converted to or from a materialized query table, or the materialized query table property cannot be altered. reason code = reason-code. 
    SQLCODE -20094 the column column-name is a generated column and cannot be used in the before trigger trigger-name. 
    SQLCODE -20100 an error occurred when binding a triggered SQL statement. information returned: section number : section-number SQLCODE sqlerror, SQLSTATEsqlstate, and message tokens token-list 
    SQLCODE -20101 the function function-name failed with reason reason-code 
    SQLCODE -20102 create or alter statement for routine routine-name specified the option option which is not allowed for the type of routine 
    SQLCODE -20104 an attempt to alter a ccsid from from-ccsid to to-ccsid failed 
    SQLCODE -20106 the ccsid for the table space or database cannot be changed because the table space or database already contains a table that is referenced in existing view, or materialized query table definitions or an extended index 
    SQLCODE -20107 host variable or parameter number position-number cannot be used as specified because reason reason 
    SQLCODE -20108 a result set contains an unsupported data type in position number position-number for cursor cursor-name opened by stored procedure procedure-name 
    SQLCODE -20110 cannot implicitly connect to a remote site with a savepoint outstanding 
    SQLCODE -20111 cannot issue savepoint, release savepoint, rollback to savepoint from a trigger, from a user-defined function, or from a global transaction 
    SQLCODE -20117 a window specification for an OLAP specification is not valid. reason code = reason-code. 
    SQLCODE -20120 an SQL table function must return a table result. 
    SQLCODE -20123 call to stored procedure procedure-name failed because the result set returned for cursor cursor-name is scrollable, but the cursor is not positioned before the first row 
    SQLCODE -20124 open cursor cursor failed because the cursor is scrollable but the client does not support this 
    SQLCODE -20125 call to stored procedure procedure-name failed because the result set for cursor cursor-name is scrollable, but the client does not support this, reason reason-code. 
    SQLCODE -20127 value specified on FETCH statement for absolute or relative is too large for drda 
    SQLCODE -20129 local special register is not valid as used 
    SQLCODE -20142 sequence sequence-name cannot be used as specified 
    SQLCODE -20143 the encryption or decryption function failed, because the encryption password value is not set 
    SQLCODE -20144 the encryption is invalid because the length of the password was less than 6 bytes or greater than 127 bytes 
    SQLCODE -20146 the decryption failed. the data is not encrypted 
    SQLCODE -20147 the encryption function failed. multiple pass encryption is not supported 
    SQLCODE -20148 a return statement does not exist or was not invoked during the execution of routine routine-name with specific name specific-name. 
    SQLCODE -20163 hexadecimal constant gx is not allowed 
    SQLCODE -20165 an SQL data change statement within a from clause is not allowed in the context in which it was specified 
    SQLCODE -20166 an SQL data change statement within a SELECT specified a view view-name which is not a symmetric view or could not have been defined as a symmetric view 
    SQLCODE -20177 set data type clause on alter table specified floating point, but this change is disallowed 
    SQLCODE -20178 view view-name already has an instead of operation trigger defined 
    SQLCODE -20179 the instead of trigger cannot be created because the view view-name is defined using the with check option 
    SQLCODE -20180 column column-name in table table-name cannot be altered as specified 
    SQLCODE -20181 column cannot be added to index index-name 
    SQLCODE -20182 partitioning clause clause on stmt-type statement for index-name is not valid 
    SQLCODE -20183 the partitioned, add partition, add partitioning key, alter partition, rotate partition, or partition by range clause specified on create or alter for table-name is not valid 
    SQLCODE -20185 cursor cursor-name is not defined to access rowsets, but a clause was specified that is valid only with rowset access 
    SQLCODE -20186 a clause specified for the dynamic SQL statement being processed is not valid 
    SQLCODE -20200 the install or replace of jar-id with url url failed due to reason reason-code-(reason-string). 
    SQLCODE -20201 the install, replace, remove, or alter of jar-name failed due to reason reason-code-(reason-string) 
    SQLCODE -20202 the remove of jar-name failed as class is in use 
    SQLCODE -20203 user-defined function or procedure name has a java method with an invalid signature. the error is at or near parameter number. the signature is signature. 
    SQLCODE -20204 the user-defined function or procedure routine-name was unable to map to a single java method 
    SQLCODE -20207 the install or remove of jar-name specified the use of a deployment descriptor. 
    SQLCODE -20210 the SQL statement cannot be executed because it was precompiled at a level that is incompatible with the current value of the encoding bind option or special register 
    SQLCODE -20211 the specification order by or FETCH first n rows only is invalid 
    SQLCODE -20212 user-defined routine name encountered an exception attempting to load java class class-name from jar jar-name. original exception: exception-string 
    SQLCODE -20213 stored procedure procedure-name has returned a dynamic result set, parameter number, that is not valid 
    SQLCODE -20223 the encrypt_tdes or decrypt function failed. encryption facility not available return-code, reason-code 
    SQLCODE -20224 encrypted data that was originally a binary string cannot be decrypted to a character string 
    SQLCODE -20227 required clause is missing for argument number of expression 
    SQLCODE -20228 a stacked diagnostics area is not available 
    SQLCODE -20232 character conversion from ccsid from-ccsid to to-ccsid failed with error code error-code for table dbid.obid column column-number requested by csect-name 
    SQLCODE -20235 the column column-name cannot be added or altered because table-name is a materialized query table 
    SQLCODE -20240 invalid specification of a security label column table-name.column-name reason code reason-code 
    SQLCODE -20248 attempted to explain all cached statements or a cached statement with stmtid or stmttoken id-token but the required explain information is not accessible. reason reason-code 
    SQLCODE -20249 the package package-name needs to be rebound in order to be successfully executed (required-maintenance) 
    SQLCODE -20252 diagnostics area full. no more errors can be recorded for the not atomic statement 
    SQLCODE -20257 final table is not valid when the target view view-name of the SQL data change statement in a fullselect has an instead of trigger defined 
    SQLCODE -20258 invalid use of input sequence ordering 
    SQLCODE -20260 the assignment clause of the UPDATE operation and the values clause of the INSERT operation must specify at least one column that is not an include column 
    SQLCODE -20264 for table table-name, primary-auth-id with security label primary-auth-id-seclabel is not authorized to perform operation on a row with security label row-seclabel. the record identifier (rid) of this row is rid-number. 
    SQLCODE -20265 security label is reason for primary-auth-id 
    SQLCODE -20266 alter view for view-name failed 
    SQLCODE -20275 the XML name XML-name is not valid. reason code = reason-code 
    SQLCODE -20281 primary-auth-id does not have the mls write-down privilege 
    SQLCODE -20283 a dynamic create statement cannot be processed when the value of current schema differs from current sqlid 
    SQLCODE -20286 DB2 converted string token-type tokenfrom from-ccsid to to-ccsid, and resulted in substitution characters 
    SQLCODE -20289 invalid string unit unit specified for function function-name 
    SQLCODE -20295 the execution of a built in function function resulted in an error reason code reason-code 
    SQLCODE -203 a reference to column column-name is ambiguous 
    SQLCODE -203, error: a reference to column is ambiguous 
    SQLCODE -20300 the list of columns specified for the clause clause is not allowed in combination with the list of columns for the partitioning key for the table. 
    SQLCODE -20304 invalid index definition involving an xmlpattern clause or a column of data type XML. reason code = reason-code 
    SQLCODE -20305 an XML value cannot be inserted or updated because of an error detected when inserting or updating the index identified by index-id on table table-name. reason code = reason-code 
    SQLCODE -20306 an index on an XML column cannot be created because of an error detected when inserting the XML values into the index. reason code = reason-code 
    SQLCODE -20310 the remove of jar-name1 failed, as it is in use by jar-name2 
    SQLCODE -20311 the value provided for the new java path is illegal 
    SQLCODE -20312 the alter of jar jar-id failed because the specified path references itself 
    SQLCODE -20313 debug mode option for routine routine-name cannot be changed 
    SQLCODE -20314 the parameter list (or an option) does not match the parameter list (or option) for all other versions of routine routine-name 
    SQLCODE -20315 the currently active version for routine routine-name (routine-type) cannot be dropped 
    SQLCODE -20327 the depth of an XML document exceeds the limit of 128 levels 
    SQLCODE -20328 the document with target namespace namespace and schema location location has already been added for the XML schema identified by schema name 
    SQLCODE -20329 the completion check for the XML schema failed because one or more XML schema documents is missing. one missing XML schema document is identified by uri-type as uri 
    SQLCODE -20330 the object-type identified by XML uri-type1 uri1 and XML uri-type2 uri2 is not found in the XML schema repository 
    SQLCODE -20331 the XML comment value string is not valid 
    SQLCODE -20332 the XML processing instruction value string is not valid 
    SQLCODE -20335 more than one xsrobject-type exists identified by XML uri-type1 uri1 and uri-type2 uri2 exists in the XML schema repository. 
    SQLCODE -20338 the data type of either the source or target operand of an xmlcast specification must be XML 
    SQLCODE -20339 XML schema name is not in the correct state to perform operation operation 
    SQLCODE -20340 XML schema xmlschema-name includes at least one XML schema document in namespace namespace that is not connected to the other XML schema documents 
    SQLCODE -20345 the XML value is not a well-formed document with a single root element 
    SQLCODE -20353 an operation involving comparison cannot use operand name defined as data type type-name 
    SQLCODE -20354 invalid specification of a row change timestamp column for table table-name 
    SQLCODE -20355 the statement could not be processed because one or more implicitly created objects are involved reason-code 
    SQLCODE -20356 the table with dbid = dbid and obid = obid cannot be truncated because DELETE triggers exist for the table, or the table is the parent table in a referential constraint 
    SQLCODE -20361 authorization id authorization-name is not defined for the trusted context context-name 
    SQLCODE -20362 attribute attribute-name with value value cannot be dropped because it is not part of the definition of trusted context context-name 
    SQLCODE -20363 attribute attribute-name with value value is not a unique specification for trusted context context-name 
    SQLCODE -20365 a signaling nan was encountered, or an exception occurred in an arithmetic operation or function involving a decfloat 
    SQLCODE -20366 table with dbid=database-id and obid=object-id cannot be truncated because uncommitted updates exist on the table with 'immediate' option specified in the statement 
    SQLCODE -20369 an alter trusted context statement for context-name attempted to remove the last connection trust attribute associated with the trusted context 
    SQLCODE -20372 the system authid clause of a create or alter trusted context statement for context-name specified authorization-name, but another trusted context is already defined for that authorization id. 
    SQLCODE -20373 a create or alter trusted context statement specified authorization-name more than once or the trusted context is already defined to be used by this authorization id, profile name, or public. 
    SQLCODE -20374 an alter trusted context statement for context-name specified authorization-name but the trusted context is not currently defined to be used by this authorization id, profile name, or public 
    SQLCODE -20377 an illegal XML character hex-char was found in an SQL/XML expression or function argument that begins with string start-string 
    SQLCODE -20380 alter index with regenerate option for index-name failed. information returned: SQLCODE SQLCODE, SQLSTATE sqlstate, message tokens token-list 
    SQLCODE -20381 alter index with regenerate option is not valid for index-name 
    SQLCODE -20382 context item cannot be a sequence with more than one item 
    SQLCODE -20385 the statement cannot be processed because there are pending definition changes for object object-name of type object- type (reason reason-code) 
    SQLCODE -20398 error encountered during XML parsing at location n text 
    SQLCODE -20399 error encountered during XML validation: location n; text: text; xsrid schema-id 
    SQLCODE -204 Object not defined to DB2 
    SQLCODE -204, warning: is an undefined name 
    SQLCODE -20400 XML schema error n text 
    SQLCODE -20409 an XML document or constructed XML value contains a combination of XML nodes that causes an internal identifier limit to be exceeded 
    SQLCODE -20410 the number of children nodes of an XML node in an XML value has exceeded the limit number of children nodes 
    SQLCODE -20411 a FETCH current continue operation was requested for cursor-name but there is no preserved, truncated data to return 
    SQLCODE -20412 serialization of an XML value resulted in characters that could not be represented in the target encoding 
    SQLCODE -20422 a create table, or declare global temporary table statement for table-name attempted to create a table with all the columns defined as hidden 
    SQLCODE -20423 error occurred during text search processing (server, index-name, text) 
    SQLCODE -20424 text search support is not available reason-code 
    SQLCODE -20425 column-name (in table-name) was specified as an argument to a text search function, but a text index does not exist for the column 
    SQLCODE -20426 conflicting text search administration stored procedure running on the same index 
    SQLCODE -20427 error occurred during text search administration stored procedure error 
    SQLCODE -20428 uri specified in the xmlschema clause is an empty string. 
    SQLCODE -20433 an untyped parameter marker was specified, but an assumed data type cannot be determined from its use 
    SQLCODE -20434 an UPDATE operation has set all of its target columns to unassigned 
    SQLCODE -20444 an error occurred in a key-expression evaluation in index-name information returned: SQLCODE: SQLCODE, sqlstate: sqlstate, message token token-list and rid x rid 
    SQLCODE -20447 format string format-string is not valid for the function-name function 
    SQLCODE -20448 string-expression cannot be interpreted using format string format-string for the timestamp_format function. 
    SQLCODE -20457 the procedure procedure-name has encountered an unsupported version, version, for parameter number 
    SQLCODE -20465 the binary XML value is incomplete or contains unrecognized data at location position with the hex data text 
    SQLCODE -20469 row or column access control cannot be activated for table table-name for reason reason-code. object-type object-name is not in a valid state for activating access control for this table 
    SQLCODE -20470 object-type1 object-name1 must be defined as secure because object-type2 object-name2 is dependent on it. 
    SQLCODE -20471 the INSERT or UPDATE is not allowed because a resulting row does not satisfy row permissions. 
    SQLCODE -20472 permission or mask object-name cannot be altered as specified. reason code reason-code. 
    SQLCODE -20473 the input argument of function function-name that is defined with the not-secured option must not reference column column-name for which a column mask is enabled and the column access control is activated for the table 
    SQLCODE -20474 permission or mask cannot be created for the object-name object of the object-type type. reason code reason-code. 
    SQLCODE -20475 a column mask is already defined for the column column-name in table table-name (existing mask name mask-name) 
    SQLCODE -20476 the function-name function was invoked with an invalid format string format-string. 
    SQLCODE -20477 the function-name function is not able to use format string format-string to interpret the argument string-expression. 
    SQLCODE -20478 the statement cannot be processed because column mask mask-name (defined for column column-name) exists and the column mask cannot be applied or the definition of the mask conflicts with the requested statement. reason code reason-code. 
    SQLCODE -20479 the source table table-name cannot be altered as specified because the table is involved in row or column access controls. reason code reason-code reason-code. 
    SQLCODE -20487 hash organization clause is not valid for table-name 
    SQLCODE -20488 specified hash space is too large for the implicitly created table space. reason reason-code. (partition partition-number) 
    SQLCODE -20490 a versioning clause was specified for table table-name, but the table cannot be used as a system period temporal table. reason code = reason-code. 
    SQLCODE -20491 invalid specification of period period-name. reason code = reason-code. 
    SQLCODE -20493 a timestamp without time zone value cannot be assigned to a timestamp with time zone target 
    SQLCODE -20497 a string representation of a datetime value that contains a time zone cannot be implicitly or explicitly cast to a target defined as datetime without time zone 
    SQLCODE -205 Column name not in specified table 
    SQLCODE -20517 xmlmodify attempted to UPDATE a column which was not specified in the UPDATE set clause 
    SQLCODE -20522 invalid specification of without overlaps clause. reason code reason-code. 
    SQLCODE -20523 table table-name was specified as a history table, but the table definition is not valid for a history table. reason code = reason-code. 
    SQLCODE -20524 invalid period specification or period clause for period period-name. reason code = reason-code. 
    SQLCODE -20525 the requested action is not valid for table table-name because the table is the wrong type of table. reason code = reason-code 
    SQLCODE -20527 period-name is not a period in table table-name 
    SQLCODE -20528 the target of the data change operation is a table table-name, which includes a period period-name. a row that this data change operation attempted to modify was also modified by another transaction. 
    SQLCODE -20531 the version number actual-version specified in a binary XML value is not supported. the highest supported version is supported-version. 
    SQLCODE -206 Column does not exist in any table in the SELECT -or- 
    SQLCODE -206, warning: is not a column of an inserted table, updated table, or any table identified in a from clause 
    SQLCODE -208 the order by clause is invalid because column name is not part of the result table 
    SQLCODE -208, error: the order by clause is invalid because column is not part of the result table 
    SQLCODE -212 name is specified more than once in the referencing clause of a trigger definition 
    SQLCODE -214 an expression in the following position, or starting with position-or-expression-start in the clause-type clause is not valid. Reason code = reason-code 
    SQLCODE -216 You need to use the same number of expressions on both sides of the comparison. when using multiple operands in a comparison, Correct example: WHERE (E.SALARY, E.COMM) IN (SELECT S.PAY, S.COMMISSION Incorrect example: WHERE (E.SALARY, E.COMM, E.BONUS) IN (SELECT S.PAY, S.COMMISSION 
    SQLCODE -218, warning: the SQL statement referencing a remote object cannot be explained 
    SQLCODE -219 the required explanation table table-name does not exist 
    SQLCODE -220 the column column-name in explanation table table-name is not defined properly 
    SQLCODE -220, warning: the column in explanation table is not defined properly
    SQLCODE -221 "set of optional columns" in explanation table table-name is incomplete. Optional column column-name is missing 
    SQLCODE -224 FETCH cannot make an INSENSITIVE cursor SENSITIVE 
    SQLCODE -225 FETCH statement for cursor-name is not valid for the declaration of the cursor 
    SQLCODE -227 FETCH FETCH-orientation is not allowed, because cursor cursor-name has an unknown position (SQLCODE,sqlstate) 
    SQLCODE -228 for UPDATE clause specified for read-only cursor cursor-name 
    SQLCODE -229 The locale specified in a SET LOCALE statement was not found. 
    SQLCODE -236, warning: SQLDA includes sqlvar entries, but are required for columns 
    SQLCODE -237, warning: SQLDA includes sqlvar entries, but are required because at least one of the columns being described is a distinct type 
    SQLCODE -238, warning: SQLDA includes sqlvar entries, but sqlvar entries are needed for columns because at least one of the columns being described is a LOB 
    SQLCODE -239, warning: SQLDA includes sqlvar entries, but are required for columns because at least one of the columns being described is a distinct type
    SQLCODE -240 the partition clause of a lock table statement is invalid 
    SQLCODE -242 the object named object-name of type object-type was specified more than once in the list of objects, or the name is the same as an existing object 
    SQLCODE -243 sensitive cursor cursor-name cannot be defined for the specified SELECT statement 
    SQLCODE -244 sensitivity sensitivity specified on the FETCH is not valid for cursor cursor-name 
    SQLCODE -245 the invocation of function routine-name is ambiguous copyright 2014 TheAmericanProgrammer.com Unauthorized copying prohibited 
    SQLCODE -246 statement using cursor cursor-name specified number of rows num-rows which is not valid with dimension 
    SQLCODE -247 a hole was detected on a multiple row FETCH statement using cursor cursor-name, but indicator variables were not provided to detect the condition 
    SQLCODE -248 a positioned DELETE or UPDATE statement for cursor cursor-name specified row n of a rowset, but the row is not contained within the current rowset 
    SQLCODE -249 definition of rowset access for cursor cursor-name is inconsistent with the FETCH orientation clause clause specified 
    SQLCODE -250 the local location name is not defined when processing a three-part object name 
    SQLCODE -250, error: the local location name is not defined when processing a three-part object name 
    SQLCODE -251 token name is not valid 
    SQLCODE -253 a non-atomic statement statement successfully completed for some of the requested rows, possibly with warnings, and one or more errors 
    SQLCODE -254 a non-atomic statement statement attempted to process multiple rows of data, but errors occurred 
    SQLCODE -270 function not supported 
    SQLCODE -300 the string contained in host variable or parameter position-number is not nul-terminated 
    SQLCODE -30000 execution failed due to a distribution protocol error that will not affect the successful execution of subsequent commands or SQL statements: reason reason-code (sub-code) 
    SQLCODE -30002 the SQL statement cannot be executed due to a prior condition in a chain of statements 
    SQLCODE -30005 execution failed because function not supported by the server: location location-name product id product-identifier reason reason-code (sub-code) 
    SQLCODE -30020 execution failed due to a distribution protocol error that caused deallocation of the conversation: reason reason-code (sub-code) 
    SQLCODE -30021 execution failed due to a distribution protocol error that will affect the successful execution of subsequent commands or SQL statements: manager manager at level level not supported error 
    SQLCODE -30025 execution failed because function is not supported by the server which caused termination of the connection: location location product id product-identifier reason reason-code (sub-code) 
    SQLCODE -30030 commit request was unsuccessful, a distribution protocol violation has been detected, the conversation has been deallocated. original SQLCODE=original-SQLCODE and original sqlstate=original-sqlstate 
    SQLCODE -30040 execution failed due to unavailable resources that will not affect the successful execution of subsequent commands or SQL statements. reason reason-code type of resource resource-type resource name resource-name product id product-identifier rdbname rdbname 
    SQLCODE -30041 execution failed due to unavailable resources that will affect the successful execution of subsequent commands and SQL statements. reason reason-code type of resource resource-type resource name resource-name product id product-identifier rdbname rdbname 
    SQLCODE -30050 command-or-sql-statement-type command or SQL statement invalid while bind process in progress 
    SQLCODE -30051 bind process with specified package name and consistency token not active 
    SQLCODE -30052 program preparation assumptions are incorrect 
    SQLCODE -30053 owner authorization failure 
    SQLCODE -30060 rdb authorization failure 
    SQLCODE -30061 rdb not found 
    SQLCODE -30070 command command not supported error 
    SQLCODE -30071 object-type object not supported error 
    SQLCODE -30072 parameter subcode parameter not supported error 
    SQLCODE -30073 parameter subcode parameter value not supported error 
    SQLCODE -30074 reply message with codepoint (svrcod) not supported error 
    SQLCODE -30080 communication error code (subcode) 
    SQLCODE -30081 prot communications error detected. api=api, location=loc, function=func, error codes=rc1 rc2 rc3 
    SQLCODE -30082 connection failed for security reason reason-code (reason-string) 
    SQLCODE -30090 remote operation invalid for application execution environment 
    SQLCODE -301 the value of input host variable or parameter number position-number cannot be used as specified because of its data type 
    SQLCODE -30104 error in bind option option-name and bind value option-value. 
    SQLCODE -30105 bind option option1 is not allowed with bind option option2copyright 2014 TheAmericanProgrammer.com Unauthorized copying prohibited 
    SQLCODE -30106 invalid input data detected for a multiple row INSERT operation. INSERT processing is terminated 
    SQLCODE -302 the value of input variable or parameter number position-number is invalid or too large for the target column or the target value 
    SQLCODE -303 a value cannot be assigned to output host variable number position-number because the data types are not comparable 
    SQLCODE -304 a value with data type data-type1 cannot be assigned to a host variable because the value is not within the range of the host variable in position position-number with data type data-type20 
    SQLCODE -305 the null value cannot be assigned to output host variable number position-number because no indicator variable is specified 
    SQLCODE -309 a predicate is invalid because a referenced host variable has the null value 
    SQLCODE -310 decimal host variable or parameter number contains non-decimal data 
    SQLCODE -311 the length of input host variable number position-number is negative or greater than the maximum 
    SQLCODE -312 variable variable-name is not defined or not usable 
    SQLCODE -313 the number of host variables specified is not equal to the number of parameter markers 
    SQLCODE -314 the statement contains an ambiguous host variable reference 
    SQLCODE -327 the row cannot be inserted because it is outside the bound of the partition range for the last partition 
    SQLCODE -330 a string cannot be used because it cannot be processed. reason reason-code, character code-point, host variable position-number 
    SQLCODE -331 character conversion cannot be performed because a string, position position-number, cannot be converted from source-ccsid to target-ccsid, reason reason-code 
    SQLCODE -332 character conversion between ccsid from-ccsid to to-ccsid requested by reason-code is not supported 
    SQLCODE -333 the subtype of a string variable is not the same as the subtype known at bind time and the difference cannot be resolved by character conversion 
    SQLCODE -336 the scale of the decimal number must be zero start of 
    SQLCODE -338 an ON clause is invalid 
    SQLCODE -339, error: the SQL statement cannot be executed from an ascii based drda application requestor to a v2r2 DB2 subsystem -or- 
    SQLCODE -339, warning: the SQL statement has been successfully executed but there may be some character conversion inconsistencies 
    SQLCODE -340 the common table expression name has the same identifier as another occurrence of a common table expression definition within the same statement 
    SQLCODE -341 a cyclic reference exists between the common table expressions name1 and name2 
    SQLCODE -342 the common table expression name must not use SELECT DISTINCT and must use UNION ALL because it is recursive 
    SQLCODE -343 the column names are required for the recursive common table expression name 
    SQLCODE -344 the recursive common table expression name has mismatched data types or lengths or code page for column column-name 
    SQLCODE -345 the fullselect of the recursive common table expression name must be a UNION ALL and must not include aggregate functions, group by clause, having clause, or an explicit join including an on clause 
    SQLCODE -346 an invalid reference to common table expression name occurs in the first fullselect, as a second occurrence in the same from clause, or in the from clause of a subquery 
    SQLCODE -348 sequence-expression cannot be specified in this context 
    SQLCODE -350 column-name was implicitly or explicitly referenced in a context in which it cannot be used 
    SQLCODE -351 an unsupported sqltype was encountered in position position-number of the select-list 
    SQLCODE -352 an unsupported sqltype was encountered in position position-number of the input-list 
    SQLCODE -353 FETCH is not allowed, because cursor cursor-name has an unknown position 
    SQLCODE -354 a rowset FETCH statement may have returned one or more rows of data. however, one or more non-terminating error conditions were encountered. use the get diagnostics statement for more information regarding the conditions that were encountered 
    SQLCODE -355 a LOB column is too large to be logged 
    SQLCODE -356 key expression expression-number is not valid, reason code = reason-code 
    SQLCODE -359 the range of values for the identity column or sequence is exhausted 
    SQLCODE -363 the extended indicator variable value for parameter position-number is out of range. 
    SQLCODE -365 use of the value of extended indicator variable in position value-position is not valid. 
    SQLCODE -372 only one rowid, identity, row change timestamp, row begin, row end, transaction start id, or security label column is allowed in a table 
    SQLCODE -373 default cannot be specified for column or SQL variable name 
    SQLCODE -374 the clause clause has not been specified in the create or alter function statement for language SQL function function-name but an examination of the function body reveals that it should be specified 
    SQLCODE -390 the function function-name, specific name specific-name, is not valid in the context where it is used 
    SQLCODE -390, error: the function name , specific name , is not valid in the context in which it occurs 
    SQLCODE -392 SQLDA provided for cursor cursor-name has been changed from the previous FETCH (reason-code) 
    SQLCODE -392, error: SQLDA provided for cursor has been changed from the previous FETCH 
    SQLCODE -393 the condition or connection number is invalid 
    SQLCODE -394, warning: user specified optimization hints used during access path selection 
    SQLCODE -395, warning: user specified optimization hints are invalid (reason code = ''). the optimization hints are ignored 
    SQLCODE -396 object-type object-name attempted to execute an SQL statement during final call processing 
    SQLCODE -397 generated is specified as part of a column definition, but it is not valid for the definition of the column 
    SQLCODE -398 a locator was requested for host variable number position-number but the variable is not a LOB 
    SQLCODE -399 invalid value rowid was specified copyright 2014 TheAmericanProgrammer.com Unauthorized copying prohibited 
    SQLCODE -400 the catalog has the maximum number of user defined indexes 
    SQLCODE -401 the data types of the operands of an operation are not compatible
    SQLCODE -402 an arithmetic function or operator function-operator is applied to character or datetime data -or- 
    SQLCODE -402, warning: location is unknown 
    SQLCODE -403, warning: the local object referenced by the create alias statement does not exist 
    SQLCODE -404 the SQL statement specifies a string that is too long 
    SQLCODE -405 the numeric constant constant cannot be used as specified because it is out of range 
    SQLCODE -406 a calculated or derived numeric value is not within the range of its object column 
    SQLCODE -407 an UPDATE, INSERT, or set value is null, but the object column column-name cannot contain null values 
    SQLCODE -408 the value is not compatible with the data type of its target. target name is name 
    SQLCODE -409 invalid operand of a count function 
    SQLCODE -410 a numeric value value is too long, or it has a value that is not within the range of its data type 
    SQLCODE -411, error: current sqlid cannot be used in a statement that references remote objects 
    SQLCODE -412 the SELECT clause of a subquery specifies multiple columns 
    SQLCODE -413 overflow or underflow occurred during numeric data type conversion 
    SQLCODE -414 a like predicate is invalid because the first operand is not a string 
    SQLCODE -415 the corresponding columns, column-number, of the operands of a set operator are not compatible 
    SQLCODE -416 an operand of a set operator contains a long string column 
    SQLCODE -417 a statement string to be prepared includes parameter markers as the operands of the same operator 
    SQLCODE -418 a statement string to be prepared contains an invalid use of parameter markers 
    SQLCODE -419 the decimal divide operation is invalid because the result would have a negative scale 
    SQLCODE -420 the value of a string argument was not acceptable to the function-name function 
    SQLCODE -421 the operands of a set operator do not have the same number of columns 
    SQLCODE -423 invalid value for locator in position position-# 
    SQLCODE -426 dynamic commit not valid at an application server where updates are not allowed 
    SQLCODE -427 dynamic rollback not valid at an application server where updates are not allowed 
    SQLCODE -430 routine-type routine-name (specific name specific-name) has abnormally terminated 
    SQLCODE -4302 java stored procedure or user-defined function routine-name (specific name specific-name) has exited with an exception exception-string 
    SQLCODE -431 routine routine-name (specific name specific-name) of type routine-type has been interrupted by the user 
    SQLCODE -433 value value is too long 
    SQLCODE -43324 Remote website copied current URL without authorization. 
    SQLCODE -434, warning: option is a deprecated feature 
    SQLCODE -435 an invalid SQLSTATE SQLSTATEis specified in a raise_error function, resignal statement, or signal statement 
    SQLCODE -438 application raised error with diagnostic text: text 
    SQLCODE -440 no authorized routine-type by the name routine-name having compatible arguments was found in the current path 
    SQLCODE -441 invalid use of 'distinct' or 'all' with function function-name 
    SQLCODE -443 routine routine-name (specific name specific-name) has returned an error SQLSTATEwith diagnostic text msg-text 
    SQLCODE -444 user program name could not be found 
    SQLCODE -445, warning: value has been truncated 
    SQLCODE -449 create or alter statement for function or procedure routine-name contains an invalid format of the external name clause or is missing the external name clause 
    SQLCODE -450 user-defined function or stored procedure name, parameter number parmnum, overlayed storage beyond its declared length. 
    SQLCODE -450, error: user-defined function or stored procedure , parameter number , overlayed storage beyond its declared length 
    SQLCODE -451 the data-item definition in the create or alter statement for routine-name contains data type type which is not supported for the type and language of the routine 
    SQLCODE -452 unable to access the file referenced by host variable variable-position. reason code: reason-code 
    SQLCODE -453 there is a problem with the returns clause in the create function statement for function-name 
    SQLCODE -454 the signature provided in the create function statement for function-name matches the signature of some other function already existing in the schema 
    SQLCODE -455 in create function for function-name, the schema name schema-name1 provided for the specific name does not match the schema name schema-name2 of the function 
    SQLCODE -456 in create function for function-name, the specific name specific-name already exists in the schema 
    SQLCODE -457 a function or distinct type cannot be called name since it is reserved for system use 
    SQLCODE -458 in a reference to function function-name by signature, a matching function could not be found 
    SQLCODE -461 a value with data type source-data-type cannot be cast to type target-data-type 
    SQLCODE -462, warning: external function or procedure (specific name ) has returned a warning sqlstate, with diagnostic text 
    SQLCODE -463, error: external function (specific name ) has returned an invalid SQLSTATE, with diagnostic text 
    SQLCODE -464, warning: procedure returned query result sets, which exceeds the defined limit 
    SQLCODE -466, warning: procedure returned query result sets 
    SQLCODE -469 SQL call statement must specify an output host variable for parameter number 
    SQLCODE -470 SQL call statement specified a null value for input parameter number, but the stored procedure does not support null values. 
    SQLCODE -4700 attempt to use new function before new function mode 
    SQLCODE -4701 the number of partitions, or the combination of the number of table space partitions and the corresponding length of the partitioning limit key exceeds the system limit; or the combination of the number of table space partitions exceeds the maxpartitions for partition by growth table space. 
    SQLCODE -4704 an unsupported data type was encountered as an include column 
    SQLCODE -4705 option specified on alter statement for routine-name (routine-type is not valid 
    SQLCODE -4706 alter statement for an SQL routine cannot be processed because the options currently in effect (envid current-envid) are not the same as the ones that were in effect (envid defined-envid) when the routine or version was first defined 
    SQLCODE -4709 explain monitored stmts failed with reason code = yyyyy 
    SQLCODE -471 invocation of function or procedure name failed due to reason rc 
    SQLCODE -4710 exchange data statement specified table1 and table2 but the tables do not have a defined clone relationship 
    SQLCODE -472 cursor cursor-name was left open by external function function-name (specific name specific-name) 
    SQLCODE -4727 system parameter system-parameter value parameter-value is inconsistent with clause clause specified on statement-name statement. 
    SQLCODE -473 a user defined data type cannot be called the same name as a system predefined type (built-in type) 
    SQLCODE -4730 invalid specification of XML column table-name.column-name is not defined in the XML versioning format, reason reason-code 
    SQLCODE -4731 the native SQL routine statement for package location-name.collection-id.program-name.consistency-token statement number statement-number cannot be processed. 
    SQLCODE -4732 the maximum number of alters allowed has been exceeded for object-type 
    SQLCODE -4733 the alter table statement cannot be executed because column column-name is mixed data, or the data type or length specified does not agree with the existing data type or length 
    SQLCODE -4734 the load module for the procedure assumes a parameter varchar option that is not consistent with the option specified on the create procedure statement for procedure-name 
    SQLCODE -4735 invalid table reference for table locator 
    SQLCODE -4736 a period specification or period clause is not supported as specified for object object-name. reason code = reason-code. 
    SQLCODE -4737 statement statement is not allowed when using a trusted connection 
    SQLCODE -4738 table table-name cannot be defined as specified in the statement statement in a common criteria environment 
    SQLCODE -4739 environment settings (identified by envid1) used by object-name are not the same as the ones that were in effect (identified byenvid2) when other column masks and row permissions were defined for table table-name 
    SQLCODE -475 the result type type-1 of the source function cannot be cast to the returns type type-2 of the user-defined function function-name 
    SQLCODE -475, error: the result type of the source function cannot be cast to the returns type of the user-defined function 
    SQLCODE -476 reference to function function-name was named without a signature, but the function is not unique within its schema 
    SQLCODE -478 drop or revoke on object type required-type cannot be processed because object dependent-object of type dependent-type is dependent on it 
    SQLCODE -480 the procedure procedure-name has not yet been called 
    SQLCODE -482 the procedure procedure-name returned no locators 
    SQLCODE -482, error: the procedure returned no locators 
    SQLCODE -483 in create function for function-name statement, the number of parameters does not match the number of parameters of the source function 
    SQLCODE -487 object-type object-name attempted to execute an SQL statement when the definition of the function or procedure did not specify this action 
    SQLCODE -490 number number directly specified in an SQL statement is outside the range of allowable values in this context (minval, maxval) 
    SQLCODE -491 create statement for user-defined function function-name must have a returns clause and: the external clause with other required keywords; the parameter names; or the source clause 
    SQLCODE -492 the create function for function-name has a problem with parameter number number. it may involve a mismatch with a source function 
    SQLCODE -494, warning: number of result sets is greater than number of locators 
    SQLCODE -495 estimated processor cost of estimate-amount1 processor seconds (estimate-amount2 service units) in cost category cost-category exceeds a resource limit error threshold of limit- amount service units 
    SQLCODE -495, warning: estimated processor cost of processor seconds ( service units) in cost category exceeds a resource limit warning threshold of service units 
    SQLCODE -496 the SQL statement cannot be executed because it references a result set that was not created by the current server 
    SQLCODE -497 the maximum limit of internal identifiers has been exceeded for database database-name 
    SQLCODE -499 cursor cursor-name has already been assigned to this or another result set from procedure procedure-name. 
    SQLCODE -500 the identified cursor was closed when the connection was destroyed 
    SQLCODE -5001 table table-name is not valid 
    SQLCODE -501 Cursor not open on FETCH [IEQ735i] 
    SQLCODE -5012 host variable host-variable is not exact numeric with scale zero
    SQLCODE -502 Opening cursor that is already open 
    SQLCODE -503 Updating column which needs to be specified in FOR UPDATE OF 
    SQLCODE -504 cursor name cursor-name is not declared 
    SQLCODE -507 the cursor identified in the UPDATE or DELETE statement is not open 
    SQLCODE -508 the cursor identified in the UPDATE or DELETE statement is not positioned on a row or rowset that can be updated or deleted 
    SQLCODE -509 the table identified in the UPDATE or DELETE statement is not the same table designated by the cursor 
    SQLCODE -510 the table designated by the cursor of the UPDATE or DELETE statement cannot be modified 
    SQLCODE -511 the for UPDATE clause cannot be specified because the result table designated by the SELECT statement cannot be modified 
    SQLCODE -512 statement reference to remote object is invalid 
    SQLCODE -513 the alias alias-name must not be defined on another local or remote alias 
    SQLCODE -514 the cursor cursor-name is not in a prepared state 
    SQLCODE -516 the describe statement does not specify a prepared statement 
    SQLCODE -517 cursor cursor-name cannot be used because its statement name does not identify a prepared SELECT statement 
    SQLCODE -518 the execute statement does not identify a valid prepared statement 
    SQLCODE -519 the prepare statement identifies the SELECT statement of the opened cursor cursor-name 
    SQLCODE -525 the SQL statement cannot be executed because it was in error at bind time for section = sectno package = pkgname consistency token = contoken 
    SQLCODE -526 the requested operation or usage does not apply to table-type temporary table table-name 
    SQLCODE -530 SQLSTATE 23503 Referential integrity prevents the INSERT/UPDATE -or- 
    SQLCODE -530 the INSERT or UPDATE value of foreign key constraint-name is invalid 
    SQLCODE -531 parent key in a parent row cannot be updated because it has one or more dependent rows in relationship constraint-name 
    SQLCODE -532 SQLSTATE 23504 Referential integrity (DELETE RESTRICT rule) prevents the DELETE -or- 
    SQLCODE -532 the relationship constraint-name restricts the deletion of row with rid x rid-number 
    SQLCODE -533 invalid multiple-row INSERT 
    SQLCODE -534 the primary key cannot be updated because of multiple-row UPDATE 
    SQLCODE -535, warning: the result of the positioned UPDATE or DELETE may depend on the order of the rows 
    SQLCODE -536 SQLSTATE 42914 Referential integrity (DELETE RESTRICT rule) prevents the DELETE 
    SQLCODE -537 the primary key, foreign key, unique, or partitioning key clause identifies column column-name more than once 
    SQLCODE -538 foreign key name does not conform to the description of a parent key of table table-name 
    SQLCODE -539 table table-name does not have a primary key 
    SQLCODE -540 the definition of table table-name is incomplete because it lacks a primary index or a required unique index 
    SQLCODE -541, warning: the referential or unique constraint has been ignored because it is a duplicate 
    SQLCODE -542 column-name cannot be a column of a hash key, primary key, a unique constraint, or a parent key because it can contain null values 
    SQLCODE -543 a row in a parent table cannot be deleted because the check constraint check-constraint restricts the deletion 
    SQLCODE -544 the check constraint specified in the alter table statement cannot be added because an existing row violates the check constraint 
    SQLCODE -545 SQLSTATE 23513 Check constraint prevents the INSERT/UPDATE 
    SQLCODE -546 the check constraint constraint-name is invalid 
    SQLCODE -548 a check constraint that is defined with column-name is invalid 
    SQLCODE -549 the statement statement is not allowed for object_type1 object_name because the bind option dynamicrules(run) is not in effect for object_type 
    SQLCODE -551 auth-id does not have the privilege to perform operation operation on object object-name 
    SQLCODE -552 authorization-id does not have the privilege to perform operation operation 
    SQLCODE -553 auth-id specified is not one of the valid authorization ids for requested operation 
    SQLCODE -553, error: specified is not one of the valid authorization ids 
    SQLCODE -554 an authorization id or role cannot grant a privilege to itself 
    SQLCODE -555 an authorization id or role cannot revoke a privilege from itself
    SQLCODE -556 revoke-target cannot have the privilege privilege object-name revoked by revoker-id because the revokee does not possess the privilege or the revoker did not make the grant 
    SQLCODE -557 inconsistent grant/revoke keyword keyword. permitted keywords are keyword-list 
    SQLCODE -558, error: invalid clause or combination of clauses on a grant or revoke 
    SQLCODE -559 all authorization functions have been disabled 
    SQLCODE -561, warning: the alter, index, references, and trigger privileges cannot be granted to public at all locations 
    SQLCODE -562 the specified privileges cannot be granted to public. 
    SQLCODE -567 bind-type authorization error using auth-id authority package = package-name privilege = privilege 
    SQLCODE -571 the statement would result in a multiple site UPDATE 
    SQLCODE -573 table table-name does not have a unique key with the specified column names 
    SQLCODE -574 the specified default value or identity attribute value conflicts with the definition of column column-name 
    SQLCODE -575 object object-name (object type object-type) cannot be referenced explicitly or implicitly 
    SQLCODE -577 object-type object-name attempted to modify data when the definition of the function or procedure did not specify this action 
    SQLCODE -578 the return statement was not executed for SQL function function-name. 
    SQLCODE -579, error: attempted to read data when the definition of the function or procedure did not specify this action 
    SQLCODE -580 the result-expressions of a case expression cannot all be null 
    SQLCODE -581 the data types of the result-expressions of a case expression are not compatible 
    SQLCODE -582 the search-condition in a searched-when-clause of a case is not valid in the context in which it was specified. the search condition contains a quantified predicate or an in predicate that includes a fullselect, and these are not allowed in the specified context. 
    SQLCODE -583 the use of function or expression name is invalid because it is not deterministic or has an external action 
    SQLCODE -584 invalid use of null Updated Sept 2013 The American Programmer unique ID IEQ735i 
    SQLCODE -585 the collection collection-id appears more than once in the set special-register statement 
    SQLCODE -586 the total length of the current path special register cannot exceed 2048 characters 
    SQLCODE -589 a positioned DELETE or UPDATE statement for cursor cursor-name specified a row of a rowset, but the cursor is not positioned on a rowset 
    SQLCODE -590 name name is not unique in the create or alter for routine routine-name 
    SQLCODE -592 not authorized to create functions or procedures in wlm environment env-name 
    SQLCODE -593 not null must be specified for column-name because it is defined as a rowid (or distinct type for rowid), row change timestamp column, row begin column, row end column, or column of a period column-name 
    SQLCODE -594 attempt to create a nullable rowid or distinct type column column-name 
    SQLCODE -599, warning: comparison functions are not created for a distinct type based on a long string data type 
    SQLCODE -601 the name (version or volume serial number) of the object to be defined or the target of a rename statement is identical to the existing name (version or volume serial number) object-name of the object type object-type 
    SQLCODE -602 too many columns, periods, or key-expressions specified in a create index or alter index statement 
    SQLCODE -603 a unique index cannot be created because the table contains rows which are duplicates with respect to the values of the identified columns and periods 
    SQLCODE -604 a data type definition specifies an invalid length, precision, or scale attribute 
    SQLCODE -607 operation or option operation is not defined for this object 
    SQLCODE -610, warning: a create/alter on object has placed object in pending 
    SQLCODE -611 only lockmax 0 can be specified when the lock size of the tablespace is tablespace or table 
    SQLCODE -612 identifier is a duplicate name 
    SQLCODE -613 the primary key or a hash key or a unique constraint is too long or has too many columns and periods 
    SQLCODE -614 the index cannot be created or altered, or the length of a column cannot be changed because the sum of the internal lengths of the columns for the index is greater than the allowable maximum 
    SQLCODE -615 operation-type is not allowed on a package in use 
    SQLCODE -616 obj-type1 obj-name1 cannot be dropped because it is referenced by obj-type2 obj-name2 
    SQLCODE -617, error: a type 1 index is not valid for table 
    SQLCODE -618 operation operation is not allowed on system databases 
    SQLCODE -619 operation disallowed because the database is not stopped 
    SQLCODE -620 keyword keyword in stmt-type statement is not permitted for a space-type space in the database-type database 
    SQLCODE -621 duplicate dbid dbid was detected and previously assigned to database-name 
    SQLCODE -622 for mixed data is invalid because the mixed data install option is no 
    SQLCODE -623 cluster is not valid for table-name 
    SQLCODE -624 table table-name already has a primary key or unique constraint with specified columns and periods 
    SQLCODE -625 table table-name does not have an index to enforce the uniqueness of the primary or unique key 
    SQLCODE -625, warning: the definition of table has been changed to incomplete 
    SQLCODE -626 the alter statement is not executable because the page set is not stopped 
    SQLCODE -627 the alter statement is invalid because the table space or index has user-managed data sets 
    SQLCODE -628 the clauses are mutually exclusive 
    SQLCODE -629 set null cannot be specified because foreign key name cannot contain null values 
    SQLCODE -630, error: the WHERE NOT NULL specification is invalid for type 1 indexes 
    SQLCODE -631 foreign key name is too long or has too many columns 
    SQLCODE -632 the table cannot be defined as a dependent of table-name because of DELETE rule restrictions 
    SQLCODE -633 the DELETE rule must be DELETE-rule 
    SQLCODE -634 the DELETE rule must not be cascade 
    SQLCODE -635 the DELETE rules cannot be different or cannot be set null 
    SQLCODE -636 ranges specified for partition part-num are not valid 
    SQLCODE -637 duplicate keyword-name keyword or clause 
    SQLCODE -638 table table-name cannot be created because column definition is missing 
    SQLCODE -639 a nullable column of a foreign key with a DELETE rule of set null cannot be a column of the key of a partitioned index 
    SQLCODE -640 locksize row cannot be specified because table in this tablespace has type 1 index 
    SQLCODE -642, error: too many columns in unique constraints 
    SQLCODE -643 a check constraint or the value of an expression for a column of an index exceeds the maximum allowable length key expression 
    SQLCODE -644 invalid value specified for keyword or clause keyword-or-clause in statement stmt-type 
    SQLCODE -645, warning: WHERE NOT NULL is ignored because the index key cannot contain null values 
    SQLCODE -646 table table-name cannot be created in specified table space table-space-name because it already contains a table 
    SQLCODE -647 bufferpool bp-name for implicit or explicit tablespace or indexspace name has not been activated 
    SQLCODE -650 the alter statement cannot be executed, reason reason-codecopyright 2014 TheAmericanProgrammer.com Unauthorized copying prohibited 
    SQLCODE -651 table description exceeds maximum size of object descriptor. 
    SQLCODE -652 violation of installation defined edit or validation procedure proc-name 
    SQLCODE -653 table table-name in partitioned table space tspace-name is not available because its partitioned index has not been created 
    SQLCODE -655 the create or alter stogroup is invalid because the storage group would have both specific and non-specific volume ids 
    SQLCODE -658 a object-type cannot be dropped using the statement statement 
    SQLCODE -660 index index-name cannot be created or altered on partitioned table space tspace-name because key limits are not specified 
    SQLCODE -661 object-type object-name cannot be created on partitioned table space tspace-name because the number of partition specifications is not equal to the number of partitions of the table space 
    SQLCODE -662 a partitioned index cannot be created on a table space, or a table space cannot be index-controlled. table space tspace-name, reason reason-code 
    SQLCODE -663 the number of key limit values is either zero, or greater than the number of columns in the key of index index-name 
    SQLCODE -664, warning: the internal length of the limit-key fields for the partitioned index exceeds the length imposed by the index manager 
    SQLCODE -665 the partition clause of an alter statement is omitted or invalid 
    SQLCODE -666 stmt-verb object cannot be executed because function is in progress 
    SQLCODE -667 the clustering index for a partitioned table space cannot be explicitly dropped 
    SQLCODE -668 the column cannot be added to the table because the table has an edit procedure defined with row attribute sensitivity 
    SQLCODE -669 the object cannot be explicitly dropped. reason reason-code 
    SQLCODE -670 the record length of the table exceeds the page size limit 
    SQLCODE -671 the bufferpool attribute of the table space cannot be altered as specified because it would change the page size of the table space 
    SQLCODE -672 operation drop not allowed on table table_name 
    SQLCODE -676 the physical characteristics of the index are incompatible with respect to the specified statement. the statement has failed. reason reason-code 
    SQLCODE -677 insufficient virtual storage for bufferpool expansion 
    SQLCODE -678 the constant constant specified for the index limit key must conform to the data type data-type of the corresponding column column-name 
    SQLCODE -679 the object name cannot be created because a drop is pending on the object 
    SQLCODE -680 too many columns specified for a table, view or table function 
    SQLCODE -681 column column-name in violation of installation defined field procedure. rt: return-code, rs: reason-code, msg: message-token 
    SQLCODE -682 field procedure procedure-name could not be loaded 
    SQLCODE -683 the specification for column, distinct type, function, or procedure data-item contains incompatible clauses 
    SQLCODE -684 the length of constant list beginning string is too long 
    SQLCODE -685 invalid field type, column-name 
    SQLCODE -686 column defined with a field procedure can not compare with another column with different field procedure 
    SQLCODE -687 field types incomparable 
    SQLCODE -688 incorrect data returned from field procedure, column-name, msgno 
    SQLCODE -689 too many columns defined for a dependent table 
    SQLCODE -690 the statement is rejected by data definition control support. reason reason-code 
    SQLCODE -691 the required registration table table-name does not exist 
    SQLCODE -692 the required unique index index-name for ddl registration table table-name does not exist 
    SQLCODE -693 the column column-name in ddl registration table or index name is not defined properly 
    SQLCODE -694 the schema statement cannot be executed because a drop is pending on the ddl registration table table-name 
    SQLCODE -694, error: the ddl statement cannot be executed because a drop is pending on the ddl registration table 
    SQLCODE -695 invalid value seclabel specified for security label column of table table-name 
    SQLCODE -696 the definition of trigger trigger-name includes an invalid use of correlation name or transition table name name. reason code=reason-code 
    SQLCODE -697 old or new correlation names are not allowed in a trigger defined with the for each statement clause. old_table or new_table names are not allowed in a trigger with the before clause. 
    SQLCODE -7008 object-name not valid for operation (reason-code) 
    SQLCODE -713 the replacement value for special-register is invalid 
    SQLCODE -715 program program-name with mark release-dependency-mark failed because it depends on functions of the release from which fallback has occurred 
    SQLCODE -716 program program-name precompiled with incorrect level for this release 
    SQLCODE -717 bind-type for object-type object-name with mark release-dependency-mark failed because object-type depends on functions of the release from which fallback has occurred 
    SQLCODE -718 rebind of package package-name failed because ibmreqd of ibmreqd is invalid 
    SQLCODE -719 bind add error using auth-id authority package package-name already exists 
    SQLCODE -720 bind error, attempting to replace package = package_name with version= version2 but this version already exists 
    SQLCODE -721 bind error for package = pkg-id contoken = contoken'x is not unique so it cannot be created 
    SQLCODE -722 bind-type error using auth-id authority package package-name does not exist 
    SQLCODE -723 an error occurred in a triggered SQL statement in trigger-name. information returned: SQLCODE: sql-code, sqlstate: sql-state, message tokens token-list, section number section-number 
    SQLCODE -723, error: an error occurred in a triggered SQL statement in trigger , section number .information returned: SQLCODE , SQLSTATE, and message tokens
    SQLCODE -724 the activation of the object-type object object-name would exceed the maximum level of indirect SQL cascading 
    SQLCODE -725 the special register register at location location was supplied an invalid value 
    SQLCODE -726 bind error attempting to replace package = package-name. there are enable or disable entries currently associated with the package 
    SQLCODE -728, error: data type is not allowed in DB2 private protocol processing 
    SQLCODE -729 a stored procedure specifying commit on return cannot be the target of a nested call statement 
    SQLCODE -730 the parent of a table in a read-only shared database must also be a table in a read-only shared database 
    SQLCODE -731 user-defined dataset dsname must be defined with shareoptions(1,3) 
    SQLCODE -732 the database is defined on this subsystem with the roshare read attribute but the table space or index space has not been defined on the owning subsystem 
    SQLCODE -733 the description of a table space, index space, or table in a roshare read database must be consistent with its description in the owner system 
    SQLCODE -734 the roshare attribute of a database cannot be altered from roshare read 
    SQLCODE -735 database dbid cannot be accessed because it is no longer a shared database 
    SQLCODE -736 invalid obid obid specified 
    SQLCODE -737 implicit table space not allowed 
    SQLCODE -738, warning: definition change of may require similar change on read-only systems 
    SQLCODE -739 create or alter function function-name failed because functions cannot modify data when they are processed in parallel. 
    SQLCODE -740 function name is defined with the option modifies SQL data which is not valid in the context in which it was invoked 
    SQLCODE -741 a database-type database is already defined for member member-name 
    SQLCODE -742 dsndb07 is the implicit work file database 
    SQLCODE -746 the SQL statement in function, trigger, or in stored procedure name violates the nesting SQL restriction 
    SQLCODE -747 table table-name is not available until the auxiliary tables and indexes for its externally stored columns have been created 
    SQLCODE -748 an index index-name already exists on auxiliary table table-name 
    SQLCODE -750 the source table table-name cannot be renamed or altered because it is referenced in an existing view, materialized query table, trigger definition, or is a clone table, or has a clone table defined for it. 
    SQLCODE -751 object-type object-name (specific name specific name) attempted to execute an SQL statement SQL-statement that is not allowed 
    SQLCODE -752 the connect statement is invalid because the process is not in the connectable state 
    SQLCODE -763 invalid table space name space-name 
    SQLCODE -764 a LOB table space and its associated base table space must be in the same database 
    SQLCODE -765 table is not compatible with database 
    SQLCODE -766 the object of a statement is a table for which the requested operation is not permitted 
    SQLCODE -767 missing or invalid column specification for index index-name 
    SQLCODE -768 an auxiliary table already exists for the specified column or partition 
    SQLCODE -769 specification of create aux table does not match the characteristics of the base table 
    SQLCODE -770 table table-name cannot have a LOB column unless it also has a rowid, or an XML column unless it also has a docid column 
    SQLCODE -771 invalid specification of a rowid column 
    SQLCODE -773 case not found for case statement 
    SQLCODE -775 statement specified in SQL routine is not allowed within a compound statement. 
    SQLCODE -776 use of cursor cursor-name is not valid 
    SQLCODE -778 ending label label-name does not match the beginning label 
    SQLCODE -779 label label specified on a goto, iterate, or leave statement is not valid 
    SQLCODE -780 undo specified for a handler 
    SQLCODE -781 condition condition-name is not defined or the definition is not in scope 
    SQLCODE -782 a condition or SQLSTATEcondition-value specified is not valid 
    SQLCODE -783 SELECT list for cursor cursor-name in for statement is not valid. column column-name is not unique 
    SQLCODE -784 constraint constraint-name cannot be dropped. 
    SQLCODE -785 use of SQLCODE or SQLSTATEis not valid 
    SQLCODE -787 resignal statement issued outside of a handler 
    SQLCODE -797 the trigger trigger-name is defined with an unsupported triggered SQL statement 
    SQLCODE -798 a value cannot be specified for column column-name which is defined as generated always 
    SQLCODE -799, warning: a set statement references a special register that does not exist at the server site 
    SQLCODE -802 exception error exception-type has occurred during operation-type operation on data-type data, position position-number 
    SQLCODE -803 an inserted or updated value is invalid because the index in index space indexspace-name constrains columns of the table so no two rows can contain duplicate values in those columns. rid of existing row is x record-id -or- 
    SQLCODE -803 SQLSTATE 23505 Duplicate key on INSERT or UPDATE. (Duplicate record in DB2) 
    SQLCODE -803, error: an inserted or updated value is invalid because index in index space constrains columns of the table so no two rows can contain duplicate values in those columns. RID of existing row is x'' 
    SQLCODE -804 an error was found in the application program input parameters for the SQL statement, reason reason 
    SQLCODE -805 dbrm or package name location-name.collection-id.dbrm-name.consistency-token not found in plan plan-name. reason reason-code -or- 
    SQLCODE -805 DBRM or package not found in plan Is plan name correct? 
    SQLCODE -806, warning: bind isolation level rr conflicts with tablespace locksize page or locksize row and lockmax 0 
    SQLCODE -807 access denied: package package-name is not enabled for access from connection-type connection-name 
    SQLCODE -808 the connect statement is not consistent with the first connect statement 
    SQLCODE -811 More than one row retrieved in SELECT INTO -or- 
    SQLCODE -811 the result of an embedded SELECT statement or a subselect in the set clause of an UPDATE statement is a table of more than one row, or the result of a subquery of a basic predicate is more than one value 
    SQLCODE -812 the SQL statement cannot be processed because a blank collection-id was found in the current packageset special register while trying to form a qualified package name for program program-name.consistency-token using plan plan-name 
    SQLCODE -815, error: a group by or having clause is implicitly or explicitly specified in a subselect of a basic predicate or a set clause of an UPDATE statement 
    SQLCODE -817 the SQL statement cannot be executed because the statement will result in a prohibited UPDATE operation. 
    SQLCODE -818 Plan and program: timestamp mismatch 
    SQLCODE -819 the view cannot be processed because the length of its parse tree in the catalog is zero 
    SQLCODE -820 the SQL statement cannot be processed because catalog-table contains a value that is not valid in this release 
    SQLCODE -822 the SQLDA contains an invalid data address or indicator variable address 
    SQLCODE -840 too many items returned in a SELECT or INSERT list 
    SQLCODE -842 a connection to location-name already exists 
    SQLCODE -843 the set connection or release statement must specify an existing connection 
    SQLCODE -845 a previous value expression cannot be used before the next value expression generates a value in the current application process for sequence sequence-name 
    SQLCODE -846 invalid specification of an identity column or sequence object object-type object-name. reason code = reason-code 
    SQLCODE -863, warning: the connection was successful but only sbcs will be supported 
    SQLCODE -867 invalid specification of a rowid column copyright 2014 TheAmericanProgrammer.com Unauthorized copying prohibited 
    SQLCODE -870 the number of host variables in the statement is not equal to the number of descriptors 
    SQLCODE -872 a valid ccsid has not yet been specified for this subsystem 
    SQLCODE -873 the statement referenced data encoded with different encoding schemes or ccsids in an invalid context 
    SQLCODE -874 the encoding scheme specified for the object-type must be the same as the containing table space or other parameters 
    SQLCODE -875 operand cannot be used with the ascii data referenced 
    SQLCODE -876 object-type cannot be created or altered, reason reason-text 
    SQLCODE -877 ccsid ascii or ccsid unicode is not allowed for this database or table space 
    SQLCODE -878 the explain-object used for explain must be encoded in unicode. it cannot be in ascii or ebcdic. 
    SQLCODE -879 create or alter statement for obj-name cannot define a column, distinct type, function or stored procedure parameter as mixed or graphic with encoding scheme encoding-scheme 
    SQLCODE -880 savepoint savepoint-name does not exist or is invalid in this context 
    SQLCODE -881 a savepoint with name savepoint-name already exists, but this savepoint name cannot be reused 
    SQLCODE -882 savepoint does not exist 
    SQLCODE -883, warning: rollback to savepoint occurred when there were operations that cannot be undone or an operation that cannot be undone occurred when there was a savepoint outstanding 
    SQLCODE -900 the SQL statement cannot be executed because the application process is not connected to a server 
    SQLCODE -900, error: the SQL statement cannot be executed because the application process is not connected to an application server 
    SQLCODE -901 unsuccessful execution caused by a system error that does not preclude the successful execution of subsequent SQL statements 
    SQLCODE -901, error: unsuccessful execution caused by a system error that does not preclude the successful execution of subsequent SQL statements 
    SQLCODE -902 pointer to the essential control block (ct/rda) has value 0, rebind required 
    SQLCODE -902, error: pointer to essential control block(rda/ct) has value 0, rebind required 
    SQLCODE -904 SQLSTATE 57011 Unavailable resource. Someone is locking the data you need you may choose to terminate the program -or- 
    SQLCODE -904 unsuccessful execution caused by an unavailable resource. reason reason-code, type of resource resource-type, and resource name resource-name 
    SQLCODE -905 unsuccessful execution due to resource limit being exceeded, resource name = resource-name limit = limit-amount1 cpu seconds (limit-amount2 service units) derived from limit-source 
    SQLCODE -906 the SQL statement cannot be executed because this function is disabled due to a prior error 
    SQLCODE -908 bind-type error using auth-id authority. bind, rebind or auto-rebind operation is not allowed 
    SQLCODE -909 the object has been deleted or altered 
    SQLCODE -910 the SQL statement cannot access an object on which uncommitted changes are pending 
    SQLCODE -911 SQLSTATE 40000 Deadlock or timeout. Rollback has been done. -or- 
    SQLCODE -911 the current unit of work has been rolled back due to deadlock or timeout. reason reason-code, type of resource resource-type, and resource name resource-name 
    SQLCODE -913 SQLSTATE 40502 Your program was the victim of a deadlock or timeout. NO rollback has been done.You should do a ROLLBACK. 
    SQLCODE -917 bind package failed 
    SQLCODE -918 the SQL statement cannot be executed because a connection has been lost 
    SQLCODE -919 a rollback operation is required 
    SQLCODE -922 authorization failure: error-type error. reason reason-code 
    SQLCODE -922, error: authorization failure: error. reason 
    SQLCODE -923 connection not established: DB2 condition reason reason-code, type resource-type, name resource-name 
    SQLCODE -924 DB2 connection internal error, function-code, return-code, reason-code 
    SQLCODE -925 commit not valid in ims, cics or rrsaf environment 
    SQLCODE -925, error: commit not valid in ims or cics environment 
    SQLCODE -926 rollback not valid in ims, cics or rrsaf environment 
    SQLCODE -927 the language interface (li) was called when the connecting environment was not established. the program should be invoked under the dsn command 
    SQLCODE -929 failure in a data capture exit: token 
    SQLCODE -939 rollback required due to unrequested rollback of a remote server 
    SQLCODE -947 the SQL statement failed because it will change a table defined with data capture changes, but the data cannot be propagated 
    SQLCODE -948 distributed operation is invalid. Updated Sept 2013 The American Programmer unique ID IEQ735i copyright 2014 TheAmericanProgrammer.com Unauthorized copying prohibited 
    SQLCODE -950 the location name specified in the connect statement is invalid or not listed in the communications database 
    SQLCODE -951 object object-name object type object-type is in use and cannot be the target of the specified alter statement 
    SQLCODE -952 processing was interrupted by a cancel request from a client program 
    SQLCODE -952854 Website copied current URL without authorization. 
    SQLCODE -981 the SQL statement failed because the rrsaf connection is not in a state that allows SQL operations, reason reason-code. 
    SQLCODE -989 after trigger trigger-name attempted to modify a row in table table-name that was modified by an SQL data change statement within a from clause 
    SQLCODE -991 call attach was unable to establish an implicit connect or open to DB2. rc1= rc1 rc2= rc2 
    SQLCODE -992 package package-name cannot be executed or deployed on location location-name 
    SQLCODE ZERO = All OK. No problems. MINUS SQLCODES indicate a severe error. PLUS or positive SQL CODES indicate a less serious error. 
    Compliments of Gabe Gargiulo, author of several recent books on programming and modern languages, available at Amazon.com. 
    Top of Page

    展开全文
  • SQLCODE Function

    2010-08-05 09:40:00
    SQLCODE Function
  • DB2 SQLCODE 大全

    2013-04-11 14:31:00
    DB2 SQLCODE 大全 DB2错误信息 sqlcode sqlstate 说明 000 00000 SQL语句成功完成 01xxx SQL语句成功完成,但是有警告 +012 01545 未限定的列名被解释为一个有相互关系的引用 +098 01568 动态SQL语句用分号结束 +100...
  • sqlcode sqlstate 说明 000 00000 SQL语句成功完成 01xxx SQL语句成功完成,但是有警告 +012 01545 未限定的列名被解释为一个有相互关系的引用 +098 01568 动态SQL语句用分号结束 +100 02000 没有找到满足SQL语句的...
  • DB2 sqlcode说明

    2019-02-10 14:55:24
    sqlcode sqlstate 说明  000 00000 SQL语句成功完成  01xxx SQL语句成功完成,但是有警告  +012 01545 未限定的列名被解释为一个有相互关系的引用  +098 01568 动态SQL语句用分号结束  +100 02000 没有找到满足...
  • db2 sqlcode 说明

    2010-03-24 19:59:17
    关于db2 sqlcode的详细说明,内容非常详细
  • db2 sqlCode大全

    2009-12-27 18:43:59
    db2,sqlCode大全,帮助查询,排错
  • ORACLE SQLCODE

    千次阅读 2012-04-19 10:41:00
    我一般捕捉异常的方式如下: BEGIN ..... EXCEPTION  WHEN OTHERS THEN  ROLLBACK;  ERR1 := SUBSTR(SQLERRM, 1, 100);... TOM_SQLCODE := SQLCODE;  SELECT SYS_CONTEXT('USERENV', 'IP_ADDRESS')
  • DB2 sqlcode

    2019-03-26 01:57:18
    NULL 博文链接:https://holdbelief.iteye.com/blog/1164629
  • DB2 的常见SQLCODE 所表示负数的含义 SQL0007 SQLCODE -07 SQLSTATE 42601 Explanation: Character &1 (HEX &2) not valid in SQL statement. SQL0010 SQLCODE -10 SQLSTATE 42603 Explanation: String constant ...
  • DB2 错误信息 SQLCODE SQLSTATE说明

    千次阅读 2019-04-18 17:17:59
    SQLCODE SQLSTATE 说明 : SQLCODE=+012 , SQLSTATE=01545 未限定的列名被解释为一个有相互关系的引用 SQLCODE=+098 , SQLSTATE=01568 动态SQL语句用分号结束 SQLCODE=+100 , SQLSTATE=02000 没有找到满足SQL语句...
  • DB2 sqlCode错误信息

    千次阅读 2019-06-12 16:50:29
    DB2错误信息(按sqlcode排序)  sqlcode sqlstate 说明  000 00000 SQL语句成功完成  01xxx SQL语句成功完成,但是有警告  +012 01545 未限定的列名被解释为一个有相互关系的引用  +098 01568 动态SQL语句用...
  • DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=1;DB2INST1.LLCLAIM, DRIVER=4.13.127 // 今天遇到的错误,这个是因为db2库 表中有主键重复,插入不进去 ...
  • Oracle SQLCODE

    2012-12-21 11:35:00
    不止一次碰到别人写的Proc的东西,返回一个SQLCODE,然后不知道什么意思。其实也有办法查询的,那些都是ORA-xxxx的错误。  今天找到一个比较简单的查询方法,比如说,你的返回码是-1438,那请在PL/SQL或者SQL PLUS...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 1,661
精华内容 664
关键字:

sqlcode