SQL Exception and Warning Messages

010AF

SEVERE WARNING: An assertion has failed, please use devclasses todetermine the source of this serious bug. 
Message = _____.

Action: Use the devclasses debug classes to determine the reason for this message, and report the problem to SAP Technical Support.

010CP

010DF

Attempt to set database at login failed. Error message:______.

Description: SAP jConnect cannot connect to the database specified in the connection URL.

Action: Be sure the database name in the URL is correct. Also, if you are connecting to SAP SQL Anywhere, use the SERVICENAME connection property to specify the database.

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.” SAP 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: Be sure your application defines the connection property only once. However, you may want your 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.

010HA

The server denied your request to use the high-availability feature. Please reconfigure your database, or do 
not request a high-availability session.

Action: Reconfigure the server to support high availability failover or do not set REQUEST_HA_SESSION to true

010HD

SAP Adaptive Server high-availability failover is not supported by this type of database server.

Action: Connect only to database servers that support high availability failover.

010HN

The client did not specify a SERVICE_PRINCIPAL_NAME Connection property. Therefore, jConnect is using the hostname
of _____ as the service principal name

Action: Explicitly specify a service principal name using the connection property.

010HT

Hostname property truncated, maximum length is 30.

Action: No action is necessary, since this is just a warning to indicate that SAP jConnect is truncating the name to 30 bytes. However, if you wish to avoid this warning, you should set the HOSTNAME to a string less than or equal to 30 bytes in length.

010KF

The server rejected your Kerberos login attempt. Most likely, this was because of a Generic Security Services (GSS)exception. Please check your Kerberos environment and configuration.

Action: Check your Kerberos environment, and make sure that you authenticated properly to the KDC. See Security for more information.

010MX

Metadata accessor information was not found on this database. Please install the required tables as mentioned 
in the jConnect documentation. Error encountered while attempting to retrieve metadata information: _____.

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

Action: Be sure that stored procedures for providing metadata are installed on the server. See Installing Stored Procedures in the SAP jConnect for JDBC Installation Guide.

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, 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. You can also prevent SAP jConnect from returning this warning, and possibly see performance improvement, by setting the DISABLE_UNPROCESSED_PARAM_WARNINGS connection property to true.

010P6

A row was received and ignored.

Description: An unexpected object of type 0xD1 was encountered in the result set being processed and has been ignored.

Action: Check the query that generated the result set and correct as required.

010PF

One or more jars specified in the PRELOAD_JARS connection property could not be loaded.

Description: This happens when using the DynamicClassLoader with the PRELOAD_JARS connection property set to a comma-delimited list of .jar file names. When the DynamicClassLoader opens its connection to the server from which the classes are to be loaded, it attempts to preload all the .jar files mentioned in this connection property. If one or more of the .jar file names specified does not exist on the server, the above error message results.

Action: Verify that every .jar file mentioned in the PRELOAD_JARS connection property for your application exists and is accessible on the server.

010PO

Property LITERAL_PARAM has been reset to false because DYNAMIC_PREPARE was set to true.

Description: To use precompiled dynamic statements, allow for parameters to be sent to those statements (if the statements take parameters). Setting LITERAL_PARAMS to true forces all parameters to be sent as literal values in the SQL that you send to the server. Therefore, you cannot set both properties to true.

Action: To avoid this warning, do not set LITERAL_PARAMS to true when you want to use dynamic SQL. See Performance Tuning for Prepared Statements in Dynamic SQL.

010RC

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

Description: See Use Cursors with Result Sets for more information about what result set types and concurrencies are available in SAP jConnect

Action: Request a supported type and concurrency combination for the result set.

010SJ

Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation.

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 the jConnect for JDBC Installation Guide. 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: Upgrade your database, or make sure that the latest version of metadata information is installed on it.

010SL

Out-of-date metadata accessor information was found on this database. Ask your database administrator to load the latest scripts.

Description: The metadata information on the server is old and needs to be updated.

Action: Install the stored procedures for returning metadata that come with SAP jConnect. See Installing Stored Procedures in the SAP jConnect for JDBC Installation Guide.

010SM

This database does not support the initial proposed set of capabilities, retrying.

Description: SAP Adaptive Server Enterprise versions 11.9.2 and lower had an issue that caused them to reject logins from clients that requested capabilities that the servers did not have. This warning indicates that SAP jConnect has detected this condition and is retrying the connection using the greatest number of capabilities that the server can accept. When SAP jConnect encounters this bug, it attempts to connect to the server twice.

