Book a Demo

Author Topic: Sybase ODBC import bug  (Read 7587 times)

Laurent_F

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
  • EA registered user!
    • View Profile
Sybase ODBC import bug
« on: September 30, 2003, 12:29:35 pm »
When reverse-engineering from Sybase, I get the following error message:

[INTERSOLV][ODBC SQL Server driver]Number of bound columns exceeds the number of result columns.

I get a messagebox for each table imported, so it is quite annoying for large reverse engineering taks. Is there a fix for this?

I'm using the ODBC driver bundled with the Sybase 11 client against a Sybase 11.9 server.

[great tool otherwise]

Tjerk

  • EA User
  • **
  • Posts: 231
  • Karma: +1/-0
    • View Profile
Re: Sybase ODBC import bug
« Reply #1 on: February 18, 2004, 02:29:59 am »
Hi Laurent,

I now find myself in the same position (same error message). Did you find any clue to solve the problem? It also seems like EA does not recognize all the types correctly (varchar[2147483647] instead of text). Do you experience the same?

Greetings,
Tjerk

Laurent_F

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
  • EA registered user!
    • View Profile
Re: Sybase ODBC import bug
« Reply #2 on: February 18, 2004, 06:09:02 am »
I never got a response nor fix. Are you using build #660? Maybe it has datatypes that were missing in prior builds. (I'm saying that because I have encountered a similar issue reverse-engineering a MS SQLServer DB and the latest build (#660) had all the datatypes defined and it solved the problem). Otherwise, I would open a bug report.

Tjerk

  • EA User
  • **
  • Posts: 231
  • Karma: +1/-0
    • View Profile
Re: Sybase ODBC import bug
« Reply #3 on: February 18, 2004, 11:46:04 pm »
Thanks for the reaction. I'm using build 355, so I have to check with the new version. Maybe it has something to do with the ODBC driver settings. Maybe I can try adding the datatypes. If I find the answer, I will repost.

hd

  • EA Administrator
  • EA User
  • *****
  • Posts: 312
  • Karma: +0/-0
    • View Profile
Re: Sybase ODBC import bug
« Reply #4 on: February 19, 2004, 02:30:44 pm »
The Sybase data types in EA refer to Sybase's Adaptive Server Anywhere 8 datatypes, which is why there is some confusion,  :-[ and causing problems importing from a Sybase 11 database.

We intend adding support for Sybase 11 in the future.

Tjerk

  • EA User
  • **
  • Posts: 231
  • Karma: +1/-0
    • View Profile
Re: Sybase ODBC import bug
« Reply #5 on: February 23, 2004, 11:58:03 pm »
Thanks Henk, I'll check if that's the case and, if it is, wait for the support of Sybase 11.

dandekar

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Sybase ODBC import bug
« Reply #6 on: September 22, 2004, 01:16:41 pm »
I get this error trying to import Sybase ASE 12.5 tables with EA 4.10.731

The driver I am using is MERANT.

Error is :
[MERANT][ODBC Sybase ASE driver] Number of bound columns exceeds number of result columns.

sagusev

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Sybase ODBC import bug
« Reply #7 on: September 24, 2004, 06:01:14 am »
Hi, Henk!
We are getting similar error connecting using Datadirect 4.20 and Merant 3.60 ODBC to Progress 10.0A and 9.1D respectively. Is there any workaround? Will EA support Progress?

Thanx in advance,
Sergey Gusev

hd

  • EA Administrator
  • EA User
  • *****
  • Posts: 312
  • Karma: +0/-0
    • View Profile
Re: Sybase ODBC import bug
« Reply #8 on: September 26, 2004, 03:21:34 pm »
EA supports the DBMS for which datatypes are provided, namely DB2, InterBase, MSAccess, MySQL, Oracle, PostgreSQL, SQL Server and Sybase Adaptive Server Anywhere.

We have plans to include Sybase ASE, but no plans yet for Progress.

voonis

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Sybase ODBC import bug
« Reply #9 on: October 20, 2004, 10:38:05 am »
Using Sybase ASA 7.01 and Sparx 4.10.739

When I Reverse Engineer Database (Project -> Database Engineering -> Import DB Schema from ODBC) all field types are imported as varchar (255).

Any idea why is occurs?  Available datatypes in my database seem to match up with available Sybase datatypes in Sparx