Switch to standard view 
  Sybase logo
 
 
 




A. SQL Exception and Warning Messages

The following table lists the SQL exception and warning messages that you may encounter when using jConnect.

SQLState

Message/Description/Action

010DP

Duplicate connection property _____ ignored.

Description: A connection property is defined twice. It may be defined twice in the driver connection properties list with different capitalization, for example "password" and "PASSWORD." Connection property names are not case-sensitive, and therefore jConnect does not distinguish between property names with the same name but different capitalization.

The connection property may also be defined both in the connection properties list, and in the URL. In this case, the property value in the connection property list takes precedence.

Action: Make sure your application defines the connection property only once. However, you may want you application to take advantage of the precedence of connection properties defined in the property list over those defined in the URL. In this case, you can safely ignore this warning.

010MX

Metadata accessor information was not found on this database. Error encountered while attempting to retrieve metadata information: _____

Description: The server may not have the necessary stored procedures for returning metadata information.

Action: Make sure that stored procedures for providing metadata are installed on the server. See "Installing Stored Procedures" in Chapter 3 of the jConnect for JDBC Installation Guide and Release Bulletin.

010P4

An output parameter was received and ignored.

Description: The query you executed returned an output parameter but the application result-processing code did not fetch it so it was ignored.

Action: If your application needs the output parameter data, you must rewrite the application so it can get it. This may require using a CallableStatement to execute the query, and adding calls to registerOutputParameter() and getXXX().

010RC

The requested ResultSet type and concurrency is not supported. They have been converted.

Description: You requested a type and concurrency combination for the ResultSet that is not supported. The requested values had to be converted.

Action: Request a type and concurrency combination for the ResultSet that is supported.

010SN

Permission to write to file was denied. File: _____. Error message: _____

Description: Permission to write to a file specified in the PROTOCOL_CAPTURE connection property is denied because of a security violation in the VM. This can occur if an applet attempts to write to the specified file.

Action: If you are attempting to write to the file from an applet, make sure that the applet has access to the target file system.

010SP

File could not be opened for writing. File: _____. Error message: _____

Action: Make sure that the file name is correct and that the file is writable.

010SJ

Metadata accessor information was not found on this database.

Description: The metadata information is not configured on the server.

Action: If your application requires metadata, install the stored procedures for returning metadata that come with jConnect (see "Installing Stored Procedures" in Chapter 3 of the jConnect for JDBC Installation Guide and Release Bulletin). If you do not need metadata, set the USE_METADATA property to "false."

010SK

Database cannot set connection option _____.

Description: Your application attempted an operation that the database you are connected to does not support.

Action: You may need to upgrade your database or make sure that the latest version of metadata information is installed on it.

010TP

The connection's initial character set,_____, could not be converted by the server. The server's proposed character set,_____, will be used, with conversions performed by jConnect.

Description: The server cannot use the character set initially requested by jConnect, and has responded with a different character set. jConnect accepts the change, and will perform the necessary character-set conversions.

The message is strictly informational and has no further consequences.

Action: To avoid this message, set the CHARSET connection property to a character set that the server supports.

010UF

Attempt to execute use database command failed. Error message:_____

Description: jConnect was unable to connect to the database specified in the connection URL. Two possibilities are:

  • The name was entered incorrectly in the URL.
  • USE_METADATA is "true" (the default condition), but the stored procedures for returning metadata have not been installed. As a result, jConnect tried to execute the use database command with the database in the URL, but the command failed. This may be because you attempted to access a SQL Anywhere database. SQL Anywhere databases do not support the use database command.

Action: Make sure the database name in the URL is correct. Make sure that the stored procedures for returning metadata are installed on the server (see "Installing Stored Procedures" in Chapter 3 of the jConnect for JDBC Installation Guide and Release Bulletin). If you are attempting to access a SQL Anywhere database, either do not specify a database name in the URL or set USE_METADATA to "false."

010UP

Unrecognized connection property _____ ignored.

