IBM Informix JDBC Driver does not support this JDBC method.
The software could not allocate memory for a new String object.
The row or column index is out of range.
Compare the index to the number of rows and columns expected from the query to ensure that it is within range.
IBM Informix JDBC Driver could not create an instance of itself and register it in the DriverManager class. The rest of the SQLException text describes what failed.
The database URL you have submitted is invalid. IBM Informix JDBC Driver does not recognize the syntax.
Check the syntax and try again.
An invalid character was found during conversion of a String value to an IntervalDF or IntervalYM object.
Check INTERVAL Data Type for correct values.
An error was found during construction of an Interval qualifier from atomic elements: length, start, or end values.
Check the length, start, and end values to verify that they are correct. See INTERVAL Data Type for correct values.
The string you have provided is null. IBM Informix JDBC Driver does not understand null input in this case.
Check the input string to ensure that it has the proper value.
The expected input is a valid date string in the following format: yyyy-mm-dd.
Check the date and verify that it has a four-digit year, followed by a valid two-digit month and two-digit day. The delimiter must be a hyphen ( - ).
Invalid syntax was passed to a jdbc escape clause. Valid JDBC escape clause syntax is demarcated by curly braces and a keyword: for example, {keyword syntax}.
Check the JDBC 3.0 documentation from Sun Microsystems for a list of valid escape clause keywords and syntax.
An invalid time format was passed to a JDBC escape clause. The escape clause syntax for time literals has the following format: {t 'hh:mm:ss'}.
An invalid time stamp format was passed to a JDBC escape clause. The escape clause syntax for time stamp literals has the following format: {ts 'yyyy-mm-dd hh:mm:ss.f...'}.
An incorrect number of arguments was passed to the scalar function escape syntax. The correct syntax is {fn function(arguments)}.
Verify that the correct number of arguments was passed to the function.
You have specified a data type that is not supported by IBM Informix JDBC Driver.
Check your program to make sure the data type used is among those supported by the driver.
Invalid syntax was passed to a jdbc escape clause. Valid JDBC escape clause syntax is demarcated by curly braces and a keyword: {keyword syntax}.
Check the JDBC 3.0 documentation from Sun Microsystems for a list of valid escape clause keywords and syntax.
An operating or runtime system error or a driver internal error occurred. The accompanying message describes the problem.
The length value for an Interval object is incorrect.
See INTERVAL Data Type for correct values.
The start value for an Interval object is incorrect.
See INTERVAL Data Type for correct values.
The end value for an Interval object is incorrect.
See INTERVAL Data Type for correct values.
The start or end value for an Interval object is incorrect.
See INTERVAL Data Type for correct values.
An error occurred during conversion of a String value to an IntervalDF or IntervalYM object. Check INTERVAL Data Type for the correct format.
An error occurred during conversion of a String value to an IntervalDF or IntervalYM object. A numeric value was expected and not found. Check INTERVAL Data Type for the correct format.
An error occurred during conversion of a String value to an IntervalDF or IntervalYM object. A delimiter was expected and not found. Check the INTERVAL Data Type for the correct format.
An error occurred during conversion of a String value to an IntervalDF or IntervalYM object. End of string was encountered before conversion was complete.
Check INTERVAL Data Type for the correct format.
An error occurred during conversion of a String value to an IntervalDF or IntervalYM object. End of string was expected, but there were more characters in the string.
Check INTERVAL Data Type for the correct format.
The SQL statement passed in was null.
Check the SQL statement string of your program to make sure it contains a valid statement.
The SQL statement was not prepared properly. If you use host variables (for example, insert into mytab values (?, ?);) in your SQL statement, you must use connection.prepareStatement() to prepare the SQL statement before you can execute it.
If this is a null opaque type, the type is unknown and cannot be processed. If this is a complex type, the data in the collection or array is of an unknown type and cannot be mapped to an Informix type. If this is a row, one of the elements in the row cannot be mapped to an Informix type. Verify the customized type mapping or data type of the object.
The method does not take an argument. Refer to your Java API specification or the appropriate section of this guide to make sure you are using the method properly.
You must obtain the connection by calling the DriverManager.getConnection() or DataSource.getConnection() method first.
You have specified an out-of-range maxRow value. Make sure you specify a value between 0 and Integer.MAX_VALUE.
The cursor name specified is not valid. Make sure the string passed in is not null or empty.
An internal error occurred during a connection attempt. Call technical support.
There is no current connection or statement.
Check your program to make sure a connection was properly established or a statement was created.
There is no metadata available for this SQL statement.
Make sure the statement generates a result set before you attempt to use it.
The column name specified does not exist. Make sure the column name is correct.
There is no current statement. Make sure the statement was properly created.
There is no data conversion possible from the column data type to the one specified. The actual data type is appended to the end of this message.
Review your program logic to make sure that the conversion you have asked for is supported. Refer to Appendix C for the data mapping matrix.
No data conversion is possible from the data type you specified to the column data type. The actual data type is appended to the end of this message.
Check your program logic to make sure that the conversion you have asked for is supported. Refer to Appendix C for the data mapping matrix.
The user has tried to call commit() or rollback() on a database that does not support transactions or has tried to set autoCommit to False on a nonlogging database.
Verify that the current database has the correct logging mode and review the program logic.
Informix does not support read-only mode.
Informix does not support setting the transaction isolation level on nonlogging databases.
If the database server could not complete the rollback, this error occurs. See the rest of the SQLException message for more details about why the rollback failed.
This error also occurs if an invalid transaction level is passed to setTransactionIsolation(). The valid values are:
IBM Informix JDBC Driver normally locks the connection object just before beginning the data exchange with the database server. The driver could not obtain the lock. Only one thread at a time should use the connection object.
The number of variables that you set using the PreparedStatement.setXXX() methods in this statement does not match the number of ? placeholders that you wrote into the statement.
Locate the text of the statement and verify the number of placeholders and then check the calls to PreparedStatement.setXXX().
The Statement.executeQuery(String) and PreparedStatement.executeQuery() methods should only be used if the statement is a SELECT statement. For other statements, use the Statement.execute(String), Statement.executeBatch(), Statement.executeUpdate(String), Statement.getUpdateCount(), Statement.getResultSet(), or PreparedStatement.executeUpdate() method.
The object passed in is null. Check your program logic to make sure your object reference is valid.
The first token of the database URL must be the keyword jdbc (case insensitive), as in the following example:
jdbc:informix-sqli://mymachine:1234/ mydatabase:user=me: password=secret
The current valid subprotocol is informix-sqli.
When you connect to an Informix database server via an ip address, the ip address must be valid. A valid ip address is a set of four numbers between 0 and 255, separated by dots ( . ): for example, 127.0.0.1.
The port number must be a valid four-digit number, as follows:
jdbc:informix-sqli://mymachine:1234/ mydatabase:user=me: password=secret
In this example, 1234 is the port number.
This statement contains the name of a database in some invalid format.
The maximum length for database names and cursor names depends on the version of the database server. In 7.x, 8.x, and 9.1x versions of the Informix database server, the maximum length is 18 characters.
For IBM Informix SE, database names should be no longer than 10 characters (fewer in some host operating systems).
Both database and cursor names must begin with a letter and contain only letters, numbers, and underscore characters. In the 6.0 and later versions of the database server, database and cursor names can begin with an underscore.
In MS-DOS systems, filenames can be a maximum of eight characters plus a three-character extension.
The database URL accepts property values in key=value pairs. For example, user=informix:password=informix adds the key=value pairs to the list of properties that are passed to the connection object.
Check the syntax of the key=value pair for syntax errors. Make sure there is only one = sign; that there are no spaces separating the key, value, or =; and that key=value pairs are separated by one colon( : ), again with no spaces.
When connecting to a Version 5.x database server, the user must set the database URL property USE5SERVER to any non-null value. If a connection is then made to a Version 6.0 or later database server, this exception is thrown.
Verify that the version of the database server is correct and modify the database URL as needed.
The result set type has been set to TYPE_FORWARD_ONLY, but the setFetchDirection() method has been called with a value other than FETCH_FORWARD. The direction specified must be consistent with the result type specified.
A method such as ResultSet.beforeFirst(), ResultSet.afterLast(), ResultSet.first(), ResultSet.last(), ResultSet.absolute(), ResultSet.relative(), ResultSet.current(), or ResultSet.previous() has been called, but the result set type is TYPE_FORWARD_ONLY. Call only the ResultSet.next() method if the result set type is TYPE_FORWARD_ONLY.
The ResultSet.absolute(int) method has been called with a value of 0. The parameter must be greater than 0.
You must register a customized type map to use any opaque types.
The SQLTypename object you specified in the SQLData or Struct class does not exist in the database. Make sure that the type name is valid.
The input value is not accepted for this data type. Make sure this is a valid input for this data type.
This error occurs when a Java user-defined routine attempts to read or set a position beyond the end of the opaque type data available from a data input stream.
Check the length and structure of the opaque type carefully against the data-input UDR code. The SQLTypeName object that was returned by the getSQLTypeName() method might also be incorrect.
Large object data read from the database server can be stored either in memory or in a local file. If the LOBCACHE value is 0 or the large object size is greater than the LOBCACHE value, the large object data from the database server is always stored in a file. In this case, if a security exception occurs, IBM Informix JDBC Driver makes no attempt to store the large object into memory and throws this exception.
IBM Informix JDBC Driver only supports a result set type of TYPE_SCROLL_INSENSITIVE and TYPE_FORWARD_ONLY. Only these values should be used.
Row type information was acquired either through the system catalogs or through the supplied row definition. The row data provided does not match this row element type. The type information must be modified, or the data must be provided.
The SQLData.writeObject() method was called for an object that is not a user-defined, distinct, or complex type.
Verify that you have provided customized type-mapping information.
You provided a type mapping to override the default for a set, list, or multiset data type, but the class does not implement the java.util.Collection interface.
Verify that all the objects in the collection are of the same class.
Array.getArray() or Array.getResultSet() was called with index and count values. Either the index is out of range or the count is too big.
Verify that the number of elements in the array is sufficient for the index and count values.
The encoding or code set entered in the DB_LOCALE or CLIENT_LOCALE variable is not valid.
Check Support for Code-Set Conversion for valid code sets.
The locale entered in the DB_LOCALE or CLIENT_LOCALE variable is not valid.
Check Support for Code-Set Conversion for valid locales.
The JDBC escape
format for date values must be specified in the format
{d 'yyyy-mm-dd'}.
Verify that the JDBC escape date format
specified is correct.
Verify the DBDATE and GL_DATE settings for the correct date string format if either of these was set to a value in the connection database URL string or property list.
The localized date string representation specified in a char, varchar, or lvarchar column is not correct, and a date object cannot be built based on the year, month, and day values.
Verify that the date string representation conforms to the DBDATE or GL_DATE date formats if either one of these is specified in a connection database URL string or property list. If neither DBDATE or GL_DATE is specified but a CLIENT_LOCALE or DB_LOCALE is explicitly set in a connection database URL string or property list, verify that the date string representation conforms to the JDK short default format (DateFormat.SHORT).
The user name is required to establish a connection with IBM Informix JDBC Driver.
Make sure you pass in user=your_user_name as part of the database URL or one of the properties.
These variables can only be used if the database server supports GLS.
Check the documentation for your database server version and omit these variables if they are not supported.
The value returned by the getSQLTypeName() method is either null or invalid.
Check the string to verify that it is either a valid named-row name or a valid row type definition.
Data in the row does not match the length in the row type information. You do not have to pad string lengths to match what is in the row definition, but lengths for other data types should match.
The extended ID of the object in the row does not match the extended ID as defined in row type information.
Either update the row information (if you are providing the row definition) or check the type mapping information.
The getSQLTypeName() method has returned a name that can not be found in the database.
Verify that the Struct or SQLData object returns the correct information.
This error occurs because the DBDATE format string that is passed to the database server either has too few characters or too many.
To fix the problem, verify the DBDATE format string with the user documentation and make sure that the correct year, month, day, and possibly era parts of the DBDATE format string are correctly identified.
This error occurs because the DBDATE format string has a year designation (specified by the character Y), but there is no character following the year designation to denote the numerical year expansion (2 or 4).
To fix the problem, modify the DBDATE format string to include the numerical year expansion value after the Y character.
This error occurs because the DBDATE format string has a year designation (specified by the character Y), but the character following the year designation is not a 2 or 4 (for two-digit years and four-digit years, respectively).
To fix the problem, modify the DBDATE format string to include the required numerical year expansion value after the Y character. Only a 2 or 4 character should immediately follow the Y character designation.
This error occurs because the DBDATE format string has a numerical year expansion (2 or 4 to denote two-digit years or four-digit years, respectively), but the year designation character (Y) was not found immediately before the numerical year expansion character specified.
To fix the problem, modify the DBDATE format string to include the required Y character immediately before the numerical year expansion value requested.
This error occurs because the DBDATE format string has a character that is not allowed.
To fix the problem, modify the DBDATE format string to only include the correct date part designations: year (Y), numerical year expansion value (2 or 4), month (M), and day (D). Optionally, you can include an era designation (E) and a default separator character (hyphen, dot, or slash), which is specified at the end of the DBDATE format string. Refer to the user documentation for further information on correct DBDATE format string character designations.
This error occurs because the date string specified does not have the minimum number of tokens or separators needed to form a valid date value (composed of year, month, and day numerical parts). For example, 12/15/98 is a valid date string representation with the slash character as the separator or token. But 12/1598 is not a valid date string representation, because there are not enough separators or tokens.
To fix the problem, modify the date string representation to include a valid format for separating the day, month, and year parts of a date value.
This error occurs because there is not a one-to-one correspondence between the date string format required by DBDATE or GL_DATE and the actual date string representation you defined. For example, if GL_DATE is set to %b %D %y and you specify a character string of Oct, there is a definite mismatch between the format required by GL_DATE and the actual date string.
To fix the problem, modify the date string representation of the DBDATE or GL_DATE setting so that the date format specified matches one-to-one with the required date string representation.
This error occurs because the date string specified does not have any more tokens or separators needed to form a valid date value (composed of year, month, and day numerical parts) based on the DBDATE format string. For example, 12/15/98 is a valid date string representation when DBDATE is set to MDY2/. But 12/1598 is not a valid date string representation, because there are not enough separators or tokens.
To fix the problem, modify the date string representation to include a valid format for separating the day, month, and year parts of a date value based on the DBDATE format string setting.
This error occurs because the date string specified does not have a valid era designation, as required by the DBDATE or GL_DATE format string setting. For example, if DBDATE is set to Y2MDE-, but the date string representation specified by the user is 98-12-15, this is an error because there is no era designation at the end of the date string value.
To fix the problem, modify the date string representation to include a valid era designation based on the DBDATE or GL_DATE format string setting. In this example, a date string representation of 98-12-15 AD would probably suffice, depending on the locale.
This error occurs because the date string specified does not have a valid numerical day designation as required by the DBDATE format string setting. For example, if DBDATE is set to Y2MD-, but the date string representation you specify is 98-12-blah, this is an error, because blah is not a valid numerical day representation.
To fix the problem, modify the date string representation to include a valid numerical day designation (from 1 to 31) based on the DBDATE format string setting.
This error occurs because the date string specified does not have a valid numerical month designation as required by the DBDATE format string setting. For example, if DBDATE is set to Y2MD-, but the date string representation you specify is 98-blah-15, this is an error, because blah is not a valid numerical month representation.
To fix the problem, modify the date string representation to include a valid numerical month designation (from 1 to 12) based on the DBDATE format string setting.
This error occurs because the date string specified does not have the correct number of tokens or separators needed to form a valid date value based on the GL_DATE %D directive (mm/dd/yy format). For example, 12/15/98 is a valid date string representation based on the GL_DATE %D directive, but 12/1598 is not a valid date string representation, because there are not enough separators or tokens.
To fix the problem, modify the date string representation to include a valid format for the GL_DATE %D directive.
This error occurs because the date string specified does not have the correct number of tokens or separators needed to form a valid date value based on the GL_DATE %x directive (format required is based on day, month, and year parts, and the ordering of these parts is determined by the specified locale). For example, 12/15/98 is a valid date string representation based on the GL_DATE %x directive for the U.S. English locale, but 12/1598 is not a valid date string representation because there are not enough separators or tokens.
To fix the problem, modify the date string representation to include a valid format for the GL_DATE %x directive based on the locale.
IBM Informix JDBC Driver Version 2.x requires a JDK version of 1.2 or greater.
You called the getConnection() method for the DataSource object, and the user name or the password is null.
Use the user name and password arguments of the getConnection() method or set these values in the DataSource object.
You called the getConnection(user, passwd) method for the DataSource object, and the values you supplied did not match the values already found in the data source.
If you retrieve a smart large object using the ResultSet.getBlob() or ResultSet.getClob() method or create one using the IfxBlob() or IfxCblob() constructor, a smart large object is opened. You can then read from or write to the smart large object. After you execute the IfxBlob.close() method, do not use the smart large object handle for further read/write operations, or this exception is thrown.
Call the moveToInsertRow() method before calling insertRow().
The table name in the query is either incorrect or refers to a table that does not exist.
The updatable scrollable feature works only for tables that have a SERIAL column, a primary key, or a row ID specified in the query. If the table does not have any of the above, an updatable scrollable cursor cannot be created.
You tried to call the insertRow(), updateRow(), or deleteRow() method for a statement that has not been created with the CONCUR_UPDATABLE concurrency type.
Re-create the statement with this type set for the concurrency attribute.
If you have a data type that requires a name (an opaque type or complex type) you must call a method that has a parameter for the name, such as the following methods:
public void IfxSetNull(int i, int ifxType, String name) public void registerOutParameter (int parameterIndex, int sqlType, java.lang.String name); public void IfxRegisterOutParameter (int parameterIndex, int ifxType, java.lang.String name);
The data type you have specified does not require a name.
Use another method that does not have a type parameter.
The function specified using the CallableStatement interface has an OUT parameter that has not been registered.
Call one of the registerOutParameter() or IfxRegisterOutParameter() methods to register the OUT parameter type before calling the executeQuery() method.
The function specified using the CallableStatement interface has an IN parameter that has not been set.
Call the setNull() or IfxSetNull() method if you want to set a null IN parameter. Otherwise, call one of the set methods inherited from the PreparedStatement interface.
The function specified using the CallableStatement interface has an OUT parameter that has not been set.
Call the setNull() or IfxSetNull() method if you want to set a null OUT parameter. Otherwise, call one of the set methods inherited from the PreparedStatement interface.
This data type is an opaque type, distinct type, or complex type, and it requires a name.
Use set methods for IN parameters and register methods for OUT parameters that take a type name as a parameter.
The SQL type specified either has no mapping to an Informix data type or has more than one mapping.
Use one of the IfxRegisterOutParameter() methods to specify the Informix data type.
Informix functions can have only one OUT parameter, and it is always the last parameter.
One or more of the directives specified by the GL_DATE environment variable is not allowed. Refer to GL_DATE Variable for a list of the valid directives for a GL_DATE format.
To perform string-to-binary conversions correctly for building a java.sql.Timestamp or java.sql.Time object, all the DATETIME fields must be specified for the chosen date string representation. For java.sql.Timestamp objects, the year, month, day, hour, minute, and second parts must be specified in the string representation. For java.sql.Time objects, the hour, minute, and second parts must be specified in the string representation.
If you repeatedly connect to a database using a DataSource object without closing the connection, connections accumulate. When the total number of connections for the DataSource object exceeds the maximum limit (100), this error is thrown.
This error occurs when the user calls the method XAConnection.getConnection() against an XPS server.
This error is thrown by the Informix HTTP Proxy if you try to communicate with the database on an invalid or bad database connection.
Make sure your application has opened a connection to the database, check your Web server and database error logs.
This error is thrown by the Informix HTTP Proxy if an error is detected while the proxy is communicating with the database. This error can occur if your database server is not accessible.
Make sure your database is accessible, check your database and Web server error logs.
The driver is unable to change the permissions on the client JAR file. This could happen if your client platform does not support the chmod or attrib command, or if the user running the JDBC application does not have the authority to change access permissions on the client JAR file.
Make sure that the chmod or attrib command is available for your platform and that the user running the application has the authority to change access permissions on the client JAR file.
The JAR filename specified when your application called UDTManager.createJar() has already been registered in the database server.
Use UDTMetaData.setJarFileSQLName() to specify a different SQL name for the JAR file.
This error occurs when the pathname set using setJarTmpPath() is not writable by user informix or the user specified in the JDBC connection.
Make sure the pathname is readable and writable by any user.
Your application called the UDRManager.createUDRs() method without specifying any UDRs for the database server to register.
Specify UDRs for the database server to register by calling the UDRMetaData.setUDR() method before calling the UDRManager.createUDRs() method.
Your application called either the UDTManager.createUDT() or the UDRManager.createUDRs() method without specifying an SQL name for the JAR file containing the opaque types or UDRs for the database server to register.
Specify an SQL name for a JAR file by calling the UDTMetaData.setJarFileSQLName() or UDRMetaData.setJarFileSQLName() method before calling the UDTManager.createUDT() or UDRManager.createUDRs() method.
Your application created a connection without specifying a database. The following example establishes a connection and opens a database named test:
url = "jdbc:informix-sqli:myhost:1533/test:" + "informixserver=myserver;user=rdtest; password=test"; conn = DriverManager.getConnection(url);
The following example establishes a connection with no database open:
url = "jdbc:informix-sqli:myhost:1533:" + "informixserver=myserver;user=rdtest; password=test"; conn = DriverManager.getConnection(url);
To resolve this problem, use the following SQL statements after the connection is established and before calling the createUDT() or createUDRs() methods:
Statement stmt = conn.createStatement();
stmt.executeUpdate("create database test
...");
Alternatively, use the following code:
stmt.executeUpdate("database test");This error occurs for one of the following reasons:
The client JAR file your application specified as the second parameter to UDTManager.createUDT() or UDRManager.createUDRs() must end with the .jar extension.
The driver encountered compilation errors in one of the following cases:
Your application called UDTManager.createUDTClass() without first specifying the number of fields in the internal data structure that defines the opaque type.
Specify the number of fields by calling UDTMetaData.setFieldCount().
Your application called UDTManager.createUDTClass() without first specifying a length for the opaque type.
Specify the total length for the opaque type by calling UDTMetaData.setLength().
Your application called UDTManager.createUDTClass() without first specifying a field name and data type for each field in the data structure that defines the opaque type.
Specify the field name by calling UDTMetaData.setFieldName(); specify a data type by calling UDTMetaData.setFieldType().
Your application called the createJar() method and passed a zero-length string for the classnames parameter. The method signature is as follows:
createJar(UDTMetaData mdata, String[] classnames)
Your application called UDTManager.createUDT() to create an opaque type whose class definition does not implement the java.sql.SQLData interface. UDTManager cannot create an opaque type from a class that does not implement this interface.
Your application called the UDTManager.createUDT() method but the driver could not find a class with the name you specified for the third parameter.
Your application called UDTManager.removeUDT(String sqlname) to remove an opaque type named sqlname from the database, but the opaque type with that name does not exist in the database.
This error occurs only if your application called the UDTMetaData.setSupportUDR() method and passed an integer other than 0 through 7 for the type parameter.
Use the constants defined for the support UDR types. For more information, see Using setSupportUDR() and setUDR().
If UDTMetaData.keepJavaFile() is not called or is set to FALSE, the driver removes the generated .java file when the UDTManager.createUDTClass() method executes. This error results if the driver was unable to remove the .java file.
Your application called a UDTMetaData.setXXX() or UDTMetaData.getXXX() method and specified a field number that was less than 0 or greater than the value set through the UDTMetaData.setFieldCount() method.
One or more parameters of the method to be registered as a UDR is of type java.lang.Object or java.sql.SQLData. These Java data types can be mapped to more than one Informix data type, so the driver is unable to choose a type.
Avoid using java.lang.Object or java.sql.SQLData as method arguments.
Your application called UDTMetaData.setFieldType() and specified a data type that has no 100 percent match in Java. The following data types are in this category:
IfxTypes.IFX_TYPE_BYTE IfxTypes.IFX_TYPE_TEXT IfxTypes.IFX_TYPE_VARCHAR IfxTypes.IFX_TYPE_NVCHAR IfxTypes.IFX_TYPE_LVARCHAR
Use IFX_TYPE_CHAR or IFX_TYPE_NCHAR instead; these data types map to java.lang.String.
Your application called UDTMetaData.setFieldType() and specified an unsupported data type for the opaque type. For supported data types, see "Mapping for Field Types" on page Mapping for Field Types.
Your application specified a field of character, date-time, or interval type by calling UDTMetaData.setFieldType(), but failed to specify a field length. Call UDTMetaData.setFieldLength() to set a field length.
Your application issued an SQL PREPARE, DECLARE, or EXECUTE IMMEDIATE statement that is longer than the database server can handle. The limit differs with different implementations, but in most cases is up to 32,000 characters.
Review the program logic to ensure that an error has not caused your application to present a string that is longer than intended. If the text has the intended length, revise the application to present fewer statements at a time.
This is the same as error -460 returned by the database server.
This error occurs when an application attempts to access a statement method after the stmt.close() method.
This error occurs when an application attempts to access a ResultSet method after the ResultSet.close() method.
This error occurs when an application attempts to set the maximum field size to a value less than zero.
This error occurs when an application attempts to access the ResultSet.next() method without executing a result set query.
This error occurs when a non-SQL exception occurs; for example, an IO exception.
This error occurs when the driver cannot obtain the JDK version from the Java virtual machine.
This error occurs when the application attempts to start an XA transaction while a local transaction is still in progress.