Skip to Content
Author's profile photo Jan Stallkamp
Jan Stallkamp
October 29, 2013 Less than a 1 minute read

News from Development – Hot News Note 1926514

Hi everyone.

I would like to let you all know that a HOT NEWS SAP Note has been released for customers running SAP applications on SAP Sybase ASE. Please have a look at SAP Note 1926514 and act accordingly as soon as possible.

The SAP Note boils down to issues with the ODBC driver versions 15.7.0.504 to 15.7.0.507. Running this ODBC driver versions in combination with older versions of the Sybase DBSL can lead to short dumps, fetch errors and incomplete result sets. We highly recommend to use at least ODBC 15.7.0.508 or higher and at least DBSL 7.20 patch level 427, 7.21 patch level 129, or 7.40 patch level 19.

Best regards,

Jan Stallkamp

(SAP on Sybase ASE Development)

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      I have Sybase ASE ODBC driver version 15.07.00.1000 which comes with 15.7 SP103. The following script results in error:

      Option Explicit

      Dim objCn

      Set objCn = CreateObject("ADODB.Connection")

      objCn.ConnectionString = "DRIVER=Adaptive Server Enterprise;Server=...;Port=5000;User ID=...;Password=...;"

      objCn.Open()

      objCn.Execute("exec [master].dbo.sp_help 'sysobjects'")

      objCn.Close()

      WScript.Echo("Done.")

      test.vbs(6, 1) Microsoft OLE DB Provider for ODBC Drivers: [Sybase][ODBC Driver][Adaptive Server Enterprise]Stored procedure 'master' not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).

      Experimentally I've found that the problem only happens when I put square brackets around the database name when exec keyword is present. Once I remove the exec or the brackets the problem is gone.

      I need the brackets to handle database names with spaces in the name.

      As I understand the problem is with the ODBC driver modifying the SQL text passed to the SQLExecDirectW API. Can somebody from SAP on Sybase ASE Development confirm that this is a known issue?