Learn about known issues and apply workarounds for Adaptive Server Cluster Edition. Known issues are listed in descending order of Change Request (CR) numbers.
Sybase does not include system problem reports (SPRs) and closed problem reports (CPRs) with Adaptive Server Enterprise. You can search the Web site for solved cases. Click
.CR # | Description |
---|---|
739773 | The load database … with listonly=load_sql command may generate load commands which, if executed, may require manually altering the target database for the load to succeed. This issue can occur in cases where an alter database off command was run on the source database. Workaround: Manually alter the target database. |
739080 | The show_condensed_text function returns a NULL value for queries in the statement cache when the enable literal autoparam configuration parameter is enabled. Workaround: Do not use the show_condensed_text function when enable literal autoparam is enabled. |
738744 | A cumulative dump cannot be used as a meta-data file for the sybdumptran utility. Workaround: None. |
738675 | load database with verify does not support automatic physical database rearrangement. If load database with verify is executed, the automatic remapping between the source and target database to ensure that the data segment is on data devices and the log segment is on log devices is not performed. This may result in the behaviour of releases prior to 15.7 SP100, which is the data segment may be mapped to log devices and the log segment may be mapped to data devices in the target database. Workaround: Sybase recommends that you use the dump database with verify command to verify the database. |
696072 | In some Cluster Edition
configurations, Adaptive Server 624 and 69x errors may occur during database
replication of a database or replication of tables within a database.
In active-active or active-passive cluster configurations, you can configure RepAgent to run on only one node of the cluster. In rare circumstances, when RepAgent reads an older image of database log pages that is on disk while the latest image is on another node, you may see Adaptive Server 624 and 69x errors. Workaround: Sybase recommends that for:
|
695625 | Confidentiality
service causes error. This message is reported by Open Client applications connecting to Adaptive Server Enterprise: ct_send(): network packet layer: internal Client Library error: State error: trying to write when connection is expecting a read. This message is reported in some cases when Kerberos message confidentiality service is turned on. Workaround: Reconnect to the server with confidentiality service turned off. |
684556 |
The select for update semantics introduced in version 15.7
do not support datapages-locked tables.
select for update support exists only for datarows-locked pages. |
680041 | The value of the
server network name as defined by the srvnetname column for a loopback
server must be the name of the cluster. For the sp_opt_querystats stored procedure to succeed, the value of the srvnetname column for a loopback remote server must be the name of a cluster in the cluster interfaces file and not the name of a cluster instance. Workaround: Make sure that the srvnetname column for the loopback remote server is the name of the cluster. |
639813 | An error is raised when renaming a read only database Error (3906) can occur when executing sp_renamedb on a database that has 'read only' status. Also, when attempting to turn off the 'read only' status on a database that you have attempted to rename, error 3501 is raised. Workaround: Execute sp_renamedb stored procedure from master database context as follows: use master go sp_renamedb <dbname>, <new_dbname> go |
615890 |
Cannot disable RMI socket operations using
pca_jvm_netio.
RMI sockets continue to function, even if you have either manually disabled
them, or executed:
sp_jreconfig "disable", "pca_jvm_netio"Consequently, a Java RMI client continues to connect to a remote RMI server to execute functionality over the network. Workaround: Remove any unused RMI classes from the database. By default, pca_jvm_netio is enabled. |
615204 |
If enable DTM is set, the distributed recovery feature is
disabled and all databases are recovered only on the cluster coordinator,
rather than on different instances of the cluster.
Workaround: None. |
595923 |
There are two known issues with transfer table:
Workaround: None. |
595859 |
A single-engine Adaptive Server may stop responding when, after performing a
Java task, additional engines are manually brought online.
While running on a single engine, Adaptive Server may either stop responding, or cause connected clients to block indefinitely, generate a stack trace, or not process when the server performs a task that uses Java, as soon as additional engines are manually brought online. This problem occurs due to an issue with the HP-UX commercial off-the-shelf Java Virtual Machine. Workaround: Always have a minimum of two engines configured when starting Adaptive Server; this allows the HP-UX commercial off-the-shelf JVM to automatically target the highest engine number available. In addition, do not set any configuration options in Adaptive Server that targets engine 0 for the HP-UX commercial off-the-shelf JVM. |
576652 | SySAM2
enabled products incorrectly determine the number of cores and chips on
quad-core processors. This may be as a result of your Adaptive Server small business edition or chip license not being activated and having gone into a grace period. Workaround: Remove this line from your
SySAM properties file, if it
exists:
cpuinfo.mechanism=NOAPICCHECKIf the problem still remains, set the following environment variable, then run the products: (sh) export SYBASE_SAM_CPUINFO=CPUID (csh) setenv SYBASE_SAM_CPUINFO CPUIDIf the problem still remains, please contact Sybase Technical Support. |
547723 |
Using Java in the database to create a file
fails on HP-UX.
Due to a known issue in HP-UX, creating a file using the Java in the database feature fails unless the working directory permission mask is set to 0777 or equivalent. Workaround: Set the mask on the working directory to 0777. (This is
not the same as the physical directory permissions in the file system. The
physical directory can have any permissions mask that is appropriate for
that directory.) This setting is only for the sybpcidb
configuration properties, where you can configure a working directory with a
mask that allows or prevents certain actions from within the JVM. Apply the
mask using either an add command or an
update command. For example:
sp_jreconfig 'add', pca_jvm_work_dir, '/some/path(ugo=rwx)'or: sp_jreconfig 'update', pca_jvm_work_dir, '/old/path', '/newpath(ugo=rwx)' |
483651 |
Incorrect cluster failover may occur during diagnostic shared-memory
dump.
If you start an instance while the rest of the cluster is performing a diagnostic shared memory dump, the instance that is starting may incorrectly perform a cluster takeover. This occurs only if automatic cluster takeover is set to 1, or if the --cluster_takeover option is passed to the data server. In environments without i/o fencing enabled, this may lead to data corruption. Workaround: Do not start an instance during a diagnostic shared-memory dump. Configure automatic cluster takeover to 0. |