From gracinet at nuxeo.com Thu Dec 7 14:22:01 2006 From: gracinet at nuxeo.com (Georges Racinet) Date: Thu Dec 7 14:22:07 2006 Subject: [egenix-users] mx.ODBC.unixODBC: Datasource not found Message-ID: <93590867-7889-4E1E-86D9-23BD5D140AA3@nuxeo.com> Hi everyone, I'm trying to get mxODBC to work with unixODBC, and I get the following error [iODBC] Datasource not found and not default driver (from memory, sorry) Actually, as those also reading the unixODBC support mailing-list already know, my unixODBC setup doesn't work so well, but it can initiate a connection, the odbc.ini and odbcinst.ini are thus ok. This really looks as if those files were ignored in the mxODBC context. I tried to duplicate my .ini files from to /etc/unixODBC/ to /etc/, with no effect. Tried to play with ODBCINI env variable - same. I'm a bit confused by the [iODBC] appearing in the error message. I imported mx.ODBC.unixODBC and tried both 'connect' and 'DriverConnect' Any help would be very appreciated, thank you very much ! Have a nice day. PS: BTW this will be used in a Zope context. I suppose it's ok to validate that the connection works with the pure python library and by the Zope encapsulated version licences, right ? --------- Georges Racinet, Nuxeo SAS Open Source Enterprise Content Management (ECM) Web: http://www.nuxeo.com/ and http://www.nuxeo.org/ - Tel: +33 1 40 33 79 87 From charlie at egenix.com Thu Dec 7 15:45:56 2006 From: charlie at egenix.com (Charlie Clark) Date: Thu Dec 7 15:46:04 2006 Subject: [egenix-users] mx.ODBC.unixODBC: Datasource not found In-Reply-To: <93590867-7889-4E1E-86D9-23BD5D140AA3@nuxeo.com> References: <93590867-7889-4E1E-86D9-23BD5D140AA3@nuxeo.com> Message-ID: Am 07.12.2006, 14:22 Uhr, schrieb Georges Racinet : > Hi everyone, > I'm trying to get mxODBC to work with unixODBC, and I get the following > error > [iODBC] Datasource not found and not default driver (from memory, sorry) Please provide a full traceback. > Actually, as those also reading the unixODBC support mailing-list > already know, my > unixODBC setup doesn't work so well, but it can initiate a connection, > the odbc.ini and odbcinst.ini We're not on that list and are, therefore, not familiar with your setup. > are thus ok. This really looks as if those files were ignored in the > mxODBC context. Presumably but it can't find it. > I tried to duplicate my .ini files from to /etc/unixODBC/ to /etc/, > with no effect. Check your paths and envrionment varibales including LDCONFIG > Tried to play with ODBCINI env variable - same. > I'm a bit confused by the [iODBC] appearing in the error message. I > imported > mx.ODBC.unixODBC and tried both 'connect' and 'DriverConnect' We are also a bit surprised but without your code and the tracebacks there is nothing we can do. > Any help would be very appreciated, thank you very much ! > Have a nice day. > PS: BTW this will be used in a Zope context. I suppose it's ok to > validate that the connection works > with the pure python library and by the Zope encapsulated version > licences, right ? Sorry, I do not understand what you mean here. The mxODBC Zope DA contains a different version of mxODBC than mxCommercial. Charlie From matt at finaldraftbooks.com Sun Dec 10 17:59:09 2006 From: matt at finaldraftbooks.com (Matthew Singer) Date: Sun Dec 10 23:59:16 2006 Subject: [egenix-users] Python 2.5 binaries for windows of the variousMXpackages Message-ID: <001201c71cae$cdb49680$0a00a8c0@PlanetX> Egenix-mx-commercial for 2.5 any closer? Moof wrote: > Hi there, > > Any ideas when the 2.5 binaries for windows for the various mx pyton > extensions will come out? We're currently planing to release a new version of both egenix-mx-base and egenix-mx-commercial in the next few weeks which will also support the new Python C API after PEP 353 was applied in Python 2.5: http://docs.python.org/dev/whatsnew/pep-353.html We've put up a Windows installer for Python 2.5 up on the web-site: http://www.egenix.com/files/python/eGenix-mx-Extensions.html#Download-mxBASE Remainder cut... -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20061210/9fd2ddd7/attachment.htm From mal at egenix.com Mon Dec 11 16:36:48 2006 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Dec 11 16:36:55 2006 Subject: [egenix-users] Python 2.5 binaries for windows of the various mx packages In-Reply-To: <001201c71cae$cdb49680$0a00a8c0@PlanetX> References: <001201c71cae$cdb49680$0a00a8c0@PlanetX> Message-ID: <457D7B10.2010602@egenix.com> Matthew Singer wrote: > Egenix-mx-commercial for 2.5 any closer? Yes. We're working on a new release for both packages, which will include updated documentation, Python datetime support and support for the changes in Python 2.5. Unfortunately, this process has taken a bit longer than we thought, so we're likely to cut the release early in January. > Moof wrote: > Hi there, > > Any ideas when the 2.5 binaries for windows for > the various mx pyton > extensions will come out? We're currently planing to > release a new version of both egenix-mx-base and egenix-mx-commercial in the > next few weeks which will also support the new Python C API after PEP 353 > was applied in Python 2.5: > > http://docs.python.org/dev/whatsnew/pep-353.html We've put up a Windows > installer for Python 2.5 up on the web-site: > > http://www.egenix.com/files/python/eGenix-mx-Extensions.html#Download-mxBASE > > > Remainder cut... -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Dec 11 2006) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From g.mattiuzzi at miriade.it Fri Dec 15 11:40:31 2006 From: g.mattiuzzi at miriade.it (Gianluca Mattiuzzi) Date: Fri Dec 15 11:41:53 2006 Subject: [egenix-users] Error message: ('IM004', 0, "[unixODBC][Driver Manager]Driver'sSQLA llocHandle on SQL_HANDLE_HENV failed", 8227) Message-ID: <45827B9F.3060705@miriade.it> *Dear, when I try to connect to Oracle 10g with mxODBC DA Plone reports this error :* ------------------------- Problem connecting to the database Connection string: DSN=DBTEST Connection pool entry: 0 Error message: ('IM004', 0, "[unixODBC][Driver Manager]Driver's SQLA llocHandle on SQL_HANDLE_HENV failed", 8227) ------------------------- *The unixODBC log is :* ------------------------- [ODBC][1280][SQLAllocHandle.c][345] Entry: Handle Type = 2 Input Handle = 0xa85a4b0 [ODBC][1280][SQLAllocHandle.c][463] Exit:[SQL_SUCCESS] Output Handle = 0xbaa45d8 [ODBC][1280][SQLDriverConnect.c][678] Entry: Connection = 0xbaa45d8 Window Hdl = (nil) Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length = 38 (SQL_NTS)] Str Out = 0x5c491f8 Str Out Max = 512 Str Out Ptr = 0x5c491f6 Completion = 0 UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE' [ODBC][1280][SQLConnect.c][1293]Error: IM004 [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_SUCCESS] SQLState = IM004 Native = 0x5c48f70 -> 0 Message Text = [[unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_HENV failed] [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_NO_DATA] [ODBC][1280][SQLFreeHandle.c][268] Entry: Handle Type = 2 Input Handle = 0xbaa45d8 [ODBC][1280][SQLFreeHandle.c][317] Exit:[SQL_SUCCESS] [ODBC][1280][SQLAllocHandle.c][345] Entry: Handle Type = 2 Input Handle = 0xa85a4b0 [ODBC][1280][SQLAllocHandle.c][463] Exit:[SQL_SUCCESS] Output Handle = 0xbaa45d8 [ODBC][1280][SQLDriverConnect.c][678] Entry: Connection = 0xbaa45d8 Window Hdl = (nil) Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length = 38 (SQL_NTS)] Str Out = 0x5c491f8 Str Out Max = 512 Str Out Ptr = 0x5c491f6 Completion = 0 UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE' [ODBC][1280][SQLConnect.c][1293]Error: IM004 [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_SUCCESS] SQLState = IM004 Native = 0x5c48f70 -> 0 Message Text = [[unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_HENV failed] [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_NO_DATA] [ODBC][1280][SQLFreeHandle.c][268] Entry: Handle Type = 2 Input Handle = 0xbaa45d8 [ODBC][1280][SQLFreeHandle.c][317] Exit:[SQL_SUCCESS] [ODBC][1280][SQLAllocHandle.c][345] Entry: Handle Type = 2 Input Handle = 0xa85a4b0 [ODBC][1280][SQLAllocHandle.c][463] Exit:[SQL_SUCCESS] Output Handle = 0xbaa45d8 [ODBC][1280][SQLDriverConnect.c][678] Entry: Connection = 0xbaa45d8 Window Hdl = (nil) Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length = 38 (SQL_NTS)] Str Out = 0x5c491f8 Str Out Max = 512 Str Out Ptr = 0x5c491f6 Completion = 0 UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE' [ODBC][1280][SQLConnect.c][1293]Error: IM004 [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_SUCCESS] SQLState = IM004 Native = 0x5c48f70 -> 0 Message Text = [[unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_HENV failed] [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_NO_DATA] [ODBC][1280][SQLFreeHandle.c][268] Entry: Handle Type = 2 Input Handle = 0xbaa45d8 [ODBC][1280][SQLFreeHandle.c][317] Exit:[SQL_SUCCESS] ------------------------- * The problem is the same if I connect with isql without set $ORACLE_HOME. Can I tell to mxODBC DA where is the Oracle Home? There is a workaround or a special Linux configuration? * -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20061215/e6e201c7/attachment.htm From g.mattiuzzi at miriade.it Fri Dec 15 16:31:47 2006 From: g.mattiuzzi at miriade.it (Gianluca Mattiuzzi) Date: Fri Dec 15 16:33:21 2006 Subject: [egenix-users] help Message-ID: <4582BFE3.1050404@miriade.it> *Dear, when I try to connect to Oracle 10g with mxODBC DA Plone reports this error :* ------------------------- Problem connecting to the database Connection string: DSN=DBTEST Connection pool entry: 0 Error message: ('IM004', 0, "[unixODBC][Driver Manager]Driver's SQLA llocHandle on SQL_HANDLE_HENV failed", 8227) ------------------------- *The unixODBC log is :* ------------------------- [ODBC][1280][SQLAllocHandle.c][345] Entry: Handle Type = 2 Input Handle = 0xa85a4b0 [ODBC][1280][SQLAllocHandle.c][463] Exit:[SQL_SUCCESS] Output Handle = 0xbaa45d8 [ODBC][1280][SQLDriverConnect.c][678] Entry: Connection = 0xbaa45d8 Window Hdl = (nil) Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length = 38 (SQL_NTS)] Str Out = 0x5c491f8 Str Out Max = 512 Str Out Ptr = 0x5c491f6 Completion = 0 UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE' [ODBC][1280][SQLConnect.c][1293]Error: IM004 [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_SUCCESS] SQLState = IM004 Native = 0x5c48f70 -> 0 Message Text = [[unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_HENV failed] [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_NO_DATA] [ODBC][1280][SQLFreeHandle.c][268] Entry: Handle Type = 2 Input Handle = 0xbaa45d8 [ODBC][1280][SQLFreeHandle.c][317] Exit:[SQL_SUCCESS] [ODBC][1280][SQLAllocHandle.c][345] Entry: Handle Type = 2 Input Handle = 0xa85a4b0 [ODBC][1280][SQLAllocHandle.c][463] Exit:[SQL_SUCCESS] Output Handle = 0xbaa45d8 [ODBC][1280][SQLDriverConnect.c][678] Entry: Connection = 0xbaa45d8 Window Hdl = (nil) Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length = 38 (SQL_NTS)] Str Out = 0x5c491f8 Str Out Max = 512 Str Out Ptr = 0x5c491f6 Completion = 0 UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE' [ODBC][1280][SQLConnect.c][1293]Error: IM004 [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_SUCCESS] SQLState = IM004 Native = 0x5c48f70 -> 0 Message Text = [[unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_HENV failed] [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_NO_DATA] [ODBC][1280][SQLFreeHandle.c][268] Entry: Handle Type = 2 Input Handle = 0xbaa45d8 [ODBC][1280][SQLFreeHandle.c][317] Exit:[SQL_SUCCESS] [ODBC][1280][SQLAllocHandle.c][345] Entry: Handle Type = 2 Input Handle = 0xa85a4b0 [ODBC][1280][SQLAllocHandle.c][463] Exit:[SQL_SUCCESS] Output Handle = 0xbaa45d8 [ODBC][1280][SQLDriverConnect.c][678] Entry: Connection = 0xbaa45d8 Window Hdl = (nil) Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length = 38 (SQL_NTS)] Str Out = 0x5c491f8 Str Out Max = 512 Str Out Ptr = 0x5c491f6 Completion = 0 UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE' [ODBC][1280][SQLConnect.c][1293]Error: IM004 [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_SUCCESS] SQLState = IM004 Native = 0x5c48f70 -> 0 Message Text = [[unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_HENV failed] [ODBC][1280][SQLError.c][424] Entry: Connection = 0xbaa45d8 SQLState = 0x5c48f78 Native = 0x5c48f70 Message Text = 0x5c48f88 Buffer Length = 511 Text Len Ptr = 0x5c48f76 [ODBC][1280][SQLError.c][461] Exit:[SQL_NO_DATA] [ODBC][1280][SQLFreeHandle.c][268] Entry: Handle Type = 2 Input Handle = 0xbaa45d8 [ODBC][1280][SQLFreeHandle.c][317] Exit:[SQL_SUCCESS] ------------------------- * The problem is the same if I connect with isql without set $ORACLE_HOME. With $ORACLE_HOME set isql work, but mxODBC DA return the error. Can I tell to mxODBC DA where is the Oracle Home? Is there a workaround or a special Linux configuration?? THANK YOU FOR SUPPORT BYE * From charlie at egenix.com Fri Dec 15 16:34:46 2006 From: charlie at egenix.com (Charlie Clark) Date: Fri Dec 15 16:35:01 2006 Subject: [egenix-users] Error message: ('IM004', 0, "[unixODBC][Driver Manager]Driver'sSQLA llocHandle on SQL_HANDLE_HENV failed", 8227) In-Reply-To: <45827B9F.3060705@miriade.it> References: <45827B9F.3060705@miriade.it> Message-ID: Am 15.12.2006, 11:40 Uhr, schrieb Gianluca Mattiuzzi : > The problem is the same if I connect with isql without set $ORACLE_HOME. > Can I tell to mxODBC DA where is the Oracle Home? > There is a workaround or a special Linux configuration? This is not an mxODBC problem. Please check the documentation for your Oracle ODBC driver. Sincerely Charlie Clark From fabiorizzo at gmail.com Fri Dec 15 13:46:56 2006 From: fabiorizzo at gmail.com (Fabio Rizzo Matos) Date: Fri Dec 15 16:47:11 2006 Subject: [egenix-users] help In-Reply-To: <4582BFE3.1050404@miriade.it> References: <4582BFE3.1050404@miriade.it> Message-ID: Hi Gianluca, You set the variables of the Oracle? you need to set then to run correctly the connection. Cheers On 12/15/06, Gianluca Mattiuzzi wrote: > > *Dear, > when I try to connect to Oracle 10g with mxODBC DA Plone reports this > error :* > > ------------------------- > Problem connecting to the database > > Connection string: DSN=DBTEST > > Connection pool entry: 0 > > Error message: ('IM004', 0, "[unixODBC][Driver Manager]Driver's SQLA > llocHandle on SQL_HANDLE_HENV failed", 8227) > ------------------------- > > *The unixODBC log is :* > > ------------------------- > [ODBC][1280][SQLAllocHandle.c][345] > Entry: > Handle Type = 2 > Input Handle = 0xa85a4b0 > [ODBC][1280][SQLAllocHandle.c][463] > Exit:[SQL_SUCCESS] > Output Handle = 0xbaa45d8 > [ODBC][1280][SQLDriverConnect.c][678] > Entry: > Connection = 0xbaa45d8 > Window Hdl = (nil) > Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length = > 38 (SQL_NTS)] > Str Out = 0x5c491f8 > Str Out Max = 512 > Str Out Ptr = 0x5c491f6 > Completion = 0 > UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE' > > [ODBC][1280][SQLConnect.c][1293]Error: IM004 > [ODBC][1280][SQLError.c][424] > Entry: > Connection = 0xbaa45d8 > SQLState = 0x5c48f78 > Native = 0x5c48f70 > Message Text = 0x5c48f88 > Buffer Length = 511 > Text Len Ptr = 0x5c48f76 > [ODBC][1280][SQLError.c][461] > Exit:[SQL_SUCCESS] > SQLState = IM004 > Native = 0x5c48f70 -> 0 > Message Text = [[unixODBC][Driver Manager]Driver's > SQLAllocHandle on SQL_HANDLE_HENV failed] > [ODBC][1280][SQLError.c][424] > Entry: > Connection = 0xbaa45d8 > SQLState = 0x5c48f78 > Native = 0x5c48f70 > Message Text = 0x5c48f88 > Buffer Length = 511 > Text Len Ptr = 0x5c48f76 > [ODBC][1280][SQLError.c][461] > Exit:[SQL_NO_DATA] > [ODBC][1280][SQLFreeHandle.c][268] > Entry: > Handle Type = 2 > Input Handle = 0xbaa45d8 > [ODBC][1280][SQLFreeHandle.c][317] > Exit:[SQL_SUCCESS] > [ODBC][1280][SQLAllocHandle.c][345] > Entry: > Handle Type = 2 > Input Handle = 0xa85a4b0 > [ODBC][1280][SQLAllocHandle.c][463] > Exit:[SQL_SUCCESS] > Output Handle = 0xbaa45d8 > [ODBC][1280][SQLDriverConnect.c][678] > Entry: > Connection = 0xbaa45d8 > Window Hdl = (nil) > Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length = > 38 (SQL_NTS)] > Str Out = 0x5c491f8 > Str Out Max = 512 > Str Out Ptr = 0x5c491f6 > Completion = 0 > UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE' > > [ODBC][1280][SQLConnect.c][1293]Error: IM004 > [ODBC][1280][SQLError.c][424] > Entry: > Connection = 0xbaa45d8 > SQLState = 0x5c48f78 > Native = 0x5c48f70 > Message Text = 0x5c48f88 > Buffer Length = 511 > Text Len Ptr = 0x5c48f76 > [ODBC][1280][SQLError.c][461] > Exit:[SQL_SUCCESS] > SQLState = IM004 > Native = 0x5c48f70 -> 0 > Message Text = [[unixODBC][Driver Manager]Driver's > SQLAllocHandle on SQL_HANDLE_HENV failed] > [ODBC][1280][SQLError.c][424] > Entry: > Connection = 0xbaa45d8 > SQLState = 0x5c48f78 > Native = 0x5c48f70 > Message Text = 0x5c48f88 > Buffer Length = 511 > Text Len Ptr = 0x5c48f76 > [ODBC][1280][SQLError.c][461] > Exit:[SQL_NO_DATA] > [ODBC][1280][SQLFreeHandle.c][268] > Entry: > Handle Type = 2 > Input Handle = 0xbaa45d8 > [ODBC][1280][SQLFreeHandle.c][317] > Exit:[SQL_SUCCESS] > [ODBC][1280][SQLAllocHandle.c][345] > Entry: > Handle Type = 2 > Input Handle = 0xa85a4b0 > [ODBC][1280][SQLAllocHandle.c][463] > Exit:[SQL_SUCCESS] > Output Handle = 0xbaa45d8 > [ODBC][1280][SQLDriverConnect.c][678] > Entry: > Connection = 0xbaa45d8 > Window Hdl = (nil) > Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length = > 38 (SQL_NTS)] > Str Out = 0x5c491f8 > Str Out Max = 512 > Str Out Ptr = 0x5c491f6 > Completion = 0 > UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE' > > [ODBC][1280][SQLConnect.c][1293]Error: IM004 > [ODBC][1280][SQLError.c][424] > Entry: > Connection = 0xbaa45d8 > SQLState = 0x5c48f78 > Native = 0x5c48f70 > Message Text = 0x5c48f88 > Buffer Length = 511 > Text Len Ptr = 0x5c48f76 > [ODBC][1280][SQLError.c][461] > Exit:[SQL_SUCCESS] > SQLState = IM004 > Native = 0x5c48f70 -> 0 > Message Text = [[unixODBC][Driver Manager]Driver's > SQLAllocHandle on SQL_HANDLE_HENV failed] > [ODBC][1280][SQLError.c][424] > Entry: > Connection = 0xbaa45d8 > SQLState = 0x5c48f78 > Native = 0x5c48f70 > Message Text = 0x5c48f88 > Buffer Length = 511 > Text Len Ptr = 0x5c48f76 > [ODBC][1280][SQLError.c][461] > Exit:[SQL_NO_DATA] > [ODBC][1280][SQLFreeHandle.c][268] > Entry: > Handle Type = 2 > Input Handle = 0xbaa45d8 > [ODBC][1280][SQLFreeHandle.c][317] > Exit:[SQL_SUCCESS] > ------------------------- > * > The problem is the same if I connect with isql without set $ORACLE_HOME. > With $ORACLE_HOME set isql work, but mxODBC DA return the error. > Can I tell to mxODBC DA where is the Oracle Home? > Is there a workaround or a special Linux configuration?? > > THANK YOU FOR SUPPORT > > BYE > * > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users > -- Fabio Rizzo ThreePointsWeb fabiorizzo@threepointsweb.com ------------------ next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20061215/c7f080a9/attachment.htm From fabiorizzo at gmail.com Fri Dec 15 14:19:54 2006 From: fabiorizzo at gmail.com (Fabio Rizzo Matos) Date: Fri Dec 15 17:20:03 2006 Subject: [egenix-users] help In-Reply-To: <4582C54A.6050502@miriade.it> References: <4582BFE3.1050404@miriade.it> <4582C54A.6050502@miriade.it> Message-ID: the user that run zope, must set this variables. do you do that? On 12/15/06, Gianluca Mattiuzzi wrote: > > Dear, > what are the varibles? > how I can set the variables? > > I set ORACLE_HOME : > export ORACLE_HOME= > > with isql it's all ok, but in mxODBC DA an error occur. > > Fabio Rizzo Matos ha scritto: > > Hi Gianluca, > > > > You set the variables of the Oracle? you need to set then to run > > correctly the connection. > > > > Cheers > > > > On 12/15/06, *Gianluca Mattiuzzi * > > wrote: > > > > *Dear, > > when I try to connect to Oracle 10g with mxODBC DA Plone reports > this > > error :* > > > > ------------------------- > > Problem connecting to the database > > > > Connection string: DSN=DBTEST > > > > Connection pool entry: 0 > > > > Error message: ('IM004', 0, "[unixODBC][Driver > > Manager]Driver's SQLA > > llocHandle on SQL_HANDLE_HENV failed", 8227) > > ------------------------- > > > > *The unixODBC log is :* > > > > ------------------------- > > [ODBC][1280][SQLAllocHandle.c][345] > > Entry: > > Handle Type = 2 > > Input Handle = 0xa85a4b0 > > [ODBC][1280][SQLAllocHandle.c][463] > > Exit:[SQL_SUCCESS] > > Output Handle = 0xbaa45d8 > > [ODBC][1280][SQLDriverConnect.c][678] > > Entry: > > Connection = 0xbaa45d8 > > Window Hdl = (nil) > > Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length > = > > 38 (SQL_NTS)] > > Str Out = 0x5c491f8 > > Str Out Max = 512 > > Str Out Ptr = 0x5c491f6 > > Completion = 0 > > UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE > 'UCS-2LE' > > > > [ODBC][1280][ SQLConnect.c][1293]Error: IM004 > > [ODBC][1280][SQLError.c][424] > > Entry: > > Connection = 0xbaa45d8 > > SQLState = 0x5c48f78 > > Native = 0x5c48f70 > > Message Text = 0x5c48f88 > > Buffer Length = 511 > > Text Len Ptr = 0x5c48f76 > > [ODBC][1280][SQLError.c][461] > > Exit:[SQL_SUCCESS] > > SQLState = IM004 > > Native = 0x5c48f70 -> 0 > > Message Text = [[unixODBC][Driver Manager]Driver's > > SQLAllocHandle on SQL_HANDLE_HENV failed] > > [ODBC][1280][SQLError.c][424] > > Entry: > > Connection = 0xbaa45d8 > > SQLState = 0x5c48f78 > > Native = 0x5c48f70 > > Message Text = 0x5c48f88 > > Buffer Length = 511 > > Text Len Ptr = 0x5c48f76 > > [ODBC][1280][SQLError.c][461] > > Exit:[SQL_NO_DATA] > > [ODBC][1280][SQLFreeHandle.c][268] > > Entry: > > Handle Type = 2 > > Input Handle = 0xbaa45d8 > > [ODBC][1280][SQLFreeHandle.c][317] > > Exit:[SQL_SUCCESS] > > [ODBC][1280][SQLAllocHandle.c][345] > > Entry: > > Handle Type = 2 > > Input Handle = 0xa85a4b0 > > [ODBC][1280][SQLAllocHandle.c][463] > > Exit:[SQL_SUCCESS] > > Output Handle = 0xbaa45d8 > > [ODBC][1280][SQLDriverConnect.c][678] > > Entry: > > Connection = 0xbaa45d8 > > Window Hdl = (nil) > > Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length > = > > 38 (SQL_NTS)] > > Str Out = 0x5c491f8 > > Str Out Max = 512 > > Str Out Ptr = 0x5c491f6 > > Completion = 0 > > UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE > 'UCS-2LE' > > > > [ODBC][1280][SQLConnect.c][1293]Error: IM004 > > [ODBC][1280][SQLError.c][424] > > Entry: > > Connection = 0xbaa45d8 > > SQLState = 0x5c48f78 > > Native = 0x5c48f70 > > Message Text = 0x5c48f88 > > Buffer Length = 511 > > Text Len Ptr = 0x5c48f76 > > [ODBC][1280][SQLError.c][461] > > Exit:[SQL_SUCCESS] > > SQLState = IM004 > > Native = 0x5c48f70 -> 0 > > Message Text = [[unixODBC][Driver Manager]Driver's > > SQLAllocHandle on SQL_HANDLE_HENV failed] > > [ODBC][1280][SQLError.c][424] > > Entry: > > Connection = 0xbaa45d8 > > SQLState = 0x5c48f78 > > Native = 0x5c48f70 > > Message Text = 0x5c48f88 > > Buffer Length = 511 > > Text Len Ptr = 0x5c48f76 > > [ODBC][1280][SQLError.c][461] > > Exit:[SQL_NO_DATA] > > [ODBC][1280][SQLFreeHandle.c][268] > > Entry: > > Handle Type = 2 > > Input Handle = 0xbaa45d8 > > [ODBC][1280][SQLFreeHandle.c][317] > > Exit:[SQL_SUCCESS] > > [ODBC][1280][SQLAllocHandle.c][345] > > Entry: > > Handle Type = 2 > > Input Handle = 0xa85a4b0 > > [ODBC][1280][SQLAllocHandle.c][463] > > Exit:[SQL_SUCCESS] > > Output Handle = 0xbaa45d8 > > [ODBC][1280][SQLDriverConnect.c][678] > > Entry: > > Connection = 0xbaa45d8 > > Window Hdl = (nil) > > Str In = [DSN=DBTEST;UID=reporter;PWD=**********][length > = > > 38 (SQL_NTS)] > > Str Out = 0x5c491f8 > > Str Out Max = 512 > > Str Out Ptr = 0x5c491f6 > > Completion = 0 > > UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE > 'UCS-2LE' > > > > [ODBC][1280][ SQLConnect.c][1293]Error: IM004 > > [ODBC][1280][SQLError.c][424] > > Entry: > > Connection = 0xbaa45d8 > > SQLState = 0x5c48f78 > > Native = 0x5c48f70 > > Message Text = 0x5c48f88 > > Buffer Length = 511 > > Text Len Ptr = 0x5c48f76 > > [ODBC][1280][SQLError.c][461] > > Exit:[SQL_SUCCESS] > > SQLState = IM004 > > Native = 0x5c48f70 -> 0 > > Message Text = [[unixODBC][Driver Manager]Driver's > > SQLAllocHandle on SQL_HANDLE_HENV failed] > > [ODBC][1280][SQLError.c][424] > > Entry: > > Connection = 0xbaa45d8 > > SQLState = 0x5c48f78 > > Native = 0x5c48f70 > > Message Text = 0x5c48f88 > > Buffer Length = 511 > > Text Len Ptr = 0x5c48f76 > > [ODBC][1280][SQLError.c][461] > > Exit:[SQL_NO_DATA] > > [ODBC][1280][SQLFreeHandle.c][268] > > Entry: > > Handle Type = 2 > > Input Handle = 0xbaa45d8 > > [ODBC][1280][SQLFreeHandle.c][317] > > Exit:[SQL_SUCCESS] > > ------------------------- > > * > > The problem is the same if I connect with isql without set > > $ORACLE_HOME. > > With $ORACLE_HOME set isql work, but mxODBC DA return the error. > > Can I tell to mxODBC DA where is the Oracle Home? > > Is there a workaround or a special Linux configuration?? > > > > THANK YOU FOR SUPPORT > > > > BYE > > * > > > > > > > _______________________________________________________________________ > > eGenix.com User Mailing List > > http://www.egenix.com/ > > https://www.egenix.com/mailman/listinfo/egenix-users > > > > > > > > > > -- > > Fabio Rizzo > > ThreePointsWeb > > fabiorizzo@threepointsweb.com > > ---- > > > -- Fabio Rizzo ThreePointsWeb fabiorizzo@threepointsweb.com ------------------ next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20061215/c466b6e2/attachment.htm From david.krosel at maxxian.com Fri Dec 15 11:34:04 2006 From: david.krosel at maxxian.com (David Krosel) Date: Fri Dec 15 17:34:06 2006 Subject: [egenix-users] mxODBC Zope DA and Linux Zope -- pooling not increasing Message-ID: <013001c72066$e3df1730$0101a8c0@maxdk1> Hello, Under stress testing running 20 web clients concurrently, the number of "Physical connections" doesn't go higher than "1". By observations, it is clear that multiple requests are pending since only one connection is open to the database. My configuration is as follows: mxODBC Zope DA 1.0.10 Zope 2.7.7 Pool size = 21 Number Zope threads = 21 Linux Centos 4.3 The ODBC is configured for a local MySql 4.1.x Can you help? Thank you, David-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20061215/149c4db9/attachment.htm From mal at egenix.com Tue Dec 19 22:21:44 2006 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Dec 19 22:21:51 2006 Subject: [egenix-users] mxODBC Zope DA and Linux Zope -- pooling not increasing In-Reply-To: <013001c72066$e3df1730$0101a8c0@maxdk1> References: <013001c72066$e3df1730$0101a8c0@maxdk1> Message-ID: <458857E8.9010305@egenix.com> On 2006-12-15 17:34, David Krosel wrote: > Hello, > > Under stress testing running 20 web clients concurrently, the number of "Physical connections" doesn't go higher than "1". By observations, it is clear that multiple requests are pending since only one connection is open to the database. > > My configuration is as follows: > > mxODBC Zope DA 1.0.10 > Zope 2.7.7 > Pool size = 21 > Number Zope threads = 21 > Linux Centos 4.3 > > The ODBC is configured for a local MySql 4.1.x > > Can you help? Do you see any error messages in the log file or the shell (when running Zope manually from the command line) ? It is possible that the ODBC driver doesn't allow multiple connections to the database for some reason. Which ODBC manager are you using ? If it's unixODBC, then you might be experiencing the following problem with unixODBC: """ When using mxODBC Zope DA with the unixODBC ODBC manager providing the connection to the ODBC driver, Zope appears to hang whenever a long running query is initiated on one of the Zope connections. This is due to the unixODBC manager applying a very restrictive thread isolation protection which basically serializes all requests to the drivers on a per process scope. For references, have a look at these links: http://www.unixodbc.org/odbcinst.html http://archives.postgresql.org/pgsql-odbc/2004-03/msg00060.php These are the available unixODBC Thread Levels (taken from the __handle.c file of unixODBC): * Level 0 - Only the DM internal structures are protected * the driver is assumed to take care of it's self * * Level 1 - The driver is protected down to the statement level * each statement will be protected, and the same for the connect * level for connect functions, note that descriptors are considered * equal to statements when it comes to thread protection. * * Level 2 - The driver is protected at the connection level. only * one thread can be in a particular driver at one time * * Level 3 - The driver is protected at the env level, only one thing * at a time. * * By default the driver open connections with a lock level of 3, * this can be changed by adding the line * * Threading = N * * to the driver entry in odbcinst.ini, where N is the locking level * (0-3) Fortunately, the fix is easy: just add the line Threading = 0 to the section in odbcinst.ini for the driver you are using, e.g. [PostgreSQL] Description = PostgreSQL driver for Linux & Win32 Driver = /usr/local/lib/libodbcpsql.so Setup = /usr/local/lib/libodbcpsqlS.so Threading = 0 Note that "Threading = 0" is normally only allowed for ODBC drivers which are fully multi-threaded, however, since the mxODBC Zope DA already provides the necessary thread protection at the connection level, you can get some added performance by disabling the additional protection in the unixODBC manager. The iODBC manager does not seem to have this problem. So this is a second alternative to solve the problem. """ -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Dec 19 2006) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From david.krosel at maxxian.com Tue Dec 19 17:04:25 2006 From: david.krosel at maxxian.com (David Krosel) Date: Tue Dec 19 23:04:05 2006 Subject: [egenix-users] mxODBC Zope DA and Linux Zope -- pooling not increasing References: <013001c72066$e3df1730$0101a8c0@maxdk1> <458857E8.9010305@egenix.com> Message-ID: <002101c723b9$a6655850$0101a8c0@maxdk1> Hello Marc-Andre, We are using unixODBC and unfortunately, the "Threading" option is not being used in our odbcinst.ini. This is very good news and I will try it immediately. Thank you for your response. Regards, David ----- Original Message ----- From: "M.-A. Lemburg" To: "David Krosel" Cc: Sent: Tuesday, December 19, 2006 4:21 PM Subject: Re: [egenix-users] mxODBC Zope DA and Linux Zope -- pooling not increasing > On 2006-12-15 17:34, David Krosel wrote: >> Hello, >> >> Under stress testing running 20 web clients concurrently, the number of >> "Physical connections" doesn't go higher than "1". By observations, it is >> clear that multiple requests are pending since only one connection is >> open to the database. >> >> My configuration is as follows: >> >> mxODBC Zope DA 1.0.10 >> Zope 2.7.7 >> Pool size = 21 >> Number Zope threads = 21 >> Linux Centos 4.3 >> >> The ODBC is configured for a local MySql 4.1.x >> >> Can you help? > > Do you see any error messages in the log file or the shell > (when running Zope manually from the command line) ? > > It is possible that the ODBC driver doesn't allow multiple > connections to the database for some reason. > > Which ODBC manager are you using ? > > If it's unixODBC, then you might be experiencing the following > problem with unixODBC: > > """ > When using mxODBC Zope DA with the unixODBC ODBC manager providing > the connection to the ODBC driver, Zope appears to hang whenever a > long running query is initiated on one of the Zope connections. > > This is due to the unixODBC manager applying a very restrictive > thread isolation protection which basically serializes all requests > to the drivers on a per process scope. > > For references, have a look at these links: > > http://www.unixodbc.org/odbcinst.html > http://archives.postgresql.org/pgsql-odbc/2004-03/msg00060.php > > These are the available unixODBC Thread Levels (taken from the > __handle.c file of unixODBC): > > * Level 0 - Only the DM internal structures are protected > * the driver is assumed to take care of it's self > * > * Level 1 - The driver is protected down to the statement level > * each statement will be protected, and the same for the connect > * level for connect functions, note that descriptors are considered > * equal to statements when it comes to thread protection. > * > * Level 2 - The driver is protected at the connection level. only > * one thread can be in a particular driver at one time > * > * Level 3 - The driver is protected at the env level, only one thing > * at a time. > * > * By default the driver open connections with a lock level of 3, > * this can be changed by adding the line > * > * Threading = N > * > * to the driver entry in odbcinst.ini, where N is the locking level > * (0-3) > > Fortunately, the fix is easy: just add the line > > Threading = 0 > > to the section in odbcinst.ini for the driver you are > using, e.g. > > [PostgreSQL] > Description = PostgreSQL driver for Linux & Win32 > Driver = /usr/local/lib/libodbcpsql.so > Setup = /usr/local/lib/libodbcpsqlS.so > Threading = 0 > > Note that "Threading = 0" is normally only allowed for ODBC drivers > which are fully multi-threaded, however, since the mxODBC Zope DA > already provides the necessary thread protection at the connection > level, you can get some added performance by disabling the additional > protection in the unixODBC manager. > > The iODBC manager does not seem to have this problem. So this > is a second alternative to solve the problem. > """ > > -- > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, Dec 19 2006) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ > ________________________________________________________________________ > > ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From mal at egenix.com Wed Dec 20 20:48:00 2006 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Dec 20 20:48:06 2006 Subject: [egenix-users] mxODBC Zope DA and Linux Zope -- pooling not increasing In-Reply-To: <003101c723c2$3289d5b0$0101a8c0@maxdk1> References: <013001c72066$e3df1730$0101a8c0@maxdk1> <458857E8.9010305@egenix.com> <003101c723c2$3289d5b0$0101a8c0@maxdk1> Message-ID: <45899370.2090106@egenix.com> Hello David, > Definite improvement, however the connection pool didn't go past '3'. > > I set "Pool Size" = 21 and zope configuration "zserver-threads 21". I > did reboot Zope. > > Did I miss something? Zope will usually only start more threads if necessary and the Zope DA will only maintain one physical connection per thread (and per Zope connection object). If you stress test the server, it should start more threads up to the limit you've set. The Zope DA will then also open more physical connections. Hope that helps, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Dec 20 2006) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: > Thank you, > David > > ----- Original Message ----- From: "M.-A. Lemburg" > To: "David Krosel" > Cc: > Sent: Tuesday, December 19, 2006 4:21 PM > Subject: Re: [egenix-users] mxODBC Zope DA and Linux Zope -- pooling not > increasing > > >> On 2006-12-15 17:34, David Krosel wrote: >>> Hello, >>> >>> Under stress testing running 20 web clients concurrently, the number >>> of "Physical connections" doesn't go higher than "1". By >>> observations, it is clear that multiple requests are pending since >>> only one connection is open to the database. >>> >>> My configuration is as follows: >>> >>> mxODBC Zope DA 1.0.10 >>> Zope 2.7.7 >>> Pool size = 21 >>> Number Zope threads = 21 >>> Linux Centos 4.3 >>> >>> The ODBC is configured for a local MySql 4.1.x >>> >>> Can you help? >> >> Do you see any error messages in the log file or the shell >> (when running Zope manually from the command line) ? >> >> It is possible that the ODBC driver doesn't allow multiple >> connections to the database for some reason. >> >> Which ODBC manager are you using ? >> >> If it's unixODBC, then you might be experiencing the following >> problem with unixODBC: >> >> """ >> When using mxODBC Zope DA with the unixODBC ODBC manager providing >> the connection to the ODBC driver, Zope appears to hang whenever a >> long running query is initiated on one of the Zope connections. >> >> This is due to the unixODBC manager applying a very restrictive >> thread isolation protection which basically serializes all requests >> to the drivers on a per process scope. >> >> For references, have a look at these links: >> >> http://www.unixodbc.org/odbcinst.html >> http://archives.postgresql.org/pgsql-odbc/2004-03/msg00060.php >> >> These are the available unixODBC Thread Levels (taken from the >> __handle.c file of unixODBC): >> >> * Level 0 - Only the DM internal structures are protected >> * the driver is assumed to take care of it's self >> * >> * Level 1 - The driver is protected down to the statement level >> * each statement will be protected, and the same for the connect >> * level for connect functions, note that descriptors are considered >> * equal to statements when it comes to thread protection. >> * >> * Level 2 - The driver is protected at the connection level. only >> * one thread can be in a particular driver at one time >> * >> * Level 3 - The driver is protected at the env level, only one thing >> * at a time. >> * >> * By default the driver open connections with a lock level of 3, >> * this can be changed by adding the line >> * >> * Threading = N >> * >> * to the driver entry in odbcinst.ini, where N is the locking level >> * (0-3) >> >> Fortunately, the fix is easy: just add the line >> >> Threading = 0 >> >> to the section in odbcinst.ini for the driver you are >> using, e.g. >> >> [PostgreSQL] >> Description = PostgreSQL driver for Linux & Win32 >> Driver = /usr/local/lib/libodbcpsql.so >> Setup = /usr/local/lib/libodbcpsqlS.so >> Threading = 0 >> >> Note that "Threading = 0" is normally only allowed for ODBC drivers >> which are fully multi-threaded, however, since the mxODBC Zope DA >> already provides the necessary thread protection at the connection >> level, you can get some added performance by disabling the additional >> protection in the unixODBC manager. >> >> The iODBC manager does not seem to have this problem. So this >> is a second alternative to solve the problem. >> """ >> >> -- >> Marc-Andre Lemburg >> eGenix.com >> >> Professional Python Services directly from the Source (#1, Dec 19 2006) >>>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ >> ________________________________________________________________________ >> >> ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::