Description: You attempted to set a connection property in the URL that jConnect does not currently recognize. jConnect ignores the unrecognized property.

Action: Check the URL definition in your application to make sure it references only valid jConnect driver connection properties.

JW0I0

I/O layer: thread operation failed.

Description: An internal error occurred with a timed I/O stream.

Action: Close and reopen the connection.

JZ001

User name property '_____' too long. Maximum length is 30.

Action: Do not exceed the 30 byte maximum.

JZ002

Password property '_____' too long. Maximum length is 30.

Action: Do not exceed the 30-byte maximum.

JZ003

Incorrect URL format. URL: _____

Action: Verify the URL format. See "URL Connection Property Parameters".

If you are using the PROXY connection property, you may get a JZ003 exception while trying to connect if the format for the PROXY property is incorrect.

The PROXY format for the Cascade proxy is:

ip_address:port_number

The PROXY format for the TDS Tunneling Servlet is:

http[s]://host:port/tunneling_servlet_alias

JZ004

User name property missing in DriverManager.getConnection(..., Properties)

Action: Provide the required user property.

JZ006

Caught IOException: _____

Description: An unexpected I/O error was detected from a lower layer. When such I/O exceptions are caught, they are re-thrown as SQL exceptions using the ERR_IO_EXCEPTION JZ006 sqlstate. These errors are often the result of network communication problems.

Action: Try increasing the statement cache size.

JZ008

Invalid column index value _____.

Description: You have requested a column index value of less than 1 or greater than the highest available value.

Action: Check call to the getXXX() method and the text of the original query, or be sure to call rs.next().

JZ009

Error encountered in conversion. Error message: _____

Description: Some of the possibilities are:

  • A conversion between two incompatible datatypes was attempted, such as date to int.
  • There was an attempt to convert a string containing a non-numeric character to a numeric type.
  • There was a formatting error, such as an incorrectly formatted time/date string.

Action: Make sure that the JDBC specification supports the attempted type conversion. Make sure that strings are correctly formatted. If a string contains non-numeric characters, do not attempt to convert it to a numeric type.

JZ00B

Numeric overflow.

Description: You tried to send a BigInteger as a TDS numeric, and the value was too large, or you tried to send a Java long as an int and the value was too large.

Action: These values cannot be stored in Sybase. For long, consider using a Sybase numeric. There is no solution for Bignum.

JZ00E

Attempt to call execute() or executeUpdate() for a statement where setCursorName() has been called.

Action: Don't try to call execute or executeUpdate on a statement that has a cursor name set. Use a separate statement to delete or update a cursor. See "Using Cursors with Result Sets" for more information

JZ00F

Cursor name has already been set by setCursorName().

Action: Do not set the cursor name twice for a statement. Close the result set of the current cursor statement.

JZ00G

No column values were set for this row update.

Description: You attempted to update a row in which no column values were changed.

Action: To change column values in a row, call updateXX() methods before calling updateRow().

JZ00H

The result set is not updatable. Use Statement.setResultSetConcurrencyType().

Action: To change a result set from read-only to updatable, use the Statement.setResultSetConcurrencyType() method or add a for update clause to your SQL select statement.

JZ00L

Login failed. Examine the SQLWarnings chained to this exception for the reason(s).

Action: See message text; proceed according to the reason(s) given for the login failure.

JZ010

Unable to deserialize an Object value. Error text: _____

Action: Make sure that the Java object from the database implements the Serializable interface and is in your local CLASSPATH variable.

JZ011

Number format exception encountered while parsing numeric connection property _____.

Description: A non-integer value was specified for a numeric connection property.

Action: Specify an integer value for the connection property.

JZ012

Internal Error. Please report it to Sybase technical support. Wrong access type for connection property _____.

Action: Contact Sybase Technical Support.

JZ013

Error obtaining JNDI entry: _____

Action: Correct the JNDI URL or make a new entry in the directory service.

JZ0BD

Out of range or invalid value used for method parameter.

Action: Verify that the parameter value in the method is correct.

JZ0BR