Action: Clients can safely ignore this warning, but to eliminate the warning and ensure that SAP jConnect makes only one connection attempt, they can set the ELIMINATE_010SM connection property to true. Do net set this property to true when connecting to SAP Adaptive Server versions 12.0 and later.

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.

010SQ

The connection or login was refused, retrying connection with the host/port address.

Description: The CONNECTION_FAILOVER connection property is set to true, and SAP jConnect cannot to connect to one of the database servers in the list of servers to which to connect. Therefore, SAP jConnect now tries to connect to the next server in the list.

Action: No action is required, as long as SAP jConnect can to connect to another database server. However, determine why SAP jConnect could not to connect to the particular server that caused the connection warning to be issued.

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 SAP jConnect, and has responded with a different character set. SAP jConnect accepts the change, and performs 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.

010TQ

jConnect could not determine the server's default character set. This is likely because
of a metadata problem. Please install the required tables as mentioned in the jConnect documentation. 
The connection is defaulting to the ascii_7 character set, which can handle only characters in the range from 0x00 through 0x7F.

Description: When this occurs, the only characters that are guaranteed to translate properly are the first 127 ASCII characters. Therefore, SAP jConnect reverts to 7-bit ASCII. The message is strictly informational and has no further consequences.

Action: Install the stored procedures for returning metadata that comes with SAP jConnect. See Installing Stored Procedures in the SAP jConnect for JDBC Installation Guide.

010UF

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

Description: SAP jConnect cannot connect to the database specified in the connection URL. Two possibilities are:

Action: Make sure the database name in the URL is correct. Make sure the stored procedures for returning metadata are installed on the server. See Installing Stored Procedures in the SAP jConnect for JDBC Installation Guide and SAP jConnect for JDBC 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 SAP jConnect driver connection properties.

0100V

The version of TDS protocol being used is too old. Version: _____.

Description: SAP jConnect requires version 5.0 or later.

Action: Use a server that supports the required version of TDS. See the System Requirements in the SAP jConnect Installation Guide.

01S07

Adaptive Server may round or truncate nanosecond values.

Description: A time value more precise than 1/300th of a second encountered. Because SAP Adaptive Server does not support such precision, jConnect rejected the value.

Action: Make sure that time values are of precision up to 1/300th of a second.

01S08

This connection has been enlisted in a Global transaction. All pending statements on the current local transaction (if any) have been rolled back.

Description: SAP jConnect issues rollback to clear out any current local transactions. This occurs when a global transaction has been enlisted, after issuing XAResource.start().

Action: Either commit or roll back active local transactions before issuing the XAResource.start() method.

01S09

The local transaction method ___________ cannot be used while a global transaction is active on this connection.

Description: An example of a local operation is calling the commit() method on the connection. Other operations that cannot be used include: rollback(), rollback(Savepoint), setSavepoint(), setSavepoint(String), releaseSavepoint(Savepoint), and setAutoCommit().

Action: Keep local transactions separate from global transactions. Complete all local transactions and their operations before starting the global transaction.

01S10

The local transaction method _____ cannot be used on a pre-System 12 XAConnection.

Description: You have used a local transaction method that does not work with versions earlier than SAP SQL Anywhere version 12.

Action: Do not use the method.

01S11

WARNING: Your data might be truncated.

Description: The user-specified length of a stream or LOB is greater than the limit (Integer.MAX_VALUE) in a ResultSet.updateXXX method.

Action: Make sure that the length is within the limit.

01S12

Unable to continue with HOMOGENEOUS_BATCH protocol, falling back to normal batching.

Description: When DYNAMIC_PREPARE is set to false, SAP Adaptive Server does not send parameter metadata. When HOMOGENEOUS_BATCH is true, SAP jConnect requires this information for optimization. Thus, jConnect reverts to normal batching.

Action: Use optimized batching (HOMOGENEOUS_BATCH set to true) with precompiled dynamic SQL prepared statements only (DYNAMIC_PREPARE set to true).

01S13

Connected Adaptive Server server does not support the set option 'logbulkcopy' needed for logging BCP. 
Falling back to normal bulk load without logging which is equivalent to setting ENABLE_BULK_LOAD=BCP.

Description: If the SAP Adaptive Server is earlier than 15.7 ESD #1 and does not support logged bulk loading, SAP jConnect reverts to normal batching.

Action: Use ENABLE_BULK_LOAD=LOG_BCP setting only with SAP Adaptive Server 15.7 ESD #1 or later.

01ZZZ

Password has expired Please set the NEWPASSWORD property with the new password or use sp_password to change passwords.

Action: Reset the password for connecting to SAP Adaptive Server.

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 tunnelling 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 is detected from a lower layer. When such I/O exceptions are caught, they are rethrown as SQL exceptions using the ERR_IO_EXCEPTION JZ006 sqlstate. These errors are often the result of network communication problems. If the I/O exception causes the database connection to be closed, SAP jConnect chains a JZ0C1 exception to the JZ006. Client applications can look for the JZ0C1 exception in the chain to see if the connection is still usable.

Action: Examine the text of the original I/O exception message, and proceed from there.

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: Verify the call to the getXXX method and the text of the original query, or call rs.next.

JZ009

Error encountered in conversion. Error message: _____.

Description: Possibilities include:

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

JZ00A

Invalid precision and scale specified for a numeric value.

Description: When using the setBigDecimal method, the BigDecimal value is set to either a precision value of less than 1, a negative scale value, a precision less than the scale value, or precision value greater than 127.

Action: Examine the query and correct to specify a legal precision/scale value.

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 SAP jConnect. For long, consider using a SAP jConnect numeric. There is no solution for Bignum.

JZ00C

The precision and scale specified cannot accommodate numeric value _____.

Description: When using the setBigDecimal method, the BigDecimal value has a precision or scale that exceeds the specified precision or scale.

Action: Make sure that the specified precision and scale can accommodate the BigDecimal value.

JZ00E

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

Action: Use a separate statement to delete or update a cursor. See Use Cursors with Result Sets.

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: 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.

JZ00I

Invalid scale. The specified scale must be >=0.

Description: The scale value must be greater than zero.

Action: Be sure the scale value is not negative.

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.

JZ00M

Login timed out. Check that your database server is running on the host and port number you specified. 
Also check the database server for other conditions (such as a full tempdb) that might be causing it to hang.

Action: Follow the recommended actions in the error message.

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 noninteger value was specified for a numeric connection property.

Action: Specify an integer value for the connection property.

JZ012

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

Action: Contact SAP Technical Support.

JZ013

Error obtaining JNDI entry: _____.

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

JZ014

You may not setTransactionIsolation(Connection.TRANSACTION_NONE). This level cannot be set; it can only be returned by a server.

Action: Check your application code, where it calls Connection.setTransactionIsolation, and verify the value you are passing to the method.

JZ015

Illegal value set for the GSSMANAGER_CLASS connection property. 
The property value must be a String or an Object that extends org.ietf.jgss.GSSManager.

Action: Check the value to which you set the GSSMANAGER_CLASS property.

JZ017

Savepoint is not valid.

Description: You have specified a nonexistent savepoint for rollback or release.

Action: Examine the query and correct to specify an existing savepoint.

JZ018

This method can not be applied to this type of savepoint.

Description: The getSavepointId() method does not work on named savepoints (which have no ID), and the getSavepointName() method does not work on unnamed savepoints (which have no name).

Action: Examine the query and correct.

JZ019

Error obtaining SERVERNAME : _____.

Description: The URL set using jdbc::jndi:file does not specify either the sql.ini file (Windows) or the interfaces file (UNIX) or a server name.

Action: Examine the URL command and correct.

JZ021

The Specified _____ file not found.

Description: The sql.ini file (Windows) or the interfaces file (UNIX) specified in the connection URL is not found.

Action: Check the connection URL and correct.

JZ022

The Specified _____ file has an unknown format.

Description: The connection URL string in the sql.ini file (Windows) or the interfaces file (UNIX) is not in the correct format.

Action: Check the connection URL string and correct.

JZ024

The Specified Server : _____ has no entry in the interfaces/sql.ini file :_____.

Action: Check the connection URL string and correct.

JZ025

The TLI format for Specified Server in interfaces/sql.ini is Invalid.

Action: Check the settings and correct.

JZ026

The Specified Protocol : _____ for Server : _____ in interfaces/sql.ini file :_____ is not Supported.

Description: A protocol other than TLI, TCP, and NLWNSCK is specified in the sql.ini file (Windows) or the interfaces file (UNIX).

