The purpose of this KBA is to help SAP customers obtain a general idea of potential fixed situations in future Adaptive Server Enterprise (ASE) EBF/SP or PL releases. Please be sure to read the Disclaimer below.
If the EBF/SP has been released, check the CR list and coverletter at the service.sap.com.
Disclaimer: This document lists the targeted (not committed) release dates and the targeted fixed CR list for each release. Please be aware that the purpose of this posting is solely to provide you, our customers with estimated release dates and targeted CR lists. SAP does not commit to releasing on the specified dates or to including the CR fixes in the said release. While every effort will be made to meet the said targets, changes can occur at any time. It is also possible (although unlikely) that SAP may decide not to release an EBF/SP that was previously scheduled for release.
|609832||A 3478 error, “During undo the page timestamp value is less than new timestamp from log. Page #= < num > , object id = < id > , page timestamp= < value1 > . Log new timestamp= < value2 > . Log record marker = ( < num > , < rowid > ).” may be reported in the error log together with a stack trace which includes the modules ‘xact_rollback’ and ‘rec_undo_session’ when SAP ASE rolls back a transaction and while the housekeeper garbage collection task is working on the same Page# unexpectedly.|
|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.|
|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.|
|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.|
|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.|
|746870||Remove Sybase Central ASEP from ASE installer for 15.0.3 ESD#4.4|
|748675||Insert into corrupted table failed and did not return any error, originally seen on 12.5.4.|
|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.|
|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.|
|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.|
|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: 126.96.36.199: 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”.|
|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.|
- AIX 64bit
- HP-UX on IA64 64bit
- Linux on Power 64bit
- Linux on x86 64 64bit
- Solaris on Sparc 64bit
- Solaris on x86 64 64bit
- Windows on x64 64bit
CR, ASE 15.0.3 ESD#4.4, ASE 15.0.3, ESD#4.4, Adaptive, Server, Enterprise, Fix, Patch, Error, Bug , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , BW-SYS-DB-SYB , BW on Sybase ASE Database Platform , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.