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.
|776546||A 12308 error "Internal error : Invalid row id (Row < > , Page < > ) encountered in the table < > in database < > ." may be reported by level 0 scans / dirty reads or a 1514 error "Sort failed because it attempted to allocate page < > and found that the page was busy..." may be reported during create index, on a table on which 'reorg rebuild with online' has been run.|
|784069||A 3957 error, “New transaction cannot be started due to an ongoing HADR deactivate operation.”, may be reported when a DML command that is part of an already running user active transaction is incorrectly terminated while sap_failover < site1 > , < site2 > , < timeout_in_seconds > is executed. Moreover SAP Business Suite applications can run into data consistency errors since SAP Business Suite does not reapply lost transactions when error 3957 is raised. The expected behavior is that active transactions will not be interrupted when sap_failover < site1 > , < site2 > , < timeout_in_seconds > is run.|
|785377||TRUNCATE of a specified partition may sometimes may truncate the wrong partition when there exists a partition name for the table whose partition name starts with the full partition name of the partition that is intended to be truncated. e.g. if partition name "week1" was requested to be truncated and there was also a partition name on the table called "week14", then "week14" may be truncated instead of "week1".|
|785404||ESP (extended stored procedure) execution may fail if overall path of the ESP DLL is more than 99 characters or more (including the name of the DLL).|
|785554||Under UTF8 sort order 99, if a composite index contains a leading NULL VARCHAR field, REORG REINDEX may not be able to rebuild the index.|
|785701||In rare circumstances, a 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < > , object id = < > ..." is reported by SAP ASE during a LOAD TRAN of a transaction dump that includes a transaction of online REORG REBUILD or non-online CREATE INDEX if the earlier portion of load sequence contains a transaction of online CREATE INDEX with deferred recovery.|
|786618||KBA 2192618: On AIX Platform, xpserver fails to start with error messages: "exec(): 0509-036 Cannot load program xpserver because of the following errors: 0509-150 Dependent module libsybsrv64.so could not be loaded. 0509-022 Cannot load module libsybsrv64.so. 0509-026 System error: A file or directory in the path name does not exist." This shared object is not distributed with SAP ASE or the SAP Connectivity SDK.|
|786671||This PC-Client SP is based on SDK 15.7 SP126. A list of changes in SDK 15.7 SP126 is available at http://download.sybase.com/swr/17983/EBF22690_README.html|
|788080||On the IBM AIX platform, xp_cmdshell executions may fail with the error message: "Could not load library < $SYBASE > / < $SYBASE_ASE > /lib/sybsyesp.so"|
|788474||KBA 2211717: Under some rare condition, if columns in a table have more than one constraints (not necessary in the same column), it can cause invalid rows to be inserted.|
|789967||KBA 2217884 - In rare circumstances, a 12308 error "Invalid row id (Row < > , Page < > ) encountered in the table 'T' in database 'D'" or a 614 error "Adaptive Server accessed a row that has an illegal length of < n > while in data base 'X' ..." may be reported by a reorg rebuild index or a DML following 'reorg defrag' on a table.|
- SAP Adaptive Server Enterprise (ASE) 15.7 SP135 HF
- 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
"Change Request", Fix, Hot, "Hot Fix", Patch, Error, Bug, EBF, SP , 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.