Cause | Invalid protocol. |
Action | Verify that the protocol is valid and that the message transmission sequence is correct. |
Cause | Failed to login. |
Action | Verify that the user ID and password are correct. |
Cause | Failed to execute the SQL statement. |
Action | Check that the statement is correct. |
Cause | Failed to login. |
Action | Check to see if there are any errors in the authentication gateway. |
Cause | Failed to open the cursor in the gateway. |
Action | Contact the technical support team. |
Cause | Invalid cursor. |
Action | Contact the technical support team. |
Cause | Fetch failed. |
Action | Contact the technical support team. |
Cause | The message was received from a database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | The target database system connected to the gateway has successfully completed the function. |
Action | Check the message received from the target database system. |
Cause | The target database system connected to the gateway completed the function with a warning message. |
Action | Check the message received from the target database system. |
Cause | Cursor operation conflict occurred within the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Failed to disconnect from the target database system which is connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | NULL values have been eliminated from a set function in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | String data right truncation occurred in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | There are too few item descriptor areas for the result set or gateway. |
Action | Check the message received from the target database system. |
Cause | Failed to revoke the privilege in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Failed to grant the privilege in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Implicit zero-bit padding in the target DB system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | The search condition for schema information is too long in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | The query expression for schema information is too long in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | There is no data satisfying the condition in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Failed to execute the dynamic SQL statement in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | The dynamic SQL statement to be executed in the target parameter does not match parameter specification. |
Action | Check the message received from the target database system. |
Cause | The cursor specification cannot be executed in the dynamic gateway. |
Action | Check the message received from the target database system. |
Cause | A USING clause is required for a dynamic SQL statement in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | A prepared statement which does not have a cursor in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Data type error has occurred in a dynamic SQL statement in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | A USING clause must be used to receive the resulting data from a gateway. |
Action | Check the message received from the target database system. |
Cause | The number of descriptors shown in the dynamic SQL statement is invalid. |
Action | Check the message received from the target database system. |
Cause | Invalid descriptor index in the dynamic SQL statement of the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An exception has occurred in a connection with the target database system. |
Action | Check the message received from the target database system. |
Cause | Failed to connect to the target database system. |
Action | Check the message received from the target database system. |
Cause | The name of the connection with the target database system is already in use. |
Action | Check the message received from the target database system. |
Cause | A connection to the target database system does not exist. |
Action | Check the message received from the target database system. |
Cause | Connection to the target database system has been rejected. |
Action | Check the message received from the target database system. |
Cause | Failed to connect with the target database system. |
Action | Check the message received from the target database system. |
Cause | Unknown transaction in the target database system. |
Action | Check the message received from the target database system. |
Cause | Feature is not provided by the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | In the target database system connected to the gateway, the sub query contains more than two records. |
Action | Check the message received from the target database system. |
Cause | A data error occurred in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Right truncation of string data occurred in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | There is no parameter indicator in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Some numeric data to be expressed in the target database system connected to the gateway is out of range. |
Action | Check the message received from the target database system. |
Cause | The data was not assigned in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Invalid date or time format in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | A date or time data overflow problem occurred in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Invalid time zone setting in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An error occurred while extracting a substring in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An attempt was made to divide by zero in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An INTERVAL data overflow problem occurred in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid character value for case was used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid escape character was used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Invalid character data was used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An indicator overflow problem occurred in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid parameter value was used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An unterminated C string was used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid escape sequence was used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Mismatched string data length in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Failed to trim the character string in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Some data in the target database connected to the gateway violates integrity constraints. |
Action | Check the message received from the target database system. |
Cause | An invalid cursor state exists in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid transaction state exists in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid statement name exists in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Invalid use of trigger in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid authorization specification exists in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Dependent privilege descriptors still exist in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | The specified character set is not supported in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid transaction termination occurred in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid connection name has been used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid SQL descriptor has been used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid cursor name has been used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid condition number has been used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An ambiguous cursor name has been used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid catalog name has been used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An invalid schema name has been used in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | A transaction rollback error has occurred in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | A serialization failure between transactions has occurred in the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | A transaction of the target database system connected to the gateway violated integrity constraints. |
Action | Check the message received from the target database system. |
Cause | The termination of a transaction in the target database system connected to the gateway has not yet been confirmed. |
Action | Check the message received from the target database system. |
Cause | In the target database system connected to the gateway, bad syntax was used, or an invalid object was accessed. |
Action | Check the message received from the target database system. |
Cause | An invalid use of the WITH CHECK option occurred in a view of the target database system connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An Oracle system error has occurred. |
Action | Check the message received from the target database system. |
Cause | An error occurred in the Oracle resources connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An error has occurred in the Oracle server or process connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An error has occurred in the Oracle XA protocol or the two-task interface connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An error has occurred in the Oracle control file or database file during archive or media recovery. |
Action | Check the message received from the target database system. |
Cause | An error has occurred while executing Oracle PL/SQL connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An error has occurred in the Oracle SQL*Net driver connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | A problem occurred in the license of the Oracle database connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | An error occurred in Oracle SQL*Connect. |
Action | Check the message received from the target database system. |
Cause | An error has occurred while executing an SQL statement in the Oracle database connected to the gateway. |
Action | Check the message received from the target database system. |
Cause | Invalid data type in the target database table. |
Action | Check to see if LONG, CLOB or BLOB types exist in the table. |
Cause | Failed to execute 'prepare' in the target database. |
Action | Check if there are any SQL syntax errors. |
Cause | Failed to start a global transaction for the target database. |
Action | Check the error message from the target database system. |
Cause | Target database system has failed to prepare a global transaction. |
Action | Check the error message from the target database system. |
Cause | Target database system has failed to commit a global transaction. |
Action | Check the error message from the target database system. |
Cause | Target database system has failed to rollback a global transaction. |
Action | Check the error message from the target database system. |
Cause | Failed to execute the statement. |
Action | Check if the statement is correct. |
Cause | Failed to execute the statement. |
Action | Check if the statement is correct. |
Cause | Another connection was requested while connecting with server. |
Action | Check the connection with the gateway. |
Cause | Failed to start a gateway process. |
Action | Ensure gateway process execution is permitted (e.g. permissions). |
Cause | The target database system connected to the gateway has successfully completed the function. |
Action | Check the message received from the target database system. |
Cause | The target database failed to allocate the top-level handle. |
Action | Check if the environmental variables required in the target database system are configured properly. |