 | | | ODBC 3.51.22 not working with Systat | ODBC 3.51.22 not working with Systat 2007-11-29 - By Gary Lewis
Back
Good idea. WinSQL worked fine for me also. Which would seem to point to a
problem with Systat, but not definitively. For example, the default DSN
configuration might work fine for WinSQL but not for Systat. In the MySQL
refman-5 (See http://man-5.ora-code.com).1-en.pdf, 26.1.3.5, p1397, there's a very nice table for
recommended option configurations for selected applications. Unfortunately,
Systat is not one of those listed.
In any event, I've requested help from Systat support.
Thanks for your help.
Gary
On Nov 29, 2007 11:40 AM, Imran Abizar <imranh@(protected)> wrote:
> Try using another ODBC client such as WinSQL and see how does that
> behave. Before posting this reply I tried running the following queries
> with WinSQL and it worked, at least on my end.
>
> SHOW TABLE STATUS
> SHOW TABLE STATUS LIKE 't1'
>
> Regards.
>
>
>
>
> Gary Lewis wrote:
> > Hi - I downloaded and installed mysql-connector-odbc-3 (See http://dbc-3.ora-code.com).51.22-win32.msi.
> The
> > OS is MS Windows XP Professional Version 2002 SP2. The installation
> > completed successfully. I used ODBC Data Source Administrator to create
> and
> > successfully test a DSN using the MySQL ODBC 3.51 driver.
> >
> > What doesn't work is Systat (v 12.01.02) when I try to access a MySQL
> > database table via ODBC. It sees the Data Source I created, but it does
> not
> > list the database (ie, schema) or any tables. These are grayed out and
> just
> > hung.
> >
> > Here's the last bit of the sql.log trace file:
> > SYSTAT c40-f60 ENTER SQLGetData
> > HSTMT 05082B88
> > UWORD 12
> > SWORD 1 <SQL_C_CHAR>
> > PTR 0x0012C18C
> > SQLLEN 128
> > SQLLEN * 0x0012C20C
> > SYSTAT c40-f60 EXIT SQLGetData with return code 0
> (SQL_SUCCESS)
> > HSTMT 05082B88
> > UWORD 12
> > SWORD 1 <SQL_C_CHAR>
> > PTR 0x0012C18C
> > SQLLEN 128
> > SQLLEN * 0x0012C20C (0)
> > SYSTAT c40-f60 ENTER SQLFetch
> > HSTMT 05082B88
> > SYSTAT c40-f60 EXIT SQLFetch with return code 100
> > (SQL_NO_DATA_FOUND)
> > HSTMT 05082B88
> > SYSTAT c40-f60 ENTER SQLFreeStmt
> > HSTMT 05082B88
> > UWORD 1 <SQL_DROP>
> > SYSTAT c40-f60 EXIT SQLFreeStmt with return code 0
> (SQL_SUCCESS)
> > HSTMT 05082B88
> > UWORD 1 <SQL_DROP>
> >
> > And the myodbc.log file:
> > -- Query logging
> > --
> > -- Driver name: MySQL ODBC 3.51 Driver Version: 03.51.22
> > -- Timestamp: 071129 11:24:18
> > SHOW TABLE STATUS ;
> > SHOW TABLE STATUS LIKE 't1';
> >
> > What I'd like to figure out is if this is a MySQL ODBC Connector problem
> or
> > a Systat problem. I'm using a 30-day trial version of Systat, but it's
> > supposed to be a fully functional version.
> >
> > Any help would be appreciated. Thanks.
> >
> > Gary
> >
> >
>
|
|
|