Action: Specify a supported protocol.

JZ027

The Specified SECMECH entrys: _____ for Server : _____ in interfaces/sql.ini file :_____ are not Supported.

Description: An invalid value is specified in the Kerberos connection URL.

Action: Examine the URL and correct.

JZ028

Illegal value set for JCE_PROVIDER_CLASS connection property. The property value must be a fully qualified provider 
class name passed as a String or an instance of java.security.Provider.

Action: Specify a legal value.

JZ029

Error looking up address for ALTERNATE_SERVER_NAME _____,(_____).

Description: SAP jConnect cannot locate the server specified with the ALTERNATE_SERVER_NAME property using the SAP SQL Anywhere UDP discovery protocol.

Action: Check the server name specified with the ALTERNATE_SERVER_NAME connection property and correct.

JZ030

JZ031

Failed to unwrap the object of _____.

Description: SAP jConnect cannot unwrap the object of a custom class because the custom class is not in the classpath.

Action: Add the class to classpath.

JZ032

JZ033

Unknown Blob type returned by the server.

Description: SAP jConnect cannot map the SAP Adaptive Server datatype of the column to a BLOB datatype.

Action: Make sure that the SAP Adaptive Server column is convertible to a BLOB datatype.

JZ034

The connected server is not capable of handling Large Objects [LOB].

Action: Use the regular stream methods to access LOB.

JZ035

JZ036

JZ037

JZ038

JZ040

_____ operation failed. The _____ has been closed alread.

Description: The read (write) operation has failed as input stream or LOB reader (output stream or LOB writer) has already closed

Action: Check the application to locate the reason of the conflict and correct.

JZ041

_____ operation failed on the _____.

Description: The read(write)(available()) operation has failed as input stream or reader (output stream or writer)(input stream) has already closed.

Action: Check the application to locate the reason of the conflict and correct.

JZ042

JZ043

JZ044

JZ0BD

JZ0BI

setFetchSize: The fetch size should be set with the following restrictions – 0 <= rows <= 
(maximum number of rows in the ResultSet).

Action: Verify that you are calling setFetchSize with the parameter falling within the above range of values.

JZ0BJ

JZ0BP

JZ0BR

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

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

JZ0BS

Batch Statements not supported.

Action: Install or update the SAP jConnect metadata stored procedures on your database with the latest versions.

JZ0BT

The _____ method is not supported for ResultSets of type _____.

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

JZ0C0

Connection is already closed.

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

JZ0C1

An IOException occurred which closed the connection.

Description: The connection cannot be used for any further database activity. If this exception occurs, it can always be found in an exception chain with the JZ006 Exception.

Action: Determine the cause of the IOException that disrupted the connection.

JZ0CL

JZ0D4

Unrecognized protocol in JDBC URL:_____.

Description: You specified a connection URL using a protocol other than TDS, which is the only protocol currently supported by SAP 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::Tds:host:port

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

jdbc::jndi:

JZ0D5

Error loading protocol _____.

Action: Check the settings for the CLASSPATH system variable.

JZ0D6

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: Please report this error to SAP Technical Support.

JZ0F1

SAP Adaptive Server Enterprise high-availability failover connection was requested but the companion server address is missing.

Description: When you set the REQUEST_HA_SESSION connection property to true, you must also specify a failover server.

Action: You can specify the secondary server using the SECONDARY_SERVER_HOSTPORT connection property, or you can set the secondary server using JNDI.

JZ0F2

SAP Adaptive Server Enterprise high-availability failover has occurred. The current transaction is aborted, but the connection is still usable. Retry your transaction.

Description: The back-end database server to which you were connected stopped responding, but because you failed over to a secondary server, the database connection is still usable.

Action: Client code should catch this exception, then restart the transaction from the last committed point. Assuming you properly handle the exception, you can continue executing JDBC calls on the same connection object.

JZ0FP

Incorrect value passed for parameter ____.

Description: The value of the parameter specified for the state of the current result set is invalid.

Action: Make sure the value is valid: CLOSE_CURRENT_RESULT, KEEP_CURRENT_RESULT, CLOSE_ALL_RESULTS.

JZ0GC

JZ0GK

The _____ array can not be null and has to contain only one key.

Description: The autogenerated key column name/index array is either NULL or contains more than one key. Only one key is allowed in the array since it relates to the IDENTITY column.

