Error messages

Error messages provide information about problems that have occurred during the operations of the gateway. You can use the information that they contain to resolve such problems.

The following table describes the error messages that the gateway generates:
Table 1. Error messages

Error

Description

Action

Batch creation failed exception

The gateway failed to create a new batch of work in store and forward.

Check the exception text for an indication of the cause of the error. If the cause of the problem is not clear from the error message, contact IBM® Software Support.

Data UUID of recovery file (uuid) does not match uuid

A persistent file has been corrupted.

Persistent files are differentiated by universally unique identifiers (UUID). The UUID is used to name a persistent file and is also embedded in the contents of that file. The error message is indicating that, for a particular persistent file, the embedded UUID does not match the file name UUID. The file has been corrupted.

Locate, and save a copy of, the file named uuid in the $OMNIHOME/var/G_JDBC/ directory. Contact IBM Software Support.

DML type unknown: type

A data manipulation language (DML) command of an unknown type was requested. Inserts, updates, and deletes are the only types supported by the gateway.

Contact IBM Software Support.

Failed to rename file to uuid

The gateway could not write a persistent file named uuid.

Verify that the gateway has write permission for the $OMNIHOME/var/G_JDBC directory.

SQL State is null

A database processing error has occurred and the JDBC driver did not set a valid SQL error state. The gateway cannot determine the cause of the error.

Check the database log for any indication of errors. Check that the database can still be reached. If there are no other obvious error indicators, restart the gateway. If the problem persists, contact IBM Software Support.

JDBC error messages are described in the following topic: