Lists the Engine error messages from X350 through X399.
Restriction: This topic applies to Windows environments only.
X352: Server violation. The server experienced a protection exception while processing a user's command. The exception handling code has rolled back
the user's current transaction and logged the user out.
X355: Error connecting to remote server(name). An error has occurred while trying to connect to server name. Make sure you have enough remote engine threads and that the server-to-server connectivity setup is correct in your system
catalogs.
X356: Error sending to remote server(name). An error has occurred while trying to send to server name. Make sure you have enough remote engine threads and that the server-to-server connectivity setup is correct in your system
catalogs.
X357: Error receiving from remote server(name). An error has occurred while trying to receive from server name. Make sure you have enough remote engine threads and that the server-to-server connectivity setup is correct in your system
catalogs.
X358: Governor limit exceeded. One of the governor limits has been exceeded, and the server logged out the user. You could increase the governor limit for
that user. The governor will be active only if the server security is ON.
X361: No remote thread available to process request. A client has tried to connect to a remote server and the primary server does not have any thread available to handle the request.
In these cases, there are no remote threads set for the primary server, or all the remote threads are already in use.
X362: Index error during recovery. While XDB Server was recovering a location, a fatal error occurred. You must compact and re-index the location immediately.
Do not use the location until the compact and re-index has finished.
X365: Log path cannot be set to path. The logging system cannot set the log to the path specified. Ensure that the path exists, and that there are no other logs
present in the path.
X368: Illegal string string found. XDB Server received a different string than it expected. For example: SET CURRENT RULES <parm> must be either DB2 or STD.
Using a different parameter will return an x368.
X389: Illegal operation on temporary table The current operation is not allowed on a temporary table. Temporary tables are not allowed to have primary/unique keys,
or to be referenced by foreign keys. Also, update/delete operations on records in temporary tables are not allowed.
X393: Output host variable PositionNumber is incompatible with the query result. The XDB Server is not able to return the result of a CALL, FETCH, or SELECT statement because the data type of the variable
at PositionNumber in the output SQLDA (to which the result was to be written) does not match the data type of the result.
X394: Input host variable PositionNumber is incompatible with the current query. The XDB Server is not able to execute the requested SELECT statement because it contains a host variable whose data type is
not correct. (For example, the WHERE clause may be using a numeric host variable to select from a DATE field in the database.)
The host variable causing the problem is located at PositionNumber in the input SQLDA.