Known Issues for Adaptive Server

Learn about known issues and apply workarounds for Adaptive Server. Known issues are listed in descending order of Change Request (CR) numbers.

Note:

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 Support > Services > Solved Cases.

CR #Description
616224
Setting the default sort order to nonbinary, single-file sort order may cause like pattern evaluation failures.
If you configure Adaptive Server to use the nonbinary, single-byte sort order as its default sort order, you may encounter an issue where a query containing a like expression using a constant literal as the argument (with or without wildcards) does not correctly evaluate the value in the table is the same as the like argument prefix up to the wildcard character. For example:
create table t1 (c1 varchar(20))

insert t1 values ('John')
insert t1 values ('Johnson')
insert t1 values ('Johnston')
Both of these queries fail to return the first record:
select * from t1 where c1 like 'John'
select * from t1 where c1 like 'John%'
This query, however, works correctly:
select * from t1 where c1 like 'Joh%'
A query using variables or procedural parameters is not affected by this incorrect behavior, and the following returns an expected and correct result set:
declare @var varchar(20)
select @var = 'John'
select * from t1 where c1 like @var
Workarounds:
  1. Enable the statement cache. See "Setting the statement cache" in Chapter 3, "Configuring Memory," of System Administration Guide: Volume 2.
  2. Activate the autoparameterization of literals:
    -sp_configure 'enable literal autoparam', 1
  3. Restart Adaptive Server using trace flag -T7739. This step parameterizes like constant literals.
Note: Queries that are not placed in the statement cache, such as select into, may not benefit from this workaround.

For more information about CR #616224, contact your local Sybase Technical Support Center using the information from http://www.sybase.com/contactus/support#tech.

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.

607917
Running transfer table may report SySAM errors.
When you invoke the transfer table command, this error may be written to the error log:
SySAM: Failed to obtain license(s) for ASE_DTU 
feature from license file(s) or servers(s).

Workaround: This is an erroneous report. As long as you have a valid license for the Adaptive Server in-memory database feature, transfer table executes successfully.

607464
Recovering a template displays an error.
In some cases, when a database that is used as a template for creating a database with a durability of no_recovery is being recovered, a 937 error may be reported to the error log:
The database '<template_dbname>' is currently 
unavailable. It is being used to create a new database.
Workaround: This error does not impact the correct recovery of any databases. Following the completion of recovery, however, the default data cache may have a memory pool configuration that differs from the configured values. Execute sp_poolconfig and reconfigure the default data cache to required values.
607095
If you restart Adaptive Server after using sp_renamedb to rename a database that is the template database for an in-memory database, Adaptive Server may create the in-memory database using the model database instead of the template database, or the in-memory database may become inaccessible.

Workaround: After you run sp_renamedb, run sp_configure so that Adaptive Server can recognize the new name of the template database.

The default command is:
sp_renamedb "tdb", "tdb_old"
where "tdb" is a template database, and "tdb_old" is the name you are renaming it to. This assumes that you have an in-memory database called "timb" that has "tdb" as its template database.

After you run sp_renamedb, run:

sp_configure "allow updates", 1
go
update master.dbo.sysdatabases set def_remote_loc='tdb_old' where def_remote_loc='tdb'
go
sp_configure "allow updates", 0
go
606234
If you enable ASE_JAVA for a commercial off-the-shelf Java Virtual Machine, then start Adaptive Server version 15.5 in a multiengine configuration, Adaptive Server may perform an incorrect setup of the JVM module responsible for physical file and network I/O protection.

This incorrect setup allows Java methods executed from Adaptive Server to perform permission-sensitive physical file I/O operations, as well as launch network services while taking on the full identity of the user who restarted the Adaptive Server.

Workaround:
  • Do not enable the PCI subsystem. If you do, you cannot execute Java methods from Adaptive Server.
  • Restart a single-engine Adaptive Server first, then bring additional engines online before any requests are made to execute Java methods.
  • Configure the PCI bridge so that it defaults towards binding the commercial off-the-shelf JVM under engine 0.
595986
Differing byte orders may generate an error during database dump.

When you load a dump of a database that has a durability of no_recovery or at_shutdown, you may see:

Adaptive Server cannot load this database because
the database that was dumped was not quiescent 
when the dump was performed.

This occurs when you load a dump of a database from one platform to another platform with a different byte order.

Workaround: None.

595923
There are two known issues with transfer table :
  • When creating a unique index that is using the ignore_dup_key property, importing a row with a key that is already present in the table leads to an error, and the import is aborted. This differs from when a duplicate key is inserted with bcp or with a regular insert statement, since in those cases, the row is discarded, and the transaction continues.
  • When an insert trigger exists, the trigger is not fired when data is inserted through transfer table...from.
595859
Differing byte orders may generate an error during database dump.

When you load a dump of a database that has a durability of no_recovery or at_shutdown, you may see:

Adaptive Server cannot load this database because
the database that was dumped was not quiescent 
when the dump was performed.

This occurs when you load a dump of a database from one platform to another platform with a different byte order.

Workaround: None.

589269
Adaptive Server may stop responding during start-up.

If you are using the in-memory database or relaxed-durability database feature, Adaptive Server may run into a timeslice error during start-up if it cannot access the license server as it starts.

Workaround: Make sure Adaptive Server can access the license server.

582815
Under certain conditions, you may need to re-create abstract plans associated with stored procedures that include the built-in function isnull.
These are the conditions:
  • One of the parameters to isnull is a char datatype and another is a literal.
  • enable literal parameterization is set to on.

Workaround: Re-create the abstract plans associated with the stored procedure.

567466
When your statement cache is on, if an exception occurs while compiling a statement that includes temporary tables, error message 8203 may appear.

Workaround: Use command-line traceflag 467, which prevents statements referencing temporary tables from being cached.

551972
Using Java in the database to create a file fails on HP-UX.

Due to 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)'
466370
If Adaptive Server is configured for a large number of spinlocks, you may see a performance issue with sp_sysmon.
This is because index creation on the worktable used by sp_sysmon fails due to duplicate key values. sp_sysmon reports error 1508: 
Create index aborted on duplicate rows.
The large number of spinlocks on Adaptive Server account for a large number of rows in the table, and result in duplicate key values. sp_sysmon performance is slower due to the lack of an index on the worktable.

Workaround: Run sp_sysmon with the clear option.

Note: The clear option will reset the monitor counter values on your server.
462184
Monitor Server and Historical Server do not work with an Adaptive Server that has set its net password encryption reqd options set to 1 or 2.

Workaround: None.

439406
Configuring Job Scheduler Self Management for Simplified Chinese

When you configure the Job Scheduler Self Management feature for an Adaptive Server localized for Simplified Chinese, you may 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.

439404
Creating Job Scheduler schedules for Adaptive Server with Simplified Chinese.

When you attempt to create a Job Scheduler schedule using the Adaptive Server plug-in for an Adaptive Server that is localized for Simplified Chinese, you may 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.

400784
Starting Monitor Client GUI fails when the Lightweight Directory Access Protocol (LDAP) server is used.

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.

382874
Creating RSSD database fails with earlier versions of Replication Server.

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.