The cursor is not positioned on a row that supports the %ls method.

Description: You attempted to call a ResultSet method that is invalid for the current row position (e.g., calling insertRow() when the cursor is not on the insert row).

Action: Do not attempt to call a ResultSet method that is invalid for the current row position.

JZ0BT

The %ls method is not supported for ResultSets of type %2s.

Description: You attempted to call a RelsultSet method that is invalid for the type of ResultSet.

Action: Do not attempt to call a ResultSet method that is invalid for the type of ResultSet.

JZ0C0

Connection is already closed.

Description: The application has already called Connection.close() on this connection object; it cannot be used any more.

Action: Fix the code so that connection object references are nulled out whenever a connection is closed.

JZ0D0

This jConnect installation has not been registered yet. You need to install the appropriate SybDriverKey classes.

Action: Go to the jConnect Web site. Once you register, you can download the SybDriverKey classes necessary to activate the jConnect driver.

JZ0D1

Invalid SybDriverKey for this jConnect driver.

Description: You tried accessing the jConnect driver with an activation key that does not match the jConnect driver you are using.

Action: Go to the jConnect Web site. Once you register, you can download the SybDriverKey classes necessary to activate the jConnect driver.

JZ0D2

Your Sybase JDBC license expired on _____. Please obtain a new license.

Action: Contact Sybase to obtain a new license for your jConnect driver

JZ0D3

Your Sybase JDBC license will expire soon. Please obtain a new license. It will expire on _____.

Action: Contact Sybase to obtain a new license for your jConnect driver

JZ0D4

Unrecognized protocol in Sybase JDBC URL:_____.

Description: You specified a connection URL using a protocol other than TDS, which is the only protocol currently supported by jConnect.

Action: Check the URL definition. If the URL specifies TDS as a subprotocol make sure that the entry uses the following format and capitalization:

jdbc:sybase:Tds:host:port

If the URL specifies JNDI as a subprotocol, make sure that it starts with:

jdbc:sybase:jndi:

JZ0D5

Error loading protocol _____.

Action: Check the settings for the CLASSPATH system variable.

JZ0D6

Unrecognized version number _____ specified in setVersion. Choose one of the SybDriver.VERSION_* values, and make sure that the version of jConnect that you are using is at or beyond the version you specify.

Action: See message text.

JZ0D7

Error loading url provider _____. Error message: _____

Action: Check the JNDI URL to make sure it is correct.

JZ0D8

Error initializing url provider: _____

Action: Check the JNDI URL to make sure it is correct.

JZ0EM

End of data.

Action: Report this error to Sybase Technical Support.

JZ0H0

Unable to start thread for event handler; event name = _____.

Action: Report this error to Sybase Technical Support.

JZ0H1

An event notification was received but the event handler was not found; event name = _____.

Action: Report this error to Sybase Technical Support.

JZ0HC

Illegal character '_____' encountered while parsing hexadecimal number.

Description: A string that is supposed to represent a binary value contains a character that is not in the range (0-9, a-f) that is required for a hexadecimal number.

Action: Check the character values in the string to make sure they are in the required range.

JZ0I1

I/O Layer: Error reading stream.

Description: The connection was unable to read the amount requested. Most likely, the statement timeout period was exceeded and the connection timed out.

Action: Increase the statement timeout value.

JZ0I2

I/O layer: Error writing stream.

Description: The connection was unable to write the output requested. Most likely, the statement timeout period was exceeded and the connection timed out.

Action: Increase the statement timeout value.

JZ0I3

Unknown property. This message indicates an internal product problem. Report this error to Sybase Technical support.

Action: Indicates an internal product problem. Report this error to Sybase Technical Support.

JZ0I5

An unrecognized CHARSET property was specified: _____.

Description: You specified a character set code for the CHARSET connection property that is not supported.

Action: Enter a valid character set code for the connection property. See "jConnect Character-Set Converters".

JZ0I6

An error occurred converting UNICODE to the charset used by the server. Error message: _____