Action: Check the query and correct.

JZ0GN

Error instantiating the class ___ as a GSSManager. The exception was ____. Please check your
CLASSPATH and make sure the GSSMANAGER_CLASS property value refers to a fully qualified class name of a 
GSSManager implementation.

Action: Make sure your CLASSPATH environment variable includes any .jar files required by your third-party GSSManager implementation.

JZ0GS

A Generic Security Services API exception occurred. The major error code is ___. The major error message is ___. 
The minor error code is ___. The minor error message is ____.

Action: Examine the major and minor error codes and messages. Check your Kerberos configuration. See Security.

JZ0H0

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

Action: Report this error to SAP Technical Support.

JZ0H1

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

Action: Report this error to SAP 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.

JZ0I3

Incorrect argument _____ passed to method _____.

Action: Verify in the product documentation or in the JDBC API that the correct argument was passed.

JZ0I5

An unrecognized CHARSET property was specified: _____.

Action: Enter a valid character-set code for the CHARSET 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 SAP jConnect client that supports all the characters you need to send to the server. You may need to install a different character set on the server, too. Also, if you are using SAP jConnect version 6.05 or later, and SAP Adaptive Server Enterprise 12.5 or later, you can send your data to the server as unichar/univarchar datatypes.

JZ0I7

No response from proxy gateway.

Description: The connection cannot be established as there is no response from proxy gateway specified with the PROXY connection property.

Action: Check the PROXY setting and correct.

JZ0I8

Proxy gateway connection refused.  Gateway response: %1s.

Action: Check the proxy gateway settings.

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 SAP jConnect client that supports all the characters you need to send to the server. You may need to install a different character set on the server, too.

JZ0IB

JZ0IR

getXXX may not be called on a column after it has been updated in the result set with a java.io.Reader.

Action: Remove the getXXX call on the ResultSet column you updated using a reader.

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 these SybResultSet methods: getAsciiStream, getUnicodeStream, getBinaryStream. SAP jConnect does not support this usage.

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

JZ0J0

JZ0LA

Failed to instantiate Cipher object. Transformation %1s is not implemented by any of the loaded JCE providers.

Action: Make sure that the implementation is specified correctly in the JCE_PROVIDER_CLASS connection property of the CLASSPATH.

JZ0LC

You cannot call the ____ method on a ResultSet which is using a language cursor to fetch rows. 
Try setting the LANGUAGE_CURSOR connection property to false.

Description: The application tried to call one of the ResultSet cursor scrolling methods on a ResultSet which was created with a language cursor.

JZ0MD

ResultSet metadata is not available.

Action: Install the metadata stored procedures.

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: In the URL, make sure that the port number consists only of numeric characters.

JZ0NF

JZ0NK

Generated keys are not available because either the Statement.NO_GENERATED_KEYS was used or no keys were automatically generated.

Description: The getGeneratedKeys() method cannot return the autogenerated keys because the statement was executed with .NO_GENERATED_KEYS or the statement produced no autogenerated keys.

Action: Use getGeneratedKeys() only on statements executed with .RETURN_GENERATED_KEYS, or those that are expected to autogenerate keys.

JZ0NS

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 SAP Open Server application, it may indicate an error in the SAP Open Server application that causes the SAP Open Server to send unexpected sequences of results.

Action: Use the com..utils.Debug(true, “ALL”) debugging tools to try to determine what unexpected result is seen, and to understand its causes.

JZ0P4

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 be sure that you read columns in ascending column-index order.

JZ0P8

The RSMDA Column Type Name you requested is unknown. This is a SAP internal error; please report it to technical support.

Description: SAP jConnect cannot determine the name of a column type in the ResultSetMetaData.getColumnTypeName method.

Action: Be 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.

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.

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 SAP jConnect creates a connection with a server, it informs the server of capabilities it wants supported, and the server informs SAP 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, SAP jConnect generates this message.

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

JZ0PC

The number and size of parameters in your query require wide table support. But either the server does not offer such support, or it was not requested
during the login sequence. Try setting the JCONNECT_VERSION property to >=6 if you wish to request widetable support.

Description: You are trying to execute a statement with a larger number of parameters than the server is configured to handle. The number of parameters that can produce this exception varies, depending on the datatypes of the data you are sending. You never get this exception if you are sending 481 or fewer parameters.

