sybase：SQL Exception and Warning Messages大全

内容全部来自sybase官方网站：

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc39001.0707/html/prjdbc0707/CHDGJJIG.htm

网页不好看，但是可以方便大家搜索

这里有个文件的下载地址：https://files.cnblogs.com/files/baby-lijun/sybase%E9%94%99%E8%AF%AF%E7%A0%81%E5%A4%A7%E5%85%A8.rar

 

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

SQL state	Message/description/action
010AF	SEVERE WARNING: An assertion has failed, please use devclasses todetermine the source of this serious bug. Message = _____. Description: An internal assertion in the jConnect driver has failed. Action: Use the devclasses debug classes to determine the reason for this message and report the problem to Sybase Technical Support.
010CP	AutoCommit option has changed to true. All pending statements on this transaction (if any) are committed. Action: See message text.
010DF	Attempt to set database at login failed. Error message:______. Description: jConnect cannot connect to the database specified in the connection URL. Action: Be sure the database name in the URL is correct. Also, if connecting to 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.” Connection property names are not case-sensitive; 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: 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. Description: The server to which jConnect attempted an HA-enabled connection did not allow the connection. Action: Reconfigure the server to support high availability failover or do not set REQUEST_HA_SESSION to "true."
010HD	Sybase high-availability failover is not supported by this type of database server. Description: The database to which jConnect attempted a connection does not support high availability failover. 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: Make sure to explicitly specify a service principal name using the connection property.
010HT	Hostname property truncated, maximum length is 30. Description: You provided a string greater than 30 characters for the HOSTNAME connection property, or the host machine on which the jConnect application is running has a name longer than 30 bytes in length. Action: No action is necessary, since this is just a warning to indicate that 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 Chapter 3, “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 Chapter 3 of the 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, 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. You can also prevent jConnect from returning this warning, and possibly get a 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 was 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: If you wish to use precompiled dynamic statements, then you must 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 wish to use dynamic SQL. See “Performance tuning for prepared statements in dynamic SQL” for more information.
010RC	The requested ResultSet type and concurrency is not supported. They have been converted. Description: You requested a type and concurrency combination for the result set that is not supported. The requested values had to be converted. See “Using cursors with result sets” for more information about what result set types and concurrencies are available in jConnect Action: Request a type and concurrency combination for the result set that is supported.
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 Chapter 3 of 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: You may need to 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 jConnect (see “Installing Stored Procedures” in Chapter 3 of the jConnect for JDBC Installation Guide).
010SM	This database does not support the initial proposed set of capabilities, retrying. Description: Adaptive Server Enterprise versions 11.9.2 and lower had a bug that caused them to reject logins from clients that requested capabilities that the servers did not have. This warning indicates that jConnect has detected this condition and is retrying the connection using the greatest number of capabilities that the server can accept. When jConnect encounters this bug, it attempts to connect to the server twice. Action: Clients can safely ignore this warning, but if they wish to eliminate the warning and ensure that jConnect makes only one connection attempt, they can set the ELIMINATE_010SM connection property to "true." Please note that this property should not be set to "true" when connecting to 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 jConnect was unable to connect to one of the database servers in the list of servers to which to connect. Therefore, jConnect now tries to connect to the next server in the list. Action: No action is required, as long as jConnect is able to connect to another database server. However, you should determine why jConnect was unable 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 jConnect, and has responded with a different character set. 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: jConnect could not determine the server's default character set. When this occurs, the only characters that are guaranteed to translate properly are the first 127 ASCII characters. Therefore, jConnect reverts to 7-bit ASCII in this case. The message is strictly informational and has no further consequences. Action: Install the stored procedures for returning metadata that comes with jConnect (see “Installing Stored Procedures” in Chapter 3 of the jConnect for JDBC Installation Guide).
010UF	Attempt to execute use database command failed. Error message:_____ Description: jConnect cannot 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 an Adaptive 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 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 jConnect driver connection properties.
0100V	The version of TDS protocol being used is too old. Version: _____ Description: The server does not support the required version of the TDS protocol. jConnect requires version 5.0 or later. Action: Use a server that supports the required version of TDS. See the system requirements section in the jConnect installation guide for details.
01S07	Adaptive Server may round or truncate nanosecond values. Description: A time value of precision better than 1/300th of a second was encountered. Because 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: jConnect issues rollback to clear out any current local transactions. This occurs when Global transaction has been enlisted, after issuing XAResource.start(). Action: If you have local transactions active prior to issuing the XAResource.start() method, you need to either commit or rollback the local transactions.
01S09	The local transaction method ___________ cannot be used while a global transaction is active on this connection Description: Warns that a local operation is being performed in the global transaction. An example of a local operation is calling the commit() method on the connection. Other operations that can't be used: rollback(), rollback(Savepoint), setSavepoint(), setSavepoint(String), releaseSavepoint(Savepoint), and setAutoCommit(). Action: Local transactions need to be kept separated from global transactions. Make sure to complete all local transactions and their operations prior to 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 meth