Action: Choose a different character set code for the CHARSET connection property on the jConnect client that can support all the characters you need to send to the server. You may need to install a different character set on the server, too.

JZ0I7

No response from proxy gateway.

Description: The Cascade or security gateway is not responding.

Action: Make sure the gateway is properly installed and running.

JZ0I8

Proxy gateway connection refused. Gateway response: _____

Description: The Web server/gateway indicated by the PROXY connection property has refused your connection request.

Action: Check the access and error logs on the proxy to determine why the connection was refused. Make sure the proxy is a JDBC gateway.

JZ0I9

This InputStream was closed.

Description: You tried to read an InputStream obtained from getAsciiStream(), getUnicodeStream(), or getBinaryStream(), but the InputStream was already closed. The stream may have been closed because you moved to another column or cancelled the result set and there were not enough resources to cache the data.

Action: Increase the cache size or read columns in order.

JZ0IA

Truncation error trying to send_____.

Description: There was a truncation error on character set conversion prior to sending a string. The converted string is longer than the size allocated for it.

Action: Choose a different character set code for the CHARSET connection property on the jConnect client that can support all the characters you need to send to the server. You may need to install a different character set on the server, too.

JZ0IS

getXXXStream may not be called on a column after it has been updated in the result set.

Description: After updating a column in a result set, you attempted to read the updated column value using one of the following SybResultSet methods: getAsciiStream(), getUnicodeStream(), getBinaryStream(). jConnect does not support this usage.

Action: Do not attempt to fetch input streams from columns you are updating.

JZ0J0

Offset and/or length values exceed the actual text/image length.

Action: Check the offset and/or length values you used to make sure they are correct.

JZ0NC

wasNull called without a preceding call to get a column.

Description: You can only call wasNull() after a call to get a column, such as getInt() or getBinaryStream().

Action: Change the code to move the call to wasNull().

JZ0NE

Incorrect URL format. URL: _____. Error message: _____

Action: Check the format of the URL. Make sure that the port number consists only of numeric characters.

JZ0NF

Unable to load SybSocketFactory. Make sure that you have spelled the class name correctly, that the package is fully specified, that the class is available in your class path, and that it has a public zero-argument constructor.

Action: See message text.

JZ0P1

Unexpected result type.

Description: The database has returned a result that the statement cannot return to the application, or that the application is not expecting at this point. This generally indicates that the application is using JDBC incorrectly to execute the query or stored procedure. If the JDBC application is connected to an Open Server application, it may indicate an error in the Open Server application that causes the Open Server to send unexpected sequences of results.

Action: Use the com.sybase.utils.Debug(true, "ALL") debugging tools to try to figure out what unexpected result is seen, and to understand its causes.

JZ0P4

Protocol error. This message indicates an internal product problem. Report this error to Sybase technical support.

Action: See message text.

JZ0P7

Column is not cached; use RE-READABLE_COLUMNS property.

Description: With the REPEAT_READ connection property set to "false," an attempt was made to reread a column or read a column in the wrong order.

When REPEAT_READ is "false." You can only read the column value for a row once, and you can only read columns in ascending column-index order. For example, after reading Column 3 for a row, you cannot read its value a second time and you cannot read Column 2 for the row.

Action: Either set REPEAT_READ to "true," or do not attempt to reread a column value and make sure that you read columns in ascending column-index order.

JZ0P8

The RSMDA Column Type Name you requested is unknown.

Description: jConnect was unable to determine the name of a column type in the ResultSetMetaData.getColumnTypeName() method.

Action: Check to make sure that your database has the most recent stored procedures for metadata.

JZ0P9

A COMPUTE BY query has been detected. That type of result is unsupported and has been cancelled.

Description: The query you executed returned COMPUTE results, which are not supported by jConnect.

Action: Change your query or stored procedure so it does not use COMPUTE BY.

JZ0PA

The query has been cancelled and the same response discarded.

Description: A cancel was probably issued by another statement on the connection.

Action: Check the chain of SQL exceptions and warnings on this and other statements to determine the cause.

JZ0PB

