Problem while connecting Sybase 15.7 Table via WMB DataDirect 6.0 Sybase Wire Protocol - Forum - DataDirect Connect - Progress Community

Problem while connecting Sybase 15.7 Table via WMB DataDirect 6.0 Sybase Wire Protocol

 Forum

Problem while connecting Sybase 15.7 Table via WMB DataDirect 6.0 Sybase Wire Protocol

This question is not answered

Hi All,

I got stuck in very wierd problem.Currently am facing an issue while inserting data in to Sybase database 15.7 with WMB code flow. Am currently using WMB7 Broker which is using DataDirect 6.0 Sybase Wire Protocol for connecting Sybase 15.7 Database.I have written code in our message flow which is trying to insert the data in the table directly . The data types used in database table is int and Image. But insert operation is not completing anyways.

Whereas the same message flow code is inserting the data in Database table which is on Sybase 12.5 which is also using the same Data Direct 6.0 Sybase Wire Protocol. Also ASE Client is also inserting the data in database directly in to the table.

Again I have changed th DataType for the table from Image to varbinary, So its behaving correctly for small amount of data (within the limit of page size of DB which is 2K in my case), but again its failing for large amount of data.

I have also used text/unitext they all are behaving same as Image data type.
 

I can sense this may be  compatibility issue of ODBC drivers with Sybase 15.7 which are present in WMB7 Broker. Any kind of direction would be great help 

All Replies
  • Well, Sybase 15.7 was not supported with Connect for ODBC until the 6.1 release so you may encounter problems when connecting to that version of the database with the 6.0 driver.  Here are the details of the specific hotfix level that is required:  http://ow.ly/AGnVK

  • : Can you please let me know for what datatype/issue this hotfix has been introduced

  • I'm sorry, , I'm not following your question.  Are you asking what fixes are included in 6.1 drivers?  If so, the driver packages always contain a fixes.txt file that will include a list of all the issues that have been resolved in the drivers.

  • ODBCTraces.txt

    | my problem is a little bit typical. Am trying to insert the data in Sybase 15.7 database table from WMB 7.0 Message flow using DataDirect 6.0 Sybase Wire Protocol.

    Database table is containing one column with Image Datatype and other datatype is Integer and from Message flow am using BLOB dataype.

    And insert operation is failing in any case.

    The same flow was working correctly in Sybase 12.5 with same Driver. I have checked in ODBC traces but not able to figure out the error in traces as well. Am attaching the traces for more details.

    Your kind help is much appreciated.

     

  • Keep in mind that the 6.0 Sybase ODBC driver is not certified with Sybase 15.7 meaning it has not been tested.  That means that we may find that some functionality does not work correctly with that combination.  So, what you really want to do first is get a driver that is designed to work with that version of Sybase.

    You are using the ODBC drivers that are including with WMB, right?  I know that WMB does ship later versions of the ODBC drivers but I am not sure what they make available with WMB 7.0.  Have you reached out to them yet to see if they can provide a version of the driver that is certified for use with Sybase 15.7?  I do believe that is an important step in getting this to work correctly.

  • And where exactly I can get information which version of DataDirect ODBC Driver to use for Sybase 15.7

  • Connect for ODBC 6.1 was the first version that supported Sybase 15.7.  Versions 7.0 and 7.1 support it as well.  You can view information on what exactly is supported by the current drivers, 7.1, in ODBC support matrix:  http://ow.ly/AJtVW

    I do think it is still a good idea to talk to the WMB people.  They may also have requirements for supporting Sybase 15.7 as well as updated drivers.  They should be able to provide guidance on the correct WMB configuration to work with that database.