I'm in the middle of migrating an existing MS SQL database to MaxDB and while experimenting with pointing the application that's generating the database information at the MaxDB server, I am encountering what I hope is a trivial problem for someone on this list.
I have created an instance for use with the database and the application "should" create the tables dynamically when it connects and sees that they are missing. However, I get an error that I am unable to make go away. The following is an excerpt from the trace log: SELECT TYPE_NAME, DATA_TYPE, PRECISION, LITERAL_PREFIX, LITERAL_SUFFIX, CREATE_PARAMS, NULLABLE, CASE_SENSITIVE, SEARCHABLE, UNSIGNED_ATTRIBUTE, MONEY, AUTO_INCREMENT, LOCAL_TYPE_NAME, MINIMUM_SCALE, MAXIMUM_SCALE FROM SYSDBA. SYSODBCTYPES ORDER BY 2, 1 PARSE : CMD : SQLCODE: -4004 Unknown table name:SYSODBCTYPES PARSEID: OUTPUT: 00000000 00000000 00000000 00000000 SQLERRD(INDEX_6) : 220 ERROR NEAR ^ : CALE FROM ^SYSDBA.SYS START : DATE : 2006-04-05 TIME : 0008:40:02 END : DATE : 2006-04-05 TIME : 0008:40:02 I have dropped an recreated the instance in the hopes that the problem with the missing TRIGGER.py file was causing the load_systab to bail before adding in the SYSODBCTYPES table (yes, I installed from rpm). Alas, that is not the case and I'm stuck. Of note: The client is running Windows NT4.0 SP6a. Since the 7.6.00.16 release of maxodbc doesn't work with NT4.0 due (see http://www.mysqltalk.org/maxdb-and-windows-odbc-driver-vt76235.html ) I installed sqlstudio and tried using the sqlstudioodbc driver instead. It failed as well, but I couldn't get it to create a trace file for some reason. Server is running MaxDB 7.6.00.16 installed from rpm on SuSE ES 9. Any pointers are appreciated. Thanks, --Robert -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