The server does not support a requested operation.

Description: When jConnect creates a connection with a server, it informs the server of capabilities it wants supported and the server informs jConnect of the capabilities that it supports. This error message is sent when an application requests an operation that was denied in the original capabilities negotiation.

For example, if the database does not support precompilation of dynamic SQL statements, and your code invokes SybConnection.prepareStatement(sql_stmt, dynamic), and dynamic is set to "true," jConnect will generate this message.

Action: Modify your code so that it does not request an unsupported capability.

JZ0R0

Result set has already been closed.

Description: The ResultSet.close() method has already been called on the result set object; you cannot use the result set for anything else.

Action: Fix the code so that ResultSet object references are nulled whenever a result set is closed.

JZ0R1

Result set is IDLE as you are not currently accessing a row.

Description: The application has called one of the ResultSet.getXXX column-data retrieval methods, but there is no current row; the application has not called ResultSet.next(), or ResultSet.next() returned "false" to indicate that there is no data.

Action: Check that rs.next() is set to "true" before calling rs.getXXX.

JZ0R2

No result set for this query.

Description: You used Statement.executeQuery(), but the statement returned no rows.

Action: Use executeUpdate for statements returning no rows.

JZ0R3

Column is DEAD. This is an internal error. Please report it to Sybase technical support.

Action: See message text.

JZ0R4

Column does not have a text pointer. It is not a text/image column or the column is NULL.

Description: You cannot update a text/image column if it is NULL. A NULL text/image column does not contain a text pointer.

Action: Make sure that you are not trying to update or get a text pointer to a column that does not support text/image data. Make sure that you are not trying to update a text/image column that is NULL. Insert data first, then make the update.

JZ0RM

refreshRow may not be called after updateRow or deleteRow.

Description: After updating a row in the database with SybCursorResult.updateRow(), or deleting it with SybCursorResult.deleteRow(), you used SybCursorResult.refreshRow() to refresh the row from the database.

Action: Do not attempt to refresh a row after updating it or deleting it from the database.

JZ0S0

Statement state machine: Statement is BUSY.

Description: The only time this error is raised is from the Statement.setCursorname() method, if the application is trying to set the cursor name when the statement is already in use and has non-cursor results that need to be read.

Action: Set the cursor name on a statement before you execute any queries on it, or call Statement.cancel() before setting the cursor name, to make sure that the statement isn't busy.

JZ0S1

Statement state machine: Trying to FETCH on IDLE statement.

Description: An internal error occurred on the statement.

Action: Close the statement and open another one.

JZ0S2

Statement object has already been closed.

Description: The Statement.close() method has already been called on the statement object; you cannot use the statement for anything else.

Action: Fix the application so that statement object references are nulled out whenever a statement is closed.

JZ0S3

The inherited method _____ cannot be used in this subclass.

Description: PreparedStatement does not support executeQuery(String), executeUpdate(String), or execute(String).

Action: If you want to pass a query string, use Statement, not PreparedStatement.

JZ0S4

Cannot execute an empty (zero-length) query.

Action: Do not execute an empty query ("").

JZ0S8

An escape sequence in a SQL Query was malformed: '_____'.

Description: This error results from bad escape syntax.

Action: Check JDBC documentation for correct syntax.

JZ0S9

Cannot execute an empty (zero-length) query.

Action: Do not execute an empty query ("").

JZ0SA

Prepared Statement: Input parameter not set, index: _____.

Action: Make sure that each input parameter has a value.

JZ0SB

Parameter index out of range: _____.

Description: You have attempted to get, set, or register a parameter that goes beyond the maximum number of parameters.

Action: Check the number of parameters in your query.

JZ0SC

Callable Statement: attempt to set the return status as an InParameter.

Description: You have prepared a call to a stored procedure that returns a status, but you are trying to set parameter 1, which is the return status.

Action: Parameters that you can set start at 2 with this type of call.

JZ0SD

No registered parameter found for output parameter.