Action: Run the query against an SAP Adaptive Server 12.5 or later server. When you connect to the database, set the JCONNECT_VERSION property to “6”.

JZ0PD

The size of the query in your dynamic prepare is large enough that you require widetable support. 
But either the server does not offer such support, or it was not requested during the login sequence. 
Try setting the JCONNECT_VERSION property to >=6 if you wish to request widetable support.

Description: You are trying to execute a dynamic prepared statement with larger number of parameters than the server is configured to handle.

Action: Run the query against an SAP Adaptive Server 12.5 or later server. When you connect to the database, set the JCONNECT_VERSION property to “6”.

JZ0PE

The number of columns in your cursor declaration OR the size of your cursor declaration itself are large enough 
that you require widetable support. But either the server does not offer such support, or it was not requested during the 
login sequence. Try setting the JCONNECT_VERSION property to >= 6 if you wish to request wide table support.

Description: This error can occur when your SELECT statement tries to return data from more than 255 columns, or when the actual length of the SELECT statement is very large (greater than approximately 65500 characters).

Action: Run the query against a version 12.5 or later SAP Adaptive Server. When you connect to the database, set the JCONNECT_VERSION property to “6”.

JZ0PN

Specified port number of ____ was out of range. Port numbers must meet the following conditions: 0<= portNumber <=65535.

Action: Check the port number that is specified in the database URL.

JZ0R0

Result set has already been closed.

Action: Fix the code so that ResultSet object references are set to null 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.nextreturned false to indicate that there is no data.

Action: Verify 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

JZ0R4

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

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

JZ0R5

The ResultSet is currently positioned beyond the last row. You cannot perform a get* operation to read data in 
this state.

Action: Alter the code so that it does not attempt to read column data when the ResultSet is positioned beyond the last row.

JZ0RD

You cannot call any of the ResultSet.get* methods on a row that has been deleted with the deleteRow() method.

Action: Alter the code so that the application does not attempt to retrieve data from a deleted row.

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 noncursor 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 is not busy.

JZ0S1

Statement state machine: Trying to FETCH on IDLE statement.

Action: Close the statement and open another one.

JZ0S2

Statement object has already been closed.

Action: Fix the application so that statement object references are set to null whenever a statement is closed.

JZ0S3

The inherited method _____ cannot be used in this subclass.

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

Action: To pass a query string, use Statement, not PreparedStatement.

JZ0S4

Cannot execute an empty (zero-length) query.

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

JZ0S5

The local transaction method ____ cannot be used while a global transaction is active on this connection.

Description: This exception can occur when using distributed transactions.

Action: See Distributed Transaction Management Support.

JZ0S6

The local transaction method _____ cannot be used on a pre-System 12 XAConnection.

Description: This exception can occur when using distributed transactions.

Action: See Distributed Transaction Management Support.

JZ0S8

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

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: Be sure that each input parameter has a value.

JZ0SB

Parameter index out of range: _____.

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.

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, ...

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.

JZ0SK

The oj escape is not supported for this type of database server. Workaround: use server-specific outer join syntax,
if supported. Consult server documentation.

Action: In addition to following the instructions in the message, also install the latest version of the SAP jConnect metadata.

JZ0SL

Unsupported SQL type _____.

Action: If possible, declare the parameter to be of a type supported by SAP jConnect. Do not use Types.NULL or PreparedStatement.setObject (null).

JZ0SM

JZ0SN

JZ0SO

Invalid ResultSet concurrency type:_____.

Action: Check that your declared concurrency is either ResultSet.CONCUR_READ_ONLY or ResultSet.CONCUR_UPDATABLE.

JZ0SP

Invalid ResultSet type:_____.

Action: Check that your declared ResultSet type is ResultSet.TYPE_FORWARD_ONLY or ResultSet.TYPE_SCROLL_INSENSITIVE. SAP jConnect does not support the ResultSet.TYPE_SCROLL_SENSITIVE ResultSet type.

JZ0SQ

In valid UDT type ____.

Description: When calling the DatabaseMetaData.getUDTs method, jConnect throws this exception if the user-defined type is not Types.JAVA_OBJECT, Types.STRUCT, or Types.DISTINCT.

Action: Use one of the three UDTs mentioned.

JZ0SR

JZ0SS

JZ0ST

JZ0SU

 A Date or Timestamp parameter was set with a year of ______, but the server can only support year values 
