Cause | The function has concluded successfully but with warnings or additional information related to the results. |
Action | Check the warnings and additional information with the GetDiagField() function. |
Cause | DSN file could not be found. |
Action | Check the dsn file in the 'client/config' directory under the database home directory. |
Cause | DSN file is corrupted. |
Action | Check the dsn file in the 'client/config' directory under the database home directory. |
Cause | DSN file format is invalid. |
Action | Check the dsn file in the 'client/config' directory under the database home directory. |
Cause | The user name is too long. User names may not be longer than 128 bytes. |
Action | Check the size of the user name in the argument. |
Cause | The password is too long. Passwords may not be longer than 63 bytes. |
Action | Check the size of the password in the argument. |
Cause | The table name is too long. Table names may not be longer than 128 bytes. |
Action | Check the size of the table name in the argument. |
Cause | The column name is too long. Column names may not be longer than 127 bytes. |
Action | Check the size of the column name in the argument. |
Cause | The schema name is too long. Schema names may not be longer than 127 bytes. |
Action | Check the size of the schema name in the parameter. |
Cause | Actual data is larger than the buffer. |
Action | Check the size of the data buffer. |
Cause | Invalid parameter number. |
Action | Check the parameter number. |
Cause | The prepared statement does not provide a valid cursor specification. |
Action | Verify the statement is a SELECT statement. |
Cause | Invalid column index. |
Action | Check the descriptor column index. |
Cause | Invalid record index. |
Action | Check the descriptor record index. |
Cause | Cannot connect to the server. |
Action | Verify that the server is running, and check the DB connection settings. |
Cause | Server or session handle is not registered as an attribute of OCISvcCtx. |
Action | Verify that the OCISvcCtx handle is correctly created. |
Cause | Already connected to the server. |
Action | Disconnect the server and retry, or continue with desired actions. |
Cause | Not connected to the server. |
Action | Reconnect to the server and try action again. |
Cause | The SQL_C type is not supported. |
Action | Check the SQL_C type and change it. |
Cause | Unsupported SQL data type. |
Action | Check the SQL data type and change it. |
Cause | SQL statement has not been prepared. |
Action | Execute when SQL statement is prepared. |
Cause | Invalid null pointer was used. |
Action | Check the null pointer. |
Cause | Invalid argument type. |
Action | Check the argument type. |
Cause | Invalid argument value. |
Action | Check the argument value. |
Cause | Invalid function sequence. |
Action | Check the sequence of functions. |
Cause | Failed to set attributes. |
Action | Check the attributes. |
Cause | Invalid transaction operation. |
Action | Check whether the current transaction operation is valid. |
Cause | Cannot modify IRD (Implementation Row Descriptor). |
Action | Check the target descriptor type to modify. |
Cause | Invalid use of an automatically allocated descriptor handle. |
Action | Create a new descriptor handle. |
Cause | Invalid descriptor information. |
Action | Check the binding descriptor. |
Cause | Invalid attribute value. |
Action | Confirm that the value can be specified for the current attribute. |
Cause | Invalid length of character string. |
Action | Change the length of the string. |
Cause | The descriptor field identifier is undefined or not implemented. |
Action | Check the descriptor field identifier. |
Cause | The specified descriptor field is read-only. |
Action | Check the attributes of the descriptor field. |
Cause | Invalid attribute or option. |
Action | Recheck the attribute or option. |
Cause | Invalid parameter index. |
Action | Check the parameter index. |
Cause | Invalid parameter type. |
Action | Check the parameter type. |
Cause | Invalid cursor position. |
Action | Verify that the cursor position is correct. |
Cause | The function has not yet been implemented. |
Action | Use an alternative function. |
Cause | Invalid cursor state. |
Action | Check the cursor state. |
Cause | No indicator has been specified. |
Action | Specify the indicator. |
Cause | Invalid name for the savepoint. |
Action | Check the name of the savepoint. |
Cause | Duplicate cursor name detected. |
Action | Change the cursor name. |
Cause | Invalid cursor name |
Action | Change the cursor name. |
Cause | Invalid diagnostics record index |
Action | Check the diagnostics record index. |
Cause | The function has not been implemented. |
Action | Use an alternative function. |
Cause | The attribute has not been implemented. |
Action | Use an alternative attribute. |
Cause | Unable to find DSN. |
Action | Check whether DSN configuration is valid. |
Cause | Invalid offset value for large object (LOB). |
Action | Check the offset value of LOB. |
Cause | Invalid LOB length |
Action | Check the LOB length. |
Cause | Not authorized to perform this task. |
Action | Check the user name and password. |
Cause | Invalid environment parameter type. |
Action | Check the environment parameter type. |
Cause | Invalid plan was executed. |
Action | Check whether the plan ID is valid. |
Cause | The cursor is already open. |
Action | Check the cursor state. |
Cause | Cursor is not open. |
Action | Check the cursor state. |
Cause | Executed SQL statement is NULL. |
Action | Check the SQL statement again. |
Cause | Invalid scrollable cursor fetch. |
Action | Check whether the cursor type is scrollable. |
Cause | Data type is unsupported by server. |
Action | Check the data type again. |
Cause | Exceeds the maximum data length supported by server. |
Action | Check the data length. |
Cause | Invalid diagnostics index |
Action | Check the diagnostics index. |
Cause | Data type is currently unsupported. |
Action | Use an alternative data type. |
Cause | Unable to change the data type. |
Action | Check the data type. |
Cause | Invalid parameter mode. |
Action | Check the parameter mode. |
Cause | There is no NULL at the end of string bind value. |
Action | Check the bind value. |
Cause | Data was too long and was truncated. |
Action | Check the data length. |
Cause | Index value was out of range. |
Action | Check the index. |
Cause | Invalid indicator type. |
Action | Check the indicator type. |
Cause | There is a problem reading from the server. |
Action | Check the connection. |
Cause | There is a problem writing to the server. |
Action | Check the connection. |
Cause | There is a problem closing the communication with server. |
Action | Check the connection. |
Cause | Invalid buffer length. |
Action | Check the buffer length. |
Cause | Invalid handle. |
Action | Check whether the handle is valid. |
Cause | Invalid handle type. |
Action | Check whether or not the handle type is valid. |
Cause | Invalid connection handle. |
Action | Check the connection handle. |
Cause | Invalid statement handle. |
Action | Check the statement handle. |
Cause | Failed to initialize the handle manager. |
Action | Check the handle allocation. |
Cause | CLI Driver manager has not been initialized. |
Action | Initialize the CLI Driver Manager. |
Cause | The specified fetch location is before the first record of the result set. |
Action | Specify a valid fetch location. |
Cause | Invalid socket file descriptor. |
Action | Check the connection with the server. |
Cause | Failed to close socket. |
Action | Verify the connection with the server is still available. |
Cause | Invalid server connection protocol. |
Action | Check the condition of the server and clients. |
Cause | Invalid LOB locator received from server. |
Action | Check the LOB locator. |
Cause | No data. |
Action | Check the fetch state. |
Cause | The server requires some data. |
Action | Ensure the data to be sent is available. |
Cause | Failed to connect to server. |
Action | Check the server state. |
Cause | Failed to disconnect. |
Action | Check the server state. |
Cause | Failed to execute SQL statements. |
Action | Recheck the SQL statements. |
Cause | Failed to fetch. |
Action | Check the cursor state. |
Cause | Failed to prepare a statement. |
Action | Check the execution statement. |
Cause | Failed to close the cursor. |
Action | Check the cursor state. |
Cause | Failed to commit. |
Action | Check the transaction state. |
Cause | Failed to close the session. |
Action | Check the server state. |
Cause | Failed to end the session. |
Action | Check the server state. |
Cause | Failed to roll back. |
Action | Check the transaction state. |
Cause | Failed to set a savepoint. |
Action | Check the transaction state. |
Cause | Failed to transfer the data. |
Action | Verify the data is valid. |
Cause | Failed to cancel. |
Action | Check the transaction state. |
Cause | Failed to obtain the LOB type length. |
Action | Check the LOB locator. |
Cause | Failed to read LOB data. |
Action | Check the LOB locator. |
Cause | Failed to write LOB data. |
Action | Check the LOB locator. |
Cause | Failed to truncate LOB data. |
Action | Check the LOB locator. |
Cause | Unable to find a cursor with the specified name. |
Action | Verify the cursor is valid. |
Cause | Failed to prepare DPL. |
Action | Verify the operation is valid. |
Cause | DPL load stream operation failed. |
Action | Verify the operation is valid. |
Cause | DPL data save operation failed. |
Action | Verify the operation is valid. |
Cause | DPL abort operation failed. |
Action | Verify the operation is valid. |
Cause | DPL finish operation failed. |
Action | Verify the operation is valid. |
Cause | Failed to flush a particular record. |
Action | Verify the operation is valid. |
Cause | Additional data is needed after DPL load stream operation. |
Action | Provide the necessary data. |
Cause | No data has been inserted after DPL load stream operation. |
Action | Verify the data is valid. |
Cause | Failed to read DSN information from ODBC.INI. |
Action | Check the DSN information. |
Cause | Data fetch process is complete. |
Action | Perform the next required action. |
Cause | Invalid communication ID. |
Action | Check the communication ID. |
Cause | Failed to shut down. |
Action | Check the server state. |
Cause | Failed to obtain information on the last executed SQL statement. |
Action | Check whether the operation was valid. |
Cause | The request is a duplicate. |
Action | Verify the operation is valid. |
Cause | The handle is in use. |
Action | Check the handle state. |
Cause | There is no error of the descriptor. |
Action | Check the index. |
Cause | The chunk index is invalid. |
Action | Check the chunk index. |
Cause | There is a problem communicating with the server. |
Action | Check the connection with the server. |
Cause | There are more indexes than diagnostics records. |
Action | Check the diagnostics record index. |
Cause | There is additional data for the column. |
Action | Receive the remaining data by calling the SQLGetData() function. |
Cause | The cursor is not updatable. |
Action | Change to an updatable cursor and retry. |
Cause | The record index is out of range. |
Action | Specify a record index smaller than the total number of records in the result set. |
Cause | An invalid size was specified for the integer buffer. |
Action | Choose a value between 1 to 8 bytes. |
Cause | An invalid size was specified for the floating point buffer. |
Action | Choose a value between 4 and 8 bytes. |
Cause | The server connection was terminated but a new connection was made to a server instance with the same DNS name. |
Action | The job being executed by the user was canceled and must be restarted. |
Cause | An attempt was made to connect to a server that is not supported by the current client. |
Action | Use a client that supports connections to this server. |
Cause | The length of the IP address in the DSN file is longer than 128 bytes. |
Action | Check the length of the IP address. |
Cause | Invalid date/time format. |
Action | Check the date/time format. |
Cause | Out of range for numeric. |
Action | Check the buffer size or the data type. |
Cause | Invalid bookmark value. |
Action | Check if the bookmark value is null or a valid value. |
Cause | Invalid fetch direction for the current cursor type. |
Action | Verify the cursor type is scrollable. |
Cause | The current cursor type does not support this query type. The query type will be changed. |
Action | Check the query type. |
Cause | The numbers after the decimal point are truncated. |
Action | Check the buffer size or the data type. |
Cause | Invalid character string value for changing the type. |
Action | Verify the character string is valid to change to the specified type. |
Cause | No available connection exists in the connection pool. |
Action | Modify the parameter to change the number of connections available in the connection pool. |
Cause | Failed to create a daemon thread. |
Action | Internal error. Contact the technical support team. |
Cause | Failed to detach the daemon thread. |
Action | Internal error. Contact the technical support team. |
Cause | Invalid descriptor index. |
Action | Check if the column/parameter exists for the descriptor index. |
Cause | Invalid date type value. |
Action | Check the data value of the date type. |
Cause | The chunk index is invalid. |
Action | Check the chunk index. |
Cause | The specified option is not supported. The option value has been changed to other one. |
Action | Check the option value. |
Cause | Cannot find connection information of JEPA. |
Action | Check the dsn file in the 'client/config' directory under the database home directory. |
Cause | Failed to execute psm. |
Action | Internal error. Contact the technical support team. |
Cause | Failed to set the size of TCP Send Buffer. |
Action | Contact the technical support team. |
Cause | Failed to set the size of TCP Receive Buffer. |
Action | Contact the technical support team. |
Cause | Failed to set the size of TCP Send Buffer. |
Action | Contact the technical support team. |
Cause | Failed to set the size of TCP Receive Buffer. |
Action | Contact the technical support team. |
Cause | Failed to get the size of TCP Send Buffer. |
Action | Contact the technical support team. |
Cause | Failed to get the size of TCP Receive Buffer. |
Action | Contact the technical support team. |
Cause | Failed to set the size of TCP Send Buffer. |
Action | Contact the technical support team. |
Cause | Failed to set the size of TCP Receive Buffer. |
Action | Contact the technical support team. |
Cause | Failed to get the size of TCP Send Buffer. |
Action | Contact the technical support team. |
Cause | Failed to get the size of TCP Receive Buffer. |
Action | Contact the technical support team. |
Cause | Failed to determine the speed of data transmission between server and client. |
Action | Contact the technical support team. |
Cause | Multi thread mode is not set. |
Action | Use the SQLAllocHandle2 or SQLAllocEvn2 API with a true value in the last argument when allocating the env handle. |
Cause | Topic, callback functions, and listen port information are not set in subscription. |
Action | Set all the necessary attributes for the subscription. |
Cause | A client tried to register the same topic using the same DBC handle. |
Action | Registering the same topic in the same dbc handle is not allowed. |
Cause | The topic to unregister is not in the list of subscriptions. |
Action | Register the topic first. |
Cause | There is no listener listening for the port of the unregistering subscription. |
Action | Check if the port of the subscription and the subscription are registered. |
Cause | An I/O error occurred during select failover. |
Action | Try again later. |
Cause | Application fetched too many rows. |
Action | Reduce the number of fetch request. |
Cause | The current server does not support the parallel DPL option. |
Action | Use the latest version of the server. |
Cause | The password has expired(grace). |
Action | Update the password and then try again. |
Cause | Failover was not able to restore the result set to its original state to continue fetching rows. |
Action | Re-execute the query to fetch from the first row. |
Cause | The subscription name is invalid or too long. |
Action | Use a valid subscription name. |
Cause | An unregistered subscription name is used or there is a server error. |
Action | Use a valid subscription name and check if TQ can be used on the server. |
Cause | There is a server error. |
Action | Check if TQ can be used on the server. |
Cause | Connection information is incorrect or insufficient. |
Action | Check if the DSN configuration is incorrect or incomplete. |
Cause | An unexpected protocol was received. |
Action | Check that the protocol is from a valid context. |
Cause | Cannot read a LOB object in a remote server. |
Action | Change the query. |
Cause | The password will expire within %1$s days. |
Action | Update the password. |