Known Issues

Workaround: None

Workaround: None.

srvbuild and srvbuildres fail to configure Job Scheduler.

Workaround: Add $SYBASE_JRE6/bin/classic to the LIBPATH environment variable before running srvbuild or srvbuildres.

kernel  PCI(M1): ERROR: JNI_CreateJavaVM; failed retrieving the JVMTI handle in GetEnv() with -4
kernel  PCI(M1): ERROR: JNI_CreateJavaVM; PCA/VM FAILED; not enough memory
kernel  PCI(M1): ERROR: jsigcache_destroy; Signature cache destroy request without a JavaVM handle to destroy
kernel  PCI(M1): PCA/JVM Signature cache is detached
kernel  PCI(M1): Failed to destroy the VM signature cache

Workaround: None. Restart Adaptive Server if the server hangs due to this issue.

When you create a new Adaptive Server, the out-of-the-box configuration feature prompts you to allocate a total amount of memory for Adaptive Server, and a default value that is 80% of the system's physical memory. The server does not start if the amount of memory specified is not actually available for use by Adaptive Server.

Workaround: Determine the amount of memory you need, and confirm that this amount is available for Adaptive Server.

When using SQL statement replication on a table subscription-based replication topology, a data markup language (DML) executed on a replicated table owned by the database owner (dbo) is not replicated as a statement if the replication definition defined for the primary table does not include the owner information. In such cases, the standard replication used instead.

For a database subscription-based replication topology, a DML is replicated according to the settings in the database replication definition.

If both a table and database replication definition/subscription exist on a table, and the owner information is not specified in the table replication definition, a DML is replicated according to the settings in the database replication definition.

Workaround: Mark the table as 'owner_on' at the source database, and create a replication definition for the primary table using the owner information.

When opening a database at the same time a process is scavenging the DBTABLE of that same database, the process may stop responding. You see modules dbt_grab(), dbt_clean(), metrics_proc_dump(), metrics_dump(), and dbt_get() in the stack of the blocked spid.

Workaround: Increase the number of open databases and reboot the server. The number of open databases should be configured to be at least the value returned by the query 'select count(*) from master..sysdatabases'.

If the Java-in-the-database feature is enabled in Adaptive Server 15.0.3 or 15.0.3 ESD #1, all processes that access remote servers through Component Integration Services (CIS) are redirected to the engine that handles processes using Java. This can have a serious performance impact in a multi-engine system where most of the processes use CIS, as all of the processes are running on a single engine.

Workaround: If CIS and Java in the database feature are not used by the same client, the -T 9403 trace flag may improve performance by distributing CIS connections across all engines.

When you attempt to create a Job Scheduler schedule using the Adaptive Server plug-in for an Adaptive Server localized for Simplified Chinese, you occasionally receive an error indicating that the varchar datatype cannot be converted to a date.

Workaround: Localize the Adaptive Server for Simplified Chinese before configuring Job Scheduler.

When you configure the Job Scheduler Self Management feature for an Adaptive Server localized for Simplified Chinese, you occasionally receive an error saying that a varchar datatype cannot be converted to a date. The Job Scheduler configuration process stops at this point.

Workaround: Do not configure the Self Management feature for Simplified Chinese.

When updating the filename column of a proxy table mapped to a directory of files, Sybase recommends that you qualify the update to specific files by including the filename in the where clause. Some file systems may rename a file by deleting and re-creating a new directory entry; therefore, the same file name may be updated multiple times if the update is not restricted.

For example, this statement could cause multiple updates:

update t1 set filename=filename + 'old' where filetype
= 'REG'

Workaround: Add a clause such as 'and filename like '%.c'.

The allow backward scan configuration parameter does not work in Adaptive Server.

When you start the Monitor Client GUI in an environment using LDAP instead of an interfaces file, the Monitor Client GUI cannot connect to any servers.

Workaround: Create an interfaces file with entries for the servers that are monitored and use this with the Monitor Client GUI.

rs_init in Replication Server version 12.6 and earlier cannot create an RSSD database in Adaptive Server Enterprise version 15.0 or later.

Workaround: If you do not use an embedded RSSD (ERSSD), manually create the RSSD database before using rs_init to create a new Replication Server. See the Replication Server Administration Guide.