between _____ and _______. If you’re trying to send data to date or timestamp columns or parameters on Adaptive Server Anywhere,
you may wish to send your data as Strings, and let the server convert them.

Description: SAP Adaptive Server Enterprise and SAP SQL Anywhere have different allowable ranges for datetime and date values. datetime values must have years greater or equal to 1753. The date datatype, however, can hold years greater or equal to 1.

Action: Make sure that the date/timestamp value you are sending falls in the acceptable range.

JZ0SV

Combination of setting parameters by name and by index is not allowed in the same CallableStatement.

Description: The CallableStatement has parameters specified by name and by index (ordinal position). Mixed use is invalid.

Action: Specify parameters by name only or by index (ordinal position) only.

JZ0SW

Invalid ResultSet holdability type: ____.

Description: You have specified an invalid value with the setHoldability() method.

Action: Use the legal values only: HOLD_CURSORS_OVER_COMMIT or CLOSE_CURSORS_AT_COMMIT.

JZ0T2

Listener thread read error.

Action: Check your network communications.

JZ0T3

Read operation timed out.

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

JZ0T4

Write operation timed out. Timeout in milliseconds: _____.

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 abort, please contact SAP Technical Support.

JZ0T8

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.

JZ0TD

Caught ThreadDeath.

Description: The calling application thread was killed while SAP jConnect was performing a timed I/O operation.

Action: Check the application code to locate the conflict and correct.

JZ0TE

Attempted conversion between an illegal pair of types. Valid database types are: ‘_________'.

Description: The database column datatype and the datatype requested in the ResultSet.getXXX call are not implicitly convertible.

Action: Use one of the valid datatypes listed in the error message.

JZ0TI

jConnect cannot make a meaningful conversion between the database type of _________ and the requested type of _________.

Description: This kind of exception can occur, for example, if an application tries to call ResultSet.getObject(int, Types.DATE) on a time value that is returned from the database.

Action: Make sure that the database datatype is implicitly convertible to the object type you want to retrieve.

JZ0TO

Read operation timed out.

Description: This exception occurs when there is a socket read timeout.

Action: Increase the timeout period by calling Statement.setQueryTimeout. Also, check the query or stored procedure you are executing to determine why it is taking longer than expected.

JZ0TS

Truncation error trying to send __________.

Description: The application specified a string that was longer than the length that the application wanted to send. Therefore, the string is truncated to the declared length.

Action: Set the length properly to avoid truncation.

JZ0US

JZ0XC

____________ is an unrecognized transaction coordinator type.

Description: The metadata information indicates that the server supports distributed transactions, but SAP jConnect does not support the protocol being used.

Action: Verify that you have installed the latest metadata scripts. If the error persists, please contact SAP Technical Support.

JZ0XS

The server does not support XA-style transactions. Please verify that the transaction
feature is enabled and licensed on this server.

Description: The server to which SAP jConnect attempted a connection does not support distributed transactions.

Action: Do not use XADataSource with this server, or upgrade or configure the server for distributed transactions.

JZ0XU

Current user does not have permission to do XA-style transactions. Be sure user has _______ role.

Description: The user connected to the database is not authorized to conduct distributed transactions, most likely because the user does not have the proper role.

Action: Grant the user the role shown in the error message, or have another user with that role conduct the transaction.

JZBK1

SybBCP class is NOT initialized Please Re-Run MDA sqls to update the MDA stored procedures.

Action: Install MDA stored procedures.

JZBK3

Bulk load table does not exists.

Action: Correct the table name.

JZBK4

Illegal usage of sql statements mixed with batches in bcp/arrayinsert mode.

Description: During a batch operation, you are attempting to execute a nonbatch operation.

Action: Wait for the batch operation to complete before attempting a nonbatch operation.

JZBK5

JZBK6

JZBK7

JZBKI

Invalid value set for property ENABLE_BULK_LOAD.

Action: Set ENABLE_BULK_LOAD to one of the valid values only –ARRAYINSERT_WITH_MIXED_STATEMENTS, ARRAYINSERT, BCP, or LOG_BCP.

JZNNA

Column does not allow null values.

Description: You attempted to set a bit-type column to a NULL value using setNull() in a prepared statement.

Action: Examine the query and correct to set a value of 0 or 1 for bit-type columns.

S0022

Invalid column name ‘_____’.

Action: Check the spelling of the column name, and that the named column exists.

ZZ00A

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

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