SAP Knowledge Base Article - Preview

2900067 - Targeted CR List for SDK 16.0 SP03 PL08 for ASE

Symptom

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. 

 Please note that ADO.NET  fixes are only for Windows environments

Component CR Description
ADO.NET 820691 ADO.NET: Visual Studio crashes System.AccessViolationException Sybase.Data.AseClient.Unmanaged.GetDatabase. See KBA 2873822
ADO.NET 820723

ADO.NET: Bulk insert bcp.WriteToServer(dt)is generating the following exception
Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at Sybase.Data.AseClient.Unmanaged.GetDatabase(IntPtr ConnectionHandle, Char[] database, Int32 databaseCapacity). See KBA 2874341

Directory Services 819882 Update to openLDAP 2.4.48 for LDAP driver
JDBC Driver 820395 [jConnect] In rare circumstances, the error message, "Invalid column length: <x>. Value must be between <x> and <x> at offset <offset> for 'all-pages' row with minimum row length of <x>.", may be reported in the SAP ASE error log after performing an INSERT from a jConnect client that has ENABLE_BULK_LOAD enabled. Alternatively, a 2507 error, "Table Corrupt: Offset table is incorrect (page number <x>, partition ID <x>; row number <x>; offset in the offset table is <x>; the correct offset is <x>�, may be reported by DBCC CHECKTABLE on the target table. See KBA 2794550.
JDBC Driver 820175 [jConnect] For numeric/decimal data type, jConnect needs to make sure correct parameter format is send for different values for incoming data. See KBA 2898035.
JDBC Driver 819900 [jConnect] Clear reference of Statement/Prepare/Callable in PooledConnection for Vector. See KBA 2832476.
JDBC Driver 819461 [jConnect] The RSMDA Column Type Name you requested is unknown with nchar and nvarchar fields on utf8 server. See KBA 2801765.


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) Software Developer Kit (SDK) 16.0 SP03 PL08
  • 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
  • Windows on x32 32bit

Product

SAP Adaptive Server Enterprise SDK 16.0

Keywords

CR, CR List, SDK 16.0 SP03, Adaptive Server Enterprise, Fix, Patch, Error, Bug, Software Developers Kit, ADO.NET, ESQL, LDAP, jConnect, jdbc, ODBC, OLEDB, BCP, driver, cslib, ctlib, srvlib, PYTHON, PHP, php, python, SDK for SAP ASE, perl , KBA , BC-SYB-SDK , SDK , Problem

About this page

This 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.