温馨提示！由于新浪微博认证机制调整，您的新浪微博帐号绑定已过期，请重新绑定！&&|&&
LOFTER精选
网易考拉推荐
用微信&&“扫一扫”
将文章分享到朋友圈。
用易信&&“扫一扫”
将文章分享到朋友圈。
阅读(2879)|
用微信&&“扫一扫”
将文章分享到朋友圈。
用易信&&“扫一扫”
将文章分享到朋友圈。
历史上的今天
loftPermalink:'',
id:'fks_',
blogTitle:'[转载]一个不错的简繁转换代码',
blogAbstract:'[转载]一个不错的简繁转换代码',
blogTag:'',
blogUrl:'blog/static/',
isPublished:1,
istop:false,
modifyTime:0,
publishTime:0,
permalink:'blog/static/',
commentCount:0,
mainCommentCount:0,
recommendCount:0,
bsrk:-100,
publisherId:0,
recomBlogHome:false,
currentRecomBlog:false,
attachmentsFileIds:[],
groupInfo:{},
friendstatus:'none',
followstatus:'unFollow',
pubSucc:'',
visitorProvince:'',
visitorCity:'',
visitorNewUser:false,
postAddInfo:{},
mset:'000',
remindgoodnightblog:false,
isBlackVisitor:false,
isShowYodaoAd:false,
hostIntro:'',
selfRecomBlogCount:'0',
lofter_single:''
{list a as x}
{if x.moveFrom=='wap'}
{elseif x.moveFrom=='iphone'}
{elseif x.moveFrom=='android'}
{elseif x.moveFrom=='mobile'}
${a.selfIntro|escape}{if great260}${suplement}{/if}
{list a as x}
推荐过这篇日志的人：
{list a as x}
{if !!b&&b.length>0}
他们还推荐了：
{list b as y}
转载记录：
{list d as x}
{list a as x}
{list a as x}
{list a as x}
{list a as x}
{if x_index>4}{break}{/if}
${fn2(x.publishTime,'yyyy-MM-dd HH:mm:ss')}
{list a as x}
{if !!(blogDetail.preBlogPermalink)}
{if !!(blogDetail.nextBlogPermalink)}
{list a as x}
{if defined('newslist')&&newslist.length>0}
{list newslist as x}
{if x_index>7}{break}{/if}
{list a as x}
{var first_option =}
{list x.voteDetailList as voteToOption}
{if voteToOption==1}
{if first_option==false},{/if}&&“${b[voteToOption_index]}”&&
{if (x.role!="-1") },“我是${c[x.role]}”&&{/if}
&&&&&&&&${fn1(x.voteTime)}
{if x.userName==''}{/if}
网易公司版权所有&&
{list x.l as y}
{if defined('wl')}
{list wl as x}{/list}DB2 Universal Database for iSeries SQL Messages and Codes
SQLSTATE Classes and Codes
DB2 UDB for iSeries returns
to the applications that access it through SQL. SQLSTATE codes
indicate whether the database operation was successfully performed or whether
DB2 returned warnings or errors to the application.
SQLSTATEs can be associated with one or more SQLCODEs.
The tables below provide descriptions of SQLSTATE codes that could be
returned to applications by DB2 UDB for iSeries.
SQLSTATE Value
& SQLCODE Values
Execution of the SQL statement was
successful and did not result in any type of warning or exception
condition.
SQLSTATE Value
& SQLCODE Values
A DISCONNECT error occurred.
Null values were eliminated from the argument of
a column function.
The value of a string was truncated when assigned
to a host variable.
+000, +445, -20141
Insufficient number of entries in an SQLDA.
A privilege was not revoked.
A privilege was not granted.
The query expression of the view is too long for
the information schema.
One or more ad hoc result sets were returned from
the procedure.
The cursor that was closed has been re-opened on
the next result set within the chain.
The procedure returned too many result sets.
+464, +20206
The number of result columns is larger than the
number of host variables provided.
+000, +030
The UPDATE or DELETE statement does not include a
WHERE clause.
+000, +088
The statement was not executed because it is
unacceptable in this environment.
An adjustment was made to a DATE or TIMESTAMP
value to correct an invalid date resulting from an arithmetic operation.
The null value has been assigned to a host
variable, because the non-null value of the column is not within the range of
the host variable.
A character that could not be converted was
replaced with a substitute character.
The null value has been assigned to a host
variable, because a numeric value is out of range.
The null value has been assigned to a host
variable, because the characters cannot be converted.
The local table or view name used in the CREATE
ALIAS statement is undefined.
Isolation level has been escalated.
WHERE NOT NULL is ignored, because the index key
cannot contain null values.
An undefined object name was detected.
The string representation of a datetime value is
+180, +181
An arithmetic operation on a date or timestamp
has a result that is not within the valid range of dates.
During remote bind where existence checking is
deferred, the server-name specified does not match the current server.
Connection is successful but only SBCS characters
should be used.
Authorization ID does not have the privilege to
perform the operation as specified.
The null value has been assigned to a host
variable, because a subs for example, an argument of
SUBSTR is out of range.
An unqualified column name has been interpreted
as a correlated reference.
A mixed data value is improperly formed.
+191, +304, +802
The authorization ID does not have the privilege
to perform the specified operation on the identified object.
Too many host variables have been specified on
SELECT INTO or FETCH.
The null value has been assigned to a host
variable, because division by zero occurred.
The null value has been assigned to a host
variable, because a miscellaneous dat for example, the
character value for the CAST, DECIMAL, FLOAT, or INTEGER scalar function is
a floating-point NAN (not a number) or invalid data in a packed
decimal field was detected.
+304, +420, +802
The table was created but not journaled.
The unit of work was committed or rolled back,
but the outcome is not fully known at all sites.
An ALTER TABLE may cause data truncation.
Insufficient number of entries in an SQLDA for
ALL information (i.e. not enough descriptors to return the distinct name).
The DATALINK value may not be valid because the
table is in reconcile pending or reconcile is not a possible state.
The external program could not be updated with
the associated procedure or function attributes.
The distinct data type name is too long and
cannot be returned in the SQLDA. The short name is returned instead. of
Assignment to SQLCODE or SQLSTATE variable does
not signal a warning or error.
A result sets could not be returned because the
cursor was closed.
A DB2SQL BEFORE trigger changed to DB2ROW.
Valid warning SQLSTATEs returned by a
user-defined function or external procedure CALL.
SQLSTATE Value
& SQLCODE Values
One of the following exceptions
The result of the SELECT INTO statement or the subselect of the INSERT
statement was an empty table.
The number of rows identified in the searched UPDATE or DELETE statement
The position of the cursor referenced in the FETCH statement was after the
last row of the result table.
The fetch orientation is invalid.
No additional result sets returned.
SQLSTATE Value
& SQLCODE Values
The number of host variables is not
the same as the number of parameter markers.
The call parameter list or control block is
The statement identified in the EXECUTE statement
is a select-statement, or is not in a prepared state.
The USING clause is required for dynamic
parameters.
The statement name of the cursor identifies a
prepared statement that cannot be associated with a cursor.
An input host variable, transition variable, or
parameter marker cannot be used, because of its data type.
SQLSTATE Value
& SQLCODE Values
The application requester is unable
to establish the connection.
-30080, -30082, -30089
The connection already exists.
The connection does not exist.
-843, -900
The application server rejected establishment of
the connection.
-30060, -30061
A DISCONNECT is not allowed when the connection
uses an LU6.2 protected conversation.
SQLSTATE Value
& SQLCODE Values
A triggered SQL statement
SQLSTATE Value
& SQLCODE Values
The CONNECT statement is invalid,
because the process is not in the connectable state.
SQLSTATE Value
& SQLCODE Values
The schema name list in a SET PATH
statement is not valid.
SQLSTATE Value
& SQLCODE Values
The locator value does not currently
represent any value.
SQLSTATE Value
& SQLCODE Values
A RESIGNAL was issued but a handler is not active.
SQLSTATE Value
& SQLCODE Values
The case was not found for the CASE
statement.
SQLSTATE Value
& SQLCODE Values
The result of a SELECT INTO is a
result table of more than one row, or the result of the subquery of a basic
predicate is more than one value.
SQLSTATE Value
& SQLCODE Values
Character data, right truncation
for example, an update or insert value is a string that is too long
for the column, or a datetime value cannot be assigned to a host variable,
because it is too small.
-302, -303, -404, -433
A null value, or the absence of an indicator
pa for example, the null value cannot be assigned to a
host variable, because no indicator variable is specified.
A numeric value is out of range.
-302, -304, -406, -446, -802
A null value cannot returned from a procedure
that is defined as PARAMETER STYLE GENERAL or a type-preserving method that is
invoked with a non-null argument.
The fetch orientation is invalid.
An invalid datetime that is,
an invalid string representation or value was specified.
-180, -181
Datetime fie for example, an
arithmetic operation on a date or timestamp has a result that is not within the
valid range of dates.
A subs for example, an
argument of SUBSTR is out of range.
Division by zero is invalid.
The character value for the CAST, DECIMAL, FLOAT,
or INTEGER scalar function is invalid.
The LIKE predicate has an invalid escape
character.
A character is not in the coded character
-330, -331
A parameter or host variable value is
-302, -304, -406, -802
A NUL-terminated input host variable or parameter
did not contain a NUL.
The LIKE predicate string pattern contains an
invalid occurrence of an escape character.
The length control field of a variable length
string is negative or greater than the maximum.
The string representation of a name is
A mixed data value is invalid.
-191, -304, -406, -802
The value for a ROWID or reference column is not valid.
A CCSID value is not valid at all, not valid for
the data type or subtype, or not valid for the encoding scheme.
Character conversion resulted in truncation
SQLSTATE Value
& SQLCODE Values
The update or delete of a parent key
is prevented by a RESTRICT update or delete rule.
-531, -532
An insert or update value is null, but the column
cannot contain null values.
The insert or update value of a foreign key is
The update or delete of a parent key is prevented
by a NO ACTION update or delete rule.
-531, -532
A violation of the constraint imposed by a unique
index or a unique constraint occurred.
A parent row cannot be deleted, because the check
constraint restricts the deletion.
The check constraint cannot be added, because the
table contains rows that do not satisfy the constraint definition.
The resulting row of the INSERT or UPDATE does
not conform to the check constraint definition.
The unique index could not be created or unique
constraint added, because the table contains duplicate values of the specified
The range of values for the identity column or sequence is exhausted.
The foreign key cannot be defined, because all of
its values are not equal to a parent key of the parent table.
SQLSTATE Value
& SQLCODE Values
The identified cursor is not
-501, -507
The cursor identified in an OPEN statement is
already open.
The cursor identified in the UPDATE, DELETE, SET,
or GET statement is not positioned on a row.
The statement identified in the PREPARE is the
statement of an open cursor.
FETCH CURRENT was specified, but the current row
is deleted, or a value of an ORDER BY column of the current row has
FETCH NEXT, PRIOR, CURRENT, or RELATIVE is not
allowed, because the cursor position is not known.
A previous error has disabled this cursor.
SQLSTATE Value
& SQLCODE Values
An update operation is invalid for
the application execution environment.
Update operation not allowed.
The statement is only allowed as the first
statement in a unit of work.
SQLSTATE Value
& SQLCODE Values
The statement identified does not
-514, -516
The statement name specified in a DECLARE CURSOR
already has a cursor allocated to it.
SQLSTATE Value
& SQLCODE Values
An attempt was made to change the
same row in the same table more than once in the same SQL statement.
SQLSTATE Value
& SQLCODE Values
Authorization name is invalid.
-113, -188
SQLSTATE Value
& SQLCODE Values
COMMIT and ROLLBACK are not allowed
in an ATOMIC Compound statement.
Dynamic COMMIT or COMMIT ON RETURN procedure is
invalid for the application execution environment
-30090, -426
Dynamic ROLLBACK is invalid for the application
execution environment.
-30090, -427
SQLSTATE Value
& SQLCODE Values
Connection name is invalid.
-113, -188, -251
SQLSTATE Value
& SQLCODE Values
The external function attempted to
modify data, but the function was not defined as MODIFIES SQL DATA.
The statement is not allowed in a function or
procedure.
The external function attempted to read data, but
the function was not defined as READS SQL DATA.
The function did not execute a RETURN
statement.
SQLSTATE Value
& SQLCODE Values
Cursor name is invalid.
SQLSTATE Value
& SQLCODE Values
Valid error SQLSTATEs returned by a
user-defined function, external procedure, or trigger.
The external routine is not allowed to execute
SQL statements.
The external routine attempted to modify data,
but the routine was not defined as MODIFIES SQL DATA.
The statement is not allowed in a routine.
The external routine attempted to read data, but
the routine was not defined as READS SQL DATA.
Error occurred while calling a user-defined
function, external procedure, or trigger (using the SIMPLE CALL or SIMPLE CALL
WITH NULLS calling convention).
-443, -4302
SQLSTATE Value
& SQLCODE Values
A user-defined function has returned
an invalid SQLSTATE.
A null value is not allowed for an IN or INOUT
argument when using PARAMETER STYLE GENERAL.
-470, -20205
SQLSTATE Value
& SQLCODE Values
The savepoint is not valid.
The maximum number of savepoints has been reached.
A duplicate savepoint name was detected.
A RELEASE or ROLLBACK TO SAVEPOINT was specified, but a savepoint does not exist.
SQLSTATE Value
& SQLCODE Values
The cursor name is ambiguous.
SQLSTATE Value
& SQLCODE Values
The authorization ID does not have
the privilege to perform the specified operation on the identified object.
The authorization ID does not have the privilege
to perform the operation as specified.
Owner authorization failure occurred.
A character, token, or clause is invalid or
-007, -029, -097, -104, -109, -115, -128, -199,
-441, -491
A character that is invalid in a name has been
-113, -251
An unterminated string constant has been
An invalid numeric or string constant has been
-103, -105
The number of arguments specified for a scalar
function is invalid.
An invalid hexadecimal constant has been
An operand of a column function is invalid.
All operands of an operator or predicate are
parameter markers.
A parameter marker is not allowed.
-184, -418
The column or argument definition is
-106, -604
The statement string is an SQL statement that is
not acceptable in the context in which it is presented.
Clauses are mutually exclusive.
A duplicate keyword is invalid.
Invalid options are specified.
The statement string is blank or empty.
A host variable is not allowed.
-090, -312, -5012, -5024
Read-only SCROLL was specified with the UPDATE
The check constraint or generated column
expression is invalid.
A name or label is too long.
A DEFAULT clause cannot be specified.
A CASE expression is invalid.
Parameter names must be specified for SQL
An expression must be specified on a RETURN statement in an SQL function.
A duplicate column name in an INSERT or UPDATE
statement was detected.
A column reference is ambiguous, because of
duplicate names.
An undefined column or parameter name was
-205, -206, -213, -378, -379, -5001
An undefined object or constraint name was
An undefined server-name was detected.
A column name in ORDER BY does not identify a
column of the result table.
A duplicate column name in a PRIMARY, UNIQUE, or
FOREIGN KEY clause was detected.
A duplicate object or constraint name was
-456, -601
A duplicate column name was detected in the
object definition or ALTER TABLE statement.
A duplicate table designator was detected in the
FROM clause. or REFERENCING clause of a CREATE TRIGGER statement.
The local server name is not defined.
A function with the same signature already exists
in the schema.
Unable to access an external program used for a
user-defined function or a procedure.
-444, -4300, -4303, -4304, -4306
A routine was referenced directly (not by either
signature or by specific instance name), but there is more than one specific
instance of that routine.
Duplicate names for common table expressions were
A duplicate schema name in the SET CURRENT PATH
statement was detected.
A procedure with the specified name cannot be
added to the schema because the procedure overloading is not allowed in this
database and there is already a procedure with the same name in the
A duplicate parameter-name was detected.
The label specified on the GOTO, ITERATE, or
LEAVE statement is not found or not valid.
The condition specified in the handler is not
A duplicate column name or unanmed column was
specified in a DECLARE CURSOR statement of a FOR statement.
The number of insert or update values is not the
same as the number of columns.
A column reference in the SELECT or HAVING clause
is invalid, because it is n or a column reference in the
GROUP BY clause is invalid.
-119, -122
The result expressions in a CASE expression are
not compatible.
An integer in the ORDER BY clause does not
identify a column of the result table.
A value cannot be assigned to a host variable,
because the data types are not compatible.
The INSERT, UPDATE, or DELETE is not permitted on
this object.
-150, -155
A column identified in the INSERT or UPDATE
statement is not updateable.
The identified object is not the type of object
to which the statement applies.
-152, -156, -159
A view is identified in a FOREIGN KEY
The number of columns specified is not the same
as the number of columns in the SELECT clause.
A library name is required in CREATE TABLE in the
system naming mode.
WITH CHECK OPTION cannot be used for the
specified view.
The column cannot be dropped, because it is the
only column in the table.
The data type, length, scale, value, or CCSID is
-060, -171, -451, -713, -5005, -846
A datetime value or duration in an expression is
-182, -187
The column cannot be dropped, because RESTRICT
was specified and a view or constraint is dependent on the column.
The operands of an operator or function are not
compatible.
-131, -401
An operand of an arithmetic operation or an
operand of a function that requires a number is not a number.
A numeric constant is too long, or it has a value
that is not within the range of its data type.
-405, -410
A data type for an assignment to a column is not
compatible with the column data type.
An expression in the ORDER BY clause or GROUP BY
clause is not valid.
Multiple columns are returned from a subquery
that only allows one column.
An operand of LIKE is not a string, or the first
operand is not a column.
-132, -414
The rows of UNION, INTERSECT, EXCEPT, or VALUES
do not have compatible columns.
The rows of UNION, INTERSECT, EXCEPT, or VALUES
do not have the same number of columns.
The table identified in the UPDATE or DELETE is
not the same table designated by the cursor.
The table designated by the cursor of the UPDATE
or DELETE statement cannot be modified, or the cursor is read-only.
-510, -520
FOR UPDATE OF is invalid, because the result
table designated by the cursor cannot be modified.
The foreign key does not conform to the
description of the parent key.
The operation is not allowed on system
The qualified object name is inconsistent with
the naming option.
SET NULL cannot be specified, because the foreign
key does not allow null values.
Cyclic references cannot be specified between
named derived tables.
The specification of a recursive, named derived
table is invalid.
The column cannot be altered, because its
attributes are not compatible with the current column attributes.
A parameter marker can not be a user-defined type
or reference type.
A column definition is invalid, because a
specified option is inconsistent with the column description.
An invalid use of a NOT DETERMINISTIC or EXTERNAL
ACTION function was detected.
Cast from source type to target type is not
supported.
An OVRDBF command was issued for one of the
referenced files, but one of the parameters is not valid for SQL.
Isolation level CS WITH KEEP LOCKS is not
A logical file is invalid in CREATE VIEW.
A referenced file is not a table, view, or
physical file.
The privileges specified in GRANT or REVOKE are
invalid or inconsistent. (For example, GRANT ALTER on a view.)
The assignment of the LOB to this host variable
is not allowed. The target host variable for all fetches of this LOB value for
this cursor must be a locator or LOB variable.
A referenced file has more than one format.
Operation cannot be applied to the specified
The CHECK constraint cannot be dropped because it
is enforcing a primary key to be not null.
An extended dynamic statement cannot be executed
against a non-extended dynamic package.
An undefined host variable in REXX has been
The data type in either the RETURNS clause or the
CAST FROM clause in the CREATE FUNCTION statement is not appropriate for the
data type returned from the sourced function or RETURN statement in the
function body.
FETCH statement clauses are incompatible with the
cursor definition.
An invalid number of rows was specified in a
multiple-row FETCH.
ALWCPYDTA(*NO) was specified, but a copy is
necessary to implement the select-statement.
The schema-name portion of a qualified name must
be the same name as the schema name.
Different CCSIDs for keys in CREATE INDEX are
only allowed with a *HEX sort sequence.
The column name cannot be qualified.
An invalid function or procedure name was used
with the EXTERNAL keyword.
The data type of one or more input parameters in
the CREATE FUNCTION statement is not appropriate for the corresponding data
type in the source function.
The CAST TO and CAST FROM data types are
incompatible, or would always result in truncation of a fixed string.
Invalid use of a function.
The specific instance name qualifier is not equal
to the function name qualifier.
No function was found with a matching
signature.
No function or procedure was found with the
specified name and compatible arguments.
The number of input parameters specified on a
CREATE FUNCTION statement does not match the number provided by the function
named in the SOURCE clause.
The IN, OUT, or INOUT parameter attributes do not
The function is not valid in the context where it occurs.
The table does not have a primary key.
The table already has a primary key.
A column list was specified in the references
clause, but the identified parent table does not have a unique constraint with
the specified column names.
A duplicate UNIQUE constraint already
The referential constraint and trigger are not
allowed, because the DELETE rule and trigger event are not compatible.
The object or constraint cannot be dropped or
authoritites cannot be revoked from the object, because other objects are
dependent on it.
-478, -616
The DEFAULT value is invalid.
For static SQL, an input host variable cannot be
used, because its data type is not compatible with the parameter of a procedure
or user-defined function.
The ASP number is invalid.
An invalid correlated reference or transition
table was detected in a trigger.
Correlated references and column names are not
allowed for triggered actions with the FOR EACH STATEMENT clause.
Unable to access a file referenced by a file
reference variable.
The number specified in an SQL statement is out
of the valid range.
The name specified on a rename is not valid.
Only one ROWID or IDENTITY column can be specified for a table.
A ROWID or reference column specification is not valid.
A ROWID or IDENTITY column cannot be specified as the target column of an INSERT or UPDATE.
Unable to access a file referenced by a DATALINK
AS LOCATOR cannot be specified for a non-LOB
parameter.
A cursor specified in a FOR statement cannot be
referenced in an OPEN, CLOSE, or FETCH statement.
The ending label does not match the beginning
UNDO is not allowed for NOT ATOMIC compound
statements.
The condition value is not allowed.
The sqlcode or sqlstate variable declaration is
not valid.
The qualifier for a declared global temporary table name or an index on a declared global temporary
table must be SESSION
An SQL TABLE function must return a table result.
An integer expression must be specified on a RETURN statement in an SQL procedure.
A WHERE, VALUES, GROUP BY, HAVING, or SET clause
includes an invalid reference, such as a column or OLAP function.
The SQL procedure was not created because of a
compile error.
A column function in a subquery of a HAVING
clause includes an expression that applies an operator to a correlated
reference.
The string is too long.
The statement does not include a required column
CREATE VIEW includes an operator or operand that
is not valid for views. For example, UNION or UNION ALL.
The statement is not allowed in an ATOMIC
Compound statement.
A decimal divide operation is invalid, because
the result would have a negative scale.
A column cannot be updated, because it is not
identified in the UPDATE clause of the select-statement of the cursor.
The DELETE is invalid, because a table referenced
in a subquery can be affected by the operation.
The object cannot be explicitly dropped.
A user-defined data type cannot be created with a
system-defined data type name (for example, INTEGER).
Nested compound statements are not allowed.
DROP SCHEMA cannot be executed under commitment
Program or package must be recreated to reference
an alias-name.
An alias resolved to another alias rather than a
table or view at the remote location.
Locators are not allowed with COMMIT(*NONE).
The same column was identified in FOR UPDATE OF
and ORDER BY.
The program preparation assumptions are
incorrect.
The parameter must not have a subtype of
The object cannot be created, because the
specified identifier is reserved for system use.
-457, -707
The authorization ID cannot be both an owner and
primary group owner.
The server name specified does not match the
current server.
A long column, LOB column, structured type column
or datalink column cannot be used in an index, a key, or a constraint.
The connection failed, because there is no
current software license.
The package was not created and the current unit
of work was rolled back, because of internal limitations or an invalid section
COMMIT HOLD or ROLLBACK HOLD is not allowed to a
non-sql400. application server.
SQL statements cannot be executed under
commitment control, because DFM is already active under commitment control to
another system.
An expression in a join-condition references
columns in more than one of the operand tables.
The authorization ID cannot be changed when
connecting to the local server.
An indicator variable is not a small
CREATE SCHEMA is not allowed if changes are
pending in the unit of work.
The privilege cannot be granted to the view,
because *OBJOPR or *OBJMGT authority exists on a dependent view or table, and
the grantee does not have *ALLOBJ or the specified privilege on the dependent
table or view.
The statement is not allowed in a routine.
-577, -579, -751
The statement is not allowed in a trigger.
A unique index or unique constraint is not
allowed because the key columns are not a superset of the partitioned key
The requested function does not apply to global temporary tables.
The partition key cannot be a datatime or
floating-point column.
A referential constraint is not allowed because
the foreign key columns are not a superset of the partitioned key columns or
the node group is not the same as the parent table.
Rows from a distributed table cannot be
redistributed because the table contains a datalink column with FILE LINK
A referential constraint with a delete rule of
CASCADE is not allowed on a table with a DataLink column with FILE LINK
RETURN must be the last SQL statement of the atomic compound statement within an SQL row or table
SQLSTATE Value
& SQLCODE Values
The INSERT or UPDATE is not allowed,
because a resulting row does not satisfy the view definition.
SQLSTATE Value
& SQLCODE Values
The URL specified on an install or
replace of a jar procedure did not identify a valid jar file.
The jar name specified on the install, replace,
or remove of a java procedure is not valid.
The jar file cannot be removed, a class is in use
by a procedure.
A Java function has a Java method with an invalid
signature.
A Java function could not map to a single Java
The install or remove jar procedure for
&&jar-id&& specified the use of a deployment descriptor.
SQLSTATE Value
& SQLCODE Values
The package corresponding to an SQL
statement execution request was not found.
Consistency tokens do not match.
An address in the SQLDA is invalid.
COMMIT or ROLLBACK is not allowed, because
commitment control has not been started.
An attempt was made to execute a section that was
found to be in error at bind time.
SQL statements cannot be executed until the
application process executes a rollback operation.
An implicit connect to a remote server is not allowed because a savepoint is outstanding.
The operation is not allowed because a trigger
has been marked inoperative.
SQLSTATE Value
& SQLCODE Values
The statement is too long or too
A string constant is too long.
The statement has too many table names or too
many items in a SELECT or INSERT list.
-129, -840
The sort key is too long, or has too many
The result of concatenation is too long.
The key is too long, a column of the key is too
long, or the key many columns.
-602, -613, -614, -631
Too many users were specified in GRANT or
The record length of the table is too long.
Too many columns were specified for a table or
-101, -680
The row is too long.
The maximum number of late descriptors has been
exceeded, probably because too many different CCSIDs were used.
Too many constraints, or the size of the
constraint is too large.
The limit for the number of parameters or
arguments for a function or a procedure has been exceeded.
-442, -448
The maximum number of concurrent LOB handles has
been reached.
An internal object limit exceeded.
Maximum depth of nested functions, procedures, or
triggers was exceeded.
A multiple-byte (UCS-2) sort sequence table
cannot be supprted in DRDATM because it is too large.
SQLSTATE Value
& SQLCODE Values
Recursion is not supported to a
non-sql400. application server.
The object cannot be dropped, because it is
currently in use by the same application process.
-615, -950
The object cannot be altered, because it is
currently in use by the same application process.
The schema cannot be dropped, because it is in
the library list.
The table is in an invalid state for the
operation.
Local program attempted to connect to a remote
The alias is not allowed because it identifies a
single member of a multiple member file.
An object cannot be created into a protected schema.
SQLSTATE Value
& SQLCODE Values
An unsupported SQLTYPE was
encountered in a select-list or input-list.
-351, -352
A bind option is invalid.
SQLSTATE Value
& SQLCODE Values
The statement cannot be executed,
because a utility or a governor time limit was exceeded.
The object cannot be created, because a DROP or
CREATE is pending.
The object cannot be used, because a DROP or
ALTER is pending.
Virtual storage or database resource is not available.
-904, -971, -7053
A non-database resource is not available. This
will not affect the successful execution of subsequent statements.
A non-database resource is not available. This
will affect the successful execution of subsequent statements.
Processing was canceled as requested.
Character conversion is not defined.
Deadlock or timeout occurred without automatic
DDM recursion has occurred.
A local SQL application program cannot be
executed on an application server.
The file server is not currently available.
SQLSTATE Value
& SQLCODE Values
An invalid section number was
A system error (that does not necessarily
preclude the successful execution of subsequent SQL statements) occurred.
SQLSTATE 58004, when combined with SQLCODE -4301, indicates this meaning for
the failure: Java interpreter startup or communication failed.
-901, -4301
Execution failed due to a distribution protocol
error that will not affect the successful execution of subsequent DDM commands
or SQL statements.
Execution failed due to a distribution protocol
error that caused deallocation of the conversation.
Execution failed due to a distribution protocol
error that will affect the successful execution of subsequent DDM commands or
SQL statements.
The DDM command is invalid while the bind process
in progress.
The bind process with the specified package name
and consistency token is not active.
The DDM command is not supported.
The DDM object is not supported.
The DDM parameter is not supported.
The DDM parameter value is not supported.
The DDM reply message is not supported.
The commit operation failed, because a resource
in the unit of work was not able to commit its resources.
An unexpected error occurred while attempting to
access a client driver.
| Table of Contents ]}