2081350 - Targeted CR List for ASE 15.5 ESD#5.4 -SAP ASE

CR number

Description

687372

A 697 error, "An attempt was made to fetch logical page < pagenum > for database < dbname > ....", during transaction rollback, if the transaction is doing some DMLs to upgrade row lock to table lock.

688481

The message "current process infected with 11" in the module sdes_num_in_chain() together with a stack trace which includes the modules kill_proc() and LeExecSqlFunc() may be reported in the error log if a long running user-defined SQL function session gets killed. ASE may need to be rebooted following this error.

693413

The wash size may be returned as a negative value in the ASE configuration file.

706799

Memory allocation failures appear in the ASE errorlog when the network memory pool is exhausted or when fragmentation of memory occurs due to memory that is not freed.

710847

The error messge, "Page Verification Error: Virtual page < page_num > in device < dev_num > is out of database range." may be reported in the Backup Server error log as a result of a LOAD DATABASE command.

730673

The PCI Memory management layer is enhanced to better service memory allocation requests for ASE tasks executing JAVA operations. The layer now makes a better decision from where to allocate the requested memory. It either uses the PCI Fragment memory pool for end-user coded objects, or the O/S system run-time for JavaVM internal operations.

735036

When running concurrent SELECT commands and DELETE/UPDATE commands on TEXT/IMAGE/UNITEXT columns, the client connection may hang or report a TDS token error or raise error 7128 state 6.

736426

The Java Compile Suite layer in Adaptive Server that is responsible for UDF/ADT support and SQLJ queries execution towards the target JavaVM has been enhanced to allow the release of intermediate allocated Java objects. This was causing the JavaVM heap memory allocation to be exhausted under a heavy load application environment.

740020

Under rare circumstances on Windows NT 64-bit platform ASE may stop with no errors being reported while processing Web Services requests that involve the execution of Java code.

744011

When a user database is binded to a named cache, create index in it might report Error 693 while a dump database process running simutanously.

744013

In a High Availability server, sp_addlogin and sp_addremotelogin will fail with permission errors when the user executing the stored procedures is granted sso_role only.

744389

The message, "Current process infected with signal 8 (SIGFPE)", followed by a stack trace that includes the module sam_setup_ptn() may be reported in the error log under rare circumstances.

745599

In rare circumstances the message "current process infected with 6" in the module '__systemcall' together with a stack trace which includes the modules 'jvmfini' and 'BRIDGEjvm_AbortJavaVM' may be reported in the error log during the execution of a UDF/ADT or SQLJ query.

745873

In rare cases a 692 error, "Uninitialized logical page ' < pageno > ' was read while accessing database ..." may be reported sometime after loading a database dump that was taken of a database in both Enterprise Edition and Cluster Edition, that had been created on devices with “direct i/o” turned on, or taken of a database in a Cluster Edition system only, that had been created on devices with “dsync” turned on.

746349

Backup Server introduces a remote access control feature that prevents remote dumps and loads and execution of remote procedure calls (RPC) from any client or server running on unauthorized servers. Local dumps are not affected by this feature. Authorization to dump or load, to or from Backup Server is achieved by including the authorized hosts in the host.allow access control file. The default location of hosts.allow file is $SYBASE. The location and name can be changed using the Backup Server parameter -h. This feature failed when the connection to the backup server was through a named pipe.

746442

Backup Server introduces a remote access control feature that prevents remote dumps and loads and execution of remote procedure calls (RPC) from any client or server running on unauthorized servers. Local dumps are not affected by this feature. Authorization to dump or load, to or from Backup Server is achieved by including the authorized hosts in the host.allow access control file. The default location of hosts.allow file is $SYBASE. The location and name can be changed using the Backup Server parameter -h. This feature failed when the connection to the backup server was through a AF_UNIX socket.

749101

The connection to a backup server can be rejected if the client host has multiple IP addresses and the entries in the target backup server hosts.allow file are not authorizing the first remote IP address. Likewise, the connections will be rejected if the host name used in the first column of the hosts.allow file specifies a host alias different from the actual host name.

750316

Under rare race conditions, when BCP IN is in progress with the INSERTs running concurrently on the same table, BCP may encounter an 820 error where the process tries to dirty a buffer which is already pinned to another PLC.

750683

