Micro Focus Enterprise Developer 3.0 for Visual Studio 2013 > Programming > Mainframe Programming > SQL Option for DB2 > Reference > Error Messages > X - Engine Error Messages > X050 - X099

X050 - X099

Lists the Engine error messages from X050 through X099.

X051: Duplicate key value when creating unique index indexname.
Unable to create unique index because a value appears more than once in the column(s).
X052: Cannot update field to incompatible type.
An attempt was made to update a field using an incompatible value. Check the field types of the table you are updating.
X053: String length is larger than field length.
An attempt was made to insert a character string into a field too short to hold it. Check to see if you are using DB2 compatibility.
X054: Unequal number of fields and values.
When inserting a record, an attempt was made to insert more values than the table has fields. If you supply too few values, the system automatically places NULL values in the other fields.
X055: Duplicate names name in insert/alter/create list.
A field name appears more than once in an INSERT, ALTER, or CREATE command.
X056: Table/View name already exists.
All tables and views in a database must have unique names. To obtain a list of the tables or views in a database, you can perform the query:
X057: Specified more fields or values than the table has.
The number of values listed in an INSERT command exceeds the number of fields in the table named.
X058: Field name type incompatible with type type.
Unable to perform a command because the type of the field named is incompatible with the type displayed (e.g. a time field is incompatible with a date field for comparison operations).
X059: Inserting character constant larger than field length specified.
A character string in an INSERT command values list is longer than the target character field. Value is truncated.
X060: value is outside allowable field length boundary.
See the SQL Reference for description of data type ranges.
X061: number is greater than maximum allowable number of fields.
Tables are limited to 750 fields.
X062: Value value is too large to insert into field name.
Unable to insert the value into the field specified, because it is larger or longer than maximum value permitted.
X063: Index name not found.
Reference was made to an index not found in the current database. For a list of the currently active indices in the current database, execute the query:
X064: Not a proper command or command not implemented.
An attempt was made to execute a command that is not a valid XDB Server or SQL command, or to execute a command that is not yet implemented.
X065: Illegal field name name in order specification.
A field or column in an ORDER BY clause was not selected in the SELECT clause of the query, or does not exist in the table.
X066: Illegal number number in order/group specification.
There is no matching column number for a column number listed in the ORDER BY or GROUP BY clause of the query.
X067: Aggregates not allowed in WHERE clause of query.
XDB Server does not permit an aggregate function in the WHERE clause of a query. Aggregate functions should appear in a HAVING clause if used as a selection criterion.
X068: Selecting an expression with a GROUP BY clause.
XDB Server does not permit use of expressions (other than aggregate functions) in a query having a GROUP BY clause unless you include the expression in the GROUP BY clause using its column number.
X069: Too many set clauses in update command.
There are more SET clauses in the UPDATE command than there are fields in the table being updated.
X070: Ordering by field name that is not selected.
In DB2 mode, the ORDER BY clause must specify one of the fields in the SELECT clause.
X071: Selecting more than one item in a nested query.
The SELECT clause of a subquery can consist of only one column. If you want to select more than one field, try concatenating the fields using the XCONCAT function.
X072: Cannot nest aggregate functions.
Aggregate functions cannot be nested one inside the other. For example, you cannot select:
X073: Fields selected must appear in GROUP BY clause or inside an aggregate function.
If a query selects an aggregate function, any field appearing outside the aggregate function in the SELECT clause must also appear in the GROUP BY clause of the query. This is a common cause of confusion; although users may think they do not want to group a result by a particular column, they often find that adding the column name to the end of the GROUP BY clause yields the desired result.
X074: GROUP BY clause invalid on current query.
A GROUP BY clause can only be used if the SELECT clause of the query includes one or more column names, or one or more aggregate functions (such as COUNT, and AVG.)
X075: Cannot mix fields with aggregates without GROUP BY.
If a query selects an aggregate function, any field appearing outside the aggregate function in the SELECT clause must also appear in a GROUP BY clause.
X076: Luname servername does not exist in tablename SYSLUNAMES table.
You are inbound/outbound mapping to or from a server name that does not exist in SYSLUNAMES. Insert a record for that server name in the SYSLUNAMES table or insert a dummy generic record with blanks.
X077: Cannot include join in table expansion.
PREVIOUS clause cannot be used on a join.
X078: Illegal level value for table expansion.
LEVEL clause specifies a non-positive or non-integer level, or a level beyond the maximum recursive relationship level.
X079: Insert/Delete/Update function not allowed on sorted query.
You cannot perform a positioned update/insert/delete on a query that requires sorting. Queries that may require sorting are those involving ORDER BY, GROUP BY, DISTINCT, and UNION.
X080: Only one DISTINCT clause allowed per query.
XDB Server only allows one DISTINCT clause per query. For example, you cannot:
X081: Exceeds maximum number of UNIONed queries.
A maximum of 32 subselects may be connected by the UNION operator (i.e. UNION should appear no more than 31 times in a command).
X082: Each query in a UNION must have the same number of projected fields.
The number and type of columns selected in subselects connected with the UNION operator must match exactly.
X083: Data types in column name do not match.
When performing a UNION, the data types of each column in one subselect must be type compatible with the corresponding column in all UNIONed subselects.
X084: ORDER BY items must be constants for union of queries.
When the UNION operator and the ORDER BY clause appear in the same query, the ORDER BY criteria must use column numbers instead of column names.
X085: ORDER BY must follow all queries when performing a union.
The ORDER BY clause should be the last clause in any query containing a UNION operator.
X086: NULL not allowed in field name.
An illegal attempt was made to place a NULL in the field named. The field is specified as NOT NULL. You can obtain information on NULL permission from the SYSCOLUMNS table.
X087: Table/View name exceeds maximum length of number.
Table, view and synonym names are limited to the number of characters shown. Some compatibility modes allow longer table names than others.
X088: Field name length exceeds maximum length of number characters.
Table names are limited to the number of characters shown. Some compatibility modes allow longer field names than others.
X089: Cannot open location on path. Check location path setting.
The system is unable to find or open the location-name.DDT or location-name.DDF files on the path specified. These files contain essential information on location table and field specifications. Check whether there is a location in the path specified. Check whether there is more than one set of .DDT or .DDF files in your location directory. Check to see if the location name matches the location name in the SYSXDB.SYSLOCALS table. Verify whether the path is accessible by the program accessing the location. For example, in multi-user, use the drive specifier.
X090: Too many users registered.
The number of users registered is equal to the maximum number of users permitted to register at one time.
X091: User has no privilege privilege on objectname.
The current user has not been granted the privilege to perform the operation attempted on the table, view or database shown. For a listing of privileges available to a user, query the SYSTABAUTH and SYSDBAUTH tables.
X092: User account has been disabled.
The user name has been deactivated. See your database administrator, who can enable the user account.
X093: Unknown user name.
The user name entered is not found in the system, because it has not been registered on the system. See your database administrator. Query the SYSXDB.SYSACFUSERS table in the system location for a list of valid user names.
X094: User userid cannot GRANT/REVOKE on table/view/database name.
User has no authority to grant or revoke privileges on the database, table or view named. For a list of privileges available to a user, query the SYSTABAUTH and SYSDBAUTH tables.
X095: Invalid receipt. (Should register first.)
User did not obtain a valid process ID before entering a module. Exit to the operating system and try reentering the program. In extreme cases you may need to unload the SQL Engine, or in multi-user environments, kill a user session.
X096: Illegal password.
Password does not match password saved for the user name entered. Repeated attempts to log on with an incorrect password will cause this program to abort. If you have forgotten your password, see your database administrator.
X097: Illegal attempt to open more than one location.
XDB Server permits a user to access only one location at a time. This error condition occurs when a programmer attempts to call the C API Xdbxopen() function before closing the current location.
X098: Cannot grant a privilege to yourself.
A user is not permitted to grant a privilege to him/herself. The privilege must be granted by another user possessing sufficient authority to do so.
X099: User already exists.
A user with the same user name is already entered in the SYSXDB.SYSACFUSERS table. User names must be unique.

Parent topic: X - Engine Error Messages