Known Problems for Adaptive Server Plug-In

546929

Starting Interactive SQL using the Adaptive Server plug-in may generate an error message

When you launch isql from the Adaptive Server plug-in, you may see an error message similar to:

Could not connect to the Server

JZ01B: The server’s default charset of roman8 does not 
map to an encoding that is available in the client Java 
environment. Because jConnect will not be able to do 
client-side conversion, the connection is unusable and 
is being closed. Try using a later Java version, or try 
including your Java installation's i18n.jar or 
charsets.jar file in the classpath.

Workaround: jConnect™ for JDBC™ does not support the roman8 default character set on HP. To avoid this error message, on the connection dialog screen, select the “iso_1” character set.

487524

During create cluster command, sybcluster reports a permission error

You may see an error message from sybcluster that you do not have write permission to the directory in which raw devices are configured during the create cluster command. This happens when the name of the device is misspelled, or if no device by the specified name exists.

Workaround : Reenter the name of an existing device.

478875

Dropping instance in Adaptive Server plug-in functionality cannot drop connected instance

You cannot drop a connected instance in the Adaptive Server plug-in. If you drop a connected instance, your connection is lost as soon as the instance is shut down.

Workaround : Connect to another instance in the cluster before shutting down the instance to drop.

469418

Reconnecting Adaptive Server plug-in does not occur automatically

When the Adaptive Server plug-in is connected to a cluster through an instance that stops responding, the plug-in does not automatically reconnect to another running instance.

Workaround : Use host:port to reconnect to another running instance.