D:>db2 ? sql204
SQL0204N "<name>" is an undefined name.
This error is caused by one of the following:
o The object identified by "<name>" is not defined in the
o A data type is being used. This error can occur for the
- If "<name>" is qualified, then a data type with this name
does not exist in the database.
- If "<name>" is unqualified, then the user's function path
does not contain the schema to which the desired data type
- The data type does not exist in the database with a create
timestamp earlier than the time the package was bound
(applies to static statements).
- If the data type is in the UNDER clause of a CREATE TYPE
statement, the type name may be the same as the type
being defined, which is not valid.
o A function is being referenced in one of:
- a DROP FUNCTION statement
- a COMMENT ON FUNCTION statement
- the SOURCE clause of a CREATE FUNCTION statement
If "<name>" is qualified, then the function does not
exist. If "<name>" is unqualified, then a function of
this name does not exist in any schema of the current function
path. Note that a function cannot be sourced on the COALESCE,
NULLIF, or VALUE built-in functions.
This return code can be generated for any type of database
Federated system users: the object identified by "<name>" is not
defined in the database or "<name>" is not a nickname in a DROP
Some data sources do not provide the appropriate values for
"<name>". In these cases, the message token will have the
following format: "OBJECT:<data source> TABLE/VIEW", indicating
that the actual value for the specified data source is unknown.
The statement cannot be processed.
Ensure that the object name (including any required qualifiers)
is correctly specified in the SQL statement and it exists. For
missing data type or function in SOURCE clause, it may be that
the object does not exist, OR it may be that the object does
exist in some schema, but the schema is not present in your
Federated system users: if the statement is DROP NICKNAME, make
sure the object is actually a nickname. The object might not
exist in the federated database or at the data source. Verify
the existence of the federated database objects (if any) and the
data source objects (if any).
sqlcode : -204
sqlstate : 42704
"It does not work" is not a valid problem statement.