Description: This indicates an application logic error. You attempted to call getXXX() or wasNull() on a parameter, but you have not read any parameters yet, or there are no output parameters.

Action: Check to make sure that the application has registered output parameters on the CallableStatement, that the statement has been executed, and that the output parameters were read.

JZ0SE

Invalid object type specified for setObject().

Description: Illegal type argument passed to PreparedStatement.setObject.

Action: Check the JDBC documentation. The argument must be a constant from java.sql.Types.

JZ0SF

No Parameters expected. Has query been sent?

Description: You tried to set a parameter on a statement with no parameters.

Action: Make sure the query has been sent before you set the parameters.

JZ0SG

An RPC did not return as many output parameters as the application had registered for it.

Description: This error occurs if you call CallableStatement.registerOutParam() for more parameters than you declared as "OUTPUT" parameters in the stored procedure. See "RPC Returns Fewer Output Parameters Than Registered" for more information.

Action: Check your stored procedures and registerOutParameter calls. Make sure that you have declared all of the appropriate parameters as "OUTPUT." Look at the line of code that reads:

create procedure yourproc (@p1 int OUTPUT, ...

Note:
If you receive this error while using Adaptive Server Anywhere (previously known as SQL Anywhere), upgrade to Adaptive Server Anywhere version 5.5.04.

JZ0SH

A static function escape was used, but the metadata accessor information was not found on this server.

Action: Install metadata accessor information before using static function escapes.

JZ0SI

A static function escape _____ was used which is not supported by this server.

Action: Do not use this escape.

JZ0SJ

Metadata accessor information was not found on this database.

Action: Install metadata information before making metadata calls.

JZ0SM

Unsupported SQL type _____.

Action: Do not use Types.NULL, Types.OTHER, or PreparedStatement.setObject(null)

JZ0SN

setMaxFieldSize: field size cannot be negative.

Action: Use a positive value or zero (unlimited) when calling setMaxFieldSize.

JZ0T2

Listener thread read error.

Action: Check your network communications.

JZ0T3

Read operation timed out.

Description: The time allotted to read the response to a query was exceeded.

Action: Increase the timeout period by calling Statement.setQueryTimeout().

JZ0T4

Write operation timed out. Timeout in milliseconds: _____.

Description: The time allotted to send a request was exceeded.

Action: Increase the timeout period by calling Statement.setQueryTimeout().

JZ0T5

Cache used to store responses is full.

Action: Use default or larger value for the STREAM_CACHE_SIZE connection property.

JZ0T6

Error reading tunneled TDS URL.

Description: The tunneled protocol failed while reading the URL header.

Action: Check the URL you defined for the connection.

JZ0T7

Listener thread read error -- caught ThreadDeath. Check network connection.

Action: Check the network connections and try to run the application again. If the threads continue to be aborted, contact Sybase Technical Support.

JZ0T9

Request to send not synchronized. Please report this error to Sybase Technical Support.

Action: See message text.

JZ0TC

Attempted conversion between an illegal pair of types.

Description: Conversion between a Java type and a SQL type failed.

Action: Check the requested type conversion to make sure it is supported in the JDBC specification.

JZ0US

The SybSocketFactory connection property was set, and the PROXY connection property was set to the URL of a servlet. The jConnect driver does not support this combination. If you want to send secure HTTP from an applet running within a browser, use a proxy URL beginning with "https://".

Action: See message text.

S0022

Invalid column name '_____'.

Description: You attempted to reference a column by name and there is no column with that name.

Action: Check the spelling of the column name.

ZZ00A

The method _____ has not been completed and should not be called.

Description: You attempted to use a method that is not implemented.

Action: Check the release bulletin that came with your version of jConnect for further information. You can also check the jConnect Web page at http://www.sybase.com to see whether a more recent version of jConnect implements the method. If not, do not use the method.


Sybase(R) jConnect for JDBC(TM) Programmer's Reference - 29 Jan 1999

Copyright 1999 © Sybase, Inc. All Rights Reserved.



Back to Top
© Copyright 2010, Sybase Inc.