In rare circumstances, the execution of Java User Defined Functions (UDF) could mistakenly ignore the arguments it expects when these are presented to it through a single argument that holds a white space separated string.

750719

Error 247:"Arithmetic overflow during implicit conversion of < type > value < value > to a < type > field ." can be seen while running stored procedure sp_spaceusage on large table.

750991

sp_sysmon gives wrong Average values for Engine Busy Utilization in process kernel mode.

751034

If the DUMP DATABASE is run on a database, a 691 error, "Encountered invalid logical page < page id > while accessing database < database name and id > , object < object name and id > , index < index name and id > , partition < partition name and id > . This is an internal system error. Please contact Sybase Technical Support.", might be reported when running SELECT INTO cmd to create a proxy table in this database.

752391

In rare case, if DOL table has unique index, concurrent dmls may hit index corrupt(error 12313 "Insert into page id < page # > of index id < index # > of table ' < table name > ' (id = < id # > ) in database ' < db name > ' tried to replace undeleted RID ( < > , < > ) at slot < slot # > and ridposn < # > . Try dropping and recreating the index.")x.

752591

A segmentation violation occurs when the config option enable xact coordination is set to 0 and a connection is established between a primary and secondary server.

754283

Backup Server on HPUX may die with error messages: A00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 1, error code=0, system message=Pipe I/O returned 0 bytes. D00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 9, error code=0, system message=Pipe I/O returned 0 bytes while trying to print out a legitimate API error.

754622

Performance of concurrent insert is slow.

754856

When we try to alter temporary table for the database which has proxy database mapped on secondary companion, we hit error 177: CREATE PROXY_TABLE cannot create a temporary object (with '#' as the first character name.

756618

Duplicate identity values may be generated after loading a transaction log dump containing transactions that inserted identity values reserved using multiple calls to RESERVE_IDENTITY().

756631

A 644 error, "Index row entry for data row id ( < pageid > , < rnum > ) is missing from index page < index_pagenum > of index id < indid > of table ' < tablename > ' in database ' < dbname > '. Xactid is ( < xactid > ). Drop and re-create the index." may sometimes be reported in heavily concurrent systems using DATAROWS LOCKED or DATAPAGES LOCKED tables.

758938

When a process that is executing a DUMP DATABASE command is killed either using the KILL command or using CTRL-C or the SQL session goes away, the Backup Server will not release its associated resources until it finishes copying the whole database. One of the consequences is that the archive devices can remain locked for a long time because the sybmultbuf processes stay alive.

761275

When there are several scans on the same index and some of the scans hit the same index page needed to be shrunk concurrently, the index page may be shrunk twice. The second attempt will fail and a 2630 error, "In database < db > , page < page#2 > is linked backward to page < page#1 > , but that page is linked forward to page < page#3 > . Please report this internal error to SAP Technical Support". Although a 2630 error is raised, the index is not corrupted.

763301

The ASE COTS JavaVM version is updated to version JRE 6 update 45 for each supported platform in the sybpcidb database.

765720

Under some circumstances the backup server may report the error “Backup Server: 4.189.2.1: Volume validation error: attempt to set directio mode on < devicename > returned -1.” while a DUMP DATABASE or DUMP TRANSACTION command is being executed. To avoid this problem from happening execute in the master database the command “sp_deviceattr ‘devicename’,’directio’,false”.

766109

Under a heavily loaded Java application environment, the messages 'PCI(M1): ERROR: JNI_CreateJavaVM; failed attaching to the JVM for AttachCurrentThread() with -1' and 'PCI(M1): ERROR: JNI_CreateJavaVM; PCA/VM FAILED; general failure' may be reported in the SAP Adaptive Server error log. These messages usually indicate that the JavaVM heap space is exhausted. In order to solve this problem the SAP Adaptive Server needs be restarted.

766427

The indexes created internally for the replication of text/image columns are system objects and they cannot be renamed by executing the system stored procedure sp_rename.

766647

Under a heavily loaded Java application environment, the messages 'PCI(M1): ERROR: JNI_CreateJavaVM; failed attaching to the JVM for AttachCurrentThread() with -1' and 'PCI(M1): ERROR: JNI_CreateJavaVM; PCA/VM FAILED; general failure' may be reported in the SAP Adaptive Server error log. These messages usually indicate that the JavaVM heap space is exhausted. In order to solve this problem the SAP Adaptive Server needs be restarted.