Cause: An error occurred during the disconnect. However, the disconnect succeeded.
Action: Validate that the communication between the client and the server are still active.
Cause: An output buffer specified is not large enough to contain the data.
Action: Increase the size of the output buffer.
Cause: The statement was a REVOKE statement and the user did not have the specified privilege.
Action: No action needed.
Cause: An invalid or unsupported connection string attribute was specified in the connection string but the driver was able to connect to the data source anyway.
Action: No action needed.
Cause: The driver did not support the specified option value and substituted a similar value.
Action: No action needed.
Cause: The SQLCancel call was treated like a SQLFreeStmt call with the SQL_CLOSE option.
Action: No action needed.
Cause: The number of parameters specified in SQLSetParam or SQLBindParameter was less than number of parameters in the SQL statement.
Action: Respecify the SQL statement or provide more input parameters through SQLSetParam or SQLBindParameter.
Cause: The previous statement does not result in a result set.
Action: Respecify the SQL statement.
Cause: The conversion between the application data type and SQL data type is not supported by the driver.
Action: Respecify a data conversion which is supported by the driver.
Cause: The number of columns specified in SQLBindCol is greater than the number of columns in the current result set.
Action: Respecify the SQL statement or reset the bound column information in SQLBindCol.
Cause: The driver was unable to establish a connection with the data source.
Action: Ensure the server is started and that the communications between the client and server are correct.
Cause: The specified connection handle is already being used and the connection is still opened.
Action: Allocate a new connection using SQLAllocConnect and retry the connection or terminate the existing connection.
Cause: The connection specified by the connection handle is no longer active.
Action: Establish a new connection.
Cause: The connection failed during the execution of the function and it cannot be determined whether the COMMIT or ROLLBACK occurred before the failure.
Action: Establish a new connection.
Cause: The connection between the driver and the data source failed during execution of this function.
Action: Establish a new connection.
Cause: The data specified through SQLSetParam or SQLBindParameter is larger than the maximum size allowed for the corresponding use of a parameter marker.
Action: Respecify the parameter using SQLSetParam or SQLBindParameter.
Cause: The returned data was NULL but the output or indicator buffer specified was a NULL buffer.
Action: Respecify the output or indicator buffer supplying a non-NULL buffer and retry the operation.
Cause: Returning the numeric data would have caused the whole part of the number to be truncated.
SQLPutData was called more than once for a parameter and the input data was not of type character or binary.
Action: Respecify the output bindings either through SQLBindCol or SQLGetData to avoid creating a numeric data truncation.
Do not call SQLPutData for a parameter if the application data type specified for that parameter through SQLSetParam or SQLBindParameter is not SQL_C_CHAR or SQL_C_BINARY.
Cause: The data sent for a parameter or column was incompatible with the data type of the associated table column.
Action: Respecify the output binding through SQLBindCol or SQLGetData or the input binding through SQLSetParam or SQLBindParameter.
Cause: The data sent for a date field was invalid.
Action: Respecify the date data.
Cause: The data sent for a date, time, or timestamp parameter, or column, was invalid.
Action: Respecify the date, time, or timestamp data.
Cause: The statement is not positioned on a row.
Action: Position the statement on a row by calling SQLFetch or SQLExtendedFetch and retry the operation.
Cause: There was a transaction in progress when SQLDisconnect was called.
Action: Call SQLTransact before calling SQLDisconnect.
Cause: An invalid or duplicate cursor name was specified in SQLSetCursorName.
Action: Respecify a valid cursor name through SQLSetCursorName.
Cause: An invalid or incorrect SQL statement was specified.
Action: Respecify a valid SQL statement.
Cause: An unexpected system failure occurred while processing the function.
Action: Restart the application and try again.
Cause: The driver was unable to allocate memory required to support execution or completion of the function.
Action: Verify that your system has enough memory to complete the desired operation.
Cause: The value specified in iCol is less than zero, greater than the number of columns in the result set, or greater than the maximum number of columns allowed in a result set.
Action: Respecify a valid value for iCol.
Cause: The value specified for fCType is not valid.
Action: Respecify a valid value for fCType.
Cause: The value specified for fSQLType is not valid.
Action: Respecify a valid value for fSQLType.
Cause: The value specified for an argument was invalid. Possible reasons may be a null pointer, invalid length, invalid option, etc.
Action: Re-examine the argument passed in to the function and determine which argument is invalid.
Cause: This function was called in an invalid sequence.
Action: Correct the sequence in your application and retry the operation.
Cause: The operation the system is trying to perform is invalid at this time.
Action: Correct the sequence of operation and retry the operation.
Cause: The transaction option specified in SQLTransact was not SQL_COMMIT or SQL_ROLLBACK.
Action: Specify either SQL_COMMIT or SQL_ROLLBACK and retry the operation.
Cause: Memory handling error.
Action: An unexpected error occurred in the driver while handling some internal memory buffer. Restart your application.
Cause: A call was made to SQLAllocEnv, SQLAllocConnect, or SQLAllocStmt but no more handles are available in the driver.
Action: Call SQLFreeEnv, SQLFreeConnect, or SQLFreeStmt to free up some handles which are no longer being used in the application.
Cause: There was no open cursor on the statement and no cursor had been set with SQLSetCursorName.
Action: Specify a cursor name through SQLSetCursorName.
Cause: The length of the buffer specified is invalid.
Action: Specify a valid buffer length.
Cause: The description type specified is not valid.
Action: Specify a valid descriptor type.
Cause: The option type specified is not valid.
Action: Specify a valid option type.
Cause: The number specified for the parameter number is less than zero or greater than the maximum parameter supported by the data source.
Action: Specify a valid parameter number.
Cause: The scale value specified is invalid.
Action: Specify a valid scale value.
Cause: The function type is invalid.
Action: Specify a valid function type value.
Cause: The information type is invalid.
Action: Specify a valid information type value.
Cause: The column type is invalid.
Action: Specify a valid column type value.
Cause: The scope type is invalid.
Action: Specify a valid scope type value.
Cause: The uniqueness option type is invalid.
Action: Specify a valid uniqueness option type value.
Cause: The accuracy option type is invalid.
Action: Specify a valid accuracy option type value.
Cause: The direction option is invalid.
Action: Specify a valid direction option value.
Cause: The precision value is invalid.
Action: Specify a valid precision value.
Cause: The parameter type is invalid.
Action: Specify a valid parameter type value.
Cause: The fetch type is invalid.
Action: Specify a valid fetch type value.
Cause: The row value is invalid.
Action: Specify a valid row value.
Cause: The concurrency option is invalid.
Action: Specify a valid concurrency option value.
Cause: The cursor position is invalid.
Action: Specify a valid cursor position value.
Cause: The driver completion is invalid.
Action: Specify a valid driver completion value.
Cause: The operation is valid but not supported by either the driver or the data source.
Action: Specify a valid operation.
Cause: SQLParamData or SQLPutData was called but there is no data at execute pending on this statement.
Action: Respecify the parameters through SQLSetParam or SQLBindParameter.
Cause: The function expected a string argument to be supplied.
Action: Respecify the argument to the function.
Cause: The length specified for the file name is invalid.
Action: Specify a valid file name length.
Cause: An attempt to change the connection type was made but the connection or another connection (in the case of Distributed Unit of Work) is already opened.
Action: Do not attempt to change the connection type once the connection is opened.
Cause: The length supplied for the file name is greater than supported.
Action: Specify a valid file name length.
Cause: An unexpected condition occurred while closing a file.
Action: Retry the operation.
Cause: An unexpected condition occurred while opening a file.
Action: Retry the operation.
Cause: An unexpected condition occurred while writing to a file.
Action: Retry the operation.
Cause: An unexpected condition occurred while deleting a file.
Action: Retry the operation.
Cause: An invalid nullable value was specified.
Action: Respecify the nullable value.
Cause: An error occurred while fetching one or more rows. (Function returns SQL_SUCCESS_WITH_INFO.)
Action: Retry the operation.
Cause: The PARMLIST value in the stored procedures catalog table contains a syntax error.
Action: Respecify the row for this stored procedure.
Cause: SQLCancel was called on the statement.
Action: Resubmit the operation.
Cause: The database connection failed. The 'Reason:' will explain why the database was unable to connect.
Action: Fix the problem, and try the connect again.
Cause: The database connection failed. The 'Reason:' will explain why the database was unable to connect.
Action: Fix the problem, and try the connect again or continue with the configuration.
Cause: Neither one of the Visigenic or the Intersolv ODBC Driver Managers have been installed. An ODBC Driver Manager must be present before the DB2 ODBC Driver can be registered into the associated ODBCINST.INI file.
Action: Install an ODBC Driver Manager, and try running this command again.
Cause: An error has occurred while writing to an ODBCINST.INI file to be used with an ODBC Driver Manager. This may be due to invalid format of the original ODBCINST.INI file.
Action: Rename the existing ODBCINST.INI file to something else and try running this command again. If this error persists, contact your technical support.
Cause: An error has occurred while trying to locate where the DB2 OS/2 client is installed.
Action: Check that the DB2 OS/2 Client has been correctly installed.
Cause: The DB2 ODBC Driver has been registered with the installed ODBC Driver Manager(s).
Action: The user can now use the appropriate ODBC Administrator tool from the ODBC Driver Manager vendor to configure the ODBC data sources.
Cause: The DB2 ODBC Driver cannot open a dialog box with the window handle provided by the application.
Action: The application must pass a valid window handle.
Cause: The argument fFetchOrientation was SQL_FETCH_BOOKMARK and the bookmark pointed to by te value SQL_ATTR_FETCH_BOOKMARK_PTR statement attribute was not valid.
Action: Re-specify a valid bookmark value.
Cause: The value specified for the column number argument is invalid.
Action: Re-specify a valid column number.
Cause: The data for one of the columns was truncated.
Action: None needed.
Cause: The descriptor handle was associated with an IRD, and the associated statement handle was not in a prepared state.
Action: Prepare the statement associated with the descriptor.
Cause: The descriptor handle was associated with an IRD, and IRD record fields cannot be updated.
Action: Specify a valid descriptor and field.
Cause: Only explict descriptors allocated using the SQLAllocHandle function can be used in this manner.
Action: Use an explictly allocated descriptor.
Cause: Communication errors caused the server to decline the cancel request.
Action: None needed.
Cause: SQLPutData was called more than once for a column that was not a character or binary column.
Action: Only call SQLPutData once for non-character and non-binary data.
Cause: A previous call to SQLPutData for this parameter specified an input buffer length of SQL_NULL_DATA
Action: Call SQLPutData with a valid input buffer length or ensure SQLPutData is called the correct number of times.
Cause: The associated descriptor failed a consistency check.
Action: Ensure that descriptor fields are valid, and all interdependent fields are set correctly.
Cause: The descriptor handle was invalid, or the TYPE, OCTECT_LENGTH, DATA_PTR, INDICATOR_PTR, or OCTECT_LENGTH_PTR field of the ARD contained an invalid value.
Action: Ensure the indirect descriptor handle is valid and that the deferred fields are set correctly.
Cause: The value given was not correct for the specified attribute.
Action: Use a correct value for the specified attribute.
Cause: Connection had been closed prior to the operation.
Action: Ensure connection close is not called prior to the operation.
Cause: Statement had been closed prior to the operation.
Action: Ensure statement close and statement connection close are not called prior to the operation.
Cause: Cannot allocate memory on server.
Action: Ask your database administrator to check the DB2 JDBC log file for details. Rerun your program.
Cause: Get*** method was called on a parameter that was not registered using registerOutParameter.
Action: Add registerOutParameter call for the parameter.
Cause: The CallableStatement get*** method was called prior to calling CallableStatement execute.
Action: Make sure that CallableStatement execute is called prior to any CallableStatement get*** method.
Cause: The CallableStatement get*** method was not the one that corresponds to the type used in registerOutParameter for this parameter.
Action: Change to the get*** method that matches to the type used in registerOutParameter for this parameter. (Refer to JDBC specification)
Cause: The value in a CHAR/VARCHAR/LONGVARCHAR column is not a valid numeric value.
Action: Use the appropriate get methods other than the ones that return numeric values.
Cause: The value in CHAR/VARCHAR/LONGVARCHAR column is invalid date/time/ timestamp value.
Action: Use appropriate get*** method other than getDate/getTime/ getTimestamp.
Cause: The get*** method is invalid on this column type.
Action: Use the valid get*** method (see JDBC specification) to retrieve data from this column.
Cause: The value of this column is too large/small for a short or int value, conversion will cause data loss.
Action: Use the get method that can accommodate the value.
Cause: The column number is less than 1 or greater than the total number of columns in the ResultSet.
Action: Make sure the column number is no less than 1 and no greater than the total number of columns.
Cause: The given column name cannot be found in the ResultSet.
Action: Ensure the column name is correct.
Cause: The given parameter number is less than 1 or greater than the total number of parameters.
Action: Ensure the parameter number is no less than 1 and no greater than the total number of parameters.
Cause: The object given in the PreparedStatment/CallableStatement setObject is not a valid object type.
Action: Make sure the object to be set is one of the object types allowed in setObject (see JDBC specification).
Cause: Error happened while sending data to server, server may be down.
Action: Ensure the server is up, and rerun your program.
Cause: Error happened while receiving from server, server may be down.
Action: Ensure JDBC server is up, and rerun your program.
Cause: Cannot open the socket to server, server may be down.
Action: Ensure JDBC server is up, and rerun your program.
Cause: Cannot close the socket to server. Server may be down.
Action: Ensure JDBC server is up, and rerun your program.
Cause: The given userid/password is not valid.
Action: Make sure the userid/password is correct, and rerun your program.
Cause: When getUnicodeStream is called on columns that are not DBCS columns, the decoding from UTF8 format is done, but the data cannot be decoded properly.
Action: Use getString/getBytes/getAsciiStream/getBinaryStream instead.
Cause: Error happened when reading data to be put from input stream.
Action: Make sure the file exists, and file length is correctly given.
Cause: The target JDBC Server configuration is not supported. If you are running the Control Center, the target JDBC Server must be a standalone db2jd process (started via db2jstrt) and not a 2-tier native JDBC Server.
Action: Reconfigure the JDBC Server using db2jstrt on the port targeted by the Control Center.
Cause: The Control Center depends upon administration support services that run with the JDBC server. The Control Center was not able to locate or access these administration services.
Action: Ensure that the Control Center's administration services are installed with the JDBC server.