JDBC Type 4 Driver Programmer's Reference for SQL/MX Release 3.2.1

Recovery: Use the getCause method on the Exception to determine the appropriate recovery
action.
nl
29116 HY000 Socket is closed.
Cause: Socket close error.
Effect: The operation fails.
Recovery: Evaluate the returned value from the getCause method on the Exception to determine
the appropriate recovery action.
nl
29117 HY000 Error while closing session. Cause: cause
Cause: An error was encountered while closing a session.
Effect: The operation fails.
Recovery: Evaluate the returned value from the getCause method on the Exception to determine
the appropriate recovery action.
nl
29118 HY000 A write to a bad map pointer occurred.
Cause: Internal error.
Effect: Operation fails.
Recovery: None. Report the entire message to your service provider.
nl
29119 HY000 A write to a bad par pointer occurred.
Cause: Internal error.
Effect: Operation fails.
Recovery: None. Report the entire message to your service provider.
nl
29120 HY000 An association server connect message error occurred.
Cause: Unable to connect to the MXCS association server.
Effect: Operation fails.
Recovery: Evaluate the returned value from the getCause method on the Exception to determine
the appropriate recovery action.
nl
29121 HY000 A close message error occurred. Cause: cause
Cause: Unable to perform this operation.
Effect: Operation fails.
Recovery: Evaluate the returned value from the getCause method on the Exception to determine
the appropriate recovery action.
nl
29122 HY000 An end transaction message error occurred.
Cause: Unable to perform the operation.
Effect: Operation fails.
Recovery: Evaluate the returned value from the getCause method on the Exception to determine
the appropriate recovery action.
nl
29123 HY000 An execute call message error occurred. Cause: cause
Cause: Unable to perform this operation.
96 Messages